Dependent extensions: error AL0132: 'TestPage G/L Account Card' does not contain a definition for 'Test Field-Xyz'

Unable to build dependent extensions.
We're supposed to upload tests for our extension as a separate package.
So we need to separate our testing codeunits into a dependant extension.test.app.
If we build our packages with al-2.0.46000 or al-2.0.47152 this does not work any more.
If we build with al-2.0.42188 it still works as expected.
The error we get is:
error AL0132: 'TestPage G/L Account Card' does not contain a definition for 'Test Field-Xyz'
I have attached code for two extensions ( range 60200 and 60201 ).
TST.BASE.DEP app extension has a dependency on TST.BASE app extension.
As mentioned, building with al extension gives the following results:

al-2.0.42188  ... works as expected
al-2.0.46000  ... compilation fails
al-2.0.47152  ... compilation fails

dep.ext.test.20180925.001.zip

Same issue here:
Building test automation with al-2.0.46000 doesn't recognize Page Fields and Controls of depending app.
Building test automation with al-2.0.43900 everything works fine.

Hi! The issue has been fixed in the latest release. It should be available shortly.


Add quote section

Description
Section that contains the quote: "קוד פתוח הוא בסיס לקהילה שעובדת יחד..."
This section makes for a good first issue, make sure to create it exactly like the figma design.
Relevant files:

components/Home/Quote.tsx
app/page.tsx

Screenshots
No response
Additional information
No response

Hi, please assign me to this issue :)

Have fun :)

How is it going? ask in our community discord channel if you encounter any issues or need to clarify something 😃

Is all well? @Etinger-Asaf

Yes, thanks for asking.
I had some minor delays.
I'm sure I'll submit the PR this weekend. 💪🏻

#49


no wheel for Python-3.8.0b3 on pypi

wheels for Python-3.8.0b3 on pypi would be appreciated

to get winml access, via winrt https://images.anandtech.com/doci/14514/Blueprint Series_May 16-2019_COMBINED FINAL_AnandTech (2)-page-083.jpg

I have no idea what "wheels" are and we don't currently have anyone working on Python support and the link you shared looks like spam. 😉


Bump MSRV to 1.48.0

Per https://github.com/console-rs/console/issues/134#issuecomment-1307391821
Closes #139

The macOS test failure should be easy to fix by use an old version of Xcode, wasm32-wasi build failure is caused by https://github.com/rust-lang/rust/issues/103306 which will be stabilized in 1.67.0, we can switch to nightly for now.
I'm not sure how to deal with the wasm32-unknown-unknown build failure.

wasm32-unknown-unknown support for errno was discussed in https://github.com/lambda-fairy/rust-errno/issues/21.

Does terminal_size actually work on WASI? Because if all it does is have some hardcoded fallback then the sanest option would probably be to just stop using that crate for WASI.

Now that I looked closer at this I'm not a huge fan of the fact that terminal_size 0.2 pulls in that many dependencies for what should be a rather simple task. I wonder if it wouldn't be better to switch to manual implementations again rather than using terminal_size.

Does terminal_size actually work on WASI?

@eminence any idea?

Does terminal_size actually work on WASI?

@eminence any idea?

No, terminal_size doesn't target WASI at all.  I'm not sure if WASI today has any interfaces to get things like "terminal size".  @sunfishcode -- Do you know if this is something that WASI might support in the future?
@messense I'm now thinking that terminal_size should just return None on WASI targets.  Would that be useful for you here?

@eminence That's right; WASI does not currently have APIs for returning the terminal size. It may in the future though.

The code is really very small, so I think you should be able to very easily drop terminal_size and just include the relevant code directly in console.


RFC: an attempt to add a new module which can run custom shell scripts

Unlike other modules, Command module was designed to be able to be used mulitple times. A special option --command-text can be set multiple times; each option specifies one script to be executed.
For example:
$ ./fastfetch -s title:separator:os:command:command:command \
            --command-key GCC --command-text 'gcc --version | head -1 | awk \'{print $3}\'' \
            --command-key CMake --command-text 'cmake --version | head -1 | awk \'{print $3}\'' \
            --command-key PkgConfig --command-text 'pkg-config --version'

I still think we should add a general way to print a module multiple times with different configs. A lot of modules would benefit from that.
But for now i think this MR is fine.

Yeah. Apart from https://github.com/LinusDierheimer/fastfetch/discussions/310, I have a thought that embed a script language such as lua, so that users have full control of module formatting and printing.
But those are all the long-time plan. For now this PR is the easiest solution I can come up with.


Syntax Error in import

Looks like a typo in gmail.py :
irecipient_idmport imaplib
import logging

Thank you for opening this issue, resolved the issue.
Commit - https://github.com/girishramnani/gmail/commit/fb4a125449a19e0be95c00b249c78f3f52c06e9a


chore: prepare for automatic release

This PR

Enforce more strict Clippy rules and fix collisions in existing code.
Configure build pipeline to pick the rules.
Add release-please workflow.

Related Issues
#4
Notes
Follow-up Tasks
How to test

release-plz/CI config looks right to me.

Thank you @toddbaert for helping out! How can I configure the CI/CD secrets?
I definitely do not mind if someone else getting it done...:-)

@sheepduke I just finished setting this up with the @openfeaturebot account. I think we're ready to test now!

@sheepduke I just finished setting this up with the @openfeaturebot account. I think we're ready to test now!

Great. Let me submit a test PR.


predict values

from same above example for which preproccessing is shown
y_pred, confidence = deeplog.predict() gives output in torch.tensor() also evertimes its giving different values in tensor. eg. [127],
[127],
[127],
[127]
how to get actual values like anomaly or not whenever new line is passed or same sample is passed for prediction?

I have added a new example_hdfs.py file in the /examples/ directory that gives an example on how to perform anomaly detection using the HDFS dataset

yeah that helped

for according to this example predict will state 1 or 2 but when i ran this it was giving [127], [127], [127] and everytime this is changing. I was also expected 1 or 2. why in this this case it was giving random state?
what does hdfs_test_abnormal data covers? how it is prepared? I dont have abnormal routine database.


Expanded Storage support

https://www.curseforge.com/minecraft/mc-mods/fastchest?comment=26

I saw your comment on curse, and I was gonna say you'd have better luck asking the people over there at Expanded Storage.
But somebody already requested the same thing on their bug tracker (https://github.com/NinjaPhenix/FabricMods/issues/87) so you should keep an eye on that.


Use checkbox instead of Buttons

For each container, tray provides two buttons (SSH & DESKTOP). Suppose, the user has 10 containers. So he will have 20 buttons on one dialog, and most of the DESKTOP button would be disabled. Soon the third button will be added, which is Upload button. But instead of adding button all over the dialog, we can use checkboxes to select containers and  EZ-SSH, EZ-DESKTOP or EZ-UPLOAD into them. Design of dialog would be improved also.

Done.


minor README updates

change docker-compose to the more current 'docker compose', and add a line about untrusted L1 node usage. See https://github.com/base-org/node/issues/2 for discussion around the latter.
cc: @protolambda @mdehoog

thank you 🙏


Role to install custom grafana + dashboards

hey @vadimzharov, I think that rather than cary a custom ansible role, we would rather use an openshift-applier based approach, as all we're really doing is deploying YAML files. We're using the approach here: https://github.com/redhat-cop/openshift-toolkit/tree/master/custom-dashboards


Models update

Models version: 5301f781e3dd173c8aa116dd5d3a97303e35477e
Tools version: b7ae4e39a0d82327349d40ed42a249c48b951774

@kchechil

@atsyplen please provide link to PR with config update for resnet-50-binary model.


Buffer writes to SQL database for speed

Queue the writes to the sql database to keep it open less, and reduce number of I/O operations. P.S.: Hey landmaster, was trying to figure out how to contact you and figured this would be a decent way to get in contact. I had been working on a website similar to btd6index, but more general purpose, when i saw you had made btd6index.win. Not sure if you'd be interested, but I had begun work on a website that includes things such as a megalist of challenge solutions (with hints but that takes a ton of time so its on the back burner), 2tcs, a gui for quincybot's features (and some more, like a hero xp reverse calculator [figure out when a hero needs to be placed to hit a certain level by a certain round]). If you're interested in talking, you can either continue the conversation here, or reach out to me on discord. My username is wordsmith123. If you don't have discord, I'd be happy to provide my email on request. Cheers.

The sql database write script there was just a one-time migration script for moving data from the old spreadsheet where 2 towers co-op chimps were once stored and is no longer needed anymore, but thanks anyway


Fix markdown lint

markdownlint not access now: https://github.com/alibaba/sealer/actions/runs/1220419777
check markdown locally:
$ docker run --rm \
    -v "$(pwd)/CHANGELOG.md:/CHANGELOG.md:ro" \
    avtodev/markdown-lint:v1 \
    --rules /lint/rules/changelog.js \
    --config /lint/config/changelog.yml \
    /CHANGELOG.md

More informations:
 https://github.com/marketplace/actions/markdown-linting-action

I am afraid that I have corrected all the markdown issue. I think we could close this. While please feel free to re-open it if needed.


Implement support for json-api

The Open Event Server is moving towards a new API as per the json-api specification. Hence all the client apps need to support the same.
You can checkout some of the Android client libraries that you can use to easily consume the API at http://jsonapi.org/implementations/#client-libraries-android.

@iamareebjamal are you working on this?

@mejariamol I don't think any one person will be sufficient for this. And check out this -> https://github.com/fossasia/open-event-android/issues/1680
We should be working with Android app team to develop a common solution. I have been implementing test apps mocking the json api. But having difficulties due to all libraries requiring to extend some classes. I'm currently analyzing the code of Open Source libraries to see any possible workarounds

https://github.com/iamareebjamal/open-event-android-sdk


Add health checks and down detection to main docker container

See https://discord.com/channels/1305640521364144210/1305640978975297707/1310098087544356984

do you run it with your docker-compose file then?

do you run it with your docker-compose file then?

Yes


Add isVideoMirrored option to disable mirror flip camera

Thanks! It will be released in the next update.


Add transfer command

Description
Add transfer command and transfer packet

Testing
tested with 2 local servers

Checklist
Things need to be done before this Pull Request can be merged.

[x] Code is well-formatted and adheres to project style guidelines: cargo fmt
[x] Code does not produce any clippy warnings cargo clippy

LGTM.
Thanks @Commandcracker


Feat(core): Update toast design

#4

Icon size should be 24x24

The icon can be leave as-is.. we'll need another update in Moai to change it. Please fix this though:

#20 should address this


Unable to save decrypted image.

I think this might not be entirely an issue with this library as the same code essentially work in react native, but on the web, the file generated by the JS is constantly "corrupted".
imageData = crypt.decrypt(privateKey(), encrypted).message;
The data coming out from that doesn't seem to be the same in react native and the web for binary data.
I save it off to a file and compare the size is different, original 1.9m vs encrypted and decrypted 1.8m

further looking through the code it might be as simple as being able to request the bytes instead of the utf-8 in decrypt(privateKey, encrypted) in https://github.com/juhoen/hybrid-crypto-js/blob/master/lib/crypt.js#L106

Hi and thanks for the issue and a possible solution. Unfortunately I'm currently busy and not able to solve this issue until next week. However, if your solution works, feel free to fork project and create pull request. That might speed up things little bit :)

working on it, but not a big JS guy,  how do you run the webpack. I am getting Couldn't find preset "react-native" relative to directory

You can generate webpack by running
npm run webpack. Unfornately the project currently doesn't include simply way to test webpacks so you have to do it manually. Open file with the browser and use developer tools to debug. Hope this helps!

ok, that is where I am getting the
`

browserify lib/webpack.js -o web/hybrid-crypto.js -t [ babelify --presets [ react-native ] ]

Error: Couldn't find preset "react-native" relative to directory "./hybrid-crypto-js" while parsing file: ./hybrid-crypto-js/lib/webpack.js
`
I am more or less muddling my way through, thanks!

yeah, i am actually at a loss.  I still get back a string so not sure where to go.  sorry

No problem, I will take a look later on.


feat(oidc-service): adds oidc-service functionality

Description
Adds oidc-service
Fixes #265
Type of change

[ ] New feature (non-breaking change which adds functionality)

Checklist:

[ ] Performed a self-review of my own code
[ ] Code conforms with the style guide

Hi @jamescrowley321
Please review the changes. I have updated based on your comments.


Refactor trust store tests to use mocks instead of full objects

Some trust store tests in go/lib/infra/modules/trust/trust_test.go use entire Messenger objects on top of fake point to point connections built on pipes. These connection do not propagate address information correctly, which makes stricter address checking in the messenger break the tests. The goroutines needed to run multiple messengers also make the tests difficult to debug.
Now that we have mocking support, the tests should be refactored to run in a single goroutine, with the trust store running on top of only mocked objects.

Supported in new trust store


importccl: cleanup how we ignore stmts in IMPORT PGDUMP

PR: https://github.com/cockroachdb/cockroach/pull/57827
From release notes:

Added a new IMPORT PGDUMP option, ignored_stmt_log, which allows users to specify where they would like to log stmts that have been skipped during an import, by virtue of being unsupported. [#57827][#57827] {% comment %}doc{% endcomment %}

Made obsolete by #10147.


process.env should not be attached inside window object

Bug report

What is the current behavior?
Just setted a set of compilation rules to compile a web project along with webpack-dev-server, here's an example:
function botonicDevConfig(mode) {
  return {
    mode: mode,
    devtool: sourceMap(mode),
    target: 'web',
    entry: path.resolve('webpack-entries', 'dev-entry.js'),
    module: {
      rules: [
        babelLoaderConfig,
        babelLoaderConfig2,
        fileLoaderConfig,
        stylesLoaderConfig,
      ],
    },
    output: {
      filename: 'webchat.botonic.js',
      library: 'Botonic',
      libraryTarget: 'umd',
      libraryExport: 'app',
    },
    resolve: resolveConfig,
    devServer: {
      static: [
        path.join(__dirname, 'dist'),
        path.join(__dirname, 'src', 'nlu', 'models'),
      ],
      liveReload: true,
      historyApiFallback: true,
      hot: true,
    },
    plugins: [
      new HtmlWebpackPlugin({
        template: path.resolve(botonicPath, 'src', 'webchat.template.html'),
        filename: 'index.html',
      }),
      new webpack.HotModuleReplacementPlugin(),
      imageminPlugin,
    ],
  }
}

After running the command webpack serve --env target=dev --mode=development and opening the browser, process object comes inside the definition of window object (attached screenshot), with env set as an empty object. See that I'm not using any kind of Environment or Define Plugin, I don't want to have process defined. In previous versions (webpack 4), this variable was undefined (as far as I understand, this should be the common behavior).

If the current behavior is a bug, please provide the steps to reproduce.
After setting above rules,

What is the expected behavior?
process.env should not be attached by default. It should be enabled (in any case) after using some of the plugins to define env variables.

Other relevant information:
webpack version:  5.9.0
Node.js version: v10.23.0, also tried v12.20.0 with same results.
Operating System: macOS Catalina 10.15.7
Additional tools:
"webpack": "^5.9.0",
"webpack-cli": "^4.2.0",
"webpack-dev-server": "^4.0.0-beta.0" (I needed to update dev server in order to make it work, it seems to be broken with latest v3.11.0).

webpack itself doesn't add that.
maybe webpack-dev-server @alexander-akait ?

Hi @sokra , check the first lines of code of this, I think you are right: https://github.com/webpack/webpack-dev-server/blob/b0161e9852cdf41730e82aa43efe7e88f44a4f9d/client-src/default/index.js.
If you prefer, let's close this one and I will open it in webpack-dev-server. Thanks 😊

Yep, @vanbasten17 known but, we are working on it


setup stuck at cdrewrite

HI.
I'm interested in trying pynini, but I can't get it installed.
I'm running ubuntu trusty32 version via a vagrant/virtualbox configuration under windows 10.
All the prerequisites, AFAIK, have been installed.
When 'sudo python setup.py install' is run,
the compilations start. However,  the compilation of cdrewrite.cc never finishes. The last thing I see
in terminal is:
i686-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -
fPIC -I/usr/include/python2.7 -c src/pynini_cdrewrite.cc -o build/temp.linux-i686-
2.7/src/pynini_cdrewrite.o -std=c++11 -Wno-unused-function -Wno-unused-local-typedef -funsigned-
char
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
[enabled by default]

I'm not knowledgeable about these kind of complicated installations, so have no idea what might
need to be done to finish the installation.  What do you suggest?

Hi there! Building pynini_cdrewrite.cc is one of the longest steps of the
process, because it translates to a huge amount of machine code. However, I
am able to do it with relatively weak computers (for instance, a $100 ARM
laptop with just 4 GB of RAM) when given enough time---it takes maybe an
hour. If you can wait a bit longer and it's not running out of RAM, I would
just allow that. Since you're compiling in a virtual environment you may
want to make sure your VM has enough computing resources for the
compilation. Or if that's not feasible, you can transpile---compile on
another machine with more juice.
Another possibility---and this is a bit of a hack, but will work for many
people, is the following. I'm assuming you're using the most recent version
of Pynini, which is 2.0.0:

open src/pynini_cdrewrite.cc with a text editor and comment out (or
delete) lines 44 and 45, which read:
REGISTER_FST_OPERATION(PyniniCDRewrite, LogArc, PyniniCDRewriteArgs);
REGISTER_FST_OPERATION(PyniniCDRewrite, Log64Arc, PyniniCDRewriteArgs);

What these lines say is that the cdrewrite function should work for
log-weight arcs. I've actually never had any need to do this---you can just
use tropical arcs and then convert to log arcs pynini.map, if desired,
and it should make compilation go 3x as fast, at least for this file.
FYI this warning here not an error. It's just a (very minor) bug in how
Python is configured on certain platforms; as I understand it it thinks
that when compiling C++ code it should use the strict prototype warnings,
which doesn't make sense for C++ (I don't even know what a strict prototype
is):
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is

valid for C/ObjC but not for C++
[enabled by default]
On Tue, Jul 31, 2018 at 11:51 PM funderburkjim<EMAIL_ADDRESS>wrote:

HI.
I'm interested in trying pynini, but I can't get it installed.
I'm running ubuntu trusty32 version via a vagrant/virtualbox configuration
under windows 10.
All the prerequisites, AFAIK, have been installed.
When 'sudo python setup.py install' is run,
the compilations start. However, the compilation of cdrewrite.cc never
finishes. The last thing I see
in terminal is:
i686-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -
fPIC -I/usr/include/python2.7 -c src/pynini_cdrewrite.cc -o build/temp.linux-i686-
2.7/src/pynini_cdrewrite.o -std=c++11 -Wno-unused-function -Wno-unused-local-typedef -funsigned-
char
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
[enabled by default]
I'm not knowledgeable about these kind of complicated installations, so
have no idea what might
need to be done to finish the installation. What do you suggest?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kylebgorman/Pynini/issues/5, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJuOe1a40thfEB8ixHGDdo9mGTsu8Y8ks5uMSXBgaJpZM4VpzRG
.

Thanks for the helpful comments.
Based on them, I increased the VM memory to 2GB -- this proved to do the trick; setup.py install worked, and took about 10 minutes.
There was another obstacle that occurred with the setup.py test step.
ImportError: libre2.so.0: cannot open shared object file: No such file or directory

https://stackoverflow.com/questions/8323794/re2-library-loading  provided a suggestion;
namely I returned to the re2 folder and issued command sudo ldconfig.
Magically, now python setup.py test ran to completion with  Ran 158 tests in 0.610s.
Also I can now import pynini and begin working with examples in your various tutorial materials on
pynini and openfst.
Incidentally, my motivation is to understand  how to apply something from your https://www.safaribooksonline.com/oriole/string-processing-with-pythons-pynini-edit-transducers tutorial.
Imagine that we have a query string and wish to find the string or strings in a
fixed lexicon it is closest to, in terms of edit distance.

Sounds good, it should be well suited for that. I hope to write more about that kind of edit distance matching in the future ;)
I would guess that you would need at least 2 GB, if not 4 GB, to compile a large project like this.


[QA]  Test the 2023b release cycle.

Target branch: 2023b

[x] Package Updates: :

[x] Check for the updated packages: all packages listed on the link
[x] Check for all the new packages: codeflare-sdk, sklearn-onnx, clients for MySQL, PostgreSQL, MSSQL, and MongoDB.
https://github.com/opendatahub-io/notebooks/pull/205
https://github.com/opendatahub-io/notebooks/pull/263

[x] Check for Add mesa-libGL on the base notebooks
https://github.com/opendatahub-io/notebooks/pull/262

Testing for this is basically about extending relevant tests in our internal ods-ci testing framework.

@jstourac  @harshad16 I didn't move this issue to Jira. I directly moved those two Jiras to our board. If they are complete please let close them on the Jira board


feat(pie-icons): DSW-1997 icons updates

Describe your changes (can list changeset entries if preferable)
[Added] - Icons
Misc

cannabis
cannabis-large
building-blocks
building-blocks-large
pacifier
pacifier-large
experiment
experiment-large

People

baby-kid
baby-kid-large

Technology

laptop-filled
laptop-filled-large

[Updated] - Icons
Pay

account-credit
account-credit-large

Bag & Basket

bag
bag-large
bag-filled
bag-filled-large

Author Checklist (complete before requesting a review)

[x] I have performed a self-review of my code
[x] I have reviewed the PIE Storybook/PIE Docs PR preview
[x] I have reviewed visual test updates properly before approving

Reviewer checklists (complete before approving)
Reviewer 1 - Maryia Radchuk

[x] I have reviewed the PIE Storybook/PIE Docs PR preview
[x] If there are visual test updates, I have reviewed them

Reviewer 2

[x] I have reviewed the PIE Storybook/PIE Docs PR preview
[x] If there are visual test updates, I have reviewed them

I think because this PR from your fork, some of the automated deployments have not worked because they don't have access to secrets/tokens. I think this is necessary because adding new icons should update the docs site.
Please could you push your branch to the original repo (i.e., not a forked repo) and create a new PR from there?

I think as your PR is from a fork, some of the build won't run correctly (as we don't share CI tokens with forks for security reasons). The best thing to do would be to push this from a cloned repo branch so the checks can all run green, and then can just get re-approvals from those who have reviewed it (as we've turned off force-merges even for admins too 😆 )


Default sample rates for USB devices

When the SysAudio system driver initializes the KMixer driver for an audio device, it assigns a sample rate corresponding to the higher of 44.1 kHz and the highest rate available on the audio device.

This doesn't seem true for USB Audio devices, which default to 16-bit 44.1 kHz even if the hardware supports 24-bit 48 kHz.  Is this documented somewhere else?

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

ID: a7582a35-f0e0-d7e5-b730-5925106afe45
Version Independent ID: ee4e58e0-c9e5-265e-1c47-f064769abbbb
Content: Policy for Mixing Audio Streams and Setting the Output Sample Rate
Content Source: windows-driver-docs-pr/audio/policy-for-mixing-audio-streams-and-setting-the-output-sample-rate.md
Service: unspecified
GitHub Login: @DOMARS
Microsoft Alias: windowsdriverdev

Actually, now that I test more carefully, this is different in Windows 10 vs previous versions, but still not consistent.
If a device supports

Playback

2 ch, 16-bit

8000, 11025, 16000, 22050, 32000, 44100, 48000

Recording

1 ch, 16-bit

8000, 11025, 16000, 22050, 32000, 44100, 48000

Then

Windows 7 and 8.1 choose 44100 for both input and output
Windows 10 chooses 44100 for input and 48000 for output

If a device supports

Playback

2 ch, 16-bit

32000, 44100, 48000

2 ch, 24-bit

44100, 48000

Recording

2 ch, 24-bit

44100, 48000

Then

Windows 7 and 8.1 choose 48000 for input and 44100 for output
Windows 10 chooses 48000 for both input and output

And a device that supports 96 kHz still defaults to 44.1 or 48 kHz.

Related, but maybe for a separate Issue:

If it supports 1 channel in, 16 | 24-bit, 32 | 44.1 | 48 kHz, Windows 7 and 8.1 will not show the 24-bit options at all.
If it supports 1 channel in, 24-bit, 32 | 44.1 | 48 kHz, Windows 7 and 8.1 will only show the 48 kHz option and not allow anything else to be selected.
No Windows version ever displays 24-bit 32 kHz as an option even if it's supported (which is reasonable, but I can't find any documentation of it)

I've never found any documentation for how the different versions handle these things.  It's difficult to know if Windows just doesn't support something, or if there's a bug in my descriptors.

I’m checking with the dev team to see if it is possible to provide this information. Thanks for your interest in improving these pages.

@endolith - Sorry for the long delay. The audio team is interested in learning more about the sample rate testing that you did in the entry above labeled "Related, but maybe for a separate Issue:".  Could you provide a Windows build version and the audio devices that are used in each case?

@DOMARS I develop USB audio devices at work, and tried altering the USB descriptors to those different configurations to see what Windows would do with them.  I can get the Windows build numbers in a few days.
(Ideally, there would be a way to prevent Windows from requesting different sample rates for input and output, but it seems Windows 10 does it by default now.  MacOS never requests different sample rates, for comparison.)

Windows 7 Professional

Version 6.1 (Build 7601: Service Pack 1)

Windows 10

Version 1803 (OS Build 17134.228)

@endolith - Thanks for the build numbers. The dev team is looking at this issue and was wondering if the hardware that you develop is publically available? They may be able to replicate with out the specific hardware, but any addtional information that you can publically share would be helpful, if that is possible.

@endolith - I followed up in email.

@endolith - As the dev team is following up on this and has an internal tracking item, closing this issue.


Add support for VK_EXT_graphics_pipeline_library

From user request:

I guess the first question is what state dependencies there are for doing the SPIR-V -> MSL conversion and whether VK_EXT_graphics_pipeline_library would give you everything you need.  I guess on macOS to generate the AIR you still need to do this offline or it is done at PSO build time?  So I guess this would only save the SPIR-V -> MSL conversion step but still that would be a pretty big win.  Ideally we’d get all the way to AIR but AFAIK there is still not an API interface to do that on Metal and has to be done offline?

I've done an initial review of the feasibility of implementing VK_EXT_graphics_pipeline_library in MoltenVK's use of SPIRV-Cross and Metal.

This will require large amount of refactoring of MVKGraphicsPipeline. This will be a significant amount of work, and since MVKGraphicsPipeline is complicated, there is a significant potential for introducing subtle regression errors.
Each rasterizing Metal graphics pipeline needs both pre-rasterization and fragment shaders. Because of this, final Metal pipelines will always need to be compiled when linked, and so graphicsPipelineLibraryFastLinking will return false.

One of the primary goals of VK_EXT_graphics_pipeline_library will be to convert and compile pre-rasterization shaders and fragment shaders independently of each other, and only once, without reference to vertex input state, and then link them together into various runnable Metal pipelines without reconverting and recompiling the shaders. Currently, the conversion of SPIR-V shaders to compiled Metal shaders are tied to other pipeline library definitions as follows:

For pre-rasterization shaders, Metal requires vertex buffer values to be declared with correct sign and vector size. We use vertex attributes from the vertex input stage to tell the shader the format to indicate both of these. We could instead check these during final Metal pipeline linking, and trigger an automatic shader reconversion and recompile if there is a mismatch. These additional compiled Metal shaders could be cached in the pipeline library for future use.

For fragment shaders, we take inputs from the outputs of the pre-rasterization shaders to match inter-stage output/input locations. We could attempt to compile the fragment shader blindly at first, check for matching locations during final Metal pipeline linking, and if they don't match, reconvert and recompile the fragment shader. These additional compiled Metal shaders could be cached in the pipeline library for future use.

Except for constant specialization, there is a 1:1 correspondence requirement between converting SPIR-V to MSL and the final Metal compiled shader. This has two implications:

The above design would result in the pipeline libraries holding final compiled Metal shaders, meaning clean pipeline linking would not require further Metal shader compiling (but would require Metal pipeline compiling as mentioned above).
Inline forced recompiles during final pipeline linking will also require reconverting SPIR-V to MSL, in addition to recompiling the Metal shader.

@danginsburg @cdavis5e  I would appreciate your commentary and discussion.

This will require large amount of refactoring of MVKGraphicsPipeline. This will be a significant amount of work, and since MVKGraphicsPipeline is complicated, there is a significant potential for introducing subtle regression errors.

Agreed. I really hate touching that code anyway, so we need to get this out of the way. I guess I'm one to talk, since most of that is my fault to begin with ;).

Each rasterizing Metal graphics pipeline needs both pre-rasterization and fragment shaders. Because of this, final Metal pipelines will always need to be compiled when linked, and so graphicsPipelineLibraryFastLinking will return false.

Or, we could compile the shaders into dylibs; then we can support fast linking. DXVK is a heavy user of fast linking, so this is important to support.

In order for the implementation to be worthwhile, we'd need to be able to minimize the cases where you have to regenerate the MSL for the pre-rasterization and fragment shaders at link time.

For pre-rasterization shaders, Metal requires vertex buffer values to be declared with correct sign and vector size. We use vertex attributes from the vertex input stage to tell the shader the format to indicate both of these. We could instead check these during final Metal pipeline linking, and trigger an automatic shader reconversion and recompile if there is a mismatch. These additional compiled Metal shaders could be cached in the pipeline library for future use.

Can you be specific about exactly what needs to be known for MSL conversion?  The sign and vector size is generally known from the high level language so I wonder if we could extend VK_EXT_graphics_pipeline_library such that pre-rasterization shaders included just that information.  For example, in HLSL we get a declaration of float/2/3/4, int/2/3/4 or uint/2/3/4.  If that was all that was needed I think we actually could actually know that at pre-rasterization time (as opposed to for example format which we do not know).

For fragment shaders, we take inputs from the outputs of the pre-rasterization shaders to match inter-stage output/input locations. We could attempt to compile the fragment shader blindly at first, check for matching locations during final Metal pipeline linking, and if they don't match, reconvert and recompile the fragment shader. These additional compiled Metal shaders could be cached in the pipeline library for future use.

I am curious on more specifics here too.  In order to use GPL you have to have matching input/outputs in your VS/FS (i.e. it's like separate shader object in OpenGL).  So what exactly do you need to know here?  I wonder again if this is something that could be passed as additional metadata or inferred from the SPIR-V.

@cdavis5e

Or, we could compile the shaders into dylibs; then we can support fast linking. DXVK is a heavy user of fast linking, so this is important to support.

That might be an option. Metal dylibs can't be used for building an executable MTLFunction, and just define linkable functions that can be called from actual executable functions. One option might be to create non-entry-point functions that have the same call signature as the Metal entry-point functions (minus argument attributes I expect), and then create identical entry-point functions (with argument attributes) during pipeline building stage, that will simply forward the call to these implementation functions. It remains to be seen what compiling that final entry point function will cost in terms of time. Might be fast.
Another option might be to use pipeline binary archives, and create binary archives of partial pipelines that can be used to create a complete pipeline. One gotcha here is that a Metal pipeline can't have only a fragment shader, and we might not be able to build a binary archive from a Metal pipeline descriptor that only contains a fragment shader. We might have to stub in a dummy vertex function that outputs dummy stage inputs used by the fragment shader.
Thoughts?
Once we come up with a couple of reasonable options, I'm going to see if I can bounce these options off the Apple engineers.

@danginsburg

Can you be specific about exactly what needs to be known for MSL conversion?

Here's the area in code that covers this. It tells the shader code if the vertex attribute is unsigned, so the shader can convert it to signed if that's what the shader expect. I guess Vulkan permits this kind of mismatch, but Metal does not. This will only affect apps that have been imprecise in the VA vs shader definitions. And perhaps we could investigate flipping this around, and changing the vertex attribute definition, after shader conversion, based on reflecting from the shader conversion.
https://github.com/KhronosGroup/MoltenVK/blob/77b3cc03f41d1f4bcf9e7de0a8dc0a26315be3e9/MoltenVK/MoltenVK/GPUObjects/MVKPipeline.mm#L1759-L1761

I am curious on more specifics here too. In order to use GPL you have to have matching input/outputs in your VS/FS.

(BTW...I'm not familiar with the acronym GPL. Can you give me some context?)
Here's the area in code that covers this. After having another look at this, I may have misspoke about the locations. It's not about tracking the location, but about matching input/output formats. Again, this is probably covering edge cases in SPIR-V shader combos that aren't playing nice. So it might not be a significant issue, and we can explore alternatives.
https://github.com/KhronosGroup/MoltenVK/blob/77b3cc03f41d1f4bcf9e7de0a8dc0a26315be3e9/MoltenVK/MoltenVK/GPUObjects/MVKPipeline.mm#L1841-L1842

I guess Vulkan permits this kind of mismatch, but Metal does not. This will only affect apps that have been imprecise in the VA vs shader definitions. And perhaps we could investigate flipping this around, and changing the vertex attribute definition, after shader conversion, based on reflecting from the shader conversion.

OK, so given it's just a corner case when signedness mismatches it seems like most of the time we would be able to hit the fast path of converting to MSL ahead of time and only have to re-generate it at draw time in rare cases.  I could imagine also even patching the MSL in this case rather than doing a full regeneration if making this case fast was important.

(BTW...I'm not familiar with the acronym GPL. Can you give me some context?)

Sorry, I was using that as shorthand for Graphics Pipeline Libraries. I probably shouldn't since it would easily be confused with the other GPL :)

Here's the area in code that covers this. After having another look at this, I may have misspoke about the locations. It's not about tracking the location, but about matching input/output formats.

Yeah, formats and locations will always have to match for the shaders we use with VK_EXT_graphics_pipeline_library so this shouldn't be an issue for us.  I'm not sure precisely what case you are handling there, I thought interface matching rules requires the same OpType across stages.


Fix markdown

Fixes #2199

@Potapy4 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @Potapy4
Thanks for fixing this. Unfortunately, I've also just fixed it in response to a user issue. Your PR now creates a merge conflict with mine. Therefore, I'll close this PR. Thanks anyway!


feat: support for uploading folders in this current example

What type of PR is this?
/kind feature

What this PR does / why we need it
support for uploading folders in this current example
Which issue(s) this PR fixes

Fixes #376
Special notes for your reviewer

https://github.com/kubeagi/arcadia/pull/410/files#diff-584560258ba40e19973b4a2ce0006d0be82697674e47353450eaaaa5ce4b9868L327
if resp.StatusCode/100 != 2 {
	klog.Errorf("[do Error] expect 200 get %d", resp.StatusCode)
	return fmt.Errorf("not 200")
}

https://github.com/kubeagi/arcadia/pull/410/files#diff-584560258ba40e19973b4a2ce0006d0be82697674e47353450eaaaa5ce4b9868L327
if resp.StatusCode/100 != 2 {
	klog.Errorf("[do Error] expect 200 get %d", resp.StatusCode)
	return fmt.Errorf("not 200")
}

done


Deletion of a Base Image gives rise to error

Once an Image Base has been created, it cannot be deleted directly from the Edgehog portal using the delete button, and the error that results is shown in the image below.

Can you post the backend logs after the DELETE? I'm suspecting this is related to #586

This is the log from Edgehog Backend pod:
level=info ts=2024-09-04T10:43:11.441+00:00 msg="POST /tenants/edgehogtenant/api" module=Phoenix.Logger function=phoenix_endpoint_start/4 request_id=fd4b4004f6eb1352a4d02f9b3b0433dc
level=error ts=2024-09-04T10:43:11.455+00:00 msg="d7b0b2a4-75fe-48ad-a894-1ca72ae19039: Exception raised while resolving query.\n\n** (Ash.Error.Unknown) Unknown Error\n\n* %Postgrex.Error{message: nil, postgres: %{code: :foreign_key_violation, line: \"2621\", message: \"update or delete on table \\\"base_images\\\" violates foreign key constraint \\\"update_campaigns_base_image_id_fkey\\\" on table \\\"update_campaigns\\\"\", table: \"update_campaigns\", file: \"ri_triggers.c\", unknown: \"ERROR\", constraint: \"update_campaigns_base_image_id_fkey\", severity: \"ERROR\", detail: \"Key (id, tenant_id)=(13, 1) is still referenced from table \\\"update_campaigns\\\".\", schema: \"public\", pg_code: \"23503\", routine: \"ri_ReportViolation\"}, connection_id: 3727, query: nil}\n  (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1\n  (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:952: Ecto.Adapters.SQL.execute/6\n  (ash_postgres 2.1.1) lib/data_layer.ex:2781: AshPostgres.DataLayer.destroy/2\n  (ash 3.1.1) lib/ash/actions/destroy/destroy.ex:196: anonymous fn/3 in Ash.Actions.Destroy.commit/3\n  (ash 3.1.1) lib/ash/changeset/changeset.ex:3421: Ash.Changeset.run_around_actions/2\n  (ash 3.1.1) lib/ash/changeset/changeset.ex:2962: anonymous fn/3 in Ash.Changeset.with_hooks/3\n  (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1358: anonymous fn/3 in Ecto.Adapters.SQL.checkout_or_transaction/4\n  (db_connection 2.7.0) lib/db_connection.ex:1756: DBConnection.run_transaction/4\n\n    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1\n    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:952: Ecto.Adapters.SQL.execute/6\n    (ash_postgres 2.1.1) lib/data_layer.ex:2781: AshPostgres.DataLayer.destroy/2\n    (ash 3.1.1) lib/ash/actions/destroy/destroy.ex:196: anonymous fn/3 in Ash.Actions.Destroy.commit/3\n    (ash 3.1.1) lib/ash/changeset/changeset.ex:3421: Ash.Changeset.run_around_actions/2\n    (ash 3.1.1) lib/ash/changeset/changeset.ex:2962: anonymous fn/3 in Ash.Changeset.with_hooks/3\n    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1358: anonymous fn/3 in Ecto.Adapters.SQL.checkout_or_transaction/4\n    (db_connection 2.7.0) lib/db_connection.ex:1756: DBConnection.run_transaction/4\n\n" module=AshGraphql.Graphql.Resolver function=log_exception/2 request_id=fd4b4004f6eb1352a4d02f9b3b0433dc
level=info ts=2024-09-04T10:43:11.455+00:00 msg="Sent 200 in 13ms" module=Phoenix.Logger function=phoenix_endpoint_stop/4 request_id=fd4b4004f6eb1352a4d02f9b3b0433dc

@lorenzopagliai the issue here was that Edgehog is not allowing a Base Image to be deleted since it's used in an Update Campaign. The problem was that the error message was not very clear, this was fixed in #591 that will be contained in the upcoming 0.9.0-rc.2 release

@rbino so once an Update Campaign is created, the corresponding Update Channel and Base Image Collection can no longer be deleted, am I wrong? Do you plan, at least in the long term, to provide the possibility to delete these objects in this scenario as well? We strongly believe that this could be a very convenient feature.
Also, a simple note on the error message, which we actually see changed in release 0.9.0-rc.2. In my opinion, it is not clear enough and should better emphasise what you have explained within this issue.


Replace Redis with Valkey (or other alternatives)

Due to recent license changes, it may hinder adoption of loco, that it pulls in Redis in its SaaS template, maybe a change to Valkey could be useful?
See https://www.theregister.com/2024/04/03/open_source_redis_alternative/

I believe most of this would be docs changes, right?

I created a pull request if this is the direction that the project wants to take, the pull request.


vm.writeJson should also be able to add new keys

Component
Forge
Describe the feature you would like
Currently, vm.writeJson is only able to update existing keys which makes it really cumbersome to use when deploying new contracts for the first time and printing them to a file. Instead, it should be able to add new key & value pairs with it, too.
It should also be possible to add nested keys where the parent(s) aren't existing yet as well.
Or at least, the docs should be updated with an easy example on how to add a new (nested) key to an existing JSON file.
From the docs:

This is useful to replace some values in a JSON file without having to first parse and then reserialize it. Note that the JSON path must indicate an existing key, so it’s not possible to add new keys this way.

Additional context
No response

Would be dope to get this implemented. Is there any blocker I'm not aware of? Or why was it implemented this way in the first place? :)
cc @DaniPopes

It looks like foundry uses jsonpath_lib::replace_with to implement this:
https://github.com/foundry-rs/foundry/blob/e01038f35750b4a41b1eda5a4ea3da976027eee2/crates/cheatcodes/src/json.rs#L276-L279
And the jsonpath library currently does not provide a way to insert a new key.


Warn for EmbulkEmbed#destroy

After #1075, warning for EmbulkEmbed#destroy as well. The method is effective only for  @PreDestroy methods, but as mentioned in #1075, we don't observe actual usages of @PreDestroy around Embulk.
Can you have a look? @sakama @kamatama41

Thanks!


Not a issue, a question : Parallax

I think that i know the answer but sometimes i'm wrong...
I'm asking if it's possible, thanks to scrollreveal to create some parallax effect on elements ?
This will introduce dynamic arguments and dynamic settings on elements.. ?
Thanks a lot

Hi, we launched AniJS Studio on KickStarter, that allow to designers and programmers add animations and interactions for Web pages in an easy and intuitive way. Please, take a look at the project and if you find it interesting or simply want to help us, you can make a small donation. I would be grateful, Greetings Dariel

@darielnoel perhaps this issue can now be closed?


Error and warning: "Cannot update during an existing state transition an error", using react-native-router-flux and redux-form Field

bug
using react-native-router-flux with <Field /> from redux-form, I run into warnings and an error.
versions
"react": "16.0.0-alpha.12",
"react-native": "0.46.4",
"react-native-router-flux": "^4.0.0-beta.16",
"react-redux": "^5.0.5",
"redux": "^3.7.2",
"redux-form": "^7.0.1",

expected behavior
No warnings and no error
actual behavior
errors

a warning:

Warning: Cannot update during an existing state transition (such as within renderor another component's constructor). Render methods should be a pure function of props and state; constructor side-effects are an anti-pattern, but can be moved tocomponentWillMount`

an error:

Uncaught RangeError: Maximum call stack size exceeded

observations

The problem came after passing mapStateToProps to ConnectedRouter:

const ConnectedRouter = connect(mapStateToProps, null, mergeProps)(Router);

in #2063

I just did a little digging. Would you mind explaining why does the component need to be stateless?, I suspect that the <Field /> component is not stateless and so, not compatible with the react-native-router-flux render.
@necsoft resolved the problem switching from
class App extends Component {

to
const App = () => {...}

in react-router/issues/4713

updating could be solution, or was a solution at this time and with react-router.
step to reproduce
<ConnectedRouter />
  <Scene contentComponent={PageHome}/>
    <MyReduxForm />
      <Field />

<ConnectedRouter />

const ConnectedRouter = connect(mapStateToProps, null, mergeProps)(Router);

<Scene />

<Scene
  key="pagehome"
  component={PageHome}
  title="Home"
/>

<Page />

const PageHome = ({ onSubmit }) => {
  return (
    <View>
      <MyReduxForm onSubmit={onSubmit} />
    </View>
  );
};

const mapStateToProps = (dispatch) => {
  return {};
};

const mapDispatchToProps = (dispatch) => {
  return {
    onSubmit: () => console.log('submit')),
  };
};

export default connect(mapStateToProps, mapDispatchToProps)(PageAccount);

<Form />

import { Field, reduxForm } from 'redux-form';

let MyReduxForm ({ handleSubmit, onSubmit }) =>
<View>
  <Text style={styles.label}>{I18n.t('strings.formAccount.fields.email.label')}</Text>
  <Field
    name="email"
    type="text"
  />
</View>

MyReduxForm = reduxForm({
  form: 'myReduxForm',
  validate,
})(MyReduxForm);

FormAccount = connect()(MyReduxForm);

I don't understand - why MyReduxForm is children of Scene ?

@aksonov the schema is very trivial. In fact MyReduxForm  is a children of the Scene component's PageHome

@aksonov did you ever used/encountered a real working exemple with redux-form?

No, I don't have any. Please give me link to repo so I can reproduce that issue. Please also check pure react-navigation, maybe the issue is from there:
https://github.com/react-community/react-navigation/issues/1589

@aksonov I'll do my best to provide one before tomorrow

Closed due inactivity

I am having the same problem. As suggested here (https://github.com/aksonov/react-native-router-flux/issues/2063) rewriting it as stateless component is no option for me because I pass props down from another component.


Update 'Wargaming.GameCenter' to <IP_ADDRESS>34

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

URL: https://wds.wargaming.net/wgc/releases_tTrHgLCKHBRiaL/wgc_<IP_ADDRESS>34_eu/world_of_tanks_install_eu.exe
Status Code: 200
(Automated message - build 857)


Feature Request: Replace debug.openExplorerOnEnd with debug.openViewOnEnd

It would be nice if we could further customize which view to open on debug session end. Right now there is only one option – debug.openExplorerOnEnd. This could be renamed to debug.openViewOnEnd, with options like neverOpen, Explorer and perhaps other built-in or extension-contributed views, but most importantly, there should be an option restoreLastActive to restore the previously open view that was active before the debugging session started. debug.openViewOnEnd is to be used in conjuction with debug.openDebug that auto-reveals the Debug view when debug session starts.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


I would like to understand the output above, I need a file like the representation prediction represented below:
81	162	81	188	door	1	1
81	67	81	100	door	1	1
15<PHONE_NUMBER>67	77<PHONE_NUMBER>67	door	1	1
19	41.5	33	41.5	door	1	1
87	41	116	41	door	1	1
97<PHONE_NUMBER>67	148<PHONE_NUMBER>67	door	1	1
47	387	115	387	door	1	1
49	104.5	75	104.5	door	1	1
52	41	71	41	door	1	1

Can you help me, please?
Thanks,
Giovanni.

@Giogi92  - can you please share how you obtained the Pytorch pretrained model?

hi, I don't remember how but some time ago I managed to download it from the Google drive link. you can download it from here:

hi, I don't remember how but some time ago I managed to download it from the Google drive link. you can download it from here: https://mega.nz/file/ux1jDD6R#IdrjIb9R1LR4PTrfn9pWVKuWIdA0wJCGW5n_-5F3H1U

Thanks a ton, very helpful!


Automatic error report

<!---   *** BEFORE SUBMITTING: PASTE CLIPBOARD HERE TO COMPLETE YOUR REPORT ***   ---!>

Closing because this is empty. Please update to our latest version (3.3.6), which has much error reporting facilities.


⚠ Bofrost.lu has degraded performance

In b53ec3a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2878 ms

Resolved: Bofrost.lu performance has improved in 2a91d19 after 10 minutes.


Subscriber is online but not receiving messages

Environment

VerneMQ Version: 1.7.1

OS: RHEL 7.6

Erlang/OTP version (if building from source): n/a

VerneMQ configuration - changes from the default: allow_anonymous = on, persistent_client_expiration = 1w, max_online_messages = 50000, listener.max_connections = 50000, listener.nr_of_acceptors = 1000, listener.tcp.default = <node_ip>:1883, listener.tcp.allowed_protocol_versions = 3,4,5,131, listener.vmq.clustering = <node_ip>:44053, listener.http.default = <node_ip>:8888, plugins.vmq_passwd = off, log.syslog = on, nodename = <node_name>, distributed_cookie = , erlang.async.threads = 128, erlang.max_ports = 1000000, erlang.process_limit = 2000000

Cluster size/standalone: 3 nodes

Expected behavior
Subscriber is getting all messages within the subscribed topic while online.
Actual behaviour
Subscriber stops receiving data within the subscribed topic while online.
Details
Subscriber is correctly getting all messages within the subscribed topic. Suddenly he stops receiving all messages, but is still online. Other clients subscribed to same topic are receiving messages correctly. When the problematic client is restarted he immediately starts receiving messages.
Unfortunately, i did not find a way how to reproduce it. It just happens time-to-time without specific (known) reason. When it happened last time, the 'vmq-admin session show' was listing this client as online and subscribed to topic. The 'vmq-admin trace client' found session for this client and was logging the ping request/response events. So it all seems healthy, just nothing happens when message is published. If i trace another client subscribed to this topic, then i see the flow logged.
Level of logging is 'info' and there was nothing related to it. I want to change it to 'debug' for future occasion.
Seems to me, i will need erlyberly to trace when it happens next time. Problem is it is a production system and erlyberly is not recommended to be used on production.
Any suggestions or ideas? Thank you very much.

You could use recon to trace (which we ship with vernemq). See http://ferd.github.io/recon/recon_trace.html.
You could also try to upgrade to 1.8.1 or 1.9.0 to see if it solves it. Without some kind of reproducing it I'm afraid there's little we can do to figure out what the issue is - so I'll close this for now, but feel free to reopen if more information becomes available.

Did you find any solution to this problem?
This is happening to me as well, for 2 to 3 hours we are getting the subscribers are getting all the messages for the topic and after that, it is not receiving any messages for the topic but still, the publisher is publishing the messages.

@vikash1508
Is it possible to pack up the client side code into a script I could test? I need something reproducable to be able to help.

:point_right: Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
:point_right: Using the binary VerneMQ packages commercially (.deb/.rpm/Docker) requires a paid subscription.

Here is my code,
Language: Python3
Packages needed: paho-mqtt==1.6.1
For subscriber:

import paho.mqtt.client as mqtt_client
import time
import json
import threading
import logging, logging.handlers, atexit, sys

filename = 'LoadTest.csv'
logLevel = logging.INFO

formatter = logging.Formatter('%(asctime)s | %(levelname)s | %(message)s')
streamhandler = logging.StreamHandler(sys.stderr)
streamhandler.setLevel(logLevel)
streamhandler.setFormatter(formatter)
memoryhandler = logging.handlers.MemoryHandler(
    capacity=1024 * 100,
    flushLevel=logging.DEBUG,
    target=streamhandler
)

filehandler = logging.FileHandler(filename)
filehandler.setLevel(logLevel)
filehandler.setFormatter(formatter)

rotationHandler = logging.handlers.RotatingFileHandler(filename,
                                                       mode='a',
                                                       maxBytes=1024 *
1024 * 50,
                                                       backupCount=10,
                                                       delay=False)
rotationHandler.setLevel(logLevel)
rotationHandler.setFormatter(formatter)

logger = logging.getLogger()
logger.setLevel(logLevel)
logger.addHandler(memoryhandler)
logger.addHandler(filehandler)
logger.addHandler(rotationHandler)
def flush():
    memoryhandler.flush()
atexit.register(flush)
logging.debug("Logger has Initialized")

mqtt_url = "<LoadBalancerURL>"
mqtt_port = 1883

topics_for_test1 = "test/topic1"

def start(username, password, url, port, client_name):
    username = username
    password = password
    url = url
    port = port
    logging.critical("started connection")
    client = mqtt_client.Client(client_id=str(client_name))
    client.on_connect = on_connect
    client.on_message = on_messages
    client.on_publish = on_publish
    client.on_log = on_log
    client.on_disconnect = on_disconnect
    client.set_clean_session = True
    try:
        something = client.connect_async(host=url, port=port,
keepalive=60, bind_address='')
        logging.info("response from connection " + str(something))
    except Exception as err:
        logging.error("error = " + str(err))
        time.sleep(5)
        start(username, password, url, port)
    client.reconnect_delay_set(1, 5)
    client.loop_start()
    while True:
        time.sleep(60)
        try:
            if not client.is_connected():
                logging.error("MQTT is disconnected. retrying for
parking - " + str(client_name))
                client.reconnect()
                logging.error("MQTT is disconnected. retry success for
parking - " + str(client_name))
        except Exception as err:
            logging.error("MQTT re-connection failed for parking - " +
str(client_name) + ". error  -" + str(err))

def on_connect(client, userdata, flags, rc):
    logging.critical("connection success full")
    client.subscribe(topic=topics_for_test1, qos=2)

def on_messages(client, obj, msg):
    logging.info("Message received")

def on_log(client, obj, level, string):
    logging.debug("log - level - " + str(level) + " - message - " + str(string))

def on_publish(client, user_data, result):
    logging.info("message published")

def on_disconnect(client, userdata, rc):
    logging.critical("disconnected. rc - " + str(rc))

start("", "", mqtt_url, mqtt_port, "Subscriber-client-1")

For Publiser:

import paho.mqtt.client as mqtt_client
import time
import json
import threading
import logging, logging.handlers, atexit, sys

filename = 'LoadTest.csv'
logLevel = logging.INFO

formatter = logging.Formatter('%(asctime)s | %(levelname)s | %(message)s')
streamhandler = logging.StreamHandler(sys.stderr)
streamhandler.setLevel(logLevel)
streamhandler.setFormatter(formatter)
memoryhandler = logging.handlers.MemoryHandler(
    capacity=1024 * 100,
    flushLevel=logging.DEBUG,
    target=streamhandler
)

filehandler = logging.FileHandler(filename)
filehandler.setLevel(logLevel)
filehandler.setFormatter(formatter)

rotationHandler = logging.handlers.RotatingFileHandler(filename,
                                                       mode='a',
                                                       maxBytes=1024 *
1024 * 50,
                                                       backupCount=10,
                                                       delay=False)
rotationHandler.setLevel(logLevel)
rotationHandler.setFormatter(formatter)

logger = logging.getLogger()
logger.setLevel(logLevel)
logger.addHandler(memoryhandler)
logger.addHandler(filehandler)
logger.addHandler(rotationHandler)
def flush():
    memoryhandler.flush()
atexit.register(flush)
logging.debug("Logger has Initialized")

mqtt_url = "afeca372c6f4149c188e01b26b6fa2c0-1222942296.ap-south-1.elb.amazonaws.com"
mqtt_port = 1883
topics_for_test1 = "test/topic1"

def start(username, password, url, port, client_name):
    username = username
    password = password
    url = url
    port = port
    logging.critical("started connection")
    client = mqtt_client.Client(client_id=str(client_name))
    # client.username_pw_set(username, password=password)
    client.on_connect = on_connect
    client.on_message = on_messages
    client.on_publish = on_publish
    client.on_log = on_log
    client.on_disconnect = on_disconnect
    client.set_clean_session = True
    try:
        something = client.connect_async(host=url, port=port,
keepalive=60, bind_address='')
        logging.info("response from connection " + str(something))
    except Exception as err:
        logging.error("error = " + str(err))
        time.sleep(5)
        start(username, password, url, port)
    client.reconnect_delay_set(1, 5)
    client.loop_start()
    while True:
        time.sleep(5)
        try:
            if not client.is_connected():
                logging.error("MQTT is disconnected. retrying for
parking - " + str(client_name))
                client.reconnect()
                logging.error("MQTT is disconnected. retry success for
parking - " + str(client_name))
        except Exception as err:
            logging.error("MQTT re-connection failed for parking - " +
str(client_name) + ". error  -" + str(err))
        send(client, "test-message-1", topics_for_test1, client_name)

def on_connect(client, userdata, flags, rc):
    logging.critical("connection success full")
    client.subscribe(topic=topics_for_test1, qos=2)

def on_messages(client, obj, msg):
    logging.info("Message received")

def on_log(client, obj, level, string):
    logging.debug("log - level - " + str(level) + " - message - " + str(string))

def on_publish(client, user_data, result):
    logging.info("message published")

def on_disconnect(client, userdata, rc):
    logging.critical("disconnected. rc - " + str(rc))

def send(client, data, topic, user_name):
    logging.info("publishing data to topic")
    try:
        client.publish(topic, payload=json.dumps(data), qos=2)
    except Exception as err:
        logging.error("failed to publish message for user - " +
str(user_name) + ". error - " + str(err))

if __name__ == "__main__":
    thread = threading.Thread(target=start, args=("", "", mqtt_url,
mqtt_port, "Publisher-client-1"))
    thread.start()

For the Kubernetes cluster, I'm using AWS EKS and .yaml file for creating
the cluster is my question itself but passing here for reference:
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: vernemq
spec:
replicas: 1
selector:
matchLabels:
app: vernemq
serviceName: vernemq
template:
metadata:
labels:
app: vernemq
spec:
serviceAccountName: vernemq
terminationGracePeriodSeconds: 600
containers:
- name: vernemq
image: vernemq/vernemq:latest
# image: index.docker.io/chouhan/mqtt-docker:latest
# image: nmatsui/docker-vernemq:debug_insecure_kubernetes_restapi
imagePullPolicy: Always
lifecycle:
preStop:
exec:
command:
- /bin/bash
- -c
- /usr/sbin/vmq-admin cluster leave
<EMAIL_ADDRESS>; sleep 60 ; /usr/sbin/vmq-admin cluster leave
<EMAIL_ADDRESS>-k; sleep 60;
ports:
- containerPort: 1883
name: mqtt
hostPort: 1883
- containerPort: 8883
- containerPort: 4369
name: epmd
- containerPort: 44053
name: vmq
- containerPort: 8888
name: health
- containerPort: 9100
- containerPort: 9101
- containerPort: 9102
- containerPort: 9103
- containerPort: 9104
- containerPort: 9105
- containerPort: 9106
- containerPort: 9107
- containerPort: 9108
- containerPort: 9109
- containerPort: 8888
resources:
limits:
cpu: "1"
memory: 1Gi
requests:
cpu: "0.5"
memory: 0.5Gi
env:
- name: DOCKER_VERNEMQ_ACCEPT_EULA
value: "yes"
- name: MY_POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: DOCKER_VERNEMQ_DISCOVERY_KUBERNETES
value: "1"
- name: DOCKER_VERNEMQ_KUBERNETES_APP_LABEL
value: "vernemq"
- name: DOCKER_VERNEMQ_KUBERNETES_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: DOCKER_VERNEMQ_ERLANG__DISTRIBUTION__PORT_RANGE__MINIMUM
value: "9100"
- name: DOCKER_VERNEMQ_ERLANG__DISTRIBUTION__PORT_RANGE__MAXIMUM
value: "9109"
- name: DOCKER_VERNEMQ_ALLOW_ANONYMOUS
value: "on"
- name: DOCKER_VERNEMQ_LISTENER__TCP__DEFAULT
value: "<IP_ADDRESS>:1883"
- name: DOCKER_VERNEMQ_VMQ_WEBHOOKS__POOL_timeout
value: "6000"
- name: DOCKER_VERNEMQ_LISTENER__HTTP__DEFAULT
value: "<IP_ADDRESS>:8888"
- name: DOCKER_VERNEMQ_LISTENER__MAX_CONNECTIONS
value: "infinity"
- name: DOCKER_VERNEMQ_LISTENER__NR_OF_ACCEPTORS
value: "10000"
- name: DOCKER_VERNEMQ_MAX_INFLIGHT_MESSAGES
value: "0"
- name: DOCKER_VERNEMQ_ALLOW_MULTIPLE_SESSIONS
value: "on"
- name: DOCKER_VERNEMQ_ALLOW_REGISTER_DURING_NETSPLIT
value: "on"
- name: ALLOW_PUBLISH_DURING_NETSPLIT
value: "on"
- name: ALLOW_SUBSCRIBE_DURING_NETSPLIT
value: "on"
- name: ALLOW_UNSUBSCRIBE_DURING_NETSPLIT
value: "on"
---
apiVersion: v1
kind: Service
metadata:
name: vernemq
labels:
app: vernemq
spec:
clusterIP: None
selector:
app: vernemq
ports:
- port: 4369
name: empd
- port: 44053
name: vmq
---
apiVersion: v1
kind: Service
metadata:
name: mqtt
labels:
app: mqtt
spec:
type: LoadBalancer
selector:
app: vernemq
ports:
- port: 1883
name: mqtt
targetPort: 1883
---
apiVersion: v1
kind: Service
metadata:
name: health
labels:
app: health
spec:
type: LoadBalancer
selector:
app: vernemq
ports:
- port: 8888
name: health
targetPort: 8888
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: vernemq
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: endpoint-reader
rules:
- apiGroups: ["", "extensions", "apps"]
resources: ["endpoints", "deployments", "replicasets", "pods"]
verbs: ["get", "list"]
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: endpoint-reader
subjects:
- kind: ServiceAccount
name: vernemq
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: endpoint-reader
---
apiVersion: autoscaling/v1
kind: HorizontalPodAutoscaler
metadata:
name: vernemq
spec:
scaleTargetRef:
apiVersion: apps/v1
kind: StatefulSet
name: vernemq
minReplicas: 1
maxReplicas: 4
targetCPUUtilizationPercentage: 80

On Fri, Mar 25, 2022 at 12:31 PM ioolkos @.***> wrote:

@vikash1508 https://github.com/vikash1508
Is it possible to pack up the client side code into a script I could test?
I need something reproducable to be able to help.
👉 Thank you for supporting VerneMQ: https://github.com/sponsors/vernemq
👉 Using the binary VerneMQ packages commercially (.deb/.rpm/Docker)
requires a paid subscription.
—
Reply to this email directly, view it on GitHub
https://github.com/vernemq/vernemq/issues/1285#issuecomment-1078717006,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU5C4GY2BXMFW3LK4RJP5XDVBVQFHANCNFSM4IKH7YTQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


[WC-2165]: fix excessive scrollbars of scroll container

test still failing, seems like need to update screenshots.


Issue with Tasks on High Sierra

Hi,
I am facing an issue when clicking the "taks" button in Springroll studio.

Note: I can run grunt directly on the project's root and it compiles the app properly. I can then launch it through the preview command from spring roll studio.
System:
mac os 10.13.3
Let me know if I can provide any other info.

Hi @LaurieTrichet can you tell me which version of the global grunt-cli, local grunt, and lastly node and npm  that you are using?

Hi,
node version is v9.11.1
npm version is 5.6.0
grunt global version 1.0.2
the local grunt was 0.0.1. So I have updated the local grunt to the latest, and now it is working.
So not sure what happened at installation time, but my local grunt was behind.
Thank you.


location is updated when no intenet connection?

i wanna to know if location updated when no internet found

Yes, the location updates don't require an internet connection, they are based on your gps/location


[HIPIFY] Unable to convert cudnnSetFilter4dDescriptor

Hello,
Hipify-clang is unable to convert convolutional_layer.c file(https://github.com/pjreddie/darknet/blob/61c9d02ec461e30d55762ec7669d6a1d3c356fb2/src/convolutional_layer.c#L125)
Could you please help?
Error message:
tmp/convolutional_layer.c-276d1c.hip:132:5: warning: CUDA identifier is unsupported in HIP.
cudnnSetFilter4dDescriptor(l->dweightDesc, CUDNN_DATA_FLOAT, CUDNN_TENSOR_NCHW, l->n, l->c/l->groups, l->size, l->size);
^
/tmp/convolutional_layer.c-276d1c.hip:133:5: warning: CUDA identifier is unsupported in HIP.
cudnnSetFilter4dDescriptor(l->weightDesc, CUDNN_DATA_FLOAT, CUDNN_TENSOR_NCHW, l->n, l->c/l->groups, l->size, l->size);
^
2 warnings generated when compiling for host.
Thank you,
Rohan

cudnnSetFilter4dDescriptor and cudnnGetFilter4dDescriptor methods are not yet supported by hipDNN.
The above are the warnings, not errors; thus your CUDA source should be hipified despite these warnings; cudnnSetFilter4dDescriptor will stay nonhipified in the output HIP file.
Please refer Supported CUDA APIs to check whether particular CUDA method or data type is supported by HIP or not.
I may advise you 2 things here:

Try to rewrite the source or an output code based on (cu)hipdnnSetFilterNdDescriptor.
Open a ticket in hipDNN for supporting cudnnSetFilter4dDescriptor in  it.


feat: add feed

:tada: This PR is included in version 0.4.0 :tada:
The release is available on:

GitHub release
v0.4.0

Your semantic-release bot :package::rocket:


⚠ Bofrost.at has degraded performance

In 17ee783, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1751 ms

Resolved: Bofrost.at performance has improved in 5eba21a after 6 minutes.


Example for flow in docs is incorrect?

For the FieldProps example, it looks like the flow type FieldProps is trying to demonstrate typing the props that get passed into the wrapped component, and not the Field itself. I couldn't find a flow type that exposed the FieldPassedProps (input & meta).
Currently looking into the code it looks like FieldProps is:
export type Props = {
  names: string[],
  component: Function | ReactClass<*>,
  format?: (value: any, name: string) => ?any,
  parse?: (value: any, name: string) => ?any,
  props?: Object,
  withRef?: boolean
}

when in the example its looking for something like...
type FieldPassedProps = {
   input: ...
   meta: ...
}

Hey @juhaelee ,
I have the same problem. Have you found a way to sort this out?

i believe the FieldPassedProps needs to be exported from the library. Currently I just typed them myself

Looks like this was mentioned here: https://github.com/erikras/redux-form/issues/3214

Published fix in v7.0.2.


API call to Github fails with Invalid request.  Only 65535 characters are allowed

Describe a bug
Using the action, seeing failures in Github actions logs.
Expected behavior
API calls to Github should succeed and action should succesfully execute.
Details

Action version: v2 (SHA:6f1418344ffb25717bf09a95cff68f9fa4c3bdad)
OS, where your action is running (windows, linux): linux

action.yml file

      - name: 🐛 Run tests
        uses: actions/ArtiomTr_jest-coverage-report-action@v2
        with:
          test-script: npm run test:ci

</details>

Screenshots
<!-- If you encounter an incorrect coverage comment display, replace this comment with screenshot -->

<!-- If your action unexpectedly fails, please replace this comment with a screenshot of your console  -->

Additional context
Begin failed tests' annotations publication...
Failed tests' annotations publication failed
Error: HttpError: Invalid request.

Only 65535 characters are allowed; 76633 were supplied.
HttpError: Invalid request.

Only 65535 characters are allowed; 76633 were supplied.
    at /runner/_work/_actions/actions/ArtiomTr_jest-coverage-report-action/v2/dist/index.js:2:329684
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async /runner/_work/_actions/actions/ArtiomTr_jest-coverage-report-action/v2/dist/index.js:52:1897
    at async Ge (/runner/_work/_actions/actions/ArtiomTr_jest-coverage-report-action/v2/dist/index.js:51:156)
    at async Cw (/runner/_work/_actions/actions/ArtiomTr_jest-coverage-report-action/v2/dist/index.js:52:1762)
Failed tests' annotations publication ended
Begin coverage annotations publication...
Coverage annotations publication ended
Error: Jest coverage report action failed
Error: Process completed with exit code 1.

Hello @MisterJimson :wave:,
That is GitHub's limitation - comments could have only 65535 characters. But I think the action could notify the user if the too long report was generated, and some detailed information was hidden.

Maybe a way to have the report success but trimmed would be nice

Hello!
I'm encountering a similar problem with the character limit, but it looks like mine is happening at a different stage.
Test results written to: report.json
Done in 299.70s.
Running tests ended
Begin collecting coverage...
Collecting coverage ended
Begin parsing coverage...
Parsing coverage ended
Base coverage collection ended
Begin generating report...
Generating report ended
Begin report publish...
Report publish failed
Error: HttpError: Validation Failed: {"resource":"IssueComment","code":"custom","field":"body","message":"body is too long (maximum is 65536 characters)"}
Report publish ended
Begin failed tests' annotations publication...
Failed tests' annotations publication skipped
Failed tests' annotations publication ended
Begin coverage annotations publication...
Coverage annotations publication skipped
Coverage annotations publication ended
Error: Jest coverage report action failed
Error: Process completed with exit code 1.

I think I can code a simple fix that would check if the generated report length (with the title/footer template) is longer than the allowed limit, truncate it with some safe margin (say 1k characters) and prepend a warning message saying the report body was too long.
Does this solution make sense?

Hello @maciejtutak :wave:,
I think report truncation will break the overall report structure and will look bad. In my opinion, if the report is too long, the details (2 spoilers - one with newly covered files and another with files with decreased coverage) should be omitted. Like this:

This would look nice. However, I think it would be better if the report could contain at least some coverage details, like this:

I'd love to see your fix - this repository is always open for new contributors. You can pick one of these solutions (the first is a bit easier to code), or propose your own, as long as it follows the structure:

Title.
Errors (if there are any)
Overall coverage information (table).
Coverage details (not very important information, could be omitted)
Test execution result
Failed test output (also quite not important information, could be omitted).
Tool name ("Report generated by ..." string)


helloworld-knative to 0.1.22

Promote helloworld-knative to version 0.1.22

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


xRDCertificateConfiguration:The term ''Get-RDServer'' is not recognized

ISSUE DESCRIPTION
I'm using Ansible to run the xRDCertificateConfiguration resource and only when applying a certificate to the RDWebaccess role I get the following error message.
Failed to invoke DSC Set method: Failed to apply certificate from path ''C:\windows\temp\rds-cert.pfx'' to role ''RDWebAccess'' on connection broker ''hostnamel''. Error: ''The term ''Get-RDServer'' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.'''
Suggested solution to the issue
I figured this was an issue due to the box not being ready so I added a delay of 60 seconds and 10 retires and unfortunately the result is the same.
The DSC configuration that is used to reproduce the issue (as detailed as possible)

name: Configure RDS Certificate
win_dsc:
Resource_name: xRDCertificateConfiguration
Role: "{{ item }}"
ConnectionBroker: "{{ hostname }}.{{ domain }}"
ImportPath: C:\windows\temp\rds-cert.pfx
Credential_username: Welcome1!
Credential_password: Welcome1!
PsDscRunAsCredential_username: "{{ domain_admin }}"
PsDscRunAsCredential_password: "{{ domain_admin_password }}"
with_items:

RDRedirector
RDPublishing
RDWebAccess

###Output of successfully applying a certificate to other roles
TASK [ad_rds : Configure RDS Certificate] ************************************************************************************************************************************************************************************************************************changed: [<IP_ADDRESS>] => (item=RDRedirector) => changed=true
ansible_loop_var: item
attempts: 1
item: RDRedirector
module_version: 2.0.0
reboot_required: false
changed: [<IP_ADDRESS>] => (item=RDPublishing) => changed=true
ansible_loop_var: item
attempts: 1
item: RDPublishing
module_version: 2.0.0
reboot_required: false
The operating system the target node is running
OsName               : Microsoft Windows Server 2019 Standard
OsOperatingSystemSKU : StandardServerEdition
OsArchitecture       : 64-bit
WindowsVersion       : 1809
WindowsBuildLabEx    : 17763.1.amd64fre.rs5_release.180914-1434
OsLanguage           : en-US
OsMuiLanguages       : {en-US}
Version and build of PowerShell the target node is running
Name                           Value

PSVersion                      5.1.17763.771
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.771
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
Version of the DSC module that was used
Version 2.0.0

Ok, looking at the error message you get this goes wrong at this stage:
https://github.com/dsccommunity/xRemoteDesktopSessionHost/blob/523c4356c411dfe10f9286011e5a147df90a2dc4/source/DSCResources/MSFT_xRDCertificateConfiguration/MSFT_xRDCertificateConfiguration.psm1#L92
Set-RDCertificate, in the beginning of the code, indeed calls Get-RDServer (which seems to be unavailable in your error).
The reason it's possible that command cannot be found is not entirely clear to me, it could be related to the fact that in the module where this command is defined (C:\windows\system32\WindowsPowerShell\v1.0\Modules\RemoteDesktop\Deployment.psm1) it's call Get-Server, not Get-RDServer. The RD prefix is only added as soon as the RemoteDesktop module is loaded.
Since this module loads the RemoteDesktop module explicitly, I would not expect any issues there though, but in this case it's clear there are issues.
Would you be so kind to help testing a change in the code? Maybe if we load the module in the global context, this prevents the issue. What you would need to do locally on your machine is change this line:
https://github.com/dsccommunity/xRemoteDesktopSessionHost/blob/523c4356c411dfe10f9286011e5a147df90a2dc4/source/DSCResources/MSFT_xRDCertificateConfiguration/MSFT_xRDCertificateConfiguration.psm1#L6
and make it:
Import-Module -Name RemoteDesktop -Global
Then test it with your configuration. Thanks in advance!

That worked! Thank you so much and thank you for not saying because you're using Ansible I can't help you ( =

Happy to hear that it worked, thank you for reporting back! To add to that, which tool you use, if it's Puppet, Chef, Ansible or plain DSC, that doesn't matter, in the end it's the DSC resource that needs to do the work.

@danielboth are you looking for assistance in getting this fix implemented via a PR?

I hit this problem.
PR raised.


Arkjs transactions are only working on the mainnet

Transaction->create is only working on the mainnet:
$tx = Lark::api('Transaction')->create('DKfEF2sykKCZzom3vFg1dp9D2kisB8hM2Q', 10, 'testing', 'word word word word word word word word word word word word', null);
UnexpectedValueException with message '(node:29824) UnhandledPromiseRejectionWarning: Unh                            andled promise rejection (rejection id: 1): Error: Wrong recipientId'
Darknet addresses are failing validation on arkjs https://github.com/ArkEcosystem/ark-js/blob/4f7ef0075c3d5694126ec530281e06b365bfb699/lib/transactions/transaction.js#L9
https://github.com/ArkEcosystem/ark-js/blob/95b591c4641ab12869890889c9e3cbbcbe457166/lib/transactions/crypto.js#L392
Works fine when using the mainnet.

As already mentioned feel free to send a PR for devnet support, pretty easy to do if you know how to switch the network with ark-js.


hictk balance: honor --in-memory

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 84.85%. Comparing base (87e0442) to head (a055982).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #166      +/-   ##
==========================================
+ Coverage   84.80%   84.85%   +0.05%
==========================================
  Files         117      117
  Lines       10036    10030       -6
==========================================
  Hits         8511     8511
+ Misses       1525     1519       -6

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


Create All in One App .py

Personally, I see no need for this as we are actually moving away from flask right now. Additionally having the same thing in this as is in the separated files doesnt seem to create any benefit that im aware if and makes two places to edit the same code.


Missing kernelspec on new notebooks created in VSCode

Notebooks created in vscode don't have a kernel spec until you run them, which causes issues when trying to run them with elyra

moved to https://github.com/elyra-ai/elyra/issues/1337


need private tabs

am ya

Closing, similar in scope to #1065. Let’s continue the discussion there.


flowblade-<IP_ADDRESS> built with mlt-7.20 doesn't start

FLOWBLADE MOVIE EDITOR <IP_ADDRESS>
-------------------------------
Launch script dir: /nix/store/kddzdraycracw4r0q4qva1yvhxclznq7-flowblade-<IP_ADDRESS>/flowblade
Running from filesystem...
MLT found, version: 7.20.0
numpy version: 1.25.2
Application version: 2.10.0
OS: NixOS 23.05 (Stoat)
Python 3.11.5 (main, Aug 24 2023, 12:23:19) [GCC 12.3.0]
GTK+ version: 3.24.38
...
restacking compositors!
Adding full track compositors DONE
G'MIC found
Player initialized with profile:  HD 1080p 30 fps
Selected color NOT detected
BG color detected
[mlt_producer 0x2238330] <playlist>
    Playlist can not create blank producer without profile
[mlt_producer 0x2238330] <playlist>
    Playlist can not create blank producer without profile
fish: Job 1, 'flowblade' terminated by signal SIGSEGV (Address boundary error)

flowblade-<IP_ADDRESS>, installed from unstable doesn't start. <IP_ADDRESS> from 5a86504, which ships mlt-7.16.0, runs fine.
This issue has recently been reported on arch forums and project's issues.
I'm fairly new to Nix, but my assumption is that mlt should be a runtime dependency of flowblade, since the script imports mlt7 at runtime. Does that mean flowblade should be a referrer of mlt? Because it isn't. On that note, gmic is basically a runtime dependency - mostly unusable on stable due to gmic's command rework. Wish flowblade had it's dependencies pinned, since they are quite specific for the two mentioned packages.
Edit: the mlt referrer digression turns out to be incorrect, but pinning still bothers me.
@polygon

for me older version of flowblade (2.8) are crashing too.

@yaitskov same reason?


Update repo url on aws

Description
Updates repo URL on AWS to match the playbook. We are getting 404's because the playbook is using update number instead of repo id. To avoid signing it again, I went for the small change of uploading to that URL instead.
Fixes # (issue)
Type of change
What is it?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run go fmt ./... to check that my code is properly formatted
[ ] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #452 (d7e6527) into main (7f5a20f) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main     #452   +/-   ##
=======================================
  Coverage   31.61%   31.61%
=======================================
  Files          31       31
  Lines        3169     3169
=======================================
  Hits         1002     1002
  Misses       2072     2072
  Partials       95       95

Impacted Files
Coverage Δ

pkg/services/repobuilder.go
2.97% <0.00%> (ø)

Continue to review full report at Codecov.

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


590 api docs fix

Major cleanup/refactoring:
Patients belong to a cohort namespace, with uniqueness requirement
Swagger documentation using restx at / (works with latest version of werkzeug), see it at "host":5004
Added convenience methods for working with patient and cohort nodes
Added unit tests for patient and cohort node logic (match vs. create)
Simplified API routes
Error and response messages make sense and are informative (mostly)

This is really cool and nice documentation! I'll plan to work on the graph code more next sprint also for radiology annotations. I'm wondering if there is a way to have separate documentation for put/delete/get methods?

This is really cool and nice documentation! I'll plan to work on the graph code more next sprint also for radiology annotations. I'm wondering if there is a way to have separate documentation for put/delete/get methods?


Add RQC

"All security levels of RQC were reduced to less than 128 bits of security."

https://nvlpubs.nist.gov/nistpubs/ir/2020/NIST.IR.8309.pdf
Thus, the data from the round 2 submission is inaccurate and we don't enter it. (As it has not advanced to round 3, no updated submission is to be expected.)


Update event service documentation.

Remove outdated information about the original v1.0 event hub.
Provide summary of event service.
Clarify block events versus chaincode events.

@Mergifyio backport release-2.5


API changes, Examples and Python Docker image work

Just an initial iteration on the API changes, relevant examples and python pipeline step for docker image

The conflicts are due to refactored classes for orchestration. Will solve them at the end of finishing this PR.


[Feature Request] Sorting options affect file tree

In the sidebar there is a menu with sorting options (under the cog icon). It affects only the sorting of files on list for the left / right pane. I would love to have it change the order of sorting for the file tree as well (though regardless of the chosen sorting order, the directories should be listed first, I think).

To list the directories first, you could try to add this in your preferences.
{
    "sortDirectoriesFirst": true
}

I know about that. I'm talking about a proper sorting of the file tree, no only "directories first".

What sorting options would you like there to see?

@zaggino I'd assume name/type/date like the working set items.

That should be quite easy to implement I think.

@petetnt Exactly as @zaggino said: name/type/date, but with folders first (by default or as an option), maybe sorted the same way among themselves.

P.S. when were are already at it, then to make it perfect, maybe also an option for sorting direction. (or each sorting type split into "up" and "down")  :stuck_out_tongue_winking_eye:

I guess that should be a second level menu when right clicking the tree
Sort > ...options

@zaggino -- a question not connected with the issue -- what extension gives you the "add to / remove to .gitignore" options?

@retan this one https://github.com/zaggino/brackets-git

to the cog, I believe it would pollute the ui and I prefer to keep it clean, I dont want an icon in there for a feature that I will never use

@zaggino Sorry but I don't follow you. I meant the cog that is already there, the one displaying sorting options for left/right pane.

(thank you for the extension by the way)

That already sorts working tree. How would the menu look like if you add options to sort file tree?

@zaggino Working tree? That's what you call the "left" / "right" lists?
The thing is... I don't use those lists at all. With many files opened they reduce the space for the file tree quite a bit and when I work in split view (almost all the time) and cycle through files it's hard to tell which file is actually open (you can tell of course but you need to run with your eyes all around the interface). I've got one the extensions that adds tabs to the UI (and hides those "left" / "right" lists).
But my request is not about those lists (working tree) but about the file tree - the main one with all the files.
If it is possible to add a non active items / group headers, to the cog menu, I think I should look like this:
Panel lists sorting // (or whatever you call it) gourp header
-------------------
Automatic sort
-------------------
By name ⇓
By name ⇑
By type ⇓
By type ⇑
By added ⇓
By added ⇑
-------------------
File tree sorting // group header
-------------------
Folders first
-------------------
By name ⇓
By name ⇑
By type ⇓
By type ⇑
By date ⇓
By date ⇑
I have doubts if the "Automatic sort" option (for the left / right lists) is necessary (it took me a while to understand what difference it does and I can't see why somebody would want to switch that off) but it's already there so let's leave it.
I would be preferable If you would actually grouped those two sections of the menu (in the its code) to allow extensions adding tabs to hide the group for the opened files.

That seems like a doable solution, I was just confused where you want to place those options.  Take note that when the working tree is hidden, the cog is not visible too so that'd have to be changed otherwise you won't be able to use it of course. If anyone wants to pick this up, go ahead.

@zaggino I'm glad it's clear finally. :smile:
Well.. I don't think that's an issue. Why would I want to change sorting method for the tree if it was hidden.
What do you mean by "pick this up"?

"pick this up" is a phrase for "start implementing this and opening a pull request"

@zaggino
Aaaa! Well, I hope somebody does.


BREAKING CHANGE: It's no longer allowed to omit the '-loader' suffix when using loaders

Edit - Fixed and created pull request
Original:

dotnet restore
npm install
npm install babel-core
webpack --config webpack.server.config.js gives this error
`
$ webpack --config webpack.server.config.js
Hash: 8a3e7278453b7c4c1782
Version: webpack 3.8.1
Time: 1408ms
Asset    Size  Chunks                    Chunk Names
bundle.server.js  414 kB       0  [emitted]  [big]  main
[50] ./VueApp/server.js 394 bytes {0} [built]
[51] ./VueApp/app.js 866 bytes {0} [built]
[58] ./VueApp/vuex/store.js 1.18 kB {0} [built]
[59] ./VueApp/vuex/actions.js 662 bytes {0} [built]

168 hidden modules

ERROR in ./node_modules/axios/lib/adapters/http.js
Module not found: Error: Can't resolve 'json' in 'c:\WORKFOLDER\VuejsSSRSample\VuejsSSRSample'
BREAKING CHANGE: It's no longer allowed to omit the '-loader' suffix when using loaders.
You need to specify 'json-loader' instead of 'json',
see https://webpack.js.org/guides/migrating/#automatic-loader-module-name-extension-removed
@ ./node_modules/axios/lib/adapters/http.js 12:10-41
@ ./node_modules/axios/lib/defaults.js
@ ./node_modules/axios/lib/axios.js
@ ./node_modules/axios/index.js
@ ./VueApp/vuex/actions.js
@ ./VueApp/vuex/store.js
@ ./VueApp/app.js
@ ./VueApp/server.js
`

Thank you!


Wildcard mocha dev dependency

Fixes an issue with NPM exiting with 1 when installing older mocha versions.

Coverage remained the same at 94.643% when pulling f580689ca90f6370484caa8cbb32b26967060c78 on mocha-wild into affd30e105f051f950738c973acfca3d1a4396ba on master.

Coverage remained the same at 94.643% when pulling f580689ca90f6370484caa8cbb32b26967060c78 on mocha-wild into affd30e105f051f950738c973acfca3d1a4396ba on master.


Automatic Declaration for my other teams

Context
As a teammate or a captain
I want to be able not to inform all my teams when I was already declaring  my journey in one team
In order to not repeat my declaration as "absent" for all my other teams
Expected Behavior
When I declare myself in one team, for all my other teams I want to be automatically displayed as "absent"
Acceptance Criteria
My status was automatically set as "absent" if I was already declared in a team
My status doesn't change automatically if I set a status by myself
But i also want to be able to set my status in 2 different teams
Exemple :
Team 1 : Morning = Remote
Afternoon = Absent
Team 2 : Morning = Absent
Afternoon = Remote
Technical Analysis needed.

status update, will not use Absent
Team 1 : Morning = Remote
Afternoon = occupied
Team 2 : Morning = occupied
Afternoon = Remote
Technical Analysis needed.

Tech part :
Mobile backend: retrive current user declaration, must in the API get all his other team and automaticaly update the status for him.
case : User Roger in team A, B, C
Roger create declaration for team A  full day
Option 1 :
Only create a delaration for team A, but when team B,C captain will check declaration, the request will check:
there is a declaration made for this day, but not for the current team, just set status to "occupied"
PRO :
Less declarations created, so less data used in the DB
CON:
? Will the get request heavier than Option2 ?
For log, how to handle the fact that there isn't any declaration created for team B & C
Option 2:
In front end only create declaration for teamA, but in API get all user's teams, and create declaration for the others teams with the status occupied.
PRO:
Easier as post declaration request is made and will work
Will create declaration for others teams for the logs
CON:
? Will the get request heavier than Option1 ?
Bigger data usage because more declaration created

This has changed with bastiUI desgin


feat(COMMON,LLD,LLM): Add missing attributes for Polkadot Transaction coming from Wallet API

📝 Description
Adds the missing attributes mapping for the Polkadot Transaction coming from the wallet-api, concerning changes made here: https://github.com/LedgerHQ/wallet-api/pull/271
❓ Context
We're from StakeKit and we've just released a Ledger Live app that offers users a unified non-custodial staking experience across a wide range of networks and protocols. We're opening this PR because we would like to offer users the possibility to participate in Polkadot staking via our Ledger Live app.
✅ Checklist
Pull Requests must pass the CI and be code reviewed. Set as Draft if the PR is not ready.

[x] npx changeset was attached.
[ ] Covered by automatic tests.
[x] Impact of the changes:

This PR impacts how Polkadot transactions are built coming from the Wallet API

🧐 Checklist for the PR Reviewers

[ ] The code aligns with the requirements described in the linked JIRA or GitHub issue.
[ ] The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
[ ] There are no undocumented trade-offs, technical debt, or maintainability issues.
[ ] The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
[ ] Any new dependencies have been justified and documented.
[ ] Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

Hey I created the branch yesterday just had no time push this until today, @haammar-ledger could take a look at https://github.com/LedgerHQ/ledger-live/pull/5697 instead please ?


Added-button-3031

Targets #3031

Description
Added clear button.

It provides option to clear the search result , so user can see the complete list again.
Checklist:

[x] I have performed a self-review of my own code.

@jaskaransingh304 Also add expected effort in the comment
You can take reference form this PR
https://github.com/ColoredCow/portal/pull/3104

@GauravGusain98 , Here is the screenshot.

@GauravGusain98 , I have updated the title of the PR.


Revert "Improve graph structure a little bit"

Reverts gdalle/SparseMatrixColorings.jl#114

Superseded by #107


The known issue "VR power abnormal assertion when system power on. (VCCD POUT)"

Hi @DelphineChiu,
When system DC cycle, the current will drop to 0.
It has a chance to get the negative power value (0xFF 0xFF).
Do we have a plan to filter the negative value for VR power and current like YV3?
Thanks
Young

Hi @YoungLi123
We find this issue from stress test result , and report this issue to the vendor Renesas.
Because VR would report negative current/power value during DC cycle , Renesas recommends that BIC can treat as 0 when receiving current value in -0.2~0.2 A.
Regards,
Lora.

#274 #282 fix this issue