Fix: container argument for keda-operator in 12-keda-deployment.yaml

Fixed keda-operator container argument causing pod crashloop
Checklist

[ ] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ ] A PR is opened to update KEDA core (repo) (if applicable, ie. when deployment manifests are modified)
[ ] README is updated with new configuration values (if applicable)

Fixes #191

@zroubalik Can you review this one please? Given this is inline with the raw YAML that we have on https://github.com/kedacore/keda/blob/main/config/manager/manager.yaml#L32

--enable-leader-election was the previous flag, --leader-elect is the new flag we are going to use with KEDA 2.5, this change was brought be migrating to Kubebuilder v3 - https://github.com/kedacore/keda/pull/2082

So I presume this enhancement is redundant then @zroubalik ?

@tomkerkhove yeah, from 2.5 onwards we will use --leader-elect flag.

Thank you for your contribution but it seems like we no longer need this.
Feel free to re-open if you feel the need.

@tomkerkhove Thanks for your time, but I can see that latest helm chart version is 2.4 which is expecting --leader-elect flag hence we are unable to use it. My suggestion is either 2.4 should have older docker image which would work with older flag or it should have new flag.

v2.4 is using --enable-leader-election as per https://github.com/kedacore/charts/blob/v2.4.0/keda/templates/12-keda-deployment.yaml#L54.
What is currently in master is just the WIP version of what v2.5 will be, we only bump the chart version when we are about to ship.


how can i draw different class?

i set 5 classes in it ,but i dont know how to choose these class. it seems no thing happend whether click the class button on the right of the windows

Can you pull and try now? It was a bug, I think it works now. Thanks!

Can you pull and try now? It was a bug, I think it works now. Thanks!

yes，it works and i have another question ，if i add a predict mask，how can i delete it， thanks

I have not added delete yet. Seems like a couple people want it, I'll add it soon. Closing this issue for now.


[FEATURE] updateScaleDefaults does not change active scales

Expected Behavior
I think when this method is called the chart should be redrawn with the updated scale defaults. I tried using .update() and .render() after the call but both have no effect.
Using the method when initializing the charts it does have effect, so that is not the issue.

Current Behavior

Currently the .updateScaleDefaults method only has an effect at the initialisation of charts, but not to change the style of a scale during execution time.
Context
I am trying to implement some sort of theming inside a dashboard, switching between dark and light styles. Found the updateScaleDefaults method, which seems suited for my goal but the changes made here do not take effect.

Environment

Chart.js version: 2.5
Browser name and version: Chrome v57
Link to your project:

This is currently as designed. I don't think it's wise to change this. In v2.5 we released support for updating options by changing the actual options. @simonbrunel thoughts?

@etimberg That would mean for me that I have to go over every single chart and change the options of the individual charts. If this could be done globally it would make it more efficient, as you don't have to specify all the options for each chart in that case.

@etimberg Changing defaults shouldn't impact already instantiated charts, meaning that all options should be resolved at construction time and not change until next update(). Calling chart.update() should re-evaluate all options (user options + defaults options, including scale defaults). That would simplify things since we could remove all random access to Chart.defaults and would make the whole logic more robust and predictable IMO.
@Evertvdw So yes, I think chart.update() should update scales options based on the current defaults.

@simonbrunel I can support that. Sounds like a good change.

@Evertvdw How did you solve this problem? I am also trying to have themes in our charts - option to chose between light / dark theme. @simonbrunel @etimberg Any better way do this currently that updateScaleDefaults?

With the change in v3.0.0-beta.12 to how options are handled, this works. See https://jsfiddle.net/q87z24s5/


1.1.0: separate code and docs

Hi @michaelrsweet .
Separate code and docs only. No changes code.

Not interested in doing this.


updated readme (user and developer documentation)

Hey, I updated the readme with all necessary informations the user needs to run the code.

Looks good, thank you!


Artifacts on the web page for LinkFree on the QR Codes screenshot

Description
This is the same issue as I just raised with the other section.
The screenshot we have used contains little bits of text that can be cropped out.

DL 🙇♂

Screenshots

Additional information
No response

Hello @loftwah if it is approved than can I work on this issue ?

All good with me, assuming it is approved and nobody else has it earmarked.

awesome ! have created a pr !


Normalize column names based on veda-tags.json

@siddharth-krishna I had a quick look at the changes and I think I know where (part of) the problem is. In case of TFM_* and UC_T tables, we should not switch to using cset_cn or pset_pn columns.

@siddharth-krishna with the latest changes both Demo 1 & 2 should be back at 100%. :-) One can't see this on CI, because pyright is throwing some errors...
For the other Demos, there seems to be an error due to renaming of allregions to value. Later on we use melt, but it fails because a column named value is already present (due to alias normalisation).

Thanks Olex! I can look into the issue with melt.
Btw it looks like your last commit has made changes to every line in the two files. Perhaps your editor's settings have changed / need to be changed to not convert line endings to Windows style?

Also, I'm curious why the transform apply_postnormalisation_fixes that you added is reverting some of the normalization? For instance, it renames commname to commodity for ~FI_COMM tables, but that is the opposite of the normalization specified by veda-tags.json for this table tag. Perhaps a better solution is to change the code to use commname instead of commodity? (Or change the canonical name for this column to commodity in veda-tags.json)

Sorry for the string of comments :)
So the issue with the melt is that we have tables containing both an allregions column and a region name column e.g. REG1 in DemoS_004/SysSettings.xlsx:B6:H14. How should we handle the case when a row has values in both columns? The rightmost column has priority?

Thanks Olex! I can look into the issue with melt.
Btw it looks like your last commit has made changes to every line in the two files. Perhaps your editor's settings have changed / need to be changed to not convert line endings to Windows style?

Apologies for this! An issue with pyright was preventing me from committing, so I uploaded the files via web interface... Otherwise, I believe, my git settings handle this.

Also, I'm curious why the transform apply_postnormalisation_fixes that you added is reverting some of the normalization? For instance, it renames commname to commodity for ~FI_COMM tables, but that is the opposite of the normalization specified by veda-tags.json for this table tag. Perhaps a better solution is to change the code to use commname instead of commodity? (Or change the canonical name for this column to commodity in veda-tags.json)

Yeah... As you can see the canonical field names are not consistent across the tables and they come from elsewhere (that is why I didn't change veda-tag.json). At the same time there is no reason to keep the distinction in the code (makes things confusing, I think).
So basically, normalisation ensures canonical field names are used in the tables, while the fixes transform (we could give it a better name) allows to make the field names consistent across the tables.
I'm open to changing this approach. :-)

Sorry for the string of comments :)
So the issue with the melt is that we have tables containing both an allregions column and a region name column e.g. REG1 in DemoS_004/SysSettings.xlsx:B6:H14. How should we handle the case when a row has values in both columns? The rightmost column has priority?

No problem! I think we should just do it as before, i.e. the columns to the right become rows that are lower than those to the left. I've added more renaming to the post-normalisation transform to make it work as before, so we can check whether anything else was affected by the normalisation.

Seems only Demo 9 is failing now, but the convergence on e.g. Ireland has decreased.

@siddharth-krishna with the latest commit all the benchmarks will execute (if pyright let's them).
I've stumbled upon another issue that is reducing the match. Somehow TechName (column headear) ends-up in the attribute column, while the actual name of the process is placed in the value column (i.e. search for "techname" in merged_tables to see what I mean).

I fixed all regressions! :)

An issue with pyright was preventing me from committing

Btw, you can git commit --no-verify to skip the pre-commit checks.

Yeah... As you can see the canonical field names are not consistent across the tables and they come from elsewhere (that is why I didn't change veda-tag.json). At the same time there is no reason to keep the distinction in the code (makes things confusing, I think).

I agree that it's nicer if the code uses commodity everywhere. But is there any reason that the veda-tags.json file needs to be consistent with its source? I would rather specify the canonical field name in the config file than have a hacky post-normalization fix transform.
If we do this, we can also change the canonical name for allregions to be allregions and not value, that would allow us to maintain the code as it is.

Great, thanks! Regarding the canonical names, I guess the main reason for me was the fact that the source determines them, not us... I'd say the fixes transform is temporary and is meant to make things work while clearly showing "inconsistencies" from the source.
There is some more info that I would like to pick up from the file. We could restructure it after that in a way that allows us to get rid of the fixes. Would that work?

Okay, sounds good, thanks. If the source is something we'd like to sync with again in the future we can move the fixes code to utils/ and make a little script that generates our version of the canonical file in configs/. That way it's clear that the file in configs/ is our version that our code is consistent with, and we have a script to re-generate it from source if necessary.


Docker: failed to build v1.1.0

I used Dockerfile from realease v1.1.0, with modification on DCORE_SYMBOL_NAME.

The command '/bin/sh -c git clone -b $version https://github.com/EOSIO/eos.git --recursive     && cd eos && echo "$version:$(git rev-parse HEAD)" > /etc/eosio-version     && cmake -H. -B"/tmp/build" -GNinja -DCMAKE_BUILD_TYPE=Release -DWASM_ROOT=/opt/wasm -DCMAKE_CXX_COMPILER=clang++        -DCMAKE_C_COMPILER=clang -DCMAKE_INSTALL_PREFIX=/tmp/build  -DSecp256k1_ROOT_DIR=/usr/local -DBUILD_MONGO_DB_PLUGIN=true -DCORE_SYMBOL_NAME=$symbol     && cmake --build /tmp/build --target install && rm /tmp/build/bin/eosiocpp' returned a non-zero code: 1

Full build logs can be found on Travis CI.
Also, there are a lot of warnings, more than versions before.
Is there a need to update Dockerfile or eosio/builder for v1.1.0?

you need to build a new builder image, official one is not up to date.

How does one build a new builder image? Normally the docker repo would show the Dockerfile used to generate the image, but perhaps I don't have enough Docker experience to know what I'm missing here?

The builder image has been updated on DockerHub, and the v1.1.0 image of eosio/eos and eosio/eos-dev are now available as well.
You can do docker pull eosio/builder:latest to get the updated builder, and then you build should be successful.

@JohnnyZhao @ericiles Thanks, it is working.
The sync is far quicker than before.


Use -d:release for Nim

@frol can you merge this and re-run benchmark? Nim will be much faster with that :)

I am so sorry for that! I will update the numbers ASAP!

You might want to run with --gc:markAndSweep as well as it is quite a bit faster.

I will give it a try!

@frol also you can use clang with Nim:
nim c -d:release --cc:clang file.nim
You can add both GCC/Clang results (they probably would differ)

@Yardanico clang makes it slower:

Options
Time, seconds
Memory, MB

--opt:speed
4.0
0.5

-d:release
0.95
0.5

-d:release --gc:markAndSweep
0.55
5

-d:release --gc:markAndSweep --cc:clang
0.6
5

Notice the memory usage. Is that expected?
I have updated the results!

@frol can you keep both versions in the tables? One with -d:release (for low memory) and the other with -d:release --gc:markAndSweep (for maximum speed).

Notice the memory usage. Is that expected?
The different GCs use different amounts of memory. I don't have the memory checking utility installed, would be interesting to run it with all the different GCs and see what the performance/memory balance between each was.

@narimiran Done!

Not sure why you are seeing so high memory usage rates. I installed cgmemtime and these are my results from all the different GCs: https://i.imgur.com/1Xz3Elo.png

It seems that object vs ref object is a big deal, it is 376 KB now!
-d:release --gc:markAndSweep now has the lowest time and memory footprint! Should I drop the line representing the results for -d:release without --gc:markAndSweep from the main README?

Well, markAndSweep isn't the default gc, so it makes sense to show both. But if you feel that it adds unnecessary clutter I wouldn't be opposed to just showing markAndSweep. You could also try the other GCs as well, as you can see from my graph the regions GC is potentially even better.

It makes sense that using objects vs. ref objects makes a bit of a difference. Objects are more or less the same as a struct, and will be allocated on the stack. This means that as soon as the calling proc returns the memory is freed, but it might end up costing you some memory copying if you're not careful. A ref object on the other hand is again like a struct, but this time allocated on the heap. These will live on until the garbage collector figures out that they are no longer in use and will free them. What you are seeing here is that the object I changed from ref to a simple object is only used to pass multiple return variables (we could also have used a tuple for this, or an array of static length 3). This means that all these object are no longer floating around on the heap waiting for garbage collection. If we turn off the garbage collector completely with --gc:none we can see that our memory consumption skyrockets to (on my machine) 41MiB as none of these are ever cleared. By simply changing them to use object instead of ref object, still compiling with --gc:none the memory consumption drops to 504 KiB. So it's not the garbage collector using more memory, it's just that we allocate a lot of memory on the heap by using ref object which then have to be GC'ed away. To learn more about how objects and references work in Nim you can read my post on it here.

We have just uncovered another pity bug in Nim benchmark implementation. Testing the resulting code again, the memory footprint jumped to 5MB using swapAndSweep GC. Could you, please, confirm that is the case?
Another question I couldn't find an answer to is how to enable LTO for Nim? We are going to enable it for all the languages.

@frol you should pass arguments to the C compiler with --passC and --passL (you can look on how to use them in the docs).

@frol, running it on my machine I only see a jump to 768KiB.. I'll investigate further and see if I can get it back down

@frol Can you also try with Nim devel? If you don't want to compile it manually you can use choosenim.

Ah yes, it turns out that I do in fact get 5MiB when using Nim 0.18.0, using the devel version drops it to 768KiB


Sorting Should Respect Newlines

I would like to enable Sort On Save but unfortunately there is a conflict when using Prettier.
Prettier wants long class attributes names' to be on separate lines but Windi will sort them back onto one line.
After saving it appears Windi's sorting is happening after Prettier leading to issues if you are also using ESLint with Prettier.

So one solution, if possible, could be to run the sorter before Prettier or other formatters.
However I think the better solution would be to respect the formatting when sorting class names.

I would like to work on this. Will make a PR soon.

v0.20.0


Removed VIM package (it isn't necessary)

But sometimes it can be useful

It is useful only for development. We will be able to do apt-get update && apt-get install vim if it is necessary.


grace period for dedicated node is not clear when you try to deploy on the node

Description
I have a dedicated node which is in grace period ,when i try to make a deployment on it i get that no space on disks instead of that the node contract is on grace period

Steps to reproduce
1-reserve a dedicated node
2- transfer all your tfts
3-wait for it to become in grace period
4-try to make deployment on the node

the deployment didn't even start so I think this is a connection issue which is handled here #1341.

Add more validation (in node_selector.vue) to check if rent contrat of node (node) is in grace_period ..

Work In Progress:

make checking grace period in UI while validating node.
so if node in grace period deploy button won't get enabled.

It looks like this pr causes an issue while deploying solution #2394
if (contractInfo.state.gracePeriod) I assume this is the issue

verified on devnet
version : a03d4ed

the error message is now clear
https://app.testlodge.com/a/26076/projects/40893/suites/234374?expand_section=430127#case_4260717


Fix for issue 10

The generalized_index_bit should ideally match the spec version. Because our version returned a 0 and the spec version returns a 1, I had to update the merkle proof left and right node as well.
Resolves: https://linear.app/snowfork/issue/SNO-637

Closing to create a new branch off tag oak-security-audit.


Address #5047 - Open global create when a user logs in for the first time

Details
When a user opens New Expensify for the first time, the Global Create Menu should open automatically.
Fixed Issues
$ https://github.com/Expensify/App/issues/5047
Tests
Ensure that menu opens for new users & existing users logging in for the first time since update

Sign in
Validate that menu opens
Refresh
Validate menu doesn't open

Ensure that menu doesn't open for existing users who the menu has already opened for

Sign in
Validate that menu doesn't open

QA Steps
Using a brand new account:

Sign in after signing up
Verify that the global create menu opens automatically

Using an existing account which hasn't seen the menu open automatically yet

Sign in
Verify that the global create menu opens automatically

Using the same existing account

Refresh the page
Verify that the global create menu doesn't open

Tested On

[x] Web
[ ] Mobile Web
[x] Desktop
[x] iOS
[ ] Android

Screenshots
Web
https://user-images.githubusercontent.com/39444813/132962018-0fb8c444-ce55-42f2-a960-62111d5f8e09.mov
Desktop
Attached is an example of the menu not opening for an existing user, but not it opening for a new user.
I can't see a way to test for a new user on desktop because I can't replace the address in Electron (meaning I can't create a new account & click the signup link to open the desktop app). If necessary, I could create a url bar in Electron, but that would take some extra work.
https://user-images.githubusercontent.com/39444813/132962175-90bbd66f-23ce-4195-b592-441fe7183201.mov
Mobile Web
https://user-images.githubusercontent.com/39444813/133081332-55502ff1-669f-4184-8608-7d22c3de60ae.mov
iOS
https://user-images.githubusercontent.com/39444813/133081362-c255d122-9e2c-4a6f-9309-1d6249b3aab2.mov
Android
Incoming - still getting my environment set up

Looks like there's a weird issue on iOS causing the menu not to open. Investigating now.

Here's a demonstration of the issue:
https://user-images.githubusercontent.com/39444813/133005281-d0be33dc-6a35-4c7d-bf18-37ad5c0d6194.mov
The menu opens when you refresh the simulator, but not when the app first loads (which will presumably happen in production).
But I think I've zeroed in on what's causing it.
This is the only PopoverMenu in the app that has an issue rendering on first load [on mobile] because it's the only one inside drawerContent:
<BaseDrawerNavigator
    drawerContent={() => <SidebarScreen />}
    screens={[
        {
            name: SCREENS.REPORT,
            component: ReportScreen,
            initialParams,
        },
    ]}
    isMainScreen
/>

When it gets passed directly as a screen, it has no issue rendering on first load
<BaseDrawerNavigator
    screens={[
        {
            name: SCREENS.REPORT,
            component: SidebarScreen,
            initialParams,
        },
    ]}
    isMainScreen
/>

https://user-images.githubusercontent.com/39444813/133005666-96438040-591f-455c-af7b-52d1364aacfe.mov
The only workaround I've found is to set a timeout in SidebarScreen.js's componentDidMount, which makes me think it's a race condition.
    componentDidMount() {
       ...

        setTimeout(() => {
            this.toggleCreateMenu()
        }, 200) // Setting the timeout to 0 seconds (i.e. waiting for the tick) doesn't work
    }

But obviously that's... not ideal.
Since it seems like the issue is with react-native-modal (note that using the standard react-native modal didn't help) inside @react-navigation/drawer, I don't think the root issue can be solved within this codebase. My suggestion - besides reopening the issue - would be to go with the non-ideal workaround (which could very well break on different devices) or only automatically open the menu on desktop/web. For what it's worth, it strikes me as nonstandard behavior on mobile anyway.

@mateomorris thanks for the investigation into the issues on mobile! If your temporary workaround (using setTimeout) works fine on all platforms now (I'll test in a minute), maybe we can move forward with your workaround and create a new issue for what you're reporting. I'll look into this a bit today too to see if I can get anywhere

3 more little linting errors (we're close!)

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @Beamanator in version: 1.0.97-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Just one idea that I haven't tested but to get around the setTimeout could we instead check for a change to the prop in componentDidUpdate like this?
SidebarScreen.propTypes = propTypes;
export default compose(
    withLocalize,
    withWindowDimensions,
    withOnyx({
        betas: {
            key: ONYXKEYS.BETAS,
        },
        isFirstTimeNewExpensifyUser: {
            key: ONYXKEYS.NVP_IS_FIRST_TIME_NEW_EXPENSIFY_USER,
            initWithStoredValues: false, // Ensure we always use the value from the server
        },
    }),
)(SidebarScreen);

Then have a defaultProp of false for this value. Which will allow us to check the the NVP in the server and then decide to open the menu like this:
componentDidUpdate(prevProps) {
    if (!prevProps.isFirstTimeNewExpensifyUser && this.props.isFirstTimeNewExpensifyUser) {
        this.toggleCreateMenu();
        NameValuePair.set(CONST.NVP.IS_FIRST_TIME_NEW_EXPENSIFY_USER, false, ONYXKEYS.NVP_IS_FIRST_TIME_NEW_EXPENSIFY_USER);
    }
}

This has been deployed to production and is now subject to a 7-day regression period.
If no regressions arise, payment will be issued on 2021-09-22.  :confetti_ball:

🚀 Deployed to production by @francoisl in version: 1.0.98-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Discussed with @marcaaron , I'm removing DeployBlockerCash as this fix is needed for n6. I'll make a new issue to get to the bottom of the weirdness experienced here so we can remove the need for setTimeout


Attempt to address Mouse latency issues on Netcast

See https://github.com/ConnectSDK/Connect-SDK-Android/issues/33

I've checked the Sampler 1.4.1 app with Netcast TVs 39LN5700-LN and 32LM6200-UE. The cursor movement is pretty smooth on both TVs and is compared with the official LG TV Remote app.


Generating CLI documentation

Fixes: https://github.com/python-wheel-build/fromager/issues/217
References:
https://sphinx-click.readthedocs.io/en/latest/examples/commands/
https://www.sphinx-doc.org/en/master/usage/quickstart.html
https://stackoverflow.com/questions/53668052/sphinx-cannot-find-my-python-files-says-no-module-named

It's a good idea and a good start. I have done the same for InstructLab a while ago,
Next steps:

move the click doc to a separate page, https://github.com/instructlab/instructlab/blob/main/docs/ilab.rst
configure the click extension, https://github.com/instructlab/instructlab/blob/main/docs/conf.py
create a requirements.txt in the docs folder, https://github.com/instructlab/instructlab/blob/main/docs/requirements.txt
create a tox target to build the docs: https://github.com/instructlab/instructlab/blob/main/tox.ini#L124-L134

I did first three steps but still I haven't been able to generate the documentation when I run make html
I also get a ModuleNotFound error that I mentioned above. I have pushed my latest attempt. Am I still missing something?

.. click:: fromager.__main__:main
  :prog: bootstrap
  :nested: full

Not sure whether :prog:  should be bootstrap since it looks like above. Any idea what it should be?

Not sure whether :prog:  should be bootstrap since it looks like above. Any idea what it should be?

prog should be the name of the script. In our case it is fromager.

Ah, okay! Changing that and adding readthedocs.yaml file as well

Let me know if any changes are required!

This looks good to me. @tiran had asked for a change, I'll wait for him to re-review before merging.

I have made the suggested changes!
Let me know if any more changes are required.
Also, @tiran is there any reason to leave a blank line at EOF for some files you mentioned above? Just curious about why do we do that.

Not sure why one check is getting cancelled only after squishing commits :(

I'm happy with this version. If we spot any other issues, let's plan to submit follow-ups after we have the doc publishing configured.

is there any reason to leave a blank line at EOF for some files you mentioned above? Just curious about why do we do that.

If we all configure our editors the same way it cuts down on spurious reformatting changes when we submit PRs. Having a blank line at the end of a file means if you cat it then it comes out with your command prompt on the next line instead of joined up with the last line of the file.


WinUI 3 sometimes doesn't render clearly

Describe the bug
WinUI 3 sometimes not renders texts clearly, when setting the Margin of TextBlock to some certain value.
Steps to reproduce the bug
<Page
    x:Class="WinUIAlphaTest.MainPage"
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    xmlns:local="using:WinUIAlphaTest"
    xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
    xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
    mc:Ignorable="d"
    Background="{ThemeResource ApplicationPageBackgroundThemeBrush}">
    <StackPanel Orientation="Vertical">
        <TextBlock>Margin = 0</TextBlock>
        <TextBlock Margin="1">Margin = 1</TextBlock>
        <TextBlock Margin="2">Margin = 2</TextBlock>
        <TextBlock Margin="3">Margin = 3</TextBlock>
        <TextBlock Margin="4">Margin = 4</TextBlock>
        <TextBlock Margin="5">Margin = 5</TextBlock>
        <TextBlock Margin="6">Margin = 6</TextBlock>
        <TextBlock Margin="7">Margin = 7</TextBlock>
        <TextBlock Margin="8">Margin = 8</TextBlock>
    </StackPanel>
</Page>

Expected behavior
The text should all be clear.
Screenshots

When Margin is 2 or 5, the texts are rather blurred.
For comparison, here is the render result of the traditional UWP:

(The title isn't well-named, ignore it.)
Version Info
NuGet package version:
Microsoft.WinUI 3.0.0-alpha.191101.0

Windows 10 version
Saw the problem?

Insider Build (19018)
Yes

Device form factor
Saw the problem?

Desktop
Yes

Additional context
The DPI of my screen is 90 (125%).

Probably related to #1441

Looks like text coordinates are not properly rounded.

I don't use winui 3 anymore. Anyone who faces this problem, feel free to reopen.


calendar component

in this pull request you will find

[x] changed the grcalendar to calendar
[x] a working demo that handles type ="date" and "datetime-local"
[ ] error handling and big changes to the calendar.py

closing this because i can't figure out how to fully integrate the calendar componenet as a gradio componenet.
these are interesting resources that might help :

https://svelte.dev/repl/77f694a1851d464b85b382f4f152cb8e
https://github.com/sveltejs/svelte/issues/3921
best of luck 🍀


set --enable-loadable-sqlite-extensions in configure?

It'll be nice if heroku could enable sqlite extension by default

Hi! To pre-empt what I imagine will be Kenneth's question... what's the use case for using sqlite extensions (or sqlite at all) on Heroku dynos? (Since the filesystem is ephemeral)

Sqlite:
We have a few readonly sqlite database stored in S3, they'll be fetched to dyno to be served as API.
Sqlite-extension:
Many mathematical functions, e.g log, expt are not available in sqlite, we'd like to load extension-functions.c

sqlite is very useful to have, as it’s a very fast database that can be used despite our ephemeral filesystem — it just can’t be used persistiently.
In addition to that, some tools/libraries, e.g. iPython, import sqlite, expecting it to be available as part of the stdlib, and will not function if it is not compiled at build time.
I don’t forsee changing our level of support here, though.

I just ran into the missing support for loadable extensions myself (I have a read-only sqlite DB and an extension for PCRE support).
I understand that this is not a common use case, but the change is trivial and I can't really think of any downsides (there's no extra dependency or anything). Would you be willing to reconsider?
My workaround for now is using a post_compile hook to re-build python with --enable-loadable-sqlite-extensions:
# rebuild python if it's missing loadable sqlite extensions
if  ! python3 -msysconfig | grep enable-loadable-sqlite-extensions \
    > /dev/null; then
  PYTHON_VERSION="$(< runtime.txt)"
  export WORKSPACE_DIR="$(cd "$BIN_DIR"/.. || exit; pwd)/builds"
  rm -f .heroku/python/bin/python   # prevent failing ln after build
  sed -i 's!figure --pre!figure --enable-loadable-sqlite-extensions --pre!' \
    "$WORKSPACE_DIR"/runtimes/python3
  "$WORKSPACE_DIR/runtimes/$PYTHON_VERSION" /app/.heroku/python/
fi

@obfusk Hi! I've reopened this issue to remind me to take a look when I get a chance to triage the issues in this repo (have been catching up with urgent fixes/tech debt first; hope to get to triage soon).

The official Python docker images use --enable-loadable-sqlite-extensions so I'd be inclined to copy them:
https://github.com/docker-library/python/pull/125

The official Python docker images use --enable-loadable-sqlite-extensions

So do Debian & Ubuntu and AFAIK most other Linux distros. Also Termux.

Tracking internally at W-8060029.

@obfusk hello I have same problem with you but what I want to add is --enable-shared
can you tell me how and where to add that post_compile hook scripts of yours?
thanks

@buncis https://github.com/obfusk/jiten/blob/master/bin/post_compile


valueMeta.setLength( kettleLength );
        valueMeta.setComments( label );
        rowMeta.addValueMeta( valueMeta );
      } catch ( Exception e ) {
        throw new SasReaderException( "Unable to create new value meta type", e );
      }
    }

    public boolean readData() {
      return false;
    }

    public boolean row( int rowNumber, Object[] rowData ) {
      return true;
    }
  } );
} catch ( Exception e ) {
  throw new KettleException( "Unable to determine the layout of SAS7BAT file '" + filename + "'", e );
}

}
@Override
public String toString() {
return filename;
}
/**

@return the filename
*/
public String getFilename() {
return filename;
}

/**

@return the rowMeta
*/
public RowMetaInterface getRowMeta() {
return rowMeta;
}
}` (at engine/src/main/java/org/pentaho/di/trans/steps/sasinput/SasInputHelper.java line 44)

↘ final String filename (at engine/src/main/java/org/pentaho/di/trans/steps/sasinput/SasInputHelper.java line 55)
↘ new File( filename ) (at engine/src/main/java/org/pentaho/di/trans/steps/sasinput/SasInputHelper.java line 58)

🐸 JFrog Frogbot

🐸 JFrog Frogbot

:x: Build failed in 3h 22m 7s
Build command:
mvn clean verify -B -e -Daudit -Djs.no.sandbox -pl ui

:ok_hand: All tests passed!
Tests run: 357, Failures: 0, Skipped: 0    Test Results

:information_source:  This is an automatic message


Swap out "externalRepresentation" stuff for separate ontology

I've been working on generalizing the external representation stuff into its own ontology here: https://github.com/gtfierro/ref-schema . I am also posting this to the 223P development repository as well. Ideally we all (REC, Brick, 223P, etc) are using the same ontology for these external references
Do we want to remove the Brick-specific relationships/definitions and replace them with this external schema? Or perhaps fold the ref-schema work into this repository, or have them extend the Brick namespace?

I'm happy with using a common vocabulary set instead of maintaining our own.


Form conformance committee

Committee formed with

@hblixt from Intuit
@wanghong230
@jannfis from Redhat
@todaywasawesome from Codefresh

See Argo Maintainer's meeting Sept 14, 2021.

Done.


Hotfix indicator order (prod)

FYI @etorem, i fixed some merge conflicts - not entirely sure what was happening but you may have edited a non up to date version of the .md file that lacked other recent changes, and it wasn't serving. Something to keep an eye on for next time - don't forget to pull a utd branch before committing. thanks!

[like]  Emily Torem reacted to your message:

From: M. Montesano @.>
Sent: Friday, June 28, 2024 5:03:02 PM
To: nychealth/EH-dataportal @.>
Cc: Emily Torem @.>; Mention @.>
Subject: [EXTERNAL] Re: [nychealth/EH-dataportal] Hotfix indicator order (prod) (PR #1057)
FYI @etoremhttps://github.com/etorem, i fixed some merge conflicts - not entirely sure what was happening but you may have edited a non up to date version of the .md file that lacked other recent changes, and it wasn't serving. Something to keep an eye on for next time - don't forget to pull a utd branch before committing. thanks!
—
Reply to this email directly, view it on GitHubhttps://github.com/nychealth/EH-dataportal/pull/1057#issuecomment-2197331355, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A54THZ26OLZ7RZF5ZJL3QGLZJWJMNAVCNFSM6AAAAABKCFNWSSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJXGMZTCMZVGU.
You are receiving this because you were mentioned.Message ID: @.***>
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.  Forward suspect email to<EMAIL_ADDRESS>as an attachment (Click the More button, then forward as attachment).
Sent from the New York City Department of Health & Mental Hygiene. This email and any files transmitted with it may contain confidential information and are intended solely for the use of the individual or entity to whom they are addressed. This footnote also confirms that this email message has been swept for the presence of computer viruses.


Cannot execute switch statement in a code cell

Entering the following code does not work.

char grade = 'B';

switch (grade) {
    case 'A':
        System.out.println("great job!");
        break;
    case 'B':
        System.out.println("good job!");
        break;
    case 'C':
        System.out.println("let's do better!");
        break;
    case 'D':
        System.out.println("need serious improvement!");
        break;
    default:
        System.out.println("ouch!");
}

The message output is as follows.

switch (grade) {
switch expressions are a preview feature and are disabled by default.
  (use --enable-preview to enable switch expressions)

The /usr/local/conda/share/jupyter/kernels/java/kernel.json file looks like the following.

{
    "argv": [
        "java",
        "-ea",
        "--enable-preview",
        "-jar",
        "/usr/local/conda/share/jupyter/kernels/java/ijava-1.3.0.jar",
        "{connection_file}"
    ],
    "display_name": "Java",
    "env": {},
    "interrupt_mode": "message",
    "language": "java"
}

The following are some environment information.

java -version
openjdk version "12.0.2" 2019-07-16
OpenJDK Runtime Environment (build 12.0.2+9-Ubuntu-119.04)
OpenJDK 64-Bit Server VM (build 12.0.2+9-Ubuntu-119.04, mixed mode)

conda --version
conda 4.7.12

python --version
Python 3.7.3

jupyter --version
jupyter core     : 4.5.0
jupyter-notebook : 6.0.0
qtconsole        : 4.5.1
ipython          : 7.6.1
ipykernel        : 5.1.1
jupyter client   : 5.3.1
jupyter lab      : 1.0.2
nbconvert        : 5.5.0
ipywidgets       : 7.5.0
nbformat         : 4.4.0
traitlets        : 4.3.2

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.04
DISTRIB_CODENAME=disco
DISTRIB_DESCRIPTION="Ubuntu 19.04"

Any ideas on how to get switch statements to work?

If anyone is interested, I had to set the environment variable as follows.

IJAVA_COMPILER_OPTS="--source 12 --enable-preview"

Note that when I set the environment as follows, I get an error complaining that --release cannot be used with --source. So, try not to --release.

IJAVA_COMPILER_OPTS="--release 12 --enable-preview"


Add an opt-in warning on missed events

Objective
Add an opt-in warning for events that get missed. Addresses #7089. Based on (and requires) #7086.
Solution
Add an associated const on the Event trait, which is set with an additional attribute macro. Only emit the warning of that associated const is true.
I believe this should have no performance impact for events that do not enable the warning, as the branch should be trivially optimized out.
Notes
Should this be inverted i.e. warn by default, add #[event(ignore_missed)]? Should the attribute be formatted in a different way? I did not add the warning to any engine events, although some should probably have them (AssetEvent comes to mind).
This implementation only allows for the warning to be enabled/disabled when the event is declared. Events sent by third-party plugins that are intended to be handled by the user are required to make a call on whether or an event must be handled, which can differ depending on the application.
I added the documentation for the attribute to Events, as that is where most of the documentation around events currently resides. Should this go on Event instead?

Changelog
Added
Users can add the #[event(warn_missed)] attribute to emit a warning if that event is not handled.

I like this quite a bit. A few nits, and this is blocked, but I think that this is a good strategy. I think we either:
a) need to show how to enable this only in debug mode
b) enable this by default for all events in debug mode and provide both opt-in and opt-out behavior
I prefer b), so you can debug third party events more easily.
We also need to benchmark this with the flag turned off (or compare the assembly) to verify there's no perf regression.

Backlog cleanup: closing due to inactivity and ongoing WIP status, but obviously could be adopted/re-opened. Noting that the dependent PR was merged, and a tracking issue (#7089) already exists.


build: simplify the SDK packaging step

The swift install rules now can distribute the auxiliary files which removes the dependency on the source tree.  Update the rules accordingly.

?

!

Please test with following PRs:
https://github.com/apple/swift-installer-scripts/pull/178
@swift-ci please build toolchain Windows platform

@swift-ci please smoke test

Please test with following PRs:
https://github.com/apple/swift-installer-scripts/pull/178
@swift-ci please build toolchain Windows platform

@swift-ci please smoke test

Please test with following PRs:
https://github.com/apple/swift-installer-scripts/pull/178
@swift-ci please build toolchain Windows platform

Please test with following PRs:
https://github.com/apple/swift-installer-scripts/pull/178
@swift-ci please build toolchain Windows platform


Sift with aggregated suffixes

Some fixes / slight improvements in small commits and the promised implementation of sifting.

Seems to work correctly on benchmark examples too.


Initial commit of jostler source code

The watchdir and uploadbundle packages in this initial commit are minimal in order to avoid burdening the code review process with a lot of code.  This commit compiles as is and once it is merged actual code the implement watchdir and uploadbundle will be added in similar steps.

This change is

Yes, the unit tests for packages will be added along with the full implementation of the packages.
I almost always include a test for the main package too and will do that after this PR is merged.

.golangci.yml line 8 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
I did not go through the disabled linters one by one to see what they do specifically, I trust you that these settings make sense :)

This file isn't really needed but I added it to the repo to make it convenient for collaborators to run golangci-lint run ./... to lint their changes.
Please note that some of the linters aren't really useful and force their author's style preference.  I've updated the file so it's more clear now what some linters are disabled.

main.go line 66 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Nit: The hostname format should be $machine-$site.$project.measurement-lab.org -- e.g. mlab4-abc0t.mlab-sandbox.measurement-lab.org

Corrected.

main.go line 90 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
What happens if a single watcher or bundleUploader goroutine fails? This comment makes me think that on any error all the goroutines would be terminated, is that what actually happens?

I updated the comment to be more clear.  I also successfully tested the case where multiple goroutines were running but had to terminate due to context cancelation.

main.go line 136 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
This func does a bit more than just validating -- it searches for a golden row file for the given datatype, checks that it's formally valid JSON, trims \n at the end and returns the file content as a string. Also, the function name implies that the first argument is the golden row (either as a path or as []byte), so I find datatype here a bit surprising.
Would you be willing to consider renaming it to something like goldenRowForDatatype(datatype string) (string, error) ? It can still return the golden row content as a string, or it could just return the golden row path (to be subsequently read/validated by another func), or it could return the content as a []byte (again, to be validated by another func)

You are right and goldenRowForDatatype is a much better name.
The motivation for returning string was that the golden row could be easily added to each bundle without requiring further validation, conversion, etc.  However, per my last meeting with Stephen and Cristina, handling golden row will be different so this function will change in a future PR.

main.go line 145 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
If I saw this error in the logs I would assume the golden row file isn't present on disk, not that its path hasn't been specified at all. Perhaps something like datatype %v has no corresponding golden row file?

The --golden-row flag is now optional and its default value is /var/spool/<experiment>/<datatype>/golden-row.json so the function and this error message are little different now.

main.go line 153 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Nit: It would help to also know what the unmarshalling error is (especially when testing/writing JSON by hand, knowing that I missed a , on line 83 is nice)

Unfortunately, json.Valid() does not return an error so I changed it to json.Unmarshal().  However, while the error says what went wrong, it does not include a line number.

main.go line 160 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Typo: "notifies"

Thanks for catching this.  I wonder why codespell caught other typos but not this one!

main.go line 161 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Typo: blank space after )

Done.

main.go line 166 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Nit: This will output failed to start directory watcher: failed to instantiate watcher: <actual error> -- what would you think of just returning nil, err here so the error message is only added once? The same reasoning applies to failed to instantiate uploader in startBundleUploader.

The intention of wrapping the error is to provide more context for what failed.  In this particular case, there is only one error (failed to instantiate watcher) so perhaps wrapping the error from the watchdir package does not add more useful information.  But if this function is extended in the future and can have multiple conditions that return error, it is recommended that errors be wrapped to provide more context.
If you are not strongly opposed to it, I suggest we leave it as is.

main.go line 180 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Typo: "starts"

Done.

main.go line 181 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Typo: Not sure if "into a (single) JSONL bundle"  or "into JSONL bundles" is what you meant here.

Updated the comment.

uploadbundle/uploadbundle.go line 3 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Typo: Cloud

Done.

uploadbundle/uploadbundle.go line 9 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Nit: I think you meant [a-zA-Z0-9\/:._-]+? (without the ^ or it would only match whitespace characters or similar)

I updated the comment to specifically mention the basename with this format: ^[a-zA-Z0-9][a-zA-Z0-9:._-]*.json

uploadbundle/uploadbundle.go line 61 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Typo: mostly

Thanks for catching all these typos.  I am puzzled why the spell checker tools catch some typos and miss others!!

watchdir/watchdir.go line 93 at r1 (raw file):
Previously, robertodauria (Roberto D'Auria) wrote…
Typo: possibly

Done.


API Access to patient DB

Hi
Can i have API access to patient data base like elasticsearch so that any one can do some analysis on patient  data and view them in dashboard like Kibana.
If you don't have the ES database, i can create one such DB in the cloud for any one to use. You just need to export the data from patient DB in the Google spreadsheets.
Regards

I am also looking for this. Can you please suggest how can I download the google sheets

https://api.covid19india.org/raw_data.json

I know with a python script the patient data from Google sheets can be read. Just curious about API access to patient DB in case it is available :}

Data from all the spreadsheets are not available like statewise_tested_numbers_data, case_time_series, district_list, statewise and likes :)

@DwijadasDey  The api repo has the links listed. https://github.com/covid19india/api

@DwijadasDey please do create an issue in https://github.com/covid19india/api if you need an API for a specific sheet. We will definitely look into it :)


4.5.0 release not available through npm/yarn

I'm not able to use the blendid 4.5.0 release in my package.json, because the registry is saying it doesn't exist. Any ideas?

Seems to be available now.


PDS shall log error and output streams when no result

Situation
It is very inconvenient, when a PDS server fails on script execution, an administrator cannot find the problem inside the logs but has always to fetch the PDS result/or failure from JobUUID.
Wanted
When no result file is available,

the first 1024 characters of  output stream and
the first 1024 characters of  error streams

shall be logged as errors

Here a "real world" output from the last commit
2021-06-30 18:33:35.752 ERROR 59528 --- [pool-2-thread-1] c.d.s.p.execution.PDSExecutionCallable   : job d5db1d75-711b-4ba6-be59-4273b01916f8 wrote no result file - here part of console log:
output stream:

error stream:
cp: cannot stat '/home/developer/projects/sechub/sechub-integrationtest/build/test-results/pds-runtime/workspace/d5db1d75-711b-4ba6-be59-4273b01916f8/upload/unzipped/sourcecode/returned_sarif_result.json': No such file or directory


Update contact phone number for group rates

New number for group rates. Make sure it shows up right. This is barely enough for a PR, but I haven't deployed this app before so I might need help with that part in particular.

LGTM. The deployment instructions are in the README.md. If you run into anything let us know. We can also deploy it for you if you need that.


feat: Implement handler of dgs for exception control

Pull Request Test Coverage Report for Build #151
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-2.7%) to 80.568%

Files with Coverage Reduction
New Missed Lines
%

../../../.gradle/daemon/8.4/util/src/main/kotlin/com/lomeone/util/exception/ExceptionAdvice.kt
1
10.53%

Totals

Change from base Build #149:
-2.7%

Covered Lines:
369

Relevant Lines:
458

💛  - Coveralls


setByValue: doesn't update to previous option

Current
when instantiating flounder with array options, as so:
var flounder = new Flounder($0,  {data:['a', 'b', 'c']});

and trying to reset the value programmatically as so:
flounder.setByValue('b');
flounder.setByValue('a');

the current selected value is not updated back to a (default 1st option).
Wanted
fix this bug

@mousemke thanks for the fix! the fix is quite important. when is the release schedualed which will include it?

are #69 and #71 clear? i'd love to get 0.7.0 out today

@mousemke sweat! will 0.7.0 have any breaking changes? i just checked out to 0.7.0. yes #69 and #70 look good!


Keycloak OIDC not supported

Release: wandb/local:0.58.1
I'm trying to configure a local instance of wandb to use Keycloak as an OIDC provider, but struggling to get it to work either through the web admin settings or by setting docker enviroment variables.
I believe it's because of the way keycloak uses 'realms' - so where most OIDC providers will use a URL of the schema https://{DOMAIN}/users/sign_in keycloak uses something like https://{DOMAIN}/realms/{REALM_NAME}/protocol/openid-connect/auth?client_id={CLIENT_ID}.
Other OIDC clients (e.g. Outline) allow more expressive docker environment variables which work with Keycloak, e.g:
OIDC_AUTH_URI=https://{DOMAIN}/realms/{REALM_NAME}/protocol/openid-connect/auth
OIDC_TOKEN_URI=https://{DOMAIN}/realms/{REALM_NAME}/protocol/openid-connect/token
OIDC_USERINFO_URI=https://{DOMAIN}/realms/{REALM_NAME}/protocol/openid-connect/userinfo

But if I try to set these for wandb, the gorilla service still tries to use the old url schema and panics as it does not exist:
{"level":"INFO","time":"2024-09-07T15:44:41.254942969Z","info":{"program":"gorilla","source":"github.com/wandb/core/services/gorilla/cmd/gorilla.go:1409","pid":1583},"data":{"dd.service":"gorilla","dd.version":"18d22e645275697ba614e1d1ea139452c4bed39f"},"message":"parsed schema","dd.trace_id":""}
panic: Get "https://{DOMAIN}/users/sign_in": stopped after 10 redirects

goroutine 1 [running]:
github.com/wandb/core/services/gorilla/cmd.(*gorillaCommander).MainCmd(0xc00188db00, {0xc00188dbe0, 0x1, 0x1})
        /home/circleci/go/src/github.com/wandb/core/services/gorilla/cmd/gorilla.go:1528 +0xccb6
main.main()
        /home/circleci/go/src/github.com/wandb/core/services/gorilla/cmd/megabinary/main.go:75 +0x431

Apologies if this is implemented and I am missing it in the docs, but am struggling to find anything.

Hi Bonnie,
Thanks for getting back to me - glad to see there are resources available
to help!
Sorry but I'm not seeing a link or any attachments here - could you please
resend?
Thanks,
Benjamin
On Mon, 9 Sept 2024 at 16:23, exalate-issue-sync[bot] <
@.***> wrote:

Bonnie Shen commented:
Hello Benjamin:
Thanks for writing to us! Here's some resource to configure Keycloak as
OIDC provider. Please give it a try and let us know if it works for you.
Best,
W&B
—
Reply to this email directly, view it on GitHub
https://github.com/wandb/server/issues/142#issuecomment-2338417750, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEPAENGZX3RSBUEFK4T5XGDZVW4NFAVCNFSM6AAAAABN2D73EWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZYGQYTONZVGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi @b-d-e !
It seemed like my link didn't get carried over from my backend. I'm attaching it here directly in the comment. Sorry for the inconvenience.

Is that a private repo? I'm getting 404.

I apologize, it is currently a private repo. Let me list the instructions here in the next comment. Your patience is greatly appreciated.

Keycloak Configuration

Create Keycloak ream

This is optional and you can use the master realm, but it's highly recommended to work with realms.

Create and Configure Client

:warning: Replace all the values with valid values for your organization.
Next step after create the realm, is setup the client, which is the configuration to be used by the application that will authenticate with Keycloak.
The client type myst be OpenID Connect

Create client

Configure the client

Keep the Standard flow and the Implicit flow enabled.

Set W&B URL's

For this configuration, the most important URL is the Valid redirect URLs.
This is the callback URL that Keycloak will call to send W&B the authentication token.

Configure OIDC Scope

When the client type OpenID Connect is created, Keycloak already set a default OIDC scope that contain all required claims. However, some Keycloak configuration may set different claims for OIDC scopes.
For W&B, one of the most important claims is the email, so regarldess the scop you will use, ensure the claims email and profileare set to Default

Enable PKCE

Still in the client configuration, navigate to the Advanced tab and click on Advanced Settings

Search for the drop down menu Proof key code exchange and select S256

Save the configuration.

Add user and/or groups

Now the next step is assign users and/or groups to the newly created realm to allow users authenticate using the also newly created wandb client.
W&B Configuration
The W&B configuration will depend on how did you installed the platform. For this guide, I will cover the configuration using the W&B helm chart and the configuration via W&B Operator console.

Helm Cart

As highlighted in the above link, you will need to add the Keycloak configuration according to the example below in the values.yaml you used to install W&B.
sso:
  enabled: true
  # Automatically provision a user if SSO auth succeeds
  autoProvision: true
  clientId: wandb
  issuer: http://keycloak.home.lab/realms/wandb/
  # Can be implicit or pkce
  method: pkce

Once the values.yaml is configured, apply the new configuration and test it.

Operator Console

Navigate to https://<WANDB FQDN>/console/settings/auth and input Keycloak data.

Login Screens
W&B Login

Login redirected to Keycloak for Authentication

In case the Keycloak user is also new, it may need to change the password depending how Keycloak is configured

After SSO authentication, user is created in W&B

Login is complete

Hi Bonnie. I have had a quick look (on docker, not with helm), though was hitting another issue - but I think that might be an networking issue my end.
Do you have a comprehensive list of the environment variables a docker instance ofwandb/local takes? There's this list, but that isn't exhaustive (e.g. there's some GORILLA vars that aren't in there)

Hi Benjamin! Does this one help?


Add other corrections

[x] Add JMS/JMR only for signal for now
[x] Add QCDscale/PDF copying over old code
[x] Add JECs for VBFFatJets and bbFatJets
[x] Tested locally

LGTM


[v9RC1] Install/Update Languages hangs site

Clicking on Install/Update Languages in System & Settings > Basics > Languages either shows a totally blank page without menus or anything or after several clicks (go back and click) the page is continuously waiting for something without end hanging the whole site - clicking on any links is not responding, the whole site hangs, even Ctrl-F5 doesn't help. The site is no longer accessible. Even restart of Apache doesn't help. The site is stuffed.

Hmm. This is not my experience. Can anyone else replicate this?
FYI: you will need to ensure you're running PHP 7.3 if perhaps that's an issue you're encountering.

n/m my previous comment (now deleted); I didn't read closely enough.

This should be fixed by https://github.com/concrete5/concrete5/pull/9664
There is a separate issue of languages not being returned properly for version 9 from the translation repository; I'm not sure why this is the case. I'll create a separate issue for this.


NOISSUE - Fix Auth Config

Pull request title should be MG-XXX - description or NOISSUE - description where XXX is ID of issue that this PR relate to.
Please review the CONTRIBUTING.md file for detailed contributing guidelines.
What does this do?
Which issue(s) does this PR fix/relate to?
Put here Resolves #XXX to auto-close the issue that your PR fixes (if such)
List any changes that modify/break current functionality
Have you included tests for your changes?
Did you document any new/modified functionality?
Notes

Current dependencies on/for this PR:

main

PR #4   👈

This stack of pull requests is managed by Graphite.


reading in data to SPIAT

Hi. Thanks for your work on the SPIAT package. I have data from a spatial proteomics experiment in the format shown below, which just contains x-y co-ordinates, intensity and mz values.
What function should I use to read this into a SPIAT object? I was trying one of the "format_" functions but did not have any luck. I was also trying to maybe read the data into an SPE object and convert from there to a SPIAT object?

Thanks

Hi @cathalgking,
Thank you for your interest in the tool and I apologise for the delayed response.
SPIAT uses SPE object as the base object to do all operations and calculations of the images. Please try function format_image_to_spe() and use the argument method = "general". Please refer to the tutorial here for guidance.
Yuzhou

@fuerzhou
I just tried this but it does not seem to have the method argument in that function. Did you mean the format argument? When I try format = "general" it gives an Error which is:
Error in data.frame(Cell.ID = Cell_IDs, Phenotype = phenotypes, Cell.X.Position = coord_x,  :
  arguments imply differing number of rows: 6, 0

Do you know how best to read in this data?

Yes sorry the argument should be format. Could you send me your code on formatting the image?

@fuerzhou
The code I run is:
spiat <- format_image_to_spe(intensity_matrix = AR_kd_full, format = "general")

And the file I am trying to read in is a data frame which looks like:

To use this function, you need to follow the instructions in the documentation -
#' @ param format String specifying the format of the data source. Default is
#'   "general" (RECOMMENDED), where the cell phenotypes, coordinates and marker
#'   intensities are imported manually by the user. Other formats include
#'   "inForm", "HALO", "cellprofiler" and "CODEX".
#' @ param intensity_matrix (Optional) For "general" format. A matrix of marker
#'   intensities or gene expression where the column names are the Cell IDs, and
#'   the rownames the marker.
#' @ param phenotypes (Optional) For "general" format. String Vector of cell
#'   phenotypes in the same order in which they appear in intensity_matrix. If
#'   no phenotypes available, then a vector of NAs can be used as input. Note
#'   that the combination of markers (e.g. CD3,CD4) needs to be used instead of
#'   the cell type name (e.g. helper T cells).
#' @ param coord_x (Optional) For "general" format. Numeric Vector with the X
#'   coordinates of the cells. The cells must be in the same order as in the
#'   intensity_matrix.
#' @ param coord_y (Optional) For "general" format. Numeric Vector with the Y
#'   coordinates of the cells. The cells must be in the same order as in the
#'   intensity_matrix.
It seems that you put the x,y coordinates, intensities all in the same data frame. Instead, you need to specify each argument separately.


Workshops Of Doom Failed to Load Correctly

Hello! Can you please help me, I am not sure if I can fix it on my end or not.
Minecraft: 1.18.2
Java: 17
Forge Installer: 1.18.2-forge-40.2.0
Mod: workshopsofdoom-1.18.1-<IP_ADDRESS>
CP:  Windows 11 Home
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz 2.90 GHz
Installed RAM: 32.0 GB (31.9 GB usable)
System type: 64-bit operating system, x64-based processor
crash-2023-04-16_16.18.21-fml.txt

I never updated the mod to 1.18.2, it doesn't work on 1.18.2

I never updated the mod to 1.18.2, it doesn't work on 1.18.2

T^T PLEASEEEEEEEEEEEEEEEEEEEEE make it for 18.2..... don't forsake me....


Register domain UUID

Added the feature requested in #5350

User request

Tested locally, unit test

Register domain functionality can stop working

RegisterDomainRequest schema changed

Documentation Changes

The corresponding issue is closed as it turns out this is not a need. Closing the PR.


Generating SECRET

Can anyone provide me assistance in generating the secret for password for authentication in the dashboard and api. I have tried a few times without success.

@coreyjansen you had any advance in this issue? i think you have the same problem than me https://github.com/SamyPesse/betty/issues/26

I believe that am with both of you. I cannot find what the default username is suppose to be. I do get some residual effect from entering in my password. It acts as if it starts to load the page, then reopens the login prompt.
Are we suppose to be using our twilio account login credentials on this or something else?
I believe that exporting the 'secret' is working but as for what the username should be I am clueless. #26


Ensure subscriber can detect and re-download updated granules based on collection redeliveries

Update CMR query to use updated_since rather than created_at in the CMR query:
    params = {
        'scroll': "true",
        'page_size': 2000,
        'sort_key': "-start_date",
        'provider': 'POCLOUD',
        'ShortName': short_name,
        'created_at': data_within_last_timestamp,
        'token': token,
        'bounding_box': bounding_extent,
    }

here:
https://github.com/podaac/data-subscriber/blob/main/subscriber/podaac_data_subscriber.py#L298
as well as here:
https://github.com/podaac/data-subscriber/blob/main/subscriber/podaac_data_subscriber.py#L310

The only real issue with this change would be:

A user consistently using the subscriber and used the original data will not be able to "reproduce" that result since the underlying data has changed.
A user only needs "NRT" data and doesn't care if that data is updated later on. In this instance, they will downlaod data they don't need.

2 is one we can work on and add an additional (that's a lot of words starting with 'A') parameter in future work to specify updated_at vs created_at. I don't think that's in scope for this change, to be honest, and we should only add it if we get requests to do so.
1 is an issue with the data provider replacing these files. If it's simple replacement/metadata then this is fine. but there are times when a provider will send a "quicklook" file and then a better version days later, but uses the same filename and replaces the existing data.
tl,dr;
Go ahead with the fix and we'll respond to user requests to add a flag if desired to differentiate updated vs created times.

Good points.  I can definitely see a future flag for static downloads vs continuous updating being useful to certain users.
I will move forward with this change for the time being.


Implement authentication

Supports authentication via one of the followings:

plain text, e.g. plain username & password
decrypt kms password
get username & password from s3 slips

Yay, I paired with henry on this, so I'll merge straight away :)


the orionsdk pypi package is at version 0.0.6 and more than 1 year out of date on pypi.org

... but the documentation on the github age applies to version 0.0.8. if one installs the sdk via pip (as documented) and then one tries to use the exposed session object, one gets an exception.

This is getting to be problematic. Please address soon, if possible.
Willing to help should you want it.

In the mean time, put the below line into your requirements.txt file and pip will install the most recent version. At least it did for me. I make no guarantees about this.
git+https://github.com/solarwinds/orionsdk-python

one must be careful if one uses this trick because when 'freezing' the
environment back to requirements.txt, the version of the installed package
is saved and the git+https line will be lost.
On Fri, May 10, 2019 at 2:44 PM atxviking<EMAIL_ADDRESS>wrote:

In the mean time, put the below line into your requirements.txt file and
pip will install the most recent version. At least it did for me. I make no
guarantees about this.
git+https://github.com/solarwinds/orionsdk-python
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/solarwinds/orionsdk-python/issues/31#issuecomment-491439086,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANTBTC6S3SGSJGWPKWF3N3PUXUEHANCNFSM4GYY5N2A
.

I got bit also by the pypi version being old and things not working because I was reading the docs from github. bump :)

Version 0.1.0 is now available at https://pypi.org/project/orionsdk/.

Thank you!


Detect type inconsistencies

Instances of some types, like atomic.Value, container.* and sync.Pool should be passed always the same type for their interface{} values.
This sounds like something that might be easily checked.
Extra points for checking the type assertion on the getters.
(BTW, love the tool, thanks for all this work!)

Not a trivial check, and of somewhat limited use in local analysis, and we're not currently doing whole program analysis. I'll check how feasible a limited implementation of it is.

Even with points-to analysis as implemented by go/pointer, this isn't doable without risking false positives (and a fair amount of false negatives, without which we'd have even more false positives).
Let's address the false negatives first: When we get a points-to set (in our case for the method receivers in the Put calls), it has to include at least all pointees that are possible during execution. However, it may also include pointees that are not possible, for a number of reasons (flow-insensitivity, context-insensitivity, and in general the fact that it's not generally possible to compute the exact set, see Rice's theorem). We can work around this by only considering singletons: if we know that the pointer refers to at most one instance of a sync.Pool, and two different types are put into it, it's a violation.
That, however, brings us to the false positive: while we do have a context-sensitive heap, multiple pools can be created with the exact same context, for example by storing multiple pools in a slice in a loop. That way, all pools in the slice will be treated as a single pool, so we could see conflicting types in "the" pool even though they're separate pools. And of course somewhere deep down the stack, we'll have no idea where the pools came from (a slice), only that they all seem to be the same one.
Admittedly, allocating and storing pools that way seems bizarre and won't (shouldn't!) happen a lot in practice, so it might be worth adding the check and benchmarking its false positive rate.
However, since our PTA is in general context-insensitive, many pools being passed to a single function would instantly result in a false negative in case of misuse. Just like before, passing around pools might not happen all that often, as they should ideally be package-level variables and be referenced directly. So maybe this isn't a concern, either.
As I am writing this comment, it becomes apparent that this is at least worth an experiment.


Adafruit Feather ESP32-S3 panik resets in the Scan Continuous example.

Hey :) great library! It works beautifully on an Arduino ESP32 for me and I am trying to port the code to the Adafruit Feather ESP32-S3 Reverse TFT now so I can have a display. While doing so I am getting panik resets. I have narrowed this down to the following line in the Scan Continuous example:
  BLEScanResults foundDevices = pBLEScan->start(scanTime, false);

The example code I am using:
#include <NimBLEDevice.h>

int scanTime = 5; //In seconds
BLEScan* pBLEScan;

class MyAdvertisedDeviceCallbacks: public BLEAdvertisedDeviceCallbacks {
  /*** Only a reference to the advertised device is passed now
    void onResult(BLEAdvertisedDevice advertisedDevice) { **/
    void onResult(BLEAdvertisedDevice* advertisedDevice) {
  /** Serial.printf("Advertised Device: %s \n", advertisedDevice.toString().c_str()); **/
      Serial.printf("Advertised Device: %s \n", advertisedDevice->toString().c_str());
    }
};

void setup() {
  Serial.begin(115200);
  Serial.println("Scanning...");

  BLEDevice::init("");
  pBLEScan = BLEDevice::getScan(); //create new scan
  pBLEScan->setAdvertisedDeviceCallbacks(new MyAdvertisedDeviceCallbacks());
  pBLEScan->setActiveScan(true); //active scan uses more power, but get results faster
  pBLEScan->setInterval(100);
  pBLEScan->setWindow(99);  // less or equal setInterval value
}

void loop() {
  // put your main code here, to run repeatedly:
  BLEScanResults foundDevices = pBLEScan->start(scanTime, false);
  Serial.print("Devices found: ");
  Serial.println(foundDevices.getCount());
  Serial.println("Scan done!");
  pBLEScan->clearResults();   // delete results fromBLEScan buffer to release memory
  delay(2000);
}

I checked that the pBLEScan pointer is not a nullptr. If I comment out the offending line the code runs fine (but doesnt do any scanning of course). The code works fine on my other ESP32 from Arduino.
Any idea what might be going wrong or how to debug it?

Could you provide a debug log and or backtrace?

Closing this as there has been no response, please re-open if still having this issue.


Bug fix for have_failed with RSpec 3.0.0

With Mr. Weirich sadly no longer with us, I don't know who if anyone wil be maintaing this, but I figure I may as well at least post the issue/PR in case anybody else comes across the same issue.
With the release of RSpec 3.0.0, the have_failed mechanism no longer works.  Attempting:
  When(:result) { stack.pop }
  Then { expect(result).to have_failed(UnderflowError, /empty/) }

Results in an error like:
 Failure/Error: Then { expect(credentials).to have_failed UnderflowError }
    expected UnderFlowError but was not given a block

This PR should fix that.
(The specific RSpec change that caused this to break was rspec/rspec-expections@79582c2, which cleaned up the delineation between blocks and values for expect { } vs expect() as per rspec/rspec-expectations#526 ; unfortunately rspec-given was relying on the previous looseness to be able to use a value that quacked like a Proc.)

Hey ronen — I'm going to take a look at this branch today. Do you think it's ready to merge into rspec-given's new repo? https://github.com/rspec-given/rspec-given

hey justin -- glad to see you've taken on this gem!

Do you think it's ready to merge into rspec-given's new repo? https://github.com/rspec-given/rspec-given

hmm....  no idea...   i haven't thought about this issue or looked at any of the repos since i submitted the PR...

No worries. Fortunately there were tests broken by your issue and this patch fixes several of them. I'm digging into it now and I think I understand the RSpec API change that caused the issue. I've already merged your patch into my PR and you'll get the credit :D

Cool, glad you're on top of it.


Support UnboundMethod objects.

This code snippet does not work right now:
class X
    def bar
        1 + 2
    end
end

X.instance_method(:bar).to_source

Hey @matthias-springer , thanks for the PR, but i'm reluctant to merge it cos i'm no longer supporting this project... sorry.


Add @awslabs/smithy-rs-server as owners to codegen-core

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I don't think there is a way to do a logical and. I think we would need to write a GitHub Action to enforce reviews from both groups on codegen-core.

Perhaps adding two lines with the same directory, each scoped to different teams?

I don't think that's a feature. As far as I can tell, GitHub doesn't support any mechanism for requiring two groups to approve.

We could also create a separate GitHub team containing the union of both teams.

This would be equivalent to listing the two teams on the folder in CODEOWNERS. Only one person from the larger group would have to approve.

Ah yeah you're right.
🤷 I guess this is the best we can do unless we write a GitHub action.
Can you also address https://github.com/awslabs/smithy-rs/pull/1737#issuecomment-1248518829 (allowing @awslabs/smithy-rs-server to approve on changes to shared directories like buildSrc, design, tools).


Increase distance of effects affecting the player

Hi Theis,
I have been wondering if it would be possible to get stone path to increase the players speed when the player is 0.1 tiles away from the stone path. The reason for this is that it can be super frustrating to get the character to walk on the stone path between buildings. This is one of those annoying "I just need to spend enough time on it" things (like RNG with huge rocks), so it would be really nice if the stone path area of effect (or the characters "affected by effects" area) could be increase by 0.1, so it doesn't matter where between buildings the character is placed.
I have had a look at the documentation, but I cannot seem to find any obvious field which could be changed.

I am afraid not. It seems that the characters position only ever evaluates to 1 tile.
It is of course possible by uses mimic'ing. By setting the speedboost of the tile prototype to 0 and then check every tick if the player is on or near a tile and set the speedboost using character_running_speed_modifier.

That could be the way to go and i guess that is also the way Factorio does it. Thanks for your input. :)


Cleanup way page template filenames are generated

This pull request cleans up the way Wagtail generates default template filenames and assigns them to pages.
All the logic has been moved into methods which are easy to override with custom behaviour. Methods are also simpler to grasp than metaclasses which should make it easier for developers to debug.

Closed in favour of #1730


Bluetooth: ISO: Broadcast Code minimum length

Is your enhancement proposal related to a problem? Please describe.
Core spec 5.4, Vol 3, Part C, section <IP_ADDRESS> states:

On the UI level, the Broadcast Code parameter shall be represented as a string
of at least 4 octets

To ensure such a requirement, the overall requirement for a broadcast code in Zephyr should also be a minimum of 4 octets. Furthermore, we may want to ensure that the broadcast code is valid UTF-8.
Describe the solution you'd like
Add a minimum length of the broadcast code where applicable, and reject where it can be rejected.
Furthermore, consider an UTF-8 validation function that ensures that the Broadcast Code supplied can be represented as a printable UTF-8 string.
Describe alternatives you've considered
N/A
Additional context
This both affects ISO and Audio (BAP)
Some shell commands may need to be updated as well to only work as strings

Since we do not supply the broadcast code length, and since any value (including all zeroes) can be represented as a string value, this is not something we can enforce in the stack.


Update style

heyy @Aum8 I want to add some style. please assign this issue to me.

Style file not link properly.

Thanks for pointing it out!
I have assigned you the issue, feel free to give any suggestions.


feat: move schematic to package dependencies to simplify ng-add

Proposed change
move @o3r/schematic package to packages dependencies to simplify ng-add and supporting it outside of Otter project.

Related issues

- No issue associated -

Temporary closed due to the large amount of dependencies bring by it


error: Segmentation fault: 11

Hi,
I need help about "error: Segmentation fault: 11" compiler issue.
When I add below code to my viewController, getting that error:
googleButton.rx.tap.bind{ [weak self] _ in
    guard let strongSelf = self else {return}
    RRGoogleLogin.shared.googleSignIn(viewController: strongSelf)
}.disposed(by: rxbag)

I have checked the error and it is known XCode bug but couldn't find the solution.
Please let me know if you have any idea.
Thanks!

I have checked sample code and its working perfectly. Not found any compiler error. Please refer the sample code...

So sorry @Rahul-Mayani, I found the reason. My googlebutton was not UIButton, it's type was GoogleSignInButton. Closing the bug, thanks.


updates

I can't understand why you changed " to ' and added space in default parameters if type-hint is there.
Can you undo the changes in doc-strings about renaming "anekos" to "nekos"?

it was my formatter that i use (blue)

I can't understand why you changed " to ' and added space in default parameters if type-hint is there.


Update playlist images to be optional.

The Playlist API just started returning a null image array (instead of an empty array as the documentation suggests and the code assumes). This change prevents the JSONDecoder from crashing when decoding such playlists.

Change the code to decode a value of null into an empty array. This will avoid breaking API compatibility.

Please try d2eb1f3.

Implemented in version 3.0.1.


Create a API that returns the current version.

Should this be extended to be a more general metadata endpoint? Other things that you might want for similar reasons:

node version
mongo version
node_env
uptime (for davis, host, or both)

I'm sure there would be other things as well

Makes sense to include additional information.  Perhaps we should also add:

up to date boolean
last version available (probably on NPM)

0c26873

Oops just closed the wrong one

@beeme1mr how does /api/v1/system/meta sound as an endpoint? I'm torn between meta and info

also should this be restricted to admin users?

@dyladan Yes, admin only and I prefer info.

b23dc92


Initial plugin skeleton

We can move functionality from j2objc.gradle into J2objcPlugin.groovy as we are able to.
Skeleton for empty Gradle plugin build
- Empty Groovy class for plugin.
- Standard Gradle build wrapper

For now we use com.github.brunobowden.j2objcgradle as our root package (i.e. group).

Starts issue #55

ptal

LGTM

I gave an LGTM in person


Table/style

Issue: for now, there is no clean way to give the title to the column with lower case first letter, like vCPU for instance.
Solution: Removed the uppercase transform for the first letter of the header cell. The property is uncontrollable and when removed can be easily reproduced in more controllable way with the text itself.

May be we can do it via option, like capitalizeHeading?

Oh, this is for next major, ok


Failures on [cfe] Add ClassMember.memberKind and .getTearOff

There are new test failures on [cfe] Add ClassMember.memberKind and .getTearOff.
The tests
co19/LanguageFeatures/Extension-types/superinterfaces_of_extension_type_A05_t07 CompileTimeError (expected Pass)

are failing on configurations
cfe-strong-linux
cfe-weak-linux
dart2wasm-linux-chrome
dart2wasm-linux-d8
vm-mac-debug-arm64
vm-mac-release-arm64

@eernstg Do we have any specification on whether/when we should report errors on property/method and getter/setter conflicts in extension types? I can't seem to guess what co19 expects.

The test co19/LanguageFeatures/Extension-types/superinterfaces_of_extension_type_A05_t07 should be updated, because it expects no errors in a situation where there is a setter/getter signature conflict (and they should be reported here, just as they are reported for classes etc.).
This test is presumably intended to verify that there is no constraint like the override correctness that we enforce with class member override relations. In particular, it's OK to redeclare a getter (in this case: an implicitly induced external getter) as a method.
It looks like the setter/getter signature conflict is an accident, and in that case the test could just use external final int id2; to avoid introducing the setter in the first place.

I created a co19 issue here: https://github.com/dart-lang/co19/issues/2335.

The test has now been updated and matches our expectations.


Fix wrong return value in map_graph()

There is a mismatch between the declared and actual return values for the map_graph() function located in /ops/function.py.
Currently, map_graph() returns:

network_nodes
nodes_by_depth
operations
operations_by_depth

However, both the Function.__init__ and the  map_graph() docstring indicate that it should return:

nodes
nodes_by_depth
operations
operations_by_depth

network_nodes appears to be an internal temporary variable not used outside of map_graph(), while nodes is required as a key property of the Function class.
To resolve this discrepancy, we should either:

Modify the function's output to match its documentation and  Function.__init__, or
Update the documentation and Function.__init__ to be consistent with the function's current behavior.

I'm leaning towards adjusting the function's return value. If that's not feasible, I'll submit another PR to update the docstring and Function.__init__.
I would appreciate any feedback or suggestions on this matter. Thank you.

Thanks for the PR. Currently, tests are failing. The original code appears to be correct. Perhaps you can just update the docstrings to indicate that the function returns not a list, but a dict.


Unexpected view jump when selecting bytes

I have a large binary blob that I want to select a lot of bytes from (on the order of several megabytes). To do this, I would like to:

Click the start address (or end address)
Scroll to the end (or start)
Press Shift
Click the appropriate address

However, pressing Shift snaps the view back to the original address I selected.
If I change the order to the following it works:

Click the start address (or end address)
Press Shift
Scroll to the end (or start)
Click the appropriate address

But it's kind of annoying to have to hold Shift down while I try to find the end of what I'm looking at. It would be nice if pressing shift didn't reset the view.

Fixed in build 2249


Migrate to Xcode 8 beta 6

@duemunk
Most changes are due to https://github.com/apple/swift-evolution/blob/master/proposals/0103-make-noescape-default.md

Thanks!


GET endpoints by endpointIds not works.

Bug description
API: GET /api/endpoints
QueryString:  endpointIds=11&endpointIds=14&start=0&limit=2
The Portainer server has returned two objects, but they do not match the ids specified in the query string. The filter not worked at all.
Expected behavior
only return specified ids in string

Portainer version: 2.18.1

Oh, I found the reason. Query string should be endpointIds[]=11&endpointIds[]=14


Fix hibernate-core compilation error on wip/6.0

the existing 'antlr( libraries.antlr )' is only meant for generating antlr sources. We still need to add compile dependency to ensure the compiling of the generated antlr sources succeed.

really strange, compile( libraries.antlr ) is already present at line 59 https://github.com/hibernate/hibernate-orm/pull/3215/files#diff-197d2841569f03ef77fff9b387e93425L59

really strange, compile( libraries.antlr ) is already present at line 59 https://github.com/hibernate/hibernate-orm/pull/3215/files#diff-197d2841569f03ef77fff9b387e93425L59

Thanks. It must be my error. PR closed.


fix: Cilium CLI version

Reason for Change:

Unblocks the PR pipeline as Cilium CLI update v0.15.11 -> v0.15.12 brought in new tests for features we may or may not support.
Issue Fixed:

Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[x] relevant PR labels added

Notes:
https://github.com/cilium/cilium-cli/releases/tag/v0.15.12
https://github.com/cilium/cilium-cli/compare/v0.15.11...v0.15.12

We can parameterize it in a follow on PR, but I want to lean on the original implementation.
For the parameterization I will have it be able to consume any version that is provided and on empty use the original implementation of consuming the current stable release of Cilium CLI.
Should we look into skipping these tests? The test infra itself is rather robust, so I think we should look more into the root cause of missing feature flags ect, instead of just skipping... https://github.com/cilium/cilium-cli/blob/6948dd10b838a883c985a4b1f5a40daa68db00bf/connectivity/suite.go#L755-L759


add Instagram.shareAsset feature

based on this article http://blog.horizon.camera/post/102273431070/video-share-objc-ios-instagram feature for sharing video to instagram on ios

Thanks for the PR!
Can you share an example of the asset url? It might be possible to keep the JavaScript API simpler by adding the option to share the asset url with the current share method.

sorry I can't, I hope someone can catch this "asset url" by using UISaveVideoAtPathToSavedPhotosAlbum in debug break point variables inspector

Hello there, please read this http://stackoverflow.com/questions/34226433/instagram-hooks-pre-select-media-issue
If anyone can update code to work with new method based on instagram://library?LocalIdentifier=(localID) url, please help with it.
Add this code http://stackoverflow.com/a/36019299 for converting urls, change url parameter "AssetPath" to new "LocalIdentifier" and this must work

Hello again, I update code and test it, everything is working well, based on PHAsset LocalIdentifier

Thanks for updating the PR.
The question now is that if this adds a new method we could separate the canvas case from the other cases in which the input is an URL, and make the new method work for both iOS and Android. Each case would be handled based on the URI scheme.

This new method work for both image and video, only if you have PHAsset LocalIdentifier and only in iOS 8+, also this feature undocumented, because of that I don't see any reason for

separate the canvas case

and

make the new method work for both iOS and Android

Just add as new method, because in any moment Instagram can change behaviour for this feature


Use find latest in etl compare

The tool compare etl-catalog currently is only able to compare a local dataset with the same version of the same dataset in the remote catalog. However, often a user has fixed a small issue in one country/variable/year, creates a new fixed dataset, and wants to ensure that, with respect to the previous dataset remote version, only that specific country/variable/year has changed, and nothing else.
This PR uses find_latest instead of find_one in compare etl-catalog so that a user can compare a new version of a dataset with its previous version in the remote catalog. However, if a user wants to compare a specific version (and not the latest), the optional argument --version can also be used.
Caveat: A user may not be aware that they are comparing different versions of a dataset. It would be good to print "Comparing local version XXXX-XX-XX with remote version YYYY-YY-YY".
Ideally, the tool should let the user compare two arbitrary local and remote datasets. For example, you may want to compare datasets of different channels (e.g. what's the difference between garden and meadow?). But for now, this PR already provides some value.

Lookgs good to me!
The only thing I would slightly change is the description of the command (docstring under cli function). That's the description that the user gets if they type compare --help.
I think that it is not generic enough, as it specifically talks about "dataframes".

Good point. I have changed it a bit, to be shorter and more generic. The previous docstring was actually pretty much the same as that for dataframes only.


Can't run game with Live Scan

Map: Download, GDrive
To play/host this map (the access denied is not related, I think at least, but in case you want to play/test the map) you need 1.27 wc3
WC3: Download, GDrive
Run the Launch.bat or launch-windowed.bat file

Hi, thanks for the report.
It will probably tied to your specific setup, so it needs to be diagnosed on your PC.
Could you run Process Monitor on MPQEditor.exe and see what exactly was denied?

Hi, thanks for the report. It will probably tied to your specific setup, so it needs to be diagnosed on your PC. Could you run Process Monitor on MPQEditor.exe and see what exactly was denied?

Sure! I'm not familiar with the tool, so I will go test it. If you want to communicate through Discord I can do that too, but give me a moment, I will install Process Monitor and check

Hello, we can go discord. Can you e-mail me your discord name?

Hello, we can go discord.  Try to add me as ladikthegrey.

Cant see it in any of my mailboxes. Try to add me as ladikthegrey.

Weird, I added you again

Fixed


Update the upsert api to handle multiple columns as unique index

We want the api to look like this:
apiVersion: 0.1.0
meta:
  version: 0.3.1
  name: json-sql-connector
  type: sql-sink
  topic: sql-topic
  create-topic: true
  secrets:
    - name: DATABASE_URL
sql:
  url: ${{ secrets.DATABASE_URL }}
transforms:
  - uses: infinyon/json-sql
    with:
      mapping:
        operation: "upsert"
        table: "topic_message"
        unique-columns:
          - device_id
          - user_id
        map-columns:
          "device_id":
            json-key: "device.device_id"
            value:
              type: "int"
              default: "0"
              required: true
          "record":
            json-key: "$"
            value:
              type: "jsonb"
              required: true

@galibey maybe we can find a better name for unique-columns? since the combination of them should be unique and they don't need to be unique individually.

@ozgrakkurt I like parallel keywords, and since we already have map-columns, unique_columns makes sense.

implemented in https://github.com/infinyon/sql-connector/pull/74 but the implementation is hacky, need to update fluvio-model-sql and sql-sink to handle it as array instead of single variable named uniq_idx and add actual tests, and update docs

opened follow-up issue here:  https://github.com/infinyon/sql-connector/issues/79


Added header case sensitivity and removed deprecated parameter

Added a case_sensitive field and defaulted it to False to avoid annoying conflicts between the csv files' headers and the model field names. I believe there aren't many good reasons as to why you would need case sensitivity.
Also removed the 'U' parameter passed when opening the csv file as is it deprecated according to the documentation and replaced it with 'newline=None' for Universal Newlines.
Please bare with me as this is my first ever contribution to OSS and my first ever attempt at Git. I realize these features need to be tested. I will do so, however I'm taking baby steps here.

Ok the first two commits are dumb. I didn't know how to roll back or remove them. Sorry, I'm new to this.

No sweat. Nothing wrong with being new.
What's your use case here for insensitivity?

I'd say it's simply not having to go through all your csv files and make sure the headers case match your model fields.
So as it currently stands, 'header' != 'Header' and django-postgres-copy will raise a FieldDoesNotExist error. Now if you have many models with many fields and many csv files to upload from different sources, chances of there being a conflict increase. Many conflicts could arise, but at least header case is ruled out.
I believe that chances of you having, for example, 'date' and 'Date' in your model fields are slim and thus no real need to differentiate them. And if that was the case you can always set the case sensitivity to True.

are you OK if I close this request and create two new ones?

fix the deprecated parameter passed to 'open()'
add the case insensitivity logic hopefully now with tests (or please advice if you believe this will not be merged and I will action on it or drop it)

Splitting them sounds like a great idea.


Avoid parsing URI multiple times.

@iGEL @tgxworld Is this one still relevant?

@perlun Probably not. It has been so long since I last looked into this.


AddPolicyAction - Recursion removal

Issue #, if available: #774
Description of changes:
Removed recursion when checking permissions on indices.
Fixed index pattern permission check: injected "injected_user" property into threadContext
CheckList:

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@petardz pls do a manual backport... not sure what's conflict that keeps failing the auto backport


Run iOS apps in an lldb session

Getting an lldb session running in the simulator is a two-step process:

The binary itself must be launched from within lldb in order to capture the processes output streams.

Once the binary is launched, the app must then be "launched" from within the simulator. This doesn't actually create a new process, but instead brings the app into the foreground of the simulator, and is analogous to tapping on the app icon.

Because of the order of these steps, the xcrun simctl launch command has to be run from with the lldb session.
Because lldb won't normally accept further commands after process launch, we use the -s argument to have the app pause just after starting (like stopping at a breakpoint). However, running xcrun simctl launch at this very early stage (before main has even executed) causes a separate instance of the app to start up in the simulator.
In order to work around this we set a breakpoint on -[UIApplication _run], which is early enough that the application hasn't actually started yet, but after UIApplicationMain has set everything up and started the main run loop. Breaking here is a safe place to shell out to xcrun simctl launch, which will no longer start a separte process because the app is already "running".
The other quirk is that in order to feed commands to lldb we need to use the -s option, which requires a file. So the launch script is written to a temporary file first so that it can be passed to lldb. Bash process substitution may also work (e.g., <(cat "$script")).

Related conversation: https://github.com/gfontenot/vim-xcode/pull/76#issuecomment-236105104


Antique Atlas reports Connector Not Available

Mod Name
Antique Atlas 4
Mod Homepage
https://modrinth.com/mod/antique-atlas-4
Minecraft version
1.21.1
Describe the bug
Connector is installed, but mod reports it's not
Steps to reproduce

Add Antique Atlas and its dependencies (Connector, FFAPI) to mods folder
Run server, get error

...
Logs
See Additional context
Additional context
Similar to this Discord conversation: https://discord.com/channels/1141048834177388746/1281143111116128329/1281149382926012447
net.neoforged.fml.ModLoadingException: Loading errors encountered:
        - Mod antique_atlas requires connector any
          Currently, connector is not installed
[main/ERROR] [loading.ModSorter/LOADING]: Missing or unsupported mandatory dependencies:
        Mod ID: 'connector', Requested by: 'antique_atlas', Expected range: '*', Actual version: '[MISSING]'
[main/WARN] [service.ConnectorLoaderService/]: Broken FML mod files found, not adding Connector locator errors

antique atlas is a client side mod

You are correct, I am inattentive.  Thank you.


Change database user to admin for SW 5.2.x

Hello Dirk,
After Shopware 5.2 we migrated from tutum/mysql 5.6 (where the root was "admin") to the native mysql 5.7. However, it is not directly usable in Shopware because of some UTF-8 issues.
We have created a new mysql image based on the native one: https://hub.docker.com/r/dnhsoft/mysql-utf8/
So I'd prefer to keep the default user to root to simplify the docker-compose.yml configurations like this: https://github.com/dnhsoft/sw-docker-demo/blob/master/04-shopware-db-pma-cron-mail/docker-compose.yml
You can always override it in a docker-compose or a child container with a custom Dockerfile...
Best regards
chudo

Okay, thanks chudo