alpine support?

Hi @artempartos, would you mind add more details for the request. Do you mean to use session manager plugin in alpine linux, or facing some issues when connecting to an alpine linux target?

Sorry, I mean I want to use it on alpine machine, it can't use rpm or deb packages.
Could you build bin for alpine as well, please?

Since the session manager client seems to be only a single binary I was able to just copy the binary from the deb to my alpine container with a multistage Dockerfile:
FROM ubuntu:20.04 as sessionmanagerplugin

RUN apt-get update \
    && apt-get install -y curl \
    && curl -Lo "session-manager-plugin.deb" "https://s3.amazonaws.com/session-manager-downloads/plugin/latest/ubuntu_64bit/session-manager-plugin.deb" \
    && dpkg -i "session-manager-plugin.deb"

FROM alpine:2.13

COPY --from=sessionmanagerplugin /usr/local/sessionmanagerplugin/bin/session-manager-plugin /usr/local/bin/

Not the cleanest solution but better than compiling it myself IMO.

Inspired by this comment, Dockerfile for session-manager-plugin compilation for Alpine
FROM golang:1.15.3-alpine as ssm-builder

ARG VERSION=1.2.279.0

RUN set -ex && apk add --no-cache make git gcc libc-dev curl bash zip && \
    curl -sLO https://github.com/aws/session-manager-plugin/archive/${VERSION}.tar.gz && \
    mkdir -p /go/src/github.com && \
    tar xzf ${VERSION}.tar.gz && \
    mv session-manager-plugin-${VERSION} /go/src/github.com/session-manager-plugin && \
    cd /go/src/github.com/session-manager-plugin && \
    make release

FROM alpine

COPY --from=ssm-builder /go/src/github.com/session-manager-plugin/bin/linux_amd64_plugin/session-manager-plugin /usr/local/bin/

Keep in mind that until this issue  is resolved, golang version has to be < 1.16

I hope session-manager-plugin is gonna be the next! https://github.com/aws/aws-cli/issues/4685

```dockerfile

Hi, I'm still getting "SessionManagerPlugin is not found. Please refer to SessionManager Documentation here: http://docs.aws.amazon.com/console/systems-manager/session-manager-plugin-not-found"
Do I need to do anything else with file /usr/local/bin/session-manager-plugin ?

Initially missed @Skaronator's solution because the following entry had more attention - nice work thanks!
My improvement on this is:
FROM amd64/ubuntu:20.04 as sessionmanagerplugin

ADD https://s3.amazonaws.com/session-manager-downloads/plugin/latest/ubuntu_64bit/session-manager-plugin.deb .
RUN dpkg -i "session-manager-plugin.deb"

FROM alpine

COPY --from=sessionmanagerplugin /usr/local/sessionmanagerplugin/bin/session-manager-plugin /usr/local/bin/

since it's cached.
Had tried the alpine builder, then used AWS's image for a slightly cleaner set of commands, but both unnecessarily build the binary each time and it's a significant wait.

@Skaronator
Hi, I'm still getting "SessionManagerPlugin is not found. Please refer to SessionManager Documentation here: http://docs.aws.amazon.com/console/systems-manager/session-manager-plugin-not-found"
Do I need to do anything else with file /usr/local/bin/session-manager-plugin ?

Did you ever figure it out? I'm getting the same issue:
/app # /usr/local/bin/session-manager-plugin
sh: /usr/local/bin/session-manager-plugin: not found

@raysn0w you need to install gcompat for it to work as the plugin depends on glibc (https://wiki.alpinelinux.org/wiki/Running_glibc_programs).

@raysn0w you need to install gcompat for it to work as the plugin depends on glibc (https://wiki.alpinelinux.org/wiki/Running_glibc_programs).

I have installed gcompat but still get the following:
~ # session-manager-plugin
ld-linux-x86-64.so.2: /usr/local/bin/session-manager-plugin: Not a valid dynamic program

I installed a glibc package instead: https://github.com/sgerrand/alpine-pkg-glibc?tab=readme-ov-file
That worked, but I am still wondering why gcompatdid not work.

this works for ARM / M1/Mx Mac. Tested on Alpine 3.18.6
apk add dpkg
curl "https://s3.amazonaws.com/session-manager-downloads/plugin/latest/ubuntu_arm64/session-manager-plugin.deb" -o "session-manager-plugin.deb"
cp session-manager-plugin/usr/local/sessionmanagerplugin/bin/session-manager-plugin  /usr/bin/session-manager-plugin

Copying a binary from another source doesn't solve the issue that as is today the session manager plugin can't be built from source on Alpine Linux.

This is the solution ended up working for us, a continuation of @bobbymaher's:
FROM alpine AS ssm-builder

ARG TARGETARCH

RUN apk add dpkg curl; \
    if [ "$TARGETARCH" = "arm64" ]; then \
     curl "https://s3.amazonaws.com/session-manager-downloads/plugin/latest/ubuntu_arm64/session-manager-plugin.deb" -o "session-manager-plugin.deb"; \
    else \
     curl "https://s3.amazonaws.com/session-manager-downloads/plugin/latest/ubuntu_64bit/session-manager-plugin.deb" -o "session-manager-plugin.deb"; \
    fi; \
    dpkg -x session-manager-plugin.deb session-manager-plugin

FROM alpine

COPY --from=ssm-builder /session-manager-plugin/usr/local/sessionmanagerplugin/bin/session-manager-plugin /usr/local/bin/

ARG TARGETARCH

# session-manager-plugin requires gcompat on amd64
RUN if [ "$TARGETARCH" = "amd64" ]; then \
     apk add --no-cache gcompat; \
    fi

RUN chmod +x /usr/local/bin/session-manager-plugin


Squeezelite player display suddenly useless

What version of Music Assistant has the issue?
2.0.0b70
The problem
Since I updated to 2.0.0b70 from 68 the display on my squeezelite devices only display the IP address of the MA server.
Previous versions would show Artist-Title and a visualizer on the display. BT, AirPlay, and Spotify show correct metadata.
How to reproduce
Update MA2.0 to the most recent version, play a track or a radio station. Display doesn’t change from: <IP_ADDRESS>:8096
Relevant log output
No response
Additional information
No response
What version of Home Assistant Core are your running
2023.8.1
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

Have you tried restarting MA or rebooting the host?

Yes, I've tried both. No change after a full restart of the host.
These are ESP32-A1S SqueezeESP32 boards to be specific (Firmware: squeezelite-esp32-master-v4.3-I2S-4MFlash-16-21335)

Ok will have to wait and see if this can be replicated as I don’t have one of these devices.

Today I connected a display to the Muse Luxe with squeezelite 2.1652-16#v4.3#Muse#master-v4.3. Tested it with bluetooth and airplay which displays correctly. Does not work with slimproto and only show double characters on one line. MA2.0.0b75

Is this still a problem?

We will close this soon due to no followup


MacOS brew install rust incompatibility with fdev

It should be noted that developers using brew install rust will run into issues when using fdev.
Here's how to replicate the problem:

$ brew install rust
$ curl https://sh.rustup.rs -sSf | sh
$ cargo install freenet fdev
$ rustup target add wasm32-unknown-unknown
$ cd <absolute path to identity-managent in freenet-core>
$ gmake build

The following is output from gmake build:
brew_build_output.txt
This problem can be avoided by not using the homebrew version of rust. Here's how to get fdev working again:

$ brew remove rust
$ gmake build

Here's the new (correct) output from gmake build:
cd /Users/redacted/Documents/GitRemotes/freenet-core/modules/identity-management
fdev build --package-type delegate --features contract
Compiling delegate with rust
   Compiling identity-management v0.0.1 (/Users/redacted/Documents/GitRemotes/freenet-core/modules/identity-management)
    Finished release [optimized] target(s) in 1.84s
cd /Users/redacted/Documents/GitRemotes/freenet-core/modules/identity-management
hash=$(bash -c "fdev inspect build/freenet/identity_management delegate | grep 'code hash:' | cut -d' ' -f3")
mkdir -p /Users/redacted/Documents/GitRemotes/freenet-core/modules/identity-management/build
echo -n $hash > /Users/redacted/Documents/GitRemotes/freenet-core/modules/identity-management/build/identity_management_code_hash
cd /Users/redacted/Documents/GitRemotes/freenet-core/modules/identity-management
cargo run -- --path /Users/redacted/Documents/GitRemotes/freenet-core/modules/identity-management/build
    Finished dev [unoptimized + debuginfo] target(s) in 0.10s
     Running `/Users/redacted/Documents/GitRemotes/freenet-core/target/debug/tool --path /Users/redacted/Documents/GitRemotes/freenet-core/modules/identity-management/build`
storing private key file: `identity-manager-key.private.pem`
storing private key file: `identity-manager-key.public.pem`
storing parameters file: `identity-manager-params`

currently same for windows. I will work as soon as we will have a stable network release.


Broken with Firefox

Hi,
The demo seems to be broken with Firefox. Tested with Iceweasel 38.0.1 on Debian.
The clock is not centered in the window and it is almost impossible to pick a value.
Can you reproduce this?
Thanks!
Vincent

I've fixed the issue in the 0.1 branch, however for 1.0 a new issue has popped up with regard to svg templates. I've opened a new issue for that.


forced-target does not work with target dependencies within same package

Problem
forced-target will fail when used with target dependencies defined in the same package that match that target.
thread 'main' panicked at 'activated_features for invalid package: features did not find PackageId { name: "regex", version: "1.8.1", source: "registry `crates-io`" } NormalOrDev', src/cargo/core/resolver/features.rs:321:14

Steps
Try to build a project with the following manifest:
cargo-features = ["per-package-target"]
[package]
name = "foo"
version = "0.1.0"
edition = "2021"
forced-target = "wasm32-unknown-unknown"

[target.'cfg(target_family="wasm")'.dependencies]
regex = "1"

This requires resolver=2.
Possible Solution(s)
There are several issues here:

Missing RustcTargetData information (which is being fixed in #12062).
The FeatureResolver doesn't know about per-package targets.
Feature resolution for per-package targets is up in the air at the moment.

Notes
No response
Version
cargo 1.71.0-nightly (569b648b5 2023-05-05)
release: 1.71.0-nightly
commit-hash: 569b648b5831ae8a515e90c80843a5287c3304ef
commit-date: 2023-05-05
host: aarch64-apple-darwin
libgit2: 1.6.3 (sys:0.17.0 vendored)
libcurl: 7.87.0 (sys:0.4.61+curl-8.0.1 system ssl:(SecureTransport) LibreSSL/3.3.6)
ssl: OpenSSL 1.1.1t  7 Feb 2023
os: Mac OS 13.3.1 [64-bit]

I've been thinking about this while reading the feature resolver code. I think the best way to support forced-target and default-target is to add those fields to the Summary type. I don't what that would entail, for the index side, but I think it would reduce the amount of changes needed for feature resolver to support these fields.


Update fault-wise-permission.md

Removed explicit ID
Was do to a build warning from the Netlify Plug-in
Could not parse redirect number 162:

  {"from":"/docs/chaos-engineering/chaos-faults/kubernetes/fault-wise-permissions","query":{},"to":"/docs/chaos-engineering/chaos-faults/kubernetes/permissions/Fault-wise","status":"permissions","force":false,"conditions":{}}

Invalid status code

Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[x] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is:

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://669fd304d4d6275cfbd22afa--harness-developer.netlify.app


Introduce retina support

This pull request will make circles look cool on devices that have devicePixelRatio bigger than one.

Please, fix the indentation in your code.
And could you, please, add at least one test for this functionality?

@kottenator I'm Sorry. Haven't checked indentation before pushing.
I've also posted some tests for this. Let me know if I'm not doing something correctly.

@kottenator Is there something more I can do in order to get this merged?

Try to remove setTimeout in your tests (and make them faster). I think you don't need them to check the canvas dimensions

@kottenator The problem is that modernizr no more includes it's build into bower package.

Do you want me to go about bundling modernizr into tests directory?

I'd be very happy if you'd fix it ;)

@kottenator Now it is strange. It's failing only on Firefox. And only inside travis build. I'm getting straight green on my local machine.

Yeah, that's strange. Did you test it locally on Firefox? Could you try to reproduce the bug somehow? (and of course, to fix it, because it's in your new tests :) )

Any progress on that? I'm interested in merging your PR

@kottenator I'm already using my fork in production and it works reasonable fine on every browser.
As I've said, I'm getting straight green on all tests locally locally. I'm not sure why it fails on travis. Maybe the version of firefox that is used there doesn't allow to change window.devicePixelRatio manually, via assignment?

This doesn't seem to fix the problem of having the circle loaded and then zooming in. It will still look pixelated. Can this be addressed as well or should it be a different issue?

@webjunkie Can you please give me reproduction and a couple of screens, so that I can see the problem? jsfiddle would also welcome.
I'm actually interested in finally getting this pull request done in the right way, I'm having some time now to investigate the problem.
@kottenator Nothing new about the failing tests?

@andreiglingeanu You can just zoom in to any example with your browser or mobile device. It's just a small edge case issue that is because this library relies on canvas and not something with vectors, I guess.

@kottenator Hi. I'm on this. Should provide a way to fix the tests today or tomorrow.

Move to #117.


feat(localization_launch): replace localization_launch with tier4_localization_launch

Signed-off-by: kminoda<EMAIL_ADDRESS>PR Type

Improvement

Related Links
Also need to merge https://github.com/tier4/aip_launcher/pull/98

Description
Remove localization_launch and use tier4_localization_launch in autoware.universe.
The parameter configuration in autoware.universe and autoware_launch has been modified as described in this issue.
With this modification, we are now able to pass parameter paths to tier4_xx_launch from the outside of the package, i.e. autoware_launch packages. Thus, I would like to remove xx_launch from tier4/autoware_launch and replace it with tier4_xx_launch in autoware.universe.
With this PR, we can reduce the maintenance cost of xx_launch.
(Before this PR: we need to modify both tier4_xx_launch and xx_launch. After this PR: we only need to modify tier4_xx_launch)

Review Procedure

Remarks
Please refer to this TIER IV internal link, too.

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Code follows coding guidelines
[x] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR: Required to pass before the merge.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@tkimura4 @h-ohta  I'll leave it to your judgment.

@kminoda Could you add some reason why you make this PR, e.g. issues etc?

The change looks good to me.
It's fine for me to merge if psim and lsim work well with this PR.

I confirmed starting autoware.launch.xml and logging_simulator.launch.xml

@h-ohta Sorry, would you approve this again?

@h-ohta Sorry, would you approve this again? :bow:

@YamatoAndo Regarding the issue due to https://github.com/autowarefoundation/autoware.universe/pull/2114, I think there are two solutions

Fix aip_launcher and incorporate the modification in https://github.com/autowarefoundation/autoware_launch/pull/108
Provide /sensing/lidar/top/... as a pointcloud_container_name from autoware_launch (no need for modification in aip_launcher)

I thought 2 would be a simple and thus better for a temporary solution. What do you think?

@kminoda If it is a temporary solution, option 2 would be fine.


Work banner test in android device but not real banner

hi i can't show real banner in android device, this work fine with banner test but not with real banner code, in ios emulator work fine too, i can't understand what is wrong

So it works with an admob test ID but does not work with your real id?

yes, don't work with real id only in android

I reinstalled all the project and now works fine, please close this, best regards


Allow choosing cache compression algorithm explicitly

Copy of actions/toolkit#544 for using this possibility here in case it got added to actions/toolkit first :-)

Currently the compression algorithm for caches is chosen implicitly according to what tools and versions are available on an environment.
It would be nice if it were possible to instead manually select the compression algorithm, including choosing no compression algortithm.
The use-case is, that I build something on one environment and want to test it on multiple others.
I don't want to use artifacts for that, as that is not really their intention imho and you also cannot delete the artifacts.
Imho the cache with the workflow run id as cache key should be better suited for inter-job file sharing.
But you currently have the problem, that if you for example build on a gzip environment like windows-latest and then try to restore on a zstd environment like windows-2016, you get a cache miss.
actions/toolkit#543 would improve on that example, but as soon as you swap it around and build on windows-2016, wanting to test on windows-latest, actions/toolkit#543 would not help.
So it would be nice if you could manually select the compression algorithm in the cache-action (and therefore having it possible here first), to be able to choose the lowest common denominator (including no compression) that can be understood on all part-taking environments.

.

+1

Hi @Vampire @pratikbin the idea of choosing own compression algorithm is not planned to be worked on in the near future. Please visit #984 and provide feedback on the current proposed changes to tar compression. Closing as wontfix.


Scene with spatial understanding components crashes on IL2CPP (HoloLens)

Overview
I wanted to have a simple scene that visualizes the spatial mapping mesh as the HoloLens scans. The example scene only worked in the editor, so I've rebuilt the scene with the same prefabs and deployed it on a HoloLens which worked on the .NET backend. However, when on IL2CPP it crashes when calling the native function GeneratePlayspace_InitScan.
I looked into the native sources and the underlying DLL seems to use the cdecl calling convention. However, as far as i know the CLR on Windows x86 defaults to stdcall for P/Invoke, so I'm not entirely sure why it works at all if that is the case.
Expected Behavior
The spatial mesh is rendered as is the case on .NET backend.
Actual Behavior
The app crashes with the error message "Run-Time Check Failure #0 - The value of ESP was not properly saved across a function call.  This is usually a result of calling a function declared with one calling convention with a function pointer declared with a different calling convention."
Steps to reproduce

Clone the repo at https://github.com/Holo-Krzysztof/SpatialMappingCrashRepro
Build the project with IL2CPP (default for UWP since Unity 2017.2)

Unity Editor Version
2017.2.1
Mixed Reality Toolkit Release Version
2017.2.1

Might want to open this on the main Mixed Reality Toolkit

The bug is in the bindings though; I guess there's no error on the native side.
It'd be possible to change the calling convention to __stdcall there, but I'm not sure whether that's desired or if it breaks other platforms. So I think the better solution is to annotate the DllImports with CallingConvention.Cdecl.

Ahh, thanks for clearing that up.

I'm going to try to do that and report back if it works.


Discover database resources with third-party providers

Initial pass at Discovery feature.

Heroku
AWS (partially, no way to get db/user/pass for RDS instance)

This is highly experimental feature and still work-in-process.

@bsx thanks for  the feedback. i'll add the missing aurora stuff (i've used your code as a base) and aws config file support.

@bsx have a look at the latest build here, i've added AWS config support (with profiles). It does work, although it's kinda limited because there's no way to switch AWS profiles using the web UI.


Self registration and connecting with a certificate

Hello! Do you currently support a way to connect with a certificate so that I can register users? I want to do some fancy stuff with ACL and groups and to my knowledge you can only add users to groups if they are registered.

Unfortunately, no, certificates aren't currently supported.
That being said it shouldn't be too hard to add the feature, I believe you'd only need to use a certificate in the ssl.AuthenticateAsClient in MumbleTCPConnection line 68.
I can't work on that right now, but if you get that working I'd happily accept a PR

Ok. I'll see what I can hack together. In the meantime can you mark this as an enhancement/feature?


Fractal goose 10K

The file format of each file has been carefully checked ~ please pass

Please change the slug name to the folder name.

@fackjack001

I have modified it and hope it can be approved. Thank you~~~

Please help me review it. Can I merge it in?
The #goose community is looking forward to it~~Thank you

Looks great!
cloud6605 @.***>于2024年10月19日 周六下午3:40写道：

Merged #623
https://github.com/unisat-wallet/fractal-ordinals-collections/pull/623
into main.
—
Reply to this email directly, view it on GitHub
https://github.com/unisat-wallet/fractal-ordinals-collections/pull/623#event-14729662741,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDCVHPDHZRNGDFLAQUU3EDLZ4IEHPAVCNFSM6AAAAABQA6GBVGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUG4ZDSNRWGI3TIMI
.
You are receiving this because you were mentioned.Message ID:
<unisat-wallet/fractal-ordinals-collections/pull/623/issue_event/14729662741
@github.com>

Shaniqua Tlucek @.***>于2024年10月19日 周六下午3:42写道：

Looks great!
cloud6605 @.***>于2024年10月19日 周六下午3:40写道：

Merged #623
https://github.com/unisat-wallet/fractal-ordinals-collections/pull/623
into main.
—
Reply to this email directly, view it on GitHub
https://github.com/unisat-wallet/fractal-ordinals-collections/pull/623#event-14729662741,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDCVHPDHZRNGDFLAQUU3EDLZ4IEHPAVCNFSM6AAAAABQA6GBVGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUG4ZDSNRWGI3TIMI
.
You are receiving this because you were mentioned.Message ID:
<unisat-wallet/fractal-ordinals-collections/pull/623/issue_event/14729662741
@github.com>

Hello, I would like to inquire now when the collection of #GOOSE community
will be displayed on #UNISAT MARKET, because many people in the community
are anxiously waiting for its launch and purchase their favorite #GOOSE
thank you.

cloud6605 @.***>于2024年10月18日 周五上午11:37写道：

image.png (view on web)
https://github.com/user-attachments/assets/d20e8a46-4db2-4e74-b8ef-6b8d05bb4214

Please change the slug name to the folder name.
image.png (view on web)
https://github.com/user-attachments/assets/638cf8f6-8d21-4a84-aac4-259f61f9a606
@fackjack001 https://github.com/fackjack001

—

Reply to this email directly, view it on GitHub
https://github.com/unisat-wallet/fractal-ordinals-collections/pull/623#issuecomment-2421233570,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDCVHPBTB46MX5IOAC7IOJDZ4B7AFAVCNFSM6AAAAABQA6GBVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRRGIZTGNJXGA
.
You are receiving this because you were mentioned.Message ID:
@.***
com>

Hello, thank you very much. Now you can see the collection compiled by the
#GOOSE community on the UNISAT market. However, since the source images are
all in HTML format, can you adjust it in the background so that it is
suitable like OKX-market? The proportion is displayed, thank you very
much~~~


fix cookie handling with different cookie params

We need to remove the existing cookie. If the cookie domain, path or something else got altered via session_set_cookie_params() then it does not get deleted without these params.
Another thing is the missing refresh of session cookie when you have set a specific lifetime of a session cookie.

@tflori Thanks for contributing :+1:
Could you add a test that demonstrates the issue, and then we can ensure this change fixes it, and we're protected from future regressions?

@duncan3dc that's a problem. it was not tested before and headers_list() does not return the cookie that got set in cli mode - I think the hole functionality of set_cookie() is disabled in cli.

@tflori Ok, I'll take a look when I get a minute and see if I can find a way to test, thanks

2 weeks ago.. I like this lib, it's small and easy but I don't want to work with dev branch. So please consider to merge.

Hi @tflori, sorry I didn't get chance to resolve this yet, I'll merge it as soon as I can

@tflori I've added some tests that use the built in webserver to test cookies now, so if you could write a failing test for your issue then we can demonstrate that this pr fixes it, thanks

@duncan3dc I've added the tests. In this tests I found out that destroy a session creates a new session with wrong name and sends a second cookie PHPSESSID... I fixed this too by calling $this->init() instead of @session_start()

@duncan3dc what about this PR?

@tflori It looks like the tests are failing on PHP 5.6, could you make the regular expression less restrictive? Or maybe use the guzzle cookie parsing so that you can just check the relevant parts of the cookie?

@duncan3dc i've fixed them already:
https://travis-ci.org/duncan3dc/sessions/builds/183076797

@tflori Sorry I wasn't clear, that test still relies on very specific formatting of the cookie, and tests parts of it we don't care about, for instance we aren't testing that it's httponly, so the test shouldn't fail if the cookie returns "HTTPONLY"

in SessionInstance in line 64 and 189 we using $cookieParam['httponly'] - we define this param in tests/web/sub/bootstrap.php and this has to be tested too. The cookie we update or delete should exactly match with the cookie that php generates. That was the reason to check if the line also includes [Hh]ttp[Oo]nly

@duncan3dc I'm waiting for a release with this fix since 11th december. Three weeks ago you had a question. I answered. Everything is ready.
Without progress I will have to fork this package.

Sorry for the delay @tflori, but I need to be careful what code I accept in the project, as I then must maintain that code and support users with it indefinitely.
Are you happy for me to merge this and then adjust the tests to only test the things we need to test?

Hi @tflori, I've pushed some changes to master that should handle everything you need, you can inject a Cookie instance to manage the cookie settings now. Can you check and let me know if there's anything missing/broken from your use case? Sorry again for the delay on this

It is not solving anything for non-session cookies. It just adds another class to hold information that is already handles by php itself.
Before I liked your session library - it was small, simple and allows to have simultaneous request using the same session even with session_handler files.

Sorry @tflori, the changes I've made mean that the library now respects session cookie parameters and ensures they are used when starting the session. I understood that was the issue.
Please could you help me to understand any remaining issues?

session_set_cookie_params() can be executed before. Or the Params can be set in the ini file. It worked before too.
There are two remaining issues:

PHP does never delete the cookie. If you have a lot of traffic on your page and mostly the people are not signed in and don't have a session - you don't even have to look for a session file (or key in redis) and this makes it some bit faster. But you need to delete the cookie - it will be nice when the session manager handles this.
PHP does not refresh the cookie. A lot of websites (including our big friends google and github) store sessions for longer than a browser session - you are still logged in, right? You will have to refresh the cookie to stay logged in. Imagine your cookie is valid for 7 days and it never gets refreshed: after 7 days while browsing on this website you are suddenly logged out (intruder alert - someone must have stolen my cookie). It will be nice if session manager handles this too.

That are my changes and this I'm testing. To make this work the cookie has to be exactly what php is sending including HttpOnly and the one thing I still can't test: secure only.

@duncan3dc I added two tests. one to show session_start is required and one to show session_destroy is required. I hope we can come to an end now.

Hi Thomas, I've merged your work into master now, could you check it out to see if it fixes your issues?
Thanks again for your patience, I think you've helped to make the library much better and I'm glad you contributed :+1:

@duncan3dc yes it works for me but there is untested code. you can remove the cookie params in destroy without any error. also the code will not work for someone that is not using cookies.
anyway it needs some cleanup now. I don't understand why you not just merged the pr instead of squashed commited something different.
I'm very unhappy to contribute to this library anymore.


f3d::reader API could be simplified

Is your feature request related to a problem? Please describe.
With the addition of the meta importer in https://github.com/f3d-app/f3d/pull/1609, the f3d::reader API could be simplified has it can now only provided an importer, either the full scene importer or generic importer

Actually, since vtkF3DGenericImporter is not part of the public VTK module, it cannot be done.
Making it public is not worth it imo.


upgrade packer to version 1.5.6

This PR bumps packer to version 1.5.6.
I feel that we should automate this process instead of manually bumping versions. Any idea how we can achieve that @mariux ?

This PR bumps packer to version 1.5.6.
I feel that we should automate this process instead of manually bumping versions. Any idea how we can achieve that @mariux ?

we could but we need to update unless something important is fixed or implemented... so we do not need to catch every version... this might even introduce new bugs...


Improve the UI of the About Us page

Fixes : #44
UI of the /about us page changed, now it looks like modern about us page.
And when user click on FAQs button user scrolled down to FAQ section.
Also set up tailwind CSS so contributors can apply styles easily from now on.
https://github.com/user-attachments/assets/41122304-944c-4317-ae4c-ecf859315a05

@SatyamThakur0 , It is looking nice. But this theme is not matching with our UI theme please use our theme color or it's similar variants..... and LMK!

Thankyou @vishalverma9572  for merging my PR,
Soon I will design the homepage too which matches the about page.


More honest internal method name

Sorry, I didn't get a chance to look through #50 fully so I missed this - if I was reading tar-rs I'd be pretty suprised at read_all not doing what it says on the tin!

Oh the min on the with_capacity part is actually just limiting memory allocation, this helper still consumes the entire Entry for all the data that it contains. It's just a little more efficient if one call to read can be made instead of multiple

That's embarrassing, sorry.

Oh no worries! Thanks for taking a look :)


Restructure frontend files into component-based folders

Context
Currently, the frontend code of our app is organized in a way in which most components contain a single .tsx file with all of the component's logic, styles, and rendered HTML markup in one place. The file structure is also organized in a way in which most components sit at the root of the dashboard or other subfolder preventing the components and their related files from being grouped in the most intuitive way.
As we begin to design out a new potential dashboard for the recommendations feature and further expand the app's UI, we should refactor and organize our frontend in a way that groups a component and its related assets/subcomponents into a single folder for better navigation, organization of concerns, and maintainability.
Example:
CarbonIntensityMap
├── __snapshots__
│   └── CarbonIntensityMap.test.tsx.snap
├── AWSMap.svg
├── AzureMap.svg
├── CarbonIntensityMap.test.tsx
├── CarbonIntensityMap.tsx
├── GCPMap.svg
├── index.ts
└── carbonIntensityStyles.ts

Tasks
For each primary dashboard component, do the following:

[x] Create a subfolder in /dashboard with the component names in uppercase format (i.e. dashboard/CarbonIntensityMap) to hold each of the component's files and supporting assets
[x] Move the primary component into that subfolder, and update import paths as necessary (IntelliJ or VSCode should do this for you)
[x] Create an index.ts file to export the component as the directory's default export (for easy imports)
[x] Move test file of component into new subfolder
[x] Identify any rendered subcomponents (i.e. ApexBarChart.ts) and move them as well as their test files into the subfolder (make sure imports and paths are updated)
[x] Check for any remaining assets (images, specific helper files, etc) and move them into the new folder as well

Afterwards:

[x] Run Changesets, bump any packages that have been updated/changed
[x] Did you make changes to the client, api or cli package? If so, considering updating the create-app templates.

Tech/Implementation Details
This could also be a good opportunity to identify and organize any reused subcomponents into a common folder.
Good resource, especially for index exporting: https://medium.com/bootstart/you-should-be-using-folder-components-b30b7d165c39

The CarbonIntensityMap was created with this directory pattern in mind, so it can be a good reference for how each component directory should look.

We may need to think about where to place non-dashboard specific components such as the InfoSidebar (previously named CarbonFormulaDrawer), HeaderBar, ErrorPage, and others. One idea that came up is a src/common folder for what will eventually be common components, styles, and other reused files.

Today we focused on extracting non-dashboard specific files and commonly used components/helpers into an appropriate subdirectories of the src folder (utils, layouts, and common). This cleans up the smaller subdirectories and loose files that were spread across the src and dashboard folders, with scalable thinking as far as what organization would work best as we plan to add new pages to the dashboard.
Preview of new directories:
layout
│   ├── ErrorPage
│   │   ├── ErrorPage.test.tsx
│   │   ├── ErrorPage.tsx
│   │   └── index.ts
│   ├── HeaderBar
│   │   ├── HeaderBar.tsx
│   │   └── index.ts
│   └── InfoSidebar
│       ├── InfoSidebar.test.tsx
│       ├── InfoSidebar.tsx
│       ├── __snapshots__
│       │   └── InfoSidebar.test.tsx.snap
│       └── index.ts
utils
    ├── data
    │   ├── data.json
    │   ├── generateEstimations.test.ts
    │   ├── generateEstimations.ts
    │   └── index.ts
    ├── helpers
    │   ├── index.ts
    │   ├── transformData.test.ts
    │   └── transformData.ts
    ├── hooks
    │   ├── EmissionFactorServiceHook.test.ts
    │   ├── EmissionFactorServiceHook.ts
    │   ├── RemoteServiceHook.test.ts
    │   ├── RemoteServiceHook.ts
    │   └── index.ts
    └── models
        └── types.ts

Next steps:

Dive into dashboard/filters and dashboard/charts to ensure that those components are properly organized and exported, and which should be extracted.
Give the dashboard folder a name that's representative of the page view it now holds. In addition, the CarbonCloudContainer.tsx should share the same name as well as be organized as the primary component/container for that page. (Some ideas that came up were EmissionsMetricsPage, EmissionsPage, and EmissionsInsightsPage)

Today we focused on extracting dashboard specific files and filters into appropriate subdirectories. We added a new pages directory under under src/pages and moved the EmissionssMetricPage(previously named dashboard) and all its components to this new directory. This cleans up smaller subdirectories and sets the base for the new project structure as we plan to add new pages to the dashboard.
Preview of new subdirectories under src:
pages
└── EmissionsMetricsPag
│   ├──ApexDonutChart
│   ├──CarbonComparissonCard
│   ├──CarbonIntensityMap
│   ├──CloudUsage
│   ├──EmissionsBreakdownCard
│   └── FilterBar
│       └── Filters
│       │   └── AccountFilter.test.tsx
│       │   ├── AccountFilter.tsx
│       │   ├── CloudProviderFilter.tsx
│       │   ├── DateFilter.test.tsx
│       │   ├── DateFilter.tsx
│       │   ├── DropdownFilter.tsx
│       │   ├── MonthFilter.test.tsx
│       │   ├── MonthFilter.tsx
│       │   ├── ServiceFilter.test.tsx
│       │   ├── ServiceFilter.tsx
│       │   └── index.ts
│       └── utils
│           └──  DropdownConstants.test.ts
│           ├── DropdownConstants.ts
│           ├── FilterHook.test.ts
│           ├── FilterHook.ts
│           ├── Filters.test.ts
│           ├── Filters.ts
│           ├── FiltersUtil.test.ts
│           ├── FiltersUtil.ts
│           ├── __mocks__
│           │   └── Filters.ts
│           └── options
│               └──  AccountChooser.ts
│               ├── CloudProviderChooser.ts
│               ├── OptionChooser.ts
│               ├── ServiceChooser.ts
│               ├── common.ts
│               └── index.ts
├──EmissionsMetricsPage.test.tsx
├──EmissionsMetricsPage.tsx
└──index.ts

We haven't run the changeset or make any updates to the create-app templates as we wanted to have these new changes be reviewed before we do this.

Looking great, I think I only have two questions / points of feedback:

packages/client/src/pages/EmissionsMetricsPage/CloudUsage -- I feel like this could be named ApexLineChart given that is what is contained in it. (the tooltip is only used in the line chart).
I'm not sure the models/types.ts should exist in the utils directory, as it's not really utility classes/functions.... It's only not really models, so maybe just move the file inside src directory and call it Types.ts for now?

Looking great, I think I only have two questions / points of feedback:

packages/client/src/pages/EmissionsMetricsPage/CloudUsage -- I feel like this could be named ApexLineChart given that is what is contained in it. (the tooltip is only used in the line chart).
I'm not sure the models/types.ts should exist in the utils directory, as it's not really utility classes/functions.... It's only not really models, so maybe just move the file inside src directory and call it Types.ts for now?

Thanks for the feedback, Dan! In regards to your questions/comments:

We named the folder 'CloudUsage' because there is some containing logic that we were gonna extract from the EmissionsMetricsPage that had the styling and wrapping container elements for the ApexLineChart. We were gonna name that new container file CloudUsage and do the actual extraction as part of the work for a separate ticket that will focus on cleaning up that EmissionsMetricsPage component. However, if you don't think that's necessary, we can leave it and rename the folder!
You're probably right. The models subfolder already existed, so we just moved it in under utils and left it as a folder in case we ever decided to add a new types file for other pages/components. But I do agree, we can just leave it under src for now and cross that bridge if we ever get there.

I'm not 100% sure I follow the reasoning behind 1, but maybe could we rename the directory to EmissionsOverTimeChart as that is what the Line Chart is all about... CloudUsage is just to vague/broad -- the whole front-end is about "Cloud Usage". Hope that makes sense.

That makes sense! I think we could definitely rename it to something better than Cloud Usage so we'll make that change


added :vim command

:vim to open file with gui vim (gvim, macvim, etc)
use after set gvimpath in .ideavimrc
example :
set gvimpath=/usr/local/opt/macvim/bin/mvim

Place add ex model :g command, this is very useful.

Hi!
After some discussions, we decided not to include this command in IdeaVim because the original vim has a completely different meaning of this command. If the user wants to have this command, he should define it using :command.

I would add that in the original Vim this case is handled by :!vim % and we would like to have something similar in IdeaVim so that an interactive command is executed in the Terminal tool window similar to what you've implemented for :shell.


Migrate to Go modules

Sorry for my absence.
I checked the migration to Go modules from Godep and looks nice.
Go 1.12 or later is required, and export GO111MODULE=on (until Go 1.13).
How about this?

@st0012 Updated the .travis.yml. I think Go 1.11 or earlier should be out-of-scope.

@hachi8833 I wonder why this was working even if we didn't update .travis.yml 🤔

@st0012 I guess Go 1.11 has already the Go modules feature.

@hachi8833 If the migrate is compatible with previous Go versions, I think we should still support them in .travis.yml

That makes sense. I updated .travis.yml

@hachi8833 thanks for all the work ❤


Updating effects via useFrame

I've started a thread over in the react-three-fiber discussions (https://github.com/react-spring/react-three-fiber/discussions/595), but I'm wondering if you can add some insight. How should effects be updated after they're changed via useFrame? Sending these along to the EffectsComposer via state is not very efficient. And setting state inside of useFrame is really not a good idea.

tbh I don't know, better ask @drcmda
if u want to update ur effect conditionally, use useLayoutEffect hook like here:
  useLayoutEffect(() => {
    if (depthTexture) {
      effect.setDepthTexture(depthTexture.texture, depthTexture.packing)
    }
  }, [depthTexture])

usage with useFrame - idk the best way to combine it w/ rpp

i tried it out and it works, but you need to know postprocessing internals because the constructor parameters that you pass have are mapped to internals.
for instance this is how you fade Blooms luminianceThreshold:
function Effects() {
  const ref = useRef()
  useFrame((state) => {
    if (ref.current) {
      ref.current.luminanceMaterial.threshold = 0.1 + (1 + Math.sin(state.clock.getElapsedTime() * 2)) / 3
    }
  }, [])
  return (
    <EffectComposer>
      <Bloom ref={ref} KernelSize={KernelSize.VERY_LARGE} height={400} opacity={2} />
      <SSAO />
    </EffectComposer>
  )
}

now that's unfortunate and mostly due to postprocessing not using getter/setters but contructor parameters. react-postprocessing could try to abstract this but it seems rather hacky, and pp could thrash that in any patch version.

Wow, that's a process for sure. But, nice work hacking this together! I really appreciate it.

for this btw we could really need help, it would be easy to do:
import { BloomEffect as BloomEffectImpl } from 'postprocessing'

class BloomEffect extends BloomEffectImpl {
  set luminanceThreshold(v) { this.luminanceMaterial.threshold = v }
  get luminanceThreshold() { return this.luminanceMaterial.threshold }
  ...
}

the react-pp effects would then instanciate that instead of the original. if you want @robksawyer PR's welcome 🙂

I think it's safe to close this


HMR 'reload on save' breaks on import but build does not

Describe the bug
HMR reload on save breaks when importing with "wrong" case.
import Xyz from 'Xyz.svelte'✅
vs
import Xyz from 'xyz.svelte' ❌ no reload
Reproduction

Import component import X from "x.svelte" (notice the lower case)
Modify X and the expected update does not happen.

Example:
2 iframes showing two routes where one imports Component.svelte and another component.svelte
https://github.com/mallsoft/hmr-bug-reprod
Logs
No response
System Info
Windows 10
Firefox 100.0 64
VSCode
Terminal - bash

Severity
annoyance
Additional Information
No response

Relevant discord thread https://discord.com/channels/457912077277855764/970337730712186921

You must always use the exact case of the filename on disk when importing, even on case insensitive file systems.
To be honest i am surprised building works without errors in your case, your reproduction produces errors on both pnpm dev and pnpm build in a case sensitive file system (ext4)
I suggest you turn on case sensitivity in your file system (options exist for windows and mac) to get immediate feedback when using the "wrong" case.
There is also an enhancement pending in vite to warn you about case inconsistencies: https://github.com/vitejs/vite/issues/964
closing here as an upstream issue exists


Disable binding for layout props

Disable bindings for layout props, following the discussion here: https://github.com/mui/mui-toolpad/pull/804
I decided to keep the underlying infrastructure for layout bindings just in case we still want it in the future.

This will conflict with changes I'm making in https://github.com/mui/mui-toolpad/pull/838/files#diff-ec80be28f55d9a65ffd34db07be05d96cde782bcd9ace685dc77515e840cfb91L65
I believe disabled should just mean disabling the whole control.

This will conflict with changes I'm making in https://github.com/mui/mui-toolpad/pull/838/files#diff-ec80be28f55d9a65ffd34db07be05d96cde782bcd9ace685dc77515e840cfb91L65 I believe disabled should just mean disabling the whole control.

ok, no rush for me to merge this one for me so we can merge yours first and then i can see how to make my PR work with the new changes

This will conflict with changes I'm making in https://github.com/mui/mui-toolpad/pull/838/files#diff-ec80be28f55d9a65ffd34db07be05d96cde782bcd9ace685dc77515e840cfb91L65 I believe disabled should just mean disabling the whole control.

I've updated this PR according to these changes.


[ArchReview] Add a Range Class to Azure Core

Add a class that corresponds to the Range header into Azure Core. Many of our client libraries have their own implementation and it would be nice to centralize it.

I think this ship has sailed and we probably missed it. This can probably be closed.


wsl-tech-preview-md: Fix typo

Proposed changes
Fixed a typo (missing space)

Deploy preview for docsdocker ready!
Built with commit f9dd088a3b0062ef9ab32d7e37f7c52e324f8b7a
https://deploy-preview-10093--docsdocker.netlify.com


Page storage location?

After creating a page using GUI, where the HTML file of the page get stored?

@rajatguptarg why do you mean specifically? The pages get dynamically created according to the pages you create. /cc @mkoistinen @yakky

@rajatguptarg there is no such thing as "HTML file of the page". pages are generated on the fly by aggregating content from database + templates + whatever, in the same way as any django application does


Include a checksum for Zarr archives in the Dataset checksum

Changelogs

Integrated a checksum for Zarr archives in the Polaris Dataset.
In accordance with the Apache 2 license, added a separate NOTICE and LICENSE file.

Checklist:

[X] Was this PR discussed in an issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.
[X] Add tests to cover the fixed bug(s) or the newly introduced feature(s) (if appropriate).
[X] Update the API documentation if a new function is added, or an existing one is deleted.
[X] Write concise and explanatory changelogs above.
[X] If possible, assign one of the following labels to the PR: feature, fix or test (or ask a maintainer to do it for you).

How it works
To understand how this works, I was quite happy with this docstring:
Consider the following directory structure:
               . (root)
              / \
             a   c
            /
           b

Within zarr, this would for example be:
- root: A Zarr Group with a single Array.
- a: A Zarr Array
- b: A single chunk of the Zarr Array
- c: A metadata file (i.e. .zarray, .zattrs or .zgroup)
To compute the checksum, we first find all the leaves (i.e. all the files below the root) in the tree, in this case b and c. We compute the hash of the content (i.e. the raw bytes) for each of these files. This uses md5.
We then work our way up the tree. For any node (directory), we find all children of that node. In an deterministic order, we then serialize a list with - for each of the children - the checksum, size, and number of children. The hash of the directory is then equal to the hash of the serialized JSON.
The Polaris implementation is heavily based on the zarr-checksum package. The deviation is the compute_zarr_checksum method.
Note: This implies the checksum can change, even if the content doesn't. For example because you rechunk the dataset. I think this fits the use-case of Polaris, but I wanted to raise it anyways.
Questions

Are we happy with the checksum for the Dataset.table attribute? This is not easy to compute on the Hub, so maybe we would be better of saving the table to .parquet and computing the hash for the bytes of that file? This would be a change that breaks backwards compatibility.
Are we happy with the use of md5? There are other hashing functions, specifically for checksum, that are faster (at the cost of being less cryptographically secure)
How should the checksum be used? Right now, we always compute the checksum on creating a dataset object. Is that what we want? We should probably distinguish downloads / uploads of chunks from downloads / uploads of the entire archive.

Thanks, @Andrewq11.
To answer your questions:

Might be missing something here but why would we need to compute the checksum on the hub?

why not just then shift to individual chunk checksums only

Because we want to know if the entire dataset was uploaded / downloaded successfully. If not, a Dataset should for example not be made public on the Hub. This means we don't only need to verify the data integrity of every individual chunk, but we also need to check if those chunks are organized as expected within the Zarr archive.

a faster hashing function might be needed depending on if the number of chunks to download becomes exceedingly large.

One issue with changing hashing functions, is that we need to make sure to Hub supports the same hashing function. One argument in favor of md5 is that I believe the md5 hash to already be returned "for free" in the headers when we fetch a file from the R2 bucket.

Because we want to know if the entire dataset was uploaded / downloaded successfully. If not, a Dataset should for example not be made public on the Hub.

So we would need to download the zarr archive to the hub directly? Is this the correct flow?
Client computes the checksum for the zarr archive -> uploads it to R2 ->  the Hub downloads the dataset -> the Hub calculates and confirms checksums match.
If so, I could see this being an issue on the Hub when datasets get sufficiently large. I think we would likely need a dedicated service with enough memory and disk space available to complete the download and perform the check.

This means we don't only need to verify the data integrity of every individual chunk, but we also need to check if those chunks are organized as expected within the Zarr archive.

Makes sense, thank you.

One issue with changing hashing functions, is that we need to make sure to Hub supports the same hashing function. One argument in favor of md5 is that I believe the md5 hash to already be returned "for free" in the headers when we fetch a file from the R2 bucket.

That would be very handy if so. This seems like something that could be useful to benchmark in the future and see if we could get any significant gains using different hashing functions.

Just came across this: Instead of manually saving the checksum to R2, we could also a codec like this one: https://numcodecs.readthedocs.io/en/latest/checksum32.html
Although this lets us verify the integrity of individual chunks, I don't think it covers our use case. We would also need to be able to lookup the checksums on the Hub to verify the entire dataset was uploaded correctly.

@cwognum : I'm seeing new activity here. Should this be part of the all-Zarr dataset we had talked about?

@cwognum : I'm seeing new activity here. Should this be part of the all-Zarr dataset we had talked about?

I'm not sure I understand what you mean. We already "support" Zarr datasets, so we will need this checksum anyways, independent of when we plan to pursue the all-Zarr dataset. Or am I missing something?


Extend core templates

The selection of templates for core branch is quite limited.
I would expect at least

F# templates on par with C#
Precompiled functions templates

I can see that templates are loaded from https://functionscdn.azureedge.net/public/templates.json.

Is there a way to send a pull request to this file?
Is there a way to substitute this file with my own (for personal use / demos)?

Yeah, we hope to have some cycles to focus on the F# experience soon.
The templates are kept here: https://github.com/azure/azure-webjobs-sdk-templates
With some Fiddler filters, you can set a response for that API and return your own payload (either from a local file or something on GitHub, for example).

Thanks for the pointers @fabiocav
If I understand it correctly, CLI uses portal templates. Does it mean there are no plans to add precompiled templates to CLI (since they won't work in the portal)?

@mikhailshilkov precompiled functions can be deployed from VS, so they are supposed to be working in portal. Thus you can write a template (for that repository: https://github.com/azure/azure-webjobs-sdk-templates).
I also need that template, since precompiled functions should be much faster.

@PoisonousJohn Yes, "won't work" was bad wording. I meant that there isn't much sense to create precompiled functions in the portal directly, since they will be read-only.

@fabiocav does this CLI use "VS" templates? I want to understand what kind of template should I add to support precompiled .net core project.

Bumping this - any ETA on F# templates for v2?
This is my first time dealing with Azure Functions, and I must say it's a tad confusing. Most of the blog posts were written about 1.0 (where F# templates were available for .NET Framework on Windows), but didn't explicitly refer to the version number. I was unaware of this, so created a project using 2.0 (which has no templates), and had no idea why "func new" wasn't allowing me to select "F#".

@fabiocav where we can found templates for v2?
How we can make changes to https://functionscdn.azureedge.net/public/templates.json ?
Thanks.

@fabiocav any news?


feat: flavor refactor, reduce duplication

Reduces duplication in Flavor classes by using a macro that combines pointer_view with struct fields (along with a new get_all getter that is perhaps more ergonomic) and subclassing. Note that this is a stepping stone, ideally https://github.com/AztecProtocol/barretenberg/issues/788 is used instead of multiple inheritance
Also resolves https://github.com/AztecProtocol/barretenberg/issues/784

Introduces a RefVector class, like std::vector<T&> (which is impossible). It is backed by a pointer, and gives operator[] and iterator semantics on the underlying derefenced pointer. Compare std::vector<std::reference_wrapper>, which would operate more like actual pointers (you change the reference, not the value held by the reference).
Introduces a get_all alternative to pointer_view that uses RefVector, update other types to use RefVector, get rid of the HandleType in flavor entity classes
Removes some flavor base classes that didn't do much after array backing removal. Now we get rid of virtual base class methods here, but I don't think it makes sense to do polymorphism in two ways. We can instead use concepts if we want to constrain this with a static assert
Introduces macros that define flavor classes in flavor_macros.hpp. These remove duplication of pointer view and normal listing.
Use inheritance to remove duplication in the larger AllEntities classes in GoblinUltra and GoblinTranslator
Removes modernize-use-nodiscard - too noisy a linter setting, I doubt we'd hit a bug that it would fix (i.e. if you return error codes it can be useful to not ignore them).

Benchmark results
Metrics with a significant change:

note_history_trial_decrypting_time_in_ms (10): 202 (+29%)
note_trial_decrypting_time_in_ms (8): 99.8 (+433%)
note_trial_decrypting_time_in_ms (32): 93.4 (+589%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 5cfbb68b and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,984
868,052
3,449,504

l1_rollup_execution_gas
842,071
3,595,160
22,204,873

l2_block_processing_time_in_ms
2,048 (+1%)
7,627 (-2%)
30,133 (-1%)

note_successful_decrypting_time_in_ms
296 (-6%)
883 (-2%)
3,214 (-2%)

note_trial_decrypting_time_in_ms
:warning: 99.8 (+433%)
:warning: 93.4 (+589%)
141

l2_block_building_time_in_ms
20,671 (-3%)
82,122 (-1%)
329,257

l2_block_rollup_simulation_time_in_ms
11,973 (-3%)
47,566 (-1%)
189,891 (-1%)

l2_block_public_tx_process_time_in_ms
8,655 (-1%)
34,415 (-1%)
138,838

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
21,964 (-1%)
43,089 (-1%)

note_history_successful_decrypting_time_in_ms
2,134 (+1%)
4,193 (+1%)

note_history_trial_decrypting_time_in_ms
126 (-1%)
:warning: 202 (+29%)

node_database_size_in_bytes
1,625,763
1,095,758 (-1%)

pxe_database_size_in_bytes
29,748
59,307

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
772
61,697
18,905

private-kernel-ordering
128
24,297
8,153

base-rollup
1,763
656,428
873

root-rollup
173 (+2%)
4,072
1,097

private-kernel-inner
795
81,568
18,905

public-kernel-private-input
573
41,519
18,905

public-kernel-non-first-iteration
410
41,561
18,905

merge-rollup
15.6
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
8,787
27,547

@codygunton I have checked timings and they are similar + re-added noexcept just in case, but I'm sure it was just cargo cult copied over. I have gone over review feedback and adjusted or responded accordingly


screen resizable/closable/maximizable/iconifiable

Currently a modal screen/content has default options: close, resize
It should be possible to change this default options. Server sends following boolean properties:
"screen_closable_"
"screen_resizable_"
"screen_iconfiable_"
"screen_maximizable_"
"content_closable_"
"content_resizable_"
"content_iconfiable_"
"content_maximizable_"
Please use what's supported. I don't know if maximizable/iconifiable are supported.

added support for closable, resizable and maximizable, iconfiable is not supported


Bruno won't send ndjson body properly

Context
In Elasticsearch, when you want to do a bulk indexing, you send all documents in JSON separated by new lines (known as ndjson or jsonl format). According to standard and Elasticsearch, body should end with a new line.
Problem
In Bruno, it seems there's no way to send a body that ends with a new line, I tried JSON format or text, it doesn't matter. Seems somehow newline is removed somewhere. When I use "generate code" and copy the curl it's fine but when I run it in bruno Elasticsearch complains.
Sample .bru file:
meta {
  name: Bulk add 22
  type: http
  seq: 47
}

post {
  url: {{ES_URL}}/tmp/_bulk
  body: json
  auth: none
}

headers {
  Content-Type: application/json
}

body:json {
  { "update" : {"_id" : "6"}
  { "doc" : {"f1" : 8}, "doc_as_upsert" : true}

}

Sample cURL:
curl --request POST \
  --url http://localhost:9200/tmp/_bulk \
  --header 'Content-Type: application/json' \
  --data '{ "update" : {"_id" : "6"}
{ "doc" : {"f1" : 8}, "doc_as_upsert" : true}
'

Error returned from Elasticsearch (only when run with bru):
{
  "error": {
    "root_cause": [
      {
        "type": "illegal_argument_exception",
        "reason": "The bulk request must be terminated by a newline [\\n]"
      }
    ],
    "type": "illegal_argument_exception",
    "reason": "The bulk request must be terminated by a newline [\\n]"
  },
  "status": 400
}

When I run an nc on my local, I get a weird body being sent:
➜  ~ nc -l 9200
POST /tmp/_bulk HTTP/1.1
Accept: application/json, text/plain, */*
Content-Type: application/json
request-start-time:<PHONE_NUMBER>192
User-Agent: axios/1.5.1
Content-Length: 93
Accept-Encoding: gzip, compress, deflate, br
Host: localhost:9200
Connection: close

"{ \"update\" : {\"_id\" : \"6\"}\n{ \"doc\" : {\"f1\" : 8}, \"doc_as_upsert\" : true}\n\n\n"

BTW keep up good work 🙌 I'm waiting for my golden edition ☺

When you use json as body-type, then your request should not work -- since newline-delimited-json is not json.
But using "text" as body-type absolutely should work. I encountered the same bug in my workaround here: https://github.com/usebruno/bruno/issues/1768#issuecomment-1994262911

Aha! It seems this behavior only happens if you manually set the Content-Type: application/json header!
Arguably, bruno should just send the body as-is, allowing you to send malformed json, but in your case, you can just set the header to application/x-ndjson, which is more appropriate anyways.

When you use json as body-type, then your request should not work -- since newline-delimited-json is not json.

It's not standard JSON but It works with curl or any other client as Elasticsearch accepts this Content-Type. Bruno is messing with the content.
At least if it's not a proper JSON I don't think it's good to turn it into a big JSON string, that's not what user ever intends. I think modifying body should never happen, unless you want to add some goodies, e.g. I saw if I comment a JSON line with // it will be skipped in the output. This can be a nice feature. But every JSON blob, and turning invalid JSON into a JSON string is too much.

But using "text" as body-type absolutely should work. I encountered the same bug in my workaround here:

It doesn't work I tried it 😅, body type doesn't change the behavior. Text or JSON body, with or without JSON content type, it will mess up the body.

this behavior only happens if you manually set the Content-Type: application/json header

Even if I don't set any headers this will happen as well. The only solution is what you said, setting content type to application/x-ndjson.

Unfortunately, this behavior is (mostly) caused by the underlying axios library: https://github.com/axios/axios/blob/d844227411263fab39d447442879112f8b0c8de5/lib/defaults/index.js#L42
I tend to agree with @Rmaan : Bruno is a testing tool and should send the body exactly as I define it, even if that violates some standard. Seeing what an API does with malformed data is a core part of testing.

Interesting, I think we can copy the default transformer and remove the stringifySafely function. That is the weird behavior that if JSON.parse fails it will do a JSON.stringify instead.


fix(error handler): fix confusing error message

fixes #496

Coverage remained the same at 87.46% when pulling ce7955562f81287f42aa4146b819f60d279bd0c6 on error-handler into be99bc41a7a0f1ef95d74946294f9a5e1efdcd6c on master.


Switch from 'provided' dependency to 'annotationProcessorsPath' for Maven projects

annotationProcessorsPath looks more natural and less invasive than provided dependency

The documentation is updated. The tests still use the old approach as there is no direct way to define annotation processors path from the local file system.
The only solution which comes to my mind is to configure a local maven repo per-test and install traute-javac there. Later on, that local repo can be configured for tests. However, it requires a significant amount of changes and it looks like the benefit doesn't worth it.


Bug in nullBytes(), trueBytes() and falseBytes() overwriting unparsed buffer space

Discovered while trying to debug the cause for huge memory consumption by go-json, more on that in a separate issue.
Problem
At the beginning of nullBytes(), trueBytes() and falseBytes(), the code checks whether the buffer has still enough data in it left to read the whole token (null/true/false). If not, it tries to read more from the reader:
https://github.com/goccy/go-json/blob/4d51b8b764e125e7f6715e037b196210d81c5ee4/decode_string.go#L236-L241
https://github.com/goccy/go-json/blob/4d51b8b764e125e7f6715e037b196210d81c5ee4/decode_bool.go#L16-L21
https://github.com/goccy/go-json/blob/4d51b8b764e125e7f6715e037b196210d81c5ee4/decode_bool.go#L38-L43
There's two problems with that:
Overwriting remaining buffer data
s.read() overwrites everything in the buffer from the current cursor onwards. See s.readBuf(), it returns a slice beginning from the current cursor position:
https://github.com/goccy/go-json/blob/4d51b8b764e125e7f6715e037b196210d81c5ee4/decode_stream.go#L67
...in which the new data is read next:
https://github.com/goccy/go-json/blob/4d51b8b764e125e7f6715e037b196210d81c5ee4/decode_stream.go#L77
if the cursor isn't at the very last position of the remaining data in the buffer (s.length-1, I think), everything from the cursor position onwards gets overwritten and is lost.
This is the case in nullBytes(), trueBytes() and falseBytes(), it looks ahead and reads new data while the cursor isn't at the end of the current data left in the buffer.
Potentially insufficient data read from stream
These functions only call s.Read() once, however s.Read() isn't guaranteed to read enough bytes to include the entire value. An io.Reader, can very well only return 1 char, or even 0 (even though that's discouraged):

If some data is available but not len(p) bytes, Read conventionally returns what is available instead of waiting for more.
Implementations of Read are discouraged from returning a zero byte count with a nil error, except when len(p) == 0. Callers should treat a return of 0 and nil as indicating that nothing happened; in particular it does not indicate EOF.

https://golang.org/pkg/io/#Reader
Instead, in places like these, s.read() should be called in a loop, until it either has read enough chars to fit the entire expected value, or it returns false due to an unexpected EOF or whatever.
This also touches the memory consumption problem I have, but I'll open a separate issue for that, with some pprof data and a reproduction benchmark if I can get one to work.

I understood your point. I will fix this.

Sorry, I was busy otherwise, so I didn't have time to prepare some code.
But I can confirm that #208 is looking good, and the test from #199 was exactly how I'd have crafted the JSON,
that is placing a null (or true or false) right around the 1024th char, so that it begins within the initial buffer (which is 2*initBufSize long, but ends afterwards.


next auth Authentification

Basically next auth to handle authentification.
https://authjs.dev/

can explain little bit more about issue?

Basically create authentification for the application.
Currently there is no auth. On demo we are using clerk.dev, which is quite easy to implement. But I think people will benefit from proper auth.
Basically need to primarily work on the frontend folder I think.

If this issue is open I can work upon it

Would be great, please do, ill assign it to you for now

hey i saw there is nothing yet from code or UI to sign in or sign up in dev mode in frontend folder ...am i correct?

hey @dartpain i saw there is nothing yet from code or UI to sign in or sign up in dev mode in frontend folder ...am i correct? And also which type of auth should i use ..github or google and how can i get their api keys ...i shouldn't be using my personal ones ig

@dartpain @aaditya9899 Dear all, any update for authentication funcation?

hey @dartpain i saw there is nothing yet from code or UI to sign in or sign up in dev mode in frontend folder ...am i correct? And also which type of auth should i use ..github or google and how can i get their api keys ...i shouldn't be using my personal ones ig

@dartpain @aaditya9899 Dear all, any updates on authentication function development?

hey @dartpain i saw there is nothing yet from code or UI to sign in or sign up in dev mode in frontend folder ...am i correct? And also which type of auth should i use ..github or google and how can i get their api keys ...i shouldn't be using my personal ones ig

@dartpain @aaditya9899 Dear all, any updates on authentication function development?

Yeah I was working upon it just stuck on that doubt so couldn't continue...

@aaditya9899 https://github.com/aaditya9899 which API key you need?
clerk.com API key?
On Wed, 18 Oct 2023 at 12:47, aaditya9899 @.***> wrote:

hey @dartpain https://github.com/dartpain i saw there is nothing yet
from code or UI to sign in or sign up in dev mode in frontend folder ...am
i correct? And also which type of auth should i use ..github or google and
how can i get their api keys ...i shouldn't be using my personal ones ig
@dartpain https://github.com/dartpain @aaditya9899
https://github.com/aaditya9899 Dear all, any updates on authentication
function development?
Yeah I was working upon it just stuck on that doubt so couldn't continue...
—
Reply to this email directly, view it on GitHub
https://github.com/arc53/DocsGPT/issues/369#issuecomment-1767633246, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A76VNQROFK6SPDYFBOEVYE3X75NM3AVCNFSM6AAAAAA5PFYPECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRXGYZTGMRUGY
.
You are receiving this because you commented.Message ID:
@.***>

--
P Help save paper - do you need to print this email?

@aaditya9899 https://github.com/aaditya9899 which API key you need? clerk.com API key?
…
On Wed, 18 Oct 2023 at 12:47, aaditya9899 @.> wrote: hey @dartpain https://github.com/dartpain i saw there is nothing yet from code or UI to sign in or sign up in dev mode in frontend folder ...am i correct? And also which type of auth should i use ..github or google and how can i get their api keys ...i shouldn't be using my personal ones ig @dartpain https://github.com/dartpain @aaditya9899 https://github.com/aaditya9899 Dear all, any updates on authentication function development? Yeah I was working upon it just stuck on that doubt so couldn't continue... — Reply to this email directly, view it on GitHub <#369 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A76VNQROFK6SPDYFBOEVYE3X75NM3AVCNFSM6AAAAAA5PFYPECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRXGYZTGMRUGY . You are receiving this because you commented.Message ID: @.>
-- P Help save paper - do you need to print this email?

In these auth provider services I mean
export const authOptions = {
  // Configure one or more authentication providers
  providers: [
    GithubProvider({
      clientId: process.env.GITHUB_ID,
      clientSecret: process.env.GITHUB_SECRET,
    }),
    // ...add more providers here
  ],
}

CAN we make those auth. API key configurable in .env file? let user input
by themselves.
On Thu, 19 Oct 2023 at 18:49, aaditya9899 @.***> wrote:

@aaditya9899 https://github.com/aaditya9899
https://github.com/aaditya9899 which API key you need? clerk.com API key?
… <#m_3141642545070216470_>
On Wed, 18 Oct 2023 at 12:47, aaditya9899 @.> wrote: hey @dartpain
https://github.com/dartpain https://github.com/dartpain
https://github.com/dartpain i saw there is nothing yet from code or UI to
sign in or sign up in dev mode in frontend folder ...am i correct? And also
which type of auth should i use ..github or google and how can i get their
api keys ...i shouldn't be using my personal ones ig @dartpain
https://github.com/dartpain https://github.com/dartpain
https://github.com/dartpain @aaditya9899 https://github.com/aaditya9899
https://github.com/aaditya9899 https://github.com/aaditya9899 Dear all,
any updates on authentication function development? Yeah I was working upon
it just stuck on that doubt so couldn't continue... — Reply to this email
directly, view it on GitHub <#369 (comment)
https://github.com/arc53/DocsGPT/issues/369#issuecomment-1767633246>, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A76VNQROFK6SPDYFBOEVYE3X75NM3AVCNFSM6AAAAAA5PFYPECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRXGYZTGMRUGY
https://github.com/notifications/unsubscribe-auth/A76VNQROFK6SPDYFBOEVYE3X75NM3AVCNFSM6AAAAAA5PFYPECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRXGYZTGMRUGY
. You are receiving this because you commented.Message ID: @.>
-- P Help save paper - do you need to print this email?
In these auth provider services I mean
export const authOptions = {
// Configure one or more authentication providers
providers: [
GithubProvider({
clientId: process.env.GITHUB_ID,
clientSecret: process.env.GITHUB_SECRET,
}),
// ...add more providers here
],
}
—
Reply to this email directly, view it on GitHub
https://github.com/arc53/DocsGPT/issues/369#issuecomment-1770556801, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A76VNQSW6T3WFVFKFCDSA6DYAEAS5AVCNFSM6AAAAAA5PFYPECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZQGU2TMOBQGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
P Help save paper - do you need to print this email?

CAN we make those auth. API key configurable in .env file? let user input by themselves.
…
On Thu, 19 Oct 2023 at 18:49, aaditya9899 @.> wrote: @aaditya9899 https://github.com/aaditya9899 https://github.com/aaditya9899 which API key you need? clerk.com API key? … <#m_3141642545070216470_> On Wed, 18 Oct 2023 at 12:47, aaditya9899 @.> wrote: hey @dartpain https://github.com/dartpain https://github.com/dartpain https://github.com/dartpain i saw there is nothing yet from code or UI to sign in or sign up in dev mode in frontend folder ...am i correct? And also which type of auth should i use ..github or google and how can i get their api keys ...i shouldn't be using my personal ones ig @dartpain https://github.com/dartpain https://github.com/dartpain https://github.com/dartpain @aaditya9899 https://github.com/aaditya9899 https://github.com/aaditya9899 https://github.com/aaditya9899 Dear all, any updates on authentication function development? Yeah I was working upon it just stuck on that doubt so couldn't continue... — Reply to this email directly, view it on GitHub <#369 (comment) <#369 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A76VNQROFK6SPDYFBOEVYE3X75NM3AVCNFSM6AAAAAA5PFYPECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRXGYZTGMRUGY https://github.com/notifications/unsubscribe-auth/A76VNQROFK6SPDYFBOEVYE3X75NM3AVCNFSM6AAAAAA5PFYPECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRXGYZTGMRUGY . You are receiving this because you commented.Message ID: @.> -- P Help save paper - do you need to print this email? In these auth provider services I mean export const authOptions = { // Configure one or more authentication providers providers: [ GithubProvider({ clientId: process.env.GITHUB_ID, clientSecret: process.env.GITHUB_SECRET, }), // ...add more providers here ], } — Reply to this email directly, view it on GitHub <#369 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A76VNQSW6T3WFVFKFCDSA6DYAEAS5AVCNFSM6AAAAAA5PFYPECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZQGU2TMOBQGE . You are receiving this because you were mentioned.Message ID: @.**>
-- P Help save paper - do you need to print this email?

yeah we can do that , let me implement it with GitHub first then will see of the other providers as well , sounds okay?

just having one more doubt , should I implement it in front end or backend.... next js auth give some issues in frontend and in backend i am having a bit difficulty in understanding where should it be implemented as there is no overall index or route file ...

We need to implement in both. Basically need to make sure requests are authorised to backend with jwt token too.

sure but is the frontend in next js?

Currently its react, but I think for next auth we might need to migrate to nextjs


Fix flaky errors with py3

We ran into some test failures while using jsonschema==2.4.0 with python3.  The failures were intermittent (approximately 1 in every 10 runs), but were reproducible in both py33 and py34 (py26 and py27 were unaffected).
You can see the failures in travis-ci for this PR https://github.com/Yelp/swagger_spec_validator/pull/11 or use that branch to reproduce them (tox -e py34). The best example is test_success in this build.
The code calling jsonschema is pretty straightforward:
resolver = RefResolver('file://{0}'.format(schema_path), schema)
jsonschema.validate(json_document, schema, resolver=resolver)

The error is:
Unresolvable JSON pointer: 'definitions/simpleTypes'

I added a bunch of debugging to jsonschema to see what was happening. From what I can tell, RefResolver.resolve_fragment() is being called with a ref of definitions/simpleTypes but the current base_uri in the RefResolver is actually http://swagger.io/v2/schema.json instead of what it should be (http://json-schema.org/draft-04/schema).
I also noticed that the ordering was totally undefined, every run would produce a different call stack.  Some orderings would fail, and some would succeed, but there was definitely more than one order which caused it to fail.  I tried a few things, and found that adding this sorted() to iterations before descend() resolved the problem.  I tried with list() as well, but that didn't solve the problem.
Without being able to completely explain the problem, I can say that this fixes it. My understanding is that some combination of the undefined order of fields, and the lazy evaluation of iteritems() causes some call stack which results in the wrong state.

It turns out that some part of #182 also fixes this bug

replaced by the solution in #203


[admin] (Versioning) Add moniker to TOC fusion

Adding a moniker and the build support for a new PPT moniker.

Docs Build status updates of commit 0720328:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 4a1cbf8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


chore(isolated-declarations): remove outdated panic comment

#7462  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Nov 25, 12:27 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
Nov 25, 12:27 AM EST: A user added this pull request to the Graphite merge queue.


External IP stuck in Pending

When running "kubectl get service azure-vote-front --watch" my external IP status has been pending for approximately 3 hours. What could be causing this IP to not allocate?

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

ID: a7e0a294-1b8a-1711-6f80-cb9ee87730ad
Version Independent ID: 46e6645b-48ca-fa7c-1fb9-bc3442fde1d7
Content: Kubernetes on Azure tutorial  - Deploy Application
Content Source: articles/aks/tutorial-kubernetes-deploy-application.md
Service: container-service
GitHub Login: @neilpeterson
Microsoft Alias: nepeters

Thanks for the feedback! We are currently investigating and will update you shortly.

@jdogg89 if you cancel the command and try again does it present the same behavior?

Similar issue #10465

@jdogg89 I tested this and it took about 2 mins to update:
image
You can cancel the watch operation and run the command ubectl get service azure-vote-front --watch again to see if the process has changed

@jdogg89 any update on this?

It seems to be an intermittent issue, right now, I'm no longer experiencing
it.
On Thu, Jun 21, 2018, 2:53 PM Micah<EMAIL_ADDRESS>wrote:

@jdogg89 https://github.com/jdogg89 any update on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/10427#issuecomment-399222656,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASXGZXC-p0PP5dnUp7LR1LW9ajc9AesLks5t-_mcgaJpZM4Ut7t-
.

@jdogg89 thanks for the update.
Since I cannot repo this and your unblocked I will close this out for now. If the issue comes back please come back to this issue and we can reopen and investigate further :)

same


BUG: Fix blas + axpy by only using it for certain cases

Only use blas axpy for 1D arrays or contiguous arrays.

cc @SuperFluffy

Other than the negative and zero stride case, did you find anything that would prevent using blas for non-contiguous but equispaced/compatible arrays?

It should be fine. Equispaced stride doesn't cover one case though, which is F1 + F2 (both arrays are 2+ dimensions, same shape, but in fortran memory order).

Changed to a revert since it broke existing uses of is_contiguous (for negative stride arrays). It's my responsibility to decide on merges, so it's my responsibility there is a bug.

A clearer thought on the situation is that we have two input arrays, and we need to figure out if they are separately blas compatible, but also that they are memory order compatible with each other. Same problem that zip needs to solve.


ng-select does not consistently select when using keyboard

Bug observed in Google Chrome 45.0.2454.101. Bug NOT observed in Firefox 41.
JSFiddle using Angular 1.4.7 available here: https://jsfiddle.net/oeo9h2vh/5/
In the case where a select box is populated with multiple items with the same first letter, attempting to select the second item, by typing the first letter via the keyboard, does not update the ID. After selecting the third, the selection updates as expected.
Basic steps:

Tab into a select box with N>2 items with the same first letter (using 's' as an example).
Hit 's' to select the first. ng-model is updated.
Hit 's' to select the second. ng-model is NOT updated.
Hit 's' to select the third. ng-model is updated.
All subsequent updates function as expected.

It looks like this is a dupe of https://github.com/angular/angular.js/issues/9134


XAMPP on Debian 12

[Enter feedback here]
Its seem like it doesnt work in Xampp on Debian 12. Doesnt seem to load the modules no matter where it is placed.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: ebfbb264-f108-d1a9-24f0-0a120bd05891
Version Independent ID: f7eac012-d453-c553-cbba-359ca8dfcbb3
Content: Microsoft Drivers for PHP for SQL Server - PHP drivers for SQL Server
Content Source: docs/connect/php/microsoft-php-driver-for-sql-server.md
Service: sql
Sub-service: connectivity
GitHub Login: @David-Engel
Microsoft Alias: v-davidengel

### Tasks

@davcheong Thanks for your feedback. We appreciate it. To make sure we have all the information needed to triage your issue, please provide more context around the general task.

Hi Tim,
I am currently manually downloaded sqlsrv using debian11-8.2.tar, extracted the files and placed under lib/php/extensions and also i have nano php.ini added extension=/path of php_sqlsrv_8.2.so after reboot or restarted moving around the driver and change in php.ini, and whenever i check on phpinfo, sqlsrv module was never loaded. In which i cant use sqlsrv_query on my php.
Kindly help and guide is there anyway?
Using Xampp 8.2.4
Debian 12

@davcheong -- thank you for your feedback. This seems to be a product issue, rather than a documentation issue. Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@davcheong If those resources don't pan out for you, you could also file an issue at the Microsoft/msphpsql repo. They should be able to help you troubleshoot your configuration.
Regards,
David

@davcheong If those resources don't pan out for you, you could also file an issue at the Microsoft/msphpsql repo. They should be able to help you troubleshoot your configuration.
Regards, David

Thanks David. Will do. I have tried many times still failed to load the sqlsvr.

@davcheong If those resources don't pan out for you, you could also file an issue at the Microsoft/msphpsql repo. They should be able to help you troubleshoot your configuration.
Regards, David

Sorry type so fast to reply, how to we file an issue at this page repo, coz i thought i did. Or i didnt manage to. Coz my 1st time use github.
Thanks in advance for the guide.

@davcheong -- please go to the link in David's answer, then select "Issues" in the top row.  The Issues page should have a green "New issue" button.


Unhandled promise rejection wenn Unifi Controller nicht erreichbar ist mit js-controller 3.2.x

Beim Testen vom js-controller 3.2.x (verwendete Version 3.2.6-4) kommt folgende Fehlermeldung wenn der Unifi Network Controller nicht erreichbar ist.
Unifi Adapter v.0.5.8

host.beebox(iobrokerMaster)
2021-01-16 16:54:48.711
info
Restart adapter system.adapter.unifi.0 because enabled

host.beebox(iobrokerMaster)
2021-01-16 16:54:48.710
error
instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

host.beebox(iobrokerMaster)
2021-01-16 16:54:48.710
error
Caught by controller[0]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)

host.beebox(iobrokerMaster)
2021-01-16 16:54:48.709
error
Caught by controller[0]: Error: connect EHOSTUNREACH <IP_ADDRESS>:8443

host.beebox(iobrokerMaster)
2021-01-16 16:54:48.709
error
Caught by controller[0]: This error originated either by throwing  inside of an async function without a catch block, or by rejecting a  promise which was not handled with .catch(). The promise rejecte

unifi.0
2021-01-16 16:54:48.068
warn
(27765) Terminated (UNCAUGHT_EXCEPTION): Without reason

unifi.0
2021-01-16 16:54:48.066
info
(27765) terminating

unifi.0
2021-01-16 16:54:48.065
info
(27765) cleaned everything up...

unifi.0
2021-01-16 16:54:48.035
error
(27765) Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH <IP_ADDRESS>:8443

unifi.0
2021-01-16 16:54:48.035
error
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)

unifi.0
2021-01-16 16:54:48.035
error
(27765) Error: connect EHOSTUNREACH <IP_ADDRESS>:8443

unifi.0
2021-01-16 16:54:48.034
error
(27765) unhandled promise rejection: connect EHOSTUNREACH <IP_ADDRESS>:8443

unifi.0
2021-01-16 16:54:48.033
error
(27765) Unhandled promise rejection. This error originated either by  throwing inside of an async function without a catch block, or by  rejecting a promise which was not handled with .catch().

unifi.0
2021-01-16 16:54:44.711
info
(27765) UniFi adapter is ready

unifi.0
2021-01-16 16:54:44.659
info
(27765) starting. Version 0.5.8 in /opt/iobroker/node_modules/iobroker.unifi, node: v12.18.3, js-controller: 3.2.6-4

host.beebox(iobrokerMaster)
2021-01-16 16:54:42.147
info
instance system.adapter.unifi.0 started with pid 27765

javascript.0
2021-01-16 16:54:31.175
info
(26800) script.js.Skripte.Lueftung: Lüftung.js - Betriebszustand Lüftungsanlage:0

host.beebox(iobrokerMaster)
2021-01-16 16:54:12.079
info
Restart adapter system.adapter.unifi.0 because enabled

host.beebox(iobrokerMaster)
2021-01-16 16:54:12.078
error
instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

host.beebox(iobrokerMaster)
2021-01-16 16:54:12.077
error
Caught by controller[1]:     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)

host.beebox(iobrokerMaster)
2021-01-16 16:54:12.076
error
Caught by controller[1]: Error: connect EHOSTUNREACH <IP_ADDRESS>:8443

host.beebox(iobrokerMaster)
2021-01-16 16:54:12.070
error
Caught by controller[0]: This error originated either by throwing  inside of an async function without a catch block, or by rejecting a  promise which was not handled with .catch(). The promise rejecte

unifi.0
2021-01-16 16:54:11.405
warn
(27691) Terminated (UNCAUGHT_EXCEPTION): Without reason

unifi.0
2021-01-16 16:54:11.402
info
(27691) terminating

unifi.0
2021-01-16 16:54:11.400
info
(27691) cleaned everything up...

unifi.0
2021-01-16 16:54:11.366
error
(27691) Exception-Code: EHOSTUNREACH: connect EHOSTUNREACH <IP_ADDRESS>:8443

unifi.0
2021-01-16 16:54:11.365
error
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16)

unifi.0
2021-01-16 16:54:11.365
error
(27691) Error: connect EHOSTUNREACH <IP_ADDRESS>:8443

unifi.0
2021-01-16 16:54:11.364
error
(27691) unhandled promise rejection: connect EHOSTUNREACH <IP_ADDRESS>:8443

unifi.0
2021-01-16 16:54:11.363
error
(27691) Unhandled promise rejection. This error originated either by  throwing inside of an async function without a catch block, or by  rejecting a promise which was not handled with .catch().

javascript.0
2021-01-16 16:53:31.165
info
(26800) script.js.Skripte.Lueftung: Lüftung.js - Betriebszustand Lüftungsanlage:0

unifi.0
2021-01-16 16:53:07.316
info
(27691) Update done

unifi.0
2021-01-16 16:52:52.809
info
(27691) UniFi adapter is ready

unifi.0
2021-01-16 16:52:52.758
info
(27691) starting. Version 0.5.8 in /opt/iobroker/node_modules/iobroker.unifi, node: v12.18.3, js-controller: 3.2.6-4

Der Adapter kommt offenbar noch nicht mit node.js 14.x zurecht ¯(ツ)/¯
Nachdem ich zurück auf den 12.22.1 gewechselt habe, funktioniert der automatische Adapterstart wieder.

Problem besteht noch

Ich bekomme das Problem, wenn ich in Proxmox stopp-backups mache. Bei snapshots kommt es nicht.

Fehler besteht noch immer
2021-12-13 11:55:07.128  - error: unifi.0 (1563) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2021-12-13 11:55:07.128  - error: unifi.0 (1563) unhandled promise rejection: connect ECONNREFUSED <IP_ADDRESS>:8443 2021-12-13 11:55:07.128  - error: unifi.0 (1563) Error: connect ECONNREFUSED <IP_ADDRESS>:8443 2021-12-13 11:55:07.128  - error: unifi.0 (1563) Exception-Code: ECONNREFUSED: connect ECONNREFUSED <IP_ADDRESS>:8443 2021-12-13 11:55:07.138  - info: unifi.0 (1563) cleaned everything up... 2021-12-13 11:55:07.138  - info: unifi.0 (1563) terminating 2021-12-13 11:55:07.140  - warn: unifi.0 (1563) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-12-13 11:55:07.754  - error: host.ioBroker instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-12-13 11:55:07.754  - info: host.ioBroker Restart adapter system.adapter.unifi.0 because enabled 2021-12-13 11:55:37.800  - info: host.ioBroker instance system.adapter.unifi.0 started with pid 10328 2021-12-13 11:55:38.635  - info: unifi.0 (10328) starting. Version 0.5.10 in /opt/iobroker/node_modules/iobroker.unifi, node: v14.17.1, js-controller: 3.3.19 2021-12-13 11:55:38.651  - info: unifi.0 (10328) UniFi adapter is ready 2021-12-13 11:55:38.719  - error: unifi.0 (10328) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2021-12-13 11:55:38.720  - error: unifi.0 (10328) unhandled promise rejection: connect ECONNREFUSED <IP_ADDRESS>:8443 2021-12-13 11:55:38.720  - error: unifi.0 (10328) Error: connect ECONNREFUSED <IP_ADDRESS>:8443 2021-12-13 11:55:38.720  - error: unifi.0 (10328) Exception-Code: ECONNREFUSED: connect ECONNREFUSED <IP_ADDRESS>:8443 2021-12-13 11:55:38.726  - info: unifi.0 (10328) cleaned everything up... 2021-12-13 11:55:38.728  - info: unifi.0 (10328) terminating 2021-12-13 11:55:38.728  - warn: unifi.0 (10328) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-12-13 11:55:39.346  - error: host.ioBroker instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-12-13 11:55:39.346  - info: host.ioBroker Restart adapter system.adapter.unifi.0 because enabled 2021-12-13 11:56:09.394  - info: host.ioBroker instance system.adapter.unifi.0 started with pid 10345 2021-12-13 11:56:10.272  - info: unifi.0 (10345) starting. Version 0.5.10 in /opt/iobroker/node_modules/iobroker.unifi, node: v14.17.1, js-controller: 3.3.19 2021-12-13 11:56:10.287  - info: unifi.0 (10345) UniFi adapter is ready 2021-12-13 11:56:10.345  - error: unifi.0 (10345) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2021-12-13 11:56:10.345  - error: unifi.0 (10345) unhandled promise rejection: connect ECONNREFUSED <IP_ADDRESS>:8443 2021-12-13 11:56:10.345  - error: unifi.0 (10345) Error: connect ECONNREFUSED <IP_ADDRESS>:8443 2021-12-13 11:56:10.345  - error: unifi.0 (10345) Exception-Code: ECONNREFUSED: connect ECONNREFUSED <IP_ADDRESS>:8443 2021-12-13 11:56:10.351  - info: unifi.0 (10345) cleaned everything up... 2021-12-13 11:56:10.352  - info: unifi.0 (10345) terminating 2021-12-13 11:56:10.353  - warn: unifi.0 (10345) Terminated (UNCAUGHT_EXCEPTION): Without reason 2021-12-13 11:56:11.443  - error: host.ioBroker instance system.adapter.unifi.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2021-12-13 11:56:11.443  - info: host.ioBroker Restart adapter system.adapter.unifi.0 because enabled 2021-12-13 11:56:11.443  - warn: host.ioBroker Do not restart adapter system.adapter.unifi.0 because restart loop detected

Problem besteht weiter, auch mit JS-Controller 4.0.21 und Node.js 14.19.0.

Bitte GitHub version testen

0.6.0 on GitHub ... @Feuer-sturm please report

@Apollon77 I will check  on wednesday

@Apollon77 Issue is fixed :-) Thank you.
New log entry if unify controller is not online:

unifi.0
2022-06-07 21:44:08.603
error
Error site undefined: Host or network cannot be reached.

unifi.0
2022-06-07 21:44:05.277
info
UniFi adapter is ready