required-only with yarn3 doesn't exclude dev dependencies

I try to generate a SBOM including only required dependencies for my project with yarn3 and workspaces.
But it seems that the dev dependencies are listed in the bom file as well.
I noticed that yarn3 doesn't add a dev flag to dev dependencies in lockfile.
Is there any other way for cdxgen to filter devDependencies?
I run cdxgen like this: cdxgen --required-only -o bom.json
My yarn config:
compressionLevel: 0
enableGlobalCache: true
nmMode: hardlinks-local
nodeLinker: node-modules
plugins:
  - path<EMAIL_ADDRESS>    spec: "@yarnpkg/plugin-workspace-tools"
yarnPath: .yarn/releases/yarn-3.5.1.cjs

Example for a dev dependency in yarn.lock and bom.json
"wait-on@npm:^3.2.0":
  version: 3.3.0
  resolution: "wait-on@npm:3.3.0"
  dependencies:
    "@hapi/joi": ^15.0.3
    core-js: ^2.6.5
    minimist: ^1.2.0
    request: ^2.88.0
    rx: ^4.1.0
  bin:
    wait-on: bin/wait-on
  checksum: 1bc2cc53bb62887ae31822645771b526b7f65e304762cfd48a8f2cf563070c4b2198026b863bd48aad78d7e45687f6c23f7eb0de7969604dd1ed4993d12fa74e
  languageName: node
  linkType: hard

{
      "author": "",
      "publisher": "",
      "group": "",
      "name": "wait-on",
      "version": "3.3.0",
      "description": "",
      "hashes": [
        {
          "alg": "SHA-512",
          "content": "1bc2cc53bb62887ae31822645771b526b7f65e304762cfd48a8f2cf563070c4b2198026b863bd48aad78d7e45687f6c23f7eb0de7969604dd1ed4993d12fa74e"
        }
      ],
      "licenses": [],
      "purl"<EMAIL_ADDRESS>      "type": "library",
      "bom-ref"<EMAIL_ADDRESS>      "evidence": {
        "identity": {
          "field": "purl",
          "confidence": 1,
          "methods": [
            {
              "technique": "manifest-analysis",
              "confidence": 1,
              "value": "/home/michael/Projekte/app-mivao/yarn.lock"
            }
          ]
        }
      },
      "properties": [
        {
          "name": "SrcFile",
          "value": "/home/michael/Projekte/app-mivao/yarn.lock"
        }
      ]
    },

@qroac Thanks for reaching out. I will add this to my queue and get back to you.

cdxgen uses babel to detect used dependencies but looks like it is not working well here. Is it possible to share a test project with both the lock file and some code to replicate this problem?

@prabhu I think the example is for this repo.

Replicated using tesseract.

@prabhu and @cerrussell,
I picked wait-on as one example out of the list of dev-dependencies that was easy to find in the lockfile because no other package depends on it.
My project is based on this starter kit, I could reproduce the issue with the current code from the kit:
https://github.com/sysgears/apollo-universal-starter-kit/
You have to add -t js.
cdxgen tries to retrieve sbt.version from project/build.properties, that dont exist in the starter kit.

Any idea yet?
Could it be a required configuration for babel?

@qroac, could you test with the PR branch https://github.com/CycloneDX/cdxgen/pull/475
git checkout https://github.com/CycloneDX/cdxgen
git checkout fix/issue-469
npm install
node bin/cdxgen.js -t js --required-only <path>

Sorry, I missed the notification on your comments in my mailbox.
The PR branch is no longer available but is merged with master, so I tested with master.
My picked example package wait-on is still included in bom.json, so the issue seems to still exist.

@qroac, we had a major refactor recently by switching to arborist. I will take a look at this later.


feat: Implement pharaoh framework

Description
This PR introduces a Class-Based backend development in addition to purely being functions. Also adds on a nice layer for elegant routing, request validation etc.

Type of Change

[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Codecov Report
Attention: Patch coverage is 63.49892% with 169 lines in your changes are missing coverage. Please review.

Project coverage is 71.34%. Comparing base (8901578) to head (9f99f23).
 Consider uploading reports for the commit 832d1da to get more accurate results

Files
Patch %
Lines

packages/pharaoh/lib/next/_core/reflector.dart
46.57%
39 Missing :warning:

packages/pharaoh/lib/next/http.dart
4.16%
23 Missing :warning:

packages/pharaoh/lib/next/_core/config.dart
24.00%
19 Missing :warning:

packages/pharaoh/lib/next/router.dart
62.00%
19 Missing :warning:

packages/pharaoh/lib/next/_router/definition.dart
70.96%
18 Missing :warning:

packages/pharaoh/lib/next/_core/core_impl.dart
26.08%
17 Missing :warning:

packages/pharaoh/lib/next/core.dart
76.81%
16 Missing :warning:

packages/pharaoh/lib/next/_core/container.dart
0.00%
7 Missing :warning:

packages/pharaoh/lib/next/_router/meta.dart
88.33%
7 Missing :warning:

packages/pharaoh/lib/next/_validation/dto.dart
80.00%
1 Missing :warning:

... and 3 more

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #120      +/-   ##
==========================================
- Coverage   74.44%   71.34%   -3.10%
==========================================
  Files          34       47      +13
  Lines        1119     1574     +455
==========================================
+ Hits          833     1123     +290
- Misses        286      451     +165

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Push RTSP stream

can i use this module to push RTSP stream not RTMP ?

I am not sure #412  is the answer for this problem. We have same requirements (push from some cameras, each with their own rtsp uri (rtsp://serverip:port/cameraid) and we are not sure if rtmp module will help us with this situation to route traffic to different backends.
Thanks,
Javier R.


Fix: address issues 40 and 41

This fixes the tag propogation issues we were seeing in issue 40, and also introduces ruff format --check . into the quality checks pipeline, which is the request from issue 41.

Thanks @jmfiola for this and the addition of ruff format. LGTM to me merge. But will have to wait for @alteryx-sezell since she is the only code owner currently.

Updated and merged #43 to add more code owners. But would still wait for another set of eyes on the changes before merging.


mypy errors don't show up in problems view nor in editor

VS Code version
1.62.2
Extension version
v2021.11.1422169775
OS type
Linux
OS version
20.04 LTS
Python distribution
python.org
Python version
3.9
Language server
Pylance
Expected behaviour
Show mypy errors in problems and in editor
Actual behaviour
They only show up in the Python/Output view:
##########Linting Output - mypy##########
downloader.py:9:1: error: Function is missing a return type annotation
downloader.py:9:1: error: Function is missing a type annotation for one or more arguments
Found 2 errors in 1 file (checked 1 source file)

Steps to reproduce
Create a python file a function that does not have a return type, hit safe.
Logs
see above
Code of Conduct

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

Hi, I think something like this has happened to me before.
Can you run mypy directly on your terminal and see if it fails? If it does, it may provide some hints about what's going wrong - Mine was failing and apparently vscode wasn't being able to provide any informative information about it.

It's running fine. Expected output, it doesn't fail, but correctly shows the problems in my code.

I have the same issue (no visual indication, but the log shows that mypy is running and correctly identifying errors).
The only difference in my setup is that I'm using mypy==0.812 and python3.8

I have the same issue and do not see any issues for mypy (pylint, bandit, black and pep8 work as expected):
Version: 1.63.2 (user setup)
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:40:02.816Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows 10 Enterprise x64 19043.1415
Python extension v2021.12.1559732655
Tried it with python 3.7 as well as 3.9, running mypy via terminal returns 2 issues (using --strict mode in both the VSCode Settings and via command line)

@diegovalenzuelaiturra does it work for you?

@dreamflasher and @jmrgibson I just set up my new laptop and there it works as expected. Exact same Versions as I mentioned above. The only change is in on the Laptop where it works I installed VSCode directly via the downloadable *:exe, in the other system it was installed via anaconda navigator (quite some time ago when it was shipped as the preferred IDE). I cannot pinpoint any other differences in the setup. Might be worth for you to just try to setup VSCode from scratch.

There was an error in the highlight and in the pop up, but it has been solved, could you try again and see if the error continues?

This seems to have gotten worse in 1.64.0.  I was getting correct mypy results prior to 1.64.0 (although only one character underlined for an error).  Now in 1.64.0, there is no highlighting of errors, nor mypy errors in the Python channel.  I only see:
##########Linting Output - mypy##########

If I run mypy from the command line, I get the expected error.

This seems to have been fixed in  1.64.1.  Now mypy works again, but there's still of course the issue that only one character is underscored.

Seems to be broken on 1.64.1 and 1.65.0 insider build for me, issue also isn't reproducible 😔

Seems to be broken on 1.64.1 and 1.65.0 insider build for me, issue also isn't reproducible 😔

fixed it for me, it was an internal assertion error in mypy, which caused the linting output to go empty somehow.

For me mypy errors don't show up in Problems view inside a Dev container (while other linting errors, e.g. flake, do). Mypy shows errors if run from terminal in the same container. They also show up in Problems view if I open the same file outside of the container. Mypy is enabled in devcontainer.json: "python.linting.mypyEnabled": true is among the settings.
Is this the same problem?
Version: 1.64.2
Commit: f80445acd5a3dadef24aa209168452a3d97cc326
Date: 2022-02-09T22:02:29.527Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.4.0-97-generic

@WizzyGeek How did you fix it?

@mardukbp my issue was not really related to vscode it is due to a bug in dataclass mypy plugin which raised an error, so I just changed my code so that mypy won't encounter the error

Thanks for your answers, I'm going to close the issue since it was a mypy problem. And it's fixed.


Added Send+ Sync to egui Toasts context

Wrapped the function callback in Arc<> and specified Send+ Sync on the dyn Fn input. This PR Allows for the usage of Toasts in something such as Bevy ECS like so:
use bevy::prelude::*;

#[derive(Resource)]
pub struct Toasts(egui_toast::Toasts);

Looks reasonable, thanks!


Avoiding getSession() function call when token is absent

Describe the bug
The getSession() function should not be called if the bearer token is missing, as it will result in an error. Please ensure that the bearer token is present before calling getSession() to avoid any issues.
Also please make sure that in each request you send a header "Accept: application/json" (or maybe you can add it as an option to endpoints config).
Currently, I'm using Nuxt v3.4.2 and @sidebase/nuxt-auth  v0.6.0-alpha.2

Good one - should be almost a one-line fix, do you want to contribute it?
I assume this is about the local provider? In that case: just add an if to the getSession func that chrcks for token existance (:

closed via #355, thanks @tnt-freskim-veliu 🎊


Multiple selectors with arguments result in a union type

Typescript 4.4.2
Reselect 4.1.1
If I have a selector like:
export const testSelector = createSelector(
  (_: RootState, { testNumber }: { testNumber: number }) => testNumber,
  (_: RootState, { testString }: { testString: string }) => testString,
  (testNumber, testString) => testNumber + testString
)

When I try to call the selector using:
  const test = useSelector((state: RootState) =>
    testSelector(state, { testNumber: 1, testString: '10' })
  )

I get the error:
Argument of type '[{ testNumber: number; testString: string; }]' is not assignable to parameter of type '[{ testNumber: number; }] | [{ testString: string; }]'.
  Type '[{ testNumber: number; testString: string; }]' is not assignable to type '[{ testNumber: number; }]'.
    Type '{ testNumber: number; testString: string; }' is not assignable to type '{ testNumber: number; }'.
      Object literal may only specify known properties, and 'testString' does not exist in type '{ testNumber: number; }'. ts(2345)

It appears that Reselect is converting all the different arguments into a union type, when instead they should be combined using an intersection type.
Workaround is to drop back to Reselect 4.0.0, which uses the intersection type.

I came here to create a new issue but I believe this issue describes the root cause. I paste my example here for reference. It all works on reselect 4.0 but not on 4.1. I believe my example covers some more incorrect errors than the post above.
The code still runs correctly on 4.1, so this seems to be purely at typing problem. Unfortunately, this is a blocker for us to use 4.1 in our codebase since we heavily rely on correct typing but we really want to use the new memoize options.
import { createSelector } from "reselect"

// Args

const select1Arg = createSelector(
  [
    (state, arg1) => state,
    (state, arg1) => arg1
  ],
  (state, arg1) => [state, arg1]
)

const select2Arg = createSelector(
  [
    (state, arg1, arg2) => state,
    (state, arg1, arg2) => arg1,
    (state, arg1, arg2) => arg2
  ],
  (state, arg1, arg2) => [state, arg1, arg2]
)

const select2ArgWrapped = createSelector(select2Arg, x => x)

console.log('select1Arg', select1Arg('state', 1))
console.log('select2Arg', select2Arg('state', 1, 2))
console.log('select2Wrapped', select2ArgWrapped('state', 1, 2))

// Props
console.log()

const select1Prop = createSelector(
  [
    (state, props) => state,
    (state, props) => props
  ],
  (state, props) => [state, props]
)

const select2Prop = createSelector(
  [
    (state, props) => state,
    (state, props) => props,
  ],
  (state, props) => [state, props]
)

const select2PropWrapped = createSelector(select2Prop, x => x)

console.log('select1Prop', select1Prop('state', { prop1: 1 }))
console.log('select2Prop', select2Prop('state', { prop1: 1, prop2: 2 }))
console.log('select2Wrapped', select2PropWrapped('state', { prop1: 1, prop2: 2 }))

// Args chained
console.log()

const select2ArgChained = createSelector(
  [
    select1Arg,
    (state, arg1, arg2) => arg2
  ],
  (state, arg2) => [state, arg2]
)

const select2ArgWrappedChained = createSelector(select2Arg, x => x)

console.log('select2ArgChained', select2ArgChained('state', 1, 2))
console.log('select2WrappedChained', select2ArgWrappedChained('state', 1, 2))

// Props chained
console.log()

const select2PropChained = createSelector(
  [
    select1Prop,
    (state, props) => props,
  ],
  (state, props) => [state, props]
)

const select2PropWrappedChained = createSelector(select2Prop, x => x)

console.log('select2PropChained', select2PropChained('state', { prop1: 1, prop2: 2 }))
console.log('select2WrappedChained', select2PropWrappedChained('state', { prop1: 1, prop2: 2 }))

Pasting a screenshot that highlights where the errors are. In the screenshot I hover on one particular error that I believe is distinct from what is described in the the post above. Let me know if I should open more issues.

I worked on this issue both last weekend and all of this weekend. I've got progress, but also roadblocks.
The good news is that I think I've got a reworked version of the parameters handling that correctly intersects the parameters at a given position, and passes both of the examples shown here.
Unfortunately, it's also failing another existing type test, because it's now also wiping out a valid use of a union type as an argument.
Additionally, I'm now seeing "excessively deep instantiation" errors in some of our tests, like "ensure we can handle 20+ input selectors".
So, kind of between a rock and a hard place here. Fix this, break something else.

Thanks for your efforts Mark! Perhaps reselect should revert back to the code from 4.0? It seems to be solid. We are now specifying version 4.0 explicitly in our dependencies. I consider > 4.0 broken at the moment.

I would really rather not do that - the old types were also effectively broken and impossible to maintain:
https://github.com/reduxjs/reselect/blob/v4.0.0/src/index.d.ts
There's no meaningful way to add the additional memoization options to those types.

Part of the issue here is I don't think it's very well defined what the final generated selector's arguments should be based on the available input selectors.
For "params at the same index of each input selector", the obvious properties are:

All params are the same: use that type
Params are objects: intersect them so that all fields must be included
Params are incompatible (say, string and number): use never so that there's an error
One selector is longer than another, so that params1[3] is string but params2[3] is undefined: use the value

So far, these are all reasonably accomplished with UnionToIntersection<>.
The problem comes when some of the parameters are unions themselves.  For example, even just one selector like (key: keyof SomeObj) => whatever, or (val: string | number) => whatever.  When UnionToIntersection gets applied here, the union in that parameter gets intersected, and thus ends up as never for what would have been a perfectly valid input argument.
As a more specific example, for this selector:
const input1a = (
  _: StateA,
  { testNumber }: { testNumber: number },
  c: number,
  d: string
) => testNumber

const input1b = (
  _: StateA,
  { testString }: { testString: string },
  c: number
) => testString

const input1c = (
  _: StateA,
  { testBoolean }: { testBoolean: boolean },
  c: number | string,
  d: string
) => testBoolean

const input1d = (_: StateA, { testString2 }: { testString2: string }) =>
  testString2

const testSelector = createSelector(
  input1a,
  input1b,
  input1c,
  input1d,
  (testNumber, testString, testBoolean) => testNumber + testString
)

the parameters arrays are:
[
  [StateA, { testNumber: number; }, number, string],
  [StateA, {  testString: string; }, number],
  [StateA, { testBoolean: boolean; }, string | number, string],
  [StateA, {  testString2: string; }]
]

If we transpose them to extract the types at each parameter index, we get:
[
  [StateA, StateA, StateA, StateA],
  [{testNumber: number}, {testString: string}, {testBoolean: boolean}, {testString2: string}],
  [number, number, string | number, undefined],
  [string, undefined, string, undefined]
]

The first two are easy: StateA and {testNumber, testString, testBoolean, testString2}.  The third should end up as string | number, and the fourth should end up as string.
But, because we need to apply UnionToIntersection on the entire array, the third one actually ends up as a union of string | string | number -> string | number, and intersectioned that becomes never.
So. What I've got locally solves the problems listed in this issue, #541, and #548 .  But, it also results in a never any time there's a legitimate union being passed as a parameter type.
I could clean up what I've got and put out an alpha release to let folks try it out, I guess. I'm just trying to figure out if there's any viable options for fixing the union/intersection issue here.

Update: after some major help from @Retsam and @pfgray , we may have something that seems to be A) passing all our type tests, and B) not killing TS with excessively deep processing.
The current branch is incredibly hacked up and I'll really need to start from scratch with the final approach in mind, but I think we might actually be on to something here.

Out in https://github.com/reduxjs/reselect/releases/tag/v4.1.3


derived Serialize/Deserialize/JsonSchema

Generally best practice to implement these for all types. Hope this helps!

There is also a change to add a configurable derivation path here. There are two options. The more technically correct one is to store the derivation path only in the ChainCfg, and pass it around as a parameter everywhere, which is kind of annoying. The other option (which I've done here), is to store it along side the key, which is also annoying since it requires you set it every time you add a new key.

The other option (which I've done here), is to store it along side the key, which is also annoying since it requires you set it every time you add a new key.

Putting it with the SigningKey for ergonomics is fine with me.
We could add a SigningKey constructor that sets derivation_path for us from the ChainCfg, so you only have to manually set it if you use the SigningKey struct directly.

The other option (which I've done here), is to store it along side the key, which is also annoying since it requires you set it every time you add a new key.

Putting it with the SigningKey for ergonomics is fine with me.
We could add a SigningKey constructor that sets derivation_path for us from the ChainCfg, so you only have to manually set it if you use the SigningKey struct directly. What do you think?

For development It might be useful for users to be able to use the same key with different derivation paths for multiple chains. This would prevent that, but probably not a huge deal. The other disadvantage, is Key A with derivation path a will not work on a chain with derivation path b. Perhaps we should be passing it around. It's not that bad after all.

Anything you want done before this gets merged?

Anything you want done before this gets merged?

Sorry, Ive been really sick. Im looking over the PR now.

Sorry to hear you were sick! Hope you're feeling better. If these look good to you I'll go ahead and update the tests and get it ready to merge.

Sorry to hear you were sick! Hope you're feeling better. If these look good to you I'll go ahead and update the tests and get it ready to merge.

Looks great, thanks!


Map Flavors to Cloud Tenants during Openstack Cloud refresh (Depends on 11033)

Builds a many-to-many mapping of Cloud Tenants to the Flavors that they have access to during the Openstack cloud provider refresh. Tenants have to be queried one at a time for which Flavors they can access, since Flavors don't belong to any one specific Tenant and multiple Tenants could have access to them.
@tzumainn

WIP, needs tests.

Looks solid at first glance!  You may have to run 'bundle exec rake evm:db:write_schema' to update schema.yml

@miq-bot remove_label wip

:+1: LGTM!

@miq-bot assign @chessbyte

Assigned to @Fryguy to review SQL migration. @Ladas @blomquisg Please review as well.
@mansam Please rebase and push again

@mansam you can get rid of the warnings if you use the hostnames in the environment yaml, then they will be obfuscated
the patch itself is more complex than need to be. For saving code you basically need just one line:
https://github.com/Ladas/manageiq/blob/838cd207c9825118d9e8ede308adbe0affa37056/app/models/ems_refresh/save_inventory.rb#L66-L66
though write it like this:
https://github.com/Ladas/manageiq/blob/4f5dda55dfdd663c18b6fc9270f8336f29c6e1c4/app/models/ems_refresh/save_inventory_network.rb#L258-L258
then refresh code for the same case, image has and belongs to many cloud_tenants:
https://github.com/Ladas/manageiq/blob/7f841eed10af19aa5aa0bbc4729db7fd9d6896ea/app/models/manageiq/providers/openstack/refresh_parser_common/images.rb#L38-L38
so it takes in account an owner and case when image is public

Now depends on https://github.com/ManageIQ/manageiq/pull/11033. Working on the rest of the feedback.

Unlabeling sql migration because the DB changes were extracted.

@miq-bot remove_label sql migration

@Fryguy This should be ready to go now that its prereq is merged :)

@miq-bot add_label euwe/yes

@miq-bot assign @blomquisg

@tzumainn @mansam dang guys ... sorry, I was swamped today and missed this one :/  And, now you're getting the dreaded VCR conflicts.

@blomquisg No problem! I've just updated it again to fix the conflicts.


[Feat]: I want to add my profile to devDisplay

What feature?
I want to add my profile to DevDisplay
Add screenshots
NA
Code of Conduct

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

Please assign to proceed further with labels

hey @codeaashu  please assign to me, i am keen to showcase my profile

Hey @codeaashu please assign me this


Setting default filter values in FilterBox

Make sure these boxes are checked before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if any
[ ] I have reproduced the issue with at least the latest released version of superset
[ X] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.25.5
Expected results
I need to set a default value in a filterbox which will then filter non-immune slices on the dashboard the filterbox is added to.  I know there is an option to set a filter in a filterbox and then save the dashboard which will retain the filtering when selected.  This option does not work when the filter choices in the filterbox may differ for each user.  There is no property in the filterbox slice builder to set a default value.  I have thought of adding to Dashboard.jsx a new property in formData which may then be leveraged in utils.py when the query is created similar to what extra_filters does now; however, I have not found a means to enforce the use of this "default_filter" only for the first time the dashboard is selected.  As for as a default value, I would just use the first value in the list of filter choices.  I was able to set a default value in a filterbox by changing the value property in the OnPasteSelect in filter_box.jsx; the issue here is that it does not propagate to the other slices on the dashboard making it ineffective.
Is there a way of knowing when a dashboard is initially selected by a user?
Can setting a default value in the filterbox be added as a new property which is perhaps picked up by extra_filters?
Any thoughts or ideas would be appreciated.
Referred the below issues but did not find a solution.
#3071
#3183
#3618
#665
Actual results
No property option currently available.
Steps to reproduce
Not currently supported to my knowledge.

We have been able to resolve this issue/request.  We duplicated the files associated to filter_box to create a single-select filter box.  Once we had that object working, we were able to force a default initial value to all columns assigned within this filter box.  We added a new property to the controls which allows us to either have a default or to turn default off.  All testing to-date on this new object has been good.

Is it possible to set default value in filter based on logged in user details by using some interim mapping table etc or otherwise?


Animate the title on hovering

Enhancement: Animate the word 'First' on hovering in the website title.
Create any cool animation when we hover on the word 'First'.
eg-Create an animation in which each alphabet of the word jumps or dances when we hover on that. This is just an example, you can use your own imagination or can implement the same.

I want take this

Hi @Suhaas10
Assigning this issue to you. You can start work on this. Please raise PR after completing this.
Don't forget to give a star. 😉
Thanks & Regards
Jitender Singh Chhapola

How do I run this vanilla JS project locally? @niteshjitender

Done https://github.com/niteshjitender/HacktoberFest2022/pull/14

'First' keyword is highlighted not animated. Not closing this issue. Although your PR is accepted.

Done https://github.com/niteshjitender/HacktoberFest2022/pull/14

This issue is still open and anybody who is up to this. Please comment.

hey can you assign it to me I'll try to do my best

hi i am hacktoberfest participant  can u please assign this issue to me.

@niteshjitender Please assign back to me, I have created new PR

hi i am new to open source please assign this to me for learning

Working on this, will soon submit a PR


Added npm package, gulpfile and sass source

Thanks this looks awesome. Will take a deeper look asap.

@Wtower Have a few questions. Bear with me as I'm more familiar with Grunt than Gulp.

I ran the gulp command, which built the /build/ folder and email.html and css/email.css. What use is the css/email.css at this point? I would expect maybe a non-inlined version of email.html to make use of the CSS file. Otherwise I'm not sure what it is for.
I previewed the output in Litmus. Compared to the original (which was inlined with Putsmail) there are some things off like spacing and responsiveness (see below).
Looks like the media queries and CSS in the head aren't carried across to the build. So we lose some of the responsive features.
I wasn't sure what In order to build the final html file you need to use gulp-inline-css meant in the readme. Why not include this in the gulpfile?

@leemunroe thank you for your review, these are excellent points. I will look into them and get back to you.

Hello @leemunroe , I just look into your last comment:

Bear with me as I'm more familiar with Grunt than Gulp.

I would be more than happy to help as much as I can. Gulp is not much different than grunt so I think you will catch up quickly. So if there is anything to tell you about it let me know, possibly it will help other users that might visit this too.

I ran the gulp command, which built the /build/ folder and email.html and css/email.css. What use is the css/email.css at this point? I would expect maybe a non-inlined version of email.html to make use of the CSS file. Otherwise I'm not sure what it is for.

Actually the build/css/email.css is an intermediate file that is built from the src/email.sass file for those familiar with it.
The proposed changes are mostly intended to be introduced in a larger project workflow. It is unlikely that my gulpfile will be used as is but mostly to take a rough idea how to build. The html file also is unlikely that will be used as is without replacing. But the sass file is more likely to be used as is directly in any replaced html without having to repeat its rules all over, but probably to simply override it.
Of course the proposed gulpfile is intended though to be able to build the html properly.

I wasn't sure what In order to build the final html file you need to use gulp-inline-css meant in the readme. Why not include this in the gulpfile?

You are right. In the previous commit I used a project of mine which defines a number of common gulp tasks together with their dependencies. But that is again intended for final projects and an overkill for this one, so in my last commit I replaced it and defined the proper dependencies and gulp tasks explicitly.

Looks like the media queries and CSS in the head aren't carried across to the build. So we lose some of the responsive features.

You are absolutely right. The gulp-inline-css has a couple of options: preserveMediaQueries and applyWidhtAttributes that are disabled by default and needed to be enabled explicitly. Fixed in the last commit.

I previewed the output in Litmus. Compared to the original (which was inlined with Putsmail) there are some things off like spacing and responsiveness...

It seems this is a paid service? Could you please recheck after the last commit?
I hope the above clarifies and improves things a bit. Please do not hesitate to fire up more comments if necessary.

@Wtower Sorry for the hold up. I really like what you've done here but I fear this overcomplicates the current goals of this project. I think a lot of people appreciate the simplicity of the current repo, and for more advanced workflows they can use something like https://github.com/leemunroe/grunt-email-workflow


Add streaming vesting

I fixed vesting tests and added the streaming functions. Also the Sepolia URL was outdated so I updated that in my repos scarb.toml. There is one test fail for upgrades-
tests::basic::test_upgrade_mainnet_to_master
Failure data:
0x4e6f20766f74696e6720706f776572 ('No voting power')

Looks good to me so far. We should add documentation for this later and also streaming of tokens from treasury.


Minor clarification of GCS data validation docs; change default hash algo?

The docs for createReadStream and createWriteStream say

"By default, data integrity is validated with an MD5 checksum for maximum reliability, falling back to CRC32c when an MD5 hash wasn't returned from the API."

It appears that actually both are calculated, and both are verified if present (although the md5 check overrules the crc32c check), so I think it would be more accurate to say

"By default, checksums are calculated using both MD5 and CRC32c on the fly; MD5 is used for the final validation for maximum reliability, falling back to CRC32c when an MD5 hash wasn't returned from the API (i.e. in the case of composite objects)."

But, using a cryptographic hash seems like an overkill default. What do you think of changing it to by default calculating CRC32c only, and not calculating MD5 unless the validation method is "MD5"?
(Also, if you specify "md5" then it does not appear to fallback to CRC32c if there was no MD5 returned -- ideally it would fallback instead of doing zero validation, I think?)

I'm fine with the docs change. As far as disabling MD5 check by default, that would be validating using the less-reliable method, by our own words. If it being expensive to compute is an issue to the user, they have the option to disable, which I think is good enough.

(Also, if you specify "md5" then it does not appear to fallback to CRC32c if there was no MD5 returned -- ideally it would fallback instead of doing zero validation, I think?)

This seems ideal. If the user wanted MD5 validation specifically and we couldn't do it, that should be a failure.

Thanks as always for the prompt reply!

validating using the less-reliable method, by our own words

Sure, although I think those words might be google-cloud-node's? The GCS docs advise CRC32C "for all cases":

Google recommends that customers use CRC32C for all cases, as described in the Validation section below. Customers that prefer MD5 can use that hash, but that hash is not supported for composite objects.

Because it's configurable :heart:, I totally don't feel strongly about changing it, but I think most people would say MD5 is overkill for data integrity checks. (The risk of undetected corruption with CRC32c is 1/2^32, or 0.99999999977 detection.)
(Re: last point, makes sense.)

Oh jeez, if we just made that up, then I'm fine re-thinking this. We can follow that doc's advice and do crc32c by default and md5 if asked. Any interest in a PR? No pressure, if not, I'll get to it soon :)
Thanks for calling this out!


Old version of Kryo used in benchmarks

Hi, interesting to see a Kryo competitor. The benchmarks compare it against 2.23 but the current version is 4.0.0 (the package was changed) https://github.com/EsotericSoftware/kryo/releases. Would also be good to include memory usage as part of the comparison. Thanks!

I have tested the latest version recently and had major regressions in many testcases compared to 2.23/3.0.  see https://github.com/RuedigerMoeller/serialization-benchmark (4.0 tests not released).
Anyway there is a conceptual difference as fst emulates (and reuses implementations) of standard jdk serialization.
In addition I am not to deep into letting other peoples work look bad, and ofc there might be testcases where kryo performs better.

updated  https://github.com/RuedigerMoeller/serialization-benchmark to kryo 4.0.0 . Actually some stuff got better in kryo 4 compared to kryo 3 (still AFAIR slower than kryo 2.23).
Kryo has a shorter init time and produces on average ~10 to 20% smaller file/msg sizes, however in most object graph serialization use cases fst2 has a small to medium performance advantage.

btw: to which benchmark link are you referring to ??

https://github.com/RuedigerMoeller/fast-serialization/wiki/Benchmark was the link received from the main website. Might need to correct it if that's also old. Thanks!

Oh .. thanks :)

The latest Kryo is 5.0.0-RC2. Possible to update the results again? There are lots of big changes in the latest release as well.


Keyfilter directive feature

Select one ...  (check one with "x")
[ ] bug
[x] feature request
[ ] enhancement

Expected behavior
Can we get a keyfilter directive as one in PrimeNG?
This will be very helpful and handy for form inputs.
https://www.primefaces.org/primeng/#/keyfilter
Actual behavior

Reproduction of behavior

Include a link to the reproduction scenario you created by forking one of the Clarity Plunker Templates:

Environment details

Angular version: 5.x.x

Clarity version:

OS and version:

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

This is a duplicate of #1259
Closing this for now. Please subscribe to #1259 for updates. Thanks!


Example claude_desktop_config?

Hey Team - Any chance you have an example of what claude_desktop_config.json  would look like using this via HTTP.  Every example I can find of this file uses stdio (cannot find one... google fail)

Ahh, whoops.  https://github.com/orgs/modelcontextprotocol/discussions/91

good catch!
For LLM UIs, the only ones that I know that support MCP on SSE are LibreChat and Superinterface.

LibreChat as direct replacement of Claude Desktop.
Superinterface as the only way for web-based assistants to use MCP.
You can also use mcp inspector to check that SSE is running.


[Event Request] Codeunit 22 Item Jnl.-Post Line - Function InitTransValueEntry

Dear ALAppExtensions Team,
We would like to request the following event publisher in codeunit 22 Item Jnl.-Post Line - Function InitTransValueEntry
local procedure InitTransValueEntry(var ValueEntry: Record "Value Entry"; ItemLedgEntry: Record "Item Ledger Entry")
var
    AdjCostInvoicedLCY: Decimal;
    AdjCostInvoicedACY: Decimal;
    DiscountAmount: Decimal;
    IsHandled: Boolean;
begin
    InitValueEntry(ValueEntry, ItemLedgEntry);
// DINNL <<
DINOnInitTransValueEntryOnAfterInitValueEntry(ValueEntry, ItemLedgEntry);
// DINNL >>
    ValueEntry."Valued Quantity" := ItemLedgEntry.Quantity;
    ValueEntry."Invoiced Quantity" := ValueEntry."Valued Quantity";
    ValueEntry."Location Code" := ItemLedgEntry."Location Code";
    ValueEntry."Valuation Date" := GlobalValueEntry."Valuation Date";

local procedure DINOnInitTransValueEntryOnAfterInitValueEntry(var ValueEntry: Record "Value Entry"; ItemLedgEntry: Record "Item Ledger Entry")

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Swagger update

Description

This was done manually. Perhaps in the future it should be automated, as described in #435.
Related issues

Fixes #435

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Changes Made

Update swagger schema docs

Testing

[x] Tests do not apply

Mentions

Rebased to fix conflicts


[UI] Assert options on dark mode

I have checked the following:

[X] I use the newest version of bruno.
[X] I've searched existing issues and found nothing related to my issue.

Describe the bug
Hard to see assert options on dark mode. On screenshot seems better than on monitor :D
.bru file to reproduce the bug
No response
Screenshots/Live demo link

don't know which PR fixed this, but this bug has been fixed in latest release:

Just re-checked it, and can update info. If used "system" theme, and system use dark theme it bug caused. At least on Windows 10. Thanks for reply. If use force "dark" it's work fine.

Hi there, was fixed in 1.26 @sanjai0py

Yes @SPIRIT-00


linked devices not showing in tuya v2

linked my tuya account to tuya v2, authorization was successful and in the integration section Tuya v2 shows my tuya smart account ID. although no devices were added and there is no configuration option within the tuya v2 tab.
I disabled my local tuya and tuya integration from my HA but nothing solved the issue. even tried deleting the integration and started with a fresh copy.

@yab999 check your device is supported.
https://github.com/tuya/tuya-home-assistant/wiki/Supported-Device-Category

@yab999 check your device is supported.
https://github.com/tuya/tuya-home-assistant/wiki/Supported-Device-Category

its a tuya dimmer, works fine with tuya smart and logs do not show any issues

@yab999 Can you provide device specifications from the log?

@yab999 Can you provide device specifications from the log?

sure, thats HA logs:
2021-07-05 18:33:39 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration tuya_v2 which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2021-07-05 18:33:39 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2021-07-05 18:33:39 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2021-07-05 18:33:58 ERROR (Thread-3) [tuya iot] error while get mqtt config 2021-07-05 18:33:58 ERROR (Thread-3) [root] Uncaught thread exception Traceback (most recent call last): File "/usr/local/lib/python3.8/threading.py", line 932, in _bootstrap_inner self.run() File "/usr/local/lib/python3.8/site-packages/tuya_iot/openmq.py", line 173, in run time.sleep(self.mq_config.expireTime - 60) AttributeError: 'TuyaOpenMQ' object has no attribute 'mq_config' 2021-07-05 18:34:15 ERROR (MainThread) [custom_components.hacs] thomasloven/lovelace-gui-sandbox - Repository is archived. 2021-07-05 18:34:15 ERROR (MainThread) [custom_components.hacs] thomasloven/lovelace-dummy-entity-row - Repository is archived. 2021-07-05 18:34:15 ERROR (MainThread) [custom_components.hacs] thomasloven/lovelace-gap-card - Repository is archived.
and this is from tuya iot hub:
`
Dimmer 1
{
"result": {
"active_time":<PHONE_NUMBER>,
"biz_type": 0,
"category": "tgkg",
"create_time":<PHONE_NUMBER>,
"icon": "smart/icon/ay1536047723331OpdLN/16f98664612d4aad7010a64b3170851c.png",
"id": "eb55bc88dbb084d0bffmns",
"name": "Smart Dimmer Switch 2",
"online": true,
"owner_id": "44730101",
"product_id": "4pa61y3uci6i1wmg",
"product_name": "Smart Dimmer Switch",
"status": [
{
"code": "switch_led_1",
"value": true
},
{
"code": "bright_value_1",
"value": 640
},
{
"code": "brightness_min_1",
"value": 10
},
{
"code": "led_type_1",
"value": "led"
},
{
"code": "work_mode",
"value": "light_white"
},
{
"code": "light_mode",
"value": "none"
}
],
"sub": false,
"time_zone": "+03:00",
"uid": "az1625161985280qtxsJ",
"update_time":<PHONE_NUMBER>,
"uuid": "f08b554038806b9f"
},
"success": true,
"t":<PHONE_NUMBER>147
}
Dimmer 2
{
"result": {
"active_time":<PHONE_NUMBER>,
"biz_type": 0,
"category": "tgkg",
"create_time":<PHONE_NUMBER>,
"icon": "smart/icon/ay1536047723331OpdLN/16f98664612d4aad7010a64b3170851c.png",
"id": "eb3338800b713aa4abldif",
"local_key": "",
"name": "Smart Dimmer Switch",
"online": true,
"owner_id": "44730101",
"product_id": "4pa61y3uci6i1wmg",
"product_name": "Smart Dimmer Switch",
"status": [
{
"code": "switch_led_1",
"value": false
},
{
"code": "bright_value_1",
"value": 510
},
{
"code": "brightness_min_1",
"value": 10
},
{
"code": "led_type_1",
"value": "led"
},
{
"code": "work_mode",
"value": "light_white"
},
{
"code": "light_mode",
"value": "none"
}
],
"sub": false,
"time_zone": "+03:00",
"uid": "az1625161985280qtxsJ",
"update_time":<PHONE_NUMBER>,
"uuid": "28562e3dbd5f50d6"
},
"success": true,
"t":<PHONE_NUMBER>463
}`

@yab999 category tgkg is not supported now.

@yab999 category tgkg is not supported now.

thank you for letting me know, hope this gets added soon.


Refactor & restructuring

Sorted properties, methods etc. by purpose.
Encapsulated some initialisers into dedicated methods for less clutter, leaving the logic untouched.
Added "//  MARK"-style comment delimiters to files, these represent the Swift version of Objective-Cs "pragma". Removes onboarding hurdles for some devs:

Thanks man! I'll merge it in after #201 is merged to prevent conflicts

@danielbuechele with pleasure, thanks for a great project.
I reintegrated the changes from #201 with this refactor and updated this PR - should be ready to merge now. :-)


Add renovate config for xnat plugins

renovate all defaults plugin version using custom managers

Any ideas how to add these custom managers to a group so they all get updated together? There are docs on grouping packages but I don't know how to do this for the custom managers we have

Any ideas how to add these custom managers to a group so they all get updated together? There are docs on grouping packages but I don't know how to do this for the custom managers we have

I would ask on https://github.com/renovatebot/renovate/discussions

Make sure to check the console https://developer.mend.io/github/UCL-MIRSG/ansible-collection-xnat


Improve first-time setup

Allow the user to choose the location of rg.exe from the user interface instead of making them edit the .config file.

Changed this behavior in commit 2787033.  Now rg.exe is bundled in the release .zip and expected to be in the same folder as rg-gui.exe.

Changed this behavior in commit https://github.com/kcowolf/rg-gui/commit/27870337c7384e9cd2dae4e23f8c1dfcf175b710. Now rg.exe is bundled in the release .zip and expected to be in the same folder as rg-gui.exe.


Allow multiple instances of datasources

Currently Gungnir only supports a single global datasource. We should support having multiple instances.
From Slack:
@Ramblurr
And the second thing is related to that use of a global database  var: In many systems it is desirable to connect to multiple different databases, but this won't be possible with gungnir.
I think it makes lots of sense to do away with the global var, and instead return a state-map that contains the functions needed.
I'm thinking of how the sente library works here: it's equivalent function to make-datasource! returns a map of state and functions for operating on that state. (edited)
For example make-datasource! could return a map that contains the keys:
:stop-fn - a function to close the connnection pool
:changeset-fn - the changeset function bound to this particular db connection
:database  - the *database* for this particular connection
:find!-fn  - the query/find! function for this particular connection
... and so forth

some thought would have to be given for how gungnir.model/register! would be bound to a particular gungnir instance
@kwrooijen
For your second point, yes Gungnir only supports a single database connection at the moment. I'm still thinking of a way to handle this. What I would really like is for multiple instances to be optional, whereas a single global instance is the default. I don't often have multiple datasources but I understand that this should be supported in some way.
One way would be to map datasources to identifiers. e.g. (gungnir/make-datasource! ::datasource-1 {,,,}) . Then when you register a model you can register it with a specific datasource
(gungnir.model/register!
 {:user
  [:map
   {:datasources [::datasource-1]}
   [,,,]]})

Then, whenever you query the database, you can pass in the datasource or key
Casey  2:51 PM
If all the functions supported an arity with a datasource param, that would probably work too
kwrooijen  2:52 PM
Yeah, I think that would be difficult with the current API though. the find! find-by! and all! functions are quite flexible but also not my most elegant pieces of code. Worst case we could create a different variant of these functions which support accepting a datasource (edited)
e.g. find-with-datasource!   find-by-with-datasource!   all-with-datasource!  or something along those lines

Here is a example code of how I imagine the apis working:
;; db1.clj
(ns myproj.db1 (:require [gungnir.database :as gungnir]))

;;  calling make-datasource returns a state-map
;;  this state map has all the functions and state you need to operate with this particular connection
(let [{:keys [close-fn changeset-fn datasource find!-fn find-by!-fn all!-fn save!-fn]}
      (gungnir/make-datasource! :datasource1
                                {:adapter "postgresql" :username ....})]

  ;;  the idea for this was taken from the well known and mature websockets library sente
  ;;  see the first code example in the sente readme https://github.com/ptaoussanis/sente
  ;;  the tradeoff is this little bit of boilerplate here
  ;;  but this could easily be wrapped into a gungnir provided namespace for the default case
  (def *datasource* datasource)
  (def find! find!-fn)
  (def find-by! find-by!-fn)
  (def all! all!-fn)
  (def save! save!-fn)
  (def changeset changeset-fn)
  (def close close-fn))

;; now an example of how to use it
;; user.clj
(ns myproj.user
  (:require [myproj.db1 :refer [find! find-by! all! changeset save!]]
            [gungnir.model :as model]))

(model/register!
  {:user
    [:map
     [:user/id {:primary-key true} uuid?]
     [:user/email [:re {:error/message "Invalid email"}<EMAIL_ADDRESS>     [:user/password [:string {:min 6}]]
     [:user/created-at {:auto true} inst?]
     [:user/updated-at {:auto true} inst?]]})

(defn by-id [id] (find! id))
(defn by-email [email] (find-by! email))
(defn change-password [id new-password]
  (save! (changeset (by-id id) {:user/password new-password})))

;; that was the basic use case
;; now, how would one connect to multiple datasources?
;; well, we duplicate db1, but as db2, so you have myproj.db1 and myproj.db2
;; each should connect to different databases, but def the same functions

;; product.clj
;; in this example the user database is separate from the database of products
(ns myproj.products
  (:require [myproj.db2 :as db2]
            [gungnir.model :as model]))

(model/register!
  {:product
    [:map
     [:product/id {:primary-key true} uuid?]
     [:product/sku [:re {:error/message "Invalid SKY"} #"SKU-.*"]]
     [:product/name [:string]]
     [:product/amount-in-stock [:int {:min 0}]]
     [:product/description [:string]]
     [:product/image [:string]]
     [:product/created-at {:auto true} inst?]
     [:product/updated-at {:auto true} inst?]]})

(defn by-id [id] (db2/find! id))
(defn by-sku [sku] (db2/find-by! sku))
(defn decrement-stock [sku]
  (let [old-p (by-sku sku)]
    (db2/save! (db2/changeset old-p (update old-p :product/amount-in-stock dec)))))

Some points:

model registration doesn't care about datasources, so you could use the same :user or :product models on the different datasource connections.
good developer experience: That is, the day-to-day usage of the query and changeset functions stays the same. No extra params to inject when working with multiple datasources.
The current gungnir.database namespace could become the default global one, so everything stays the same for devs now. And then if you need to reach out to a 2nd data source you could use a function in a new ns, like gungnir.datasource.factory  or something that would provide the make-datasource! function in my snippet above.

kwrooijen:

I think the only addition we'd need is a new ns / function to do this. Possibly gungnir/make-datasource-map! Or something. There is a problem with this however which needs some thought. Currently the sql and database namespaces are intertwined. I want to separate them, and create a new namespace.
sql.honeysql
database  (next-jdbc)
database.hikaricp
The reason for this is that there are users that want to use Gungnir but not use Honeysql. So users can use a different adapter for their needs. In your example we're using a function that holds context of both HoneySQL and HikariCP, breaking that separation. I like your idea though, having a namespace for your datasource / functions. I think that's also what Ecto does but through a macro.
This could probably be fixed by having database.hikaricp/make-datasource! and sql.honeysql/api functions.  then building those two together the way you're doing

gungnir/make-datasource-map! would return functions that are already partial'd with the datasource. example (partial find!-underlyling-impl datasource) would be what is returned for find!-fn
Including the datasource itself in the state map is just for completeness so the dev could hook other stuff into it, if necessary

I'll add that at first I found the '(let [...] (def..) (def ..))` pattern strange and off-putting when I encountered it in sente, but after using that library a fair bit, it works just fine and gives you great power


system.pod6 needs example of user interaction

Show an example of a running program asking for input from the user.

Could it be some other example? I kinda hate those entry-level programs that prompt the user for stuff. Maybe working with an environment variable? Or filtering standard output?

Well, it seems like a reasonable thing to me. And of course other examples are always helpful.
My motivation for this suggestion is I need it for a program I’m writing for managing Apache passwords and want to present a choice to the user (me) after analyzing the state of password sets.  I can’t remember how to do it and haven’t found the right topic in the search box yet. This topic seems to be the perfect landing place for my quest.

Closed with commit 0ecbd02.


Fix wiki clone urls

Regressed by: https://github.com/go-gitea/gitea/commit/9a4050f1e839af1bd072aff9ac5fc69e650747c8
Fixes: https://github.com/go-gitea/gitea/issues/15420

Small fix pushed


Fix typo

@samajammin This looks simple enough, but I thought about it more after approving... will this cause translations to break? If I recall, the english string is essentially hashed, and then it looks up the translation by that hash. In this case, that hash will now be different and it won't know which translated string to inject. If I'm correct we may need to update the reference to this string in the compiled intl files with the new hash.

No problemo. Thanks for all your hard work maintaining this project @samajammin @wackerow


Support Apple Silicon

Currently tapping this repo with brew tap on a Apple silicon (m1) machine fails with the following:
> brew tap tetratelabs/getenvoy
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).
==> Updated Formulae
Updated 3 formulae.

==> Tapping tetratelabs/getenvoy
Cloning into '/opt/homebrew/Library/Taps/tetratelabs/homebrew-getenvoy'...
remote: Enumerating objects: 106, done.
remote: Counting objects: 100% (106/106), done.
remote: Compressing objects: 100% (92/92), done.
remote: Total 214 (delta 22), reused 63 (delta 14), pack-reused 108
Receiving objects: 100% (214/214), 48.15 KiB | 1.85 MiB/s, done.
Resolving deltas: 100% (44/44), done.
Error: Invalid formula: /opt/homebrew/Library/Taps/tetratelabs/homebrew-getenvoy/Formula/getenvoy.rb
formulae require at least a URL
Error: Cannot tap tetratelabs/getenvoy: invalid syntax in tap!

Judging by source, this is intentionally disabled but the error message above is a bit obscure.
It would be nice if I don't have to launch a VM to run envoy :)

@musaprg can you take a look?
We don't have M1 mac to test for that, but I guess we can use x86_64 binary meanwhile to rely on Rosetta. @fiibbb can you test whether the binary itself works?

@lizan Sure. Actually, I bought M1 Mac and it will come around 14th Apr. I can work on it after that. cc: @fiibbb

Just tried both the getenvoy binary and the ~/.getenvoy/builds/standard/1.17.1/darwin/bin/envoy. Both executes fine on m1 machine. Looks like it's just a matter of updating homebrew formula and the download script.

@fiibbb Thank you! I also confirmed that the getenvoy binary itself and fetched envoy binary worked well on M1 Macbook Air with Rosetta. :+1:

Looks like it's just a matter of updating homebrew formula and the download script.

Since fetched envoy will be executed with Rosetta implicitly, it's enough to build just only getenvoy itself for darwin-arm64. But we also need to ensure that it works well on Apple Silicon Mac inside our CI infra. Currently, any cloud provider (including GHA or AWS) doesn't release Apple Silicon instances. After releasing, it's a good time for getenvoy to support Apple Silicon :+1:

added this issue to ask envoy to retain the binaries they already build https://github.com/envoyproxy/envoy/issues/16830

This won't be solved here as this formula is deprecated for the official brew install envoy
Please follow-up on https://github.com/envoyproxy/envoy/issues/16482
and here https://github.com/Homebrew/homebrew-core/blob/master/Formula/envoy.rb


Exception: Release mode is not supported for iPhone 12 Pro Max

Exception: Release mode is not supported for iPhone 12 Pro Max
See below:

flutter doctor -v

Hi @gionlime Thanks for filing the issue, It looks fishy here. Please note that you cannot build an ios app on windows and you need a mac to build for ios so I believe this is working as intended.
Thanks

If you are trying to run the app on the ios simulator on mac in release mode, it's not supported as well Here's the related issue https://github.com/flutter/flutter/issues/11754
Closing as working as intended if you disagree fee free to write in the comments and I will reopen it.
Thank you.


Is there any command only for inference? codes in main.sh are all used for training

Please wait for several days. I need to revise the manuscript for now. After that, I will write a tutorial for how to conduct inference. Stay tuned.

https://github.com/anthonyweidai/SvANet/commit/e9d0a1ae112818aaa5ab527d1223e9f32fdace0b


parseQueryString method parse array with one element as object

Can be easilly checked by following fixture:
expect(parse('a[0]=b')).toEqual({a: ['b']});

Fixed.


Is an Empty VersionOverrides1_0  acceptable?

This document talks about the VersionOverrides element. However in the scheme of things, even before VersionOverrides1_0 is defined in the manifest, a default mode of operation/behavior is already defined. Something like this :
  ...
  <Hosts>
    <Host Name="Mailbox" />
  </Hosts>
  <Requirements>
    <Sets>
      <Set Name="MailBox" MinVersion="1.1" />
    </Sets>
  </Requirements>
  <FormSettings>
    <Form xsi:type="ItemRead">
      <DesktopSettings>
        <SourceLocation DefaultValue="..."/>
        <RequestedHeight>250</RequestedHeight>
      </DesktopSettings>
    </Form>
  </FormSettings>
  <Permissions>ReadWriteMailbox</Permissions>
  <Rule xsi:type="RuleCollection" Mode="Or">
    <Rule xsi:type="ItemIs" ItemType="Message" FormType="Read" />
  </Rule>
  ...

  <VersionOverrides xmlns="http://schemas.microsoft.com/office/mailappversionoverrides" xsi:type="VersionOverridesV1_0">
    ....
    <VersionOverrides xmlns="http://schemas.microsoft.com/office/mailappversionoverrides/1.1" xsi:type="VersionOverridesV1_1">
      ....

So in effect, we do have three modes of operation correct? 1_1, 1_0 and the default operation. So in my understanding if the "Requirements" are not met. for overrides 1_1 and 1_0, overrides will never be used and the default operation will be used. In this light, and in consideration of the manifest snippet below, I would like to ask 2 things :
  ....
  <Hosts>
    <Host Name="Mailbox" />
  </Hosts>
  <Requirements>
    <Sets>
      <Set Name="MailBox" MinVersion="1.1" />
    </Sets>
  </Requirements>
  <FormSettings>
    <Form xsi:type="ItemRead">
      <DesktopSettings>
        <SourceLocation DefaultValue="..."/>
        <RequestedHeight>250</RequestedHeight>
      </DesktopSettings>
    </Form>
  </FormSettings>
  <Permissions>ReadWriteMailbox</Permissions>
  <Rule xsi:type="RuleCollection" Mode="Or">
    <Rule xsi:type="ItemIs" ItemType="Message" FormType="Read" />
  </Rule>
  <DisableEntityHighlighting>false</DisableEntityHighlighting>

  <VersionOverrides xmlns="http://schemas.microsoft.com/office/mailappversionoverrides" xsi:type="VersionOverridesV1_0">
    <VersionOverrides xmlns="http://schemas.microsoft.com/office/mailappversionoverrides/1.1" xsi:type="VersionOverridesV1_1">
      <Requirements>
        <bt:Sets DefaultMinVersion="1.5">
          <bt:Set Name="Mailbox" />
        </bt:Sets>
      </Requirements>
   ....

Making VersionOverrides1_0 empty, will force environment that do not support mailbox version 1.5 to use the default mode of operation. Correct? The drop-down list box type of UI.
And corollary to that, manifests with empty VersionOverrides1_0 (intentionally done), are perfectly valid manifests right?

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

ID: a9caa983-63bf-9ec7-6885-acc576f18747
Version Independent ID: b7f72393-be3e-3237-7b2c-b43dc26a2061
Content: VersionOverrides element in the manifest file - Office Add-ins
Content Source: docs/reference/manifest/versionoverrides.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@glr0221 Thanks for asking about this.
@Rick-Kirkham Can you take a look and direct as appropriate?
Thanks.

@JuaneloJuanelo any updates on this? thank you so very much!

@JuaneloJuanelo any updates for this item? thanks again.

@ElizabethSamuel-MSFT
Seems like @JuaneloJuanelo may not have the time to answer my inquiry. Any chance somebody else can take my question on? Thanks.

@glr0221 Apologies for the wait. We're checking for an appropriate person who can look into this issue. Thx.

@ElizabethSamuel-MSFT thank you always for your support. This inquiry is a bit critical for us, that is why there is some sense of urgency. Thank you very much for understanding.

@glr0221 Understood. Working on getting you the help you need.
@exextoc Is this something you can help with? Can you take a look?
Thanks.

That is correct. From our documentation regarding support of requirement sets on clients, the only clients that do not support 1.5 is 2016 one-time purchase and 2013 one time purchase (MSI versions). Are you trying your target for the addin to only the clients that use those builds of Outlook? 1.5 will be supported for other clients, say MAC and Browser.
Yes, an empty versionOverrides1_0 is totally valid.

Thank you @exextoc ... you saved me a lot of trouble.
Yes you are correct. I am trying to custom our manifests based on supported mailbox versions. Thank you so very much.
@ElizabethSamuel-MSFT Thank you and I am closing this ticket.


4.3.4 release doesn't have packages

Required Information

[X] AEM Version, including Service Packs, Cumulative Fix Packs, etc: all
[X] ACS AEM Commons Version: 4.3.4
[X] Reproducible on Latest? yes/no

Expected Behavior
Current release package binaries are missing from the release page.
Actual Behavior
These files should be there.
Steps to Reproduce
https://github.com/Adobe-Consulting-Services/acs-aem-commons/releases/tag/acs-aem-commons-4.3.4
You'll notice only the source is downloadable.
Links
Links to related assets, e.g. content packages containing test components

Sorry about that, my fault!  In the near term you can always find them in bintray.  https://bintray.com/acs/releases/acs-aem-commons/4.3.4#files/com/adobe/acs

Updated the release with binaries.  Note: The apps and content packages are now split as this is considered the in-vogue best practice.  This will affect any projects that include ACS Commons packages directly.  If you deploy ACS Commons separately from your other packages then you should just note there are two packages instead of one now.


Share ScanNet skip.lst

I believe that ScanNet has a few frames where the pose matrices are all -inf, and others where the depth is all missing. For both cases, the Ponder pretraining code ends up throwing an error, and I'm guessing that is why you added the skip.lst file for the scannet.py dataloader.
Would it be possible to share this skip list, since it is not included in the repo and I want to make sure that I am training on the same data that you did :)
Thank you!

I generated the skip list using this file -- hope it helps!
import argparse
import os

import numpy as np
from tqdm import tqdm

def crawl_and_check_pose_files(root_dir, output_file=None):
    scenes = [
        d for d in os.listdir(root_dir) if os.path.isdir(os.path.join(root_dir, d))
    ]
    with open(output_file, "w") if output_file else None as f:
        for scene in tqdm(scenes, desc="Processing scenes"):
            scene_dir = os.path.join(root_dir, scene, "pose")
            if os.path.exists(scene_dir):
                for file in os.listdir(scene_dir):
                    if file.endswith(".txt"):
                        file_path = os.path.join(scene_dir, file)
                        try:
                            matrix = np.loadtxt(file_path)
                            if np.any(np.isinf(matrix)):
                                frame_id = file.replace(".txt", "")
                                output = f"{scene} {frame_id}\n"
                                if f:
                                    f.write(output)
                                else:
                                    print(output)
                        except Exception as e:
                            print(f"Error reading {file_path}: {e}")

def main():
    parser = argparse.ArgumentParser(
        description="Crawl directories for pose files, identify files with all -inf values, and save the results."
    )
    parser.add_argument(
        "path", type=str, help="The root directory to start crawling from."
    )
    parser.add_argument(
        "--output",
        "-o",
        type=str,
        default=None,
        help="File to save the output. Prints to stdout if not specified.",
    )

    args = parser.parse_args()
    crawl_and_check_pose_files(args.path, args.output)

if __name__ == "__main__":
    main()

Hi, thanks for your interest and your awesome code! Sorry for the late replt, I was on vacation last month ：）Year we skip some broken data, and this is the skip.lst we use. I think your code can produce similar file with ours:)
skip.lst.txt

I have pushed our skip.lst file to the repo :)


Remove security plugin from our build

Gradle 6.0 deprecated the use of HTTP in build scripts by default.
We should rely on the build tool support instead of maintaining a custom
plugin. An upside is that it catches HTTP repositories in settings,
a downside is that it does not fail the build but uses deprecation
warnings.

@melix @jjohannes Just happened to see this while browsing our build files. Not sure if I'm missing something obvious but it sounded like a candidate for simplification.

@bot-gradle test RFM

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


Spike to understand how far turning our CSS variables to CSS ones would bring us

What
Try introducting CSS custom properties for each of the variables in _colours-applied.scss settings file to identify potential breakages from doing so.
Assess the impact of having turned those to CSS custom properties in browsers that don't support CSS custom properties (IE11), and potentially older Sass compilers.
With the variables in place, provide a second set of values for them that would trigger a dark mode and identify what works or breaks.
Why
This provides a cheap way to find out the impact of us moving to CSS variables for running a dark mode.
Who needs to work on this
Developers
Who needs to review this
Developers, potentially with designer and accessibility specialist support
Done when:

[ ] We've documented the impact of turning our applied colours into CSS custom properties, especially

[ ] Possible chances that need to happen inside Sass code so it compiles OK
[ ] The impact on browsers that don't support CSS custom properties, ideally with one or multiple fallback plans we could implement
[ ] The impact on people using older Sass compilers ('It does not compile' could be enough there)
[ ] What swapping some of the values of these custom properties gives us for implementing a dark mode and what other values we may need to change

Initial findings documented in this google doc (internal to team only)

[!IMPORTANT]
This is a writeup of a speculative spike into 'dark mode', specifically in the context of things built using the Design System appearing in webviews in apps. This may ultimately not go anywhere, and doesn't mean that dark mode for the wider web version of GOV.UK is likely or even viable.

As a first attempt at spiking this we tried defining the applied CSS palette as CSS variables in Sass, however we quickly ran into issues where we were trying to treat the underlying value as a colour in Sass (for example passing $govuk-brand-colour to the Sass mix mixin).
We then explored instead exposing the 'applied' palette as CSS variables on the :root (the <html> element)

We then updated references to those Sass variables elsewhere in the codebase to instead reference the CSS variables.
By exposing that 'abstraction layer' in CSS we can make changes to it 'at runtime', dynamically changing which colour should be used for the page background, text colour etc.
As long as components consistently use those abstractions, we can avoid individual components needing to be aware of the existence of a 'dark mode' at all (at least in the majority of cases).
However, unsurprisingly, we aren't doing this consistently and there are some other pain points that came up during the spike.
Pain points we identified
I've used the 'Note' callout to highlight things that we may want to do today, regardless of whether we plan to take any other action off the back of this spike.
Hard-coded use of light-grey to delineate bits of user interface
There are multiple components that are hard-coded to use light-grey as a way to delineate a bit of the user interface, including:

Text input prefixes and suffixes
Inactive tabs
Summary card

These components currently use light-grey in our spike, often with white or light-coloured text on top.

[!NOTE]
We should work out a name for this functional use of colour and create a new variable for it, and then update these components to reference it.
We couldn't easily come up with a good descriptive name for this. It might help to look at what other design systems do in this space.

We also identified that the cookie banner was hard-coded to use light-grey as a background colour (fixed in cd9bfc8). We think that the cookie banner uses light-grey for the same reason the footer does – it's the 'canvas' colour used for the <html> area and everything outside of the <body>, including any viewport after the footer and the overscroll area. As the cookie banner appears above the header, it's conceptually outside of the body of the page.

[!NOTE]
We should update the cookie banner to use $govuk-canvas-background-colour for its background colour.

If we proceed with using CSS variables, we can then use the respective CSS variable instead and dark mode would 'just work'.
Hardcoded use of light-grey for hover states
Some components have a hard-coded reference to light-grey as part of a hover state:

Accordion
Pagination
Task list

These components currently use light-grey when hovered in our spike, often with white or light-coloured text on top.

[!NOTE]
We should create a new $govuk-hover-background-colour and update these components to reference it.

Links
The --style-text link modifier class has a hover state where the colour does not change, but because of a (since fixed) bug in Safari we force an imperceptible colour change to force Safari to re-paint it.
We're doing this by calculating a 99% alpha version of the text colour at compile time in Sass:
https://github.com/alphagov/govuk-frontend/blob/2dd9c90b1376f55db40373d563b836833fd3133d/packages/govuk-frontend/src/govuk/helpers/_links.scss#L229-L235
However, now we want to change what 'text style' means at runtime in CSS, so there's a conflict.
As this bug has now been fixed in Safari we could consider removing the workaround, depending on usage stats. Alternately, depending on whether the versions of Safari we're targeting support it, we could switch to using a CSS function that does something similar at runtime like:
color: hsl(from var(--govuk-text-colour) h s l / 0.99);

File upload
We're setting the native file input element to use color: text-color which is applied to both the button and the filename that displays next to it:
https://github.com/alphagov/govuk-frontend/blob/2dd9c90b1376f55db40373d563b836833fd3133d/packages/govuk-frontend/src/govuk/components/file-upload/_index.scss#L8-L10
However, we're not setting a background colour for the button so in the spike we end up with white text on a grey button.

We'd need to look at the file input component in more detail and understand what's possible in terms of styling the button and how it appears in the different browsers.

[!NOTE]
We should investigate other situations where the fact we're setting the text colour but not the background colour on the file input button may be an issue. There's a chance we might be failing WCAG 1.4.3, 1.4.6 and 1.4.8 due to due to specifying foreground colors without specifying background colors or vice versa (F24)

Header
The header has a hardcoded reference to white for the bottom border, which is  designed to blend with the body of the page. This means that we ended up with a stripe of white in our spike (fixed in 9fcff9b):

The header also has two hardcoded colours which are not part of the colour palette:

#2e3133, used for the border between items in the navigation on mobile
#1d8feb, used to delineate the 'active' navigation item

[!NOTE]
There is another piece of work happening around navigation which is likely to involve changes to the header component, which means it's not worth investing much time on improvements. I think it may still be worth:

updating the bottom border on the header to reference $govuk-body-background-colour
changing the border colour to use one of the greys from the colour palette

Footer
The footer includes an image of the coat of arms of the United Kingdom, which is a single-color PNG in light-grey

Depending on the colours we end up using, we may need a way to recolour it depending on mode. This might mean switching out to an SVG (which has been explored before, but discounted because the complexity of the paths results in a comparatively larger file) or using e.g. filter.
Warning text
The '!' icon within the warning text component is hardcoded to use black for its background and border and white for the text colour.
This means that in dark mode although the exclamation mark is visible, the circle is not and the icon has less overall prominence.

[!NOTE]
We should update the warning text component so that the icon matches the text colour – using $govuk-text-colour for the background and border, and $govuk-body-background-colour for the text colour.

If we proceed with using CSS variables, we can then use the respective CSS variables instead and dark mode would 'just work'.
(This still assumes that warning text will always appear against the body – really we want the exclamation mark to 'punch through' the circle and use whatever background is behind it. But this is an existing issue we can probably consider out of scope…)
Multiple components hardcoded to use white
There are a number of components that are hardcoded to use white, including:

Button (text colour for default, secondary and warning variants; background colour for inverse)
Inverse links, including inverse breadcrumbs and inverse back links
Header
Panel

Although this may be a gap in how we define colours at a system level, we didn't spend much time on this as it seems likely that all of these components will continue to use white in the same way in dark mode.
Tags
Tags appear very 'bright' in the spike and need further consideration.

This is possibly the only place where it seems inevitable that the component will need some awareness of 'mode', and it would be difficult to abstract it away given it references the colour palette directly.
Other unanswered questions
What happens to things that are already 'dark'? What does that mean for 'inverse' modifiers?
There seems to be a general theme emerging that things that already use light text on a dark background would continue to do so in dark mode, rather than being 'inverted' to dark on light, including things like:

the header
'mastheads' / 'heros' (the big blue areas at the top of some pages including the Design System homepage)
the panel component

This suggests that things like inverse breadcrumbs, back links and buttons should remain the same in dark mode.
Which does raise the question of whether 'inverse' is the right name for those modifiers. We briefly talked about '--on-dark' as an alternative.
Text inputs and textareas
Should text inputs and textareas continue to use black text on a white background, or should they match the body background and text colour?

Still to do…

Understand the impact on CSS weight
Understand the impact on older browsers that don't support CSS variables

We need to think about print styles as part of this – we only want dark mode to apply to screen media, when printing we want to keep the dark on light theme.

[!NOTE]
We might want to set up visual regression for our print styles in Percy to catch anything that falls through the gaps, rather than rely on manual testing (and remembering that this is a thing!)

The meta.module-variables Sass function could be really useful for iterating over variables to export them as CSS properties, but requires us to be in a Sass module world.

The spike-css-custom-properties branch holds a codebase where dark mode is implemented through custom properties.


adds bug fix for mask value checking

Made changes to error checking module to address mask value checking issue.

Can one of the admins verify this patch?


Add support for FSharp.Json serialization library

It would be nice to have support for F# FSharp.Json library to the already existing Thoth, Newtonsoft and SystemTextJson.
Will try implementing that for my local project for now, if it works -> will create a PR in this repo.
Any suggestions on impoving the code will be highly appreciated. 🙂

@dbrattli could you please help with understanding next things:?
        // json handler w/ FSharp.Json library
        let json<'TResult> (options: JsonConfig) (source: HttpHandler<HttpContent>): HttpHandler<'TResult> =
            let parser (stream: Stream) =
               use sr = new StreamReader(stream)
               // `ReadToEnd` can throw OOM exception. What is the best way to handle it in Oryx?
               let textJson = sr.ReadToEnd()
               Json.deserializeEx<'TResult> options textJson

            parse parser source

What is the best way to handle OOM exception for StreamReader.ReadToEnd()? I have only seen one for Thoth, but I don't know if it will be an OK to return Result wrapped model

match ret with
                | Ok result -> return result
                | Error error -> return raise (JsonDecodeException)

What is the purpose of JsonPushStreamContent and do I need to implement that as well?


testsuite: ztress: multi-cpu case fixed

testsuite: ztress: Make cpu load calculation multi-cpu ready
Use idle threads on all cores for cpu load calculation.
Additionally, minor tweaks which fixes tests for multi-cpu and qemu_cortex_a9. Removing limitations from tests.

Note that ztress might be somehow disturbed by #41792 since cpu_load value is invalid.

Failing compliance check cannot be fixed. UTIL_LISTIFY does not support adding separator so semicolon termination is required.


move install to /usr/local from /usr/

It works for Silveblue. In reference to #20

@Aman9das
Thanks for contributing, can you please check if the built-in app updater is working with these changes?

It installs the package to the correct directory.

@Aman9das
Thanks, I'll check the gui one and will merge this pr.


Add the dynamically assigned IP address to the Kubernetes Ingress

As a Kubernetes user, when I specify an Ingress with a dynamic IP address, I want to see the IP address that was assigned by the Infoblox and used by the F5 BIG-IP when viewing the Kubernetes Ingress object

Implemented in commit 1779ef9511ad53b5e8f1b7b5918b06b1361a03e9


Support for custom save locations

beet watch --link <World> seems to .minecraft folder for saves.
My saves are however located in a custom location (the new Launcher supports that).
Is there an option to change the folder in which beet will look?

When you use beet link or the --link option you can also give it the full path to your world folder. The following commands are equivalent:
$ beet link Demo
$ beet watch --link Demo
$ beet link C:\Users\name\AppData\Roaming\.minecraft\saves\Demo
$ beet watch --link C:\Users\name\AppData\Roaming\.minecraft\saves\Demo

Thx for the help. I watched your video again thats why I closed the issue already :D. But now its at least searchable for others :)


change Directory?

How can i change a Directory ??? cd .. does not working

Hello, at the moment we don't have support for changing directory.
If you need specify some file or folder from a specific directory, you should enter the entire path.

No more required since we have web UI.


[HELP] - Creating integration tests

Hi guys!
We are trying to create some basic integration/snapshot tests for our app.
Here is the repo: https://github.com/Danwhy/learn-react-native/tree/master/testing
Our tests are just hanging or always passing. However in general we would like to know how to write basic integration tests for components.
Any suggestions are more than welcome!:)

:+1:

:+1:

:+1:

Check out: https://github.com/kif-framework/KIF for acceptance testing - I've had good success using this on a React Native app. Alternatively, like you have attempted here, you could use the integration testing harness built into React Native. Sorry there is not currently a lot of documentation around this. @tadeuzagallo may be able to help you out. If you figure it out we would love to add a section on this to the docs!

@brentvatne you suggested, also https://github.com/facebook/webdriveragent .
Close?

Happy to close it guys! Thanks for the feedbacks!

:smile: :rocket:


Check constructor equality in .toStrictEqual()

Associated Issue: #6767
Summary
Modified typeEquality to check for constructor equality and not just compare constructor names. This makes .toStrictEqual() no longer treat different classes with the same name as equal.
Test plan

Added a test case that verifies that .toStrictEqual() no longer treat different classes with the same name as equal.

@emilsjolander mind taking a look?

@SimenB Changelog updated ✔


migrate from travis-ci to github actions

@andylytical I am trying to resurrect CI by migrating to github actions.  Recent versions of yamllint are now paying attention to quoting for array values, which required fixing up some of the NCSA hierarchy.  Of course, github actions are having trouble today...


Support Microsoft Edge Chromium, fix Chrome driver download

This pull request is a combination of:

Fixing the Chrome driver discovery and download
Support for the Microsoft Edge Chromium browser (removing Edge HTML support)

Unfortunately, I cannot get it compiled with xuggle, so I had to disable video capture, any help with this would be appreciated.
I added a new downloadable release for public use.

@rhpijnacker About the huggle I had replaced it https://github.com/groupon/Selenium-Grid-Extras/pull/410
And then I had completely removed it and used ffmpeg intead https://github.com/groupon/Selenium-Grid-Extras/pull/412 also some memory leaks fixes in the same area https://github.com/groupon/Selenium-Grid-Extras/pull/411 ...

Can this be merged?  I'm looking to use edge chromium and i cannot do it in the 2.0.4 snapshot version.  @damencho  @rhpijnacker

@rrapier You can try https://github.com/rhpijnacker/Selenium-Grid-Extras/releases/tag/v2.1.0

I grabbed the release version and started it up.
i am getting the following on execution:
[INFO ] 2022-07-20 09:30:15 Log - Started with Driver Creation
error	20-Jul-2022 09:30:15	org.openqa.selenium.WebDriverException: Error forwarding the new session cannot find : Capabilities {browserName: edge, deviceType: Web, platformName: windows, report.customFields: Build=Release,ReleaseName=0..., securityToken: eyJhbGciOiJIUzI1NiIsInR5cCI..., takesScreenshot: true, user<EMAIL_ADDRESS>I noticed it downloaded msedgedriver version 75.  Edge latest is 103.  Why is it not grabbing latest version of edge driver?

I think it downloads the version that you have specified in the node_5555.json file.
Could it be it is configured for version 75 there?
You could try removing all json files and running the initial configuration again.


ukvm running in a container does not handle SIGINT

There is no default handler for SIGINT for processes with pid=1, so we need to add one. This is based on:
https://github.com/docker-library/mysql/issues/47
https://github.com/docker/docker/pull/3240

fixed


Document supported env variables for transaction-logger service

Ensure that TRANSACTION_LOGGER_PGPASSWORD etc. are documented in the README or in a new file that includes the parts from legacy-transaction-logging.md that are not actually legacy (i.e. PostgreSQL setup).
See #24.

Resolved by #41 in the context of removing support for the legacy method.


Should yarn be mentioned as a step during installation

Even though yarn/node_modules aren't strictly required for the base installation, the engines setting in package.json is not checked during ./script/build-release dist (one of the steps in documentation) is run. I ran into an error while running this on node 8.9.4[1], which didn't point to this. Running yarn in the folder after clone would hint users to this better, making the UX better.
Should the step be added in docs?
[1]:
><EMAIL_ADDRESS>build /Users/kashyap.k/Documents/github_clones/rome
> ./scripts/build-release

 Building trunk
Error thrown inside the CLI handler
TypeError: stdout.off is not a function
    at Object.outStream.teardown (/Users/kashyap.k/Documents/github_clones/rome/scripts/vendor/rome.cjs:69854:20)
    at ___R$project$rome$$romejs$cli$reporter$Reporter_ts$default.removeStream (/Users/kashyap.k/Documents/github_clones/rome/scripts/vendor/rome.cjs:70010:16)
    at ___R$project$rome$$romejs$cli$reporter$Reporter_ts$default.teardown (/Users/kashyap.k/Documents/github_clones/rome/scripts/vendor/rome.cjs:70419:14)
    at endEvent.subscribe (/Users/kashyap.k/Documents/github_clones/rome/scripts/vendor/rome.cjs:94782:25)
    at ___R$project$rome$$romejs$events$Event_ts$default.call (/Users/kashyap.k/Documents/github_clones/rome/scripts/vendor/rome.cjs:5950:29)
    at ___R$project$rome$$romejs$events$Event_ts$default.callOptional (/Users/kashyap.k/Documents/github_clones/rome/scripts/vendor/rome.cjs:6022:21)
    at ___R$project$rome$$romejs$core$client$Client_ts$default.end (/Users/kashyap.k/Documents/github_clones/rome/scripts/vendor/rome.cjs:95097:27)
    at ___R$project$rome$$romejs$cli$cli_ts$default (/Users/kashyap.k/Documents/github_clones/rome/scripts/vendor/rome.cjs:98319:18)
    at <anonymous>

I don't think it makes sense to recommend running yarn or npm just to get the engines validation. We could add a step to all scripts to check it instead.

Just created and merged #209 which adds the message to all scripts. You will still encounter syntax errors if your Node version doesn't support any of the syntax that the scripts use, but that's a much better indicator for an outdated Node than some obscure API calls. Thanks for the report!


Use new base58 parser (Version: 2.1.0)

Summary
rippled introduced a new, faster parser for base58: https://github.com/XRPLF/rippled/pull/4327
Motivation
15x faster than the previous implementation. It shows about 10% speedup for RPC commands in rippled and should be for Clio too.
Solution
Use the new parser.
Paths Not Taken

Write our own parser.
Use a library
Leave as is

Looks like nothing to do in Clio in order to support this.
The fast algorithm is automatically used when compiled outside of MSVC (relies on __int128 found in both gcc and clang).
Clio already uses libxrpl's base58 functions and does not use other 3rd party library for this nor introduces a custom parser for base58.


impossible to go back from amendments to motion

open a motion with e.g. 2 amendments
click o the amendments button to see the amendments of this motion
now try to go back to the motion

result: this is not possible because you can only go back to the list of motions. This is annoying for conferences with many motions because you loose time to select the motion in the motion list. The solution is a back button to the motion of the amendments like there is in all other lists.

You are in the amendment list for one specific parent motion, right? If so, you can click on the selected lead motion.

You are in the amendment list for one specific parent motion, right?

No, I am in the list of amendments:

So there is no button to go back to the motion, only to the list of motions.

Please reopen. Please think about usability and intuition. In all cases I can use buttons at the upper right to jump back. Why not here? Just add a new button to jump back to the motion.
 I mean when I as experienced user don't find the way to jump back, other users won't find it as well! Therefore it is worth to consider my proposal as valuable for OS.

Ok, we'll think about an usability improvement for 3.0.

#3909 introduces a head bar which always (should) have a back button to address cases like this.
However, this specific view (motion amendments) is not yet implemented in OpenSlides 3, so I am not closing this issue now.
@donovaly perhaps you may confirm if the current version fits to your expectations?

with #4523, the global back button will navigate to the parent motion if the user is seeing a (single) amendment. There is no amendment list (yet) but this feature is in development

Navigation reworked in OS3.


Failed to build ControlCatalog.NetCore on OS X

Hello! I tried to build & run a sample from samples/ControlCatalog.NetCore on OS X but failed to build it with error:
~/.nuget/packages/sharpgentools.sdk/1.1.2/build/SharpGenTools.Sdk.targets(162,5):
Process error CX0003: Unable to generate XML file with castxml
[~/Projects/Avalonia/src/Avalonia.Native/obj/Debug/netstandard2.0/SharpGen/SharpGen-MSBuild.xml].
Check previous errors.
[~/Projects/Avalonia/src/Avalonia.Native/Avalonia.Native.csproj]

Steps to reproduce:
git clone https://github.com/AvaloniaUI/Avalonia.git
git submodule update --init
cd samples/ControlCatalog.NetCore
dotnet build

Info:
git log --pretty=format:'%h' -n 1
1478f0668
(https://github.com/AvaloniaUI/Avalonia/commit/1478f066829c93f2c5ea6dbb929bfdcd70663405)

dotnet --version
2.2.101

Build log is attached here - https://gist.github.com/KonH/f3611b36916b685e1688a09434fef1e0.
I can run from an app from template (dotnet new avalonia.app -o ...) with Avalonia.Desktop 0.7.0 package, but not from sources.
I will provide additional info if it's required.

brew install castxml. Only needed to build Avalonia itself. Also make sure to build libAvaloniaNative via XCode.


New DSC resource to install tools from dotnet globally

[x] I have signed the Contributor License Agreement.
[ ] This pull request is related to an issue.

This pull request introduces a new DSC resource. It allows users to install .NET tools globally.

@denelon Hi Demitrius, I had gone through the CONTRIBUTING.md, but I was unsure if I had to commit the spec-template file with this PR. Do you want me to include it?

Yes please. Any additional documentation will be helpful as users become informed about the new resource.

It might also be interesting to get you connected to some of the dotnet folks to discuss making dotnet.exe DSC v3 capable. I saw you're writing an e-book on DSC v3 in your GitHub profile.

It might also be interesting to get you connected to some of the dotnet folks to discuss making dotnet.exe DSC v3 capable. I saw you're writing an e-book on DSC v3 in your GitHub profile.

Would love that Demitrius. Great challenge to look at. Indeed I am. Currently storing the content from preview.10 and asked Gael to have a review/foreword. Then probably when dsc gets GA, I'll put it fully live.

We have been discussing a DSC Resource for dotnet recently. I would have thought about using a module name like "Microsoft.dotnet.Dsc" or something like that. I just don't have enough domain knowledge on dotnet to make the best recommendation.

I would recon a naming change. It was just as first thought that popped up.

Related to:

https://github.com/microsoft/winget-dsc/issues/65

@denelon In the latest commit, I have added the option for toolsPath. This allows users to choose a directory to install tools towards.
However, the latest pull request for Microsoft.VSCode.DSC, broke the participation on the export because we removed the static method. I asked Mikey for feedback on enabling export for class-based resources directly from PSDesiredStateConfiguration.
I have tried to incorporate as much of what Mikey sketched out in this change. It probably requires updating the Microsoft.VSCode.DSC also if this is the way forward.
P.S. After thinking about it, DotNetDsc would to it for me.

@denelon In the latest commit, I have added the option for toolsPath. This allows users to choose a directory to install tools towards.
However, the latest pull request for Microsoft.VSCode.DSC, broke the participation on the export because we removed the static method. I asked Mikey for feedback on enabling export for class-based resources directly from PSDesiredStateConfiguration.
I have tried to incorporate as much of what Mikey sketched out in this change. It probably requires updating the Microsoft.VSCode.DSC also if this is the way forward.
P.S. After thinking about it, DotNetDsc would to it for me.

I'd suggest trying with the experimental WinGet feature something like:
winget configure export --Resource Microsoft.dotnet.Dsc -o dotnet.winget to see if the settings get exported.
I know this is brutal with class-based v2 modules, but it gives us another working example and helps pave the way for DSC v3. We're investing into improvements for the export feature to capture all installed packages, Windows Settings, and any DSC v3 resources (soon to be identified in WinGet package manifests).

@ryfu-msft Ryan, sorry for the many commits. I had to re-name the module and figure things out with Semantic Versioning. I have tried to prepare the test to run on the ADO agents. Inside the .psd1 file, the LicenseUri and ProjectUri are included. This is more convenient for people to be redirected when they want to do changes. You mind giving it another look and run the pipelines?
Cheers and have a good weekend already.

/azp run

@denelon I have also sketch out a proposed solution in the sdk repository. I can imagine that it hasn't the highest priority, but if one operation already is exposed, this becoms obsolete.
If there is anyone whiling to participate, my C# knowledge is rusty. A first set up would greatly assist me.

/azp run

/azp run

And thanks for all the feedback! Please let me know when you get it published

@Gijsreyn,
It's published: https://www.powershellgallery.com/packages/Microsoft.DotNet.Dsc/0.1.1-alpha

@denelon Thanks for letting me know. I'll try to put out some docs tomorrow and spend some love in some upcoming blogs I'm writing. Curious to your thoughts. Cheers.

@ryfu-msft and I were chatting about the best place to put docs here, and a sample over at https://aka.ms/dsc.yaml inside the Dev Home repository. We could also consider centralizing examples here now that this repository is open to the public. That would allow me to change the redirect to this repository.