Implemented client side re-ordering

When --correct-order flag is specified in the open-stream, the CLI correct order of packets in the bundler by a stable sort ordered by time_first_byte_received property of the telemetry.
There is no behavior change when --correct-order flag is not specified for backward compatibility.

Thinking about this algorithim, is it possible that out of order packets received near the end of a bundle will still be out of order?  (In other words, if their bundle is flushed before the earlier packets arrive.)

In other words, it seems like we want to flush packets that are older than 500ms, rather than flushing all packets every 500ms.

I am going to merge this PR and fix the issue around end of bundle case in the following PR.


Discribe conflicts between unitree-z1-docs and unitree_ros

Unitree-z1-docs states that Simulations can be run on ROS melodic or neotic versions.(https://dev-z1.unitree.com/use/build.html)
However, here states that Simulations can not be run on ROS neotic.
Is it a mistake in unitree-z1-docs or the Simulation of Z1 Robotic Arm can be run on neotic version?

Unitree-z1-docs and Unitree_ros are two different packages, responsible for different functions. Unitree_ros is mainly Ros for robot dogs, so please use it according to their respective instructions.


No dialog shown,seems invisible

Hi
I want to use this component in my app,I've done all setups,I see no error in console but dialog seems invisible to me,after I show it I can't focus something in window so there must be present.
What could cause this?
Also tried your examples , run npm install in demo folder but got errors on install:

npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>lint: tslint src/**/*.ts
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\user\AppData\Roaming\npm-cache_logs\2018-04-27T09_58_11_725Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>build: npm run lint && npm run test && ngc
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      C:\Users\user\AppData\Roaming\npm-cache_logs\2018-04-27T09_58_11_778Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>postinstall: cd .. && npm i && npm run build && cd demo && rimraf node_modules/ngx-simple-modal && cp -rf ../dist node_modules/ngx-simple-modal
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

thanks

Could you dump the output for ng -v on your command line for me so I can try to recreate your environment?
Thanks

Hi.thanks for your answer
ng -v :
@angular/cli: 1.7.4
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.4.2
webpack: 3.11.0

I've updated  angular CLI with npm install -g @angular/cli@latest
now got error after ng serve:
ERROR in multi ./src/styles.css ./node_modules/ngx-simple-modal/styles/simple-modal.css
Module not found: Error: Can't resolve 'c:\aa\2\ngx-simple-modal-master\demo\node_modules\ngx-simple-modal\styles\simple-modal.css' in 'c:\aa\2\ngx-simple-modal-master\demo'
ERROR in src/app/alert-select/alert-select.component.ts(2,38): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/alert/alert.component.ts(2,38): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/app.component.ts(3,36): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/app.module.ts(5,55): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/app.module.ts(17,75): error TS2307: Cannot find module 'ngx-simple-modal/simple-modal/simple-modal-options'.
src/app/confirm/confirm.component.ts(2,38): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/confirm/confirm.component.ts(35,10): error TS2339: Property 'result' does not exist on type 'ConfirmComponent'.
src/app/confirm/confirm.component.ts(36,10): error TS2339: Property 'close' does not exist on type 'ConfirmComponent'.
src/app/confirm/confirm.component.ts(39,10): error TS2339: Property 'result' does not exist on type 'ConfirmComponent'.
src/app/confirm/confirm.component.ts(40,10): error TS2339: Property 'close' does not exist on type 'ConfirmComponent'.
src/app/custom-error/custom-error-handler.ts(2,36): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/parent-dialog/parent-dialog.component.ts(2,58): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/parent-dialog/parent-dialog.component.ts(37,14): error TS2339: Property 'close' does not exist on type 'ParentDialogModalComponent'.
src/app/prompt/prompt.component.ts(2,38): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/prompt/prompt.component.ts(35,10): error TS2339: Property 'result' does not exist on type 'PromptComponent'.
src/app/prompt/prompt.component.ts(36,10): error TS2339: Property 'close' does not exist on type 'PromptComponent'.

Im on the move, but it feels like the post install task has failed which
would normally build the module and make a copy into the node modules demo
folder. I did it this way because I had trouble using native file refs.
I'll check when in but if you try running a build on the root folder 'npm
run build' then back in demo try another ' npm i' and check if it's
node_modules/ngx-simple-modal exists and has contents.
Not sure why it's flopped on that.
I will help you resolve.
On Fri, 27 Apr 2018, 15:39 mrjohnr<EMAIL_ADDRESS>wrote:

Hi.thanks for your answer
ng -v :
@angular/cli: 1.7.4
@angular-devkit/build-optimizer: 0.3.2
@angular-devkit/core: 0.3.2
@angular-devkit/schematics: 0.3.2
@ngtools/json-schema: 1.2.0
@ngtools/webpack: 1.10.2
@schematics/angular: 0.3.2
@schematics/package-update: 0.3.2
typescript: 2.4.2
webpack: 3.11.0
I've updated angular CLI with npm install -g @latest
now got error after ng serve:
ERROR in multi ./src/styles.css ./node_modules/ngx-simple-modal/styles/simple-modal.css
Module not found: Error: Can't resolve 'c:\aa\2\ngx-simple-modal-master\demo\node_modules\ngx-simple-modal\styles\simple-modal.css' in 'c:\aa\2\ngx-simple-modal-master\demo'
ERROR in src/app/alert-select/alert-select.component.ts(2,38): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/alert/alert.component.ts(2,38): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/app.component.ts(3,36): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/app.module.ts(5,55): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/app.module.ts(17,75): error TS2307: Cannot find module 'ngx-simple-modal/simple-modal/simple-modal-options'.
src/app/confirm/confirm.component.ts(2,38): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/confirm/confirm.component.ts(35,10): error TS2339: Property 'result' does not exist on type 'ConfirmComponent'.
src/app/confirm/confirm.component.ts(36,10): error TS2339: Property 'close' does not exist on type 'ConfirmComponent'.
src/app/confirm/confirm.component.ts(39,10): error TS2339: Property 'result' does not exist on type 'ConfirmComponent'.
src/app/confirm/confirm.component.ts(40,10): error TS2339: Property 'close' does not exist on type 'ConfirmComponent'.
src/app/custom-error/custom-error-handler.ts(2,36): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/parent-dialog/parent-dialog.component.ts(2,58): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/parent-dialog/parent-dialog.component.ts(37,14): error TS2339: Property 'close' does not exist on type 'ParentDialogModalComponent'.
src/app/prompt/prompt.component.ts(2,38): error TS2307: Cannot find module 'ngx-simple-modal'.
src/app/prompt/prompt.component.ts(35,10): error TS2339: Property 'result' does not exist on type 'PromptComponent'.
src/app/prompt/prompt.component.ts(36,10): error TS2339: Property 'close' does not exist on type 'PromptComponent'.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/KevCJones/ngx-simple-modal/issues/40#issuecomment-384990476,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAqe8K8WKn62FeMDuOqZOPdbSemGwRzaks5tsy2sgaJpZM4TqGzZ
.

If I were you I'd explore the DOM in dev tools and check if it
A. Was created
B. What CSS rules were causing it to be invisible.
By design it's typically not a visibility setting when it's shown, the
modal is created and destroyed. The container it's in might be invisible or
the zindex might be low.
I don't suppose there is anyway you can share a broken example I can help
fix?
On Sat, 28 Apr 2018, 07:22 mrjohnr<EMAIL_ADDRESS>wrote:

What about invisible status,I've tried upgrading one project from
angularx-bootstrap-modal to ngx-simple-modal but as mention before no error
on console but dialog is invisible,I'm sure it exists because after calling
this.simpleModalService.addModal I can't focus nothing on the page,there
must be invisible.thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/KevCJones/ngx-simple-modal/issues/40#issuecomment-385144790,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAqe8EE-M-MJKPxG15D2F5o1Rs6mQSbRks5ttAqegaJpZM4TqGzZ
.

Hi
I've found this class  applied to div next to  simple-modal-wrapper:
.fade:not(.show) {
    opacity: 0;
}

        <confirm>

Confirmation

Bla bla confirm some action?

        <button class="btn btn-outline-danger" type="button">Cancel</button>
        <button class="btn btn-primary" type="button">OK</button>

  </confirm>

thanks

The 'in' class is added and removed for fading. Forgot that was added,
check you have it, it's part of the default style sheet in repo added.
I'll update the docs for migration to make this clearer.
On Sat, 28 Apr 2018, 11:03 mrjohnr<EMAIL_ADDRESS>wrote:

Hi
I've found this class applied to div next to simple-modal-wrapper:
.fade:not(.show) {
opacity: 0;
}

Confirmation

Bla bla confirm some action?

Cancel
OK

thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/KevCJones/ngx-simple-modal/issues/40#issuecomment-385162039,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAqe8KnT9heFQhZ6Pz1wZZCWBM-1iJTpks5ttD5XgaJpZM4TqGzZ
.

there is any fix I can do,for the moment it doesn't work for me even I put this in confirm.component.css
.fade:not(.show) {
    opacity: 1 !important;
}

Could you recreate the problem in a stackblitz demo? If so I will help fix,
but without seeing your global styles and implementation it's pretty tough
to assist.
On Sat, 28 Apr 2018, 11:31 mrjohnr<EMAIL_ADDRESS>wrote:

there is any fix I can do,for the moment it doesn't work for me even I put
this in confirm.component.css
.fade:not(.show) {
opacity: 1 !important;
}
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/KevCJones/ngx-simple-modal/issues/40#issuecomment-385163799,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAqe8A3XZ22qu2YuU5Scg3NxqIF7wUziks5ttEUYgaJpZM4TqGzZ
.

seems to work with this:
.modal-content {
    margin: 20px auto;
    max-width: 580px;
    position: relative;
    width: 100%;
}

Just one last problem and will not annoy you: when I want to close it pressing one of the confirm buttons it took up 1 second to close,there is any way to speed it up?thanks

Seems to work fine if I put css in style.css not in component.css:
 transition: opacity 1ms linear;

I'll update the readme to make this clearer for other people but the styles are indeed mean't to be loaded globally since you might have more than one modal, its the better place to put them. Leaving your local styles for customisations and modal content only.


Freezing phswisseph version.

Considering https://github.com/jyotisham/jyotisha/runs/3331564224?check_suite_focus=true , I've frozen pyswisseph version expected. Please fix your dev machine environment as needed @karthikraman and close this issue.

Sorry for the small API changes (quick and easy to fix...) but v2.8.0-1 has some creeping bugs anyway. Currently a huge effort towards comprehensive documentation. And later will setup a test suite, so testers and contributers needed, please hit me up if you feel like giving a hand.
All that should should lead us to a high-quality, and more stable module.

Great to hear about the proposed changes and continuing maintenance! I don't begrudge the small api changes - it's just downstream users like us should be using a fixed version of the library (which was not possible earlier for some feature we needed). Once there's a new version on pypi, it would be great if you let us know somehow.

Dang - old trusty frozen version no longer installs -
$ ~/gitland/python_venv_311/bin/pip install pyswisseph==2.8.0.post1
Collecting pyswisseph==2.8.0.post1
  Using cached pyswisseph-2.08.00-1.tar.gz (521 kB)
  Preparing metadata (setup.py) ... done
Building wheels for collected packages: pyswisseph
  Building wheel for pyswisseph (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [81 lines of output]
      Searching system libswe...
      pkg-config not found
      Using internal libswe
      /home/vvasuki/gitland/python_venv_311/lib/python3.11/site-packages/setuptools/dist.py:320: InformationOnly: Normalizing '2.08.00-1' to '2.8.0.post1'
        self.metadata.version = self._normalize_version(
      libswe/swecl.c: In function ‘swe_rise_trans_true_hor’:
      libswe/swecl.c:4444:11: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
       4444 |           if (!do_fixstar)
            |           ^~
      libswe/swecl.c:4447:13: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
       4447 |             if (rsmi & SE_BIT_GEOCTR_NO_ECL_LAT)
            |             ^~
      libswe/swehel.c: In function ‘calc_rise_and_set’:
      libswe/swehel.c:478:1: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation]
        478 | else
            | ^~~~
      libswe/swehel.c:484:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’
        484 |   iflag = epheflag|SEFLG_SPEED|SEFLG_EQUATORIAL;
            |   ^~~~~
      libswe/sweph.c: In function ‘search_star_in_list’:
      libswe/sweph.c:6534:20: warning: comparison of integer expressions of different signedness: ‘long int’ and ‘size_t’ {aka ‘long unsigned int’} [-Wsign-compare]
       6534 |     if (sp - sstar != strlen(sstar) - 1) {
            |                    ^~
      libswe/swephlib.c: In function ‘swi_strnlen’:
      libswe/swephlib.c:3598:17: warning: operand of ‘?:’ changes signedness from ‘long int’ to ‘size_t’ {aka ‘long unsigned int’} due to unsignedness of other operand [-Wsign-compare]
       3598 |   return stop ? stop - str : n;
            |                 ^~~~~~~~~~
      libswe/swephlib.c: In function ‘swe_get_astro_models’:
      libswe/swephlib.c:4271:9: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
       4271 |         if (imod == SEMOD_PREC_DEFAULT) imod = 0; break;
            |         ^~
      libswe/swephlib.c:4271:51: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
       4271 |         if (imod == SEMOD_PREC_DEFAULT) imod = 0; break;
            |                                                   ^~~~~
      libswe/swephlib.c:4273:9: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
       4273 |         if (imod == SEMOD_PREC_DEFAULT_SHORT) imod = 0; break;
            |         ^~
      libswe/swephlib.c:4273:57: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
       4273 |         if (imod == SEMOD_PREC_DEFAULT_SHORT) imod = 0; break;
            |                                                         ^~~~~
      libswe/swephlib.c:4275:9: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
       4275 |         if (imod == SEMOD_NUT_DEFAULT) imod = 0; break;
            |         ^~
      libswe/swephlib.c:4275:50: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
       4275 |         if (imod == SEMOD_NUT_DEFAULT) imod = 0; break;
            |                                                  ^~~~~
      libswe/swephlib.c:4277:9: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
       4277 |         if (imod == SEMOD_SIDT_DEFAULT) imod = 0; break;
            |         ^~
      libswe/swephlib.c:4277:51: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
       4277 |         if (imod == SEMOD_SIDT_DEFAULT) imod = 0; break;
            |                                                   ^~~~~
      libswe/swephlib.c:4279:9: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
       4279 |         if (imod == SEMOD_BIAS_DEFAULT) imod = 0; break;
            |         ^~
      libswe/swephlib.c:4279:51: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
       4279 |         if (imod == SEMOD_BIAS_DEFAULT) imod = 0; break;
            |                                                   ^~~~~
      libswe/swephlib.c:4281:9: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
       4281 |         if (imod == SEMOD_JPLHOR_DEFAULT) imod = 0; break;
            |         ^~
      libswe/swephlib.c:4281:53: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
       4281 |         if (imod == SEMOD_JPLHOR_DEFAULT) imod = 0; break;
            |                                                     ^~~~~
      libswe/swephlib.c:4283:9: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
       4283 |         if (imod == SEMOD_JPLHORA_DEFAULT) imod = 0; break;
            |         ^~
      libswe/swephlib.c:4283:54: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
       4283 |         if (imod == SEMOD_JPLHORA_DEFAULT) imod = 0; break;
            |                                                      ^~~~~
      libswe/swephlib.c:4285:9: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
       4285 |         if (imod == SEMOD_DELTAT_DEFAULT) imod = 0; break;
            |         ^~
      libswe/swephlib.c:4285:53: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
       4285 |         if (imod == SEMOD_DELTAT_DEFAULT) imod = 0; break;
            |                                                     ^~~~~
      pyswisseph.c:58:10: fatal error: Python.h: No such file or directory
         58 | #include <Python.h>
            |          ^~~~~~~~~~
      compilation terminated.
      error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pyswisseph
  Running setup.py clean for pyswisseph
Failed to build pyswisseph
ERROR: Could not build wheels for pyswisseph, which is required to install pyproject.toml-based projects

[notice] A new release of pip is available: 23.2.1 -> 24.1.1
[notice] To update, run: /home/vvasuki/gitland/python_venv_311/bin/python -m pip install --upgrade pip

Might be forced to upgrade and fix api used.


fix: 🐛 warning when connecting to 6.1 chains

Description
Prevents warning when connecting to 6.1 chains
Breaking Changes
None
JIRA Link
None
Checklist

[ ] Updated the Readme.md (if required) ?

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix typos

ping @vvvar

Sorry for keeping it for such long. Didn't had time to maintain the project due to a full-time job. Merged. Thanks!


Decline a call with iPhone 5c, riot is stuck

To reproduce:

Open the room in which you will receive the call
Receive a audio or video call from a user in this room
Hit "Decline"

Riot is frozen, the hang up button in the right of the bottom bar is red, as if the call was accepted

Which version?
Does it happen in appstore version?

On 0.3.13 develop #1907.
Doesn't happen in appstore version. Therefore, on appstore version when the call decline the call, the call isn't ended on caller device.

It seems to be fixed in build 1933.
@jeangb, reopen the issue if you do not agree ;)

@manuroe I still have this issue on develop 1948. Maybe it's related to my device.

Another fix was done with https://github.com/vector-im/riot-ios/pull/1330 which is in build 1958.
@jeangb, if you meet the bug again, please rageshake.

Validated


Trying to compile a kernel results in "FAILED: load BTF from vmlinux: No such file or directory"

Windows Version
Microsoft Windows [Version 10.0.22621.1992]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
Linux version <IP_ADDRESS>-microsoft-standard-WSL2
Distro Version
Debian 11 (lsb_release is not available as command)
Other Software
No response
Repro Steps
git clone https://github.com/microsoft/WSL2-Linux-Kernel
cd WSL2-Linux-Kernel
cp Microsoft/config-wsl .config
make -j 4

Expected Behavior
The kernel would be built
Actual Behavior
The build process ends with the error message
FAILED: load BTF from vmlinux: No such file or directory

Diagnostic Logs
No response

Thank you for reporting this @ReneNyffenegger. Do you see the same error by following the build instructions ?
$ sudo apt install build-essential flex bison dwarves libssl-dev libelf-dev
$ make KCONFIG_CONFIG=Microsoft/config-wsl

?

It turned out I had quite a few packages not installed: flex, bison, dwarves, libssl-dev and libelf-dev.
After installing them with the proposed sudo apt install... command and building it with make KCONFIG..., I got
/bin/sh: 1: bc: not found
after also nstalleding bc ...
sudo apt install -y bc
the build went on without further problems (I did not yet try to install the new built kernel)

I found the cause of the problem on Stack Exchange - https://unix.stackexchange.com/a/616479/608997

I ran into the same issue today, for me the issue was that pahole ran out of memory (peak memory usage of pahole was around 2.5GB).

In order to solve this problem, I removed the RAM limit in .wslconfig:
[wsl2]
# memory=3GB

After that I compiled the kernel without any problems
You can learn more about .wslconfig and memory limits at this link- https://learn.microsoft.com/en-us/windows/wsl/wsl-config#main-wsl-settings


issue with code_execution/invoke_reflectivepeinjection module

show [!] Error: module produced an empty script

because needed required variables are set to false
how do i set it to true

Hi @amainyebriggs,
This is now fixed. You can view it in this commit: https://github.com/PowerShellEmpire/Empire/commit/a46bdac77dac6d2aebfec4eb3ab56b99f9326309
Thanks

i was thinking it could be nice to make veil generate powershell payload
because in some cases cmd is blocked and the launcher.bat will not execute on test system
and the only way is to deliver it using metasploit  reflective dll post exploitation module
to inject into a process  whichs gives empire a session, but thats blah , i really will love a great flexibility on empire, where it will be able to generate a payload using veil-evasion and java, and also being able to deliver cobaltstrike beacon over foreign listener
cause the cobalt strike post exploitation command"powershell" delivers empire payload so it will be nice to be nice to the nice guy
cobaltbeacon<=============>empire

@amainyebriggs,
Since Empire is a post-exploitation agent, you have many different ways to execute a beacon (or any other payload) from within Empire (since you have code execution on the box). Currently, beacon dll's don't inject well using Invoke-dllinjection.
You can do the same thing with Empire to deliver a beacon payload as you would do with Cobalt Strike and an Empire payload. From CS, you can export a .ps1 package and then throw a function around the whole script. You can then do a "scriptimport /path/to/beacon.ps1". Once it imports, you can do a "scriptcmd " and it will execute the beacon payload.

thanks bro

No problem. You can also read about how Empire integrates with frameworks like CS and Metasploit here: http://www.powershellempire.com/?page_id=133


Configure output directory (currently fixed to ".svelte-kit")

Describe the problem
In monorepos, builds are often centralized into a single top-level build directory.
Is there anything that prevents that change from being innocent and simple?
Describe the proposed solution
In order for svelte-kit to support that, the SVELTE_KIT constant in constants.js should be replaced by a configuration option.
setting the kit.vite.build.outDir options prints an error:
build_server: The value for kit.vite.build.outDir specified in svelte.config.js has been ignored. This option is controlled by SvelteKit.

should the vite option be used, or should there be svelte-kit specific option?
Importance
nice to have

I couldn't find any existing bug report/feature request for this, which surprises me. I hope I am not duplicating things here. Feel free to close if there's already a similar issue.

The directory is used for more than Vite builds, so we can't use vite.build.outDir — Kit needs to control it. Having it be configurable seems reasonable, we would just need to bikeshed a name. buildDir? outDir? tmpDir? something else?

The directory is used for more than Vite builds, so we can't use vite.build.outDir — Kit needs to control it.

Can't we use vite.build.outDir for more than vite builds?

we would just need to bikeshed a name. buildDir? outDir? tmpDir? something else?

I have a preference for outDir, just because it's clearer than tmpDir, is more than just a buildDir, and is in line with vite.

Figuring the same issue for adding sveltekit to https://github.com/jhipster, as a monorepo project generator, while we can't change the output dir, we can't merge the sveltekit pr

It would be a great help to create a better Nx integration

Finaly found a workarround using adapter-static
  kit: {     adapter: adapter({       pages: 'target/classes/static/',       assets: 'target/classes/static/',       fallback: 'index.html',     }),     appDir: '_app',

@Rich-Harris You wanted to keep this open until the case of outDir being outside the CWD was sorted out, right?

I did, yeah — closed by accident. An outDir outside the project directory should work as long as you don't specify paths config, but we need to address that case before we can consider this fully closed

An outDir outside the project directory should work as long as you don't specify paths config,

FYI it doesn't work for me, with this config
import adapter from "@sveltejs/adapter-static";
import { mdsvex } from "mdsvex";

/** @type {import('@sveltejs/kit').Config} */
const config = {
  kit: {
    adapter: adapter(),
    prerender: { default: true },
   // either will cause the same error
    outDir: "/an/absolute/pat",
    outDir: "../a/relative/pat",
  },

  extensions: [".svelte", ".md"],

  preprocess: [
    mdsvex({
      extensions: [".md"],
      layout: {
        blog: "src/routes/blog/_post.svelte",
      },
    }),
  ],
};

export default config;

it throws a warning, runs for a bit, then dies with
# throws a warning
Your jsconfig.json should extend the configuration generated by SvelteKit:

# runs for a bit
...

# finally dies with
...
import { c as create_ssr_component, s as setContext, v as validate_component, m as missing_component } from "./chunks/index-7b568795.js";
^^^^^^

SyntaxError: Cannot use import statement outside a module

I'm also getting Your jsconfig.json should extend the configuration generated by SvelteKit: in my console now and this is the ONLY result on google lol...

Hey guys, we're trying to deploy a basic SvelteKit app but it's not working 🤪
I tried the outDir config here and it doesn't work.
FROM node:16.15.1-alpine

# install dependencies
WORKDIR /app
COPY . .

RUN npm ci
RUN npm run build

EXPOSE 3000
// with .svelte-kit it also fails :-/
CMD ["node", "./build/index.js"]

Getting the same error as reported by @gotofritz when setting the outDir outside the project root.
I guess a possible workaround for now would be to extend the build command under the package.json scripts by some commands that simulate the behaviour of a different output directory.
E.g. directly move the output after the build with something like:
rm -rf ../custom/outside/out/* && mv build/* ../custom/outside/out/ && rm -rf build

Which clears the output directory, moves over all build files and then removes the real build folder.

Another nice feature would be a configurable production "build"  output directory

@pine3ree that already exists: https://github.com/sveltejs/kit/tree/master/packages/adapter-node#out https://github.com/sveltejs/kit/tree/master/packages/adapter-static#pages

Oh thank you @babichjacob, so it was a static-adapter option. My mind was set to find a vite option for that...and was blind to the real solution. Kind regards.

Is this still not resolved, because the docs said it should work but the link to outDir documentation 404s on me?
I'm guessing @flcarre & @devidw solutions are still the winners until this becomes more priority?
I will say the svelte and Vite config files have multiple output directory properties and none of them work when you try it which is extremely frustrating for new comers.

Thanks, it works.

https://github.com/terwer/siyuan-plugin-publisher/blob/next/apps/publisher-app/svelte.config.js#L43

Is this still not resolved, because the docs said it should work but the link to outDir documentation 404s on me?
I'm guessing @flcarre & @devidw solutions are still the winners until this becomes more priority?
I will say the svelte and Vite config files have multiple output directory properties and none of them work when you try it which is extremely frustrating for new comers.

https://kit.svelte.dev/docs/configuration#outdir
The outDir config option here is a special directory that SvelteKit writes temporary files to, needed when running the development server and while building for production. It is not the same as Vite's outDir config option which specifies the location of the build output. SvelteKit overrides the Vite outDir option because it needs to run two Vite builds: the client build and the server build. It writes to .svelte-kit/output/client and .svelte-kit/output/server.


enforce types on default values

1: optional list<string> foo = {}

We parse this and assign a default value of {} when one isn't provided. Later we die when we try to serialize the default value. This probably shouldn't compile.
@junchaowu @breerly @kriskowal

Fixed by 0.4.0


[KeyVault] KV Certificates to test proxy

closes #23676

API change check for azure-keyvault-certificates
API changes are not detected in this pull request for azure-keyvault-certificates


indentation seems to be off when configuring the pager

When I use the pager config for any diff related command (git config --global core.pager "diff-highlight | diff-so-fancy | less -r"), the indentation seems to be off.

This does not seem to happen if I just do git diff | diff-highlight | diff-so-fancy.

You need to tell less the tab stops:
-git config --global core.pager "diff-highlight | diff-so-fancy | less -r"
+git config --global core.pager "diff-highlight | diff-so-fancy | less --tabs=1,5 -R"

@noscript that solved the issue. Thank you.

@noscript should we change the readme?

just did :)

Thanks :)


Add test for sending userops

Changes

Linear: https://linear.app/thirdweb/issue/INF-171/
Here is the problem being solved.
Here are the changes made.

How this PR will be tested

[ ] Open the dashboard and click X. Result: A modal should appear.
[ ] Call the /foo/bar API. Result: Returns 200 with "baz" in the response body.

Output
(Example: Screenshot/GIF for UI changes, cURL output for API changes)

PR-Codex overview
This PR focuses on enhancing the error handling in the pollTransactionStatus function and adding user operation tests in the userop.test.ts file. It introduces an errorMessage property and improves transaction error logging.
Detailed summary

Added errorMessage property to the Timing type in transactions.ts.
Changed timing to be a constant in pollTransactionStatus.
Improved error logging in pollTransactionStatus.
Added a suite of user operation tests in userop.test.ts.
Implemented tests for sending NFT claims and handling permission errors.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Merge activity

Oct 9, 4:48 AM EDT: @joaquim-verges started a stack merge that includes this pull request via Graphite.


Cannot find ionic scss

Hi!
I've tried the setting stack to -14 solution (but i believe that the latest version of heroku doesn't require that setting already since they have deprecated the previous stack version https://devcenter.heroku.com/articles/cedar), and i'm still getting the error of
remote: Errors prevented bundling:
remote: While building the application:
remote: /tmp/build_c76b59a4fbbd167b917775f6cee37410/client/stylesheets/app.scss:4:9:
remote: Scss compiler error: file to import not found or unreadable:
remote: .meteor/local/build/programs/server/assets/packages/meteoric_ionic-sass/ionic
remote: Current dir: /tmp/build_c76b59a4fbbd167b917775f6cee37410/client/stylesheets/
remote:
remote:
remote:
remote:  !     Push rejected, failed to compile Node.js app

any help will be greatly appreciated!

Cedar-10 vs cedar-14 shouldn't be (and hasn't yet been) an issue, as far as I know.
Your issue looks like it's related to #19 -- meteor needs to launch once to build your static scss files before it can build the bundle.  Try setting BUILDPACK_PRELAUNCH_METEOR = 1 in your heroku environment and rerunning.

Hi @yourcelf !
Thanks for your prompt reply! i've followed your suggestion, and have managed to deploy to heroku, however, now the deployment doesn't show any CSS at all! Here's the link to my deployment: http://mighty-forest-6021.herokuapp.com/
Any idea what may have caused this??


Fix Samples Section

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

Somehow my previous PR didn't merge properly for the samples section, so creating this PR to fix it


Rendering Glitches in  Component Options in Firefox When Using Objects as Values

Vue version
3.4.19
Link to minimal reproduction
https://play.vuejs.org/#eNp9U8GO0zAQ/ZWRL+lquwlluVDSSgv0UA6AttwwQm0yLd5N7Mh2QlGUf2dsp2nKshspkj3vzfjNG7tld1UVNzWyOUtNpkVlwaCtqyWXoqyUttCCxj10sNeqhIioEZdcZkoaC7VB/aWygjawcLzJdy6BUkQ+h2gWTUGrAml5l5dCRtBNR/DrM7zKhVX6H/z2jG/qnRO3Q8fh8sfVu7MGgwVmFvOgo5fxvAKXGhKFtKibbdGnvHII9b7uw5PJFSyW0DpFJ2pMf43X18TspjALMtIkGEeW0cZiWRVbi7QDcH9aLVuSczqs69LEucutB4N6aG5KlWOx4OyyHc58HfelKjTY3OyVJmK/FXI8Bc5g/oh/BjgWuQt52UNwVJTMbqGnOqNI3nBeEuI9l7r0ynyXPpCLZqiz6VXD+uPclbzsglRQYUh3GpKnKfd+QE+TLvSkSTguTQaD2ZRZQ6Pci0P8YJSkK+yHxVmmykoUI1OofCjD2bYo1O9PPmZ1jf7C+ZxfmD3+J/5gji7G2VeN5HODnA2Y3eoD2gCvNp/xSOsBpIHWBbFfAO/RqKIOI3G097XMSfaI59Wu/UMU8vDNrI4WpTk15YQ6Zng2nNHj/PBC62e5t/Ebn0fXmFz82aB2NclAAuLZW9b9BfSbVgo=
Steps to reproduce

Utilize a component incorporating a <select> element, with each <option> explicitly bound to an object using the :value="option" attribute.
Trigger DOM updates at short intervals using setInterval, causing frequent re-rendering.
Open the dropdown of the <select> component in Firefox to observe rendering issues.

What is expected?
The options within the dropdown should render without any glitches, allowing for the selection of an option.
What is actually happening?
The dropdown options glitch, showing intermittent rendering, making it impossible to select any option.
System Info
No response
Any additional comments?
This issue has been observed in Firefox version 123.0 (64-bit)

+ v-memo="[selectedOption]"

<select v-model="selectedOption" v-memo="[selectedOption]">


GA4GH server 0.1.2 broken

It seems that the update has broken the server or the documentation have not been updated. I am very sure that couple of weeks ago when I followed the API demo documentation things were working.
There seems to be two problems.
First, the server now requires the following directories that are not part of the example data set
OSError: [Errno 2] No such file or directory: '*/ga4gh-example-data/variants'
OSError: [Errno 2] No such file or directory: '*/ga4gh-example-data/references'
OSError: [Errno 2] No such file or directory: */ga4gh-example-data/reads'

Second, executing
"curl --data '{}' --header 'Content-Type: application/json' \http://localhost:8000/datasets/search

gives the following error message
{"errorCode": 523835337, "message": "The request path was not found"}

Thanks for the bug report @mkzia. A few more details would be useful: are you using the version of the server from pypi or from github?
I agree the situation with the released version and the version in github being quite different is very unfortunate and confusing. We hope to  rectify this soon with an updated release, and we can then update all of the documentation as well.

I downloaded it using pip, which shows that the version is ga4gh==0.1.2.

The correct documentation should then be
http://ga4gh-reference-implementation.readthedocs.org/en/stable/index.html
Does this clear things up?
Unfortunately it's not at all clear that this is the case, and I apologise for the confusion. The main problem is that the development version has diverged quite a lot from the released version. Hopefully we'll be able to release an update soon.

Yes. I was following the wrong documentation. Thanks!

OK, thanks @mkzia. Closing this issue.


Update Settings menu styles

[x] Add more padding
[x] Move slightly higher to appear more 'from' the button
[x] Lighten the bg colour

Essentially aim to go 'more chrome'

This is sorted on the #420 branch

@safesurfer there's not sooo much to check here. This was some visual changes over a previous state.

The updated state FYI: https://www.dropbox.com/s/2oo456fdn32b1iv/Screenshot 2018-12-03 18.35.31.jpg?dl=0

Verified the setting menu style


Move other dadguide enums into common

actually this PR makes me think i was wrong to create the /common.py file, and all of the enums shouldve just gone into that models file in the first place


compare to SIBR_gaussianViewer_app

it seems to render more blurry than SIBR_gaussianViewer_app？Is that because of webgl？

Hi there!
Something similar to the SIBR Gaussian viewer is the Aras-P Unity plugin, but it is not yet compatible with WebGL.
Using the same dataset, both SIBR and the Unity plugin provide excellent visuals. However, when it comes to web deployment, neither seems competitive.
Is there any room for improvement on this?

got it~


host kubeflow fairing API docs to readthedocs.io

What this PR does / why we need it:
That's not good if use markdown or htmlpreview.github.io. As kubeflow pipeline SDK, it's great to host  kubeflow fairing API docs to readthedocs.io
Which issue(s) this PR fixes:
Fixes #413
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

This change is

/lgtm

/retest

/lgtm

/approve


Add a GIF in the ReadMe

Add a GIF (lightweight) instead of the static image in the readme file, which shows how to use the H2. Make sure to remove the current image from the repository as well and the new GIF should be uploaded on the img directory.

HelIo! I would like to work on this.

Sure @ming060, please go ahead.

Parent Issue was: #36


Add authentication and authorization

Fixes #125  ; refs #125
Implement SSO (authentication) + AD/LDAP (authorization).
@ucsdlib/developers - please review

Coverage decreased (-1.3%) to 90.458% when pulling e0bcf1b38c4b445702c13be2608fc2d7554f2ae3 on feature/ad_ldap into a8f133a7f31417ece7f71c73c9d5b6433de04870 on develop.

Coverage decreased (-0.6%) to 91.214% when pulling cc6a892a5a99a68fbaf197e8545ca3b56738001a on feature/ad_ldap into a8f133a7f31417ece7f71c73c9d5b6433de04870 on develop.

@mcritchlow @lsitu - I tried Longshou's suggestion before it doesn't work.  I tried again today and still got that error.  I think it's because it failed at this part
https://github.com/ucsdlib/horton/blob/feature/ad_ldap/spec/controllers/batch_import_controller_spec.rb#L58
because it called hyrax:user model

BatchImportController Excel XL metadata source #create enqueue an update job is successful
Failure/Error: log.success!
ActiveModel::UnknownAttributeError:
unknown attribute 'password' for User.

That's odd. Using @lsitu's suggestion, your just overriding the methods defined in the module in the included class.
Is there a stacktrace, or any additional info from byebug? I'm curious where/why it's bypassing the methods you're defining locally.

@mcritchlow - It related to the structure of the module hyrax:user
Here's the stack trace.  It does call back to hyrax:user class.  It doesn't use these methods in model/user.rb
 # /Users/tchu/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/bundler/gems/hyrax-9f117a32a9fd/app/models/concerns/hyrax/user.rb:163:in `find_or_create_system_user'
 # /Users/tchu/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/bundler/gems/hyrax-9f117a32a9fd/app/models/concerns/hyrax/user.rb:146:in `audit_user'
 # /Users/tchu/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/bundler/gems/hyrax-9f117a32a9fd/app/services/hyrax/message_user_service.rb:27:in `job_user'
 # /Users/tchu/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/bundler/gems/hyrax-9f117a32a9fd/app/services/hyrax/message_user_service.rb:11:in `call'
 # /Users/tchu/.rbenv/versions/2.4.0/lib/ruby/gems/2.4.0/bundler/gems/hyrax-9f117a32a9fd/config/initializers/hyrax_callbacks.rb:29:in `block in <top (required)>'

@VivianChu I've added a commit https://github.com/ucsdlib/horton/pull/139/commits/1f0bfdd1c1e85af2500ee1ddefd612043ea26eb1 that works in my local environment as we discussed this morning. Could you do a clean checkout to see whether it works for you?

@lsitu - It works for me.  Thanks.

Coverage decreased (-0.7%) to 91.108% when pulling c6a60eb5dfb975069c1a38abccc4fb6b8ca92222 on feature/ad_ldap into a8f133a7f31417ece7f71c73c9d5b6433de04870 on develop.

@ucsdlib/developers - please review, comment, etc... Thanks

Coverage decreased (-0.7%) to 91.242% when pulling 3a20aede9443cf4d9f4e6ca7a6b211145fcd5017 on feature/ad_ldap into 172d66d1a93ae2dbfda0783e78a484c2f7ce1b65 on develop.

@ucsdlib/developers - The commits have been merged for easier review.  Thanks

:+1:


Wink sensors

Haven't followed the guidelines yet, since I'd like to start a discussion on sensors.
I built this based on my Quirky Tripper, but there are other sensor_pod_id types that do things like motion.  Should we customized down to the device 'sensing' or try to keep an abstract set of states that different sensors might populate?

Coverage decreased (-1.02%) when pulling abfaca3bfbad93675bd23e3d056a184b77e01f93 on kangaroo:wink-sensors into 93f93aff93870b316bacd944b6c337070a85342d on balloob:master.

Ooh, this is very cool. I must admit that I have not given much thought yet to how to properly integrate sensors into Home Assistant. Here are some of my thoughts (unorganized, in no way a requirement to get this pull request merged):

The things that can be sensed are basically unlimited.
There is a difference between event based sensors (ie motion sensor) and measurement sensors (thermometer).
Sensors are read only and can report multiple pieces of data
About the interface: I would imagine 1 card per location that has sensors. ie. A Garden card with current temperature/humidity.
For other components to be able to respond to sensor values, new listeners could be useful. ie a temperature listener that would only fire once when the sensor falls below a certain temperature but would require a significant temperature increase above the threshold before firing again when getting below the limit.
In Home Assistant, the best approach for now is to have a different state for each measurement with the measurement as the state. An attribute to each sensor could be a grouping/location attribute so we can group them in the interface later.

Looking at your code, I think you have done an excellent job and have set a good foundation for sensors!

Could you create a pull request against the dev branch so that I can make sure that all other components are not going crazy with the increased time changed events before we merge into master?

Will rebase on dev.  As per your comments vis-a-vis sensor.  I mostly agree.  They're a complicated base, and I'm not sure its possible to encompass everything on first pass.  I at the least only own one, with one on the way.  All the datasets will be hard to predict.  I hope to not, but API/ABI break might be needed.

Closing this, fixed pylint and flake8 issues.  Will reopen on dev.


Ref to aludratest-surefire-provider broken

POM references aludratest-surefire-provider 3.0.2 which is not released yet.
Workaround:
Change POM locally and change version from "$aludratestversion" to "3.0.2"

Hmm, according to mvnrepository, it should be available in Maven Central:
http://mvnrepository.com/artifact/org.aludratest/aludratest/3.0.2
What is exactly the error message you receive? Have you tried mvn -U compile?

At that time repo1 search did not found 3.0.2, only 3.0.0.
Might be a repo synchronization topic.
No,  I did use -U.
Will check tomorrow.


Category for WebAssembly-compiled OPA policies?

Neither the official npm nor the Go SDK are listed yet - so, where should https://github.com/christophwille/csharp-opa-wasm go? (I think it should be grouped around wasm and not added to the language listings)

Agreed, I think WASM deserve a category of its own. A new top level section after "Language integrations" with yours and the Go / Node ones, WDYT?

Agreed, I think WASM deserve a category of its own. A new top level section after "Language integrations" with yours and the Go / Node ones, WDYT?

That location sounds about right. Have sub-sections for "SDKs", "Docs" and "Blogs and articles".

That location sounds about right. Have sub-sections for "SDKs", "Docs" and "Blogs and articles".

Sounds great! Will you do the honors?

Sounds great! Will you do the honors?

Can do, but... maybe you know more links than I do? (most of the things I used I put on the root README on my repo)

Can do, but... maybe you know more links than I do? (most of the things I used I put on the root README on my repo)

Give it a shot and I can add more later. Not trying to be lazy about it, more like I'd appreciate seeing some contributors listed for the project rather than looking like a one man show, which it certainly isn't given a lot of links are from the OPA Slack, and so on :)

Give it a shot and I can add more later. Not trying to be lazy about it, more like I'd appreciate seeing some contributors listed for the project rather than looking like a one man show, which it certainly isn't given a lot of links are from the OPA Slack, and so on :)


Add version control module

Changelog Description
Adds version control module
Additional info
Includes system settings to toggle no/off and choose which version control backend to use.

It currently only has a backend for perforce.
Testing notes:
It should start up with no problem, but it won't do anything as it is standalone and contains no modifications to the main code base that would be required to get it properly functional.

It's good to note that this PR adds over 75 MB to the files that get added to each .zip deployment due to the vendorized P4 files.

We are working on communicating with perforce using websockets - that would eliminate the need to have multiple vendorize perforce api for every individual dcc specific python, so this could be then refactored slightly.

Interesting - are there docs for that, I would be interested to take a look.
But yeah, it is written to use any backend that is exposed via the interface.

Just a note that as much as this functionality is highly desired until we're done with the websocket perforce connection, it is not viable to merge it. We'll happily keep it open and get back to it once we're ready

That makes sense, I have changed to a draft.
Is there any existing code for this approach that I can take a look at?
I have pondered on this for a while and I have a worry that whilst you guys are solving the problem of interfacing with perforce in a novel and potentially clever way, it might be too novel and clever.
I have been unable to find any documentation on perforce connection with websockets ( including the magic of AI search engines... ) which is not an ideal situation.
And at least across the games industry where the vast number of p4 users are, the standard is to use P4Python which could mean reduced contributions if it is vastly different from what is the norm.
And the last thing, which I guess definitely would have been discussed, perforce is a complex thing to work with, so the planned approach would have to be certain to have the matching functionality as P4Python or p4 cmd.
Please feel free to disregard my concerns if this has all been considered already.

@munkybutt the native perforce integration has move quite a bit since this PR was openend and because we're splitting OpenPype into ayon-core and individual addons, this PR would have to be re-created to target one of those. Thank you for the contribution, it helped immensely with the perforce work we've done since.

@mkolar - thanks for the update!
I have since moved on to a new studio and am in the process of getting Ayon set up there, which will involve a rewrite of this anyways.


update crypto vendors

as title

@sapk see maintainers channel on discord

ping LG-TM

Does this need backporting?

@kolaente yes

Is this a fix for CVE-2020-9283 when using the builtin SSH server?

@acohn yes this has been discussed on discord channel and I think it would be disclosed when 1.11.2 is released.


Error thrown when setting dynamic current and vehicle not charging, expected?

The problem
I've created an automation that uses the service "set circuit dynamic limit" for my Easee One charger.
I always get this error when executing it with the car is not charging, is this to be expected?
Version of Easee integration having the issue?
0.9.59
Version of Home Assistant Core having the issue?
2024.9.0
Anything in the logs that might be useful for us?
Logger: homeassistant.components.automation.limit_dynamic_current
Source: helpers/script.py:525
integration: Automation (documentation, issues)
First occurred: 10:04:46 AM (1 occurrences)
Last logged: 10:04:46 AM

Limit dynamic current: Error executing script. Unexpected error for call_service at pos 3: 'dynamicCircuitCurrentP1'
Traceback (most recent call last):
  File "/config/custom_components/easee/controller.py", line 760, in check_circuit_current
    or charger_data.state[compare_p2] != current_p2
       ~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/pyeasee/utils.py", line 55, in __getitem__
    if type(self._storage[key]) == str and validate_iso8601(self._storage[key]):
            ~~~~~~~~~~~~~^^^^^
KeyError: 'dynamicCircuitCurrentP2'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 525, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 764, in _async_call_service_step
    response_data = await self._async_run_long_action(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 727, in _async_run_long_action
    return await long_task
           ^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2763, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2806, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/easee/services.py", line 582, in circuit_execute_set_current
    circuit = controller.check_circuit_current(
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/easee/controller.py", line 766, in check_circuit_current
    charger_data.config[compare_p1] != current_p1
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/pyeasee/utils.py", line 55, in __getitem__
    if type(self._storage[key]) == str and validate_iso8601(self._storage[key]):
            ~~~~~~~~~~~~~^^^^^
KeyError: 'dynamicCircuitCurrentP1

Additional information
No response

I think this and your other problem is one and the same really.
Did this start happening after upgrading HA to the latest version possibly?

Probably same root cause as https://github.com/nordicopen/easee_hass/issues/454

I think this and your other problem is one and the same really. Did this start happening after upgrading HA to the latest version possibly?

I don't know, as when I installed the integration for the first time I was asked to upgrade HA, so I ended up on 2024.9.0. My previous HA version was not supported.

Ok, I have not myself tried it with 2024.9.0 yet, so I will try that later this evening and see if I can reproduce the errors you are seeing.

No, it works for me with 2024.9.0...
If you have not, can you please enable logging for Easee (see readme) and then search for any rows containing state_dynamicCircuitCurrentP1, state_dynamicCircuitCurrentP2 or state_dynamicCircuitCurrentP3 in the log file after doing a restart?
You should see some lines like this, indicating where values for the circuit current limits are received from the cloud.
´´´
2024-09-05 17:31:51.527 DEBUG (MainThread) [custom_components.easee.controller] Observation state_dynamicCircuitCurrentP1 0 type 3 <class 'int'>
2024-09-05 17:31:57.616 DEBUG (MainThread) [custom_components.easee.controller] Callback EXXXX 111 state_dynamicCircuitCurrentP1 0.0 3
2024-09-05 17:31:51.527 DEBUG (MainThread) [custom_components.easee.controller] Observation state_dynamicCircuitCurrentP2 0 type 3 <class 'int'>
2024-09-05 17:31:57.616 DEBUG (MainThread) [custom_components.easee.controller] Callback EXXXXX 112 state_dynamicCircuitCurrentP2 0.0 3
2024-09-05 17:31:51.527 DEBUG (MainThread) [custom_components.easee.controller] Observation state_dynamicCircuitCurrentP3 5 type 3 <class 'int'>
2024-09-05 17:31:57.616 DEBUG (MainThread) [custom_components.easee.controller] Callback EXXXX 113 state_dynamicCircuitCurrentP3 5.0 3
´´´

Hang on. Easee One is a one phase version, right?
It could be that it provides the data in a different way...
Do you have anything that says Callback EXXXXX 112 state_dynamicCircuitCurrentP1/2/3 at all?
Do you have any log file rows that says Unsupported data id?

Hang on. Easee One is a one phase version, right? It could be that it provides the data in a different way... Do you have anything that says Callback EXXXXX 112 state_dynamicCircuitCurrentP1/2/3 at all?  Easee One is a one phase version, right? It could be that it provides the data in a different way... Do you have anything that says Callback EXXXXX 112 state_dynamicCircuitCurrentP1/2/3 at all? Do you have any log file rows that says Unsupported data id?

2024-09-05 18:32:27.037 DEBUG (MainThread) [custom_components.easee.controller] Callback XXXXXXXXX 11 state_chargerOfflineReason 0 4
2024-09-05 18:32:27.038 DEBUG (MainThread) [custom_components.easee.controller] Callback XXXXXXXXX 15 config_localPreAuthorizeEnabled True 2
2024-09-05 18:32:27.038 DEBUG (MainThread) [custom_components.easee.controller] Callback XXXXXXXXX 16 config_localAuthorizeOfflineEnabled True 2
2024-09-05 18:32:27.038 DEBUG (MainThread) [custom_components.easee.controller] Callback XXXXXXXXX 17 config_allowOfflineTxForUnknownId True 2
2024-09-05 18:32:27.038 DEBUG (MainThread) [custom_components.easee.controller] Callback XXXXXXXXX 21 config_detectedPowerGridType 3 4
2024-09-05 18:32:27.039 DEBUG (MainThread) [custom_components.easee.controller] Callback XXXXXXXXX 22 config_circuitMaxCurrentP1 40.0 3
2024-09-05 18:32:27.039 DEBUG (MainThread) [custom_components.easee.controller] Callback XXXXXXXXX 30 state_lockCablePermanently False 2````

> No, it works for me with 2024.9.0... If you have not, can you please enable logging for Easee (see readme) and then search for any rows containing state_dynamicCircuitCurrentP1, state_dynamicCircuitCurrentP2 or state_dynamicCircuitCurrentP3 in the log file after doing a restart? You should see some lines like this, indicating where values for the circuit current limits are received from the cloud.
>
> ```
> 2024-09-05 17:31:51.527 DEBUG (MainThread) [custom_components.easee.controller] Observation state_dynamicCircuitCurrentP1 0 type 3 <class 'int'>
> 2024-09-05 17:31:57.616 DEBUG (MainThread) [custom_components.easee.controller] Callback EXXXX 111 state_dynamicCircuitCurrentP1 0.0 3
> 2024-09-05 17:31:51.527 DEBUG (MainThread) [custom_components.easee.controller] Observation state_dynamicCircuitCurrentP2 0 type 3 <class 'int'>
> 2024-09-05 17:31:57.616 DEBUG (MainThread) [custom_components.easee.controller] Callback EXXXXX 112 state_dynamicCircuitCurrentP2 0.0 3
> 2024-09-05 17:31:51.527 DEBUG (MainThread) [custom_components.easee.controller] Observation state_dynamicCircuitCurrentP3 5 type 3 <class 'int'>
> 2024-09-05 17:31:57.616 DEBUG (MainThread) [custom_components.easee.controller] Callback EXXXX 113 state_dynamicCircuitCurrentP3 5.0 3
> ```

Ok, so it reports only the state_dynamicCircuitCurrentP1 etc...
Strange that your original post log file extract says
KeyError: 'dynamicCircuitCurrentP1 in that case, that specific key should be present.
I would expect it to fail with KeyError: 'dynamicCircuitCurrentP2' and KeyError: 'dynamicCircuitCurrentP3', but not with KeyError: 'dynamicCircuitCurrentP1', so not sure I understand why that happens...
In any case, I guess we need to change some things to be able to support these one phase versions...

@jacoscar if you are able, please try this PR https://github.com/nordicopen/easee_hass/pull/456

@jacoscar I suspect you have a similar issue as this one also?
https://github.com/nordicopen/easee_hass/issues/451
Can you please tell us which product code the Easee One has? Should be visible in same way in the GUI as in that issue.

@jacoscar I suspect you have a similar issue as this one also? #451 Can you please tell us which product code the Easee One has? Should be visible in same way in the GUI as in that issue.

@jacoscar if you are able, please try this PR #456

it works and I don't see the error when changing the dynamic circuit current limit anymore
thanks!

Thanks for testing, please let us know if you encounter anything else later.

Yes, you would need to enter at template that uses the current value of the setting and add or subtract from that to get the new value. Which should be possible to do if you switch to YAML mode.

This issue is most likely solved in v0.9.60. Please update and test.

tested and ok


CreateRequestsSharePointSite function error  "Failed to create the SharePoint site {0} Code: Authorization_RequestDenied Message: Insufficient privileges to complete the operation" v2.0.2

Description
Running the deployment script for 2.0.2 results in "Failed to create the SharePoint site {0} Code: Authorization_RequestDenied Message: Insufficient privileges to complete the operation"
This appears for CreateRequestsSharePointSite function
The script actually does create the required Sharepoint site, but it seems that no permissions are applied to it.
If I browse to the site as the GA that ran the deploy script, I am unable to access it and am asked to request access.
The PNP app reg has the following granted permissions, as per the deployment guide:
Microsoft Graph (2)
Group.Create | Application
Group.Read.All | Application
SharePoint (1)
Sites.FullControl.All
PNP shell module logging capture submitted below.
Many thanks:)
Steps to reproduce

Create the PNP app registration.
Run the deploy.ps1 script.

Expected results
SPO site creation and permissions applied.
Actual Results
SP Site is created but permissions cannot be applied. Output from PNP shell module log is as follows (real names redacted):
pwsh Error: 0 : 2024-10-14 09:39:10.3018	[PnP.Framework]	[0]	[Error]	Graph call returned the following error: Insufficient privileges to complete the operation..	0ms
pwsh Error: 0 : 2024-10-14 09:59:05.7690	[PnP.Framework]	[0]	[Error]	ExecuteQuery threw following exception: Microsoft.SharePoint.Client.ServerException: Cannot get site https://.sharepoint.com/teams/ProvisionAssist.
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
at Microsoft.SharePoint.Client.ClientRequest.ExecuteQueryToServerAsync(ChunkStringBuilder sb)
at Microsoft.SharePoint.Client.ClientRequest.ExecuteQueryAsync()
at Microsoft.SharePoint.Client.ClientRuntimeContext.ExecuteQueryAsync()
at Microsoft.SharePoint.Client.ClientContext.ExecuteQueryAsync()
at Microsoft.SharePoint.Client.ClientContextExtensions.ExecuteQueryImplementation(ClientRuntimeContext clientContext, Int32 retryCount, String userAgent)
ServerErrorCode: -1
ServerErrorTypeName: Microsoft.Online.SharePoint.Common.SpoNoSiteException
ServerErrorTraceCorrelationId: d7c659a1-10b7-a000-2b97-0c6abc17fb46
ServerErrorValue:
ServerErrorDetails:
.	0ms
pwsh Error: 0 : 2024-10-14 09:59:17.3410	[PnP.Framework]	[0]	[Error]	Graph call returned the following error: Insufficient privileges to complete the operation..	0ms
Solution component
Deployment Script
Operating system (environment)
Windows
Additional Info
version 2.0.2 being used here

I was running the deploy script again to capture another problem where the script was not handing an existing site correctly (it would fail with an error that states there was an existing site with the same name).
However, the script appears to be running through, but still does not apply any permissions to the GA account that ran the deploy script. When browsing to the site, I am asked to request access.

@lhaynes1970 the deployment script grants permission to the Service Account when creating the site not the account you run the script as.
This will be the Service Account you specify in the parameters.json, this is done by design so that all of the assets pertaining to the solution use (and are owned) by the Service Account.
I'll close this issue but please reopen if you still encounter problems.
Thanks

that makes sense. Apologies, and many thanks for coming back to me


Accept db tools conn with proxy authentication

In this upload, the provider can accept db tools connection with proxy authentication, only if username is set in proxy authentication, without password or roles.
Specifically, according to OCI docs,
DatabaseToolsConnectionOracleDatabaseProxyClient has two direct known subclasses,
which is DatabaseToolsConnectionOracleDatabaseProxyClientNoProxy, and
DatabaseToolsConnectionOracleDatabaseProxyClientUserName.
If a db tools connection with proxy authentication is given, we can retrieve proxy authentication info from proxyClientUserName. Otherwise, we will get proxyClientNoProxy.
Username is retrieved here and added to properties of the Connection. If retrieved password or roles are not null, an exception will be thrown.
Also README is updated in oci.
Please take a look.

Looks good to me, thanks. Approved this PR while we should wait until the proxyAuthentication APIs become available in OCI SDK before we merge this branch.

Correct my comment above. The proxyAuthentication APIs are available in OCI Java SDK 3.28.1. Thanks @norah-li for reminding.


Game Crashes when placing slabs/destroying slabs

Crash report: https://pastebin.com/vxWj4W7D
Not sure if it a mod conflict, but the game consistently crashes when placing or destroying slabs especially vertical slabs and double layered slabs

I have basically the same crash with the same error. My world is now broken because of it.
Unfortunately I can't share the crash log because my log is so long that it exceeds the maximum file size on pastebin/hastebin.

Can confirm the same issue on my end. I can upload my crash log, but it's pretty much identical.
also worth noting: since the error has something to do with dim7 (same dimension twilight forest uses by default), I've noticed it causing issues with the twilight forest mod, where the twilight portal just spits me back out into the overworld as if it were the twilight forest. Removing double slabs has fixed both issues.

https://github.com/TheidenHD/DoubleSlabs/releases/tag/0.11.1

Thanks for the bug report. I'm extremely sorry in the delayed response and inactivity. I believe this crash is a duplicate of #140. Please use that issue to post further updates. Thank you again, and my sincerest apologies for the inconvenience.


[BUG] - cardano cli should use mary era as default if era not specified.

Internal/External
External   otherwise.
Area
Other   Any other topic (Delegation, Ranking, ...).
Summary
cardano cli should use allegra era as default if era not specified.
Steps to reproduce
query utxo without specifying era:
cardano-cli query utxo --address $(cat payment.addr) --mainnet
Shelley command failed: query utxo Error: A query from a certain era was applied to a ledger from a different era: EraMismatch {ledgerEraName = “Allegra”, otherEraName = “Shelley”}

Expected behavior
if not specified the default should be used
Version: 1.25.1

this was fixed in the meantime.


Feature/1838 auto campaignmember enhancements

Warning
Info

This release disables by default the automatic Campaign Member management for Opportunities. Go to NPSP Settings > Donations > Campaign Members to re-enable the feature.
This release includes more flexibility for which status is chosen for automatic campaign member management.

Issues
Fixes #1838

@njjc yay!  was just going to submit an issue to request settings for the default statuses.  very helpful!  any idea when this will be rolled out?

@mscholtz  tomorrow's release to sandbox, week after to production!

@davidhabib could you please merge this after #1872 goes through? Thank you!


Added proper brackets in the dict on helpers.py line 252

Fixed

This was addressed in 1.1.8, thank you!


Trying to create an index in db.seed running rspec fails

Under db/seeds.rb
Model.__elasticsearch__.create_index! force: true
$ bundle exec rspec --backtrace
Backtrace

Model
class Model
  include Mongoid::Document
  include Mongoid::Attributes::Dynamic
  include Elasticsearch::Model

  def as_indexed_json(_options = {})
    as_json(only: %w[id name product_id product_variant_id])
  end
end

I opened a PR with a fix for this. If you're impatient, you can update your Gemfile entry for elasticsearch-model to use the fix before they merge the fix and release a new version:
gem "elasticsearch-model", github: "indirect/elasticsearch-rails"

(At least, I hope it's a fix! It seems like the same keyword arguments issue. If it's not, apologies.)

Thanks for your help @indirect !


how can I get something like '' ?

How do I code from Stipple.Html.div() to get something like <div :class="hidden"></div> ?
Thanks

@hhaensel

this has been the convention in Stipple from the beginning and yes, it is intentional. In Stipple the convention is that a symbol value is a reference to the name of a field from the ReactiveModel. With this convention, Stipple generates Vue specific HTML attributes code.
this does not work in Genie which a) predates Stipple; b) does not generate Vue specific code.
there should be a well defined/supported/recommended way to do these things in Genie as well - but Genie conceptually operates at a lower level of abstraction: it is JS framework agnostic. So it should allow for the generation of any kind of code for integration with any kind of framework, not just with Vue.
as explicitly supporting all the possible JS frameworks is not an option (though it could be done with individual plugins/adapters, eg GenieVue.jl, GenieReact.jl, etc but that's a different story), it's best to support none, and just provide the ability for the users to write any kind of JS framework integration code. What do I mean by that? Say we add support for Vue in Genie so that foo = :foo produces :foo = "foo". But what if in some other framework the HTML properties should be foo: = "foo"? We can't optimize for Vue in Genie.
I agree that the fact that Stipple elements support foo = :foo but Genie elements do not is super confusing and should be addressed. So yes, unified syntax would be great.

I think a good approach could be:

extend Genie to allow/provide a way to write non-standard HTML attributes (eg containing @, :, -, etc) but do not explicitly support any specific JS framework. I expect this will be non-breaking as the most straightforward way would be by using ":foo = 'foo'" which already works. So it's mostly a documentation issue.
if Stipple is used, from Stipple itself, specialize the Renderer.Html elements API to be compatible with the Stipple API so that all the elements work the same way.

Makes sense?

Actually on more thought, GenieVue.jl might be the best approach. It can be a separate plugin that extends the Genie API with Vue support - and can be used by Genie users to build Vue apps without Stipple. And Stipple would use it as a dependency.
Thoughts?
This also sets up the foundation for other GenieReact.jl GenieAngular.jl and others.
Thoughts?

@essenciary I think we have addressed all of the issues and we can close this...

Yup!


Deprecated warning on React 16.9.0-alpha.0

Next warning appeared:
Warning: componentWillMount is deprecated and will be removed in the next major version. Use componentDidMount instead. As a temporary workaround, you can rename to UNSAFE_componentWillMount.

Update on this -  React 16.9 stable has been released and the warning appears as follows:


Recommend and use group-based, non-root controller interface access

The README says:

The wpa_supplicant daemon runs as root and requires processes that attach to its control interface to be root.

This appears to be untrue. wpa_supplicant's documentation says:

The control interface of wpa_supplicant can be configured to allow non-root user access (ctrl_interface_group in the configuration file). This makes it possible to run wpa_cli with a normal user account.

and it also has guidance on a supported privilege separation approach as well as the ability to use Linux capabilities, for the daemon.
It isn't within the scope of this package to document the latter two points in any detail beyond a mention. But, I might propose:

Recommending the group configuration for non-root controller interface access, and using it on packaged Nerves Systems by default. As the primary target usage, this could eliminate the special build step and the need to explain it, along with the somewhat anxiety-inducing security consideration so early in the documentation. Plus it seems dubious to produce a setuid binary by default—among other things, consider if nerves_wpa_supplicant were a transitive dependency pulled in by another package: the end user may be less aware of what they are buying into, and there's the unsettling/bewildering experience of being prompted for a sudo password when they mix compile.
Changing the wording that "The wpa_supplicant daemon runs as root"—this might be true on current Nerves Systems, but it could vary by distribution. Given that the controller interface is the salient concern, it seems that this mention could be omitted entirely.

Considerations for non-Nerves Users
The package is potentially useful to people beyond Nerves users, I assume that's intended and desirable to maintain. They (as well as Nerves users building custom systems) do need to know that root access is potentially needed by default on their target environment's wpa_supplicant setup, and informed about the option/recommendation to enable the group setting. But this could be relegated to a less prominent position in the docs than the current build stage details, a "special cases" or FAQ section where it's less of a speed bump.
If the package build no longer makes wpa_ex setuid root, even optionally, a case could be made that it's necessary to document how to do it oneself if they don't wish to or cannot enable the group access setting in their environment. That would be kind of hairy to explain, and a step needing to be automated for every release. Honestly though, I don't believe that any ops team would willfully choose to use a setuid root binary when a lesser-privileged group can be used instead with a one-line config change. I would not even document a setuid approach, unless someone ever actually asked for it.
Whether it comes to group access setting or a setuid root binary, this is ultimately an ops matter and decision, not an application packaging one, IMO.

By the way, I haven't made it through how Buildroot works in-depth yet, but—if you agree with this proposal—if someone can nudge me in the direction of how I would customize the wpa_supplicant configuration in the system builds, I can take a stab at a pull request and updating docs accordingly.

I'm actually quite happy you brought this up. I'm fine with changing the wording, since the use of setuid always bothered me. I haven't thought much about the non-Nerves cases, though. I only use the non-Nerves case to debug this package, so while I don't care for setuid, I've learned to live with it. If you have instructions for what people should do to run locally, I'd definitely merge them (and take out the call to chmod the binary).
As for Nerves and Buildroot, the wpa_supplicant gets started when it's needed. For example, nerves_interim_wifi creates the configuration file dynamically at https://github.com/nerves-project/nerves_interim_wifi/blob/master/lib/interim_wifi/wifi_manager.ex#L285. Adding more configuration there would be straighforward.
However, before you look into this too much, everything in Nerves runs as root. As awful as this sounds, I'd categorize this as representing the current state of embedded systems rather than where we'd like Nerves to end up. It would be very easy for me to change erlinit so that it launches the Erlang VM as a normal user. (That code doesn't exist yet, but I'd write it if you're interested.) The big problem is what do you do after that's been done. That change will cause all of the hardware access libraries (elixir_ale, nerves_uart, etc., and some people write to Linux's /sys/class interfaces directly in Elixir) to be updated to get privilege somehow. Once that's done, I'm unsure whether running as non-root would be much different than running as root on these systems. However, if you tell me otherwise and that this is a solved problem, I'd completely believe you and implore your help. If we can do something better than traditional embedded in this area, I think it would be a big deal.

FYI: I added the ability for erlinit to drop the privilege of the Erlang VM (https://github.com/nerves-project/erlinit/commit/9acb6baa7c58cd9aceec188a92d1d8fca81a9a02). Regardless of whether you choose to doing anything with it, I like the idea of making it available for experimentation. If you get a chance, could you take a quick review before I merge it into master? I only set the gid and uid. If there are other things to set, then could you let me know? Thanks!

However, before you look into this too much, everything in Nerves runs as root. As awful as this sounds, I'd categorize this as representing the current state of embedded systems rather than where we'd like Nerves to end up. It would be very easy for me to change erlinit so that it launches the Erlang VM as a normal user.

This did cross my mind, and a read-only filesystem in Nerves also makes it a bit less scary. It would be nice if Nerves can eventually do better in this area especially since we're now in an era of devices running a general-purpose OS like Linux, and—although it might be a bad idea—it's not too hard to imagine systems being deployed on storage media that's more easily (re)writable than ROM chips, onboard eMMC, etc.
All of the other hardware access that you bring up is a good point, there would be a lot of trickle-down that might quickly become annoying for prototyping, hobby use, and instant-win experience for new users just trying things out. It seems like the 80% cases should be totally achievable with some judiciously applied common good practices being made defaults in Nerves systems, but I'll have to give this a lot more thought. The status quo probably does make for somewhat of an uphill battle.
This is hobby territory for me at this point so I might not be able to give it a ton of priority, but I am interested in getting more acquainted with Buildroot and how Nerves extends it and facilitates making changes to the the base systems, so that's further motivation for digging in with some purpose. It's beside the point, but another of my goals there is running pure Erlang apps—I know that was originally the focus before a shift to Elixir so I'm curious if the path is still fairly easy and just needs some documentation and perhaps cached system builds to make it simple even for new users. Maybe a rebar3 plugin can do some things similar to the Mix integration, and perhaps I can try to get the https://github.com/nerves-project/nerves-demo project running again and ask questions along the way. I'll drop in Slack for that when time permits.
Thanks for the super quick response with the uid/gid support in erlinit! That will definitely make it easier to experiment, see where frustrations start cropping up with hardware, and try to alleviate them without full root.

Regarding pure Erlang apps, if you're on Linux, the old build mechanisms still work for Erlang. I doubt that I'll remove them, since they come in really convenient at times. The basic idea is to build your system image, source a nerves-env.sh script to setup the environment, and then go to your project and run rebar or make. The mix integration handles a lot automatically and downloads prebuilt system and toolchain images. The main threat to pure Erlang support is bit rot, but we'll try our best to help out on the slack channel. If I had more time, I'd try to keep Erlang and LFE actively supported. Hopefully at some point we can find some help on this.


Run lambda from ECR image

I've been able to launch my lambda. I created and update it using jar file straightforwardly.
My jar file is generated at: ./target/frontoffice-apigateway-0.0.1-SNAPSHOT-aws.jar.
However, I need to change the way I uploading code.
Here my Containerfile:
FROM public.ecr.aws/lambda/java:21

# Copy function code and runtime dependencies from Maven layout
COPY ./target/frontoffice-apigateway-0.0.1-SNAPSHOT-aws.jar ${LAMBDA_TASK_ROOT}

# Set the CMD to your handler (could also be done as a parameter override outside of the Dockerfile)
CMD [ "org.springframework.cloud.function.adapter.aws.FunctionInvoker::handleRequest"]

And it's succesfully pushed on ECR repository.
I've created a new lambda attaching my recently pushed image, but I'm getting when it starts:
{
  "errorMessage": "Class not found: org.springframework.cloud.function.adapter.aws.FunctionInvoker",
  "errorType": "java.lang.ClassNotFoundException"
}

I've also played creating a new lambda attaching straightforwardly the jar file using aws console and code runs.
Any ideas?

This is not related to s-c-function. This question is more related to AWS, and its infrastructure. In other words there is nothing in s-c-function code that can address your question, so i'll close the issue


#1878 Add languages item to nav bar

What are the relevant GitHub issues?
resolves #1878
What does this pull request do?
Adds new item in the primary navbar linking to /languages.
How should this be manually tested?
Open home page and find Languages between Search and About in the navbar. Resize the browser and check that the navbar is still usable

I noticed this while on it, maybe

I noticed this while on it, maybe


[cleanup][metadatastore] cleanup deprecated method of metadata store etcd

Main Issue: #xyz

PIP: #xyz

Motivation
Use isPrefix insteadof deprecated method of withPrefix.

Modifications

Verifying this change

[x] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

/pulsarbot rerun-failure-checks

Failed CI to upload to codecov
[2023-10-11T04:31:04.218Z] ['info'] Pinging Codecov: https://codecov.io/upload/v4?package=github-action-3.1.4-uploader-0.6.3&token=*******&branch=cleanup_etcd_deprecated&build=6477302571&build_url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Factions%2Fruns%2F6477302571&commit=382319cdf725f045c90e27909052e0383c0f3876&job=Pulsar+CI+Flaky&pr=21253&service=github-actions&slug=apache%2Fpulsar&name=&tag=&flags=unittests&parent=
[2023-10-11T04:31:04.218Z] ['verbose'] Passed token was 0 characters long
[2023-10-11T04:31:04.218Z] ['verbose'] https://codecov.io/upload/v4?package=github-action-3.1.4-uploader-0.6.3&branch=cleanup_etcd_deprecated&build=6477302571&build_url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Factions%2Fruns%2F6477302571&commit=382319cdf725f045c90e27909052e0383c0f3876&job=Pulsar+CI+Flaky&pr=21253&service=github-actions&slug=apache%2Fpulsar&name=&tag=&flags=unittests&parent=
        Content-Type: 'text/plain'
        Content-Encoding: 'gzip'
        X-Reduced-Redundancy: 'false'
[2023-10-11T04:31:04.439Z] ['error'] There was an error running the uploader: Error uploading to [https://codecov.io:](https://codecov.io/) Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}
[2023-10-11T04:31:04.440Z] ['verbose'] The error stack is: Error: Error uploading to [https://codecov.io:](https://codecov.io/) Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}
    at main (/snapshot/repo/dist/src/index.js)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[2023-10-11T04:31:04.440Z] ['verbose'] End of uploader: 1396 milliseconds
Error: Codecov: Failed to properly upload: The process '/home/runner/work/_actions/codecov/codecov-action/v3/dist/codecov' failed with exit code 255
Run sleep 60
Run codecov/codecov-action@v3
{
  execArgs: [
    '-n',
    '',
    '-Q',
    'github-action-3.1.4',
    '-Z',
    '-F',
    'unittests',
    '-C',
    '382319cdf725f045c90e27909052e0383c0f3876',
    '-v'
  ]
}
==> linux OS detected

Codecov Report

Merging #21253 (a94dcbf) into master (f25b082) will increase coverage by 38.90%.
Report is 6 commits behind head on master.
The diff coverage is 100.00%.

Additional details and impacted files

@@              Coverage Diff              @@
##             master   #21253       +/-   ##
=============================================
+ Coverage     34.49%   73.39%   +38.90%
- Complexity    12116    32764    +20648
=============================================
  Files          1716     1893      +177
  Lines        131152   140754     +9602
  Branches      14327    15503     +1176
=============================================
+ Hits          45236   103307    +58071
+ Misses        79828    29354    -50474
- Partials       6088     8093     +2005

Flag
Coverage Δ

inttests
24.10% <27.27%> (?)

systests
24.70% <18.18%> (-0.03%)
:arrow_down:

unittests
72.69% <100.00%> (+40.90%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

...che/bookkeeper/mledger/impl/ManagedLedgerImpl.java
80.78% <100.00%> (+34.60%)
:arrow_up:

...org/apache/pulsar/broker/ServiceConfiguration.java
99.38% <100.00%> (+1.32%)
:arrow_up:

...er/service/persistent/GeoPersistentReplicator.java
67.00% <100.00%> (+29.00%)
:arrow_up:

...rg/apache/pulsar/compaction/TwoPhaseCompactor.java
78.15% <100.00%> (+10.08%)
:arrow_up:

...apache/pulsar/metadata/impl/EtcdMetadataStore.java
81.01% <100.00%> (+80.59%)
:arrow_up:

... and 1475 files with indirect coverage changes


Create Private-Audience-documentation.md

don't merge this, the file is work in progress

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

@marmuc680 I'll send you an email about GitHub account setup and working in GitHub as Microsoft-internal contributor. Thanks!

#hold-off per contributor

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


Filter button "All" to select/deselect all filters

It is quite annoying clicking through all the buttons to make all types of tests (in)visible.

IMO we don't need this in Allure. This button helps to save some clicks only in 200 cases out of 1022.


[Bug]: Unusable for installable projects whose other dependencies also define a check target

Describe the issue
I am working on a project that depends on LLVM. LLVM uses installable targets (using CMake's install command), which forces my project to do the same. If I want to use abseil-cpp or any project that depends on it, I thus need to set ABSL_ENABLE_INSTALL=ON.
Furthermore, LLVM also defines a check target in its CMake files. This clashes with the check target of Abseil.
This only happens with ABSL_ENABLE_INSTALL=ON. Otherwise, the target names are prefixed with absl_, see the definition of absl_cc_library.
Steps to reproduce the problem

What version of Abseil are you using?
Any version from about four years ago until today.
What operating system and version are you using?
Any.
What compiler and version are you using?
Any.
What build system are you using?
Any version of CMake older than 2.6.0.
Additional context
Of course, the clash is also due to to LLVM using a non-prefixed target name. However, I'd argue that this doesn't absolve abseil-cpp from being well-behaved and prefix it's target names as an effort to keep them unique no matter what other project it is used with.

Steps to reproduce the problem is not filled in. Please do so.
You also say that this is relevant to any version of CMake older than 2.6.0. I just want to confirm that this is correct as our minimum supported CMake version is 3.13. Does this work still not work with a supported CMake version?

Clone this project to abseil-cpp and create CMakeLists.txt with the following content:
add_custom_target(check)
add_subdirectory(abseil-cpp)

Create an empty folder, cd into the folder, and run cmake .. -DABSL_ENABLE_INSTALL=ON, observe the following error:
CMake Error at abseil-cpp/CMake/AbseilHelpers.cmake:317 (add_library):
  add_library cannot create target "check" because another target with the
  same name already exists.  The existing target is a custom target created
  in source directory
  "/.../".
  See documentation for policy CMP0002 for more details.
Call Stack (most recent call first):
  abseil-cpp/absl/log/CMakeLists.txt:424 (absl_cc_library)

Stumbled upon this problem too, but this time when trying to use crc32c along with abseil.
When ABSL_ENABLE_INSTALL is set to ON, it creates a library named "crc32c" which introduces conflicts.
CMake Error at build/_deps/absl-src/CMake/AbseilHelpers.cmake:251 (add_library):
  add_library cannot create target "crc32c" because another target with the
  same name already exists.  The existing target is a static library created
  in source directory
  "/build/_deps/crc32c-src".  See
  documentation for policy CMP0002 for more details.
Call Stack (most recent call first):
  build/_deps/absl-src/absl/crc/CMakeLists.txt:54 (absl_cc_library)


Feat/find dart files from directory

Motivation
I recently refactored a code base that has localization and it's now becoming larger. Now, the main localization.dart file has become a monolith that contains all localized words that have different context. So I decided to split them by feature in mixins. However, both extract_to_arb and generate_from_arb does not support generating arb file from directory containing all the .dart files.
Goal
This PR gives this library the ability to find all dart files from directories given by user.

Hey, sorry for the delay. Look like interesting addition, could you add some tests for the uses case you added?


C++ Client Work

Preview3

[ ] Fix tests
[ ] Review configuration options
[ ] Add new tests (probably mostly around protocol)
[ ] Remove unrelated tests
[ ] Remove remnants of classic ASP.NET protocol
[ ] CI build integration
[ ] Review public API
[ ] How do we ship? (From source, etc.)
[ ] Start writing docs
[ ] Resolve "TODO" comments

Preview4

[ ] Add different protocol support (json is fairly hard-coded currently)
[ ] Cross-platform builds?
[ ] Which C++ version?
[ ] Decide on WebSockets and HTTP libraries (currently uses CppRestSdk)
[ ] Decide on tasks/futures (currently uses pplx::Task from CppRestSdk)
[ ] Add SignalR Service support, mainly add redirect and auth from handshake response

Possible feature work:

[ ] Client-Side pinging
[ ] Add Streaming support (both sides)
[ ] Add MessagePack
[ ] Other transports, LongPolling and ServerSentEvents

A few questions regarding c++ signalr client:

how different is the old signalr from asp.net core signalr? Where can I read to understand these differences and why these two are incompatible?
signalr uses cpprestsdk, which isn't a tiny lib. In our case we cannot use it because of the binary size. Would that be easy to make a lean version of signalr that does only websockets (without pure http fallback)?

When linked statically, the final binary is small, meaning I'm using only a tiny bit of cpprestsdk. But there were a lot of trials and errors to finally got everything compiled and linked. Preferably there will be a small signalrclient.lib and signalrclient.dll that doesn't require any other DLLs at run-time.

I'll check size impact of signalr, but we weren't able to ship it due to app store size limits (we are a large 100mb-range app)

Speaking of using cpprestsdk, I had started a conversation last year regarding other library options back on aspnet/signalr#2510. It looks like this issue had some other good tidbits of feedback that might still be valuable, as well.
I am still interested in any potential API discussions too.

Just following up on this as I see the C++ client is being actively worked on. /cc @anurse since I originally chatted with you. Also, /cc @BrennanConroy as I believe you are the one actively working on it and might have some insight into the design process. Thanks guys!

Hey @steji113, we're currently working on cleaning up the API to not use any external libraries publicly. The big one right now is pplx::task<T> and we're looking at doing a callback model. For example invoke might look like connection.invoke("MethodName", args, [](some_param) { // process params });

Anybody know what is the roadmap for this library?

We are planning on shipping alongside the 3.0 release.

We need to break this up into smaller issues ASAP, I'll check in with you @BrennanConroy.

@BrennanConroy The ASPNET Core 3.0 release is planned to end of this year but I would like to start test something. Can I using this project https://github.com/aspnet/SignalR-Client-Cpp to test?

Our priorities have changed and I can't guarantee that this will ship in the 3.0 release.
https://github.com/aspnet/SignalR-Client-Cpp is where we will be doing work on the C++ client. Feel free to test it out and file issues in this repo.

Does signalr support a hub proxy? I can't see the hub proxy class

No, the Hub Proxy mechanism is no longer present in the SignalR client. Instead you call .InvokeAsync("NameOfMethod", arg1, arg2) on the HubConnection. By the way, this issue is tracking our work on a C++ client, I'd suggest posting a separate issue if you have a general SignalR question, or asking on Stack Overflow.


Help collecting accessibility support data

Problem statement
The non-profit OWD collective currently contributes heavily to mdn/browser-compat-data. The BCD project collects compatibility data for browsers and some runtimes like nodejs and deno. However, the BCD project doesn't collect support data for accessibility necessarily (see https://github.com/mdn/browser-compat-data#what-isnt-tracked)
Several issues were brought up about accessibility support recently, though (non-exhaustive list)

https://github.com/mdn/browser-compat-data/issues/21847
https://github.com/mdn/browser-compat-data/issues/21648
https://github.com/mdn/browser-compat-data/issues/21663

The web-features project ("baseline"), doesn't yet take accessibility support info into account due to missing data. See https://github.com/web-platform-dx/web-features/issues/498 and https://github.com/web-platform-dx/web-features/pull/519.
Web developers are not informed properly about a11y support in browsers and in assistive technologies.
Proposed solutions
There are probably a few things we could do. Some initial thoughts:

We sometimes use partial_implementation and note in BCD to say that some aspects of a feature don't work. See "
 in select" as an example for this. However, there are no BCD data guidelines about these partial support statements. We could propose to create a BCD data guideline, so that BCD can talk about at least some of the a11y support issues in a consistent way.

We could start contributing to https://github.com/accessibilitysupported/a11ysupport.io (licensed CC BY 4.0)
From https://a11ysupport.io/faq:

This is a community-driven website that aims to help inform developers about what code features (roles, states, properties, elements, etc.) are supported by assistive technologies, and what that support looks like.
It might take a bit to get familiar with this data and with testing AT. https://a11ysupport.io/contribute has some pointers.

We could look into https://github.com/web-platform-tests/interop-accessibility/ which is about improving the interop for accessibility and maybe that group has more research that ought to be surfaced in data and in documentation.

Finally, we should probably not only figure out how to curate and record good accessibility support but also figure out the data quality or other requirements needed to be met so that MDN/Caniuse/Baseline/others would consider the data good enough to be displayed and shown to web developers (prominently).

Task list
As written, the problem statement and the work on the proposed solutions is really, really large and high effort. There is a lot to unpack here. I think the OWD collective currently won't be able to do all of this. Maybe some allies in the a11y community could help. Let me try to make up a task list (this will probably change if we get into this work):

[ ]  Research how we currently record a11y support in BCD (
 in select is just one example) and use that research to propose a data guideline for BCD to talk about a11y support consistently.
[ ] Figure out if we could contribute to https://github.com/accessibilitysupported/a11ysupport.io. Probably manually for now, maybe later we could investigate if our compat data automation project (https://github.com/openwebdocs/mdn-bcd-collector) could be utilized as well, or if there are learnings from it that a11ysupport.io could use.
[ ] Talk to https://github.com/web-platform-tests/interop-accessibility/ to see if the group has data that we should record as a11y support data
[ ] Look for help/contributors in the a11y community to help with this support data collection.
[ ] Once more familiar, present all our research to the WebDX group to reconsider inclusion of a11y support data in baseline.

Priority assessment

Effort: XL (probably several months of work)
Dependencies: https://github.com/accessibilitysupported/a11ysupport.io is pretty new to me and I think to anyone from OWD. So, maybe this project depends a bit on how well we can contribute to a11ysupprt.
Community enablement: Hopefully there are a11y community who would help or at least advise us with this project, so I would say yes, we will hopefully be able to enable some folks to join us on this work.
Momentum: The issue on the WebDX repo had 30 upvotes. The a11y interop project seems pretty new, too.
Enabling learners: n/a
Enabling professionals: n/a
Underrepresented topics / Ethical web: Yes, pretty much!
Operational necessities: n/a
Addressing needs of the web industry: I think so. I have no other data/surveys that backs up the (high) need of this project, but we could try to get some more info from a11ysupport.io or we could run a survey on our own.

In order for this project to happen, please consider donating to OWD on https://opencollective.com/open-web-docs.
For more information on sponsorship and membership tiers, see https://openwebdocs.org/membership/
More information is available at https://openwebdocs.org/.
For questions, please reach out to<EMAIL_ADDRESS>

Via @dontcallmedom: https://aria-at.w3.org/reports

Via Steve Faulkner: https://freedomscientific.github.io/standards-support/html.html