Netbox 3.1.0 support

Please add support for recently released Netbox 3.1.0
Tried to manualy increase max version to 3.1.0, but
it is not enough to work. It seem something changed in classes,
manage.py update leads to this traceback:
...
  File "/usr/lib/python3.8/site-packages/netbox_bgp/urls.py", line 5, in <module>
    from .views import (
  File "/usr/lib/python3.8/site-packages/netbox_bgp/views.py", line 11, in <module>
    from .forms import (
  File "/usr/lib/python3.8/site-packages/netbox_bgp/forms.py", line 71, in <module>
    class ASNFilterForm(BootstrapMixin, CustomFieldModelForm):
  File "/usr/lib/python3.8/site-packages/django/forms/models.py", line 226, in __new__
    new_class = super().__new__(mcs, name, bases, attrs)
  File "/usr/lib/python3.8/site-packages/django/forms/forms.py", line 31, in __new__
    new_class = super().__new__(mcs, name, bases, attrs)
  File "/usr/lib/python3.8/site-packages/django/forms/widgets.py", line 191, in __new__
    new_class = super().__new__(mcs, name, bases, attrs)
TypeError: Cannot create a consistent method resolution
order (MRO) for bases BootstrapMixin, CustomFieldModelForm

We would also appreciate support for 3.1.0.

The support for 3.1.x would be awesome

It looks like the BootstrapMixin was added to classes CustomFieldModelForm and other classes with the latest release. Also CustomFieldBulkEditForm may need changed to CustomFieldModelBulkEditForm.
Also there is now a Model for ASN in Netbox, which conflicts with the plugin Model.


Issues in basic undestanding

Due to issue #516, I wasn't able to use automatic mode in my project. So I started manually inserting blocks in the files that were previously automatically optimized.
I am facing several issues and I think it might be related to my lack of understanding of some premisses.
Can someone help me out?
I can't have any custom components from other libs in my blocks? Can I pass them as parameters to blocks? I tried using a FontAwesome component and it resulted in the issue related to #516, but when I included the svg, it worked.
Another issue is with Non-deterministic; Do I need to have only one return statement, but can I return a variable that could be set with two different values?
Finally, Does state work normally inside blocks? Had some issues with state not changing accordingly.
Had issues where I received the following error message: "block.mjs:102  Uncaught TypeError: Illegal invocation".
Thanks and awesome work
Example: I tried replacing a map with For and changing the jsx inside the loop for a block. Can't figure out why this is not working.
`
import { For, block } from 'million/react';
import { ReactNode } from 'react';
import { useTranslation } from 'react-i18next';

const FaExclamationSVG = block(() => (
  <svg
    stroke='currentColor'
    fill='currentColor'
    stroke-width='0'
    viewBox='0 0 192 512'
    className='h-4 w-4 fill-white'
    height='1em'
    width='1em'
    xmlns='http://www.w3.org/2000/svg'
  >
    <path d='M176 432c0 44.112-35.888 80-80 80s-80-35.888-80-80 35.888-80 80-80 80 35.888 80 80zM25.26 25.199l13.6 272C39.499 309.972 50.041 320 62.83 320h66.34c12.789 0 23.331-10.028 23.97-22.801l13.6-272C167.425 11.49 156.496 0 142.77 0H49.23C35.504 0 24.575 11.49 25.26 25.199z'></path>
  </svg>
));

const FaCheckSVG = block(() => (
  <svg
    className='h-4 w-4 fill-white'
    xmlns='http://www.w3.org/2000/svg'
    viewBox='0 0 512 512'
  >
    <path d='M173.898 439.404l-166.4-166.4c-9.997-9.997-9.997-26.206 0-36.204l36.203-36.204c9.997-9.998 26.207-9.998 36.204 0L192 312.69 432.095 72.596c9.997-9.997 26.207-9.997 36.204 0l36.203 36.204c9.997 9.997 9.997 26.206 0 36.204l-294.4 294.401c-9.998 9.997-26.207 9.997-36.204-.001z' />
  </svg>
));

interface SectionsMenuProps {
  formProgress: Record<string, boolean | null>;
  sections: string[];
  expandSection: (sectionToExpand: string) => void;
  isAlreadyExpanded: (section: string) => boolean;
}

const SectionItemBlock = block(
  ({
    value,
    text,
    className,
    onClick,
  }: {
    value: ReactNode;
    text: string;
    className: string;
    onClick: () => void;
  }) => {
    return (

        {text}

        <button onClick={onClick} className={className}>
          {value}
        </button>

    );
  }
);

export const SectionsMenu = ({
  sections,
  formProgress,
  expandSection,
  isAlreadyExpanded,
}: SectionsMenuProps) => {
  const { t } = useTranslation();

  const focusOnSection = (
    section: string,
    isAlreadyExpanded: (section: string) => boolean,
    expandSection: (sectionToExpand: string) => void
  ) => {
    console.log(2);
    if (!isAlreadyExpanded(section)) {
      expandSection(section);
    }

    document.getElementById(section)?.scrollIntoView({ behavior: 'smooth' });
  };

  const getButtonContent = (index: number) => {
    let buttonContent: { className: string; content: ReactNode };
    if (formProgress === null) {
      buttonContent = {
        className:
          'rounded-full border-2 border-lightBlue bg-white px-2 py-1 font-bold text-lightBlue transition-all ease-in-out hover:bg-lightBlue hover:text-white',
        content: index + 1,
      };
    } else if (formProgress) {
      buttonContent = {
        className:
          'rounded-full border-2 border-green-650 bg-green-650 px-1 py-1 ease-in-out',
        content: <FaCheckSVG />,
      };
    } else {
      buttonContent = {
        className:
          'rounded-full border-2 border-warning bg-warning px-1 py-1 ease-in-out',
        content: <FaExclamationSVG />,
      };
    }
    return buttonContent;
  };

  return (

        <For each={sections}>
          {(section, index) => {
            const buttonContent = getButtonContent(index);
            return (
              <SectionItemBlock
                key={section}
                text={t(section)}
                value={buttonContent.content}
                className={buttonContent.className}
                onClick={() => focusOnSection(section)}
              />
            );
          }}
        </For>

  );
};

`

For second example: I tried removing the For and using only a block inside map.
`import { block } from 'million/react';
import { ReactNode } from 'react';
import { useTranslation } from 'react-i18next';
import { FaCheck, FaExclamation } from 'react-icons/fa';
interface SectionsMenuProps {
formProgress: Record<string, boolean | null>;
sections: string[];
expandSection: (sectionToExpand: string) => void;
isAlreadyExpanded: (section: string) => boolean;
}
const SectionItemBlock = block(
({
value,
text,
className,
onClick,
}: {
value: ReactNode;
text: string;
className: string;
onClick: () => void;
}) => {
return (

{text}
    <button onClick={onClick} className={className}>
      {value}
    </button>

);

}
);
export const SectionsMenu = ({
sections,
formProgress,
expandSection,
isAlreadyExpanded,
}: SectionsMenuProps) => {
const { t } = useTranslation();
const focusOnSection = (section: string) => {
if (!isAlreadyExpanded(section)) {
expandSection(section);
}
document.getElementById(section)?.scrollIntoView({ behavior: 'smooth' });

};
const getButtonContent = (index: number, progress: boolean | null) => {
let buttonContent: { className: string; content: ReactNode };
if (progress === null) {
buttonContent = {
className:
'rounded-full border-2 border-lightBlue bg-white px-2 py-1 font-bold text-lightBlue transition-all ease-in-out hover:bg-lightBlue hover:text-white',
content: index + 1,
};
} else if (progress) {
buttonContent = {
className:
'rounded-full border-2 border-green-650 bg-green-650 px-1 py-1 ease-in-out',
content: ,
};
} else {
buttonContent = {
className:
'rounded-full border-2 border-warning bg-warning px-1 py-1 ease-in-out',
content: ,
};
}
return buttonContent;
};
return (

{sections.map((section, index) => {
const buttonContent = getButtonContent(index, formProgress[section]);
return (
<SectionItemBlock
key={section}
text={t(section)}
value={buttonContent.content}
className={buttonContent.className}
onClick={() => focusOnSection(section)}
/>
);
})}

);
};
`
As a result, it is bringing me the className for the second if block inside getButtonContent but content is showing index....
I am lost.

should be

Hmm, thank you very much for this. We'll definitely try to review this issue and get back to you. :thinking:

@Cafezinho , could you please update to the latest million version and see if the issues have been resolved

Thanks for your kind words @Cafezinho; has this issue been resolved for you?

Will try it out in the next few days and give you a feedback. Thanks for the help

I ran into a similar issue, can you re-open this? @tobySolutions

I ran into a similar issue, can you re-open this? @tobySolutions

Can I see what you ran into?

Sure, @tobySolutions.
I tried adding a block into my routing component as shown in Kitchen-Sink by @aidenybai.
import { Routes, Route, Navigate } from 'react-router-dom';
import { Test } from '../Test';
import { TaktPage } from 'pages/TaktPage';
import { BimLayout } from 'pages/BimLayout';
import { CreateSchedulerPage } from 'pages/CreateSchedulerPage';
import { block } from 'million/react';
import { AppGlobalLayout } from 'pages/AppLayout';
import {AllRoute} from 'pages/AllRoutes';
...
...
..
export const AppRouter = block(() => {
// export const AppRouter = () => {
// const { t } = useTranslation();
return (
<>

<Route path="/" element={} />
<Route path="/login" element={This is login page} />
<Route path="/style-guide" element={} />
<Route path="/ui/Visilean/autodeskRedirect" element={} />
<Route path="/app" element={}>
<Route index path="takt-view/create/:projectId" element={} />
<Route path="takt-view/:projectId" element={} />
<Route path="/app/bim-view/:projectId" element={}>
<Route index element={} />
<Route path=":embedReportId" element={} />

<Route path=":projectId/templates" element={} />
<Route path=":projectId/reports/" element={}>
<Route index element={} />
<Route path=":embedReportId" element={} />

<Route path=":projectId/setting" element={}>
<Route path=":projectId/profile" element={}>
<Route path=":projectId/constraint" element={}>
<Route path="/app/scheduler-view/:projectId" element={}>
<Route path="/app/table-view/:projectId" element={}>

			<Route path="*" element={
{'page_not_found'}
} />
			<Route path="test" element={<Test />} />
			<Route path="/buttons" element={<ButtonStyle />} />
			<Route path="/checkbox" element={<CheckboxStyle />} />
			<Route path="/radio" element={<RadioStyle />} />
			<Route path="/chips" element={<ChipStyle />} />
			<Route path="/status" element={<StatusButtonStyle />} />
		</Routes>
	</>
);

});
But here I encountered two errors:
index.tsx:29 Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:

You might have mismatching versions of React and the renderer (such as React DOM)
You might be breaking the Rules of Hooks
You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.

react.development.js:1618 Uncaught TypeError: Cannot read properties of null (reading 'useContext')
at Object.useContext (react.development.js:1618:1)
at useInRouterContext (hooks.tsx:90:1)
at useRoutesImpl (hooks.tsx:352:1)
at useRoutes (hooks.tsx:343:1)
at Routes (components.tsx:468:1)
at unwrap (million.4d88fdd9.mjs:74:1)
at million.4d88fdd9.mjs:87:1
at Array.map ()
at unwrap (million.4d88fdd9.mjs:87:1)
at block (million.52d69b41.mjs:632:1)
//    craco.config.cjs
const million = require('million/compiler');
module.exports = {
webpack: {
plugins: { add: [million.webpack({ auto: true })] }
}
};
I am using create-react-app and the version of million is 2.6.4.

@tobySolutions & @aidenybai my app is up and running with Million. The steps I followed were:
Step 1 Install Craco:
npm i -D @craco/craco
Step 2 Update the existing calls to react-scripts in the scripts section of your package.json to use the craco CLI:
"start": "craco start"
After performing these steps my app got integrated with Million js.

Thank you folks! I'll be closing this now.


Issue with access token and token refresh

Please provide us with the following information:

This issue is for a: (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

I have followed the steps outlined in this Tutorial: Authenticate and authorize users end-to-end in Azure App Service
and successfully deployed both the frontend and backend apps and followed all the instructions provided in the documentation.
The primary distinction from the tutorial is that I configured authentication by providing the details of an existing app registration.
Here is an overview of the steps I performed:

Created AD app for frontend and backend
Added backend app's user_impersonation permission to frontend AD app
Applied authSettings property using az webapp auth set
Updated appsettings

However, after configuring everything and launching the frontend application, I encountered an error related to jwt_decode.
It appears that the access token was not a valid JWT token. So I modified the remaining portions of the code to utilize the ID token id token (x-ms-token-aad-id-token) which is a valid JWT Token. This change allowed the application to function correctly.
However, I encountered an issue when testing the refresh token.
Despite calling the /.auth/refresh endpoint, the ID token failed to refresh, even after its expiration.
Furthermore, the refresh token middleware failed to refresh the token and returned a status code of 401.
Please suggest how to resolve this issue.
Any log messages given by the failure

Expected/desired behavior

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Closing this since the issue is due to the Issuer URL
https://github.com/MicrosoftDocs/azure-docs/issues/114257#issuecomment-1711091321


Upload kind logs at e2e tests

Upload Kind logs to e2e tests

We used different method to create kind, so those logs are not exists :(


[Bug]: Array from object node does not return strings properly to next node if split is active

What happened?
I have an array in an object node, e.g.
[
"Can you suggest a good smartphone for a new purchase?",
"I'm in the market for a new phone. Which one do you think is the best right now?"
]
If I use that as an input (e.g. for embedding node) and activate split it returns:

"Can you suggest a good smartphone for a new purchase?"
"I'm in the market for a new phone. Which one do you think is the best right now?"

What was the expected functionality?
It should return:

Can you suggest a good smartphone for a new purchase?
I'm in the market for a new phone. Which one do you think is the best right now?

Describe your environment
MacOS
Relevant log output
No response
Relevant screenshots

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Should be fixed by #321 as well


PhpRedisDriver > Support SncRedisBundle BaseClient

Since the BernardBundle defaults to snc_redis.bernard it would be nice to actually support it ;)
SncRedisBundle creates a BaseClient when in dev mode that does not extend from \Redis.
This PR allows both \Redis and \Snc\RedisBundle\Client\Phpredis\BaseClient as constructor argument.

If the public API of \Redis and BaseClient is identical, then I would rather extend the PHP Redis driver in the BernardBundle and override the constructor. That way typehinting can be used and no vague optional dependency is introduced in this package.

BaseClient doesn't extend or implement \Redis but just wraps it.

Based on your PR, there must be some sort of overlap between Redis and BaseClient public API. Otherwise this would not work in the first place. Nevertheless of any overlap, this kind of extension/override/reimplementation belongs to the BernardBundle, not Bernard itself.

i agree, should be moved to the bundle.


Change Slack channel of cccatalog project on Community page

Describe the bug
Currently the Community page points to #cc-search for the Catalog project, when it actually has its own channel: cc-dev-catalog.
Expected behavior
Indicate the correct Slack channel for the CC Catalog.

Hi, I've fixed the issue and created pull request #275


Remove unexpected backquote.

Very strange—not sure where this would have come from.

Out of date.


Brigadier

Describe the problem related to your feature request.
There is no command api for valence. I would start with porting brigadier (library that mojang uses to handle commands)
What solution would you like?
A command object which will contain nodes.
Node will contain:

id - it's id in that command object
children - it's children in that command object.
kind - kind of node (integer, string, executable...)
suggestions - an optional suggestion of node (type of suggestion or executable)

Command object will handle:

command executions
command suggestions

What alternative(s) have you considered?
Just do like in bukkit. All arguments passed into an array of strings.
Additional context
Brigadier: https://github.com/Mojang/brigadier

We've already discussed this in discord quite a bit, but I can't seem to find the thread right now.

We discussed this a bit on discord in the past, but the way Brigadier relies on mutable callback functions and dynamic typing for the executes context doesn't seem like a great fit for Rust or ECS (or any language really). For example:
CommandDispatcher<CommandSourceStack> dispatcher = new CommandDispatcher<>();

dispatcher.register(
    literal("foo")
        .then(
            argument("bar", integer())
                .executes(c -> {
                    System.out.println("Bar is " + getInteger(c, "bar"));
                    return 1;
                })
        )
        .executes(c -> {
            System.out.println("Called foo with no arguments");
            return 1;
        })
);

Instead of the above, I would rather see something roughly like this:
#[derive(Command)]
struct MyFooCommand {
    bar: Option<i32>,
}

fn handle_foo_commands(foos: EventReader<CommandEvent<MyFooCommand>>) {
    for event in foos.iter_mut() {
        match event.command.bar {
            Some(n) => println!("Bar is {n}"),
            None => println!("Called foo with no arguments"),
        }
    }
}

In other words, you describe the structure of the command graph as a Rust data type and pattern match on it to do the execution.
You'd register MyFooCommand as "foo" somewhere (CommandContext resource or something) and off you go.
You could also represent cyclic commands this way:
#[derive(Command)]
struct MyCyclicCommand {
    blah: i32,
    recursion: Option<Box<MyCyclicCommand>>,
}

(Disclaimer: I have not actually used Brigadier)

We discussed this a bit on discord in the past, but the way Brigadier relies on mutable callback functions and dynamic typing for the executes context doesn't seem like a great fit for Rust or ECS (or any language really). For example:
CommandDispatcher<CommandSourceStack> dispatcher = new CommandDispatcher<>();

dispatcher.register(
    literal("foo")
        .then(
            argument("bar", integer())
                .executes(c -> {
                    System.out.println("Bar is " + getInteger(c, "bar"));
                    return 1;
                })
        )
        .executes(c -> {
            System.out.println("Called foo with no arguments");
            return 1;
        })
);

Instead of the above, I would rather see something roughly like this:
#[derive(Command)]
struct MyFooCommand {
    bar: Option<i32>,
}

fn handle_foo_commands(foos: EventReader<CommandEvent<MyFooCommand>>) {
    for event in foos.iter_mut() {
        match event.command.bar {
            Some(n) => println!("Bar is {n}"),
            None => println!("Called foo with no arguments"),
        }
    }
}

In other words, you describe the structure of the command graph as a Rust data type and pattern match on it to do the execution.
You'd register MyFooCommand as "foo" somewhere (CommandContext resource or something) and off you go.
You could also represent cyclic commands this way:
#[derive(Command)]
struct MyCyclicCommand {
    blah: i32,
    recursion: Option<Box<MyCyclicCommand>>,
}

(Disclaimer: I have not actually used Brigadier)

I've thought we could use a Execute Id, which is just a number. So execute function returns this id and fill the vector with arguments, which were calculated during finding this id.

To speed up development, I think we should try to avoid reinventing the wheel.
Azalea seems to have a workable crate already, we should evaluate if we could use it in Valence.
https://github.com/azalea-rs/azalea/tree/main/azalea-brigadier

To speed up development, I think we should try to avoid reinventing the wheel.
Azalea seems to have a workable crate already, we should evaluate it if we could use it in Valence.
https://github.com/azalea-rs/azalea/tree/main/azalea-brigadier

I already did this. See merged pr #446. We haven't done server side yet tho.

does brigadier support generating the command completion packets?
if you are curious I have auto completion and am doing something like this
https://github.com/andrewgazelka/hyperion/blob/7540e89e92b4ce38ff4249f7fe4b9ea5d87e1319/crates/hyperion-permission/src/lib.rs#L101-L121
although yea probably better to combine and not have nom + brigadier  like syntax


Error: Element type is invalid

I'm trying to get a barebone form up and running but I'm getting the following error when I try to use <Frontier />:
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

If I remove the the <Frontier /> component the rest of the app renders correctly so everything else seem to be in order.
Has there maybe been changes to the project that is not reflected in the documentation?
This is the code that produces the error:
import withApolloClient from "../../../lib/with-apollo-client";
import gql from "graphql-tag";
import Frontier from "frontier-forms";
import { myApplicationKit } from "../formUiKit";

const CREATE_USER = gql`
  mutation($email: String!, $password: String!) {
    registerUser(user: { email: $email, password: $password }) {
      success
      message
      user {
        id
      }
    }
  }
`;

const UserForm = ({ apolloClient }) => {
  return (
    <div>
      <Frontier
        mutation={CREATE_USER}
        client={apolloClient}
        uiKit={myApplicationKit}
      />
    </div>
  );
};

export default withApolloClient(UserForm);

Argh! It was a typo on my part. :)
// This:
import Frontier from "frontier-forms";

// Should be replaced with:
import { Frontier } from "frontier-forms";

Oh Javascript – with your incomprehensible error messages and your fragile imports – how I love you so.


Matlab core function mean support

🚀 Feature Request
Matlab core function mean missing in mat2py, yet.
🔈 Motivation
"all" argument of "mean" function is not implemented, yet. In Python this should be equal to an execution without arguments.
📝 Expected Results
%% Test basic functionality
A = [0 1 2; 2 3 4; 0 4 2; 4 2 6]

Mcol = mean(A)
assert(isequal(Mcol, [1.5, 2.5, 3.5]))
Mdim2 = mean(A,2)
assert(isequal(Mdim2, [1; 3; 2; 4]))
Mall = mean(A,'all')
assert(Mall == 2.5)

🛰 Alternatives
📎 Additional context

@APgEDo I am using Matlab 2015b which do not support this all in mat2py v0.0.13.
But I have already added support for it in v0.0.14. Please try again v0.0.14.
Please upgrade your mat2py with command pip3 install -U mat2py.
BTW, I may not bump the mat2py version too frequently into Pypi when implementing your requests. So please use pip3 install -U git+https://github.com/mat2py/mat2py to install a nightly build version.

Passes successfully my unit test, meaning all argument (R2018b and later) works.
    def test_mean_function(self):
        A = M[[0, 1, 2], [2, 3, 4], [0, 4, 2], [4, 2, 6]]
        Mcol = mean(A)
        assert(np.array_equal(Mcol, M[[1.5, 2.5, 3.5]]), "standard check without additional arguments")
        Mdim2 = mean(A, 2)
        assert(np.array_equal(Mdim2, M[1, 3, 2, 4]), "check with dimension argument for 'row-wise' averaging")
        Mall = mean(A, 'all')
        assert(Mall == 2.5, "additional argument 'all'")


Delegate rather than Full control

In Outlook you can designate someone as delegate rather than Full Control, is that possible to do with this powershell command?  Can Can I substitute Delegate for Full Control in the command arguments?

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

ID: 4fcbd22b-e14b-fe97-7b7f-eb672e84d382
Version Independent ID: f9a024d7-6600-4922-02b5-2c8ceeae13ab
Content: Add staff to Bookings
Content Source: microsoft-365/bookings/add-staff.md
Service: bookings
GitHub Login: @kwekuako
Microsoft Alias: kwekua

@tathmann Thank you for your feedback. Since your question is more on Outlook,  this can be done directly on the application.
Full access is granted via the admin center. However, if you would like to grant different delegate permissions, You can click on File-->Account settings-->Deleegate access-->Add to select the person you want to delete and you will see the window to grant different levels of access

Hope this helps!
Thanks
Sri

No, this is for Bookings. This is from the page of how to setup someone to manage bookings but not be on the list of people to book meetings with. The example was only to give someone full control, I want to know if it could be done with "delegate", instead. The form seemed to give the page I was submitting from so I didn't think I had to spell all that out
Troy Athmann

From: Sriraman M S @.>
Sent: Thursday, January 20, 2022 6:42:21 AM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Troy @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Delegate rather than Full control (Issue #7427)
@tathmannhttps://github.com/tathmann Thank you for your feedback. Since your question is more on Outlook, this can be done directly on the application.
Full access is granted via the admin center. However, if you would like to grant different delegate permissions, You can click on File-->Account settings-->Deleegate access-->Add to select the person you want to delete and you will see the window to grant different levels of access
[image]https://user-images.githubusercontent.com/45987684/150349858-45d886d0-8f81-400b-982b-9e8992cda4db.png
Hope this helps!
Thanks
Sri
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/issues/7427#issuecomment-1017516196, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMOWUPSMX24U6GD7P4ZXH2DUXAGL3ANCNFSM5MISJ4LA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>

@msbemba

@tathmann Thank you for the feedback. The available permissions is just full access for now. If there are any new access levels introduced, we will update the document.
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @tathmann Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


question about FeatureFlowAttention: flow.detach()

Code snippets:
flow = self.feature_flow_attn(feature0, flow.detach(),
local_window_attn=prop_radius > 0,
local_window_radius=prop_radius)
I'm curious about the flow.detach(). What was your idea for that design? I guess multipath backpropagation affects optimization performance, but I don't know if it's right.

The motivation for doing this is to make the flow prediction before propagation unaffected by the subsequent results. However, I didn't observe too much difference by removing it as far as I can remember.

The motivation for doing this is to make the flow prediction before propagation unaffected by the subsequent results. However, I didn't observe too much difference by removing it as far as I can remember.

I get it, thank you.


Solaris (x86 & SPARC)+ AIX (PPC) builds dropped from Adoptium?

Question

Context
Java version:

Your operating system and platform:

We are working on these platforms, expect them to be released later this week.


Bugfixes and changes

Added some missing functions and fixed bugs so that JuliaFEM.jl tests
pass now.

Coverage decreased (-0.8%) to 99.245% when pulling 6f7b3f12c310473632c0f55b75f955c5feaa7acf on bugfixes into 3a0f9f1a80a99d28fb56609740387f17603c7dcd on master.

Coverage remained the same at 100.0% when pulling b5628e2656091c766d9862433f9c98cfa716d6a7 on bugfixes into 3a0f9f1a80a99d28fb56609740387f17603c7dcd on master.


User can Chose Aspect  Ratio of Image while Croping

Hi,
Thanks for the great lib.
I just want to know is it possible that the user can choose between oval, rectangle or square and also the aspect ratio can be changed when the user is cropping the image?

Issue #594 will answer your question about aspect ratio.
You can do all you asked with the following code.
EditPhotoFragment.java
CropImage.activity(imageUri)
                            .setCropShape(CropImageView.CropShape.OVAL)
                            .setAspectRatio(444,100)
                            .start(myContext, this);

For square you use setCropShape(CropImageView.CropShape.RECTANGLE) and set the aspect ratio to 1:1 .setAspectRatio(1,1)


analyzer: Add support for Swift Package Manager

Swift Package Manager is still very young and no other open-source scanners support it. I thought it would benefit the community if ORT had SPM support. This commit adds a new analyzer that parses Package.resolved files and creates results that are enriched with as much data as possible.

@sschuberth Could you please take a look? Closes #723

Thanks a lot for your contribution @UgniusV! Unfortunately, I won't have time to look at this within the next days. So please be a bit patient, or maybe hope for a review by another maintainer 😉

Hey @tsteenbe ! First of all, thank you for your time and for reviewing my PR. The idea of this PR is to parse dependencies from iOS/macOS app projects that are built with XCode (using Swift Package Manager).
In these cases, there are no Package.swift files and the package show-dependencies command fails:
❯ swift package show-dependencies --format json
error: root manifest not found

This is because Package.swift files are only present for libraries that are distributed using the SPM. Not for full iOS/macOS projects. These types of projects contain only Package.resolved which are automatically created & updated by XCode whenever a new dependency is added to the app project.
There are already tools that can generate SBOMs from Package.swift. For example:
https://github.com/opensbom-generator/spdx-sbom-generator.
But there were no tools that could generate SBOM from Package.resolved files, that's the reason behind this pull request.
I do agree with you that we should make ORT cover as many cases as possible. So I will add a fallback mechanism that parses the output of swift package show-dependencies --format json in case no Package.resolved files are found and we are dealing with a Swift Library, rather than an XCode app build.

@tsteenbe I just noticed that when running swift package show-dependencies --format json inside a directory with a Package.swift file present. Package.resolved file automatically gets created and it contains the whole dependency graph (transitive dependencies are included). Maybe it would be a good idea to override beforeResolution method inside SPM class and make it run swift package show-dependencies --format json so that the Package.resolved file would get created and then we could reuse the same parsing logic and avoid additional complexity? What do you think?

What do you think?

Please have a look how this is done in other package managers that support the concept of "lockfiles", like in NPM. By default ORT refuses to analyze projects without a lockfile as results would not be deterministic. Only if the allowDynamicVersions configuration option is set to true projects without a lockfile should be analyzed.
The idea to implement analysis of projects without a lockfile by creating a temporary lockfile and then reusing the code to parse the lockfile is a good one. We were actually thinking about implementing it like this for several of the existing package managers, too, instead of coming up with a completely separate code path for the analysis of such projects.

Awesome, so I will override beforeResolution method to perform swift package show-dependencies --format json if allowDynamicVersions configuration option is set to true. Fix the README and rebase my changes.

I have added the conditional conversion of Package.swift to Package.resolved file inside mapDefinitionFiles override. This seemed like a better place to implement this rather than beforeResolution since we also need to provide a custom definition file mapping (Explained in javadoc). The parsing logic was left untouched.

I just noticed that when running swift package show-dependencies --format json inside a directory with a Package.swift file present. Package.resolved file automatically gets created and it contains the whole dependency graph (transitive dependencies are included). Maybe it would be a good idea to override beforeResolution method inside SPM class and make it run swift package show-dependencies --format json so that the Package.resolved file would get created and then we could reuse the same parsing logic and avoid additional complexity? What do you think?

AFAIK, if you use swift package show-dependencies --format json, the list of dependencies will be printed and contain the correct dependency tree.
You can use this output directly, and won't need to parse the lockfile at all.
The output should also include the transitive dependencies and associate them with their parents.
I'm not sure if this association is visible in the lockfile.

So it could also be bootstrapped or included in the Docker image.

Then I'd prefer to have it added to the Docker image as part of this PR (if the PR relies on executing SPM; I wonder how the funTests pass without it...).

I just noticed that when running swift package show-dependencies --format json inside a directory with a Package.swift file present. Package.resolved file automatically gets created and it contains the whole dependency graph (transitive dependencies are included). Maybe it would be a good idea to override beforeResolution method inside SPM class and make it run swift package show-dependencies --format json so that the Package.resolved file would get created and then we could reuse the same parsing logic and avoid additional complexity? What do you think?

The output of swift package show-dependencies --format json includes the transitive dependencies and associate them with their parents. Is this association also visible in the lockfile? Or is it a flat list?
Edit: I just checked: The lockfile does not contain the association between the packages. The output of swift package does. So maybe a combination of parsing the output of swift package and parsing the lockfile is necessary if allowDynamicVersions is enabled.

Re @MarcelBochtler That's a very good idea, I will implement dependency associations when parsing Package.swift

So it could also be bootstrapped or included in the Docker image.

Then I'd prefer to have it added to the Docker image as part of this PR (if the PR relies on executing SPM; I wonder how the funTests pass without it...).

@sschuberth And will also update the Dockerfile to have swift installed

@sschuberth @MarcelBochtler I have updated the Dockerfile and Licenses. Also, the SPM analyzer now associates parent-child dependencies whenever parsing Package.swift. I have also provided the required test coverage.

@sschuberth @MarcelBochtler Any updates?

The current state of this PR fails to analyze the vapor project locally:
❯ swift --version
swift-driver version: 1.45.2 Apple Swift version 5.6 (swiftlang-<IP_ADDRESS>3.62 clang-13<IP_ADDRESS>)
Target: x86_64-apple-macosx12.0

15:28:07.773 [DefaultDispatcher-worker-3] ERROR org.ossreviewtoolkit.analyzer.managers.SPM - Resolving SPM dependencies for 'Package.swift' failed with: JsonParseException: Unrecognized token 'Fetching': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false')
 at [Source: (String)"Fetching https://github.com/vapor/websocket-kit.git from cache
Fetching https://github.com/apple/swift-log.git from cache
Fetching https://github.com/vapor/multipart-kit.git from cache
Fetched https://github.com/vapor/websocket-kit.git (0.71s)
Fetched https://github.com/vapor/multipart-kit.git (0.71s)
Fetched https://github.com/apple/swift-log.git (0.71s)
Fetching https://github.com/apple/swift-metrics.git from cache
Fetching https://github.com/apple/swift-nio-http2.git from cache
Fetching https"[truncated 16191 chars]; line: 1, column: 9]

I'm facing the same issue in Docker. However, it was working once, and fails now.
Another thing I noticed is, that if allowDynamicVersions is set to false in the ort.conf, no SPM project is detected.
ORT handles this as UnmanagedProject and the analysis succeeds with exit code 0.
This is handled differently, e.g. for NPM, which exists with exit code 2 and the message:
15:39:45.402 [DefaultDispatcher-worker-3] ERROR org.ossreviewtoolkit.analyzer.managers.Npm - Resolving NPM dependencies for 'package.json' failed with: IllegalArgumentException: No lockfile found in '.'. This potentially results in unstable versions of dependencies. To support this, enable the 'allowDynamicVersions' option in 'ort.conf'.

@MarcelBochtler I have updated the behavior when analyzing Package.swift without allowDynamicVersions set to true to throw IllegalArgumentException (just like NPM does). I have also written an additional test case for that.
The error message looks like this now:
15:08:55.864 [DefaultDispatcher-worker-3] ERROR org.ossreviewtoolkit.analyzer.managers.SPM - Resolving SPM dependencies for 'Package.swift' failed with: IllegalArgumentException: Resolving SPM dependencies from Package.swift might result in potentially unstable versions of dependencies. To support this, enable the 'allowDynamicVersions' option in 'ort.conf'.

About "failing to analyze vapor project locally" - How are you spinning up your container? The following works fine for me.
docker run -v /opt/vapor:/vapor ort -P ort.analyzer.allowDynamicVersions=true --info analyze -i /vapor -o /vapor/ort-out --package-managers SPM
13:04:18.258 [main] INFO  org.ossreviewtoolkit.model.config.OrtConfiguration - Using ORT configuration arguments:
  ort.analyzer.allowDynamicVersions=true
________ _____________________
\_____  \\______   \__    ___/ the OSS Review Toolkit, version 1f7e11dbb1.
 /   |   \|       _/ |    |
/    |    \    |   \ |    |    Running 'analyze' under Java <IP_ADDRESS> on Linux with
\_______  /____|_  / |____|    6 CPUs and a maximum of 1948 MiB of memory.
        \/       \/
Environment variables:
ORT_CONFIG_DIR = /root/.ort/config
ORT_DATA_DIR = /root/.ort
JAVA_HOME = /opt/java/openjdk
ANDROID_HOME = /opt/android-sdk
GOPATH = /tmp/go

Looking for analyzer-specific configuration in the following files and directories:
  /root/.ort/config/curations.yml (does not exist)
  /root/.ort/config/curations (does not exist)
  /vapor/.ort.yml (does not exist)
  /root/.ort/config/resolutions.yml (does not exist)
The following package managers are activated:
  SPM
Analyzing project path:
  /vapor
13:04:18.920 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/swift-crypto/.git' as it is hard-coded to be ignored.
13:04:18.933 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/async-http-client/.git' as it is hard-coded to be ignored.
13:04:18.990 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/swift-nio-ssl/.git' as it is hard-coded to be ignored.
13:04:18.993 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/websocket-kit/.git' as it is hard-coded to be ignored.
13:04:19.023 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/swift-nio-http2/.git' as it is hard-coded to be ignored.
13:04:19.029 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/swift-backtrace/.git' as it is hard-coded to be ignored.
13:04:19.033 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/swift-metrics/.git' as it is hard-coded to be ignored.
13:04:19.039 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/console-kit/.git' as it is hard-coded to be ignored.
13:04:19.041 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/routing-kit/.git' as it is hard-coded to be ignored.
13:04:19.047 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/multipart-kit/.git' as it is hard-coded to be ignored.
13:04:19.056 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/swift-nio-extras/.git' as it is hard-coded to be ignored.
13:04:19.060 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/async-kit/.git' as it is hard-coded to be ignored.
13:04:19.064 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/swift-nio-transport-services/.git' as it is hard-coded to be ignored.
13:04:19.099 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/swift-nio/.git' as it is hard-coded to be ignored.
13:04:19.103 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.build/checkouts/swift-log/.git' as it is hard-coded to be ignored.
13:04:19.144 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/vapor/.git' as it is hard-coded to be ignored.
Found 1 SPM definition file(s) at:
  Package.swift
Found 1 definition file(s) from 1 package manager(s) in total.
13:04:19.290 [DefaultDispatcher-worker-3] INFO  org.ossreviewtoolkit.analyzer.managers.SPM - Resolving SPM dependencies for 'Package.swift'...
13:04:19.526 [DefaultDispatcher-worker-3] INFO  org.ossreviewtoolkit.utils.core.OrtAuthenticator - Authenticator was successfully installed.
13:04:19.555 [DefaultDispatcher-worker-3] INFO  org.ossreviewtoolkit.utils.core.OrtProxySelector - Proxy selector was successfully installed.
13:04:19.724 [DefaultDispatcher-worker-3] INFO  org.ossreviewtoolkit.utils.core.OrtAuthenticator - Authenticator is already installed.
13:04:19.725 [DefaultDispatcher-worker-3] INFO  org.ossreviewtoolkit.utils.core.OrtProxySelector - Proxy selector is already installed.
13:04:23.234 [DefaultDispatcher-worker-3] INFO  org.ossreviewtoolkit.utils.common.ProcessCapture - Running 'swift package show-dependencies --format json' in '/vapor'...
13:04:28.767 [DefaultDispatcher-worker-3] INFO  org.ossreviewtoolkit.analyzer.managers.SPM - Resolving SPM dependencies for 'Package.swift' took 9.457754970s.
Found 1 project(s) and 15 package(s) in total (not counting excluded ones).
Applied 0 curation(s) from 1 provider(s).
Writing analyzer result to '/vapor/ort-out/analyzer-result.yml'.
Resolved issues: 0 errors, 0 warnings, 0 hints.
Unresolved issues: 0 errors, 0 warnings, 0 hints.

Could you please provide me with a command that you used to spin up the Docker container? Cheers

Many thanks for this PR.
I rebased it locally on latest master and despite some smaller conflicts SPM.kt needs to change a bit:
Index: analyzer/src/main/kotlin/managers/SPM.kt
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/analyzer/src/main/kotlin/managers/SPM.kt b/analyzer/src/main/kotlin/managers/SPM.kt
--- a/analyzer/src/main/kotlin/managers/SPM.kt	(revision ba8f429187caf50d54ecb5ef71ee804db148deaf)
+++ b/analyzer/src/main/kotlin/managers/SPM.kt	(date<PHONE_NUMBER>414)
@@ -24,6 +24,8 @@
 import com.fasterxml.jackson.databind.JsonNode
 import com.fasterxml.jackson.databind.ObjectMapper

+import org.apache.logging.log4j.kotlin.Logging
+
 import java.io.File
 import java.net.URI

@@ -45,8 +47,7 @@
 import org.ossreviewtoolkit.model.orEmpty
 import org.ossreviewtoolkit.model.utils.DependencyGraphBuilder
 import org.ossreviewtoolkit.utils.common.ProcessCapture
-import org.ossreviewtoolkit.utils.core.log
-import org.ossreviewtoolkit.utils.core.normalizeVcsUrl
+import org.ossreviewtoolkit.utils.ort.normalizeVcsUrl

 interface SPMCLIExecutor {
     fun executeSwift(definitionFile: File): JsonNode
@@ -61,7 +62,7 @@
     analyzerConfig: AnalyzerConfiguration,
     repoConfig: RepositoryConfiguration,
     private val cliExecutor: SPMCLIExecutor
-) : PackageManager(name, analysisRoot, analyzerConfig, repoConfig) {
+) : PackageManager(name, analysisRoot, analyzerConfig, repoConfig), Logging {

     private val graphBuilder = DependencyGraphBuilder(SPMDependencyHandler())

@@ -80,7 +81,7 @@
             analysisRoot: File,
             analyzerConfig: AnalyzerConfiguration,
             repoConfig: RepositoryConfiguration
-        ) = SPM(managerName, analysisRoot, analyzerConfig, repoConfig, this)
+        ) = SPM(MANAGER_NAME, analysisRoot, analyzerConfig, repoConfig, this)
     }

     abstract class SPMDependency(private val repositoryURL: String) {
@@ -111,7 +112,7 @@
     ) : SPMDependency(repositoryURL) {

         override fun getVCSInfo(): VcsInfo {
-            val vcsInfoFromUrl = VcsHost.toVcsInfo(repositoryURL)
+            val vcsInfoFromUrl = VcsHost.parseUrl(repositoryURL)

             if (vcsInfoFromUrl.revision.isBlank()) {
                 return vcsInfoFromUrl.copy(revision = version)
@@ -149,7 +150,7 @@
         }

         override fun getVCSInfo(): VcsInfo {
-            val vcsInfoFromUrl = VcsHost.toVcsInfo(repositoryURL)
+            val vcsInfoFromUrl = VcsHost.parseUrl(repositoryURL)
             if (vcsInfoFromUrl.revision.isBlank() && !state?.revision.isNullOrBlank()) {
                 return vcsInfoFromUrl.copy(revision = state!!.revision!!)
             }
@@ -261,14 +262,14 @@

         fun parseAuthorAndProjectFromRepo(repositoryURL: String): Pair<String?, String?> {
             val normalizedURL = normalizeVcsUrl(repositoryURL)
-            val vcsHost = VcsHost.toVcsHost(URI(normalizedURL))
+            val vcsHost = VcsHost.fromUrl(URI(normalizedURL))
             val project = vcsHost?.getProject(normalizedURL)
             val author = vcsHost?.getUserOrOrganization(normalizedURL)
             if (author.isNullOrBlank()) {
-                log.warn { "Unable to parse author name from $repositoryURL VCS URL. Results might be incomplete" }
+                logger.warn { "Unable to parse author name from $repositoryURL VCS URL. Results might be incomplete" }
             }
             if (project.isNullOrBlank()) {
-                log.warn { "Unable to parse project name from $repositoryURL VCS URL. Results might be incomplete" }
+                logger.warn { "Unable to parse project name from $repositoryURL VCS URL. Results might be incomplete" }
             }

             return author to project

I rebased it locally on latest master and despite some smaller conflicts SPM.kt needs to change a bit:

Thanks @tobiasKaminsky! There's also a newer version of this PR at #6114. Would you be willing to help @MarcelBochtler to move that one forward?
I'll close this PR in favor of the mentioned #6114 to avoid confusion.


Storage limits

None of the database limits pages has any mention about storage. Which could lead someone to believe there is no max.
In order to find the difference storage max, I had to use the Pricing Calculator.

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

ID: 528deb7f-fe1c-f2af-68b3-18d74eb570d4
Version Independent ID: 81880132-cf30-f913-3555-d78897f76611
Content: Azure SQL Database server resource limits
Content Source: articles/sql-database/sql-database-resource-limits-database-server.md
Service: sql-database
Sub-service: single-database
GitHub Login: @CarlRabeler
Microsoft Alias: carlrab

@tikicoder Thank you for the feedback.
This issue is being assigned to the content author to evaluate and update as appropriate.

@KalyanChanumolu-MSFT please assign to @stevestein

Apologies i may have opened a duplicate ticket - https://github.com/MicrosoftDocs/azure-docs/issues/33052
Looking at the Pricing Calculator, i could not see the limits to go up as high as 8TB (as per the link with reference to 8TB limit - https://docs.microsoft.com/en-us/azure/sql-database/sql-database-paas-vs-sql-server-iaas)

Upon further searches, i found this doc that specifies detailed storage limits.
https://docs.microsoft.com/en-au/azure/sql-database/sql-database-dtu-resource-limits-single-databases#single-database-storage-sizes-and-compute-sizes
At least linking to this page would be useful.

@dr-ivan I agree that adding a link to the limits for databases (single or pooled) would be useful. This page is focused on server-level limits for single and pooled databases, for which there are no storage limits. There is a work item in our queue to add this link. FYI - you can also add the link directly by clicking the edit button in the upper right section of the rendered page.
Cheers,
Carl

@dr-ivan I had some time at lunch so I just submitted the change
https://github.com/MicrosoftDocs/azure-docs/compare/master...tikicoder:patch-1
I tried to base it off the change request I did with MySQL
https://docs.microsoft.com/en-us/azure/mysql/concepts-limits#storage-engine-support

@tikicoder - Hi Ron, thanks for submitting the change directly into the doc. I just commented on your PR with a small edit. Because we're fixing in your PR I'm going to close this issue.
Thanks!

#please-close


Using API in swift code.

Is it possible to use this API in native desktop application?
So far I see that I have to create separate nodejs process in order to communicate with sketch.

That's not possible no. From Swift you can create a plugin and run it on the fly using sketchtool tho


Sidecar fails when A8_SERVICE env variable is not set

If the A8_SERVICE is not set, the nginx process fails to create the Amalgam8 lua object and then most of the calls to nginx fail with a nil pointer exception. A special validity check (including user-friendly error message) for the A8_SERVICE is required on startup.

The sidecar allows the user to provide command line arguments and/or env variables (e.g. --service or A8_SERVICE), but the nginx requires the user to provide ONLY env variables (nginx does NOT read the command line arguments of the sidecar). We need to either convert the command line arguments to env variables on the sidecar or to disable the command line arguments on the sidecar.

@zachidan
(2) is a real problem. Sidecar needs to set the A8_SERVICE environment variable before forking nginx.


Updated to comply with EGA images

Describe the pull request:

[ ] Bug fix
[X] Functional change
[ ] New feature
[ ] Code cleanup
[ ] Build system change
[X] Documentation change
[ ] Language translation

Pull request long description:

Updates init script to be up to date with  v0.0.1 of the EGA-archive Docker images.
Changes made:

Separate db_user/password for in and out.
Separate users/passwords for CEGA MQ and Users services.
Added MQ password hash to trace file.
Removed MQ config files.

Related issues:

Additional information:

Release note:

Documentation change:

Mentions:

@jbygdell Looks good to me. We might want to rebase to master before merging? There are some old changes present in this PR.

@jonandernovella not according to my git history.

@jbygdell Right. I thought we fixed the README with the S3 variable names in the previous PR. Then it's good to go!


Dynamic Seccomp Profiles based on Cluster-level rules to Enforce syscalls

What would you like to be added:
Custom seccomp profiles could be dynamically modified to always allow specific system calls.
The always allowed system calls would be low risk/impact and built into the operator.
Why is this needed:
Some essential system calls (e.g. exit, exit_group) can be left out of seccomp profiles leading to containers being caught up on endless exit loops, as reported here. This is a non-deterministic behaviour, meaning that the same profile and container combination may have the issue in one kernel/platform, and not have it in another.

Sounds good! How would an API look like?

/remove-lifecycle stale

/remove-lifecycle stale


Update cspsplit.py for v2

I've been trying to parse the fields of a v2 header. I've updated the cspsplit.py script to what I believe should work with v2 headers but I'm still not getting accurate values. Below is my code with new shift/bitmask values:
    print("Priotity:         {0}".format((hdrhex >> 46) & 0x03))
    print("Source:           {0}".format((hdrhex >> 32) & 0x3fff))
    print("Destination:      {0}".format((hdrhex >> 18) & 0x3fff))
    print("Destination port: {0}".format((hdrhex >> 12) & 0x3f))
    print("Source port:      {0}".format((hdrhex >> 6) & 0x3f))
    print("HMAC:             {0}".format("Yes" if ((hdrhex >> 3) & 0x01) else "No"))
    print("RDP:              {0}".format("Yes" if ((hdrhex >> 1) & 0x01) else "No"))
    print("CRC32:            {0}".format("Yes" if ((hdrhex >> 0) & 0x01) else "No"))

Does this look correct?

I belive the problem is with the implementation. It casts the content of the sys.argv into an int() it should have been a 64-bit datatype.


QUESTION: How does a user request a new confirmation email?

Preferably, it would be nice from a user's standpoint to automatically send them a new confirmation email if they try to log in but their account isn't confirmed.

i think we should provide an endpoint that let's users request a new confirmation mail.
for now, phoenix_token_auth doesn't handle this at all.


datapath/linux: document methods that must be called with mutex held

Follow-up for #12461 per review comment
https://github.com/cilium/cilium/pull/12461#discussion_r452103203
Suggested-by: Tam Mach<EMAIL_ADDRESS>/cc @sayboras

Coverage increased (+0.03%) to 36.958% when pulling b4bba4986ef2aca1d4a919134971ff1692d0260e on pr/tklauser/neighbynode-mutex-comment into 9fe5b33a55decb598b78a5d3a8706c53c03782a0 on master.

Only comment changes, so I'm marking this as ready to merge.


Don't trim MQBYTES fields to last non-null char

Just return a Ruby string that's always the same length as the MQ field.
We might want to retrieve a binary value where a trailing null byte is significant.

I can't see where this macro is used, but the change makes sense to me.

Ah yeah, the code that uses it is generated during build


⚠ Bofrost.be has degraded performance

In a9e68ab, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1554 ms

Resolved: Bofrost.be performance has improved in dc0e4a7 after 6 minutes.


Expressing a contractual promise to accept null (categorically or conditionally): a requirement for 1.0?

This is intended to be a new framing and starting point for the same issue recently discussed under the headings "the specification for nullable", "semantics of nullable", "specifying predicate nullness", etc. Like other issues, it can move into a document IF that proves necessary.
I am hopeful that everyone can accept this particular framing of the issue -- or give a clear argument for why a different framing will help us move forward better.
If the framing appears too much to predestine a particular decision, that could happen because it's a good decision, but it might also just mean we need to add the next layer onto the model ("Now, here's where this breaks down"). But, crossing fingers that we won't just throw it out. Enough said by now.
THIS IS ABOUT 1.0
I think it is best to frame this as a requirements question for 1.0, specifically. The outcome I think we seek is a decision between listing this feature area as an explicit requirement, or listing it as an explicit non-requirement-for-now.
Please note that discussion of how we would design the feature is usually not relevant to such a decision -- but, in cases, elements of that discussion can come into play.
A "yes, make it a 1.0 requirement" answer means more work for us, but I can think of three [four] basic reasons for deciding "yes":

We judge the combined risk to be high that we will both (a) want to add the feature post-1.0, and (b) find that our 1.0 design decisions have prevented us from doing so.

We judge that too many libraries may not see the product as even worth adopting without the feature, and our 1.0 release will fizzle as a result.

Multiple partners believe they will feel compelled to proceed independently on this, in a way that could cause appreciable and harmful fracturing, yet it would be unreasonable to do it as a separate complementary project.

[Edit, thanks @lazaroclapp] Even one partner is forced to conclude they can't use our annotations profitably at all (not even by way of @Implies (#35)), or that what their users need to do is too painful.

WHAT WE'RE NOT DEBATING
The basic task I think we're all signed up for is to separate "nullable Foo" from "non-nullable Foo" as types, allowing appearances of the Foo type in APIs to signify their null-inclusion intentions. (Let's sidestep "unspecified" as a mostly orthogonal distraction here.)
The most important effect of this type separation is that tools can treat dereferencing as if it is an operation belonging to the non-nullable type only.
By analogy, we might imagine that we can create a new subtype of String called NonEmptyString, and arrange that all values of the String type except for "" will always have this new type. Some operations, like char firstChar(), would belong only to the new subtype. Methods can now choose to require the subtype to be passed in. A method can promise never to return "" simply by changing its return type to NonEmptyString (even if its supermethod doesn't).
For any community plagued with EmptyStringException stack traces, it doesn't seem a tall claim to say that this much would already make a big difference. That exception wouldn't disappear entirely, but we wouldn't expect it to, because types only do so much.
The part of our work that is (I hope) non-controversial is just this type bifurcation (really, trifurcation) part.
WHAT (I THINK) WE ARE DEBATING
Methods have contracts with many more nuances than their type signatures alone can convey. For example, using the NonEmptyString analogy, a method must accept String so long as there exists any circumstance in which "" is valid. But it has never (officially) had a way to express in its contract what these circumstances are, or even the basic fact of whether it pledges to definitely accept that value. It's only if it will never accept the value that adopting NonEmptyString gives it a path forward.
CAVEAT ABOUT THE ANALOGY
Analogies can always be seen as trivializing. In real life, there is no big problem with EmptyStringException but there is a huge problem with NullPointerException. The analogy is not meant to suggest a lower importance of solving these use cases.
BACKGROUND
This issue is attempting to serve as the new starting point for the questions raised here:
First thread
Werner's doc
Lazaro's doc

I am claiming that it is fair to treat this as a question of whether to add a new requirement to the project. As such, it has a clear base option -- unless argued successfully otherwise, it is by default not in scope.
I think that the the three criteria above are an appropriate map for crafting an argument to add the requirement. Does anyone want to put forth and champion that argument?
If not, we should state it as a non-requirement and close this issue for now.

tl;dr: I am fine with this not being a requirement for 1.0 iff this is not a requirement for CF to use jspecify annotations in a way consistent with other tools.
SIDE NOTE ON THE ANALOGY
I still feel the analogy doesn't resolve the question, because both the nullness type system and the string-emptiness type system are clear when all code is checked against those type systems, and have similar issues when some methods are expected to use those types for their signature but not have their implementation type-checked. In theory you could say that a non-type-checked method and one that does an explicit (NonEmptyString) s cast are equivalent, but I still feel that there is a difference. For a proper analogy, the difficulties of the docs above would arise when retrofitting String/NonEmptyString into the JDK API signatures (e.g. via a jdk.stub like the one used by CF), just the same as when adding nullability info to those same APIs without changing their code.
BUT... that's besides the point. I think we agree in the choices we have, and the requirements in tension, I am just not sure the analogy really argues for one decision or the other.
PROPOSED DECISION CRITERIA
I think the fundamental criteria I would like to take this choice based on is this: Can jspecify 1.0 be reasonably used by sound/sounder tools like the Checker Framework, perhaps by augmenting its annotations with special case @Contract/@Precondition/@Postcondition annotations that are seldom needed?
If such tool would need a @ReallyNullableIMeanIt annotation to go along with @Nullable even 30% of the time, then that's a big red flag for jspecify's generality for me.
MY TAKE
My most recent discussions with Werner seem to indicate that the above worst case is not true, and that CF can make some reasonable use of jspecify 1.0 with binary+unspecified nullability. I'd let him and Michael pitch in, but if they don't have a strong objection, neither do I.
Just to clarify, if I am solely acting on behalf of the NullAway project and/or Uber, then we are perfectly happy to use the existing @Nullable/@NonNull semantics, at least in regards to the issue under discussion. I just want the Checker Framework folks to also be happy with the outcome here, since that improves the chances of jspecify becoming "The Standard" (tm)
All this with the caveat that post-1.0 it does seem like a good idea to have some mechanism to specify conditional nullability, since both CF and NullAway, as well as (I believe) IntelliJ, arrived to something related in their design at some point :)

This may be subtle, but I really am trying not to use the analogy as if it is an argument in and of itself. Just a mental model for what it means to perform the kind of type bifurcation we are doing. And you're right that it does not account for the issue of unchecked code, and in fact my own thought processes are still highly undeveloped (and so you've had to try to bring that perspective numerous times). I plan to follow up separately about that.
Next, thanks very much for reminding us that even if we don't have this 1.0 requirement, we still have a requirement to support a product that does take on the requirement. It is hard to make what that means very concrete, but it must feel like that product is able to build on to what we specify rather than having to cast it aside. That is important, I believe.

Lazaro, I've just filed #115 to try to get some clarification on how we should treat issues unique to unchecked code.

I think we can consider this decided (NOT a requirement) unless/until new information comes to light.


frameConfigurationHandler problem with keyboard

Hi,
I am using frameConfigurationHandler to align my presented view to the bottom of the screen like this:
        formSheetController.presentationController.frameConfigurationHandler = ^(UIView *presentedView, CGRect currentFrame) {
            return CGRectMake(currentFrame.origin.x, weakSelf.view.frame.size.height - currentFrame.size.height, currentFrame.size.width, currentFrame.size.height);
        };

At the same time this view aligned to the bottom contains 2 input TextFields so I am also setting movementActionWhenKeyboardAppears
formSheet.presentationController.movementActionWhenKeyboardAppears = MZFormSheetActionWhenKeyboardAppearsMoveToTopInset;

The problem is that when I tap the textField the keyboard covers the whole bottom view which doesn't slide up. I suppose it is a conflict between setting my custom frame and displaying keyboard.
Or am I doing something wrong?
Thanks :)

As you can see here: https://github.com/m1entus/MZFormSheetPresentationController/blob/master/MZFormSheetPresentationController/MZFormSheetPresentationController.m#L486 If you set frameConfigurationHandler then you are responsible for keyboard movement as well.

Thanks for your quick response. Would it be possible to adjust the library to pass the property keyboardVisible to the frameConfigurationHandler along with the self.presentedView and formSheetRect?
I think it makes sense because these 3 properties are the ones which define how the frame should display and the frameConfigurationHandler is called when the keyboard appears. Otherwise I would need to register for keyboard notifications which seems redundant if you are doing this in your code already.

Sure, that make sense, i also exposed isKeyboardVisible property in presentationController. Thanks.

I want to anchor the bottom of the form sheet to the top of the keyboard but don't know how to get the keyboard's frame (height specifically) without registering for notifications. Would it be possible to expose screenFrameWhenKeyboardVisible too?

use MZFormSheetActionWhenKeyboardAppearsAboveKeyboard on presentationController

I'm using .AlwaysAboveKeyboard because my Form Sheet is full screen.
Here are a few screenshots of what I mean:
Present VC in landscape, open keyboard in landscape:  (perfect!)

Present VC in landscape, open keyboard in portrait: (VC isn't moving up enough)

Present VC in portrait, open keyboard in landscape (VC is moving up too much)

What is the fixed for this ?


"Count only bosses" Not working after Archer Revamp Update

Seems they changed whatever identifier, or packet that you track for "bosses." If you could look into it, that'd be great. :)

No issues here with detecting bosses.  What are your settings and how is it "not working"?

Here's my listed settings. When entering a boss fight, the only way I can get the meter to register DPS with the "count only bosses" option enabled is well; by disabling it and letting it counting everything. Before this update it worked, maybe you've updated and I haven't seen it?
I'm using GI0's version <IP_ADDRESS>B.

Just rechecked, <IP_ADDRESS>B have no problems detecting bosses and counting only them. (It's quite outdated, works only on RU for now - better ask questions on RU forum/my issues page)

What do you mean it works only on RU?

Last time it was updated when RU received 30-raid patch. All other regions received new patches later.
One of the things that changed (except new skills/monsters/abnormals) is structure of spawn npc packet. If you are using it on any region other than RU - it's outdated and can't detect any monster at all.


Fix entrypoint in package.json

Hello,
I updated the package.json to fix the entry point, the file in .cjs isn't build, so the library can't be used by some bundlers.

Can you release it?
Have a great day,
Maxime

Thank you!

v1.0.3 has been published.


Could not connect to your node with those details

After upgrading my raspiblitz, I should now be able to use juggernaut with it. But when I enter all the information, and click the save button, I get the error: "Could not connect to your node with those details"
I tried all three Macaroons that I got from the raspiblitz (admin, invoice, readonly).
I tried pasting the macaroon and tls cert as hex into the fields as well as scp from the raspi and enter the file names into the fields.
I was not sure what to use for port. So I tried with 10009, 8080, 9735 and without specifying a port.
Expected Behavior
It should establish a connection with the node.
Current Behavior
I get the error: "Could not connect to your node with those details"
Your Environment
Node: https://github.com/rootzoll/raspiblitz
RaspiBlitz v1.5
bitcoin v0.19.1
LND 0.9.2-beta
The public address of the lightning node is an onion address
Accept Keysend is enabled
Client: Ubuntu 18.04
Juggernaut-linux-x86_64-v0.1.1.AppImage
Both on the same subnet

same here, lnd 0.10.99-beta

same issue. Tried in both LNDCONNECT and manual. lnd 0.10.99-beta. worked fine previously.

Same here
First installation
RaspiBlitz V 1.5
lnd 0.10.0 beta

same here, with mynodebtc it works, just copy the LNDCONNECT file and is immediately on, with raspiblitz seem more complicate to set up (manual) and I didn't manage to do it

I have manage to connect the raspiblitz to Juggernaut with the file lndconnect, my file was pointing the wrong address (the external IP) I have correct it manually with mine at the beginning, I have found that also with zap didn't work for the same issue.
Example here of the beginning of the lndconnect file:
lndconnect://X.XXX.XXX.X:10009?cert=.... to change with lndconnect://<IP_ADDRESS>:10009?cert=
(i change my public ip with the XXX for privacy)

I have manage to connect the raspiblitz to Juggernaut with the file lndconnect, my file was pointing the wrong address (the external IP) I have correct it manually with the internal IP assigned to the raspi at the beginning, I have found that also with zap didn't work for the same issue.
Example here of the beginning of the lndconnect file:
lndconnect://X.XXX.XXX.X:10009?cert=.... to change with lndconnect://<IP_ADDRESS>:10009?cert=
(i change my public ip with the XXX for privacy)

Local IP gives same error for me. I am happy it worked for you though!

also cannot connect.
$ lnd --version
lnd version 0.10.99-beta commit=clock/v1.0.0-229-ge64e71d86dc1ac716c30a80f85a22e8fb544697f

I found out the issue was that the hostname I was using was not in the tls.cert file. working ok now with an included hostname.
You can list them with the following command.
sed -ne 's/^\( *\)Subject:/\1/p;/X509v3 Subject Alternative Name/{N;s/^.*\n//;:a;s/^\( *\)\(.*\), /\1\2\n\1/;ta;p;q; }' < <(openssl x509 -in ~/.lnd/tls.cert -noout -text)

Error connecting on the latest lnd master.
$ lnd --version
lnd version 0.11.99-beta commit=v0.11.0-beta-83-g751b02361e53a56d3eb56085342c5d6dcc7d928c

Failed to launch node
Please make sure you are connected to the internet and your node is online

Same issue persists using myNode and trying every conceivable connection script. I have to assume this project is dead for now, at least...as this critical issue has been open for 6 months, and that's about how long it appears since there's been any updates or merges in the repo.
Really too bad.....unless something new/improved is about to be unveiled. This was a great idea that worked well early on.


Asset type "json" fails

Using an asset type of "json" instead of "csv" does not work.
In the manger log:
ERROR	controller-runtime.manager.controller.m4dapplication	Reconciler error	{“reconciler group”: “app.m4d.ibm.com”, “reconciler kind”: “M4DApplication”, “name”: “heir-notebook”, “namespace”: “heir-mvp”, “error”: “get dataset info from katalog failed: rpc error: code = Unknown desc = the server could not find the requested resource (get assets.katalog.m4d.ibm.com diabetes-json”)“, “errorVerbose”: “rpc error: code = Unknown desc = the server could not find the requested resource (get assets.katalog.m4d.ibm.com diabetes-json”)
In the katalog-connector log:
In GetDatasetInfo: asset namespace is “heir-mvp asset name is diabetes-json”
2021/07/19 07:52:21 In GetDatasetInfo: asset namespace is “heir-mvp asset name is diabetes-json”

Not able to reproduce.

probably not...


⚠ gorzdrav.org has degraded performance

In 0518bcf, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 2105 ms

Resolved: gorzdrav.org performance has improved in d853f21.


Error installing torch==1.10.1 in Colab notebook

I am encountering an error while trying to install torch==1.10.1 in a Colab notebook. The specific command I am using is !pip install torch==1.10.1 torchvision==0.11.2. However, I am getting the following error message:
yaml
Copy code
ERROR: Could not find a version that satisfies the requirement torch==1.10.1 (from versions: 1.11.0, 1.12.0, 1.12.1, 1.13.0, 1.13.1, 2.0.0, 2.0.1)
ERROR: No matching distribution found for torch==1.10.1
I need assistance in resolving this issue so that I can successfully install torch==1.10.1 in my Colab notebook.
Steps to reproduce the issue:
Create a new Colab notebook.
Execute the command !pip install torch==1.10.1 torchvision==0.11.2.
Expected result:
The command should successfully install torch==1.10.1 and torchvision==0.11.2 without any errors.
Actual result:
The installation fails with the error message mentioned above.
Additional information:
I have already tried specifying other versions of the torch, but the error persists.
The Colab notebook environment has internet access.
Any assistance or insights to resolve this issue would be greatly appreciated. Thank you!

#having a similar problem
The conflict is caused by:
    pytorchwildlife <IP_ADDRESS> depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS> depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS> depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS> depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS>.1 depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS> depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS> depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS> depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS> depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS> depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS> depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS> depends on torch==1.10.1
    pytorchwildlife 1.0.1 depends on torch==1.10.1
    pytorchwildlife 1.0.0 depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS>.2 depends on torch==1.10.1
    pytorchwildlife <IP_ADDRESS>.1 depends on torch==1.10.1
    pytorchwildlife 0.0.1 depends on torch==1.10.1
    pytorchwildlife 0.0.0 depends on torch==1.10.1
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict


[Bug]: False positive on ec2_securitygroup_allow_ingress_from_internet_to_any_port

Steps to Reproduce
prowler --checks ec2_securitygroup_allow_ingress_from_internet_to_any_port --verbose
Expected behavior
No findings
Actual Result with Screenshots or Logs
Security group <redacted> (sg-abc123) has all ports open to the Internet.

How did you install Prowler?
Cloning the repository from github.com (git clone)
Environment Resource
EKS
OS used
Amazon Linux 2
Prowler version
3.5.3
Pip version
23.1.2
Context
Here is the security group in question. It has ports 80 and 443 open for ingress, and all egress traffic is allowed:
{
    "SecurityGroups": [
        {
            "Description": "Managed SecurityGroup for LoadBalancer",
            "GroupName": "<redacted>",
            "IpPermissions": [
                {
                    "FromPort": 80,
                    "IpProtocol": "tcp",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0",
                            "Description": ""
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "ToPort": 80,
                    "UserIdGroupPairs": []
                },
                {
                    "FromPort": 443,
                    "IpProtocol": "tcp",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0",
                            "Description": ""
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "ToPort": 443,
                    "UserIdGroupPairs": []
                }
            ],
            "OwnerId": "<redacted>",
            "GroupId": "sg-<redacted>",
            "IpPermissionsEgress": [
                {
                    "IpProtocol": "-1",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0"
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "UserIdGroupPairs": []
                }
            ],
            "VpcId": "vpc-<redacted>"
        },
    ]
}

Good catch @kenske , thank you!!
We've just fixed this issue and will be available in the next release.

Hi,
I can see this was fixed in 3.6.0 last year but I'm seeing the same issue in Prowler version 4.3.5.
I have a security group with ports 80 and 443 open for ingress, and all egress traffic is allowed:
{
    "SecurityGroups": [
        {
            "Description": "Foo",
            "GroupName": "<redacted>",
            "IpPermissions": [
                {
                    "FromPort": 80,
                    "IpProtocol": "tcp",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0"
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "ToPort": 80,
                    "UserIdGroupPairs": []
                },
                {
                    "FromPort": 443,
                    "IpProtocol": "tcp",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0"
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "ToPort": 443,
                    "UserIdGroupPairs": []
                }
            ],
            "OwnerId": "<redacted>",
            "GroupId": "sg-<redacted>",
            "IpPermissionsEgress": [
                {
                    "IpProtocol": "-1",
                    "IpRanges": [
                        {
                            "CidrIp": "<IP_ADDRESS>/0"
                        }
                    ],
                    "Ipv6Ranges": [],
                    "PrefixListIds": [],
                    "UserIdGroupPairs": []
                }
            ],
            "Tags": [
                {
                    "Key": "Name",
                    "Value": "<redacted>"
                }
            ],
            "VpcId": "vpc-<redacted>"
        }
    ]
}

which is the same as the one above.
which results in a Prowler finding off:
Details

ResourceUid:
arn:aws:ec2:eu-west-2:<redacted>:security-group/sg-<redacted>

FindingUid:
prowler-aws-ec2_securitygroup_allow_ingress_from_internet_to_any_port-<redacted>-eu-west-2-sg-<redacted>

CheckId:
ec2_securitygroup_allow_ingress_from_internet_to_any_port

Type:
AwsEc2SecurityGroup

Details:
<redacted>

StatusExtended:
Security group <redacted>- (sg-<redacted>) has at least one port open to the Internet and neither its network interface type (interface) nor its network interface instance owner (<redacted>) are part of the allowed network interfaces.

Risk:
If Security groups are not properly configured the attack surface is increased.

Notes:

Provider:
aws

Recomendation:
Use a Zero Trust approach. Narrow ingress traffic as much as possible. Consider north-south as well as east-west traffic.

RecomendationUrl:
https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html

Scan Day:
2024-09-20


trealla: 1.9.37 -> 1.12.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/trealla/versions.
meta.description for trealla is: "A compact, efficient Prolog interpreter written in ANSI C"
meta.homepage for trealla is: "https://github.com/infradig/trealla"
meta.changelog for trealla is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/pwmkp9x2qsggkck5qm9hd5kv49sw6mjs-trealla-1.12.0/bin/tpl passed the binary check.

1 of 1 passed binary check by having a zero exit code.

0 of 1 passed binary check by having the new version present in output.

found 1.12.0 with grep in /nix/store/pwmkp9x2qsggkck5qm9hd5kv49sw6mjs-trealla-1.12.0

found 1.12.0 in filename of file in /nix/store/pwmkp9x2qsggkck5qm9hd5kv49sw6mjs-trealla-1.12.0

directory tree listing: https://gist.github.com/c1c71ce9f8cb6bc4fcca63e046947d0b

du listing: https://gist.github.com/b8e94a5326dc43b9f24b17183c8a62a9

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
trealla

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pwmkp9x2qsggkck5qm9hd5kv49sw6mjs-trealla-1.12.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A trealla https://github.com/r-ryantm/nixpkgs/archive/37ae37e8b783517b96516e415164e608a888249d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pwmkp9x2qsggkck5qm9hd5kv49sw6mjs-trealla-1.12.0
ls -la /nix/store/pwmkp9x2qsggkck5qm9hd5kv49sw6mjs-trealla-1.12.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

trealla

Maintainer pings
cc @siraben for testing.

Result of nixpkgs-review pr 137706 run on x86_64-darwin 1

1 package built:

trealla


pull request for e2e test at 11/17/2016 11:26:03

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[WIP][CARBONDATA-2753] Fix Compatibility issues

Problems:
(1) CarbonTable is not refreshed in the executor side with the tableproperties.
(2) filterValues are null in case of old store.
Solution:
(1) Set the dictionary path to the AbsoluteTableIdentifier, so that we can get the dictionary path if needed.
(2) Currently filterValues filling is based on the local dictionary, if the format is not V3 then the filterValues should be reassigned with the filterKeys from the ExecutorInfo.

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[x] Testing done
Manual Testing

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6087/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7320/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6093/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7326/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7331/

retest this please

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6096/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7337/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6101/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7350/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5933/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6114/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7353/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6117/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7358/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7362/

retest this please

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6123/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5937/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7369/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5938/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6130/

retest this please

retest this please

retest sdv please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7374/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6135/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5947/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7399/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6159/

retest sdv please

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5973/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7449/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6206/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7459/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5981/

Retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7471/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6224/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6228/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7481/

LGTM

LGTM

LGTM

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5990/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6238/


Add LiveReload Instructions to README

I figured others were probably wondering how to get LiveReload enabled for this app, so I just went ahead and added a quick summary on how to do so. Hope this is helpful to you all!

Thanks!


Enabling samples with the parameters library

http://intel-ci.intel.com/ee4bd4f0-795f-f16f-95e4-a4bf010d0e2e

What is the meaning of this PR with no sample using parameters?

What is the meaning of this PR with no sample using parameters?

Fixing our nightly CI failures.


fixed typo

Sorry to bother but just realized a typo in my contribution. now its fixed

sorry about all the commits
now github action will build the site using the my-site branch
thereby allowing users to fork the repo -> build their site -> and still fetch from original repo.
also they can cherry pick specific commit to master and then merge to original repo

This template is not a very stable version for now. So, we may do some changes that may change the variable name too.
If we changed the variable name, it couldn't not be changed in the user repo and it may lead the site down.
So, this pull request may not be good until the stable version out.

No worries
I was doubting this idea myself


[2851] New console config for bridge.json and tests

Fixes #2851
{
  "console": {
    "disabled": true
  }
}

Alternative syntax:
{
  "console": false
}

This is great news! :)

@ProductiveRage, sorry for buzzing, it would be super great if you have a chance to review https://forums.bridge.net/forum/bridge-net-pro/bugs/4434-combinescripts-and-resources-bridge-console-js-extract-false-doesn-t-exclude?p=4450#post4450

There's a lot here! Will read properly tomorrow :)
On 26 Jun 2017 3:26 pm, "Leonid Veriga"<EMAIL_ADDRESS>wrote:

@ProductiveRage https://github.com/productiverage, sorry for buzzing,
it would be super great if you have a chance to review
https://forums.bridge.net/forum/bridge-net-pro/bugs/
4434-combinescripts-and-resources-bridge-console-js-
extract-false-doesn-t-exclude?p=4450#post4450
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bridgedotnet/Bridge/pull/2870#issuecomment-311075122,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAtTzAee_UTCJBG7a-w0s55kStTS17uJks5sH7-BgaJpZM4OFW5w
.

The new console changes look great. Having read through that forum thread, I will make a change to the ProductiveRage.Immutable.Extensions library to ensure that it's not packaging JS files that it's not directly responsible for.

@ProductiveRage, I would consider it as a bug partially:

it is correct that it includes minified versions
it is NOT correct that it includes core (bridge.js etc) and resources from referenced dlls (Bridge.React.js etc)

This config
{
  "outputBy":  "Project",
  "fileName": "productiveRage.immutable.extensions.js"
}

should include the following resources:

productiveRage.immutable.extensions.js
productiveRage.immutable.extensions.min.js
productiveRage.immutable.extensions.meta.js
productiveRage.immutable.extensions.meta.min.js

So you would have to use "outputFormatting": "Formatted", to exclude min resources (if you don't need them), and the resources being included:

productiveRage.immutable.extensions.js
productiveRage.immutable.extensions.meta.js

@ProductiveRage, the issue with embedding outputs from referenced dlls addressed in PR #2906.

Having read through that forum thread, I will make a change to the ProductiveRage.Immutable.Extensions library to ensure that it's not packaging JS files that it's not directly responsible for.
Additionally, there is a new config option report  - if enabled it outputs a file listing resources being embedded into assembly (see  #2906.)

@LeonidVeriga I was thinking more about how these files are packaged into the DLLs - if the ProductiveRage.Immutable binary includes all of these:
productiveRage.immutable.extensions.js
productiveRage.immutable.extensions.min.js
productiveRage.immutable.extensions.meta.js
productiveRage.immutable.extensions.meta.min.js
And if I have a project that uses this NuGet package and specifies combineScripts: true, how does the build process know that it must only include one of "productiveRage.immutable.extensions.js" and "productiveRage.immutable.extensions.min.js"?

Given a project has combineScripts: true and its output has:

project.js

Given the project references Bridge.dll with:

bridge.js
bridge.meta.js

Given the project references a dll containing:

resource1.js
resource1.min.js
resource2.js
resource3.min.js

The project formatted output projectName.js will include:

bridge.js
bridge.meta.js
resource1.js
resource2.js
resource3.min.js (as is)
project.js

The project minified output projectName.min.js will include:

bridge.js (minified by Bridge)
bridge.meta.js (minified by Bridge)
resource1.min.js (as is)
resource2.js (minified by Bridge)
resource3.min.js (as is)
project.js (minified by Bridge)

I.e.:

resource1.js and resource1.min.js are considered as one resource item. Bridge uses an appropriate version depending on formatting option;
resource2.js goes into formatted output, if minified version required then Bridge mifies it;
resource3.min.js goes into both formatted and minified outputs as is.

@LeonidVeriga Thanks for that, it all sounds good.
One final question.. :) Are resource1.js and resource1.min.js "considered as one resource item" based solely upon their file names or is there some additional metadata in the DLL that contains them?

@ProductiveRage, no extra metadata, just resolving file names (additional settings may appear in resources config in future).

@ProductiveRage, just FYI, there are some changes coming for the new Report option - see PR #2920.
We find this option usefull to monitor which resources being included into your project assembly - if the report file (by default, bridge.report.log in project's output folder) is under source control then it is very easy to see the changes (it would show changes in consist and size).


[BIOMAGE-1450] Enable navigation for processed project

Background
Link to issue
https://biomage.atlassian.net/jira/software/c/projects/BIOMAGE/boards/1?modal=detail&selectedIssue=BIOMAGE-1450
Link to staging deployment URL
https://ui-grasp6-ui572.scp-staging.biomage.net/data-management
Links to any Pull Requests related to this
Anything else the reviewers should know about the changes here
Changes
Code changes
Definition of DONE
Your changes will be ready for merging after each of the steps below have been completed:
Code updates
Have best practices and ongoing refactors being observed in this PR

[ ] Migrated any selector / reducer used to the new format
[ ] Validated that current unit tests work as expected and are enough

Testing

[ ] Unit tests written
[ ] Tested locally with Inframock (with latest production data downloaded with biomage experiment pull)
[ ] Deployed to staging
[ ] Passed integration tests

To set up easy local testing with inframock, follow the instructions here: https://github.com/biomage-ltd/inframock
To deploy to the staging environment, follow the instructions here: https://github.com/biomage-ltd/biomage-utils
Documentation updates
Is all relevant documentation updated to reflect the proposed changes in this PR?

[ ] Relevant Github READMEs updated
[ ] Relevant wiki pages created/updated

Approvers

[ ] Approved by a member of the core engineering team
[ ] (UX changes) Approved by vickymorrison (this is her username, tag her if you need approval)

Just before merging:

[ ] After the PR is approved, the unstage script in here: https://github.com/biomage-ltd/biomage-utils is executed. This script cleans up your deployment to staging

Optional

[ ] Photo of a cute animal attached to this PR

Can you also enable the experiment name on the left side of the bar?

In the admin account I found a project named 'test mh ui' where the Go to Data Processing button is disabled with a message to ensure all data is uploaded and metadata is input. However, the navigation controls for the other modules are enabled on the left hand side. (See screenshot.) This should not happen - either both should be disabled or both should be enabled.

I also found one that is the other way about - project 'Test of Stefans PR' has the Go to Data Processing button enabled and yet the navigation controls on the left side are disabled. Again, this should not happen.

@vickymorrison  I believe the last screenshot is due to that the QC is not succeeded yet and this is why the left links are disabled

I'd change the wordings to:
You have made changes that require data to be processed again.
Would you like to discard these changes and navigate to the page using old data or re-run sample processing?
and the buttons :
Discard changes and continue
Re-run sample processing
what do you think @vickymorrison?

I see that the navigation menus are disabled when QC pipeline fails. Can you add tooltips to the navigation menu links which say "Data Processing failed. Click Go to Data Processing to continue." to let the user know they have to go to Data Processing and re-run the pipeline?
https://user-images.githubusercontent.com/2862362/145179945-d2c6f1aa-6ea1-470d-8db2-70f7cccfb4f5.mov