SESSION_COOKIE_SAMESITE not woking

I wanted to embed web page to iframe, but got cross-site issue.  The solution was set SESSION_COOKIE_SAMESITE = None.  The feature have existed after flask 1.0 #2607 changed log
But no matter what I set, the samesite attribute has never shown up.
I can assure that flask and werkzung both are right version.  #1549
Expected Behavior

Set-Cookie: session=<session>; Expires=Mon, 23-Nov-2020 11:58:00 GMT; Path=/; secure; samesite=<whatever I set>

Actual Behavior

Set-Cookie: session=<session>; Expires=Mon, 23-Nov-2020 11:58:00 GMT; Path=/; secure

Environment

Python version: 3.6
Flask version: 1.1.2
Werkzeug version: 1.0.1

The literal value None means "not set". Set it to the string "None" to set it to samesite=none.

"None"

I have already tried and failed.  It's not woking.

Then there's something else wrong with your code. As demonstrated in the example above, setting samesite=none works as expected.
Please use Stack Overflow for questions about your own code. This tracker is for issues related to the project itself. Be sure to include a minimal, complete, and verifiable example.


Update code on rubygems

toto doesn't work with ruby 1.9+ but it fixed in the repo but not published.


Change file name to add links

I tried adding a  tag to my storybook and it didn't work according to old instructions. So I referenced a few projects and it seems that it has changed, i.e. https://github.com/bufferapp/buffer-components/blob/master/.storybook/head.html
Issue:
What I did
How to test

@VonIobro preview-head.html is a change that was merged yesterday and hasn't been released yet. See here:
https://github.com/storybooks/storybook/pull/1134
So while your change is technically correct, it won't be as soon as we do the next release. I'm going to release in the next hour so that the live docs are consistent with the latest released version. I apologize to you for the confusion and hassle here. 😢
@ndelangen @tmeasday we need to figure out a better solution here. See: https://github.com/storybooks/storybook/issues/1231

@VonIobro closing this per my description above. thanks for being proactive on the fix and sorry for the trouble. Please let me know if I got something wrong.


Sensor.measure(???)

For linear elasticity, the displacements u and the residual R seem to be sufficient for postprocessing. Thus, we currently have sensors.measure(u, R). For nonlinear problems, we may also want to measure (aka post-process) internal variables. And for multiphysics problems, we measure other fields.
One idea was to pass the whole problem as an argument. What could be the disadvantages? If there are none, "just" implement it :)

So far I have not found a better solution for this either, how ever I have some additional thoughts on the whole sensor concept, therefore I opened issue #24.
But my answer to the question, what to pass the sensor, I would agree the pass the whole problem.
Still, there are points to be discussed: The required fields will need to be standardized, eg. 'problem.u', 'problem.T' etc... then, if the field is not continuous, quadrature point values, would be required. The sensor then restricted to a specific field? Again the location of the function field on which to project to quadrature points, will need to have a standardized name like 'problem.visu_space'
I think this overlaps with issue #21


Autoupdater

User wants an Autoupdater because they don't want to check the Github for a new build.
I'm personally opposed to this because I think this could become a hassle:

I distribute a lot of builds to users directly that would not be tracked and could (if designed poorly) forcibly upgrade an installation back to mainline when not intended

Same concern for CI/CD artifacts

We don't actually properly automatically store the version in the application because doing that during build in C# is a PITA last time I checked

It's doable but might require scripting that would have to work across OSs and IDEs
We'd have to introduce two builds, one tagged only with version and one with commit as semver build info (I don't want to redundantly include the commit hash into releases)

But personal issues with it aside, mostly reasonable user request is my demand, so here are subtasks (which might be worth splitting into their own issues):

[x] Investigate baking the version into builds automatically in a OS+IDE agnostic way
[ ] Implement comparing if a newer version is available from Github
[ ] Implement automagically upgrading to a newer version
[ ] Expose either update notification or upgrade choice in appsettings.json

Got the first step to the puzzle from a Stack Overflow answer:
<Project Sdk="Microsoft.NET.Sdk">
    <Target Name="SetSourceRevisionId" BeforeTargets="InitializeSourceControlInformation">
        <Exec
                Command="git describe --long --always --exclude=* --abbrev=8"
                ConsoleToMSBuild="True"
                IgnoreExitCode="False"
        >
            <Output PropertyName="SourceRevisionId" TaskParameter="ConsoleOutput"/>
        </Exec>
    </Target>

This appends to the Product Version as build metadata, exactly how I would have wanted it:
VS_VERSION_INFO.StringFileInfo.000004b0.ProductVersion:6.9.0+9ee9e6b2
This unfortunately isn't exposed very well in Linux-land but doing a grep through the app strings shows:
❯ strings AdGoBye | grep 6.9.0+9ee9e6b2
6.9.0+9ee9e6b2

It's still in there, which means this is viable for embedding commit hash at the cost of a build dependency on git.
I suppose at that point we can use Assembly.GetExecutingAssembly to get and parse our own version and handle updating based on that.

WTF? Okay, so with .NET 8, "Source Link" was enabled so we already get the commit hash baked into builds implicitly (see https://github.com/dotnet/sdk/issues/34568). Reminder to read patchnotes very carefully...
Anyway, that saves us the SetSourceRevisionId configuration.
My bigger problem is that I'm not sure how to actually fetch our own ProductVersion.
Overall there's two solutions proposed for reading our own ProductVersion:

WinForms exposes ProductVersion directly. We are not a WinForms app.
Parsing the version from FileVersionInfo.GetVersionInfo, by...

Reflecting on the executing or entry Assembly location

This works in theory, however when compiling to a single file, .Location is empty.
I don't particularly like the idea of needing to ship a big folder of DLLs to users, especially since AGB expects you to do file operations in the same folder the app is in

Finding ourselves per AppContext.BaseDirectory

This is offered as direct replacement for the Assembly calls (https://github.com/dotnet/core/issues/5335), BaseDirectory returns us the directory where our app is.
We have to append our executable name though since this only returns us our executing folder
However this appears to fail since GetVersionInfo's result is fully nulled / defaults

That means we can't actually access our own version, which blocks this issue from being implemented. Is this just an unsupported usecase?
We'd have to script our own solution for including the version, which will make this a lot uglier than I'd like it to be.

@regalialong take a look at this: https://stackoverflow.com/a/77449289/12657868

@regalialong take a look at this: stackoverflow.com/a/77449289/12657868
System.Deployment.Application.ApplicationDeployment namespace belongs to ClickOnce, so we can't use this here unfortunately.

Got some help on this, the FileVersionInfo approach was wack, working on a feature branch for this.

Probably not cleanly doable, #55 implements a updater checker as compromise.


Feature/add latest block metric 2

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.

What
[TODO: Short statement about what is changing.]
Why
[TODO: Why this change is being made. Include any context required to understand the why.]
Known limitations
[TODO or N/A]

Reference Server Preview is available here:https://anchor-ref-pr985.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr985.previews.kube001.services.stellar-ops.com/


Ubuntu Suru icons

Hi,
Can you add Ubuntu Suru icons to the collection, please? These icons are used in the Ubuntu for phones at the moment. Link to the source files: http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-themes/trunk/files/head:/suru-icons/
Many thanks

Hi @mivoligo
They look really nice, but sadly they are not clean (look at the difference with the google material design code icons), they need to be cleaned up in order to be easily converted to symbols and this will take a lot of time.
I can not afford enough time to do that right now but if anyone is willing to do this I will be happy to help, step by step, on how to create the first one.
In any case, I will add this enhancement to our icon sets list.
Thanks for the reference, the icons are awesome.

Thanks for quick answer. Let me know how to "clean them up". I can give it a shot in my spare time.

I have written an article that you might find useful to start.
There is an example on the root folder called a "template.svg" where you can see how it should look like.
If you make the first one, I can test it and check if its correct.

OK, so the most important thing is that one icon should be made of paths, right? Also I found this video: https://www.youtube.com/watch?v=jdaGB0zCdHw Is it fine to put all together like in the video, when the icons are cleaned?

Nice video.
Let's do some experiment, create the icons from the UI and send a PR with the result and lets check how it looks. I'm not sure that it will be as useful as if we make it manually but might be enough for the beggining. If necesary, I'll clean the inkscape and sodipodi extra info.
The idea behind the cleaning is that the same icons, just its code copied and pasted, could be useful for front-end development as well.

I'll try to do that in the evening and let you know.

nice :+1:

I've made a test set with 10 icons. I didn't change anything in them, just did like it was shown on that video. Take a look at PR. I'm afraid it does not look good.
BTW I'm rather new in using github so please excuse if I messed something up ;)

Hi @mivoligo I just saw the code and looks a little bit complicated, but I need to test it more to be sure. I made a test symbol library with my own created symbols from the UI (see the update!) and something can be done but not much. The SVG code its not perfect, but enough for designers.
I'll be out until sunday but I will test it as soon as possible when I come back.
In any case, if it works correctly, those icons can be published so we can start to use them and I will clean them out later on. :smiley:
Thanks!

Reference for this issue: https://github.com/Xaviju/inkscape-open-symbols/pull/3


remove deprecated call to step.addBuildOption

Thanks, this looks great! I'm ready to merge it once it's no longer marked as a draft.

Why expose this? Seems like just an extra unnecessary step for users.

Hi I am still stuck on some errors. This change was done because I was not able to use any functions with usingnamespace (maybe related to the namespace change in 0.9?). I agree its a negative change 😄
The final blocking issue is that @import("build_options") cause unable to find error. Not sure what is wrong at this point. @SpexGuy do you have any idea?

Maybe a Zig bug? Looking at 0.9 release notes it seems like usage is valid here, or maybe they have change the API in master

The issue was I tried to import tracy.zig by using addPackage instead of moving the file causing the exe step to not share the configuration with the tracy.zig file/package.

Ok should be green to go. Not sure your preferred git history here since currently only the latest commit will compile so it might be an idea to simply squash all commits into one and use message "update to latest zig" or something :)

@SpexGuy Give me a heads up if there are any issues with the current PR I'll try to get to them ASAP

Thanks, looks good!


Properly serialize transitions

if a CrossSection has a cross_sections attribute (it is a transition), we should serialize it as a list of cross sections. skipping this attribute causes an improper extruded component to be reused from cache

Thank you Troy!


the server has asked for the client to provide credentials error

I'm getting the follow error (and all that is in the logs) when the pod starts. I assume this is when kube-lego tries to talk to my kube-api
2016-10-18T00:28:29.478223138Z time="2016-10-18T00:28:29Z" level=info msg="kube-lego 0.1.2-03c268d7 starting" context=kubelego
2016-10-18T00:28:29.513084276Z time="2016-10-18T00:28:29Z" level=fatal msg="the server has asked for the client to provide credentials" context=kubelego

Interesting issue, can you provide the cli flags you run your API server with?
It looks like you requiring cert auth against Kubernetes API

"the server has asked for the client to provide credentials"

this can be triggered by an invalid service account. Please check the certificate is not expired.

I use certs for all communication with the API server.
I can't see a way to use certs, or use a kubeconfig file, with kube-lego if it's possible?
          image: quay.io/coreos/hyperkube:v1.4.1_coreos.0
          command:
          - /hyperkube
          - apiserver
          - --bind-address=<IP_ADDRESS>
          - --etcd-servers=https://<IP_ADDRESS>:2379
          - --allow-privileged=true
          - --service-cluster-ip-range=<IP_ADDRESS>/24
          - --secure-port=443
          - --advertise-address={{.node.ip_v4.private}}
          - --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,ResourceQuota
          - --tls-cert-file=/etc/kubernetes/ssl/apiserver.pem
          - --tls-private-key-file=/etc/kubernetes/ssl/apiserver-key.pem
          - --client-ca-file=/etc/kubernetes/ssl/ca.pem
          - --service-account-key-file=/etc/kubernetes/ssl/apiserver-key.pem
          - --runtime-config=extensions/v1beta1=true,extensions/v1beta1/networkpolicies=true
          - --etcd-cafile=/etc/ssl/etcd/ca.pem
          - --etcd-certfile=/etc/ssl/etcd/etcd.pem
          - --etcd-keyfile=/etc/ssl/etcd/etcd-key.pem

Have you tried to mount a kubeconfig file using a secret to /root/.kube/config?
It think this is preventing it from working: https://github.com/jetstack/kube-lego/blob/master/pkg/kubelego/kube.go#L23
But it would be good to make that work..

Mounting a kubeconfig file to /root/.kube/config causes the same error.

i have the save error. how to fix.
kube-error.txt


fix bound error when in diff value of table name case config

when lower_case_table_names = 0, reference of table name should case sensitive
when lower_case_table_names = 1 and 2 cte name should case insensitive

more details, please read doris doc: https://doris.apache.org/docs/advanced/variables#supported-variables
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


sidebar: Fixes to org cycling

What's this PR do?
Fixes #691.
Two changes made-

Ctrl+Shift+Tab wasn't working for first org. It should change the active realm to last realm.
Disabled org cycling with ctrl+tab on non-server pages.

You have tested this PR on:

[ ] Windows
[x] Linux/Ubuntu
[ ] macOS

Thanks, everyone 🚀


New Win11 22621 Winget Installation Issues

Describe the bug
When trying to use a the toolbox on a brand new laptop (Dell Inspiron 15) I can only use tweaks, configs, and updates. When trying to use the toolbox to install programs, it attempts to install them as proceeds to save "installs finished" but the programs do not install. When trying to use the installer, it gives the error message "Install process is currently running."
To Reproduce
Steps to reproduce the behavior:

Go to 'Install'
Click on 'Brave' (Using Brave as an example as it does not matter what program.)
Click 'Install Selection'
See error: Programs do not install/appear anywhere even though the toolbox says they do

Expected behavior
Selected programs (Brave and Jellyfin Server)  are to be installed and appear.
Additional context
Brand new Dell Inspiron 15 Laptop that came pre-installed with McAfee. I setup a local account and used RevoUninstaller to uninstall McAfee and it's bloatware. I also ran the Tron Script to see if that would fix anything.
Windows 11 version: 22H2, 22621.2283

+1 Also encountering this behavior on fresh install of Windows 11 on my Desktop.
Version : 22H2 22621.2361

This seems as a winget version issue - I updated the winget version with the one from MS Store and after that the checked programs install fine.

Hell yeah that did the trick and now works :) thanks

Hell yeah that did the trick and now works :) thanks

Glad that it helped, another way could be to use directly the script that should install winget
"irm https://raw.githubusercontent.com/ChrisTitusTech/winutil/main/winget.ps1 | iex"
I suppose that the fix might be just adding a check for a winget version in Test-WinUtilPackageManager and not just that it exists on the system.
For some reason the latest win11 install got me winget 1.2.xxx version pre-installed (the version from "winget -v") but the latest version today is v1.6.2771.

Can confirm as the OP, WinGet needs to be updated to resolve this issue.


BAU: point cookies message at Verify

The current cookies banner points at GOV.UK’s cookies page, but should point at Verify’s. This also enables Welsh translation.

👍


Potentially vulnerable dependency marked-0.8.2.js

Potentially vulnerable dependency marked-0.8.2.js
Please see https://github.com/markedjs/marked/commit/bd4f8c464befad2b304d51e33e89e567326e62e0
marked before 1.1.1 is vulnerable to Regular Expression Denial of Service (REDoS). rules.js have multiple unused capture groups which can lead to a Denial of Service
jsdoc - marked dependency should be upgraded to 1.1.1 or above version.

marked seems to not be used by default anymore: https://github.com/jsdoc/jsdoc/issues/1243

For JSDoc 3.6.0, we'll add markdown-it and use it by default, but marked will still be available. For JSDoc 3.7.0, marked will be removed.

So you might be able to mute your vulnerability notifications for that.

Removal of marked has been proposed back in 2017, see https://github.com/jsdoc/jsdoc/issues/1413, so I'm not counting on this work landing any time soon.
I was wondering if a simpler approach would be to upgrade the existing marked library version into 1.1.1,  given that marked version 1.0.0 is "non-breaking for most users".
I tried looking into making this fix, but gave up after running into the good ol' node-gyp errors, which I'm currently not willing to work through.


Nvidia GPU not showing in panel

I can't get Nvidia GPU to display, even with pynvml installed.
I've verified that pynvml is working by running py3smi in my terminal and the GPU printout is working. Conky was also compiled with Nvidia support (conky-lua-nv 1.19.4-1 installed from AUR).

conky 1.19.4_pre compiled 2023-10-11 for Linux x86_64

Compiled in features:

System config file: /etc/conky/conky.conf
Package library path: /usr/lib/conky

 General:
  * math
  * hddtemp
  * portmon
  * IPv6
  * Curl
  * RSS
  * wireless
  * support for IBM/Lenovo notebooks
  * nvidia
  * builtin default configuration
  * old configuration syntax
  * Imlib2
  * OSS mixer support
  * apcupsd
  * iostats
  * ncurses
  * Internationalization support
  * PulseAudio

 Lua bindings:
  * Cairo
  * Imlib2
  * RSVG
 X11:
  * Xdamage extension
  * Xinerama extension (virtual display)
  * Xshape extension (click through)
  * XDBE (double buffer extension)
  * Xft
  * ARGB visual
  * Own window
  * Mouse evenets

 Music detection:
  * CMUS
  * MPD
  * MOC

 Default values:
  * Netdevice: eno1
  * Local configfile: $HOME/.conkyrc
  * Localedir: /usr/share/locale
  * Maximum netdevices: 256
  * Maximum text size: 16384
  * Size text buffer: 256

Add ”pip install pynvml” directly. Take care of your python environment.

Same issue, pynvml is installed.

I have the same issue as well.
Launching conky using the script shows no error whatsoever.
However when I try to launch conky from the terminal it does show an error
conky: llua_do_call: function conky_nvidia execution failed: ~/.config/conky/lib/components/gpu.lua:36: attempt to compare number with nil

I'm using AwesomeWM on arch 6.8.2 and have already installed pynvml system-wide as well as having made a venv just to make sure everything works.
I would've helped fix this issue myself and made a pull request but I know nothing lua related. maybe I should learn that soon.
anyway thank you for your amazing work and I hope you could maybe guide us through working around this issue.

@OldLorekeeper What do you have while running:
/path/to/lcc/lib/components/gpu_nvml

@jxai Personally when I run gpu_nvml I get:
{
{
model_name='NVIDIA GeForce GTX 970',
mem_used=570818560,
mem_total=4294967296,
mem_free=3724148736,
gpu_util=3,
mem_util=3,
fan_speed=0,
gpu_temp=49,
Traceback (most recent call last):
  File "/home/bonswouar/.config/conky/lean-conky-config/./lib/components/gpu_nvml", line 79, in <module>
    qp(
  File "/home/bonswouar/.config/conky/lean-conky-config/./lib/components/gpu_nvml", line 64, in qp
    return query_and_print(name, f, handle, *args, **kw)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/bonswouar/.config/conky/lean-conky-config/./lib/components/gpu_nvml", line 46, in query_and_print
    val = query(f, *args, **kw)
          ^^^^^^^^^^^^^^^^^^^^^
  File "/home/bonswouar/.config/conky/lean-conky-config/./lib/components/gpu_nvml", line 40, in query
    retval = f(*args, **kw)
             ^^^^^^^^^^^^^^
  File "/home/bonswouar/.local/lib/python3.11/site-packages/pynvml/nvml.py", line 2334, in nvmlDeviceGetTemperatureThreshold
    _nvmlCheckReturn(ret)
  File "/home/bonswouar/.local/lib/python3.11/site-packages/pynvml/nvml.py", line 833, in _nvmlCheckReturn
    raise NVMLError(ret)
pynvml.nvml.NVMLError_NotSupported: Not Supported

It seems querying  gpu_temp_thres nvmlDeviceGetTemperatureThreshold doesn't work for some reason.
As a workaround I've catch the exception,  here is the new output:
{
{
model_name='NVIDIA GeForce GTX 970',
mem_used=592904192,
mem_total=4294967296,
mem_free=3702063104,
gpu_util=2,
mem_util=3,
fan_speed=0,
gpu_temp=49,
0
power_usage=54.74,
power_limit=200.0,
processes={
{
pid=1199,
name='Xorg',
type='g',
gpu_util=2,
mem_util=0,
gpu_mem=185352192,
gpu_instance=4294967295,
},
{
pid=6089,
name='librewolf',
type='g',
gpu_util=1,
mem_util=0,
gpu_mem=255004672,
gpu_instance=4294967295,
},
{
pid=2415,
name='cinnamon',
type='g',
gpu_util=1,
mem_util=0,
gpu_mem=47505408,
gpu_instance=4294967295,
},
}
},
}

But I still see no GPU in LCC.

@bonswouar Should be fixed, no need to manually specify the fallback value now. Please give it a try.


ClaimsTransformationContext is not recognised in ASP Core 2.0.0

The following code is not recognized in asp mvc core 2.0.0
 app.UseClaimsTransformation
both UseClaimsTransformation and ClaimsTransformationContext  is  not recognized
using Microsoft.AspNetCore.Authentication;
public static Task<ClaimsPrincipal> AddClaims(ClaimsTransformationContext context)
{
    ....
}

What I'm doing wrong?!

In 2.0.0 it isn't middleware anymore. Reason is we are now able to use dependency injection.
To use ClaimsTransformation, register it in the service collection:
services.AddSingleton<IClaimsTransformation, ClaimsTransformer>();

And have a transformer class:
public class ClaimsTransformer : IClaimsTransformation
{
    public Task<ClaimsPrincipal> TransformAsync(ClaimsPrincipal principal)
    {
    }
}

ah thanks


Add support for Spark Connect DataFrames

This patch allows to use the assert_pyspark_df_equal when using Spark Connect.
https://spark.apache.org/docs/latest/spark-connect-overview.html
To achieve that we have to allow the pyspark.sql.connect.dataframe.DataFrame type to be allowed to be a valid input type.
The patch adds a new unit tests and updates the test dependencies as well. To avoid issues with older pyspark installations, I'm adding an import guard.

@debugger24 It would be great if you can take a look!


Jake, Kevin, Rony paradixm project

Ummmm…not sure what happened here. According to this pull request, nearly every single file has changed. Did you guys do some kind of global search and replace or something? I can’t really work with this cleanly. We need to figure out what’s going on here.


Prefix custom properties with bs-

Something @tmorehouse mentioned in https://github.com/twbs/bootstrap/pull/30466#issuecomment-612177063, we could prefix our custom properties with bs-.
Thoughts @twbs/css-review?

personally, i'd be in favour. yes it makes them more verbose, but then again...not by a monstrously huge amount

I'd be in favor to, since Bootstrap can live beside other libraries (eg. Booster v4 includes jQuery TableSorter, speaking of table styles leaking) or custom code.
However, could this be some kind of no-conflict mode, a la jQuery, to allow devs to remove/add prefixes ?

We could run all our variables through a function like this:
https://codepen.io/MartijnCuppens/pen/dyYPQVp?editors=0100

I'm still against prefixing things, regardless of the tooling or language. We haven't done it in Sass, Less, or our JS for the last 8.5 years. Makes me super hesitant to add it now.
Thinking about it more, the syntax of custom properties lends itself quite nicely to a find and replace, I think. Take this example:
:root {
  --variable: value;
  --variable2: value2;
}

Finding ··-- in this file and replacing it with ··--b- isn't difficult or time consuming. (Note that the dots here indicate spaces—GitHub doesn't render spaces for some reason.

Custom JS event names are postfixed (or is it middlefixed) (i.e. shown.bs.dropdown) :wink:

Doh, I knew that! Updated comment :).

We could run all our variables through a function like this:
https://codepen.io/MartijnCuppens/pen/dyYPQVp?editors=0100

From an user perspective I'd appreciate that.

Finding ··-- in this file and replacing it with ··--b- isn't difficult or time consuming. (Note that the dots here indicate spaces—GitHub doesn't render spaces for some reason.

Lot's of people (including me) are using Bootstrap via npm, find and replace is not really an option there. It could be possible with a PostCSS plugin, but afaik, there is non available (yet). Also, this PostCSS plugin should only run for the Bootstrap CSS so if you aggregate Bootstrap with custom CSS, you got a problem.

We haven't done it in Sass or Less or our JS for the last 8.5 years

This is different. Sass variables don't leak into the CSS, so the only conflicts we can have are in source Sass. For custom properties, we got to make sure those custom properties do not conflict with any custom CSS.

Ah, yeah, I was on a high horse about it earlier. I do see the difference here for what gets served to end users and that these things "leak" into other environments where it could clash with other CSS.


Ignore MgmtMessageHdr if ProcessManager is not running

Fix #4736

This should go to v9.0.0 because this fixes a crash.

Cherry-picked to v9.0.x branch.

This now has a merge conflict if I try to cherry-pick to 8.0.x, can you please make a new PR (and link to this one) for the 8.1.x branch?

There was a separate PR #6534 for 8.1.x and this change when into the 8.1.0 release.


AuditLog: Refactor to use AuditCategory enum

Changes:

Pull out AuditCategory from AuditMessage
Use EnumSet for all categories instead of List of Strings

No new functionality added.

AuditCategory is a type of audit log and AuditMessage represents the actual message content that is logged. It does not make sense for category to be a subclass of message as we might want to do different operations based on category. Ideally would want something like this class { category, content } to actually represent what the an audit log means.

My understanding is that AuditCategory specifies what categories of AuditMessage should be enabled/disabled.

AuditMessage stores only the content of message.
Next PR is to move AuditMessage into a builder pattern what can build a message for a given category.

I hope commit 31e72eafc6ba66b08d2e31cc53fd20ae6b010617 solves your concern of adding new method getConfigList . Reverted back to using what AbstractAuditLog originally had for parsing it.


Cannot set environment variable when using CmdLine task

Right now I use the CmdLine task to run "mono" as tool with "nunit-console.exe" as parameter so I can run my mobile tests without developing a custom task.
Now I would like to improve this a little bit, and set 2 environment variable that would contain the device model / OS on which I want to run my tests (and later fill these variable dynamically using our test plan in MTM).
How can I set these 2 env vars since CmdLine does not seem to recognize the "VAR=VALUE tool_name" in the tool field ?

Variables on the definition are propagated to tools as environment variables.

and you can set variables dynamically. see the setvariable command: https://github.com/Microsoft/vsts-tasks/blob/master/docs/authoring/commands.md
other option is to use a shell script.

@ericsciple  My point was that you cannot reproduce this :
SOME_VAR=`some_binary_result` command_to_exec


Abide: equalTo not working as expected in some edge cases

I've found a case when the equalTo validator doesn't work as expected.

Go to http://codepen.io/ruben-santacruz/pen/qvlLf where I've prepared a little example form.
Enter abc in the Enter new password field.
Enter abcd in the Confirm password field.
Go back to the Enter new password field and add a d so it is abcd now.
Now the two fields are equal, but the Confirm password field still shows an error. To remove it you have to force the check again, bringing the focus to the Confirm password field and leaving it or clicking Submit.

I know it is a little weird case but I think it should be fixed. What do you think?

In Foundation 5.5 this issue still persists, but note that if you tab to the second password field, and then tab away from it, the error goes away.
I think it's because Abide is only checking to see if the fields match when checking the second password field, because it's the one with the data-equalto attribute. So the validation doesn't go two ways, basically.
So given the following code:
<input type="text" required pattern="alpha_numeric" id="password">
<input type="text" required pattern="alpha_numeric" id="password-confirm" data-equalto="password">

Right now a validator is added to #password-confirm to check for equality. But another validator should be added to #password to check in the other direction.

We added this to our "known issues" section in our planning board for the next version. A PR would be valuable to the community, otherwise It will be addressed then. You can see and vote on the proposed updates here: https://trello.com/b/QBPKlQqf/foundation-sites


Issue while sharing using shareviawhatsapptoreceiver

This is a free plugin for which I'm no longer able to offer free support.
If you want me to look at your issue with priority (or at all) you may want to consider giving my PayPal account a bit of love. Details are in the readme.
Thank you,
Eddy

while sharing using shareviawhatsapptoreceiver on ios it is not opening particular person/number chat and showing just list of persons and when i find a issue it is showing contact number as null when try to open whatsapp. may be this can be reason that it is not going to particular chat


chore: sync the image cache feature

Then I think we should fix it, or do you wanna fix them in another PR?


Fix deprecation

Detected deprecations in use:
 - Configuration file `.php_cs` is deprecated, rename to `.php-cs-fixer.php`.

Thanks @jeffwidman


attempt to add back 2.6/3.2/3.3 CI per another repo

There's probably a way to run the CI on my own fork, but I'll just give it a try via a PR here. Can never have too many PRs :P

Partial success - 2.6 passed but 3.2/3.3 didn't (environment issues)
For reference, here's where I got the changes from:
https://github.com/noahmorrison/chevron/pull/62
I'm keeping this PR for informatonal purposes only - feel free to close it once you decide whether to add 2.6 or not.

That is nifty! I would be more than happy to run the tests again on Python 2.6, 3.2 and 3.3.
For reference, even back then when Travis CI still supported Python 3.2 with the default image, I had to pin older versions of pytest and virtualenv, see d1e4709. Maybe that does the trick?
Anyway, even if we can't make it work on Python 3.2 and 3.3, I would still accept a merge request that at least works for Python 2.6.

Okay, I'll look into it a bit later.

There we go: a096f0f


WIP: New implementation of PublisherInputStream that improves performance and fixes race conditions

New implementation of PublisherInputStream, now renamed to SubscriberInputStream as it really implements a subscriber not a publisher. This new implementation fixes a couple of important problems:

It implements the ability to read into byte arrays, not just one byte at a time for better performance and,
It changes the implementation to avoid a race condition when accessing the data chunks held in CompletableFuture's. The race condition resulted in certain tests to hang if a thread raced and updated the value of the old processed variable.

There is also a new internal document docs-internal/subscriberinputstream.md that describes the new implementation. Credit to Oleksandr Otenko.
Signed-off-by: Santiago Pericasgeertsen<EMAIL_ADDRESS>

How about to rename it to something completely different as it is not a publisher nor subscriber.
public class FlowInputStream extends InputStream{
...
 private class DataChunkSubscriber implements Flow.Subscriber<DataChunk>{
     public void on...
     public void on...
     public void on...
     public void on...
     ...
    }
}

To avoid users of the api to accidentally violate rule §1.10 like this:
SubscriberInputStream subscriber = new SubscriberInputStream(publisher);
publisher.subscribe(subscriber);

I like the idea of the private class. I'll explore that.


Add instructions on running llava-v1.6-mistral-7b

After many hours of debugging, I finally got llava-v1.6-mistral-7b to work fully on SGLang inference backend.
This PR adds the relevant instructions to README.md, which references a PR I made on Hugging Face containing all the patches needed to make loading work.
Closes https://github.com/haotian-liu/LLaVA/issues/1114
Closes https://github.com/haotian-liu/LLaVA/issues/1112
Closes https://github.com/haotian-liu/LLaVA/issues/1179
Also closes (from SGLang repo: https://github.com/sgl-project/sglang/issues/128
Summary of patches:

create added_tokens.json and put:

{
  "<image>": 32000,
  "<pad>": 32001
}

this was from https://huggingface.co/SurfaceData/llava-v1.6-vicuna-7b-processor/blob/main/added_tokens.json which is linked by https://github.com/sgl-project/sglang/issues/127#issuecomment-1920321274

in config.json, change LlavaMistralForCausalLM to LlavaLlamaForCausalLM,   "model_type": "llava_mistral", to   "model_type": "llava"
this was from https://github.com/sgl-project/sglang/issues/128#issuecomment-1920246410

change generation _onfig.json to add a line before the transformer_version:
"pad_token_id": 32001,

Add preprocessor_config.json from https://huggingface.co/SurfaceData/llava-v1.6-vicuna-7b-processor/blob/main/preprocessor_config.json

{
	"crop_size": {
	  "height": 336,
	  "width": 336
	},
	"do_center_crop": true,
	"do_convert_rgb": true,
	"do_normalize": true,
	"do_rescale": true,
	"do_resize": true,
	"image_mean": [
	  0.48145466,
	  0.4578275,
	  0.40821073
	],
	"image_processor_type": "CLIPImageProcessor",
	"image_std": [
	  0.26862954,
	  0.26130258,
	  0.27577711
	],
	"processor_class": "LlavaProcessor",
	"resample": 3,
	"rescale_factor": 0.00392156862745098,
	"size": {
	  "shortest_edge": 336
	}
  }

in special_token_map.json add

  "pad_token": {
    "content": "<pad>",
    "lstrip": false,
    "normalized": false,
    "rstrip": false,
    "single_word": false
  },

this was from https://huggingface.co/SurfaceData/llava-v1.6-vicuna-7b-processor/blob/main/special_tokens_map.json

tokenizer_config.json change to https://huggingface.co/SurfaceData/llava-v1.6-vicuna-7b-processor/blob/main/tokenizer_config.json
Diffs:

    "32000": {
      "content": "<image>",
      "lstrip": false,
      "normalized": false,
      "rstrip": false,
      "single_word": false,
      "special": true
    },
    "32001": {
      "content": "<pad>",
      "lstrip": false,
      "normalized": false,
      "rstrip": false,
      "single_word": false,
      "special": true
    }
  },

and
  "legacy": false,
  "model_max_length": 4096,
  "pad_token": "<pad>",
  "padding_side": "right",
  "processor_class": "LlavaProcessor",

But need to keep the "chat_template" row from original one (vicuna one dont have)

tokenizer.json use the original one BUT in added_tokens, append:

    {
      "id": 32000,
      "content": "<image>",
      "single_word": false,
      "lstrip": false,
      "rstrip": false,
      "normalized": false,
      "special": true
    },
    {
      "id": 32001,
      "content": "<pad>",
      "single_word": false,
      "lstrip": false,
      "rstrip": false,
      "normalized": false,
      "special": true
    }

FWIW I've pushed what I think are these patches here

Perhaps I'm doing something wrong, but these patches result in <pad> being in the response:
Prompt: [INST] <image>
What do you see in this picture? [/INST]
<s> The image shows a wooden chess set on a wooden table. There are three chess pieces visible: a rook, a knight, and a pawn. The rook and knight are standing upright, while the pawn is lying on its side. The pieces appear to be made of a dark wood, and the table has a light wood finish. The shadow of the chess pieces is<pad><pad><pad> the table,<pad><pad><pad><pad><pad><pad>, indicating that the light source is coming from the direction the shadow is cast. </s>

Yea pad seem to be extra as they use unk as pad, so i guess should delete the pad related entries and set pad token id in various files to 0 (unk)
Been running this and no issues so fa4

Yea pad seem to be extra as they use unk as pad, so i guess should delete the pad related entries and set pad token id in various files to 0 (unk)
Been running this and no issues so far

@RonanKMcGovern thanks for posting the patched version on huggingface! Quick question: did you update to include @aliencaocao 's recent pad solution?

Yeah pad is included but actually that is a bad idea and breaks generation.
Actually I’m not sure the patches are needed, rather, the loading script
from the evaluation file needs to be used to load the model. It’s messy.
There’s a vid I put on Trelis YouTube showing a bit on training. Probably
there are other better ways too.
On Sat 2 Mar 2024 at 22:35, Rylan Schaeffer @.***>
wrote:

@RonanKMcGovern https://github.com/RonanKMcGovern thanks for posting
the patched version on huggingface! Quick question: did you update to
include @aliencaocao https://github.com/aliencaocao 's recent pad
solution?
—
Reply to this email directly, view it on GitHub
https://github.com/haotian-liu/LLaVA/pull/1115#issuecomment-1974927753,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASVG6CSPUZ2Q2WJ6MXKR4W3YWJH2JAVCNFSM6AAAAABDCVGQ52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZUHEZDONZVGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@RonanKMcGovern can you link the video?

https://youtu.be/eIziN2QUt8U?si=RybNCreMN2ua7faP
On Sun 3 Mar 2024 at 06:38, Rylan Schaeffer @.***>
wrote:

@RonanKMcGovern https://github.com/RonanKMcGovern can you link the
video?
—
Reply to this email directly, view it on GitHub
https://github.com/haotian-liu/LLaVA/pull/1115#issuecomment-1975063451,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASVG6CRL7DW33JOXE66MNOTYWLAMXAVCNFSM6AAAAABDCVGQ52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGA3DGNBVGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

After many hours of debugging, I finally got llava-v1.6-mistral-7b to work fully on SGLang inference backend.
This PR adds the relevant instructions to README.md, which references a PR I made on Hugging Face containing all the patches needed to make loading work.
Closes #1114 Closes #1112 Closes #1179 Also closes (from SGLang repo: sgl-project/sglang#128
Summary of patches:

create added_tokens.json and put:

{
  "<image>": 32000,
  "<pad>": 32001
}

this was from https://huggingface.co/SurfaceData/llava-v1.6-vicuna-7b-processor/blob/main/added_tokens.json which is linked by sgl-project/sglang#127 (comment)

in config.json, change LlavaMistralForCausalLM to LlavaLlamaForCausalLM,   "model_type": "llava_mistral", to   "model_type": "llava"
this was from [Bug] liuhaotian/llava-v1.6-mistral-7b doesn't load sgl-project/sglang#128 (comment)
change generation _onfig.json to add a line before the transformer_version:
"pad_token_id": 32001,
Add preprocessor_config.json from https://huggingface.co/SurfaceData/llava-v1.6-vicuna-7b-processor/blob/main/preprocessor_config.json

{
	"crop_size": {
	  "height": 336,
	  "width": 336
	},
	"do_center_crop": true,
	"do_convert_rgb": true,
	"do_normalize": true,
	"do_rescale": true,
	"do_resize": true,
	"image_mean": [
	  0.48145466,
	  0.4578275,
	  0.40821073
	],
	"image_processor_type": "CLIPImageProcessor",
	"image_std": [
	  0.26862954,
	  0.26130258,
	  0.27577711
	],
	"processor_class": "LlavaProcessor",
	"resample": 3,
	"rescale_factor": 0.00392156862745098,
	"size": {
	  "shortest_edge": 336
	}
  }

in special_token_map.json add

  "pad_token": {
    "content": "<pad>",
    "lstrip": false,
    "normalized": false,
    "rstrip": false,
    "single_word": false
  },

this was from https://huggingface.co/SurfaceData/llava-v1.6-vicuna-7b-processor/blob/main/special_tokens_map.json

tokenizer_config.json change to https://huggingface.co/SurfaceData/llava-v1.6-vicuna-7b-processor/blob/main/tokenizer_config.json
Diffs:

    "32000": {
      "content": "<image>",
      "lstrip": false,
      "normalized": false,
      "rstrip": false,
      "single_word": false,
      "special": true
    },
    "32001": {
      "content": "<pad>",
      "lstrip": false,
      "normalized": false,
      "rstrip": false,
      "single_word": false,
      "special": true
    }
  },

and
  "legacy": false,
  "model_max_length": 4096,
  "pad_token": "<pad>",
  "padding_side": "right",
  "processor_class": "LlavaProcessor",

But need to keep the "chat_template" row from original one (vicuna one dont have)

tokenizer.json use the original one BUT in added_tokens, append:

    {
      "id": 32000,
      "content": "<image>",
      "single_word": false,
      "lstrip": false,
      "rstrip": false,
      "normalized": false,
      "special": true
    },
    {
      "id": 32001,
      "content": "<pad>",
      "single_word": false,
      "lstrip": false,
      "rstrip": false,
      "normalized": false,
      "special": true
    }

Thanks, the same applies to solving ”Cannot launch SGLang demo on llava-v1.5-13b“

isn't LLaVa 1.6 using 336 to patchify? https://huggingface.co/liuhaotian/llava-v1.6-34b/blob/main/config.json#L16-L37:~:text=1008%2C,336
LLaVA-1.5-HD used 224


perf: always copy small messages

Given the overhead of the gc thread, we should probably trigger copy=True behavior for small messages.
We'll need to do some profiling to pick a sensible but conservative default. My guess is it will be somewhere in the 4k-16k range. This could even be a socket-level option.
Senders can do this at the application level, but receivers cannot, because they don't know the size of the message before receiving it. pyzmq can make this decision based on zmq_msg_size.
Proposal:

add Socket.always_copy_threshold attribute
don't copy if a frame is smaller than
still need to wrap it in a Frame object for API compatibility, but no need to hook up the gc callback

copy_threshold is in 17.0


error: the server doesn't have a resource type "svc"

Steps taken

Created an role as per https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html#eks-prereqs
Created a K8S cluster as per https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html#eks-create-cluster
Created an IAM user with programmatic access with the following permissions

AmazonEKSClusterPolicy
AmazonEKSWorkerNodePolicy
AmazonEKSServicePolicy
AmazonEKS_CNI_Policy
AmazonEC2ReadOnlyAccess

Note: the original IAM user we had in .aws/credentials used AmazonEC2ReadOnlyAccess.
I added that in order not to break existing scripts.

Upgraded AWS CLI

% aws --version
aws-cli/1.16.30 Python/2.7.14 Linux/4.14.72-68.55.amzn1.x86_64 botocore/1.12.20

Installed kubectl as per https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html#eks-configure-kubectl

% kubectl version --short --client
Client Version: v1.10.3

Installed aws-iam-authenticator

Generated kubeconfig

% aws sts get-caller-identity
XXXXXXXXX	arn:aws:iam::XXXXXXXXX:user/bastion	XXXXXXXXXXXXXXXXXXX

% aws eks update-kubeconfig --name test
Updated context arn:aws:eks:us-east-1:XXXXXXXXX:cluster/test in /home/ec2-user/.kube/config

% kubectl get svc
error: the server doesn't have a resource type "svc"

Debugging

Fetch token

% aws-iam-authenticator token -i wizenoze-test
{
   "kind":"ExecCredential",
   "apiVersion":"client.authentication.k8s.io/v1alpha1",
   "spec":{

   },
   "status":{
      "token":"k8s-aws-v1.XXX"
   }
}

Verify token

% aws-iam-authenticator verify -i test -t k8s-aws-v1.XXX

&{ARN:arn:aws:iam::XXXXXXXXX:user/bastion CanonicalARN:arn:aws:iam::XXXXXXXXX:user/bastion AccountID:XXXXXXXXX UserID:XXXXXXXXXXXXXXXXXXX SessionName:}

Could you please help me in finding out what's wrong?
Thanks,
László

I was experiencing this until I opened a new tab in Terminal

We are also seeing this exact problem.
We additionally assumed the role we created for our EKS cluster using
aws eks update-kubeconfig --name eksgism --role-arn arn:aws:iam::XXXXX:role/eksgism-role

We too can seemingly successfully use the aws-iam-authenticator
aws-iam-authenticator token -i eksgism -r arn:aws:iam::XXXXX:role/eksgism-role
{"kind":"ExecCredential","apiVersion":"client.authentication.k8s.io/v1alpha1","spec":{},"status":{"token":"k8s-aws-v1.XXXXX}

aws-iam-authenticator verify -i eksgism -t k8s-aws-v1.XXXXX
&{ARN:arn:aws:sts::XXXXX:assumed-role/eksgism-role/XXXXX CanonicalARN:arn:aws:iam::XXXXX:role/eksgism-role AccountID:XXXXX UserID:XXXXX SessionName:XXXXX}

...And opening a new tab did not work :(
Cheers,
Sam & @teddyking

@laszlocsontos Whichever user/role's credentials you were using when you created the EKS cluster are the credentials you should be using when you try kubectl get svc.  (In your case, user/bastion).  Was this the same user that you used to create the cluster?  The EKS service role has nothing to do with it.

@Samze it appears that your AWS credentials are not accessible to the authenticator binary.  What happens when you run aws sts get-caller-identity?

I am facing the exact same issue
aws sts get-caller-identity gives the following
{
"Account": "XXXXXXXXXXXX",
"UserId": "YYYYYYYYYYYYYYYYYYY:i-XXXXXXXXXXXXX",
"Arn": "arn:aws:sts::XXXXXXXXXXXX:assumed-role//i-"
}

Identical issue here.

I'm facing the exact same problem as well.  Interestingly enough, the token generation works but the verify fails:  aws-iam-authenticator verify -i test -t "k8s-aws-v1.aMGI3YjY0M2M0YjE1Njk5"
could not verify token: sts getCallerIdentity failed: error from AWS (expected 200, got 403)

+1

narup, yes, you might be on to something.  I create the cluster from the GUI using SSO credentials which would have used temporary access/secret keys.  All the kubectl work was done using my permanent access/secret key pair.  I will have to go back and validate this again using only the CLI with my access/secret.

Also seeing this. I created two clusters, one in the console and one from the CLI. The result is the same error. I can fetch and verify my token is my SAML user, which I used to create both clusters.

Might you guys be using Terraform at all? I know it's still just an API call for both. I'm seeing this when using Terraform that assumes a role, and regardless of if I assume that role or not, I can't access the control plane.

Negative, I'm not using Terraform for this only the Console and the CLI.

My problem was related to not having my IAM user keys set as default at ~/.aws/credentials, I was using the --profile flag to run AWS CLI commands as I normally do but it doesn't seems to work for this case

I'm having the exact same issue. Kubectl logs say
I1123 13:09:45.789218   28300 request.go:942] Response Body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}

EKS is a suicide mission by AWS. This Elastic Kube Shit is not working.

Created a role
Set my user as trusted entities.
Assigned a policy to my user so it can assume the role.
Created EKS Cluster
Installed latest aws*, kubectl
aws eks update-kubeconfig --name xxxxxxxx --role-arn arn:aws:iam::xxxxxxxxx:role/EKS-Manager
Response Body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}

All so tried using a readily available EKS-cli docker images, but same error.
 Is this the same user that created the cluster? I'm at re:Invent right now. Hoping to find some EKS folks to talk to about the user experience here.

@jaydipdave Who are you at the CLI when getting your token (i.e. aws sts get-caller-identity)? Is this the same user that created the cluster? I'm at re:Invent right now. Hoping to find some EKS folks to talk to about the user experience here.

Hi @mrichman ,
Thanks for you quick response. I am using a different user at AWS CLI. i.e. "tools".
But EKS-user has a policy to assume the role:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": "sts:AssumeRole",
            "Resource": "arn:aws:iam::xxxxxxxxxxxxx:role/*"
        }
    ]
}

And in the role, who created the EKS cluster, I set the Trusted Entities.
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Principal": {
        "Service": "eks.amazonaws.com"
      },
      "Action": "sts:AssumeRole"
    },
    {
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::xxxxxxxxxxx:user/tools"
      },
      "Action": "sts:AssumeRole"
    }
  ]
}

I am assuming the role using "-r arn:aws:iam::xxxxxxxxxxxxx:role/EKS-manager ".
Should this be sufficient?

This really should be sufficient, but I don't think it is, and I think it's the problem that we're running into. Using an assumed role hasn't worked for me at all when creating a cluster, I've tried this a bunch of different ways. The only way I can do it is by using a logged in user (which uses an assumed role through SAML auth) Maybe we're all doing something wrong, but I haven't been able to figure it out.
And a little off topic, adding other users/roles at creation is a huge oversight by AWS, if one is added at creation, I can't see why they woudn't have thought to give us the ability to add more.

I’m here at reinvent trying to get an audience with anyone on the EKS team who can help.

I think the nut of the problem has do to with the initial EKS cluster creation and then the following commands via kubectl.  My hypothesis is that the initial EKS cluster setup is done via the console and then the subsequent provisioning via the kubeclt on the cli breaks the aws-iam-authenticator model because the initial cluster creation stores data in the master node that is hidden.  I will attempt to prove this theory as soon as I get a moment.  At the Reinvent conference in Vegas.
Regards
Mark Cwetna
Slalom
From: Mark Richman<EMAIL_ADDRESS>Reply-To: kubernetes-sigs/aws-iam-authenticator<EMAIL_ADDRESS>Date: Tuesday, November 27, 2018 at 11:07 PM
To: kubernetes-sigs/aws-iam-authenticator<EMAIL_ADDRESS>Cc: Mark Cwetna<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [kubernetes-sigs/aws-iam-authenticator] error: the server doesn't have a resource type "svc" (#157)
I’m here at reinvent trying to get an audience with anyone on the EKS team who can help.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kubernetes-2Dsigs_aws-2Diam-2Dauthenticator_issues_157-23issuecomment-2D442331310&d=DwMFaQ&c=fa_WZs7nNMvOIDyLmzi2sMVHyyC4hN9WQl29lWJQ5Y4&r=bizeWICKQs8YNpGSnQCdAWt6454ZIJWOmCQaNqXvmH4&m=l1zjz-TjXuvbsQ5L_znEchS-Hvu1Avt3_q9pWEluPcA&s=RbaBT5AH7kY7BiYlIaOSkVV0VZzXQhsIAc56vnJ2pEY&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AE5bgnAYay3H7PLHaRuN6rhMd9VqRDP-5Fks5uzig6gaJpZM4XUt7I&d=DwMFaQ&c=fa_WZs7nNMvOIDyLmzi2sMVHyyC4hN9WQl29lWJQ5Y4&r=bizeWICKQs8YNpGSnQCdAWt6454ZIJWOmCQaNqXvmH4&m=l1zjz-TjXuvbsQ5L_znEchS-Hvu1Avt3_q9pWEluPcA&s=j-dzY-VHOfS6d6-7P6YdwNx_Ezk-_YaJm4bLOPX5pIw&e=.

Possible solution if you created the cluster in the UI
If you created the cluster in the UI, the AWS root user created the cluster. According to the docs, "When an Amazon EKS cluster is created, the IAM entity (user or role) that creates the cluster is added to the Kubernetes RBAC authorization table as the administrator (with system:master) permissions. Initially, only that IAM user can make calls to the Kubernetes API server using kubectl. "
You'll need to first login to the AWS CLI as the root user in order to update the permissions of the IAM user you want to have access to the cluster.

You'll need to get an  access key for the root user and put this info in .aws/credentials under the default user. You can do this using the command aws configure
Now kubectl get svc works, since you're logged in as the root user that initially created the cluster.

Apply the aws-auth ConfigMap to the cluster. Follow step 2 from these docs, using the NodeInstanceRole value you got as the Output from Step 3: Launch and Configure Amazon EKS Worker Nodes

To add a non-root IAM user or role to an Amazon EKS cluster, follow step 3 from these docs.
Edit the configmap/aws-auth and add other users that need kubectl access in the mapUsers section.

Run aws configure again and add the access key info from your non-root user.

Now you can access your cluster from the AWS CLI and using kubectl!

Getting the root user credentials is not possible for everyone. In my case, I am using centrally managed role by the organization. I have admin access but don't have root credentials.

Are you able to get the Access Key ID and Secret Access Key for the role you were logged in as when you created the cluster? (Or have an admin role get this for you, if you don't the permissions to do this). And then put that info in .aws/credentials and follow the steps above?

Root credentials are taboo.
This tool does not account for the use-case of SAML providers.  The STS AssumeRole always uses temporary keys.  If the master is looking at the temporary keys that is broken.  The keys expire in 60 minutes.
Mark Cwetna
•••sent from my iPhone•••

From: Yasmin<EMAIL_ADDRESS>Sent: Thursday, November 29, 2018 2:10 PM
To: kubernetes-sigs/aws-iam-authenticator
Cc: Mark Cwetna; Comment
Subject: Re: [kubernetes-sigs/aws-iam-authenticator] error: the server doesn't have a resource type "svc" (#157)
Are you able to get the Access Key ID and Secret Access Keyhttps://urldefense.proofpoint.com/v2/url?u=https-3A__docs.aws.amazon.com_IAM_latest_UserGuide_id-5Fcredentials-5Faccess-2Dkeys.html&d=DwMFaQ&c=fa_WZs7nNMvOIDyLmzi2sMVHyyC4hN9WQl29lWJQ5Y4&r=bizeWICKQs8YNpGSnQCdAWt6454ZIJWOmCQaNqXvmH4&m=1qvTmmy2jCwQTaseeb1l6AfLs-yGiOC07A8e3NrwC1I&s=ZH28w6e3zX9Go8YIZ63XzLn3Qh2Iron8Jm9G7Sn7C3s&e= for the role you were logged in as when you created the cluster? (Or have an admin role get this for you, if you don't the permissions to do this). And then put that info in .aws/credentials and follow the steps above?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_kubernetes-2Dsigs_aws-2Diam-2Dauthenticator_issues_157-23issuecomment-2D443012625&d=DwMFaQ&c=fa_WZs7nNMvOIDyLmzi2sMVHyyC4hN9WQl29lWJQ5Y4&r=bizeWICKQs8YNpGSnQCdAWt6454ZIJWOmCQaNqXvmH4&m=1qvTmmy2jCwQTaseeb1l6AfLs-yGiOC07A8e3NrwC1I&s=nUlEMjW1pCzIZ7VJv3VKsv8X6i_hundPxmmtm1t5O7M&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AE5bgtZcLvg9BqDD91KbstgJYkQSjqoeks5u0FttgaJpZM4XUt7I&d=DwMFaQ&c=fa_WZs7nNMvOIDyLmzi2sMVHyyC4hN9WQl29lWJQ5Y4&r=bizeWICKQs8YNpGSnQCdAWt6454ZIJWOmCQaNqXvmH4&m=1qvTmmy2jCwQTaseeb1l6AfLs-yGiOC07A8e3NrwC1I&s=o_1P9xlhRIg0gUTJI6I8pI84KB9y-LL-wIMqNxRsuW4&e=.

I usually use inter-account role assumption and terraform for creation. After reading above, I decided to do a terraform destroy on my eks master. Then I used the CLI to create it manually and I planned on just doing an import into terraform later. Before I used the CLI to create the new master, I created an IAM user just for the purpose of setting up this master and managing user access. I planned on deleting this IAM user later. But even with this IAM user, I am getting the exact same problem.
[staging_ekscreator]
aws_access_key_id=xxx
aws_secret_access_key=xyz

aws --profile=staging_ekscreator eks create-cluster --cli-input-json file://eks.json
aws --profile=staging_ekscreator eks update-kubeconfig --name my-eks
kubectl get svc --v=10
I1130 15:23:45.150251   17868 loader.go:359] Config loaded from file /Users/gmiller/.kube/config
I1130 15:23:45.151062   17868 loader.go:359] Config loaded from file /Users/gmiller/.kube/config
I1130 15:23:45.151634   17868 round_trippers.go:386] curl -k -v -XGET  -H "User-Agent: kubectl/v1.12.3 (darwin/amd64) kubernetes/xxx" -H "Accept: application/json, */*" 'https://xxx.sk1.us-west-2.eks.amazonaws.com/api?timeout=32s'
I1130 15:23:45.929480   17868 round_trippers.go:405] GET https://xxx.sk1.us-west-2.eks.amazonaws.com/api?timeout=32s 401 Unauthorized in 777 milliseconds
I1130 15:23:45.929518   17868 round_trippers.go:411] Response Headers:
I1130 15:23:45.929525   17868 round_trippers.go:414]     Audit-Id: xxx
I1130 15:23:45.929530   17868 round_trippers.go:414]     Content-Type: application/json
I1130 15:23:45.929535   17868 round_trippers.go:414]     Content-Length: 129
I1130 15:23:45.929542   17868 round_trippers.go:414]     Date: Fri, 30 Nov 2018 22:23:45 GMT
I1130 15:23:45.931723   17868 request.go:942] Response Body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}
I1130 15:23:45.933017   17868 cached_discovery.go:111] skipped caching discovery info due to Unauthorized
F1130 15:23:46.625767   17868 helpers.go:119] error: the server doesn't have a resource type "svc"

update:
https://docs.aws.amazon.com/eks/latest/userguide/create-kubeconfig.html
apiVersion: v1
clusters:
- cluster:
    server: <endpoint-url>
    certificate-authority-data: <base64-encoded-ca-cert>
  name: kubernetes
contexts:
- context:
    cluster: kubernetes
    user: aws
  name: aws
current-context: aws
kind: Config
preferences: {}
users:
- name: aws
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1alpha1
      command: aws-iam-authenticator
      args:
        - "token"
        - "-i"
        - "<cluster-name>"
        # - "-r"
        # - "<role-arn>"
      env:
        - name: AWS_PROFILE
          value: "staging_ekscreator"

adding this:
      env:
        - name: AWS_PROFILE
          value: "staging_ekscreator"

fixed my issue. So maybe on cluster creation you can just use a manually created IAM and then import it into terraform after you use this user to setup your user permissions. Then you can just delete this IAM user to keep your cloud tidy and secure. I'm trying that next.

It works for me now. I had to set the aws credentials in another session (tab) than the one that is using kubectl. Thanks @weotch.

im running into this exact same thing trying to deploy from circleci to an eks cluster. horrible experience.

I've tried about 15 times in the last 24 hours to create a cluster that I can actually access.
I've tried from the console, from the cli, with the terraform module.
I've double and triple checked that the IAM credentials I created it with are the same as the ones I am trying to connect with.
I've tried using a role, using root credentials, using an IAM user. I've tried specifying a profile or even the exact keys when using aws-iam-authenticator.
I have followed the official amazon getting started guide, the terraform getting started guide, and another random one I found.
Nothing I have done has resulted in a cluster that I can actually authenticate with or that nodes can even connect to. The authenticator can create a token but cannot verify it.
$ aws-iam-authenticator verify -i <clusterid> -t <token>
could not verify token: sts getCallerIdentity failed: error from AWS (expected 200, got 403)

Is EKS just broken?

@jpatters This has happened to me before too. You're not using Cloud9 by chance are you?
Also, what's in your ~/.aws/credentials (don't post it here) just curious if you have multiple profiles, or anything in there other than just aws_access_key_id and aws_secret_access_key. I once had aws_session_token= (no value) which screwed me up like you're seeing.
What's the output from aws sts get-caller-identity? Does it match the ID in your credentials?

@mrichman I am not using cloud9. However I did just get this to work by explicitly exporting aws key and secret
export AWS_ACCESS_KEY_ID=key
export AWS_SECRET_ACCESS_KEY=secret

(I know I said I tried this in my comment above but I must not have)
I do have multiple profiles in ~/.aws/credentials but I have verified that aws sts get-caller-identity returns the correct one.
At the moment, it seems to me like aws-iam-authenticator is not properly reading ~/.aws/credentials or maybe ~/.aws/config
It was working on a test cluster just now. I am now launching my intended cluster via terraform and I will report back what I find.

The only way it is working for me is if I explicitly export the credentials. It seems to be caused by the authenticator not reading ~/.aws/credentials properly (or not it at all)

Yes. second it. It works only if I explicitly export the credentials.

I spoke to a gentleman at the AWS EKS booth at Kubecon. I explained this problem and how I typically use credentials that are temporary from STS due to MFA and role assumption. He said they are getting a lot of complaints on this problem and that they are trying to come up with a good solution. I shared that what I had done was to make an IAM user in that specific account for the purpose of account creation and that I intended to delete the user after I setup permissions the way I needed on RBAC. He said that is a good solution except to not delete the account but to keep it as a break-glass account in case problems arose.
He also mentioned they may be working on a solution to expose master logs to you so you can see and troubleshoot without as much guessing.

Are there any other workarounds/fixes for this? I tried explicitly exporting AWS_ACCESS_KEY_ID and AWS_ACCESS_SECRET_KEY and that did not work. Also tried adding
env:
        - name: AWS_PROFILE
          value: "staging_ekscreator"

and that failed on cluster create too. The error I'm getting is ERROR:root:exec: process returned 1. could not get token: AccessDenied: Access denied 	status code: 403, request id: e63b2a9f-03e2-11e9-9cea-e510a9909b67 and I'm using the Kubernetes Python Client not kubectl.

Is this a problem with aws-iam-authenticator or not? Exporting the credentials is a valid workaround but very ugly.

Thanks for the investigation. Do I understand that this is a problem with EKS and not with BKPR?

Oh, and BTW, another alternative that I believe can work is exporting the environment variable AWS_PROFILE instead of using the --profile flags and modifying the Kube configuration.

We had the same issue with EKS cluster.
We use Jenkins to deploy. After many errors and tries, we verify the token with the following command
aws-iam-authenticator verify -i cluster_name -t token_id
it appears that the token has been generated for an IAM user than the expected role
We check the env variables. It appears that the following environment variables are set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY.
Those are injected by Jenkins (with the aws-credentials plugin).
So, the AWS profile was good, but it used env variables to generate the token.
By unsetting this env variables the token is well generated and we can now request the EKS cluster

I could not solve this issue by creating a cluster on AWS EKS GUI. I tried eksctl to create cluster and it worked.


Always format generated assets

It's easy to forget formatting assets after re-generating them, so let's
do this automatically.
@juliusv @fabxc

👍


ENYO-2692: Reset metrics for pages before jump on scrollToIndex

Issue:
The pageForIndex is calculated from (i / perPage) and pagePosition is calculated by accumulating each page height. That page height is comes from measured page size when the page is already generated. But, when page is not generated, defaultPageSize (perPage * childSize) is used instead. So, there is a chance of mistake that create pages not including the control i. The scrollToIndex fails to find c on recursive call and it enters infinite loops.
Fix:
Reset page metrics before calling pagePosition so that it can generate
right pages.
Enyo-DCO-1.1-Signed-Off-By: Kunmyon Choi<EMAIL_ADDRESS>

This fix does not seem to be needed any longer.  Closing.


[Cryptsy]Get correct Balance/Available and Pending

I change the API url. The pupapi2 doesn't work.

Can you check into the errors generated by Travis CI and fix any problems?

OK. I don't know Travis. I check this.

Ohh, cool. Now it is ok.


Runtime error on iOS 11

Hi DataDog team!
Here's an issue we encountered on our side related to using this SDK and running on iOS 11...
Describe what happened
With the package @datadog/mobile-react-native (version 1.0.0-rc2) installed in our React Native app, we get a runtime error with this error message: dyld: Symbol not found: _OBJC_CLASS_$_OS_dispatch_queue_serial.
The app then crashes.
Steps to reproduce the issue:

Install @datadog/mobile-react-native in a React Native (0.63.2) project.
Install pods: pod install --project-directory=ios
Run the app from Xcode on a simulator with iOS 11.4 installed.

Describe what you expected:
The application should be running without any issue.
Additional context
- Xcode 12.5
- Simulator 11.4
- React Native 0.63.2
This issue arises specifically from that line:
https://github.com/DataDog/dd-sdk-reactnative/blame/main/packages/core/ios/Sources/QueueHolder.swift
This file uses dispatch_queue_serial_t which is available only from iOS 12+.
Apple documentation: https://developer.apple.com/documentation/dispatch/dispatch_queue_serial_t
Commit that introduced the bug: https://github.com/DataDog/dd-sdk-reactnative/commit/c568d7f1f39e5a639937d5ff0c6884c65896845d
Specific line: https://github.com/DataDog/dd-sdk-reactnative/commit/c568d7f1f39e5a639937d5ff0c6884c65896845d#diff-0288ae99caf2c07d91fce825c748ddaa7b97c2514b32317bf3eb048257804436R9

Hello @ercote! Thanks for raising the issue. It was fixed and fix will be available in the next SDK release.

Thank you @0xnm for the quick fix! Greatly appreciated.


Execution failed for task ':server:appengineEndpointsGetClientLibs'

The error message was shown on Gradle Console like this when I run the app,  what's going on ?
:server:compileJava UP-TO-DATE
:server:processResources UP-TO-DATE
:server:classes UP-TO-DATE
:server:appengineEndpointsGetClientLibs FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':server:appengineEndpointsGetClientLibs'.

There was an error running endpoints command get-client-lib: connect timed out

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED
Total time: 24.109 secs

same question

same question

same problem

same problem

same question

same question

same question

same question

how to solve this?

same question

It seems all the user commenting "same problem" come from China.

same question

same question

same question.

same question.

same question.

same question.

same question.

same question

same question

same question

same  question & come from China.

+1

same question

+1

Is anyone fix this issue? Thanks

@Trevor Johns

Hi, I finally solved this.
Read this，and if you are in China, use SSTap or what so that you can get a global agent. Then all work.
参考链接中的答案按照他的步骤来，然后开着全局翻墙，让AndroidStudio走代理。就可以了。

kongdeli的方法经测试可行，记得一定要挂代理

开了全局之后重启一下android studio

我直接在Android Studio的设置中设置代理无效。在项目的gradle.properties文件设置代理才生效了，代理设置失败的可以试试我这种设置方式。

Obsolete after the 2018 version rewrite.


Broken link to sample

And this article also doesn't seem connected to the TOC

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

ID: ce840080-2d1b-6eab-df07-5adddb1d44c1
Version Independent ID: c951952f-e5d9-2286-fea9-35cffa06d5ae
Content: Interpret ML.NET models with Generalized Additive Models - ML.NET
Content Source: docs/machine-learning/how-to-guides/use-gams-for-model-explainability.md
Product: dotnet-ml
GitHub Login: @natke
Microsoft Alias: nakersha

Thanks for raising this issue @mairaw . I was already working on this but now we have an issue to track the work item to :)

AB#1667151


ESLint documentation and CI

Describe the bug
Currently nothing ensures that the ESLint are complied. Currently 12 errors are displayed:
Async-api generator\lib\generator.js
  166:7   error  Add logic to this catch clause or eliminate it and rethrow the exception automatically  sonarjs/no-useless-catch
  217:7   error  Add logic to this catch clause or eliminate it and rethrow the exception automatically  sonarjs/no-useless-catch
  248:7   error  Add logic to this catch clause or eliminate it and rethrow the exception automatically  sonarjs/no-useless-catch
  368:3   error  Refactor this function to reduce its Cognitive Complexity from 26 to the 15 allowed     sonarjs/cognitive-complexity
  390:13  error  Merge this if statement with the nested one                                             sonarjs/no-collapsible-if
  495:7   error  Add logic to this catch clause or eliminate it and rethrow the exception automatically  sonarjs/no-useless-catch
  544:7   error  Add logic to this catch clause or eliminate it and rethrow the exception automatically  sonarjs/no-useless-catch
  586:7   error  Add logic to this catch clause or eliminate it and rethrow the exception automatically  sonarjs/no-useless-catch
  654:9   error  Refactor this function to reduce its Cognitive Complexity from 25 to the 15 allowed     sonarjs/cognitive-complexity
  786:7   error  Add logic to this catch clause or eliminate it and rethrow the exception automatically  sonarjs/no-useless-catch

Async-api generator\lib\watcher.js
  125:14  error  Expected '!==' and instead saw '!='  eqeqeq
  127:19  error  Expected '!==' and instead saw '!='  eqeqeq

Furthermore the CONTRIBUTING guideline for code validation is outdated. Command should be npm run lint
How to Reproduce
run npm run lint
Expected behavior
Would be nice if this was added as a check with the CI on each PR to ensure they comply with the code validation.

There was some errors with some of the other files not being LF, not sure if that's only on my machine or not?

I think everything has been fixed in #316. It's already on master. Can you verify?

All there is left is errors in regards to:
Expected linebreaks to be 'LF' but found 'CRLF'  linebreak-style
However this is a windows problems, so I guess we can disregard those 😄 However I would still suggest we include the check in the CI. They should be complied with just as tests.

Can see the CI already checks for it now, closing.


Implement new specs for push & pop in asm parser

This PR addresses the second stage of #84 as well as the new mem ops specified in #102

changes push handling for decimal/hexadecimal constants to allow multiple values in the format push.a.b.c... up to 16 values
adds new hex parsing to allow multiple hex values to be specified without separators, as long as the total number of specified bytes is a multiple of 8 (e.g. push.0x0000000000001234000000000000abcd)
adds push.mem/push.mem.a and pop.mem/pop.mem.a to push and pop single elements from/to memory
stubs out push.local.i and pop.local.i to be completed with the rest of the local memory handling in stage 3 of #84
updates and adds unit tests for all of the above

Another thing I'm wondering: since the file is getting rather big, should we split out tests into a separate file?

I see your point, and I don't feel very strongly, but personally I would lean towards keeping it as it is. The idiomatic structure for Rust is to keep unit tests in the same file and have separate test files be for integration tests, and I like the current organization of the parsers. The addition of the locals handling + tests will increase it by a couple hundred lines at most.
One thing that I've thought about which could address this is that while the "invalid" tests that ensure ops are well-formed are very useful and do belong here, I'm not as convinced by the "valid" tests like popw_mem or push_one. I wrote them on the first implementation to get my head around what was going on, but they feel sort of redundant and ineffective. Maybe this checking should be in the processor integration tests instead and removed from here. That would considerably shorten the file length

I think it's correct, but perhaps the variable is poorly named, and maybe it could also use inline comments to make it clearer. What do you think?
The idea is that with storew the top 4 elements are written to mem and then left on the stack (the stack is preserved), whereas with popw they are written to mem and then popped from the stack (the stack is not preserved). The address is always removed from the stack during all mem ops, so the "preserve_stack" bool is only talking about the rest of the stack, not about the address.
------- Original Message -------
On Friday, February 11th, 2022 at 6:40 AM, jonathanxuu @.***> wrote:

@jonathanxuu commented on this pull request.

In assembly/src/parsers/io_ops.rs:

@@ -198,7 +254,7 @@ pub fn parse_storew(span_ops: &mut Vec, op: &Token) -> Result<(), Ass
}

 match op.parts()[1] {

   "mem" => parse_mem_write(span_ops, op),

   "mem" => parse_mem_write(span_ops, op, true),

The memory address should be removed from the stack by STOREW according to spec

Perhaps, the preserve_stack should be false here.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

这是来自QQ邮箱的自动回复邮件。徐毅正已经收到了您的邮件。


Integrating Azure Application Insights using opentelemetry-instrumentation in the Sample-app-aoai-chatGPT

Integrating Azure Application Insights with the Sample-app-aoai-chatGPT
This guide walks through the process of integrating Azure Application Insights into the AOAI sample app using OpenTelemetry. This integration allows for enhanced monitoring and observability of the application. (Don't forget to run .\start.cmd to at the end to rebuild the vite / JS files before commiting and syncing your changes to Github so it gets deployed correctly to the web app!! )
Keep an eye on the Python package numbers for opentelemetry packages, don't forget the distro ! If Pip is up to date then it should warn you..
Prerequisites
An Azure Application Insights instance.
A fork of the AOAI sample app repository in Github Visual Studio Code.
Configuration Steps
1. Configure Azure Application Insights
After creating your Application Insights instance in Azure, add the APPLICATIONINSIGHTS_CONNECTION_STRING to your Azure Web App Service configuration for the sample web applications.
Key Setting:
APPLICATIONINSIGHTS_CONNECTION_STRING :
2. Update Local Environment
In your local environment, within the Visual Studio Code or your preferred editor, navigate to the root of your fork of the AOAI sample app repository.
3. Install Required Python Packages
Run the following command to install necessary Python packages for OpenTelemetry:
pip install opentelemetry-distro==0.43b0 opentelemetry-instrumentation==0.43b0 opentelemetry-instrumentation-flask==0.43b0 opentelemetry-sdk==1.22.0 opentelemetry-instrumentation-requests==0.43b0 azure-monitor-opentelemetry-exporter==1.0.0b18
4. Update requirements.txt
Modify the requirements.txt file under the /static directory to include the new packages:
azure-identity==1.14.0
opentelemetry-distro==0.43b0
opentelemetry-sdk==1.22.0
opentelemetry-instrumentation==0.43b0
opentelemetry-instrumentation-flask==0.43b0
opentelemetry-instrumentation-requests==0.43b0
azure-monitor-opentelemetry-exporter==1.0.0b18
Flask==2.3.2
openai==0.27.7
azure-search-documents==11.4.0b6
azure-storage-blob==12.17.0
python-dotenv==1.0.0
azure-cosmos==4.5.0
fpdf==1.7.2
python-docx==0.8.11
pymongo==4.5.0
5. Update app.py
Modify app.py to include OpenTelemetry configuration. Replace the existing imports and setup with the following code:
5. Update app.py
Modify app.py to include OpenTelemetry configuration. Replace the existing imports and setup with the following code:
import json
import os
import logging
import requests
import openai
from azure.identity import DefaultAzureCredential
from flask import Flask, Response, request, jsonify, send_from_directory
from dotenv import load_dotenv
from backend.auth.auth_utils import get_authenticated user_details
from backend.history.cosmosdbservice import CosmosConversationClient

# OpenTelemetry imports and setup
from opentelemetry import trace
from opentelemetry.sdk.trace import TracerProvider
from opentelemetry.sdk.trace.export import BatchSpanProcessor
from azure.monitor.opentelemetry.exporter import AzureMonitorTraceExporter
from opentelemetry.instrumentation.flask import FlaskInstrumentor
from opentelemetry.instrumentation.requests import RequestsInstrumentor

load_dotenv()

APPLICATIONINSIGHTS_CONNECTION_STRING = os.environ.get("APPLICATIONINSIGHTS_CONNECTION_STRING")

# Configure logging
logger = logging.getLogger(__name__)
logger.setLevel(logging.INFO)

# Configure OpenTelemetry with Azure Monitor Exporter
trace.set_tracer_provider(TracerProvider())
tracer_provider = trace.get_tracer_provider()
tracer_provider.add_span_processor(
    BatchSpanProcessor(AzureMonitorTraceExporter(
        connection_string=APPLICATIONINSIGHTS_CONNECTION_STRING)
    )
)

app = Flask(__name__, static_folder="static")

# Enable Flask auto-instrumentation
FlaskInstrumentor().instrument_app(app)

# Enable Requests auto-instrumentation
RequestsInstrumentor().instrument()

The rest of the app.py code..
6. Run the Application
Execute the ./start.cmd script to start the application. This will apply the changes and start the Flask server with OpenTelemetry integration.
7. Finalize Changes
Ensure to save, commit, and sync these changes to your forked private repository.

Feel free to remove thi if it's already been sorted...

current app is using the quart implementation? how we can integrate with?


Azure Maven Plugin for Web Apps Does NOT Allow the Use of Existing App Service Plans

Plugin name and version
Azure Maven Plugin for Web Apps 0.1.5
Plugin configuration in your pom.xml
Any configuration
Expected behavior
Should allow the use of existing app service plans
Actual behavior
Does not allow the use of existing app service plans. It creates an app service plan for every deploy. This limits the use of the Maven plugin because there are subscription limits - https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits#app-service-limits. There are known issues to cleanup app service plans which further aggravates developers. We have run into these limits several times now and then had to open support tickets to clean up app service plans. This creates FRICTION for developers.
The Azure Management Libraries for Java make it simple to use existing App Service Plans.
Steps to reproduce the problem
Just keep running one of the sample deployments to Azure Web Apps

@jdneo - please take a look at this issue


No response in the game about the content of chat function input

When I input text in the chat function, but the chat box in the game doesn't respond

Press the R key first, then input the content you need to display in chat, and then input any text in the game material border to display the text entered in chat, such as

However, this has become troublesome again. However, I recently discovered this problem. If this problem is not triggered, you can enter good content and press enter to display the content I have entered in the game

https://user-images.githubusercontent.com/816502/176070652-194a70a2-1beb-472e-ac80-94089b34587c.mp4
You can't have any controller connected.
The yellow/green pro controller in the video is the virtual controller.
You need to give the control to the virtual controller for the chat to work.

It seems that the virtual handle can't be connected to my machine

There is no connection in the handle interface

In fact, it is very simple to solve this problem. You can click detach on the Dutch sailors in the Dodo help interface to solve this problem. Thank you for your video, which provides me with ideas to solve this problem.

I added an extra button so that you can easily connect the controller without going to the dodo helper.

ok


feat: add supported countries api

we will have a breaking change if we decide to add different providers for country
Why will we have a breaking change if we use another country provider? CCA2 is a standard for country codes.

This PR precedes the mobile component https://github.com/GaloyMoney/galoy-mobile/actions/runs/5125730731/jobs/9219293994?pr=2246

we will have a breaking change if we decide to add different providers for country

Why will we have a breaking change if we use another country provider? CCA2 is a standard for country codes.

this is for validation, I meant  verification code provider, for example the african provider does not offer whatsapp so we need to inform mobile wallet what to offer. Please create a Country Type with a CountryCode attribute this will give us more flexibility in case we need to add more attributes.


knockpy: relax pyopenssl

Description of changes
Fix build (https://hydra.nixos.org/build/253559456)

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 299709 run on x86_64-linux 1

2 packages built:

knockpy
knockpy.dist


Update nnunet-customized to use scikit-learn instead of sklearn

Hi @wasserth , thanks for the excellent project! I recently encountered an error when installing TotalSegmentator. After digging into it, it turns out that nnunet installed sklearn instead of scikit-learn.
It got fixed two days ago in the original repo https://github.com/MIC-DKFZ/nnUNet/pull/1209#issuecomment-1426233399 but if I understand it correctly, it is needed to update that in the fork as well.

In the custom fork of TotalSegmentator this should already be fine: https://github.com/wasserth/nnUNet_cust/blob/working_2022_03_18/setup.py
Maybe the error has some different reason?

That was a good hint. The change was part of the nnunet_cust masterbranch but not part of the pip package yet. I updated it now. Could you try again with the latest TotalSegmentator master?
pip install git+https://github.com/wasserth/TotalSegmentator.git

It seems to work for me, sklearn requirements is now gone
Requires: batchgenerators, dicom2nifti, medpy, nibabel, pandas, requests, scikit-image, scikit-learn, scipy, SimpleITK, tifffile, torch, tqdm
Thank you ! Exceptional project!

Thank you! It works perfect now 👍

Hi @wasserth , first of all, thank you for this excellent contribution.
Unfortunately, I hit the same problem with sklearn when installing from pip with: pip install TotalSegmentator. The version that gets installed is 1.5.2 and I can see that is prior to this fix.
Is it possible to release a new version with this fix?
Thank you very much in advance!

I can confirm the latest version in PyPI is broken. A new version release would be greatly appreciated!


feat: export typescript types

This is so that users of this package can have information about the types exported.
The code in this package is not typechecked (the types are separate from the source code), but this could be done as a non breaking change later.
Notable choices:

the type of the context arguments is separate from the location type, and the first and second context have separate types
The location type and the ontext types default to the browser Location type
The location type must extend { hash?: string; action?: 'PUSH' | string }. This is the same as extending any object except that if there is a hash or action key they must be strings, and the 'PUSH' is jsut a hint to the user as to which string will have an effect.

@hedgepigdaniel Sorry for the delay here. I pushed a commit improving the type defs a bit. Let me know what you think.

Also updated the tooling, added Prettier, and added basic linting and testing around the types.

btw let me know if you want me to cut a release with just this, or if you want us to also resolve https://github.com/taion/scroll-behavior/pull/293 before cutting

Thanks!
For my use case I probably wouldn't use the release until both issues were resolved, but it wouldn't hurt to cut one.
Re your changes, I noticed these things when updating:

the types of the prevContext and context arguments are the same. In my case the context is a request object (which has preferences to the previous location). So the only possible use case for the second context arg is to pass some separate extra information, which is not possible if the types have to be the same. That said, I didn't feel the need to use it, and if I do I can instead just include that extra information in my request object.
The action key is required in the location type. This is fine (I can set it to some string that isn't "PUSH"), although I don't see the point of having to set it to a string given that I don't want to suppress the saved position for a location that already has a saved value
The context argument is required for updateScroll. This makes sense I think.

So basically yes, this works well.

for the action thing... that's really just push v pop. since we want to do different things for push v pop transitions.
for updateScroll and friends – the idea is that in my current use cases, the context only describes the current location (indeed, in the examples here, it's just the location). i suppose if your context already includes information on the previous location, then you can just always pass in null for prevContext. this is allowed in all cases.


Metadata client doesn't work on Databricks

Metadata client doesn't work on Databricks, probably due to a conflict in RocksJava version.
Steps to reproduce:

Have a public lakeFS installation ready (you can use Terraform), with a repository and a commit.
Start a Databricks cluster.
In the cluster configuration > Libraries tab, click Install new.
Put in the Maven coordinates for the metadata client: io.treeverse:lakefs-spark-client-301_2.12:0.1.0-SNAPSHOT
Put in the repository: https://s01.oss.sonatype.org/content/repositories/snapshots
In the cluster configuration > Configuration tab > Advanced options > Spark tab, configure the lakeFS client:spark.hadoop.lakefs.api.url http://<lakefs api endpoint>/api/v1/
spark.hadoop.lakefs.api.access_key <lakefs access key>
spark.hadoop.lakefs.api.secret_key <lakefs secret key>

In a Scala notebook attached to the cluster, run the following code:import io.treeverse.clients.LakeFSContext
var df = LakeFSContext.newDF(spark, "example-repo", "your-lakefs-commit-id")
df.show

The following error appears:
IllegalAccessError: tried to access field org.rocksdb.RocksObject.nativeHandle_ from class org.rocksdb.SstFileReader

The reason may be that Databricks has an old rocksdb-jni jar in the classpath.
A possible solution could be to shade the rocksdb jni in the lakeFS uber-jar, and install the uber-jar on Databricks instead of using the Maven coordinates. However, this will also be challenging since the underlying native library needs to somehow be wired to the shaded jars.

This smells like a shading issue, but with a JNI thrown in to complicate matters.
Per https://docs.oracle.com/javase/8/docs/technotes/guides/jni/spec/invocation.html#library_version we may need to load different JNI versions into different ClassLoaders (the Spark hate of ClassLoaders might be striking us again).  I.e. we'd need to load parts of the RocksDB wrapper from a separate ClassLoader.

Shading really hard here, as is dynamic loading.
https://github.com/JohnSnowLabs/spark-nlp/issues/105 might be relevant (but really old).

Update :-(
Not really possible to shade rocksdbjni:

The JAR file holds its .so in the root, so it will never loading the right one (Spark shared its ClassLoader with the JARs it loads, so both shaded and unshaded versions of the JAR always find the same .so, which is sad).
I forked rocksdbjni and made it use a .so on the package path.  Now the ClassLoader loads the shaded rocksdb which finds the right .so... and immediately fails to load the JNI, because the C++ symbol name has to contain the full package path (and shading doesn't change .so's, because it doesn't know anything about binaries).

:-(

Proposal
We see only rocksdbjni 6.2.2 on DataBricks.  If we support (only!) that version, we should be good there and everywhere else.
Possible issues

This version is 2 years old.  It may have issues.  While on DataBricks we will be able to disavow responsibility for not upgrading, that will be harder on other platforms.
Some fixed bugs will still affect all users, including those not on DataBricks.
If (when...) DataBricks issue a new version that uses some less historical version of rocksdbjni, we will have to split our support into two JARs.

Fixes to rockdbjnbi after 6.2.2 filtered for relevance
These are up to 6.20.3, which is the current release.
We only read files, which makes most fixes less important.

Fixed a backward iteration bug with partitioned filter enabled: not including the prefix of the last key of the previous filter partition in current filter partition can cause wrong iteration result.
Add a new option BlockBasedTableOptions::max_auto_readahead_size. RocksDB does auto-readahead for iterators on noticing more than two reads for a table file if user doesn't provide readahead_size. The readahead starts at 8KB and doubles on every additional read upto max_auto_readahead_size and now max_auto_readahead_size can be configured dynamically as well. Found that 256 KB readahead size provides the best performance, based on experiments, for auto readahead. Experiment data is in PR #3282. If value is set 0 then no automatic prefetching will be done by rocksdb. Also changing the value will only affect files opened after the change.
(Possibly some fixes to checksum validation; not sure because we never read a "full" RocksDB, only single component objects.)
Fix a bug where compressed blocks read by MultiGet are not inserted into the compressed block cache when use_direct_reads = true.  (Possible performance degradation, nothing worse)
Fixed a bug in the following combination of features: indexes with user keys (format_version >= 3), indexes are partitioned (index_type == kTwoLevelIndexSearch), and some index partitions are pinned in memory (BlockBasedTableOptions::pin_l0_filter_and_index_blocks_in_cache). The bug could cause keys to be truncated when read from the index leading to wrong read results or other unexpected behavior.
Fixed a bug when indexes are partitioned (index_type == kTwoLevelIndexSearch), some index partitions are pinned in memory (BlockBasedTableOptions::pin_l0_filter_and_index_blocks_in_cache), and partitions reads could be mixed between block cache and directly from the file (e.g., with enable_index_compression == 1 and mmap_read == 1, partitions that were stored uncompressed due to poor compression ratio would be read directly from the file via mmap, while partitions that were stored compressed would be read from block cache). The bug could cause index partitions to be mistakenly considered empty during reads leading to wrong read results.

An EXPERIMENTAL new Bloom alternative that saves about 30% space compared to Bloom filters, with about 3-4x construction time and similar query times is available using NewExperimentalRibbonFilterPolicy.  (_This means we will not be able to use this new Bloom alternative in Graveler..._)

Reduced memory copies when fetching and uncompressing compressed blocks from sst files.

Currently it seems that we are stuck with RocksDBJNI 6.2.2, at least when running on DataBricks.
Unfortunately this runs into a major problem:
rocksdbjni 6.2.2 does not export SstFileReader to Java
Options...
Work around it by setting up a mini-RocksDB
We can mostly work our way around this.  The key is to create a new RocksDB (directory), and "ingest" the file into RocksDB.  That usually requires a copy, but if we set the "move files" ingest option then there is no copy.  We still have to create a new DB for every file we open, which is 8 extra files totaling some 27 KiB.  Now we may iterate over this DB.
In fact we can name the DB for the metarange ID (or any similar identifier) as a first step in cache management.
Pros

Uses standard existing tested code to read SSTables.
Moderate effort on main code path

Cons

Ops: ingests are inherently trickier than opens.
Ops: need to create and manage multiple directories, each holding a RocksDB.
Ops: moving files quickly can be tricky to set up (need to have source and dest on same POSIX filesystem)
Have to set up some caching mechanism, with further code & ops & future development required

Fine, I'll write my own SSTable reader!
The RocksDB SSTable format that we use is documented: it's the block-based SSTable format.  And there are no merges or levels or tombstones or anything, it's a single-pass write.  Write our own JVM-based reader for a single file.
Pros

Known amount of effort: essentially parse file from the end, then look up a key in a 2-level consecutive map
No shading issues (no-one else uses it, and even when they do -- it's pure Java)
Can rely on OS caching of blocks

Cons

New code, possible surprises in the actual format on disk
Not using existing code, which was half the point of using a standard format
Ops: new code means novel error messages & behaviour

Write a DynamicShadingLoader or something
Write a new ClassLoader.  It will load a JAR-packaged rocksdbjni (probably a resource JAR inside our library JAR) and expose that as an appropriately shaded class.  Using some additional bytecode / reflection magic, we will be able to call routines from this JAR.  Because it will be loaded into a separate ClassLoader, we can control sharing with the Spark ClassLoader.  Probably we shall package the entire FileSystem JAR as a resource with this code, and have a single function that extracts an InputFileFormat (and some other code for export) from there.
Pros

No change to existing rocksdbjni code
Allows upgrading rocksdbjni versions
Uses standard existing tested code to read SSTables.

Cons

New area of JVM for us (me)
Clunky build, need to put a JAR inside another JAR
Not clear how to support export: it is not really based on an InputFileForma, so needs to be handled separately

Great analysis!
It's a hard problem indeed.
I'm leaning towards opening an issue (epic?) for suggestion 2: developing our own SST reader (possibly by forking rocksdb?). Considering that we rely heavily on this format, it makes sense that we would want more control over the code that does the reading. Being dependent on the only Java library in the world that can read it is evidently problematic.
That being said, this is a big effort so I think doing suggestion 1 is a good short term solution.

Had some luck using Databrick's init scripts.
The below simple script allow the export flow to continue (but flow failed because of serialization errors, see #2200 ). Hence I'm reluctant to say that using the init script will allow export to work, we should use it for debugging further issues with the Export on Databricks, and not as a workaround to enable it.
The script uses an existing rocksdbjni with version 6.4.4 (same one lakeFS jar uses) that already existed on the VMs (7.6 (includes Apache Spark 3.0.1, Scala 2.12)). If we do decide to release this script as a temp solution, we should use maven install instead of relying on the package location in the VM.
sudo rm /databricks/jars/----workspace_spark_3_0--maven-trees--hive-2.3__hadoop-2.7--org.rocksdb--rocksdbjni--org.rocksdb__rocksdbjni__6.2.2.jar
sudo cp /dbfs/FileStore/jars/maven/org/rocksdb/rocksdbjni-6.6.4.jar /databricks/jars/rocksdbjni-6.6.4.jar


Allow User to Confirm or Reject Breaks

By default all Ended Breaks should be Automatically Confirmed

Included in v.1.1.0

https://github.com/Skuty/TrackYourDay/pull/25


Kafka not sending across data for GIF image

Investigate why Kafka Topic not receiving message from Producer.

Related to #8, Kafka initializes with MAX_SIZE lesser than 1MB.
Closing this issue.