Update ZAP to 2.15

Use ZAP 2.15 (SNAPSHOT).

@kingthorin @ricekot can one of you approve this? The build failure is expected..


CMSIS-pack conditions : is the spec clear enough ?

In the spec I can see:
https://www.keil.com/pack/doc/CMSIS/Pack/html/pdsc_conditions_pg.html#element_condition
So:

Cclass*
Specifies a component class name. Predefined values can be used as listed in the table Component Classes.
CclassType
optional

Cgroup*
Specifies a software Component Group. Predefined values can be used as listed in the table Component Groups.
CgroupType
optional

But if I write conditions like:

   <condition id="Porting">
       <description>Port SBSFU on a STM32</description>
       <require Cgroup="Porting Layer*"/>
       <require Cgroup="Entry*"/>
       <require Cgroup="Startup*"/>
       <require Cgroup="Memory Partitioning"/>
   </condition>

Keil microvision complains:
fred-r.STM32_Bootloader.0.0.1-PoC0: condition 'Porting': error #502: error(s) in condition definition:
'require Porting Layer*': Cclass or Cgroup attibute is missing in expression
'require Entry*': Cclass or Cgroup attibute is missing in expression
'require Startup*': Cclass or Cgroup attibute is missing in expression
'require Memory Partitioning': Cclass or Cgroup attibute is missing in expression
To fix it:

   <condition id="Porting">
       <description>Port SBSFU on a STM32</description>
       <require Cclass="Security" Cgroup="Porting Layer*"/>
       <require Cclass="Security" Cgroup="Entry*"/>
       <require Cclass="Security" Cgroup="Startup*"/>
       <require Cclass="Security" Cgroup="Memory Partitioning"/>
   </condition>

Is there a point in the spec saying that Cclass is mandatory in addition to Cgroup ?
I understand that it probably makes no sense to provide only a Cgroup but I thought this was allowed.

You are correct, the specification describes the individual attributes but does not describe any limitations nor good use case examples. At the same time I think that this is an MDK uVision implementation specific error condition trying to give some user guidance. The fact that a user does not specify a class of a component increases the likelihood for the system to suggest a component which does not actually satisfy the requirement of the component.

Documentation updated. See version 1.7.32 (or higher)
https://open-cmsis-pack.github.io/Open-CMSIS-Pack-Spec/main/html/pdsc_conditions_pg.html#element_accept


Extend default cordova plugins

Wallet app doesnt work on this branch. It does work on master.

Should be fixed now


Update metrics-core, metrics-json to 4.0.4

Updates

io.dropwizard.metrics:metrics-core
io.dropwizard.metrics:metrics-json

from 4.0.3 to 4.0.4.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a nice day!

Superceded by #2329


Merge pull request #1 from pentaho/master

update from origin

update from origin

Hello, This is an automated comment from our build system. Since this pull request originated from a user  not in the Pentaho organization, we will not proceed  with automatic validation of the pull request.  However, rest assured that it will be reviewed manually as soon  as we get the chance. Thanks for your contribution!


It block all artisan commands in docker

When I try to use it inside Docker and run Artisan commands, it always throws this exception:
`SQLSTATE[42P01]: Undefined table: 7 ERROR:  relation "pages" does not exist
LINE 1: select * from "pages"
^ (Connection: pgsql, SQL: select * from "pages")
at vendor/laravel/framework/src/Illuminate/Database/Connection.php:822
818▕                     $this->getName(), $query, $this->prepareBindings($bindings), $e
819▕                 );
820▕             }
821▕
➜ 822▕             throw new QueryException(
823▕                 $this->getName(), $query, $this->prepareBindings($bindings), $e
824▕             );
825▕         }
826▕     }
1   [internal]:0
Illuminate\Foundation\Application::Illuminate\Foundation{closure}(Object(Z3d0X\FilamentFabricator\FilamentFabricatorServiceProvider))
+12 vendor frames`
this error happened because of the codes inside bootingPackage()

it seems there is no support for this package anymore :(

@EsiNakesy did you run the migrations? It should be done via php artisan filament-fabricator:install if you followed the documentation properly.

@ksimenic  it's completly diffrent topic after you installed fabricator, if you try to move it from dev to prod since it considers that the page table is already exist you can not run migration or any other artisan command so when docker try to build and run the services you will get an error that I mentioned to replicate the issue.

install fabricator
remove the page table manually (also from migration table)
try to run migration to recreate the page table

Could you share complete stacktrace / which line in FilamentFabricatorServiceProvider is throwing the error?

When I try to use it inside Docker and run Artisan commands, it always throws this exception: `SQLSTATE[42P01]: Undefined table: 7 ERROR: relation "pages" does not exist LINE 1: select * from "pages" ^ (Connection: pgsql, SQL: select * from "pages")
at vendor/laravel/framework/src/Illuminate/Database/Connection.php:822 818▕ $this->getName(), $query, $this->prepareBindings($bindings), $e 819▕ ); 820▕ } 821▕ ➜ 822▕ throw new QueryException( 823▕ $this->getName(), $query, $this->prepareBindings($bindings), $e 824▕ ); 825▕ } 826▕ }
1 [internal]:0 Illuminate\Foundation\Application::Illuminate\Foundation{closure}(Object(Z3d0X\FilamentFabricator\FilamentFabricatorServiceProvider)) +12 vendor frames` this error happened because of the codes inside bootingPackage()

I'm running into this same issue, my automated testing github action throws this same error while resolving the install step:
> Run php artisan key:generate

   Illuminate\Database\QueryException

  SQLSTATE[0[8](https://github.com/brumelance/brumelance/actions/runs/12439679760/job/34733881339#step:7:9)006] [7] could not translate host name "pgsql" to address: Temporary failure in name resolution (Connection: pgsql, SQL: select * from "pages")

Likewise, running the same testing locally gives me:
SQLSTATE[42P01]: Undefined table: 7 ERROR:  relation "pages" does not exist
LINE 1: select * from "pages"
                      ^ (Connection: pgsql, SQL: select * from "pages")

See pull request #160 for a fix. Idk why this is still not merged or fixed in another way.
Wrap this if-statement arround the code in the bootingPackage function inside the FilamentFabricatorServiceProvider
if (! $this->app->runningInConsole()) {
}

Does #160 being merged solve your issue @ferdbold ?

It actually wasn't, I'm still running 2.2.2, but it did give me insight into solving the actual issue. In my case I had to guard calls to Page::all() I had in my own service providers during boot() with the same check


Param check

The result is for COB4 simulation. For visual purpose, not showing the "Additional Nodes" and "Missing Nodes" below.
level: 2
name: "parameters_node"
message: "Wrong param configuration"
hardware_id: ''
values:
  -
    key: "battery_monitor/enable_light"
    value: "false"
  -
    key: "collision_velocity_filter/anti_collision_costmap/resolution"
    value: "0.05"
  -
    key: "diagnostic_aggregator/analyzers/computers/analyzers/b1/contains"
    value: "['b1 CPU Info', 'b1 CPU Usage', 'b1 HD Usage', 'b1 Memory Usage']"
  -
    key: "light_base/sim_enabled"
    value: "true"
  -
    key: "joint_state_publisher/source_list"
    value: "['/base/joint_states']"
  -
    key: "emergency_stop_monitor/enable_sound"
    value: "false"
  -
    key: "collision_velocity_filter/anti_collision_costmap/plugins"
    value: "[[['type', 'costmap_2d::ObstacleLayer']], [['name', 'obstacle_layer_0']]]"
  -
    key: "use_sim_time"
    value: "true"
  -
    key: "robot_description"
    value: "..."
  -
    key: "collision_velocity_filter/anti_collision_costmap/global_frame"
    value: "base_footprint"

@ipa-nhg @chcorbato: not sure if you wanted to club all wrong parameters in a node in a single DiagnosticStatus message

@ipa-hsd  Great job, thanks a lot :tada:
In case we use minimal "desired"_model as input, it should be ok if we club all the wrong parameters within a single Diagnostics message, probably the desired system will only ask for the analysis of a single node/component.

However, is it too complex to implement this software to support different configurations? For example using a parameter that set different analysis modes, i.e:

critical: all the errors including warnings because of additional nodes/parameters..
minimal: missed nodes and parameters and check values
minimal_verbose: missed nodes and parameters and check values, single diagnostic status per wrong parameter

If this is super complex or this is useless for your use cases, just ignore this comment!

@ipa-nhg @chcorbato: not sure if you wanted to club all wrong parameters in a node in a single DiagnosticStatus message

clubbing all the params for a node in a message is perfectly ok with me.

@ipa-nhg said:

However, is it too complex to implement this software to support different configurations? For example using a parameter that set different analysis modes

I will handle this in a new PR. I will merge this PR.


Split unfiltered AOV filter images

Move the nearest distance channel to its own image.
Avoids having to skip channels when sending the image to blender in the stdout tile callback.

Are you sure all clear_image() methods are up-to-date now that there's an extra image to clear? It's hard to check in GitHub.

Image clearing is up to date.
Fixed and rebased.


Icon from Alert component added in page are hidden when notification is launched

The following steps can be followed to replicate the issue.

add <x-bladewind::alert show_close_icon="false" show_icon="true"> in page

add <x-bladewind::notification />  in page

display the page in your browser

in browser console try showNotification(   		"test",   		"test",   	);

icon from <x-bladewind::alert show_close_icon="false" show_icon="true"> disappears

it seems that this comes from usage of modal-icon in Alert component, and showNotification remove all icon of this type.

Thanks @bhenscamp for raising this. Will fix and release an update shortly.

@bhenscamp this is fixed in 2.2.8


Create and Transfer SPL token in same transaction

Is there any way to create and transfer SPL token to an address before the token address is created? At the moment, I have to split the transaction up into 2, then wait awhile until the associated account is finished, then poll
#### create the token account
create_tx = Transaction()
create_tx.add(create_associated_token_account(
    payer=PublicKey(self.wallet_keypair.public_key),
    owner=PublicKey(address),
    mint=PublicKey(self.coin_addr_dict[currency])
))
create_acc_tx = self.solana_client.send_transaction(create_tx,
    self.wallet_keypair,
    opts=TxOpts(skip_confirmation=False, preflight_commitment=Confirmed))['result'] # unsure if getting the confirmation works asyncly

#### find the associated token account by looking at the logs
tx_recip = requests.get(f"https://api.solscan.io/transaction?tx={create_acc_tx}&cluster=").json()
#### get it again. the return looks to be in the 2nd s lot
recipient_associated_token_account = tx_recip['inputAccount'][1]['account']

#### send the transfer transaction
tx = Transaction()
tx.add(transfer_checked(
TransferCheckedParams(
    program_id=TOKEN_PROGRAM_ID,
    source=my_associated_token_account, # source account (? does it need to be MY account for the token?)
    mint = PublicKey(self.coin_addr_dict[currency]), # token ID / mint
    dest = PublicKey(recipient_associated_token_account), # destimation account ?
    owner = PublicKey(self.wallet_keypair.public_key), # me
    amount=int(amount * 10**token_decimals),
    decimals=token_decimals, #TODO
    signers=[] # multisig only
)))

result = self.solana_client.send_transaction(tx, self.wallet_keypair)

Ideally, I'd be able to just do one send_transaction without needing to poll for the transaction to finish. With this code, the 2nd transaction (the transfer) sometimes fails with the error  'Transaction simulation failed: Error processing Instruction 0: invalid account data for instruction' (probably because the account hasn't propogated yet

you should combine the two instructions into one transaction!

example of how to do this?

Transaction instructions are taken in a list (and i think executed in that order) so you can do something like this very basic example:
[
    Create_token,
    Create_token_account(recipient),
    Transfer(
        to=token_account
        from=keypair
     )
]


proposal: affected/package: Cut a latest 1.## release with every new minor release

Currently 1.21 was just released as 1.21.0 .
I'm unable to download the 1.21 release via jenkins unless I specify 1.21.0
Once we move to a new minor release, we should be able to specify that and not have to wait until a patch version (1.21.1) to be able to specify 1.21
Works:
curl https://dl.google.com/go/go1.21.0.linux-amd64.tar.gz --output go1.21.0.linux-amd64.tar.gz
Doesn't Work:
curl https://dl.google.com/go/go1.21.linux-amd64.tar.gz --output go1.21.linux-amd64.tar.gz

This goes against our policy of providing stable / explicit versioning, both for the go distribution and dependencies in general.
You can parse the latest version out of the API endpoint https://go.dev/dl/?mode=json

Why can I download 1.20 without issue then?
curl https://dl.google.com/go/go1.20.linux-amd64.tar.gz --output go1.20.linux-amd64.tar.gz

I see, I feel like this could possibly break teams build processes and cause more overhead.


Porting Microsoft.Build to .NET Core

Progress towards getting Microsoft.Build to compile for .NET Core

Hi @dsplaisted, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

LGTM


Update the game over message

Update the game over message so people know how to play again!

Update the game over message

Thank you for playing


wheels musllinux

Hi. You have recently created wheels for aarch64 platform. Especially, for manylinux  systems. But I'm working with Home Assistant OS and it is musllinux system. So, all generated wheels are unsuitable for this system.
I really need this wheels,because otherwise my HA integrations doesn't work property. I've decided to create github action for it. Also, I've integrated this action in your github action for PyPi.Wheels already tested on RPi4 with HomeAssistant OS and everything is working.
Please, add this wheels to Pypi.
If any questions, fill free to ask.

Also, I will add the same wheels for two other your libraries: py-bip39-bindings and py-ed25519-bindings.
Now py-bip39-bindings is being passed last tests.
In py-ed25519-bindings library there is an issue


Missing Exception information

In your text it says:
Asynchronously returns the only element of a sequence, and throws an exception if there is not exactly one element in the sequence.
But you don't list them.
I assume they are equal to the exceptions listed in Single + Task Cancellation...
https://docs.microsoft.com/en-us/dotnet/api/system.linq.enumerable.single?view=netframework-4.8

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

ID: d3b7deb0-a592-b6dc-1564-fba73a4dcb4c
Version Independent ID: 1836b7d9-419e-d8a4-51ff-09f504a56462
Content: EntityFrameworkQueryableExtensions.SingleAsync Method (Microsoft.EntityFrameworkCore)
Content Source: dotnet/xml/Microsoft.EntityFrameworkCore/EntityFrameworkQueryableExtensions.xml
Product: ef-core-api
GitHub Login: @dotnet-bot
Microsoft Alias: divega

Duplicate of #17564


Add option to download network

This ticket is originally from: https://github.com/idekerlab/nbgwas_rest/issues/14
Add a link to let the user download the NDEx network used in the analysis.

I thought we were going to add a link to VIEW the analysis results on NDEx (which would have it's own download button). Why would I link them to the network they passed in?

Good question. Let me check with these guys.


rockspec vs bootstrap out of sync?

The README.md file says, Dependencies are listed in the dependencies entry of the file rockspec.conf.  but that doesn't list ldoc or specl, both of which turn out to be requirements when you run bootstrap.
karlp@cuth:~/src/luaposix (master)$ ./bootstrap
bootstrap:   error: Prerequisite LuaRock 'ldoc 1.4.2' not found. Please install it.
bootstrap:   error: Prerequisite LuaRock 'specl 14.1.0' not found. Please install it.
bootstrap:   error: Missing rocks:
<<< more snipped

Thanks for the report.  In a way you are right, because the README.md isn't really there to help luaposix developers bootstrap a release, but doesn't make that very clear.
Bootstrapping is a process you need to complete before configuring and building.  The README.md is written as if you have just downloaded an already bootstrapped release from the release branch or from github, both of which are already bootstrapped.
If you do want to bootstrap the whole thing yourself, then you will need Perl, Automake, Autoconf, GNU M4, and an installed and working ldoc and specl among others in addition to the tools you need to configure and build (bourne shell, make etc).  In order to get a working specl and ldoc, you will also need several other lua modules installed correctly.
Much easier than building all of this for yourself from scratch when you are not yet familiar with all of the tools involved is to preferably:
luarocks install luaposix
Otherwise, start from a release tarball which uses the familiar:
./configure
make
sudo make install
I plan to rewrite all the README files for the projects I maintain in the near future to make it clearer that we only plan to support the first, easiest method... and otherwise assume that you already know how to bootstrap and configure if you wish to build an unreleased luaposix for yourself or your customers.
HTH,
Gary

If only luarocks was easy/sane to use with multiple different lua versions :)  I did end up going that way, but it was rather unpleasant as well :)  I'm quite used to bootstrap/autogen/cruft when building from a source checkout rather than a tarball, but I had still expected the requirements to match up.  At least, thankfully, your bootstrap actually checks for the requirements it really does need, so it was clear what was needed, this was just a minor ticket to let you know that it could be more selfconsistent.  (You could also just drop the sentence saying to look at the rockspec, it will be used by rocks anyway, so no need to refer to it at all as a human?)


Added the update job to the post-merge suite for Origin

@stevekuznetsov

Will merge once 3.6 upgrade playbook is in


BUG : Navbar is not working properly

Though i try to navigate to different pages of the website, the navbar still stays in the home page itself
https://github.com/user-attachments/assets/d5ab3ba9-fd23-4337-9556-d15c22d2492d
I would like to work on this

Issue is already resolved


Flutter app is crashing on windows on customers machines

Steps to reproduce
The Flutter app built with Flutter 3.10.6, 3.10.5 or 3.10.1 for the Windows target is crashing at random places on some customer's machines. According to the crash dump the crash is happening somewhere in the flutter_windows.dll.
We were unable to reproduce issue in the dev environment (both debug and the same release app builds).
In any case we are looking for a guidance or tips how to get to the bottom of this.
Expected results
No crash
Actual results
Here is WinDbg output for a .dmp file from one of the crashes.
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1671

    Key  : Analysis.Elapsed.mSec
    Value: 2382

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 312

    Key  : Analysis.Init.Elapsed.mSec
    Value: 106402

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 107

    Key  : Failure.Bucket
    Value: NULL_POINTER_READ_c0000005_flutter_windows.dll!Unknown

    Key  : Failure.Hash
    Value: {50c90234-ea28-50e4-5966-c3a5b7786078}

    Key  : Timeline.Process.Start.DeltaSec
    Value: 19

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 10.0.19041.546

FILE_IN_CAB:  APP_CRASH.exe.15552.dmp

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

CONTEXT:  (.ecxr)
rax=00007ffd56831810 rbx=0000000000000000 rcx=0000000000000000
rdx=000000f605b7e990 rsi=000000f605b7e990 rdi=00000284fe6b04e0
rip=00007ffd5683181b rsp=000000f605b7e870 rbp=0000000000000000
 r8=000000000000000a  r9=0000028489dafb40 r10=0000028487292240
r11=000000f605b7e6a0 r12=000000000000000e r13=000000f605b7ea70
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
flutter_windows+0x181b:
00007ffd`5683181b 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffd5683181b (flutter_windows+0x000000000000181b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]:<PHONE_NUMBER>000000
   Parameter[1]:<PHONE_NUMBER>000000
Attempt to read from address<PHONE_NUMBER>000000

PROCESS_NAME:  APP_CRASH.exe

READ_ADDRESS:<PHONE_NUMBER>000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:<PHONE_NUMBER>000000

EXCEPTION_PARAMETER2:<PHONE_NUMBER>000000

IP_ON_HEAP:  ffffffff899af5e0
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

FRAME_ONE_INVALID: 1

STACK_TEXT:
000000f6`05b7e870 ffffffff`899af5e0     : 000046f3`bfcc777c 000000f6`05b7e9d8 00000284`fe6b04e0 00000284`87410300 : flutter_windows+0x181b
000000f6`05b7e878 000046f3`bfcc777c     : 000000f6`05b7e9d8 00000284`fe6b04e0 00000284`87410300 00007ffd`56831681 : 0xffffffff`899af5e0
000000f6`05b7e880 000000f6`05b7e9d8     : 00000284`fe6b04e0 00000284`87410300 00007ffd`56831681 00000000`00000000 : 0x000046f3`bfcc777c
000000f6`05b7e888 00000284`fe6b04e0     : 00000284`87410300 00007ffd`56831681 00000000`00000000 00000000`0000000f : 0x000000f6`05b7e9d8
000000f6`05b7e890 00000284`87410300     : 00007ffd`56831681 00000000`00000000 00000000`0000000f 000000f6`05b7eb01 : 0x00000284`fe6b04e0
000000f6`05b7e898 00007ffd`56831681     : 00000000`00000000 00000000`0000000f 000000f6`05b7eb01 000000f6`00000000 : 0x00000284`87410300
000000f6`05b7e8a0 00000000`00000000     : 00000000`0000000f 000000f6`05b7eb01 000000f6`00000000 00000000`87528be0 : flutter_windows+0x1681

STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_NAME:  flutter_windows+181b

MODULE_NAME: flutter_windows

IMAGE_NAME:  flutter_windows.dll

FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_flutter_windows.dll!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {50c90234-ea28-50e4-5966-c3a5b7786078}

Followup:     MachineOwner
---------

0:000> .ecxr
rax=00007ffd56831810 rbx=0000000000000000 rcx=0000000000000000
rdx=000000f605b7e990 rsi=000000f605b7e990 rdi=00000284fe6b04e0
rip=00007ffd5683181b rsp=000000f605b7e870 rbp=0000000000000000
 r8=000000000000000a  r9=0000028489dafb40 r10=0000028487292240
r11=000000f605b7e6a0 r12=000000000000000e r13=000000f605b7ea70
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
flutter_windows+0x181b:
00007ffd`5683181b 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
0:000> .exr -1
ExceptionAddress: 00007ffd5683181b (flutter_windows+0x000000000000181b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]:<PHONE_NUMBER>000000
   Parameter[1]:<PHONE_NUMBER>000000
Attempt to read from address<PHONE_NUMBER>000000

Code sample
We were unable to reproduce issue in a small isolated sample.
Screenshots or Video
The app is simply crashes at somewhat arbitrary places on some customer's machines.
Logs
There are no flutter logs available for these crashes of the released app.
Flutter Doctor output
Doctor output
>flutter doctor -v
[✓] Flutter (Channel stable, 3.10.6, on Microsoft Windows [Version 10.0.22621.1992], locale en-CA)
    • Flutter version 3.10.6 on channel stable at C:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (2 weeks ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✗] Chrome - develop for the web (Cannot find Chrome executable at .\Google\Chrome\Application\chrome.exe)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✓] Visual Studio - develop for Windows (Visual Studio Community 2022 17.6.5)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.6.33829.357
    • Windows 10 SDK version 10.0.22000.0

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2023.1.2
    • Flutter plugin version 74.0.4
    • Dart plugin version 231.9161.14

[✓] Connected device (2 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22621.1992]
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 114.0.1823.82

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 3 categories.

Hi @ekuleshov
Can you please collect affected Windows device info (OS version, percentage occurrence of the crash) and share it here?

Here is the info I was able to collect from a customer machine.
Please let me know if you need any additional details

Thanks, that may be helpful for further investigation.

Hello, thank you for reporting this crash. Could you load Flutter's symbols to add additional debugging information to the crash? You should be able to find the symbols at C:\flutter\bin\cache\artifacts\engine\windows-x64. If needed, here are instructions on how to load symbols in WinDBG:

https://learn.microsoft.com/windows-hardware/drivers/debugger/setting-symbol-and-source-paths-in-windbg#symbol-path
https://learn.microsoft.com/windows-hardware/drivers/debugger/ld--load-symbols-

How to load Flutter's symbols in Visual Studio...

Find your Flutter SDK path using the terminal: flutter doctor --verbose.
Let's say I have the following output:
PS C:\> flutter doctor --verbose
[✓] Flutter (Channel stable, 3.7.0, on Microsoft Windows [Version 10.0.22621.1105], locale en-US)
    • Flutter version 3.7.0 on channel stable at C:\Code\f\flutter
...

My Flutter SDK path is C:\Code\f\flutter.

Add Flutter's symbols path to Visual Studio's options

Open the Debugging options using DEBUG > Options....

Navigate to the Symbols pane and use the + button to add <Flutter SDK path>/bin/cache/artifacts/engine/windows-x64
as a symbol location:

Close the Options window

Load Flutter's symbols in Visual Studio

Open the Modules window using DEBUG > Windows > Modules (or Ctrl+Alt+U):

In the Modules window, right click the flutter_windows.dll item and select Load Symbols:

The engine's symbols should now be loaded:

For more information, see the How to debug the Flutter engine on Windows guide.

Hello, thank you for reporting this crash. Could you load Flutter's symbols to add additional debugging information to the crash? You should be able to find the symbols at C:\flutter\bin\cache\artifacts\engine\windows-x64. ...
Alternatively, here's how to load Flutter's symbols in Visual Studio...

Thank you for these instructions.
The WinDbg says these symbols are invalid, but I was able to load them in VS and after clicking on "Debug with native only" action in the .dmp viewer I see this stack trace.

@loic-sharma we were able to reproduce the same issue on more Windows 11 machines.
The app is built with Flutter 3.10.6 and when Windows built in Narrator is active the app is crashing at the same place as on the customer's machines. Also, it could be related that the customer's Windows machines may also have a touch screen HID device.
Below are the top two stack frames for the crash caught in the Visual Studio running Debug build of the app. It seems like node_delegate/win_delegate is null there.

With the Windows Narrator enabled the sample from a previously closed similar issue
127789 is crashing running on Flutter 3.10.6
import 'dart:async';
import 'dart:math';

import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatefulWidget {
  const MyApp({super.key});

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  final tc = TextEditingController(text: "old text");

  final fc = FocusNode();

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      home: Scaffold(
        body: Center(
          child: Column(
            children: [
              TextField(
                controller: tc,
                focusNode: fc,
              ),
              TextButton(
                onPressed: () {
                  Timer.periodic(const Duration(seconds: 1), (timer){
                    fc.requestFocus();
                    var randomInt = Random().nextInt(1000);
                    tc.text = "new $randomInt text";
                  });
                },
                child: const Text("test"),
              ),
            ],
          ),
        ),
      ),
    );
  }
}

@ekuleshov I could reproduce this crash on Flutter 3.10.6 but not on the latest stable version (3.13) or the latest master version. I suspect this may have been fixed by https://github.com/flutter/engine/pull/43281. Could you try updating your Flutter SDK to the latest stable version and seeing if the bug still reproduces then?

@loic-sharma I wonder if such severe issue affecting almost every text field in the app has been fixed 1.5 months ago, why it wasn't included into the hot fixe releases for 3.10 release?

@ekuleshov That's a good question. I'll follow-up on why we didn't cherry-pick this back to the stable channel, it seems like we should have.
I'll close this as fixed, but let us know if you'd like to reopen this.

So far we haven't seen any crashes with updated Flutter version. Thank you.

As long as there is a touch screen on Windows and there is no external keyboard display soft keyboard setting, this problem will be encountered, and the software disk will repeatedly pop up. We hope that the official takes this issue seriously.


Switch Vezel.Ruptura.Injection to using Vezel.Ruptura.System APIs

Most of the stuff used in Vezel.Ruptura.Injection can be switched to these APIs now. It's a good way to dogfood those APIs.
The following APIs aren't covered:

[ ] CreateProcessW
[ ] CreateRemoteThreadEx
[ ] GetProcAddress
[x] IsWow64Process2
[x] K32GetModuleBaseNameW
[x] OpenProcess (with caller-provided rights)

This is partially blocked on #15 now.


🧹 Fetch GCS blob lists per day, reduce number of calls.

rather than fetch per hour, fetch per day once and filter the records per hour

already done


Incomplete DWH snapshots resulted due to pipeline failures should not be used

Possibly the pipelines can fail in between (due to application restarts / crashes / unknown errors) and the snapshots can be incomplete. Proper measures must be taken to ensure not to use these incomplete snapshots for any analytical queries.
One approach to fix this is to create another timestamp file once the pipeline completes (currently we create a timestamp file when the application starts). This applies to both batch and incremental runs. Use this as an indicator to check for the completeness of the pipeline run.

Yeah, this is a good way to deal with interrupted/failed pipeline runs. We should just make sure to include this logic into the controller as well, i.e., when it searches for the latest DWH it should take into account this extra timestamp file.


Osama j

Description of the new feature / enhancement
"Text to speech", the same as "Read aloud" but in any web browser, document, or pdf.
for selected or whole text, also it will be great feature if you added it to "Text Extractor" too it will be great feature specially when reading some pdfs.
Scenario when this would be used?
documents, web Browsers, pdf, and images with text extractor
Supporting information
No response

/dup #25309


ObjectNamePrefix conflicts with Autoformat - spaces are removed

I'm using
 "[al]": {
        "editor.formatOnSave": true
    },

which formats fields as below when saving my changes (mind the space before the field name)
field(1; "Code"; Code[10])
However, when renaming all files via the CRS extension, in combination with "CRS.ObjectNamePrefix" set, my files are changed to
field(1;"Code"; Code[10])

Yep - true.  Will be fixed in next release!

@fvet - should be fixed!


Sample client data and expected benefit values

For now they're in one file. May break them up later to make it easier for individuals to add more, but I'm not sure how much more data we're going to get and right now this file has the columns listed at the top, which I think will be useful.

@nickbreid: It's actually a clarification that I just got back today and found out that only ones that say 'Section 8' are actually Section 8. Ideally, I'd love if those were fixed. On the other hand, it's not super relevant because this data, as it stands, is not sufficient for testing Section 8 calculations, and Section 8 doesn't have much of an effect on SNAP calculations. If we're just testing SNAP, Section 8 data is just flavor text.
Do you feel up for making a quick github edit of the files to reflect the change in our understanding?

@knod: Done.


WebAssembly?

Sokol supports wasm. Is it possible to get an example of how to compile in wasm on a rust?

Last time I tried (very briefly), the Rust WASM target wasn't exactly easy to setup. I didn't get very far.
Also, sokol-rs depends on cc-rs for compiling native libraries, which doesn't target WebAssembly either.


Create a tutorial to deploy a simple Hello Email app on Microsoft Azure with PHP using this SDK

Create a tutorial that explains how to create a simple Hello Email app and deploy to Microsoft Azure.
The example should utilize best practices for storing credentials. By the end of the tutorial, the user should be able to send an email using their deployed app.
Please add the tutorial to USE_CASES.md.

Closing as this feels like more of a blog post than library documentation and use cases.


added option to change worker log file

I think it'd be better to do it via command-line args, just as --log-level.

Well the logfile isn't changed that often after setup. So it would make more sense as a config option right?


make DataSample external

make DataSample external
based on Golint:
exported method GetSamples returns unexported type map[string][]*exec.dataSample, which can be annoying to use
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @lostluck


Create links to movies found in descriptions.

Movies mentioned in descriptions are always written out in uppercase. Perhaps these can be detected, then if the movies is found in the db, a link can be created in the description.

Been thinking more of this. I've thought it to be a performance hit if this were applied to all the movies in a particular response. But perhaps a page that only shows one movie? This page could also so some additional data for this movie.

Not gonna happen. Kind of a stoopid idea.


cmd/go: test passes when build is broken

go version devel +0175064e69 Thu Jan 3 05:07:58 2019 +0000 linux/amd64
If a package can be built only in test mode, go test succeeds while go build/install fails:
// broken.go
package broken
var X typ

// broken_test.go
package broken
import "testing"
type typ int
func TestX(t *testing.T) {
	var _ typ = X
}

If one develops just a package, go test is the main means of ensuring that everything works and lots of CIs just run go test, which means that it's possible to commit code that does not even build without noticing it.
It would be nice if go test would ensure that a package actually builds.

/cc @bcmills @rsc


CSI - Default value to fstype should be properly documented

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
Issue https://github.com/kubernetes/kubernetes/issues/65122 has updated the default value of CSI fstype from "ext4" to "".  This critical change should be documented.
Proposed Solution:
The section fstype section should be updated accordingly to reflect the changes for that attribute.
Page to Update:
https://kubernetes.io/docs/concepts/storage/volumes/#csi

/assign

/sig storage

I am working on it.

/close


license: SPDX: update all vc files to use SPDX style

When imported, the vc files carried in the 'full style' apache
license text, but the standard for kata is to use SPDX style.
Update the relevant files to SPDX.
Fixes: #227
Signed-off-by: Graham whaley<EMAIL_ADDRESS>

We'd like to land this ASAP, as due to PR https://github.com/kata-containers/tests/pull/242, all pending PRs that have touched a vc file with the old copyright will now fail the CI.
Even with this PR, those pending PRs will need rebasing and pushing, but that is easier than forcing the developers to now update the licenses only in the files they have touched etc.
Related, we should also try to land #226 at the same time.


Markdown export

Would it be possible to add support for exporting or saving syndicated content into a Markdown file? Similar in operation to how belong.io or latest.is works (harvests urls from specific users on Twitter, generates a webpage of links), this could be integrated in a static site generator publishing process such as Jekyll or Hugo.

It should be fairly straight forward to do, but I think it might be better to create a separate project for this.

I'll close the issue, but here's an example script that will write Tweets to Markdown from a given account.


feat: fix bugs and add unittests

fix lots of bugs and add unit tests.
I can not fix those code with filtered interface, I don't think the existing code works.
As for now, I commented out those code.
Signed-off-by: Zxilly<EMAIL_ADDRESS>

@hsluoyz @nodece plz review.
@smrpn Could you please provide some help on filtered interfaces?

This PR is part of #3

Current not support multipie role manager. I'm trying to find a elegant way to implement it.

@hsluoyz plz review


req.body.hasOwnProperty is not a function

how to reproduce this issue?

create a project with express-generator
in routes/index.js add the below line:

router.post('/', function(req, res, next) {
	console.log(req.body.hasOwnProperty('asdf'));
});

run the server
use postman to send a POST request with a couple of body parameters.
you'll get:

<!DOCTYPE html>

        <title></title>
        <link rel="stylesheet" href="/stylesheets/style.css">

req.body.hasOwnProperty is not a function

req.body.hasOwnProperty is not a function
Why this happening? is this behaviour expected?

I tested this with node 1.8.4 and the latest node, both show me false.

Same here @notrab.
@vajahath My guess is that your OP does not contain all of the changes you made after running the generator.  Maybe you could post the entire source on github and link us to it?

Well, assuming that the above was the only change, then the answer would be that req.body is the result of Node.js core querystring module's parse function (https://nodejs.org/dist/latest-v6.x/docs/api/querystring.html#querystring_querystring_parse_str_sep_eq_options), which doesn't inherit from Object:

Note: The object returned by the querystring.parse() method does not prototypically extend from the JavaScript Object. This means that the typical Object methods such as obj.toString(), obj.hasOwnProperty(), and others are not defined and will not work.

><EMAIL_ADDRESS>start ~/__test/express-issue-3264-info
> node ./bin/www

  hoytest:server Listening on port 3000 +0ms
false
POST / - - ms - -

curl -X POST -H "Content-Type: application/json" -d '{"foo":"bar"}' "http://localhost:3000/"

I can confirm the same result as @wesleytodd  with the same settings.

strange!!
Then how will we account for this:

Note: The object returned by the querystring.parse() method does not prototypically extend from the JavaScript Object. This means that the typical Object methods such as obj.toString(), obj.hasOwnProperty(), and others are not defined and will not work.

Ohhhhh, you send a url encoded body.  My curl above is incorrect, and this new one does exhibit that behavior, and it is the expected behavior due to what Doug mentioned.
curl -X POST -H "Content-Type: application/x-www-form-urlencoded" -d 'foo=bar' "http://localhost:3000/"

@wesleytodd Ahh! missed it 😅
So this is the expected behavior. (it would be awesome if it wasn't.  L😆L )
So I can
router.post('/', function(req, res, next) {
  req.body = JSON.parse(JSON.stringify(req.body));
  console.log(req.body.hasOwnProperty('asdf'));
});

to fix the issue.

Not sure which is more performant, but you could also do:
Object.setPrototypeOf(req.body, {});

Either solution means that an external user could override prototype methods on your objects, and if you are not careful this is a security issue.  If I were you I would not recommend doing either if you can help it.  For example, with either one of the above methods, try this curl:
curl -X POST -H "Content-Type: application/x-www-form-urlencoded" -d 'hasOwnProperty=bar' "http://localhost:3000/"

Should crash your app.

comming to your first part,
JSON.parse(JSON.stringify(req.body));

This method requires stringification and parsing, which are processing intensive tasks, I guess.
On the other hand, Mozilla says about
Object.setPrototypeOf(stuff..);

as

Warning: Changing the [[Prototype]] of an object is, by the nature of how modern JavaScript engines optimize property accesses, a very slow operation, in every browser and JavaScript engine. The effects on performance of altering inheritance are subtle and far-flung, and are not limited to simply the time spent in obj.proto = ... statement, but may extend to any code that has access to any object whose [[Prototype]] has been altered. If you care about performance you should avoid setting the [[Prototype]] of an object. Instead, create a new object with the desired [[Prototype]] using Object.create().

Not sure what should I use.
second part
So how can I solve this issue safely?

That is why I said I didn't know which was more performant
Use other methods than the prototype chain to check if req.body has the fields you are looking for.  Personally I just do if (req.body.foo) // do stuff with foo.

alright.
I feel osm. Thanks everyone.
⭐

The problem is that express.urlencoded default value(=false) uses querystring.parse().
Globally elegant If you want req.body to inherit an object, change extended to true.
Then use qs.parse to inherit the object. you can use hasOwnProperty ().


Intercept Custom calls

Custom is evil and should never be used in Radian. However, a number of other Emacs facilities call into it, such as when setting safe file-local variable values, installing packages with package.el, setting safe themes, and using the actual Customize interface.
We can intercept all such calls by overriding select internal Custom functions, and converting them into something more useful (such as copying a setq or put form to the kill ring).

I no longer feel this is necessary. We set the custom-file to ~/.emacs.d/init.el which allows per-host local customizations that will not be part of version control. I think it is a good enough compromise.


[TPL2] Port over minimal subset of sql/ (value, runtime types)

Status:

[x]  I messed up and was merging the wrong branch. WIP.
[x] I need to fix merge conflicts from the TransientValue cleanup.
[ ] #915 should be merged first.

Part of #914.
Port over just enough of sql/ to get the value and runtime types ready.
This paves the way for adding the rest of sql/functions, sql/operations/, sql/vector_operations, etc.
I can't run all the unittests without my computer crashing. Going to use Jenkins...

Closing in lieu of a larger PR later.


Dependabot Integration

Description
Integrated Dependabot with the frontend.
Related Issue(s)
Fixes issue #34
Changes Made
Check for outdated dependencies on "npm" packages everyday and create pull requests for updating them.
Checklist
Please review and check the following before submitting your pull request:

[ x ] I have followed the Code of Conduct.
[ x ] My code follows the project's contributing guidelines.
[ x ] I have tested my changes locally and they work as expected.
[ x ] I have included relevant tests for my changes.
[ x ] I have updated the project documentation if necessary.
[ x ] I have reviewed my code to ensure it is free of debugging or development-related code.
[ x ] I have provided clear and informative commit messages.

Contributor License Agreement
By submitting this pull request, I confirm that my contribution is made under the terms of the project's License, and I agree to abide by the project's Code of Conduct.

@all-contributors please add @Riddhick for code


Require signed commits on go repo main branches

Initially needs to be implemented on repositories where we are adding automation to auto merge dependabot patch version updates. This will provide an additional layer of protection in our automation to prevent malicious actors from submitting unverified dependabot commits that could be auto merged.
Eventually should be rolled out to all community repositories.
Depends on: https://github.com/Senzing/knowledge-base/issues/56
Per docs GitHub already uses this flow for commits via the GitHub UI:

GitHub will automatically use GPG to sign commits you make using the web interface. Commits signed by GitHub will have a verified status. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg.

Navigate to the respective repository in the GitHub UI.
Select the Settings tab.
Select Branches in the left side nav.
If a main branch protection rule does not exist, create one. Otherwise edit the existing main branch protection rule.
Select Require signed commits.
Click Save.

See KB instructions for installing gnupg and signing commits locally.

 Will open new issues for tracking non go repositories.


Add ability to logout or remove existing credentials

Describe the feature
It would be useful to have a way to force the module to forget any existing credentials. Clearing the oauth token does not appear to do this.
Usecases
I set this module up initially expecting to need just readonly access to a spreadsheet. The spreadsheet has read access to anyone with the link, write access to a few accounts.
Later I decided I needed write access, and so wanted to change the account it was logged in with, to avoid sharing it with the other account.
I tried clearing the oauth token field, but it remainded logged in, so I ended up deleting the connection so that I could login with the other account. This meant I needed to reconfigure my actions on the new connection too

Added a new config option that when toggled on will delete current Access and Refresh token


Couldn't compile an example

OS: ArchLinux (x86_64)
Rust: cargo 1.82.0 (8f40fc59f 2024-08-21)
File Cargo.toml:
[package]
name = "system-id"
version = "0.1.0"
edition = "2018" # << i've tried 2021 too

[dependencies]
systeminfo = { git = "https://github.com/marirs/systeminfo-rs", branch = "main" }

Try to build:
$ cargo build

   Compiling systeminfo v0.1.6 (https://github.com/marirs/systeminfo-rs?branch=main#8315da97)
error[E0432]: unresolved import `humanize`
 --> /home/aaa/.cargo/git/checkouts/systeminfo-rs-12dac908e940a51c/8315da9/src/nix/hwinfo.rs:6:5
  |
6 | use humanize::Humanize;
  |     ^^^^^^^^ help: a similar path exists: `crate::humanize`
  |
  = note: `use` statements changed in Rust 2018; read more at <https://doc.rust-lang.org/edition-guide/rust-2018/module-system/path-clarity.html>

error[E0599]: no method named `humanize` found for type `f64` in the current scope
   --> /home/aaa/.cargo/git/checkouts/systeminfo-rs-12dac908e940a51c/8315da9/src/nix/hwinfo.rs:131:30
    |
131 |         .map(|x| (x * 1000.).humanize());
    |                              ^^^^^^^^
    |
   ::: /home/aaa/.cargo/git/checkouts/systeminfo-rs-12dac908e940a51c/8315da9/src/humanize.rs:8:8
    |
8   |     fn humanize(&self) -> String;
    |        -------- the method is available for `f64` here
    |
    = help: items from traits can only be used if the trait is in scope
help: there is a method `humanize_into` with a similar name, but with different arguments
   --> /home/aaa/.cargo/git/checkouts/systeminfo-rs-12dac908e940a51c/8315da9/src/humanize.rs:9:5
    |
9   |     fn humanize_into(&self, _: &str) -> String;
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: trait `Humanize` which provides `humanize` is implemented but not in scope; perhaps you want to import it
    |
2   + use crate::humanize::Humanize;
    |

Some errors have detailed explanations: E0432, E0599.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `systeminfo` (lib) due to 2 previous errors

Hi,
Ive fixed it
Thanks

The same issue on Windows


[ISSUE] v9.3.3 upgrade to 10.0.0 fails due to mismatched labels in identity

Describe the issue:
When upgrading from chart 9.3.3 to 10.0.0, the following error will appear:
Error: UPGRADE FAILED: cannot patch "RELEASE-identity" with kind Deployment: Deployment.apps "RELEASE-identity" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app":"camunda-platform", "app.kubernetes.io/component":"identity", "app.kubernetes.io/instance":"RELEASE", "app.kubernetes.io/managed-by":"Helm", "app.kubernetes.io/name":"camunda-platform", "app.kubernetes.io/part-of":"camunda-platform"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

If you format the LabelSelector in the error message, it looks like this:
{
  "app": "camunda-platform",
  "app.kubernetes.io/component": "identity",
  "app.kubernetes.io/instance": "RELEASE",
  "app.kubernetes.io/managed-by": "Helm",
  "app.kubernetes.io/name": "camunda-platform",
  "app.kubernetes.io/part-of": "camunda-platform"
}

That JSON represents the matchLabels in the newer version (10.0.0), however, the 9.3.3 version of the labels looks like this:
> k get deployment RELEASE-identity -o yaml | yq .spec.selector

matchLabels:
  app: camunda-platform
  app.kubernetes.io/component: identity
  app.kubernetes.io/instance: RELEASE
  app.kubernetes.io/managed-by: Helm
  app.kubernetes.io/name: identity
  app.kubernetes.io/part-of: camunda-platform

The difference between these 2 sets of labels is this label:
  app.kubernetes.io/name: identity

Because the two sets of labels do not match, the upgrade will fail.

Actual behavior:
Upgrade fails with message:
Error: UPGRADE FAILED: cannot patch "RELEASE-identity" with kind Deployment: Deployment.apps "RELEASE-identity" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app":"camunda-platform", "app.kubernetes.io/component":"identity", "app.kubernetes.io/instance":"RELEASE", "app.kubernetes.io/managed-by":"Helm", "app.kubernetes.io/name":"camunda-platform", "app.kubernetes.io/part-of":"camunda-platform"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

Expected behavior:
Upgrade should succeed.

How to reproduce:
Upgrade from 9.3.3 to 10.0.0

Logs:

Environment:
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

Platform:
Helm CLI version:
Chart version:
Values file:

> ~/code/helm/bin/helm template -f base-combined-pre8.5.yaml -f ./useingressnginx.yaml -f lazyUpgrade.yaml cpt camunda/camunda-platform --version 9.3.3 --show-only charts/identity/templates/deployment.yaml | yq .spec.selector
matchLabels:
  app: camunda-platform
  app.kubernetes.io/name: identity
  app.kubernetes.io/instance: cpt
  app.kubernetes.io/managed-by: Helm
  app.kubernetes.io/part-of: camunda-platform
  app.kubernetes.io/component: identity

> ~/code/helm/bin/helm template -f base-combined.yaml -f ./useingressnginx.yaml -f lazyUpgrade.yaml cpt camunda/camunda-platform --version 10.0.0 --show-only templates/identity/deployment.yaml | yq .spec.selector
matchLabels:
  app: camunda-platform
  app.kubernetes.io/name: camunda-platform
  app.kubernetes.io/instance: cpt
  app.kubernetes.io/managed-by: Helm
  app.kubernetes.io/part-of: camunda-platform
  app.kubernetes.io/component: identity

This change is already documented here, with a manual workaround:
https://docs.camunda.io/docs/next/self-managed/setup/upgrade/#identity
I wasn't aware of this when I drafted this issue yesterday.


Text's numberOfLines doesn't work in iphone8P

Envirment:  Iphone8 plus
code
<Text numberOfLines={2} >  2019年4月24日星期四 调整在途，少接飞刀 盘面观察周二A股延续弱势持续调整。从盘面看，两市股指低开后短暂上攻，但由于金融股和周期股表现不佳，大盘索性下台阶跌破3500点关口；午后市场有所回暖，                 </Text>
but it just shows one line.

How can it show tow lines.

numberOfLines is currently an android only prop!

I wanted to ask if you still experience this issue.
I'm planning to do 1-2 months of opensource and I'm preparing a list of tasks.
I have been contributing to facebook/react-native for 4 years and I specialize on the Text/TextInput components.
Thanks a lot


Scrolling teleports on fling

Using the latest from master branch. I'm running the flutter gallery in release mode. If I fling my finger fast (It's pretty easy to do this accidentally), the scrolling can effectively teleport to the top or bottom of the screen.
This only seems to happen with scrolling in Android mode. If I change the flutter gallery to ios mode, everything seems fine.
I'd take a video, but genymotion emulators are having issues at the moment with flutter: https://github.com/flutter/flutter/issues/8416
@Hixie I'm assuming this is a regression with the recent scrolling refactor.

I investigated this briefly at one point and came to the conclusion that this behavior is caused by https://github.com/flutter/flutter/issues/8255

#8255 is closed, so tentatively closing this.
@ScottPierce would you mind trying again with today's version of Flutter? We'll be happy to reopen this issue if you can still repro.


chore(blockifier): fix typos in l1_handler test

This change is

#2696  👈 (View in Graphite)
main

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


brew-audit: move style checks into main audit output

Checklist

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[X] Have you successfully ran brew tests with your changes locally?

Description
Breaks up the brew style part of the check for brew audit --strict and runs it separately for each formula, when that formula is being checked for other audits. This collects all violations for each formula in a single place, instead of doing brew style outputs for all formulae first, and then the other audit checks. Easier to read. It also makes the violation count at the end of the output include the style violations.
Before:

After:

This also localizes the --fix argument support in style so that it doesn't leak to audit. I'm not sure if that's the right thing to do, though. audit isn't documented as supporting --fix, but that doesn't necessarily mean it isn't supposed to do it.
Considerations

This turns off the syntax highlighting for the Rubocop output. I think that's fine, since we're uniformly using the main audit output style here. If someone really misses it, I could add an option to enable the old behavior, with all the style checks at the top and with coloring intact. Or we could add Tty-based coloring to audit's own output, and you'll get it everywhere. (Personally, I don't care. I think this much use of color is distracting instead of helpful.)
Will be slightly slower when auditing multiple formulae due to multiple Rubocop invocations. I don't think this is a big deal: the main use case is single-file formula audits, I think. And it was still perfectly tolerable when I ran it interactively on big batches like brew audit --strict a*.
Is brew audit actually supposed to support --fix?

A few comments but otherwise LGTM 👍

Switched to "in progress" while I look at switching to Rubocop's JSON output instead of parsing their normal results output.

I rewrote the rubocop interaction using its JSON output, per @xu-cheng's suggestion. Now we're using the appropraite machine-readable format, results for multiple files are represented correctly, and the rubocop checks can be done in a single batch up front to avoid the cost of shelling out to rubocop separately for each formula.

Question: the ==> audit problems ohai header is only displayed when --strict is given. Why is that?

Question: the ==> audit problems ohai header is only displayed when --strict is given. Why is that?

Could just be a mistake. Feel free to address it.

Looks good to me 👍

Amended to address the latest round of output.
Two significant changes:
Before, the style checks were only run when you specified files or formulae, and were skipped when you did a plain brew audit to check everything. Now it runs style checks too, since we can specify the correct set of files.
Removed the empty line between formulae in the output (and changed to 2-space indent for the bullet lists). Martin and I think it's more readable and a better use of space this way. IMHO, especially true now that audit has been tweaked to work better for large batches of files, and now includes style output in sections that previously did not have it.
New output:
$ brew audit a* b* c* --strict
homebrew/science/abinit:
  * Use '--without-test' instead of '--without-check'. Migrate '--without-check' with `deprecated_option`.
homebrew/science/abyss:
  * Options should begin with with/without. Migrate '--enable-maxk=' with `deprecated_option`.
  * Use '--without-test' instead of '--without-check'. Migrate '--without-check' with `deprecated_option`.
homebrew/science/adam:
  * `option` (line 21) should be put before `depends_on` (line 14)
  * Description is too long. "name: desc" should be less than 80 characters.
Length is calculated as adam + desc. (currently 112)
  * Use '--without-test' instead of '--without-check'. Migrate '--without-check' with `deprecated_option`.
homebrew/science/alembic:
  * `head` (line 17) should be put before `bottle block` (line 10)
  * A `test do` test block should be added
homebrew/science/alglib:
  * Formula should have a desc (Description).
homebrew/science/alpscore:
  * Use '--with-test' instead of '--with-check'. Migrate '--with-check' with `deprecated_option`.
  * C: 27: col 25: Don't use parentheses around a method call.
homebrew/science/amos:
  * Description shouldn't start with an indefinite article (A)

The format for multi-line problems is ugly, with 2nd and later lines not being indented, like "Length..." in the following.. Going to do something about that while I'm in here.
  * Description is too long. "name: desc" should be less than 80 characters.
Length is calculated as adam + desc. (currently 112)
  * Use '--without-test' instead of '--without-check'. Migrate '--without-check' with `deprecated_option`.

That turned out to be easier than I feared.
homebrew/science/adam:
  * `option` (line 21) should be put before `depends_on` (line 14)
  * Description is too long. "name: desc" should be less than 80 characters.
    Length is calculated as adam + desc. (currently 112)
  * Use '--without-test' instead of '--without-check'. Migrate '--without-check' with `deprecated_option`.
homebrew/science/alembic:

I think this is ready to go now, pending y'all's feedback on the output format change.

Looking good to me 👍. We can always iterate after shipping.

:+1: I can think of a few minor improvements, but they can wait and I've pestered you enough in this PR. I'm really happy with the code now (and the major improvement to brew audit hidden therein).
What I'd really like you to consider for future PRs (or even this PR, if you feel like retroactively doing this) would be not to lump all changes into a single commit. It's really hard to digest once some time has passed and you're looking at the Git history. Looking at the current code, here's what the theme of individual commits could be (they should be all independent and build on top of each other):

utils: add popen_read_text
utils: refactor inject_dump_stats! to be independent of Homebrew::Diagnostic::Checks (and adapt cmd/doctor.rb, diagnostic.rb accordingly).
style: refactor and use RuboCop JSON interface
style: add documentation
audit: use generalized inject_dump_stats!
audit: better integrate style checks

Sorry! I've gotten used to squashing to a single commit to formula changes; maybe overapplied it here.
I could still break these out to multiple commits if you think it would help readability. (Some git clients I use make that pretty easy; maybe they foresaw this situation.)

Sorry! I've gotten used to squashing to a single commit to formula changes; maybe overapplied it here.

No need to apologize! It's just something that I noticed and I wanted to make you aware of. Just pretend for a moment that there's a breaking change in audit (very unlikely) introduced by this code. It would be a shame to have to revert all the other improvements also contained in the same commit and then again work on a fairly big chunk to get things sorted out.

I could still break these out to multiple commits if you think it would help readability. (Some git clients I use make that pretty easy; maybe they foresaw this situation.)

I'd leave this decision up to you. It's obviously easier to do when things get split right from the start. I'm also fine merging it as-is, as nobody except me complained and even I did so at the very last moment.

Well, I was wrong: GitUp makes it easy to split commits on a per-file basis, and SourceTree has good support for staging/unstaging by line or hunk, but neither is going to help much with splitting this

Turns out splitting this would take a good amount of work: I'd want to make sure each individual commit still worked, so it would take manual editing and several rounds of testing, and I'm short on time this week. Let's just merge as-is, and I'll work on organizing future PRs better.

Shipped. Thanks for your feedback, folks!


rmux edit should be able to accept extra positional parameters that will be used for checks

resolved by #11


Why acpi_call?

TLP's documentation states:

As of version 5.17, the Linux kernel in combination with TLP 1.5 or later offers full battery care support (i.e. charge thresholds and recalibration) for ThinkPads from model year 2011 onwards.

...and later even calls acpi_call "obsolete".
So I'm curious why it's used and why the module states that it "makes tlp work for newer thinkpads"?  The natacpi + thinkpad_acpi combo works for me on older Thinkpads (e.g. X230) and my more recent ones (e.g. T470s).

It's probably fair to remove it at this point.

I noticed I'm unable to build NixOS with the latest ACPI call, here's a thread I opened on Discourse, with some findings from the community members (thanks Simon!)

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/hash-mismatch-issue/56870/6


Renewal Certificate

Please add that the CNAME must point to a static web app or the static web app must be publicly accessible for certificate renewal.

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

ID: 190b1ed3-0712-2f19-4e8f-a2a8519d136e
Version Independent ID: b02adbf4-d2a8-6c84-e70a-ff59fb3cbb7b
Content: Set up a custom domain in Azure Static Web Apps
Content Source: articles/static-web-apps/custom-domain.md
Service: static-web-apps
GitHub Login: @burkeholland
Microsoft Alias: buhollan

Thanks for the feedback! We are currently investigating and will update you shortly.

We'll update the docs to appropriately address this gap. Thanks for bringing it to our attention.
/cc @anthonychu

#please-close


Define indices_do_not_alias for faster broadcast

https://github.com/JuliaArrays/ArrayInterface.jl/pull/293
Define this function to true so ivdep is enabled and you'll get some better performance.

Done, thanks!


Windows binary missing from the release

Where is the Windows binary for 0.4.2 release?
btw. Thank you for this great piece of software that has changed my life.

See https://github.com/kmonad/kmonad/issues/767


MassTransit does not retry to connect if it can not connect to RabbitMQ the FIRST TIME

Is this a bug report?
yes

Can you also reproduce the problem with the lastest version?
yes, I'm using 5.1.4
Environment

Operating system: Windows 8.1
Visual Studio version: 2017
Dotnet version: 4.7.2

Steps to Reproduce

(Write your steps here:)

a simple client : var bus = Bus.Factory.CreateUsingRabbitMq(...);
bus.StartAsync();
wait about 10 seconds, and then start RabbitMQ server

Expected Behavior

I expect the bus retry to connect after some time. just as it do when it disconnects and tries to reconnect
Actual Behavior

the client fails to connect at the first try as expected but never retries to connect to RabbitMQ. if you swap step 2 and 3, all things goes OK even if you restart RabbitMQ
Reproducible Demo

using MassTransit;
using MassTransit.RabbitMqTransport;

namespace Test
{
    internal class Program
    {
        private static void Main()
        {
            var bus = Bus.Factory.CreateUsingRabbitMq(config =>
            {
                var _rabbitHost = config.Host(new Uri("rabbitmq://<IP_ADDRESS>"), host =>
                {
                    host.Username("guest");
                    host.Password("guest");
                });
                config.ReceiveEndpoint(_rabbitHost, this.GetType().FullName, endpoint =>
                {
                    endpoint.Handler<SomeEvent>(context =>
                        System.Console.WriteLine("event recieved");
                });
            });
            bus.StartAsync();
            // after some delay start RabbitMQ server
            System.Console.ReadLine();
        }
    }
}

This is intended behaviour, there is a issue discussing to change it. #1158


Pin conda-build to version 1.x

This pins conda-build to version 1.x. Have noticed some issues ( https://github.com/conda/conda-build/issues/1305 ) with bdist_conda that are going to cause us pain. So this should help us avoid them until they get sorted.

Seems to be working as intended.


[Bug Report] Wrong migration guide (?)

Describe the bug
At the gymnasium website (https://gymnasium.farama.org/introduction/migration_guide/) there is a migration guide named Migration Guide - v0.21 to v1.0.0 but it looks like it describes migration from v0.21 to v0.26. Is this correct behavior?
Code example
No response
System info
No response
Additional context
No response
Checklist

[X] I have checked that there is no similar issue in the repo

The core API was not changed from 0.26 to 1.0

I suggest making it clearer that the API was not changed, maybe give rename sections like this:

Example code for v0.26 -> Example code for v0.26/v1.0.0

I can create a PR if something like this is welcome.


test-mode support for source files with fewer than 1k documents

It may be useful for test-mode to relax its assumption that source files within corpora contain 1k documents. I say this for three reasons:

New users trying out Rally for the first time may--as I did :smile: --run esrally  create-track on a very small index in an already-running local Elasticsearch cluster. The resulting track will fail when run in test-mode due to the document-count being less than 1,000. The error message is rather clear, for what it's worth.
While the docs do clearly state that test-mode assumes that data files contain 1k documents, the error message that one receives if their track does not comply with this assumption is confusing. See below.
There may be legitimate use cases for actually benchmarking workloads with corpora containing fewer than 1,000 documents. In order to use test-mode on tracks that define such workloads, users would have to jump some through hoops to set things up in a way that will satisfy its assumptions.

Relaxing this assumption would be simple to implement (I have a POC on a branch) if there's agreement that this is worth doing.
If there are good reasons to preserve this assumption, however, I'd advocate for a refactoring that would surface a clearer error in the scenario described in (2) above and illustrated below.
Misleading error message
Here is a minimal track and source file that will produce the misleading error message. I tested this with esrally 2.3.1.dev0 (git revision: f2d8a11).

track.json
{
  "version": 2,
  "description": "Minimal track for illustrating --test-mode issue",
  "indices": [
    {
      "name": "test"
    }
  ],
  "corpora": [
    {
      "name": "test",
      "documents": [
        {
          "source-file": "documents.json",
          "document-count": 1,
          "uncompressed-bytes": 15
        }
      ]
    }
  ],
  "schedule": [
    {
      "operation": {
        "operation-type": "bulk",
        "bulk-size": 1,
        "target-index": "test"
      }
    }
  ]
}

documents.json
{"foo": "bar"}

Example Rally invocation:
esrally race --distribution-version=7.15.0 --track-path=~/debug-test-mode --test-mode

Output (truncated):
[INFO] Race id is [70ab67cc-d623-4c6c-aa97-cf107dc85286]
[INFO] Preparing for race ...

[ERROR] Cannot race. Error in task executor
        Cannot download data because no base URL is provided.

This error is misleading. The problem isn't that there's no base url. The problem is that there isn't actually a source file named documents-1k.json on disk, so Rally eventually assumes that it must need to be downloaded from a remote source.
More specifically, the loader.TestModeTrackProcessor.on_after_load() method sets the document_file attribute on the track.Documents instance it's operating on to documents-1k.json. This gets passed to loader.DocumentSetPreparator.prepare_bundled_document_set(), which returns False due to the file not being available locally. The control flow in the code is such that this will ultimately cause loader.Downloader.download() to be called with None as its base_url argument. This throws the exception that is ultimately presented to the user as the error message above.

Clarification: When I say "relax the assumption," I mean that test-mode would "just work" with corpora smaller than 1k, but still reduce larger corpora down to 1k. I should have mentioned that originally.

still reduce larger corpora down to 1k
I believe there's a misconception here: the 1k file is explicitly created and provided by the track developer, and co-located with the other, regular corpora.  Rally doesn't do this for us.

Poor wording on my part, thanks for clarifying.

Do you have any thoughts on this one @danielmitterdorfer and @dliappis?

Another occurrence of the misleading error message: https://discuss.elastic.co/t/urgent-corpora-definiton-no-base-url-defined-indexing-local-dump-json/324515/5


ORT use "api"-based endpoints

I'm submitting a ...

[ ] bug report
[ ] new feature / enhancement request
[x] improvement request (usability, performance, tech debt, etc.)
[ ] other

Traffic Control components affected ...

[ ] CDN in a Box
[ ] Documentation
[ ] Grove
[ ] Traffic Control Client
[ ] Traffic Monitor
[ ] Traffic Ops
[x] Traffic Ops ORT
[ ] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] unknown

Current behavior:
ORT currently fetches packages and the chkconfig from /ort/{{host name}}/packages and /ort/{{host name}}/chkconfig, respectively.
Expected / new behavior:
Handlers exist in the Perl route /api/{{version}}/servers/{{server}}/configfiles/ats/{{filename}} for those two special packages. If they are incorrect in some way, then a rewrite to Go should be done that fixes them. Either way, the "api"-based routes should be used.

Splitting this into separate issues.


Address N+1 issues detected by bullet on the dashboard

Summary
We've noticed that the dashboard incurs several warnings of N+1 queries via the bullet gem on the dashboard. This causes the page to be inefficient and a longer time than it needs to load the page.
Here is the warnings I'am seeing thus far:

Things to Consider
Sometimes a includes doesn't address the underlying issue. Its important to take a look at the logs to see what is actually going on.
Criteria for Completion

[ ] Most or some of the N+1 warnings have been addressed. For those that aren't easy fixes, please mention it in your pull request.

@gamecat2d hey there -- I was wondering if you wanted to take on this one as well. Since I saw you did really well in the other related N+1 issue. :)

Hello, it's been a while. May I give this one a try?

@rhian-cs yep! Assigning to you


Add options for controlling svelte dominators output

[ ] maximum depth in dominator tree
[ ] maximum number of rows to include in output, regardless of depth

Each of these involves new fields on the Dominator struct in ./opt/opt.rs.
The DominatorTree struct in analyze/analyze.rs should make and hold a copy of the opt::Dominators options.
Then, the impl traits::Emit for DominatorTree should consult the new options and modify its output appropriately.

@sendilkumarn, this could be a good issue for you to pick up! :)


adding additional unit and integration tests for heron windowing support

Also added some null checks in client side

@srkukarni @kramasamy Can you look.  Thanks!

Test failed due to being too long.  Though all the java tests passed

@maosongfu is there a way to increase the ci timeout?

@srkukarni @jerrypeng Already requested and the timeout was increased: now it is 150mins. Let me know if it does not work.

@maosongfu thank you!

Thanks @maosongfu That worked.


Brief psuedo code for example using template for newrelic.ini

@sleitner @marcesher @vickumar1981 @m3brown
We can decided whether to fix up, test, and execute using a template to create the newrelic.ini but here is what it would look like.

The high security mode is not currently being used.
Our latest changes now restart apache no matter what.
These changes would only force a restart if wsgi_scriptfile, or the ini file changed.
If the values for whitelist_exception are blank the line should be missing not = empty string. (line 31 in newrelic.ini.j2)

I'm :+1: on this plan. I'd clean up the template some (esp. the environment stuff).


Add support for GeoIP to automate country lookup

To automate the GeoIP country lookup / manual input, it might be cool to add this package : https://github.com/pulkitjalan/geoip

Don't think that this should be implemented in this package, as this can be easily solved by simply using something like the Geocoder package to prefill the user's country code.


Error using analysis tools

Hi again, I have tried to encode and load in YUViewer and it refuses to open with this message
Unable to obtain frame size from file and with Vicue VQAnalyzer pix_fmt not supported
My current encoding options
vvencFFapp -i 00000.m2ts -f yuv4mpegpipe -pix_fmt yuv420p - | vvencFFapp -i - --y4m -s 1920x1080 --fps 24000/1001 -b teste.266 -t 28 --passes 1 --TargetBitrate 1.5M --Verbosity verbose --preset slow --Sdr sdr_709 --OutputBitDepth 10 --InternalBitDepth 10 --Tiles 2x2  --Lookahead 1

I don't know about VQ Analyzer. It's a proprietary app. Changes are this is also a bug on their side.


abdulajet: add my new pixel

Checklist

[x] I ran npm test locally and it passed without errors.
[x] I only edited the _data/pixels.json file.
[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

Hey bud :) you need to remove the < and > from your pixel :)

whoops, long day. Could this be added as a test?


Add alert rule propagation itest

Issue
No itest confirming alerts are generated from rules received.
Solution
Use avalanche as the tester charm. Forward metrics+rules over remote-write.
Drive-by fixes:

Change base from 22.04 to 20.04.
Fetch cos-tool.
Drop StoredState.

Context
NTA.
Testing Instructions

Relate mimir and avalanche.
curl $mimir:9009/prometheus/api/v1/alerts should be non-empty.

Release Notes
Add alert rule propagation itest.

Until remote_write has a way to signal Providers that they should respond, and the Mimir charm observes it and takes action, there is no predictability to the workflow.

There's already
        # TODO add custom event to remote-write
        self.framework.observe(self.on.receive_remote_write_relation_changed, self._configure)

in place. You'd rather wait for a prom PR + CI cascade?

Yes, I'd rather wait. I'm happy to write the patches myself today. An integration test which we know has gaps may as well wait.
Remote write also needs a small audit to see "who else is using this and how likely is it that we lose/miss rules?" This is important if we're going to release 1.1 next week. Considering it something found in QA


fix: update deps

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

GitHub release
1.2.1
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Event not emited to websockets from job

I'm trying to send a event from a job. Sending that events works outside the job. But if I try to emit the event from inside the job, it does not emit.
Could you please help me?
Thank you,

Did you change your broadcasting configuration while the WS server was running? I vaguely remember having to restart the WS server after changing it to point to the new WS server (instead of sending to Pusher)

No configuration was changed. When I trigger a event to call a HTTP request and in the method of the controller the event is triggered and dispatched to webbrowser clients

I know this is pretty old, but in my case i had to use php artisan queue:work --queue=default,secondary_queue, and MyJob::dispatch($exampleId)->onQueue('secondary_queue');
This is because Laravel uses the default  queue for websockets events, and if you don't define a different queue for your jobs, the default  will by busy by current job, and the WS events won't fire until job is done.


update Cross Site Scripting link

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
https://github.com/yiisoft/yii2/issues/19000

👍🏻


Installing and running on Windows

First off, great work on the development and architecture of this plugin I'm looking forward to Ghidra + Python3 scripts!
I wanted to document my process on attempting to getting this plugin running:
Prerequisites notes
Python
Python 3.10 was installed through the Windows Store
i.e. installed to:
%LocalAppData%\Packages\PythonSoftwareFoundation.Python.3.10_...\
and therefore pip --user install jep installed to:
%LocalAppData%\Packages\PythonSoftwareFoundation.Python.3.10_...\LocalCache\local-packages\Python310\site-packages\jep
Java
Eclipse Adoptium OpenJDK installed to:
C:\Program Files\Eclipse Adoptium\jdk-<IP_ADDRESS>-hotspot
with both bin\client\jvm.dll and bin\server\jvm.dll
Building
Build succeeded with a small deprecation warning, observable with this diff:
diff --git a/build.gradle b/build.gradle
index 618e1e7..0aa608b 100644
--- a/build.gradle
+++ b/build.gradle
@@ -53,6 +53,10 @@ tasks.matching { it.name != 'copyJepNativeBinaries' && it.name != 'installJep' }
     task.dependsOn copyJepNativeBinaries
 }

+tasks.withType(JavaCompile) {
+    options.deprecation = true
+}
+
 // from here we use the standard Gradle build provided by Ghidra framework

 //----------------------START "DO NOT MODIFY" SECTION------------------------------

See: #9
And the Jep binaries were correctly discovered and bundled with the Ghidra plugin under dist/
Installing
I get a Ghidra Exception on loading the plugin after a restart:
%USERPROFILE%\.ghidra\.ghidra_10.1.5_PUBLIC\Extensions\Ghidrathon\os\win_x86_64\jep.dll: Can't find dependent libraries
java.lang.UnsatisfiedLinkError: %USERPROFILE%\.ghidra\.ghidra_10.1.5_PUBLIC\Extensions\Ghidrathon\os\win_x86_64\jep.dll: Can't find dependent libraries

in investigating the jep.dll with ldd in git bash Thanks Windows
ldd ./.ghidra/.ghidra_10.1.5_PUBLIC/Extensions/Ghidrathon/os/win_x86_64/jep.dll
        ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffc5eea0000)
        KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7ffc5d3c0000)
        KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7ffc5c380000)
        msvcrt.dll => /c/WINDOWS/System32/msvcrt.dll (0x7ffc5ed90000)
        jep.dll => %USERPROFILE%/.ghidra/.ghidra_10.1.5_PUBLIC/Extensions/Ghidrathon/os/win_x86_64/jep.dll (0x7ffc50b60000)
        ucrtbase.dll => /c/Windows/System32/ucrtbase.dll (0x7ffc5cb70000)
        vcruntime140.dll => /c/Windows/System32/vcruntime140.dll (0x7ffc35bd0000)
        jvm.dll => not found
        python310.dll => not found
        api-ms-win-crt-heap-l1-1-0.dll => /c/Program Files/Eclipse Adoptium/jdk-<IP_ADDRESS>-hotspot/bin/api-ms-win-crt-heap-l1-1-0.dll (?)
        api-ms-win-crt-runtime-l1-1-0.dll => /c/Program Files/Eclipse Adoptium/jdk-<IP_ADDRESS>-hotspot/bin/api-ms-win-crt-runtime-l1-1-0.dll (?)
        api-ms-win-crt-stdio-l1-1-0.dll => /c/Program Files/Eclipse Adoptium/jdk-<IP_ADDRESS>-hotspot/bin/api-ms-win-crt-stdio-l1-1-0.dll (?)
        api-ms-win-crt-convert-l1-1-0.dll => /c/Program Files/Eclipse Adoptium/jdk-<IP_ADDRESS>-hotspot/bin/api-ms-win-crt-convert-l1-1-0.dll (?)
        api-ms-win-crt-string-l1-1-0.dll => /c/Program Files/Eclipse Adoptium/jdk-<IP_ADDRESS>-hotspot/bin/api-ms-win-crt-string-l1-1-0.dll (?)

There are two unreachable DLLs

jvm.dll could not be found out of the Eclipse Adoptium OpenJDK install directory (or maybe not able to disambiguate between the two?)
python310.dll seems to not be distributed with the windows store build (perhaps a static build?)

I understand that these are likely issues specific to Jep itself however I wanted to report general usability issues to either make more meaningful Ghidra error messages and to upstream these issues to Jep is called for.
Thanks again for the project!
Operating System: Windows 11 21H2 22000.856
Java Version: OpenJDK <IP_ADDRESS>
Ghidra Version: 10.1.5
Gradle Version: 7.5.1
Python Version: 3.10.7
Jep Version: 4.0.3

Thank you for the report and helpful context @rchildre3 - we will do some digging here to see how we can improve usability. We will upstream the issue if it's Jep-specific.

在 Windows 上遇到了类似的问题，以下是我注意到的问题以及我的解决方案：

如果我们运行的是虚拟环境，或者在任何情况下都需要任何用户环境，我们将在该环境中启动 Ghidra。但是，默认情况下会将 Ghidra 作为后台进程启动：ghidraRun.bat

call "%~dp0support\launch.bat" bg jdk Ghidra "%MAXMEM%" "" ghidra.GhidraRun %*

这里的参数使 start Ghidra 使用命令，并且基本上清除环境（只有基本的 Cmd.exe 环境传递给它）：bg``launch.bat``start``/I
if "%BACKGROUND%"=="y" (
	set JAVA_CMD=!JAVA_CMD!w
	start "%APPNAME%" /I /B "!JAVA_CMD!" %CMD_ARGS%
	...
) else (
	"%JAVA_CMD%" %CMD_ARGS%
)

这导致了我这边的DLL依赖问题。

在典型的 conda 设置（在我的情况下是 Miniconda3）中，并且未设置，这会导致崩溃并出现以下错误：PYTHONHOME``PYTHONPATH

Python path configuration:
  PYTHONHOME = (not set)
  PYTHONPATH = (not set)
.
.
.
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

就我而言，解决方案是：

更改为 。bg``fg``ghidraRun.bat
在启动 Ghidra 之前设置 和 to。PYTHONPATH``PYTHONHOME``CONDA_PREFIX

下面是启动 Ghidra 的简单包装器：
setlocal

call <PATH_TO_YOUR_CONDA>\activate.bat <YOUR_VIRTUAL_ENV>
set PYTHONHOME=%CONDA_PREFIX%
set PYTHONPATH=%CONDA_PREFIX%
call <PATH_TO_YOUR_GHIDRA>\ghidraRun.bat

Thank u very much! I meet the same problem. Can publish more detail about this way! I'm not quite sure how to modify the file of ”ghidraRun.bat".

在 Windows 上遇到了类似的问题，以下是我注意到的问题以及我的解决方案：

如果我们运行的是虚拟环境，或者在任何情况下都需要任何用户环境，我们将在该环境中启动 Ghidra。但是，默认情况下会将 Ghidra 作为后台进程启动：ghidraRun.bat

call "%~dp0support\launch.bat" bg jdk Ghidra "%MAXMEM%" "" ghidra.GhidraRun %*

这里的参数使 start Ghidra 使用命令，并且基本上清除环境（只有基本的 Cmd.exe 环境传递给它）：bg``launch.bat``start``/I
if "%BACKGROUND%"=="y" (
	set JAVA_CMD=!JAVA_CMD!w
	start "%APPNAME%" /I /B "!JAVA_CMD!" %CMD_ARGS%
	...
) else (
	"%JAVA_CMD%" %CMD_ARGS%
)

这导致了我这边的DLL依赖问题。

在典型的 conda 设置（在我的情况下是 Miniconda3）中，并且未设置，这会导致崩溃并出现以下错误：PYTHONHOME``PYTHONPATH

Python path configuration:
  PYTHONHOME = (not set)
  PYTHONPATH = (not set)
.
.
.
Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
Python runtime state: core initialized
ModuleNotFoundError: No module named 'encodings'

就我而言，解决方案是：

更改为 。bg``fg``ghidraRun.bat
在启动 Ghidra 之前设置 和 to。PYTHONPATH``PYTHONHOME``CONDA_PREFIX

下面是启动 Ghidra 的简单包装器：
setlocal

call <PATH_TO_YOUR_CONDA>\activate.bat <YOUR_VIRTUAL_ENV>
set PYTHONHOME=%CONDA_PREFIX%
set PYTHONPATH=%CONDA_PREFIX%
call <PATH_TO_YOUR_GHIDRA>\ghidraRun.bat

Thank you very much. I encountered the same problem and solved it perfectly according to the method you provided.

To add on to this issue, I've had a similar one when attempting to load Ghidrathon using a Windows Store distribution of Python. The steps to reproduce are:

Install Python from the Windows Store (Tested this with 3.9/3.8)
Run the pip install command to install jep.
Run python ghidrathon_configure.py with the Ghidra directory. This will run successfully with no errors.
Attempt to load Ghidrathon via Window > Ghidrathon in Ghidra. The exception that is thrown is a JepException stating that the Python executable is not valid, and to please reconfigure Ghidrathon.

I wasn't able to find a way around this issue using a Windows Store Python version and resorted to installing it via the Python website. After that, Ghidrathon worked just fine.
Please let me know if there's any other information I can provide, as it seems that any user(?) trying to use Python from the Windows Store would have this issue w/Ghidrathon.

Just a note for others who might run into this issue.
pip install jep failed for me on Windows 11.
From the jep documentation:
To build, you need to install Microsoft Visual Studio 2015, 2017, or 2019. The Community Edition is fine. Newer versions might work too but haven't been tested.

The command completed successfully after install of VS.


feat(operation_mode_transition_manager): add package to manage vehicle autonomous mode change

Description

Add OperationModeTransitionManager that

checks the availability of the Autonomous mode change
publish the availability status
manage the operation_mode transition (Now only Manual <-> Autonomous is only supported)
send control_mode_request when the autonomous mode change is requested and the mode change is permitted.

Related links

Tests performed
Make sure related PRs are already merged in your testing environment:

https://github.com/autowarefoundation/autoware.universe/pull/1061
https://github.com/autowarefoundation/autoware.universe/pull/1198
https://github.com/tier4/tier4_autoware_msgs/pull/36
https://github.com/tier4/tier4_autoware_msgs/pull/41
https://github.com/autowarefoundation/autoware.universe/pull/1244
https://github.com/autowarefoundation/autoware.universe/pull/1201
https://github.com/tier4/tier4_ad_api_adaptor/pull/51

run planning simulator, set initial pose and goal.
send control mode MANUAL to simulator vehicle

# command 0: MANUAL, 1: AUTO
ros2 service call /control/control_mode_request tier4_vehicle_msgs/srv/ControlModeRequest "{mode: {data: 0}}"

check if the control mode is now MANUAL

# report: 1: AUTO, 2: MANUAL
ros2 topic echo /vehicle/status/control_mode

run controller to publish manual driving command and check the vehicle is moving following the trajectory

ros2 launch trajectory_follower_nodes simple_trajectory_follower.launch.xml external_target_vel:=-1.0

check if the AUTO mode is available (if the /autoware/engage is false and the vehicle is moving, make sure the AUTO is not available)

ros2 topic echo /control/is_autonomous_available

set autoware/engage = true (you can use api or send command directly)

ros2 topic pub /autoware/engage autoware_auto_vehicle_msgs/msg/Engage "{engage: 1}"

make sure the is_autonomous_available topic is true. (You can check the detailed info for the prohibit reason in debug topic).

ros2 topic echo /control/operation_mode_transition_manager/debug_info

send AUTO mode to vehicle and make sure the mode is changed to AUTO. The vehicle velocity will be changed to follow the reference trajectory speed.

# 1: DRIVER, 2: AUTONOMOUS
ros2 service call /api/autoware/set/operator tier4_external_api_msgs/srv/SetOperator "{mode: {mode: 2}}"

limitation and future work

write readme (will be in separate PR created soon)
Implementation

Currently implemented as a node, but could be integrated into the vehicle_cmd_gate as a class in the future PR because of the strong connection to the vehicle_cmd_gate
add a check function if the filter in the vehicle_cmd_gate is not active when releasing a transition mode
gate filter is not working when the mode is transitted from MANUAL to TRANSITION.

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@tkimura4 thank you. I'll merge after https://github.com/tier4/tier4_ad_api_adaptor/pull/51is merged

I confirmed that when the vechile is stopped the engage command is always acceptable if engage_allowed_for_stopped_vehicle is true
https://user-images.githubusercontent.com/59680180/177791266-99aa0184-b6b6-4b19-ac99-de8000712961.mp4

Perfectly working as expected.
Although this is a situation where we want to prohibit the engage obviously.
https://github.com/autowarefoundation/autoware.universe/pull/1246#issuecomment-1177660880


Use INSTALLED_APPS to look for unicorn components by default

PR for #210.

[x] Use INSTALLED_APPS for components by default
[x] Cache the component look-up since they shouldn't move after they are found
[ ] Test that templates work correctly (or just default to unicorn as the sub-folder)
[ ] Update startunicorn to accept application name (should this default to "unicorn" if it's missing? or should it be required?)

regarding the application name: I'd recommend keeping it as simple as possible. Keeping unicorn components in a separate app doesn't scale and adds more complexity. IF anyone wants to do that, nobody prevents him from doing so: create an empty app, create unicorn components in it and done. If you force the user (who doesn't want tnat) to create a unicorn app, or any "named" unicorn app, it's not a help, but a burden. So why not remove the setting completely? Alternatively, as help for beginners, make it mandatory for the startunicorn command: The dev has to name an app where the initial/example templates are placed in. You have to place them anywhere, so why not choose an app. Forcing him (or even encouraging him) to use a "unicorn" named app just adds unneeded complexity IMHO.

Oh, and keeping the unicorn components in a "unicorn" template subfolder is good IMHO. Others (reactor: unmaintained, etc.) do that too. Just keep in mind that, in a bigger project, it can get problematic, if two apps use a "counter" component. While normally they could be distinguished by foo/counter.html and bar/counter.html, in unicorn both would be named unicorn/counter.html. This could be solved in larges scaled projects by using unicorn/foo/counter.html - BUT: this adds complexity as well. you have to maintain an <app>/<component>.html structure beneath your templates/unicorn folder again. One solution would be to not look in templates folder, but create a separate structure as sibling to it: either "unicorn", or "components", as other projects do. Then you keep the components separate from normal templates in the first place.

@nerdoc Yep, I agree with a lot of your points. I'm in the middle of updating the startunicorn command right now and should hopefully get this change released in the next few days.


Fix loglevel dependencies

What does this PR do?

Motivation

Testing Guidelines

Additional Notes

Types of Changes

[ ] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

[ ] This PR's description is comprehensive
[ ] This PR contains breaking changes that are documented in the description
[ ] This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
[ ] This PR impacts documentation, and it has been updated (or a ticket has been logged)
[ ] This PR's changes are covered by the automated tests
[ ] This PR collects user input/sensitive content into Datadog

I'm going to close this PR due to it being stale. Feel free to re-open if something needs to be fixed! 🙇🏽