Renovate template try2

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fixes #
Test URLs:

Original: https://www.sunstar.com/

Before: https://main--sunstar--hlxsites.hlx.live/

After: https://renovate-template-2--sunstar--hlxsites.hlx.live/

[ ] New Blocks introduced in this PR
If yes, please provide details below

Block Name
Documentation

For e.g. cards
doc-link

[ ] New variations introduced in this PR

Variation Name
Documentation

For e.g. cards (grid)
doc-link

I see the renovate bot creates branches named like this renovate/eslint-plugin-import-2.x . The . in it could be problematic as it would change the domsain name for the test url. Can we control the name of the branch created here?

I see the renovate bot creates branches named like this renovate/eslint-plugin-import-2.x . The . in it could be problematic as it would change the domsain name for the test url. Can we control the name of the branch created here?

Ooooh, so that was the problem, ok makes way more sense now, yeah I'll look into solving this

Ooooh, so that was the problem, ok makes way more sense now, yeah I'll look into solving this

This is what we had in sunstar-engg site https://github.com/hlxsites/sunstar-engineering/blob/main/.renovaterc.json
Can the same thing work here?

Ooooh, so that was the problem, ok makes way more sense now, yeah I'll look into solving this

This is what we had in sunstar-engg site https://github.com/hlxsites/sunstar-engineering/blob/main/.renovaterc.json Can the same thing work here?

When I asked @tripod about this he suggested not extending the helix-shared config and just using the default, the token they use is only for adobe repos, I guess we could maybe override that somehow but I'd need some help with that

@sdmcraft do you want to merge this, see if it works, and then maybe open an issue in the boilerplate?

o you want to merge this, see if it works, and then maybe open an issue in the boilerplate?

Yes please


ALooper_pollAll is deprecated on Android NDK 27

Prerequisite Checklist

[X] I searched for existing issues to prevent duplicates
[X] I searched for existing discussions on the forum to prevent duplicates
[X] I am here to report an issue and not to just ask a question or look for help (use the forum or Discord instead)

Describe your issue here
Basically everything here applies to SFML (2 & 3) as well. In src/SFML/Window/Android/SensorImpl.cpp in the update function there is this line: ALooper_pollAll(0, nullptr, nullptr, nullptr); which seems to be deprecated. NDK 26 still compiles SFML fine, but NDK 27 throws out this error:
error: 'ALooper_pollAll' is unavailable: obsoleted in Android 1 - ALooper_pollAll may ignore wakes. Use ALooper_pollOnce instead. See The API documentation for more information

Your Environment
SFML version: 2.6.1
Ninja
Android studio 2024.1.1
NDK: 27.0.11902837
Steps to reproduce
Try to compile SFML for Android with NDK 27.
Expected behavior
Compiles fine.
Actual behavior
error: 'ALooper_pollAll' is unavailable: obsoleted in Android 1

https://github.com/ChrisThrasher/SFML/actions/runs/10221306711/job/28283554085
I'm starting to see this sometimes fail CI jobs so we'll probably be forced to take action on this soon.

@Zombieschannel Could you test this out for me? https://github.com/SFML/SFML/pull/3188

Closed by #3188


[BUG] Handling heterogeneous environment observations

Describe the bug
I am trying to implement an environment with set-valued observations of size N x K, where N is a set size that changes every step and K is static. Is there currently a "TorchRL approved" way of doing this?
I see that this has been discussed a bit in https://github.com/pytorch/rl/issues/766. In particular, this comment shows an example in the simple_crypto vmas env which seems similar to my use case. However, I am having trouble accessing observations from the tensordict. It was also mentioned in https://github.com/pytorch/rl/issues/1343 that printing heterogeneous lazy stacks is annoying, so I'm mostly wondering if there has been any progress made since then. Thank you!
To Reproduce
Generating a rollout works fine
from torchrl.envs.libs.vmas import VmasEnv
env = VmasEnv("simple_crypto", num_envs=32)
td = env.rollout(10, return_contiguous=False)["agents"]
print(td)

LazyStackedTensorDict(
    fields={
        action: Tensor(shape=torch.Size([32, 10, 3, 6]), device=cpu, dtype=torch.float32, is_shared=False),
        observation: Tensor(shape=torch.Size([32, 10, 3, -1]), device=cpu, dtype=torch.float32, is_shared=False)},
    exclusive_fields={
    },
    batch_size=torch.Size([32, 10, 3]),
    device=cpu,
    is_shared=False,
    stack_dim=1)

Accessing the "normal way" fails with a reasonable error message
print(td['observation'])

Traceback (most recent call last):
  File "/home/shane/anaconda3/envs/ml/lib/python3.9/site-packages/tensordict/tensordict.py", line 7030, in _get_str
    out = torch.stack(tensors, self.stack_dim)
RuntimeError: stack expects each tensor to be equal size, but got [32, 4] at entry 0 and [32, 8] at entry 1

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/shane/anaconda3/envs/ml/lib/python3.9/site-packages/tensordict/tensordict.py", line 7495, in __getitem__
    return self._get_tuple(index_key, NO_DEFAULT)
  File "/home/shane/anaconda3/envs/ml/lib/python3.9/site-packages/tensordict/tensordict.py", line 7060, in _get_tuple
    first = self._get_str(key[0], None)
  File "/home/shane/anaconda3/envs/ml/lib/python3.9/site-packages/tensordict/utils.py", line 1131, in newfun
    return fun(_self, *args, **kwargs)
  File "/home/shane/anaconda3/envs/ml/lib/python3.9/site-packages/tensordict/tensordict.py", line 7019, in _get_str
    tensors.append(td._get_str(key, default=default))
  File "/home/shane/anaconda3/envs/ml/lib/python3.9/site-packages/tensordict/utils.py", line 1131, in newfun
    return fun(_self, *args, **kwargs)
  File "/home/shane/anaconda3/envs/ml/lib/python3.9/site-packages/tensordict/tensordict.py", line 7048, in _get_str
    raise RuntimeError(
RuntimeError: Found more than one unique shape in the tensors to be stacked ({torch.Size([32, 4]), torch.Size([32, 8])}). This is likely due to a modification of one of the stacked TensorDicts, where a key has been updated/created with an uncompatible shape. If the entries are intended to have a different shape, use the get_nestedtensor method instead.

But it also fails with get_nestedtensor()
td.get_nestedtensor('observation')

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/shane/anaconda3/envs/ml/lib/python3.9/site-packages/tensordict/tensordict.py", line 7201, in get_nestedtensor
    raise RuntimeError(
RuntimeError: Because nested tensors can only be stacked along their first dimension, LazyStackedTensorDict.get_nestedtensor can only be called when the stack_dim is 0.

System info
Installed through pip
import torchrl, numpy, sys
print(torchrl.__version__, numpy.__version__, sys.version, sys.platform)

0.2.1 1.26.2 3.9.17 (main, Jul  5 2023, 20:41:20)
[GCC 11.2.0] linux

Checklist

[x] I have checked that there is no similar issue in the repo (required)
[x] I have read the documentation (required)
[x] I have provided a minimal working example to reproduce the bug (required)

I see the VMAS errors above have been fixed in the nightly package. However, advice would still be appreciated for observation spaces that vary on each step

Thanks for the comments! Here is my take on this.
The heterogeneity discussed in the comments you linked was within a single timestep. Heterogeneity through time is a little more tricky and I think the choice of not allowing it is deliberate. @vmoens maybe can say a few things about this
I think right now the only way to have an observation space with a shape that changes through time is using padding. I.e. you create the space of size Max_N x K. You can pad the non available observations with 0s or any other value of your choice. You can also output a mask among the obs, which tells what obs in the set are valid.
This is what we do for actions spaces with available actions changing through time. There, a mask is output by the env to make the specs know what actions are to be considered available. A similar thing could be done for obs.
This is similar to what we go in PettingZoo when there is a varying number of agents each step or the game is turn-based. You can check out the PettingZoo wrapper for more info on this.

Thanks for the comments! Here is my take on this.
The heterogeneity discussed in the comments you linked was within a single timestep. Heterogeneity through time is a little more tricky and I think the choice of not allowing it is deliberate. @vmoens maybe can say a few things about this
I think right now the only way to have an observation space with a shape that changes through time is using padding. I.e. you create the space of size Max_N x K. You can pad the non available observations with 0s or any other value of your choice. You can also output a mask among the obs, which tells what obs in the set are valid.
This is what we do for actions spaces with available actions changing through time. There, a mask is output by the env to make the specs know what actions are to be considered available. A similar thing could be done for obs.
This is similar to what we go in PettingZoo when there is a varying number of agents each step or the game is turn-based. You can check out the PettingZoo wrapper for more info on this.

Thank you! That's what I figured. This isn't a major problem for my application, so I'll close the issue now.


Adding balance-optiml to create OptiMLs using undersampling of Unbalanced Datasets

but still they both must be > 0, and the proportion <= 1, no?

but still they both must be > 0, and the proportion <= 1, no?

No problem adding the changes. Done.


Update zio-streams, zio-test, zio-test-sbt to 2.1.12

About this PR
📦 Updates

dev.zio:zio-streams
dev.zio:zio-test
dev.zio:zio-test-sbt

from 2.1.5 to 2.1.12
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #491.


[DynamicForm] Creating a document set sometimes throws a 409 save conflict.

Category
[ ] Enhancement
[X] Bug
[ ] Question
Version
Please specify what version of the library you are using: [3.20]
Expected / Desired Behavior / Question
When creating a document set using a dynamic form, this should just work.
Observed Behavior
For some tenants, and only sometimes, a 409 save conflict exception is thrown when submitting the form. It appears the folder is created still, but not updated to be a docset with all the filled in metadata.

The issue occurs on this line:
https://github.com/pnp/sp-dev-fx-controls-react/blob/873aa00689eaeba8c2dc85c25c5bdcb6b03f3f00/src/controls/dynamicForm/DynamicForm.tsx#L614
Steps to Reproduce
It's hard to reproduce unfortunately. My customer has it all the time (in two M365 tenants), but in my tenant I haven't seen the issue occur yet.
Fix
What we could do is add some intelligence to retry updating the list item based on the error that's returned.

PR merged and will be fixed in the next release. The fix will be available in the beta release within a few minutes


[CLOUDGA-14116] Add sensitive permission check during user, role, api key ops

There are some permissions tagged as "SENSITIVE" (eg. API_KEY.CREATE, ROLE.CREATE etc)
We need to check for these permissions in the following cases:

{create role, update role} commands- if any of the input permissions are sensitive permissions, we have to require confirmation
{invite user, update user, create API Key}  commands- if any of the roles provided for these operations contain sensitive permissions, we have to require confirmation

Please resolve conflicts and merge.


InvalidStateError: Failed to execute 'transferControlToOffscreen' on 'HTMLCanvasElement': Cannot transfer control from a canvas more than once.

DotLottieWorkerReact on Next.js is throwing the following error:
InvalidStateError: Failed to execute 'transferControlToOffscreen' on 'HTMLCanvasElement': Cannot transfer control from a canvas more than once.

Hey @theashraf ! did you find anything useful?

We have the same issue. We use<EMAIL_ADDRESS>with<EMAIL_ADDRESS>(We preferred to use @lottiefiles/dotlottie-web over @lottiefiles/dotlottie-react due to an issue the react package has with config.layout)
Way to reproduce:
"use client";

import { DotLottieWorker, type Config } from "@lottiefiles/dotlottie-web";
import {
  type ComponentPropsWithoutRef,
  useEffect,
  useLayoutEffect,
  useRef,
} from "react";

type DotLottieAnimationProps = ComponentPropsWithoutRef<"canvas"> & {
  readonly src: NonNullable<Config["src"]>;
  readonly height: string;
  readonly width: string;
};

const useIsomorphicLayoutEffect =
  typeof window === "undefined" ? useEffect : useLayoutEffect;

function createLottieWorker(canvas: HTMLCanvasElement, src: string): DotLottieWorker {
  return new DotLottieWorker({
    workerId: "dotlottie-worker",
    canvas,
    backgroundColor: "transparent",
    layout: { fit: "fit-width", align: [0.5, 0.5] },
    renderConfig: {
      autoResize: true,
      freezeOnOffscreen: false,
      devicePixelRatio: 5,
    },
    src,
    loop: true,
    autoplay: true,
  });
}

export function DotLottieAnimation({
  src,
  height,
  width,
  style,
  ...props
}: DotLottieAnimationProps): React.ReactNode {
  const ref = useRef<HTMLCanvasElement>(null);

  useIsomorphicLayoutEffect(() => {
    if (ref.current === null) {
      return;
    }

    const worker = createLottieWorker(ref.current, src);

    return () => {
      void worker.destroy();
    };
  }, [ref, src]);

  return <canvas ref={ref} style={{ height, width, ...style }} {...props} />;
}

We get the same error just by enabling StrictMode in our nextjs app.

@flow3d I haven't had time to look into this issue yet, but I'm happy to hear that you accept PRs if someone is interested in helping to fix it

Thanks to @lazybean comment I figured out it happens because createLottieWorker is called twice when StrictMode is enabled, causing a side-effect to run twice.
I made this patch to make sure the effect runs only once. This will prevent re-rendering on any state changes, so be aware that this solution might not be suitable for you.
export function DotLottieAnimation({
  src,
  height,
  width,
  style,
  ...props
}: DotLottieAnimationProps): React.ReactNode {
  const ref = useRef<HTMLCanvasElement>(null);

  useIsomorphicLayoutEffect(() => {
    if (ref.current === null) {
      return;
    }

    const { current: canvas } = ref;

    // `createLottieWorker` has a side effect, so we have to force a single worker per canvas.
    // This is a workaround to prevent multiple workers from being created, which could happen
    // when react is on strict mode (development) or when the `src` prop changes.
    // It means that changing the props `src` will not cause re-render.
    if (canvas.hasAttribute("animation")) {
      return;
    }

    canvas.setAttribute("animation", "true");
    const worker = createLottieWorker(canvas, src);

    return () => {
      void worker.destroy();
    };
  }, [ref.current, src]);

  return <canvas ref={ref} style={{ height, width, ...style }} {...props} />;
}

resolved in<EMAIL_ADDRESS>


fix(apple): Use debug prefix for network extension when building locally

Fixes the developer part of #3383

@jamilbk The TunnelStore needs a little modification as well. I'll open a separate PR that does this.


Broken syntax after a line of code

I'm using tree-sitter-perl through treesitter.nvim
sub mySub {
  my $randomBytes = `head -c 32 /dev/urandom`; # After this line there's no syntax highlighting anymore
  return encode_base64url($randomBytes);
}

sub _log {
  my ($text) = @_;
  print encode_utf8($text) . "\n";
}

@brneor , backtick quotes aren't supported as of now. Let me work on this soon.

this should work now. closing it.

@ganezdragon ty for your attention and speed on this one :)


No operations generated in Azure.AI.ContentSafety.netstandard2.0.cs

No operations generated in Azure.AI.ContentSafety.netstandard2.0.cs in https://github.com/Azure/azure-sdk-for-net/pull/34933
I've tried run eng/scripts/CodeChecks.ps1 again but nothing more generated.

@m-nash the discussion for this is included in the PR that Meng linked in the issue. Is there something that needs to be fixed for this?

Suggested solution is to run this: .\eng\scripts\Export-API.ps1 contentsafety
If it's still not working ping @m-nash and @chunyu3 to investigate

Related docs: https://github.com/Azure/azure-sdk-for-net/blob/main/CONTRIBUTING.md

Hello @mengaims  after we create the project template correct, this issue will not occur. @mengaims  do you have further problem?

Hello @mengaims  We will update the analyzer to resolve this issue.
As a workaround to unblock your work, you can suppress AZC0002 via adding line <NoWarn>AZC0002</NoWarn> in csproj file as following:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <AssemblyTitle>Device Update for IoT Hub client library</AssemblyTitle>
  ...
    <NoWarn>AZC0002</NoWarn>
   ...
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Azure.Core" />
  </ItemGroup>

  <!-- Shared source from Azure.Core -->
 <ItemGroup>
    <Compile Include="$(AzureCoreSharedSources)ArrayBufferWriter.cs" LinkBase="Shared" />
    <Compile Include="$(AzureCoreSharedSources)AzureResourceProviderNamespaceAttribute.cs" LinkBase="Shared" />
  </ItemGroup>

</Project>

It succeeded now, thanks all for the help! Closing this issue.


--remote-*wait hard to use, because it waits for BufDelete

There's no configuration for "hidden" option that allows 'nvr' to simply exit on window/tab with the file being closed. By default, the buffer will become either hidden or unloaded. This means for my "commit" to work properly, I have to remembed to end editing with :w :bd instead of :wq.
My suggestion is to wait for BufUnload or BufHide instead of BufDelete. I see little downside, especially for the first option.

+1 for this feature. So far I'm using nvr  as an $EDITOR with --remote-tab-wait option, and I've patched sources to use TabClosed event. This simple patch allows me to quickly exit from nested nvims with :wq
https://github.com/gbtb/neovim-remote/commit/e1bbb0ab95674cbe2526bb35b8f17c97ab131849.patch

I use this as a workaround:
exec nvr --nostart --remote-tab-wait '+set bufhidden=wipe' "$@"


Fix flickering tests

Trello card URL:
https://trello.com/c/8EMdqNfY/835-fix-flickering-failing-tests
Changes in this PR:
Finally found the issue behind this. The fix is to remove all whitespace from the titles when using sort_by, which mimics the behaviour of Postgres's ORDER BY

Ready for another go round now, I've also stopped using the let!s to set up state, as these get called for each spec, slowing the execution time down dramatically.


Plugin can't find linked databases

I followed all the steps on the page made a new integration added my database to it added the integration token in the plugin settings but it still says

No database linked with internal integration token

I even tried to delete the cache files manually but it still didn't work.
Could you please help me out, thanks.

Hey there,
Deleting cache files manually could cause some issues. Please restart Flow Launcher and check if the files database.json and search.json are created successfully in the cache folder. After that, trigger the plugin to query the databases and check if database.json contains your shared databases. If so, open the settings panel and ensure the default database combobox options are not empty.
If database.json is empty and more than one database shared with token, please share your Flow Launcher log file for further investigation.

yes it creates the database.json and search.json files but database.json is empty and they both have a file size of 0 KB even though I have shared two databases with my integration.
Here is the latest flow launcher log file.
2024-08-07.txt

The Notion API keeps responding with error code 401 (Unauthorized), which means the API token is invalid. Please double-check it or create a new one with all capabilities allowed.
The API token should look something like this:
secret_2XHSvQlNouUkWv5sUqND5VIFOppuA1T7iXd5cfR8gG6

After checking, this error should no longer appear in your log file:
WARN - NotionDataParser.MoveNext - Unauthorized

Or this error if there's an internet connection
WARN  - Main.MoveNext - No internet Connection for Init cache using last cached data

I refreshed the integration token, and added the new token into the plugin settings, restarted flow launcher, but got the same error. The log file still has both the warnings you mentioned here it is.
2024-08-07.txt

Just to be sure that this issue is not because of your Notion token, could you replace your token with this one, then restart Flow Launcher and see if the plugin still gets the the same error 401 ?
secret_BigY9a1CN22ifHwXNcjCz7soV1jnhiI0fvwOwgHoE2t

Alright i replaced it and it still gives the same error here is the log file.
Uploading 2024-08-07.txt…

 Let's first check if the token is correctly requested from the settings class.
First, download the v5 artifact and extract the dll file into the home plugin directory, replacing the existing one. Now, when Notion responds with a 401 error, the plugin will log the token. Restart Flow Launcher and then send me the new log file.

Hi sorry for the late reply I think our time zones are very different.
I replaced it and here is the new log file.
2024-08-08.txt

Yes, after lots of restarting and finessing of flow launcher it completely works. Thanks a lot for all your help. regarding the invalidity of my token, I refreshed it a few times after sending it, but I did make sure to update it every time in the plugin settings. Again thanks a lot for your help


Matched plurality in the documentation.

Code variable and 'return's documentation both indicate multiple poles can be returned.

Coverage remained the same at 88.861% when pulling be36db44e280793b30195646c678e26a31578fad on AutomotiveDevOps:dapperfu-patch-1 into 66d4a53d936b5ecd7bb35e3a7a5825d2c13db0f0 on python-control:master.

Good catch, thanks for the contribution!


codegpt review - context deadline exceeded

Thanks to this project for providing excellent AI generation commits.
I can use codegpt commit.
But can't use codegpt preview.
Error message:
❯ codegpt review
Code review your changes using gpt-4-turbo model
We are trying to review code changes
Error: Post "https://api.openai.com/v1/chat/completions": context deadline exceeded

❯ codegpt review
Code review your changes using gpt-4-turbo model
We are trying to review code changes
Error: Post "https://api.openai.com/v1/chat/completions": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

YAML:
git:
  diff_unified: 0
  exclude_list: ""
  template_file: ""
  template_string: ""
openai:
  api_key: "sk-proj-xxxxxxxxxxxx"
  base_url: ""
  max_tokens: 300
  model: "gpt-4-turbo"
  model_name: ""
  org_id: "org-xxxxxxxxxxx"
  provider: openai
  proxy: ""
  socks: ""
  temperature: "1"
  timeout: "10"
output:
  file: ""
  lang: en

I will take it.

@lee1221ee update the timeout to 1m using the following command.
codegpt config set openai.timeout 1m


AvFeedback is not working with reactstrap 5.0.0-beta.2 version

Although it is working with 5.0.0-beta it stops working with .2 version. I know for beta versions those kind of problems are acceptable (you are alfa, reactstrap is beta) but I want to inform you as soon as possible if you are not aware of that.

The package has been updated, please use the latest beta release with the latest reactstrap beta release.

Using the @next versions of both reactstrap and availity-reactstrap-validation I feel there are still some issues.
I have tried match and email validation. Validation itself seems to work just fine, however:

form-feedback container does not show on the invalid match, color is green as if the field is valid
typing in incomplete email addresses (with just an @ symbol) is correctly invalidated, however, gets colored green.
when using match and required and both fields are empty the match error message is shown in the second field instead of the required custom message

Since validation seems to work fine I feel those issues might just be styling related. Although in some cases the Form-Feedback container gets omitted entirely, while in others the content is just set to be empty.
Could you please show us a working example of the email match field using latest reactstrap@beta3 so we could learn from that? I would greatly appreciate!


Update sbt-scoverage to 1.7.1

Updates org.scoverage:sbt-scoverage from 1.6.1 to 1.7.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

labels: sbt-plugin-update, semver-minor

Codecov Report

Merging #173 (445cd22) into master (7f6a4c3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #173   +/-   ##
=======================================
  Coverage   41.66%   41.66%
=======================================
  Files           1        1
  Lines          36       36
  Branches        1        1
=======================================
  Hits           15       15
  Misses         21       21

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7f6a4c3...445cd22. Read the comment docs.

Superseded by #174.


refactor(transformer/class-properties): use temp_var_name_base to generate temp var names for super transform

Follow-on after #7997.
Generate "base name" for temp var using temp_var_name_base and then create the 2 temp bindings from it.
This is a bit more efficient than creating 2nd temp binding from name of the first temp binding, because the first binding's name has _ added to start, and may have digits on the end, which have to be trimmed off again. Whereas the "base name" is ready to go.
Incidentally, changing the timing of when temp bindings are created also aligns output with Babel.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#8004  👈 (View in Graphite)
#7997
main

How to use the Graphite Merge Queue
Add either label to this PR to merge it via the merge queue:

0-merge - adds this PR to the back of the merge queue
hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

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

Merge activity

Dec 18, 9:24 PM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


Run sample error using DeepStream 5.1 and YOLOv4

Complete information of setup.
• Hardware Platform (Jetson / GPU) : GPU
• DeepStream Version : 5.1
• CUDA Version : 11.1
• JetPack Version (valid for Jetson only): None
• TensorRT Version : <IP_ADDRESS>
• NVIDIA GPU Driver Version (valid for GPU only) : 460.84
• Issue Type( questions, new requirements, bugs) : questions
• How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing)
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)
I have done Deepstream 5.1 with YOLOv4 setup and while Run the Sample getting below error.
Can anybody please help me around?
ERROR:
…
(deepstreamer_env) xxxx@xxxx:/opt/nvidia/deepstream/deepstream-5.1/sources/deepstream_yolov4$ deepstream-app -c deepstream_app_config_yoloV4.txt
Unknown or legacy key specified ‘is-classifier’ for group [property]
** ERROR: main:655: Failed to set pipeline to PAUSED
Quitting
ERROR from sink_sub_bin_sink1: Could not open file “yolov4.mp4” for writing.
Debug info: gstfilesink.c(431): gst_file_sink_open_file (): /GstPipeline:pipeline/GstBin:processing_bin_0/GstBin:sink_bin/GstBin:sink_sub_bin1/GstFileSink:sink_sub_bin_sink1:
system error: Permission denied
ERROR from sink_sub_bin_sink1: GStreamer error: state change failed and some element failed to post a proper error message with the reason for the failure.
Debug info: gstbasesink.c(5265): gst_base_sink_change_state (): /GstPipeline:pipeline/GstBin:processing_bin_0/GstBin:sink_bin/GstBin:sink_sub_bin1/GstFileSink:sink_sub_bin_sink1:
Failed to start
App run failed

I got a solution.
I create a new file as yolov4.mp4 then gave read & write permission then it work me


how to integrate with springmvc env（not springboot）

Enviroment
JDK Version(required): 1.8
SpringBoot Version(required): um, i just wanna spring
Starter Version(required):
Describe
i have a demand need multiple datasource, meanwhile my project env just is spring, how
could i do?
Expected Result:
Actual Result:
Steps to reproduce

Step 1

Step 2

Step 3

参考 DynamicDataSourceAutoConfiguration 自己注入吧


Figure component refactor

Jira

http://vjira2:8080/browse/BDS-530

Summary
Clean up Figure component code and docs. Refactor Figure into web component.
Details
<bolt-figure> is now a web component. If an instance of bolt-figure already has a <figure> tag inside it, it will retain a sanitized version of that tag. Otherwise, simply include media and a caption and the web component does the rest (see the docs).
How to test

Review the new pattern page Figure with web component.
Review the existing (twig) Figure demos and verify these still render as expected.
Review code changes related to web component conversion.

@danielamorse
Never mind that, web component currently has no fallback. Can you confirm what I showed in the screenshot is the current expected behavior? @sghoweri


Testing Github link back to TW - Ticket 109

<EMAIL_ADDRESS>Include/append to the description, the user name and email from Tola Work of who submitted and issue or comment and a link back to the issue.     # - Include/append to the description, the user name and email from Tola Work of who submitted and issue or comment and a link back to the issue.

Test link back to TolaWork[View Ticket in TolaWork - <bound method Ticket.get_absolute_url of <Ticket: 320 Testing Github link back to TW - Ticket 109>>]

Test link again[View Ticket in TolaWork - <bound method Ticket.get_ticket_url of <Ticket: 320 Testing Github link back to TW - Ticket 109>>]

Breaks tag in link[View Ticket in TolaWork - <bound method Ticket.get_ticket_url of <Ticket: 320 Testing Github link back to TW - Ticket 109>>]

Fitting in a URL View Ticket in TolaWork - <bound method Ticket.get_ticket_url of <Ticket: 320 Testing Github link back to TW - Ticket 109>>URL HERE


[1.18.2] Miner's Hammer eats away one block

Forge: 40.1.0
jobsplus-0.3.0.jar
ImmersiveEngineering-1.18.2-8.0.1-147.jar
When I try to use the Miner's hammer to break a multiblock contraption from Immersive Engineering, it only returns 8 blocks instead of 9.

Fixed by 07a69860100c2f20be8f5f728e90826380e5d765


Support nested association forms (e.g. fields_for)

While I don't use nested forms frequently, I expect the functionality will be required in the app I'm currently testing superform with.
@bradgessler - I might have some time to help out with this in the coming weeks.

This should work if you call namespace(:attr_name) or collection(:attr_name). Did you try those?

@bradgessler, I may just have tried it incorrectly. I have a User that has_one :search and accepts_nested_attributes_for :search, and in my User form I tried
row field(:name).input
...
namespace :search do
  row field(:sort_order).input
  ...
end

This did not pull in the value from the associated Search record and created <input name="user[sort_order]" ...> as opposed to what I had expected: <input name="user[search_attributes][sort_order]" ...>.
Is there another pattern I should try using for this scenario?

Oh I see! Yeah, I haven't looked at nested attributes. I'm pretty sure that will take a new component and modifications to the object mapper.

Oh and try something like this for your block:
row field(:name).input
...
namespace :search_attributes do |s|
  row s.field(:sort_order).input
  ...
end

I think this will render the form, but I'm not sure how it will handle fields that are removed or parameter permits.

FYI, that raises NoMethodError undefined method 'input' for #<Superform::Field:0x00000001185442a0 @key=:sort_order, @parent=#<Superform::Namespace ... which (based on a very limited reading of the gem's code) suggests to me that the nested namespace does not have everything the root namespace has.

The issue here is that namespace is not passed Superform::Rails::Field
see #27

A note for those struggling with collection, it's not like namespace where it takes a block. The collection will take your block as a template and yield a namespace for each member of the model's collection.
It does this through an enumerator that needs to be enumerated with #each to yield the values and actually call your block:
class TestForm < ApplicationForm
  def template
    render field(:name).input(type: :text)
    render field(:email).input(type: :email)

    namespace(:contact) do |contact|
      render contact.field(:phone).input(type: :tel)
    end

    collection(:addresses).each do |address|
      render address.field(:street).input(type: :text)
    end
  end
end

This would create a field like something[addresses][0][street]. The index auto increments by one for each item.

A note for those struggling with collection, it's not like namespace where it takes a block. The collection will take your block as a template and yield a namespace for each member of the model's collection.

Yeah this is a really important distinction and I just noticed it's not in the README.md. If somebody wants to add a section that describes the difference between namespaces and collections I'd be happy to merge it.

I've added some documentation to my other PR: https://github.com/rubymonolith/superform/pull/28
If you want me to extract it into a branch without everything else just let me know.

@nolantait thanks for opening a PR! I took a stab at writing this last night and finally committed this morning before seeing your message. I would ask for that to be split from the current PR you have, but since I wrote something would you mind looking at https://github.com/rubymonolith/superform?tab=readme-ov-file#namespaces--collections to see if it makes sense? Second set of eyes is insanely helpful for docs.

Your writeup is awesome, much better than mine. I finally understand the field(:something).collection vs collection(:something). Had a hard time figuring that one out on my own.
I think the only part missing from collections is how to use accepts_nested_attributes_for. Even if you have plans to build it into the library, in the meantime I think a lot of Rails devs looking to migrate will want examples of the common use cases.
I've done it in my apps by remapping the collection key by renaming it to the expected *_attributes. Simple enough but showing its possible will go a long way while scanning the README.

What’s the use case for Rails nested attributes in Superform? I generally avoid that library so I genuinely don’t know.
if somebody on this thread has gotten nested attributes successfully with Superform and can clearly articulate the use case I’d be willing to merge a PR with a blurb about this into the README.

@bradgessler - the use case for nested attributes is when we have a closely-related (or even tightly-bound) set of data split across database tables and it makes sense to edit data from both tables together.
The specific case I was looking at when I opened this issue was where we have both predicate data like date of birth (some of our resources are limited by age) as well as accidental data like addresses (many of our resources are only shown to nearby users and we allow quickly re-searching between multiple addresses like home and work); we store those different sets in different tables but want one form for managing them.
An edge case I was working with last week was a core table that had grown to nearly 200 columns - most of those columns were not directly displayed to the end user in most scenarios so those "auxiliary" columns had been split out into a separate table. The main data collection form still needs to handle columns from both tables, so with vanilla Rails I would use nested attributes.
I think I've also seen nested attributes used for adding related has-many or HABTM records.
I try to avoid these scenarios as much as possible, but I think all of the interesting Rails apps I've worked with in the last decade have had at least one place where this pattern was used.

@nolantait I'm hitting exactly what you're saying here:

I've done it in my apps by remapping the collection key by renaming it to the expected *_attributes. Simple enough but showing its possible will go a long way while scanning the README.

Can you clarify where you're renaming it exactly? Is this inside Superform's source or are you overriding the key method?

@mhamza15 Lets say we have a form for a TodoList:
def view_template
  collection(:items).each do |f|
    render f.field(:title).input
  end
end

It would generate html that looks something like:
<input name="todo_list[items][0][title]" id="todo_list_items_0_title" />

Which means our params come out like this:
{
  todo_list: {
    items: {
      "0" => { title: "Whatever they submitted" }
    }
  }
}

Problem is, accepts_nested_attributes_for in Rails wants our params to look like this:
{
  todo_list: {
    items_attributes: {
      "0" => { title: "Whatever they submitted" }
    }
  }
}

So the simple fix is just to rename the key inside your controller or service objects:
def create
  list_params = params[:todo_list].permit!.to_h
  list_params = list_params.transform_keys(items: :items_attributes)

  TodoList.create(list_params)
end

If your model has a accepts_nested_attributes like:
class TodoList < ApplicationRecord
  has_many :items

  accepts_nested_attributes_for :items
end

Then your model has a items_attributes= already defined which will trigger the behavior from Rails.
That's the reason we need to rename the params from items to items_attributes because by default the way Rails initializes your models looks something like this:
def initialize(**attrs)
  attrs.each do |key, value|
    self.send("#{key}=", value)
  end
end

So when we pass in items it will call #items= and not #items_attributes=.

That makes sense! Would you then not use the normal assign params.require(:x), to: Form.new(record) that you would normally, and just work with the params as if it's a normal form? Since it wouldn't be able to map the _attributes to the key without _attributes that Superform expects?

I actually use dry-schema to do the transformations through dry-rails personally and don't use Superform's strong parameters so these are usually done inside schema classes.
This is a good point to bring up though. Not sure how I'd do this using the strong parameters with Superform. I'll have a look at adding this in. There are a couple of other features I have to clean up and submit from my own fork: https://github.com/nolantait/protos-protoform


Segment Tree Implementation

Hey, I am Saksham Sharma, a GSSOC'21 participant. I am a Competitive Programmer and C++ enthusiastic.
I want to contribute the code for the implementation of the Segment Tree in the C++ language.
Please assign this task to me.
@anubhavitis @dheerajkotwani @tarun26091999 @todi-2000 @geekquad @plazzy99 @rudrakshi99

Hey, I am a GSSOC'21 participant.
I would love to work on this issue in JAVA with proper comment and indentation.
Please assign this issue to me.

I am GSSOC'21 participant. Want to implement segment tree with lazy propagation. Please assign this to me.

Please assign me I want to contribute in java


ARROW-3725: [GLib] Add field readers to GArrowStructDataType

@shiro615 Can you review this?

CI failure is unrelated.
I'll merge this.


Set allow-empty globally

It would be nice if I could set allow-empty globally.
In my application most of the dates are not well defined so i have to add to every {{moment-format}} the allow-empty=true parameter.
Since its possible to define the ouput format globally I think it should be possible to define allow-empty globally too.

There is a bug in ember around parameterless helpers.  Once that is resolved I can look into adding this.

+1, what's your thoughts on a global config like this? it can default to false, I can make a PR if wanted

// addon/utils/compute-fn.js

import Ember from 'ember';
import config from '../config/environment';

export default function(cb) {
  return function(params, hash) {
    if (!params || params && params.length === 0) {
      throw new TypeError('ember-moment: Invalid Number of arguments, expected at least 1');
    }

    let allowEmpty = Ember.get(config, 'moment.allowEmpty');

    const datetime = params[0];

    if(hash.allowEmpty || hash['allow-empty'])
    {
      allowEmpty = hash.allowEmpty || hash['allow-empty'];
    }

    if ([null, '', undefined].indexOf(datetime) > -1 && allowEmpty) {
      Ember.Logger.warn('ember-moment: an empty value (null, undefined, or "") was passed to moment-format');
      return;
    }

    return cb.apply(this, arguments);
  };
}

// config.environment.js
module.exports = function() {
  return {
    moment: {
      allowEmpty: true
    }
  }
};

That seems interesting, I'd be interested and happy to review your PR.

@jasonmit well, at least I want to pass a date :) Even though its null..

Thanks @jcope2013
I have some more changes I need to make to house keeping changes and will version tomorrow.

3.6.0 closes this.  Thanks again everyone


Support dynamically grouping Events together in the S3 sink

Is your feature request related to a problem? Please describe.
S3 Sink users would like to be able to group Events together and send them to dynamic partitions of their S3 bucket. Users would like to track different groups based on what is in the Events to group them into different S3 “folders”.
Describe the solution you'd like
Proposal with path_prefix and object_name
sink:
  - s3:
      object_key:
        path_prefix: "folder-${/partition_key}/"
        object_name: "my-object-${/some_key}";
      threshold:
        // We flush and remove groups when they reach 1000 events
        event_count: 1000
        // Alternatively, flush and remove groups on time when event_count isn't reached
        event_collect_timeout: "30s"

When dynamic values are used in either the path_prefix or the object_name, we will group Events together based on the expression evaluation result.
Describe alternatives you've considered (Optional)
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@graytaylor0 , I believe this request is already expressed in #3310. Then we also have #4099 for the configurable object name. I'll close this one as a duplicate.


Requesting the inclusion of basic data cleaning functions in GeoLift package

Is your feature request related to a problem? Please describe.
This feature is being requested to overcome the challenges of creating manual data cleaning functions before a geolift analysis can be started on advertiser's data
Describe the solution you'd like
I propose a two step solution here -
First, we can include a function upfront that gives us a quick summary of the missing values in the raw data using every location x time index combination.
Second, based on the summary provided in step 1 we recommend if those missing values can be replaced with 0s or interpolated numbers for the GeoDataRead function to work well.
Describe alternatives you've considered
I have currently been using my own functions to have a glance at the data trends/missing values and then making the decision to whether replace those values with 0s or drop them from the analysis completely.
Additional context
None

Hi, thank you for your request. This is a nice-to-have feature but it doesn't block you to use GeoLift functions. If possible, I recommend you to build this feature and collaborate with the package improvement. I'm closing this issue for now. Thank you.


fix(telegraf-raid-plugin): release-1.6.4 image

What this PR does / why we need it:

Does this PR need to be backport to the previous release branch?:

3.8
/cc @swordqiu @wanyaoqi
/area host

ref: https://github.com/yunionio/cloudpods/pull/14517


pip freeze from conda environment into requirements.txt produces @ file:// entries

Just giving you a quick heads-up that your project might be affected by https://github.com/conda/conda/issues/11580, since your newly-created requirements.txt file contains many file @ entries:
https://github.com/oscarpimentel/sne-lightcurves-synthetic/blob/5c7111ee2c2e49346e16896d034577a64da46225/requirements.txt#L1-L112
Note: I found your project through a GitHub search:

Also, a quick GitHub-wide search for certifi_1655968806487 returns my issue (spinalcordtoolbox/spinalcordtoolbox#3817) and only 1 other result<EMAIL_ADDRESS>(June 24th, 2022)

I hope this saves some headache. :)

Thank you! this actually helped me!


Manual pick of rc1.0.32

This is the release for the 26 January which brings the approved changes into production from staging @coderidge

New changes to units for bottle 1.7units
14 units or less
narrative included for people that drink 1 day but exceed limit
Changes so 2-4 times and month and less, or more than 14 units so narrative is shown and not blanks


opposite gender armor

if you try to equip an opposite gender's armor the gfx id loads for that gender's gear but doesn't equip the item
Here's a puush.
http://puu.sh/hr9dx/c73f25154f.jpg It even registers while wearing armor already

Looks like there is no check in place client-side for the item gender before equipping.

Yeah, I spotted that like 20 minutes after posting this, I ran into a crash bug with NPCs as well, will post it as soon as I figure out what's causing it.

Fixed in commit 2fbfda9.


chore: Fix unicode issues in references.bib

This PR fixes two Unicode issues in references.bib, as per the discussion on Zulip, with a view towards running a bibtex parser written in Lean on it:

I removed one instance of an ö character in a citation key, which is anyway problematic for some implementations of bibtex (see e.g. this thread). According to grep, this was only referenced in one file in mathlib, which I changed accordingly.
The one other problematic entry for my bibtex parser is one where there is an \"o inside a string delimited using quotation marks. I have an upcoming fix for this in my parser, but using UTF-8 here is anyway cleaner.

I wonder if we can lint for these issues

Thanks!
bors merge


[bug?] Do not update id.dat with spoofed FW version

When using HENkaku with Ensō then id.dat gets updated with the spoofed FW version.
This leads to an unaccessible memory card when deinstalling Ensō. Just happened to me (*).
First I wanted to report this as an Ensō bug, but regarding https://github.com/henkaku/enso/issues/11 it should be reported as a HENkaku bug.
Please consider changing the behaviour of updating the id.dat. Or re-open the Ensō bug as valid and create a workaround in the Ensō deinstallation code.
Thanks a lot in advance.
P.S.:
(*) By accident I forgot to unlink my memory card (as I'm aware of this issue) and got trapped in a "You have to upgrade" boot.
Fortunately I could directly fix this by unlinking the mc in another Ensō enabled console.
Another solution would have been to temporally use another spare memory card (if you have one), format it and install Ensō again to unlink the original mc.

Yeah this is a known issue and I thought I fixed it a while ago but I’ve still seen it pop up time and time again and it’s pretty annoying. I already patched one point that updates the is.dat but there’s likely other points I missed.


Revert "feature backup and restore privileges catalogs workloadgroup (#44905)"

This reverts commit 8e5738610abbc60654f5ef32f229c117bca34251.
https://github.com/apache/doris/pull/44905
lock object in PasswordPolicy is written to disk, when user upgrade from older version, this lock will null, and cause user couldn't connect to Doris.
Code cause this issue in PasswordPolicy:
    @SerializedName(value = "lock")
    private ReentrantReadWriteLock lock = new ReentrantReadWriteLock();

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.
Please clearly describe your PR:

What problem was fixed (it's best to include specific error reporting information). How it was fixed.
Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
What features were added. Why was this function added?
Which code was refactored and why was this part of the code refactored?
Which functions were optimized and what is the difference before and after the optimization?

run buildall

run p0

run p0


CI against TiDB v5.3.0

It requires https://github.com/hooopo/tidb-playground/pull/2 is merged and hooopo/tidb-playground:v5.3.0 is available at Docker Hub

This pull request has been opened as draft until hooopo/tidb-playground:v5.3.0 is available at Docker Hub.

hooopo/tidb-playground:v5.3.0 is available


Three parameters date functions have unpredictable behavior

I am testing a JDBC connector I'm working on and the three-parameters date functions doesn't seem to be taken into consideration somehow and the TDVT tests fall back (or this is what I'm assuming based on the tests results) to the two parameters versions.
This was tested on the latest SDK checked out few hours ago and Tableau 2019.3.
My dialect.tdd file header and the overridden function is the following (and has many other functions definitions).
<?xml version="1.0" encoding="utf-8"?>
<dialect name='Custom'
         class='custom_jdbc'
         version='18.1'>
         base='SQL92Dialect'>
   <function-map>
....
<date-function name='DATEPART' return-type='int'>
      <formula>DATE_PART(%1,%2)</formula>
      <formula part='year'>DATE_PART('year',%2)</formula>
      <formula part='quarter'>DATE_PART('quarter',%2)</formula>
      <formula part='month'>DATE_PART('month',%2)</formula>
      <formula part='dayofyear'>DATE_PART('dayofyear',%2)</formula>
      <formula part='day'>DATE_PART('day',%2)</formula>
      <formula part='weekday'>DATE_PART('weekday',%2)</formula>
      <formula part='week'>DATE_PART('week',%2)</formula>
      <formula part='hour'>DATE_PART('hour',%2)</formula>
      <formula part='minute'>DATE_PART('minute',%2)</formula>
      <formula part='second'>DATE_PART('second',%2)</formula>
      <argument type='localstr' />
      <argument type='datetime' />
    </date-function>
    <date-function name='DATEPART' return-type='int'>
      <formula>DATE_PART(%1,%2)</formula>
      <formula part='year'>DATE_PART('year',%2)</formula>
      <formula part='quarter'>DATE_PART('quarter',%2)</formula>
      <formula part='month'>DATE_PART('month',%2)</formula>
      <formula part='dayofyear'>DATE_PART('dayofyear',%2)</formula>
      <formula part='day'>DATE_PART('day',%2)</formula>
      <formula part='weekday'>DATE_PART('weekday',%2)</formula>
      <formula part='week'>DATE_PART('week',%2)</formula>
      <formula part='hour'>DATE_PART('hour',%2)</formula>
      <formula part='minute'>DATE_PART('minute',%2)</formula>
      <formula part='second'>DATE_PART('second',%2)</formula>
      <argument type='localstr' />
      <argument type='date' />
    </date-function>
    <date-function name='DATEPART' return-type='int'>
      <formula part='year'>DATE_PART('year',%2)</formula>
      <formula part='quarter'>DATE_PART('quarter',%2)</formula>
      <formula part='month'>DATE_PART('month',%2)</formula>
      <formula part='dayofyear'>DATE_PART('dayofyear',%2)</formula>
      <formula part='day'>DATE_PART('day',%2)</formula>
      <formula part='weekday'>IIF(%3 = 'Monday', ISO_DAY_OF_WEEK(%2), DATE_PART('weekday',%2))</formula>
      <formula part='week'>IIF(%3 = 'Monday', ISO_WEEK_OF_YEAR(%2), DATE_PART('weekday',%2))</formula>
      <formula part='hour'>DATE_PART('hour',%2)</formula>
      <formula part='minute'>DATE_PART('minute',%2)</formula>
      <formula part='second'>DATE_PART('second',%2)</formula>
      <argument type='localstr' />
      <argument type='date' />
      <argument type='localstr' />
    </date-function>
    <date-function name='DATEPART' return-type='int'>
      <formula part='year'>DATE_PART('year',%2)</formula>
      <formula part='quarter'>DATE_PART('quarter',%2)</formula>
      <formula part='month'>DATE_PART('month',%2)</formula>
      <formula part='dayofyear'>DATE_PART('dayofyear',%2)</formula>
      <formula part='day'>DATE_PART('day',%2)</formula>
      <formula part='weekday'>IIF(%3 = 'Monday', ISO_DAY_OF_WEEK(%2), DATE_PART('weekday',%2))</formula>
      <formula part='week'>IIF(%3 = 'Monday', ISO_WEEK_OF_YEAR(%2), DATE_PART('weekday',%2))</formula>
      <formula part='hour'>DATE_PART('hour',%2)</formula>
      <formula part='minute'>DATE_PART('minute',%2)</formula>
      <formula part='second'>DATE_PART('second',%2)</formula>
      <argument type='localstr' />
      <argument type='datetime' />
      <argument type='localstr' />
    </date-function>
....
</function-map>
</dialect>

As you can see in the functions definitions, the three-parameters ones have special definitions fro week and weekday where the formula chooses between one function or another based on the value of the third parameter.
Looking in the tests' results, for exprtests/standard\setup.date.datepart.sow.week.txt which should test DATEPART('week', [date2], 'monday'), the actual query being created is
SELECT DATE_PART(,"calcs"."date2") AS "TEMP_Test________________"
FROM "calcs"
GROUP BY 1

My IIF is not there and, even more, the first parameter is not passed at all. I can only guess, that it falls back to the generic formula for the two-parameters version of the function (DATE_PART(%1,%2)).

In a second test, if I define the generic formulas for the two-parameters functions definitions to be as <formula>DATE_PART('%1',%2)</formula> for the same test - DATEPART('week', [date2], 'monday') - the query being generated is:
SELECT DATE_PART('',"calcs"."date2") AS "TEMP_Test________________"
FROM "calcs"
GROUP BY 1

The only difference is the single quotes as the first parameter. Strange is that they are empty and week is not passed as a parameter. But still, my special formula having IIF in it is not used at all. It's like the three-parameters functions are ignored and Tableau falls back to the two-parameters functions.

In a third test, I also defined generic formulas - <formula>DATE_PART(%1,%2,%3)</formula> - for the three-parameters functions as well with a noticeable change in the tests results. The query created for was
SELECT DATE_PART(,"calcs"."date2",1) AS "TEMP_Test________________"
FROM "calcs"
GROUP BY 1

which seems to indicate that monday is actually value 1 (and not monday) and, again, the first parameter - the "part" - doesn't seem to have a value.
What's also confusing to me is that the same test, but with sunday value as third parameter - DATEPART('week', [date2], 'sunday') - does create a valid query:
SELECT DATE_PART('week',"calcs"."date2") AS "TEMP_Test________________"
FROM "calcs"
GROUP BY 1

Again, there's no IIF in my query and for this one I'm assuming it doesn't use the generic formula, but one that I defined explicitly for the two-parameters functions and "part" week.

An interesting test was with a generic formula-only defined for the three params functions:
    <date-function name='DATEPART' return-type='int'>
      <formula>CASE WHEN '%3' = '1' AND '%1' = 'week' THEN ISO_DAY_OF_WEEK(%2) WHEN '%3' = '1' AND '%1' = 'weekday' THEN ISO_WEEK_OF_YEAR(%2) ELSE DATE_PART('%1',%2) END</formula>
      <argument type='localstr' />
      <argument type='date' />
      <argument type='localstr' />
    </date-function>

In this case, my custom formula was used, but the "part" parameter wasn't passed along. This is the query that was created for DATEPART('week', [date2], 'monday') test
      SELECT CASE WHEN '1' = '1' AND '' = 'week' THEN ISO_DAY_OF_WEEK("calcs"."date2") WHEN '1' = '1' AND '' = 'weekday' THEN ISO_WEEK_OF_YEAR("calcs"."date2") ELSE DATE_PART('',"calcs"."date2") END AS "TEMP_Test________________"
FROM "calcs"
GROUP BY 1

As mentioned before, "monday" has the value 1 and the "part" is missing completely. And I am stuck here and cannot explain all this behavior.

Thank you for your detailed notes. I was able to reproduce the problem and will take a look into it.

If it helps, now I'm playing with DATEDIFF and I'm seeing the same behavior. I haven't tested all of datetime functions, but at least for three of them the issue is there. Might be all, not sure, just wanted to mention this.

I found a few things in my testing. First, there is a bug in 2019.3 that means Tableau isn't always picking the right function (as you noted). This is fixed in our upcoming release for 2019.4 which should be available soon.
I also learned that Sunday is treated as the start of the week, so any of the three part functions that use Sunday will default back to the two part version.
Also, only the 'week' part for the three argument functions is actually relevant. The other parts aren't used since the only Start of Week function we support is for 'week'. Tableau will pick the 2 argument function for other date parts.
I think in 2019.4 things will work as expected. You might be able to get a beta account in order to test that, or it should be available sometime soon, although I don't know exactly when.

Linked to related documentation improvements from latest release of the SDK.


'loose' mode configuration must be the same for

After downloading, I use NPM run start to prompt this error. What settings should I set?
In the past, 2.6.108 was such a problem, and now 2.6.111 is also such a problem
'loose' mode configuration must be the same for @babel/plugin-proposal-class-properties, @babel/plugin-proposal-private-methods
and @babel/plugin-proposal-private-property-in-object (when they are enabled).

Thanks for reporting this @lifetin! This should be fixed as of the latest commit, please feel free to re-clone the repo.
Regards,
Francisco Hodge


Audit wiki articles and remove redundant headlines

It seems Gatsby automatically adds the article title as a headline, but some articles have headlines as well.

I would prefer is the title was not added automatically. As far as I understand it as generated from the filename. While we try to make filenames short and to the point, we have more room for better titles by providing one in the markdown itself. @QuincyLarson


cond :: [Pair (a -> Boolean) (a -> b)] -> a -> b

Similar to R.cond but stricter and simpler (see ramda/ramda#1673). I imagine R.cond is used with unary functions the vast majority of the time.

:+1: for type signatures
:-1: for mixed-arity lists of functions

Do we prefer Pair (a -> Boolean) (a -> b) or a -> Maybe b?

Do we prefer Pair (a -> Boolean) (a -> b) or a -> Maybe b?

It seems like we might already have defined all the functions we would need to create the conditions to build the Pair signature, while with a -> Maybe b we would often just be running our same a -> Boolean test behind the scenes and than wrapping b in a Just if it passes.
On the other hand I hope I am missing something cause that is a nice signature :)
Having written that out, maybe :: [a -> Maybe b] -> a -> b would be useful as well and fits a slightly different scenario?

Yeah there are some cases where we'll return the Maybe directly (e.g. S.head), and it could also be more efficient in some cases. But there are lots of questions when we'll have Boolean producing functions. And I think is more of a Boolean handling function. Not least because I think one is probably better off wrapping results in sum types and folding them (e.g. maybe, either) than using cond with Booleans or Maybes

Do we prefer Pair (a -> Boolean) (a -> b) or a -> Maybe b?

The latter is very elegant! You're right, though, that one could instead apply all the functions and fold. At that point the only advantage of cond is that it would avoid unnecessary computation.
Perhaps we should not add cond at all. I don't use R.cond very often.

I wasn't thinking so much of applying all the functions, but rather cond seems to be frequently be used as ersatz pattern matching. But I prefer folds to pattern matching anyway, so I would probably just fold

Hi @rjmk  and @davidchambers ,
Perhaps this is not the place to ask, but I'm trying to change a project, Kuss, over to Sanctuary. I have a few R.cond statements that I would need to convert.  However, I'm not following the "folding over pattern matching" suggestion enough to implement it.  Would you provide an example?  If there is a better place to ask this question then please direct me to there.
Here is an example R.cond statement from my project:
https://github.com/scull7/kuss/blob/couchbase/lib/couchbase/n1ql.js#L14
// :: Predicate -> String
const  predicateToWhereEq = R.compose(
  R.join(' AND ')
, R.values
, R.mapObjIndexed(R.cond([
    [ R.equals(null), (v, k) => ` ${k} IS NULL ` ]
  , [ R.is(String), (v, k) => ` ${k} = "${v}" ` ]
  , [ R.T, (v, k) => ` ${k} = ${v} ` ]
  ]))
)

cond isn't necessary in this case, since the number and string cases can both be handled with toString. I'll demonstrate one possible approach, broken into several sections.
Preamble:
'use strict';

const R = require('ramda');
const {create, env} = require('sanctuary');
const $ = require('sanctuary-def');

Specifying an environment which permits values such as [null, 123, 'abc']:
//    Value :: Type
const Value = $.NullaryType(
  'kuss/Value',
  'https://github.com/influentialpublishers/kuss',
  x => x === null || typeof x === 'number' || typeof x === 'string'
);

const S = create({checkTypes: true, env: env.concat([Value])});

Defining our functions:
//    formatPair :: Pair String Value -> String
const formatPair = ([k, v]) =>
  `${k} ${v === null ? 'IS NULL' : `= ${S.toString(v)}`}`;

//    specToQuery :: StrMap Value -> String
const specToQuery = S.pipe([S.pairs, S.map(formatPair), S.joinWith(' AND ')]);

Using specToQuery:
specToQuery({foo: null, bar: 123, baz: 'abc'});
// => 'foo IS NULL AND bar = 123 AND baz = "abc"'

Feel free to share another example of code currently written in terms of cond. :)

@davidchambers Thank you for the awesome explanation.  From that I can see that I've got a long ways to go in my understanding of the concepts behind sanctuary.js.  In an effort to understand more and hopefully discover a general pattern, I've found several other code examples from some open source repositories that I contribute to and a few interesting use cases from elsewhere.

This code takes a date in one of several formats and normalizes it to a moment.js object. https://github.com/influentialpublishers/pimp-my-sql/blob/b98e4e15dc6177457ba88c79856dc3ea3455c194/lib/query.js#L22

const dateIsUnix = _.compose(_.equals(0), _.modulo(_.__, 1));

const momentFromString = (date) => moment(new Date(date));

const momentFromDate = _.cond([
  [ _.isNil,         moment ]
, [ moment.isMoment, _.identity ]
, [ dateIsUnix,      moment.unix ]
, [ _.T,             momentFromString ]
]);

Here we validate that a given value matches an expected type shape. https://github.com/influentialpublishers/jigawatt/blob/8c9e445245119b8bd8351eea44629977d54b7d2b/lib/validate.js#L36

// I've excluded the external functions for brevity's sake.
const typeCheck = (middleware) => middleware.forEach((mw, index) => {
  return _.cond([
    [ Helper.isObject,  _.always(null) ]
  , [ Array.isArray,    typeCheckArray(index) ]
  , [ _.T,              () => throwMiddlewareNotObject(index) ]
  ])(mw);
});

This is an interesting use case from Influential's internal dashboard application. It takes an object with optional properties and retrieves a single value from a property which exists in a given priority list of property names. This is very useful when dealing with information originating from non-versioned 3rd party APIs. https://goo.gl/AQ7wqC

const propFallback = R.compose(
  R.cond
, R.append([ R.T, R.always(null) ])
, R.map((x) => [ R.has(x), R.prop(x) ])
)

propFallback([ 'foo', 'bar' ])({ foo: 'fuzz', bar: 'buzz' })

Finally, here are two examples of determining an object's "status" based upon the internal state of that object.

const parseStatus = R.cond([
  [R.propEq('is_blessed', 0), R.always('draft')],
  [R.compose( R.gt(Moment().unix()), R.prop('run_end_date') )
    , R.always('ended')],
  [R.propEq('is_blessed', 1), R.always('active')],
  [R.T                      , R.always('draft')]
])

const mergeStatus = (opportunity) => R.compose(
  R.merge(opportunity)
, R.cond([
    [R.always(checkIfCompleted(opportunity)),                           R.always({status: STATUS_COMPLETED})]
  , [R.compose(notNil, R.path(['submitted_rate'])),                     R.always({status: STATUS_ACCEPTED})]
  , [R.compose(notNil, R.path(['email_send', 'sent'])),                 R.always({status: STATUS_SENT})]
  , [R.T,                                                               R.always({status: STATUS_DRAFT})]
  ])
)(opportunity)

I don't expect answers to everything, but as I said, I hope to learn a general pattern or approach that fits more in line with the "fold over pattern matching" idea.
Also, perhaps this would make for a good start to a sanctuary.js cook book? So that others may gain from this discussion without having to search specifically for it.  Prior art... Ramda Cookbook
Thank you again for taking the time to help.

I suggest working with consistently typed values. I'm not clever enough to reason about functions which operate—in an ad hoc fashion—on four different data types. ;)

Again, I suggest working with consistently typed values.

I suggest this approach:
//    findSatisfactory :: (Any -> Boolean) -> Array String -> StrMap a -> Maybe a
const findSatisfactory = S.curry3((pred, keys, map) =>
  S.reduce(m => k => m.isJust ? m : S.get(pred, k, map), S.Nothing, keys)
);

findSatisfactory(S.is(String), ['foo', 'bar'], {});
// => Nothing

findSatisfactory(S.is(String), ['foo', 'bar'], {bar: 'buzz'});
// => Just('buzz')

findSatisfactory(S.is(String), ['foo', 'bar'], {bar: 'buzz', foo: 'fuzz'});
// => Just('fuzz')

I suggest using nested ternary expressions:
//    parseStatus :: Moment -> { is_blessed :: Integer, run_end_date :: Integer } -> Status
const parseStatus = S.curry2((now, r) =>
  r.is_blessed === 0          ? 'draft' :
  now.unix() > r.run_end_date ? 'ended' :
  r.is_blessed === 1          ? 'active' :
  /* otherwise */               'draft'
);

Note that the Moment value representing the current time is now provided as an argument. In order to write functions which are deterministic (and thus easy to test) we must avoid reading values from the outside world. :)

Thank you for looking over everything and giving thoughtful explanations.  #3 really helps to understand how folding can replace a pattern matching conditional; and #4 is beautiful, the current implementation is certainly over complicated, thank you.
I know that you stated that #1 and #2 should just deal with consistently typed data, but then what is a good approach to validating and/or transforming data coming in from the outside world, which is what those 2 functions are doing.  I'm guessing an approach similar to this: http://origamitower.github.io/folktale/en/folktale.data.validation.html using S.Either, is that going in the right direction?

When dealing with inconsistent data from the outside world it is often necessary, as you suggest, to write functions with types such as Any -> Moment or Any -> Array Integer. Functions such as get and gets make Sanctuary well suited to this task.
In the case of momentFromDate (which is misleadingly named), I suggest avoiding cond:
//    toMoment :: Moment -> Any -> Moment
const toMoment = S.curry2((fallback, x) =>
  x == null           ? fallback :
  moment.isMoment(x)  ? x :
  Number.isInteger(x) ? moment.unix(x) :
  /* otherwise */       moment(new Date(x))
);

By requiring the fallback Moment value to be provided as an argument, toMoment is deterministic.


PKG -- [fcl] Improve fcl.mutate and fcl.query argument input

Addresses: https://github.com/onflow/fcl-js/issues/1559

Closing this. There are too many issues without having a Cadence parser.


CMP Interface to quick theme switching

It would be useful for clients and beginners if there were a CMP interface which automatically displayed all of the available themes located in the /mx-themes/ folder, which can be easily switched, and if possible uninstalled.
This workflow would be much easier than having to go into the System Settings and manually typing the theme name into mtx.theme.

@silentworks and Alan Pich had done a neat Theme Switcher that could work for this I suspect. Andrew, any objections to it being appropriated here?

@rthrash Got a link to that? :)

Another idea @jaygilmore had would be if the Theme Manager CMP interface could also connect to the Package Manager installer; and if possible the Front End Templates category (the one with Skin Graft whatever that is) and the other few themes that are there.
Excerpt from the Slack chatroom with Jay and myself:

jaygilmore [10:27 PM]
I recall that Alan Pich had done something similar but not sure where it went. I agree a CMP would be more portable and it would be nice if somehow all themes could eventually show up there, paid and free.
adam [10:28 PM]
oh yeah, a marketplace integration would be a great addition
jaygilmore [10:28 PM]
from modx.com that is if the package manager installer could be extended or the PM could be accessed with a theme browser view.

Another thought; wouldn't it be easier to build on top of the existing Package Manager to include a Theme Manager in the there. The Front End Templates section hasn't had much attention in years and its a very empty category. This entire section of the Package Manager could be revamped into a Theme Manager. Just a thought; and it would also mean this becomes a core MODX improvement and not MXT.

The code for this is quite old, but I will try and find it and send it over. It was only experimental and I never had time to complete it, I would also re-write now that I know better and how to structure my code better.
I have made the repo public and its available here https://bitbucket.org/silentworks/scope/overview and here is a theme that work with it https://bitbucket.org/xtrz/scope-verti/overview.
I would like to work on this again at some point in the future as I think some MODX users could benefit from something like this, I thin it has some simplicity in it that would make it easy to create themes you can version control.


Code suggestion

Hello there.
I'm onto Materials Sciences (and CRYSTAL itself) very recently. I was diving into some codes of the library, as a way to help me learn Python and to develop some scripts for personal uses, when I've found something strange.
Where?

CRYSTALpytools.convert module
cry_gui2pmg function
Line 176

What?
A Pymatgen Structure object is returned (as expected from this function), but there are more code implemented after it (an if statement for dimensionality=3 cases).
As everything below line 176 never gets executed because the function already hit a return statement, I think this can lead to unexpected behaviors when using dimensionality=3.
That's pretty much about it.
Best regards!
Luiz.

Dear Luiz,
Sorry for the late response. You are quite right. Thank you for pointing it out. We can now confirm that code left behind line 176 are redundant and shoud be removed. If you are using 3D periodicity that should be fine but not for lower dimensions. The issue will be left open until it is merged to the new release. Thank you for your contributions!
Kind regards
CPYTools developers

Dear Luiz,
It should have been fixed by the latest release v2024.11.2. Please refer to the 2D testing cases of this example.
Happy coding!
Best,
CPYTools developers


7048 gas est reporting

create separate call to get gas estimates to display to initial reporter. convert gas to gas costs using constants, round to 4 decimals based on UI mocks
https://app.clubhouse.io/augur/story/7048/add-gas-costs-to-reporting-report-confirm-form

@justinbarry
are you suggesting breaking out the calculateGasEstimates method out of the component. I broke out formatting gas cost to ether into a help method with unit tests.

@bthaile Maybe? Breaking out the formatter like you did is good enough for me.
If we have a ban on  async inside components then maybe it should move but this is something we should decide as a team. Balancing the practical with the fancy is hard sometimes ;)

resolved merge conflict should be good to go.

Looks good!


Added Android Specific guide.

Amended the Getting started guide to include instructions on how to add RNCWebViewPackage to Android's MainApplication.java.
This could save developers a lot of time trying to figure out why they're still getting " Invariant Violation: RNCWebViewPackage could not be found" errors even after running "react-native link react-native-webview".

Closing as guide has already been updated


add syscalls

ability to detect system calls that are security sensitive
ability to provide a policy construct to check use of specific syscall in specific context ... (use-case: if setuid() is invoked in the container, send an alert with the contextual info).
[Future] Ability to generate seccomp profile based on this

Codecov Report

Merging #806 (f93e0e2) into main (b373341) will decrease coverage by 6.50%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #806      +/-   ##
==========================================
- Coverage   41.02%   34.51%   -6.51%
==========================================
  Files          30       30
  Lines        9041     9039       -2
==========================================
- Hits         3709     3120     -589
- Misses       4858     5519     +661
+ Partials      474      400      -74

Impacted Files
Coverage Δ

KubeArmor/core/crioHandler.go
0.00% <0.00%> (-63.87%)
:arrow_down:

KubeArmor/core/dockerHandler.go
0.00% <0.00%> (-53.34%)
:arrow_down:

KubeArmor/feeder/policyMatcher.go
35.14% <0.00%> (-14.71%)
:arrow_down:

KubeArmor/enforcer/appArmorProfile.go
46.66% <0.00%> (-11.29%)
:arrow_down:

KubeArmor/monitor/processTree.go
88.70% <0.00%> (-6.99%)
:arrow_down:

KubeArmor/common/common.go
36.99% <0.00%> (-5.70%)
:arrow_down:

KubeArmor/core/kubeArmor.go
48.21% <0.00%> (-4.54%)
:arrow_down:

KubeArmor/monitor/logUpdate.go
70.50% <0.00%> (-3.39%)
:arrow_down:

KubeArmor/core/kubeUpdate.go
45.82% <0.00%> (-3.28%)
:arrow_down:

KubeArmor/monitor/syscallParser.go
61.51% <0.00%> (-1.78%)
:arrow_down:

... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Can you please add an extra line at the end of all the yaml files?


Update UAA page to include new settings for OIDC

Added a warning about upgrading

[#163786813]
Signed-off-by: Ramya Shenoy<EMAIL_ADDRESS>
Hi Folks, this is a new set of UI elements on the 1.5 tile for PKS. Please re-word / move things elements around as makes sense. We included the new image also.
Please reach out if you have any questions (@neil on slack)

@neil-hickey Thanks! Merging right now!


Upgrade tested AGP versions

from 7.2.0-beta01 to 7.2.0-beta02
from 7.3.0-alpha01 to 7.3.0-alpha02

@bot-gradle test AST

@bot-gradle test AST

OK, I've already triggered the following builds for you:

AllSmokeTestsPullRequestFeedback build

@bot-gradle test AST

OK, I've already triggered the following builds for you:

AllSmokeTestsPullRequestFeedback build

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

@bot-gradle test and merge

OK, I've already triggered a build for you.


ekf2 airspeed fusion:

finished logic for fusion
fixed bug where previous control status was set in the wrong location

@priseborough It would be nice if you could have a look at the comments and give me feedback.
I would also like to talk about covariance init / reset/ growth handling with you.

@priseborough @tumbili Can we finish this up soonish so we can enter flight testing with this?

The PR as it is is safe' to go in IMO, however for flight testing to be useful we need to firstly verify that the EKF setup works acceptably with airspeed fusion turned off and that we log replay both EST and RPL logs  from the flights so that problems can be solved off-line. The problem is that flight logs from this branch I have been sent to date were for a setup with high vibration levels and absence of RPL messages in the log.

@LorenzMeier @priseborough Flight testing of this branch have until now revealed other bugs which we are fixing at the moment. As soon as we have fixed all issues I can do a replay log.

@LorenzMeier @priseborough Merged, but fusion is not activated yet.


Incorrect result is rendered in kafka-ui Kafka topic publish logs using Timestamp/any keyword search

Describe the bug

On trying to search for logs for a specific date, or using a keyword(some text relevant to a log). The search results in incorrect result set.
Set up

  Version: e85e1aafa1250573a8056bf14ee4003d3179cbae
  App is run : Pod inside EKS cluster

Steps to Reproduce
Steps to reproduce the behavior:

Open the Kafka-UI
Navigate to a Kafka topic
Within the selected Kafka topic, navigate to Messages tab
Try to search using a timestamp, for example current date
Try searching with some text you wish to fetch the log result containing it
In both the above selections, incorrect result is rendered
Refer screenshot attached

Expected behavior

   1. If I enter search parameter as timestamp=17th march, 2022, I should be able to fetch message logs only for 17th March
      Currently, result rendered contains logs from feb, refer screenshot
   2. If I enter search parameter as some keyword(text), it does not filter and render the result logs containing just the searched
       keyword, it renders all the data by default

Screenshots

Additional context

Hey, thanks for reaching out. We'll take a look.

@Haarolean Is it ok if i look into this issue ?

@gaddam1987 yep, would be nice!

The issue is in react app, the callback on submit of the filter (this function https://github.com/provectus/kafka-ui/blob/master/kafka-ui-react-app/src/components/Topics/Topic/Details/Messages/Filters/Filters.tsx#L181) is not able to use the fields set in the search criteria. The search always contains default search params irrespective of what we choose.
I don't know why this happens i am not React guy but just going through react to fix this. Will try my best to fix this in this week :)

@prajaktar1 I fixed the issue, you can checkit out from this pull request https://github.com/provectus/kafka-ui/pull/1781 and see if that works, i have tested from my side and it worked.


[#134920125] Don't run acceptance by default in dev

What
Dont run acceptance tests in dev
TODO: Let's first consider if we still want to do this, in the light of #614
How to review
make dev pipelines. Check that the acceptance tests don't run.
Who can review
not @mtekel

As you mention, now that #614 is merged, the acceptance tests take about the same amount of time as the custom acceptance tests (which this wouldn't disable). I don't think this is therefore worth doing.  What do you think?

Closing this as we think #614 will sufficiently address the speed problems for now.


Dependabot (terraform) seems to be opinionated on context of update or it is a BUG

Package ecosystem
terraform
Package manager version
1.x
Language version
1.x
Manifest location and content before the Dependabot update
reference to a private terraform module
dependabot.yml content
---
version: 2

registries:
  coop-terraform:
    type: terraform-registry
    url: https://terraform.coop.no
    token: ${{ secrets.TFE_TOKEN }}
  coop-ghcr:
    type: docker-registry
    url: ghcr.io
    username: CoopGithubServiceaccount
    password: ${{ secrets.DEPENDABOT_GHCR_PULL }}

updates:
  - package-ecosystem: "terraform"
    directory: "/azure"
    registries:
      - coop-terraform
    schedule:
      interval: "weekly"
      day: "sunday"
  - package-ecosystem: "terraform"
    directory: "/management"
    registries:
      - coop-terraform
    schedule:
      interval: "weekly"
      day: "sunday"
  - package-ecosystem: "terraform"
    directory: "/projects"
    registries:
      - coop-terraform
    schedule:
      interval: "weekly"
      day: "sunday"
  - package-ecosystem: "terraform"
    directory: "/sandboxes"
    registries:
      - coop-terraform
    schedule:
      interval: "weekly"
      day: "sunday"
  - package-ecosystem: "terraform"
    directory: "/teams"
    registries:
      - coop-terraform
    schedule:
      interval: "weekly"
      day: "sunday"
  - package-ecosystem: "terraform"
    directory: "/tfe-workspaces"
    registries:
      - coop-terraform
    schedule:
      interval: "weekly"
      day: "sunday"
  - package-ecosystem: "github-actions"
    directory: "/"
    schedule:
      interval: "weekly"
      day: "sunday"
  - package-ecosystem: "docker"
    directory: "/docker-compose"
    registries:
      - coop-ghcr
    schedule:
      interval: "daily"

Updated dependency
from 0.8.0 to 1.0.5 (from old to new version model
What you expected to see, versus what you actually saw
Expected: A PR with an update for the new version
Actually: Dependabot throws an error:
updater | ERROR <job_362442582> Error processing coopnorge/repos/github (RuntimeError)
updater | ERROR <job_362442582> Content didn't change!

Native package manager behavior
it will just update, this error above is from dependabot code ref, not terraform
For me, the question i, why is this raise even there, why should it case about the non diff.
Images of the diff or a link to the PR, issue, or logs
https://terraform.coop.no:443/api/registry/v1/modules/coopnorge/repos/github/versions
  proxy | 2022/05/10 16:44:57 [053] * authenticating terraform registry request (host: terraform.coop.no)
  proxy | 2022/05/10 16:44:57 [053] 200 https://terraform.coop.no:443/api/registry/v1/modules/coopnorge/repos/github/versions
updater | INFO <job_362442582> Latest version is 1.8.0
updater | INFO <job_362442582> Requirements to unlock own
updater | INFO <job_362442582> Requirements update strategy
updater | INFO <job_362442582> Updating coopnorge/repos/github from 1.7.0 to 1.8.0
updater | I, [2022-05-10T16:44:57.967954 #7]  INFO -- sentry: ** [Raven] Sending event ae837566be5549c0ae3582df2da0fecf to Sentry
  proxy | 2022/05/10 16:44:58 [055] POST https://sentry.io:443/api/1451818/store/
  proxy | 2022/05/10 16:44:58 [055] 200 https://sentry.io:443/api/1451818/store/
updater | ERROR <job_362442582> Error processing coopnorge/repos/github (RuntimeError)
updater | ERROR <job_362442582> Content didn't change!
updater | ERROR <job_362442582> /home/dependabot/dependabot-updater/vendor/ruby/2.7.0/gems/dependabot-terraform-0.185.0/lib/dependabot/terraform/file_updater.rb:30:in `block in updated_dependency_files'

Diff between 1.7.0 and 1.8.0 is
git diff 1.7.0 1.8.0
diff --git a/variables.tf b/variables.tf
index db45747..7cef4e4 100644
--- a/variables.tf
+++ b/variables.tf
@@ -159,7 +159,7 @@ variable "writeback_installation_id" {

 variable "allow_auto_merge" {
   type        = bool
-  default     = false
+  default     = true
   description = "Allow pull requests to auto merge when requirements are met."
 }

🕹 Bonus points: Smallest manifest that reproduces the issue
The repo (check also dependabot config) contains multiple directories, but this module is only used in the projects directory.

updated the module to 1.9.0 with the following change,
--- a/main.tf
+++ b/main.tf
@@ -17,6 +17,10 @@ locals {
   labels = concat(local.default_labels, var.labels)

   template = defaults(var.template, { owner = "coopnorge" })
+
+  migrate_repo_switch     = var.mirror.source_repo_url == "" ? 0 : 1
+  migrate_repo_dependency = local.migrate_repo_switch == 0 ? [] : [null_resource.migrate_repo[0], ]
+
 }

 resource "github_issue_label" "repo-label" {
@@ -91,6 +95,8 @@ resource "github_repository" "repo" {
   }
 }
 resource "null_resource" "migrate_repo" {
+  count = local.migrate_repo_switch
+
   depends_on = [
     github_repository.repo,
   ]
@@ -142,7 +148,7 @@ resource "github_team_repository" "access" {

 resource "github_branch_protection" "protected_branch" {
   depends_on = [
-    null_resource.migrate_repo,
+    local.migrate_repo_dependency,
   ]
   count = var.protect_default_branch ? 1 : 0

diff --git a/variables.tf b/variables.tf
index db45747..7cef4e4 100644
--- a/variables.tf
+++ b/variables.tf
@@ -159,7 +159,7 @@ variable "writeback_installation_id" {

 variable "allow_auto_merge" {
   type        = bool
-  default     = false
+  default     = true
   description = "Allow pull requests to auto merge when requirements are met."
 }

it then still shows the same error, but then instead of going form 1.7.0 to 1.8.0 , 1.7.0 to 1.9.0

Just a note, the module is used multiple times in this folder

@AtzeDeVries any interest in submitting a PR improving this? The discussion here might be helpful: https://github.com/dependabot/dependabot-core/pull/5168#issuecomment-1148006567

I am facing the similar error too. The github private repo which i use in my terraform config has sub modules and it is able to identify the latest version but fails after that
(RuntimeError)
updater | ERROR <job_445956799> Content didn't change!
updater | ERROR <job_445956799> /home/dependabot/dependabot-updater/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_updater.rb:30:in block in updated_dependency_files' updater | ERROR <job_445956799> /home/dependabot/dependabot-updater/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_updater.rb:25:in each'
updater | ERROR <job_445956799> /home/dependabot/dependabot-updater/vendor/ruby/2.7.0/gems/dependabot-terraform-0.211.0/lib/dependabot/terraform/file_updater.rb:25:in updated_dependency_files' updater | ERROR <job_445956799> /home/dependabot/dependabot-updater/lib/dependabot/updater.rb:713:in generate_dependency_files_for'
updater | ERROR <job_445956799> /home/dependabot/dependabot-updater/lib/dependabot/updater.rb:284:in check_and_create_pull_request' updater | ERROR <job_445956799> /home/dependabot/dependabot-updater/lib/dependabot/updater.rb:86:in check_and_create_pr_with_error_handling'
updater | ERROR <job_445956799> /home/dependabot/dependabot-updater/lib/dependabot/updater.rb:57:in block in run' updater | ERROR <job_445956799> /home/dependabot/dependabot-updater/lib/dependabot/updater.rb:57:in each'
updater | ERROR <job_445956799> /home/dependabot/dependabot-updater/lib/dependabot/updater.rb:57:in run' updater | ERROR <job_445956799> /home/dependabot/dependabot-updater/lib/dependabot/update_files_job.rb:17:in perform_job'
updater | ERROR <job_445956799> /home/dependabot/dependabot-updater/lib/dependabot/base_job.rb:35:in run' updater | ERROR <job_445956799> bin/update_files.rb:22:in '
updater | INFO <job_445956799> Finished job processing
updater | INFO Results:
updater | Dependabot encountered '1' error(s) during execution, please check the logs for more details.
updater | time="2022-08-25T07:09:16Z" level=info msg="task complete" container_id=job-445956799-updater exit_code=0 job_id=445956799 step=updater

Hmm, it looks like a pull request I prepared https://github.com/dependabot/dependabot-core/pull/5786 might address this issue.

@AtzeDeVries did #5786 resolve the problem for you?

@AtzeDeVries I'll just close assuming this has been fixed, but if you're still running into this feel free to reopen. Thanks!


Undefined index notice fix

Issue #29 .
Description:
Fixes the notices of undefined variables.
Changes:
Checks if the $_GET['redirect_to'] is set else use default empty value.

Hi @sanzeeb3
Great catch. Thank you for your contribution.
Best regards
Daniel


AssertionError

e.py
Traceback (most recent call last):
File "c:\Users\OpenIT\Desktop\WhatsappPABX\core.py", line 8, in
sbie.create_sandbox('testpy', settings=settings)
File "c:\Users\OpenIT\Desktop\WhatsappPABX\sandboxie\sandboxie.py", line 231, in create_sandbox
cfg = self._readini()
File "c:\Users\OpenIT\Desktop\WhatsappPABX\sandboxie\sandboxie.py", line 154, in _readini
assert currentsection is not None
AssertionError
Sandboxie.txt
I renamed file Sandboxie.txt to Sandboxie.ini

Duplicate of #5.


Specifications for custom music?

I'm probably blind but I've tried exporting custom wavs in both 32bit and 16bit pcm and none of them play at all. I know it isn't my DSP as when I put the default music it plays fine. What do I need to do in order for them to play in Super Haxagon?
If I'm being an Idiot I'm sorry.
Also I'm trying to replace the music for the default levels if your wondering.

Alright, so as  far as I  know, somme people  have  found that stereo does not  work. Try converting it to signed 16  bit PCM mono and give  that a  shot.
 I don't think it's  mentioned anywhere. If you need to know the custom tracks for each level, check here: https://github.com/RedInquisitive/Haxa-Editor/tree/master/hexlevels (the XML files will  show you the way)


Add configurable sidecar injector webhook namespace selector

I submitted a similar change to the older installer at https://github.com/istio/istio/pull/16505 but I'll copy paste the reasoning from that pull request to this one; the implementation is a little bit different over here so I implemented it again a little differently and updated the values file to have some meaningful documentation around how setting this namespaceSelector might affect other configuration options.

I'm not sure if there's an issue lurking around for something of this nature; but for us we're having some trouble where we essentially want to declare with an annotation on a pod when the sidecar injection is enabled; by default we only have access to that when we label the namespace with istio-injection: enabled. Switching over to the existing variable enableNamespacesByDefault and setting that to true does solve the problem for us but also introduces a new one which is to say inside of kube-system in order for our networking to come up we need to be able to communicate with the istio webhook which obviously can't happen.

I did consider just directly adding kube-system to the enableNamespacesByDefault configured block and leaving it at that but it seemed like a setting which a user might want more granular control over so I instead set a default value for the namespace selector but made it fully configurable inside of the values file and did not touch the enableNamespacesByDefault in order to not create a breaking change.

Hi @naphta. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@naphta: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_installer
8ee1dc1c548ab44f8bd44ec86ec886662b651da5
link
/test gencheck_installer

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[SYM-4750] Add warnings when sym_flow.vars are booleans or integers

Summary
Since sym_flow.vars values are always going to be cast to strings, we want to let users know so hopefully they won't be surprised. This is especially important now that we're enforcing input types in the SDK.
This PR raises warnings on create or update of a sym_flow if the string value given in any of its vars could reasonably be cast to an integer or boolean.
Screenshots

Current dependencies on/for this PR:

main

PR #146   👈

This comment was auto-generated by Graphite.


all other exists wallet connect events

Is it in your plan to add other events for wallet side? Like call_request

Sorry, it was a wrong question and I just saw your comment
Supported events: connect, disconnect, session_request, session_update
All the method I need works
ف

eth_sendTransaction
eth_signTransaction
eth_signTypedData
eth_sign
eth_sign
personal_sign

thanks


pipewire: 0.3.16 -> 0.3.17

Motivation for this change
New upstream release.
Things done

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

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

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

Changelog: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/f5f5beb0ece64c7d08edb5413dde537ec5b6c3e2
We should probably start using /etc/pipewire/media-session.d/ for enabling the compat modules.

We should probably start using /etc/pipewire/media-session.d/ for enabling the compat modules.

The nixos module now creates these files.  I think this is only effects the pipewire-media-session daemon, so we don't need to change anything else.

Ok, I've added some more stuff:

pipewire looks in /etc for configuration instead of ${pipewire}/etc (the with-* files were ignored because of this)
The nixos module generates a pipewire.conf file.  It's ugly that we copy parts of the example configuration file, but at least we can add arguments to pipewire-media-session now.
alsamixer works with pipewire now, as suggested by @ilya-fedin.

On the positive side, mSBC seems to work now (if you set services.pipewire.mediaSessionExtraArguments = [ "-p" "bluez5.msbc-support=true" ]).  (It's really fragile and you have to restart hsphfpd a few times, but hopefully that'll get better.)
cc @collares (you were commenting on the pipewire bluetooth issue)

I'll merge this PR now.  I don't have enough time right now to refactor the session manager part.  I also think it'll be more  productive to discuss this when/if somebody packages wireplumber.


tutorials/spring-cucumber: "mvn clean test" doesn't run cucumber tests

When I run command 'mvn clean test' from directory '/tutorials/spring-cucumber' then only test from file 'SpringContextTest' runs.
Expected: cucumber tests are run too.
P.S. 'mvn clean install -Pintegration' throws warning "The requested profile "integration" could not be activated because it does not exist"

Hi @N1kbaz,
You can either run the Cucumber tests manually right from the IDE or use the following maven command:
mvn clean test -Pintegration-lite-first --fail-at-end -Dgib.enabled=false
Hope this helps :)