Correct boost lib path

Backend
VL (Velox)
Bug description
Currently package.sh copies libboost_* from /usr/lib/${ARCH}-linux-gnu/, after upgrading to 1.84.0,  no such file error will occur.

Actually it is installed in /usr/local/lib/:

install_boost function in velox specifies /usr/local prefix
https://github.com/facebookincubator/velox/blob/2d899d4fedf8977cfc551e5c1cec3ca79273f36a/scripts/setup-ubuntu.sh#L79
more detail log: https://github.com/wForget/kyuubi/actions/runs/8469948686/job/23206490956
Spark version
None
Spark configurations
No response
System information
No response
Relevant logs
No response

I guess the previous /usr/lib/${ARCH}-linux-gnu/libboost_*.so.1.74.0 was introduced by sudo apt-get install libboost-all-dev.
https://github.com/apache/incubator-gluten/blob/dee18e7afdffa1301954ded7b71b527232b7be43/dev/setup-qat-ubuntu.sh#L14

Velox build script installs libboost-all-dev before this patch https://github.com/facebookincubator/velox/pull/8679/files#diff-960a11a4bac38369ab5702ab18b60cac5dff8a4e14a732b4adfc75964bc23b22
You may need to run sudo apt purge libboost-all-dev on your platform

You may need to run sudo apt purge libboost-all-dev on your platform

Thanks, I will try it. BTW, libboost-all-dev was not installed in advance in my failed action.
https://github.com/wForget/kyuubi/actions/runs/8469948686/workflow


Roll Engine from a9f4883dc8ad to 8028cdd332ee (1 revision)

https://github.com/flutter/engine/compare/a9f4883dc8ad...8028cdd332ee
2021-04-09<EMAIL_ADDRESS>Roll Skia from 022636b15aff to 79aaa9b6c1c5 (5 revisions) (flutter/engine#25507)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.


Duplication bug with Extra utilities and auto crafter

When using the Auto crafter with a inactivated signal to produce iron, the signal isn't used up and can be used to duplicate 4 iron for every use inside the machine.

Sorry I don't get this. Can you describe better what you're doing?

Alright, if you place a inactivated division signal in a crafting bench normal it would give you some iron. If you add the recipe to the autocrafter to transfer it into iron, it will make the iron and retain the signal, allowing you to keep putting it in the crafter and duplicate iron.

sigil, he means division sigil.

^ Yeah lol sorry

Should be fixed in next version


Add support for TC277

Is your feature request related to a problem? Please describe.
The TC29x is working well. Infineon makes a similar processor which has less on-board memory
Describe the solution you'd like
Similar to /Ghidra/Processors/tricore/data/languages/tc29x.pspec, a /Ghidra/Processors/tricore/data/languages/tc27x.pspec should exist, resulting in the TC27x processors being available for selection.
Describe alternatives you've considered
I've constructed a TC277 definition for IDA. While the TC29x definition could work for analyzing a TC27x system, it is potentially misleading.
Additional context
I can help in whatever capacity the maintainer would like.
In #13 The spaces I pasted are actually for the TC277, the 297 has double the flash (8MB) and most likely some more ram. From what I remember, the instruction set is the same.

I'm almost wondering, due to the number of processors, if we should include a standard loading script that uses some standard C header/xml/csv/etc... whatever format to add the global labels and sections.
I do not know how well this work though as the few examples I've done so far for TC1xx and TC29x didn't have section lengths,  though I guess that info could be generic for the broader platform as the section is either there or not, but typically the same address (?).
Reasoning is I parsed the the full header file for TC29x and it was 25k lines of XML (1.8MB), (the TC1xx were ~5-6k lines each).  I ended up chopping off alot, which who is to say what I cut out/left in is useful or not.
I don't know how well the Ghidra devs will react once more and more pspec files are being committed.

The .pspec files were originally intended to cover special labels for processor variants.  There has been much discussion about alternate mechanisms.  For example the variants of the MSP430 are in the hundreds.  As long as the base .sla file is the same it isn't too big of an issue.  Most of the time the basic generic registers stay in the same place, with special registers variants that change.
Two .pspec variants, using the same .sla file but with different pre-defined memory sections shouldn't be an issue.  Adding a large number of symbols probably isn't that big of an issue as long as there isn't a large number of pspec files with a large number of symbols in each.
One possibility is to parse the header files into a data type archive that define the values for particular registers in each processor variant, although this would depend on the header files and how they define the locations.  I've tried this on various toolchains and it has worked well sometimes.  Usually only used for an exact variant not all variants.
Any Define that is a value is turned into an enum of that name with the value.  An enum can be applied as a label to a program at the address of the enum value.
The .gdt files can be created by other means than parsing header files as well.  The real downside is it isn't in a text readable format.  We're currently re-thinking the .gdt files as well, since a large number of .gdt files could be problematic.
We are considering adding data types that are defined to be at a particular address to the data types manager (data type archives too), similar to the at(address) in gcc.
int var __attribute__((at(0x40001000)));

For address space variants where the processor memory varies, usually the base processor spec will suffice as the full addressing doesn't change, just the memory blocks available changes.  Normally just loading in the bytes upon import for the particular example is good enough.
Is suppose there could be a definition of memory segments too as a data type too.
Maybe:
undefined RAM[0x8000] __attribute__((at(ram:0x0));

If the processor mechanics (adressing, etc...) change you can define context variable bits to control behavior that get assumed to a value in the .pspec (x86 pspecs are an example).  Then the base compiled .sla file can be used without a full second compilation.
This issue will show up for syscalls as well, as the syscall numbers in windows can change with each OS version.  We will most likely develop some sort of OS personality that can be set outside of the processor specification files.  Some of the proposed solutions are thought to lend itself to processor variants as well.
Side note: In 9.1 you will be able to add additional address spaces in an "other" space with a given name.  This will be used for the syscalls to get to the correct location, but could be used for SPI memory, or really any other non-standard memory you want.  The trick will be creating references to them.

Thanks for the detailed response @emteere

@syntroniks the core of Tricore got merged into upstream/master today, just FYI.  Still thinking about the best solution for this though

That's great news! In the coming months I hope to pop back into tricore ghidra.
It sounds like there are a few options at the moment. I'm not intimately familiar with .pspec and .sla and .gdt files but would happily lend a hand for expanding processor address space information.
We routinely work with TC297/TC277
TC1791
TC1766
TC1767
TC1796
TC1797
If there is an easy copy/paste solution (i.e. choose a tricore processor arch, copy this file, update these addresses/registers) it should make adding support to new processor variants pretty painless. Scripts can take processor definition files (pretty much headers from a compiler toolchain) and pop that information in.
Thanks for the update!


Implement end-to-end tests

There needs to be a GitHub action on this repository that uses action-spicedb for end-to-end testing of the CLI commands and flags.

This likely would have caught #417 if we'd had them in place. I'm gonna treat this as higher-priority.


[ELWCHR] Chain Reaction - Unable to Play or Load Puzzles

Module Information

Identifier: ELWCHR
Module Name: Chain Reaction
Version: 1.0

Describe the bug
Module does not allow you to play and (L)oad Puzzle command is not present (doesn't seem to recognize SYSOP access)
File ELWCHRPZ.DAT is created from .VIR and creates an .EMU file which contains puzzles
To Reproduce
Steps to reproduce the behavior:

Load Module
Enter Module
Try to (P)
"Sorry, you've seen all the puzzles"

Expected behavior
Ability to Play Game
Screenshots

From Manual: "Note that Sysops may import a puzzle file (seven words per line, separated by
commas, with no spaces) by using the (L)oad option."
Software Information:

OS: Windows 2019 Server Standard
Telnet Client: NetRunner

Deleted *.EMU and reloaded, working now


Release 0.20 dependabot

Description of changes:
Manual back port of https://github.com/aws/eks-anywhere/pull/8584
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


viewer process still running after exit

I notice this most when using the cli. I've seen it on trunk and 2.8RC. Still working on a reliable reproducer and will post a script as soon as I can. In the meantime, developers may want to check for runaway processes when finished with a VisIt session.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 1978
Status: Pending
Project: VisIt
Tracker: Bug
Priority: High
Subject: viewer process still running after exit
Assigned to: -
Category: -
Target version: -
Author: Kathleen Biagas
Start: 09/10/2014
Due date:
% Done: 0%
Estimated time:
Created: 09/10/2014 05:33 pm
Updated: 09/24/2014 03:50 pm
Likelihood: 3 - Occasional
Severity: 5 - Very Serious
Found in version: 2.8.0
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
I notice this most when using the cli. I've seen it on trunk and 2.8RC. Still working on a reliable reproducer and will post a script as soon as I can. In the meantime, developers may want to check for runaway processes when finished with a VisIt session.
Comments:
This is doing it for me on my local linux machine, on trunk. I've shortened the path to the data for easier read.If you put this in a script, don't add the 'exit' command to the script, seems to only happen when I type exit at the cli prompt. I've tried with trunk built against VTK 6.0 and 6.1I can more consistently reproduce if the viewer has been 'idle' for a few seconds.Doesn't show up on top, so I didn't notice it before, but I also have an instance of python running:'python ./frontendlauncher.py ./visit v 2.9.0b viewer ... This may be related. I have noticed times when running from the gui, and exiting via File>Exit, all of the windows close, but the gui and viewer processes are still running (as well as the python launcher for each). I can CTRLC in the terminal window to end them. I can reliably reproduce this on my local linux box, 2.8RC, opening arbpoly.silo, drawing a Mesh plot, then exiting.

Either duplicate or very closely related to #3064


My query result on the ticket page is incorrect

If you choose to be assigned, all the data is found, and the rest of the status queries are normal

This problem has been fixed in version  dgiot-dashboard 4.4.0. Please update the front end to 4.4.0


Support for @Provider discovery in MP server (#1432)

Adds support for manual registration of providers (via Builder), as well as automatic discovery and registration of CDI beans with @Provider annotation

I've added the tests for new functionality, as we discussed, and hit the bug with MBR/MBW generic type argument processing when Weld proxies are used. I'll open a bug against Jersey for that, so we can track it.
Apart from that, I've changed some of the server semantics a bit in order to be able to mix explicit applications with auto-discovered resources and providers (implicit application).
Basically, you can now register one or more Application classes explicitly, just like before, but if you have explicitly registered or auto-discovered resources and providers in addition to those, they will be packaged into an implicit/default application and added to the applications list. That way it's not "either/or" as it is at the moment -- you can have both at the same time.
The main reason I did it was so I can have both in the test project, but I do think it makes sense in general -- it allows you to implement your own app/service using auto-discoverable resources and providers, but also add explicit apps defined elsewhere.
I've also changed ServerCdiExtension to support discovery of @RequestScoped root resources (which is an issue I've hit before but didn't know why they are not being picked up automatically), and changed it discovers everything that's discoverable, not either applications or resources/providers.
Anyway, let's discuss tomorrow and decide how to proceed.

Opened https://github.com/eclipse-ee4j/jersey/issues/4400 to track the issue with CDI-managed MessageBodyReaders/MessageBodyWriters.

The combination of discovered resource classes and application is intentionally not possible. You can add an auto-discovered application that explicitly returns resource and provider classes and combine it with registered applications
You cannot have registered application classes and combine them with discovered resources, as that may create unexpected endpoints.

Do not merge this PR please, see #1448


[backend] fixing page flows Fixed

Description
flow is now fixed
Issue
Issue Link resolve #142

@RohitGupta1237  @Kajol-Kumari can you please check


Calling layout.fix() and layout.fixSidebar()

Hello.
Sometimes my sidebar isn't refreshed when new data is added. The data is added via a computed property, from Vuex. If I see the HTML source, I see that the <li> items are there. But the sidebar isn't showing them.
I've investigated and it seems I'd have to call layout.fix() and layout.fixSidebar() for this to work. How can I accomplish this from Vue?

I'm get similiar problem, but my problem is when I change page content the height size get cutted out


something about #define

i m a newer.i have read the greatest.h,there is something that i dont understand.There are lines like  #define PASS           GREATEST_PASS
#define GREATEST_PASS() GREATEST_PASSm(NULL)
in that why don't #define PASS() GREATEST_PASSm(NULL)?
is there something important or define for a certain purpose?

It happens in two layers because they serve different purposes:
#defineing PASS to GREATEST_PASS is in a block near the end, which #defines a bunch of aliases. It's convenient to use SUITE, PASS, ASSERT, etc. rather than prefixing everything with GREATEST_, but those aliases can be turned off (by #defineing GREATEST_USE_ABBREVS to 0) in case another library also provides something called PASS, ASSERT, or whatever. I don't want the name conflict to break someone's project.
The #define for GREATEST_PASS() is making it equivalent to GREATEST_PASSm(NULL) -- it's like calling GREATEST_PASSm with a default argument of NULL. That argument is used for setting a custom message. I don't think PASSm gets used a lot, but it's helpful to say something like FAILm("not found"), rather than just FAIL(), because that message appears in the test runner's failure details.

Thanks for your detailed answer.To be honest,i haven't expected your answer so soon.Thank you very much.


[question] mqtt code 112 not translated to text

Just curious and It is not a problem for me but I notice that all of the 112/0/# are not translated to text like all the other codes e.g 98/0/currentMode. Is there a real reason for this?

Because configuration CC parameters are provided by manufacturers and are only identified by a number


PR: issue-64-explain-why-we trim-each-filter

Updated src/filters.js to explain why we trim each filter.
Make sure to fill out everything below — your pull request won't be merged until you do!
Check all applicable boxes below (put an x in between the square brackets, with no spaces)

[x] This is to fix an issue. Issue #: #64
[ ] If I modified anything other than comments, I ran npm run build and npm test

Summary
Explain your pull request

Perfect! Thank you!


Background Palettes Automatic Visual issues

Hello, I was testing the beta of 4.0.0 and I noticed a bug.
When I set the background palettes scene option to automatic, it takes the palettes of the original image correctly. However, when testing the scene in play, the dialogue and menu events are not visible. (They still work, they just can't be seen).
This error does not happen with the scene in manual mode.
Note: I think it happens when the dialog is on black tiles, because with the placeholder image this error does not happen.

Hi @NeidenAtron are you able to share an image that is showing this issue? I get the feeling that the image probably contains more than 7 unique colour palettes causing it to overwrite the 8th palette (which is the one used dialogue and menus) but it would be good to confirm.

I don't know why, but in beta 2 this problem no longer happens. I did exactly the same as in beta 1. I recently tested the automatic background palettes, the 3 color modes. (Monochromatic, Monochromatic+color and the only color mode) but now the UI is displayed without problems. I also thank you for your help. (Sorry, my knowledge of English is not that advanced).


Auto Imports not shown for npm local dependency

From @vitalysoftech on February 20, 2018 8:54

VSCode Version: 1.20.1.
OS Version: Windows 7 Professional SP1.

Steps to Reproduce:

Create "package1" folder and run "npm init" inside. Use all defaults, but for main entry point use "index.ts".
Add index.ts to the folder and add simple content there:

export function sayHello():string
{
    return "Hello";
}

Go one folder up and create "package2" folder (it must be in the same folder as "package1").
Run "npm init" inside "package2". Use all defaults, but for main entry point use "index2.ts".
Add empty "index2.ts" file.
Inside "package.json" for "package2" add the following depedency:

"dependencies": {
    "package1": "file:../package1"
}

Inside "package2" folder run "npm install". Make sure that "package1" link was added inside node_modules.
Open "package2" folder in VS Code.
Open "index2.ts" file for editing and start typing "sayHello". Notice that editor doesn't suggest you to import sayHello from "package1", but ideally should to. index.ts file from package1 is written in TypeScript so editor should have all the required information for the hint.

Is it a place for improvement? How can I make VS Code showing me hints? I want to have a multi-package workspace and having no hints for imports makes it hard to develop.
Thanks in advance.

Does this issue occur when all extensions are disabled?: Yes.
Copied from original issue: Microsoft/vscode#44019

Tested with Ts 2.8.0-dev.20180228
Confirmed that no auto-imports are shown in this case. IntelliSense seems to work fine once you add an import

PRs welcomed for supporting file:.. patterns.

Has anybody found any workarounds for this?

Closing this due to the limited user interest shown over the past two years


Please add pixi to the scoop.sh registry

Problem description
Scoop is a command line installer for Windows.
Please consider adding pixi to the Scoop registry.
A few attempts have been made by the community, but this requires installing those Scoop "buckets".

https://github.com/okibcn/ScoopMaster/blob/master/bucket/pixi.json
https://github.com/anderlli0053/DEV-tools/blob/master/bucket/pixi.json

It would be nice to have pixi in the main Scoop bucket.
Here is a basic Scoop Application manifest that seems to work for me:
{
  "homepage": "https://prefix.dev/",
  "description": "Package management made easy",
  "version": "0.27.1",
  "license": "BSD-3-Clause",
  "architecture": {
    "64bit": {
      "url": "https://github.com/prefix-dev/pixi/releases/download/v0.27.1/pixi-x86_64-pc-windows-msvc.zip",
      "hash": "459d559f0424aab1bdb44122bed8df2d4365c297d6ec8da4af5d980929282575"
    }
  },
  "bin": [ "pixi.exe" ],
  "env_set": {
    "PIXI_HOME": "$dir"
  },
  "checkver": {
    "github": "https://github.com/prefix-dev/pixi"
  },
  "autoupdate": {
    "architecture": {
      "64bit": {
        "url": "https://github.com/prefix-dev/pixi/releases/download/v$version/pixi-x86_64-pc-windows-msvc.zip"
      }
    }
  }
}

Feel free to create a PR!

@ruben-arts Thanks. Will keep this around as a reference implementation.


content_scripts defined in manifest.json won't update after HMR without a full reload of the web extension

I did some experiments on this, but it's impossible to improve this case on our side. (content_scripts defined in manifest.json).

@Jack-Works what are your thoughts on making a workaround for this? for cases where HMR is impossible, I'd like to fallback to a full page reload. I did some tests but applying window.location.reload() to content_scripts from manifest runs into an infinite refresh loop.

@cezaraugusto The JS file specified in the manifest.json will not update even if the webpage is reloaded. It has to be an extension reload. I tried chrome.scripting API to re-register the content script it also doesn't work. I have no clue for this now


HDH-321-migrate-coveo-token-generator-api-from-next-harness-io-to-de…

…veloper-harness-io
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: __________________________________
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Excessive changes were included due to the hard reset earlier today. @rohanmaharjan100 pls rebase or close/reopen PR, as appropriate.


update week list of models included in ensemble and code generating it

#149

Ready for re-review @dylanhmorris
Made slight changes to what you proposed. I included model_ids for all models submitted in a week in the csv file (renamed accordingly) and filter by designated_model when creating ensemble.
This will generate a weekly list of models submitted with a column indicating whether or not it was used for ensemble which can be used for the visualization website.

Nice idea, thanks!


Use directExecutor for local merge

TransportDistributedResultAction already runs the operation threaded, so there
is no need to dispatch to an additional thread.

ack


props defined by withDefaults and defineProps , use props in template have warning

use reactive or ref  variable in template have correct info ,It was normal until I reinstalled node_modules

We temporarily close this due to the lack of enough information. Please provide a minimal reproduction to reopen the issue. Thanks.


Does it work on MacOS?

Looking for something simple on MacOS outside of using dropdelegates

Ooh thanks for pointer! ❤ Thank ll give it a whirl and reopen if not.

Hi Joel, Hope you ate doing good,  i want this card code in  storyboards insted of swift UI i am new to ios please can you hepl me.. I  have one task that is example if i have 12345  cards i have selected card 4 if drag  and placed in b/w 1 and 2 cards , selected card should come one top of half 1 and below 2.


Kubernetes v1.20 documentation does not mention AuditSink.

Information about AuditSink is missing in documentation (Auditing -> Audit backends).

Hmm, there's also no AuditSink in https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/

AuditSink is deprecated @d0x1g0x1
Maybe https://v1-18.docs.kubernetes.io/docs/tasks/debug-application-cluster/audit/ is relevant?
/kind support
/retitle Kubernetes v1.20 documentation does not mention AuditSink.

@sftim I don't see public information about deprecation of AuditSink feature and differences between 1.18 and 1.20 codebase.

https://v1-19.docs.kubernetes.io/docs/setup/release/notes/ mentions the deprecation of dynamic auditing and the auditregistration.k8s.io/v1alpha1 API group. As this was an alpha feature the deprecation was not listed as a major change.

/close


Always use dashboard_data ImportLog when choosing what to display

A dashboard_data ImportLog is created at the very end of the monthly
import, while the prescribing ImportLog is (now) created once
convert_hscic_prescribing has been run.

Closing in favour of #2583.


Alert on clicking on download button

@AmanS369 please create an issue and link that to this PR.
Also, add a cancel button to cancel the download and change the text to Do you want to download Drifty?

Now i have added so that user can confirm it downlaoding

Add hackobeterfest-accepted label

Please add Hacktoberfest fest label to my issue
On Sat, 22 Oct, 2022, 10:50 Saptarshi Sarkar, @.***>
wrote:

@.**** approved this pull request.
LGTM 👍. Thanks for contributing.
@AmanS369 https://github.com/AmanS369 Please leave a star on this
project if you liked contributing to it.
—
Reply to this email directly, view it on GitHub
https://github.com/SaptarshiSarkar12/Drifty/pull/138#pullrequestreview-1151801684,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AV4PX7OMB2ZXJVBFJNLKZL3WEN2RXANCNFSM6AAAAAARLLIPLQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Please add Hacktoberfest fest label to my issue
…
On Sat, 22 Oct, 2022, 10:50 Saptarshi Sarkar, @.> wrote: @.* approved this pull request. LGTM 👍. Thanks for contributing. @AmanS369 https://github.com/AmanS369 Please leave a star on this project if you liked contributing to it. — Reply to this email directly, view it on GitHub <#138 (review)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AV4PX7OMB2ZXJVBFJNLKZL3WEN2RXANCNFSM6AAAAAARLLIPLQ . You are receiving this because you were mentioned.Message ID: @.***>

Already added @AmanS369 .


KOGITO-862: Support for binary content

Adds support to binary content in Resource Content Service.
A new object can be passed as parameter to method get: Options. Right now the only supported option is type, which can have values binary and text.
if users request a binary content then the resource content binaries will be encoded in a base64 string.
Example:
resourceContentService.get("/someContent")    <<< returns the content in text representation;
resourceContentService.get("/someContent", {type: "binary"}) << returns the content bytes in a base64 string

Later users can decode the base64 content or use it directly in components that support it, for example: images. In a img element you can set the content as base64 string using:
 <img src="data:image/png;base64, {img  base64 content}">

Please merge this PR with the GWT bridge PR: https://github.com/kiegroup/appformer/pull/886

Hello Tiago,
I added a couple of commits targeting each issue your found.
Since @romartin did a great job pushing the service tasks support to master, I went ahead and tested with a real image and fortunately  it working greatly!

Roger, I pushed my changes to my branch as a PoC:
https://github.com/kiegroup/kie-wb-common/compare/master...jesuino:KOGITO-862?expand=1
Notice I didn't work to correctly support images, I had to hard code PNG type, because AFAIK GWT used to solve media type for base64 contents, now we need to make it manually. The only issue I see is that service tasks are removed when I save the process.
Once that is solved we will have end to end service tasks support!

Hello @tiagobento , thanks for the review - I added a new commit with the changes
https://github.com/kiegroup/kogito-tooling/pull/60/commits/68ea61e929d09a5165b93bf35abb3090ae8d4763


Fixes regarding VOLUME_DELETE events resulting from account deletion

New version of #1491.
Original Description
New version of #1373, but updated for the 4.7 branch with another fix that allows it to properly find expunged root volumes. This is a bug fix, which is why we target the 4.7 branch.
Original pull request:
Fixes regarding usage event emission.
UsageEventUtils was previously not checking deleted accounts, which meant that if an account was deleted that had some resources running on it, those resources would get destroyed without emitting any events.
Furthermore, the VOLUME_DELETE event of ROOT volumes is the responsibility of the UserVmManager, which gets circumvented when expunging resources following the account deletion. Added a check to the AccountManager which catches the ROOT volumes that need to be deleted and emits events for them.
To test this: Create a new user. As that user, create and destroy an instance. This should cause the VM_CREATE, VM_START, VM_STOP, VM_DESTROY, VOLUME_CREATE, and VOLUME_DELETE events to be emitted.
Create a new instance as the same user. Log in as admin, and delete the user. The same set of events should be emitted, and there should be no duplicate DELETE events for the ROOT volume of the previous instance.

@blueorangutan kick

A Trillian-Jenkins job has been kicked to build packages and start testing. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian repo: http://packages.shapeblue.com/cloudstack/pr/1624

@ProjectMoon I would like to get this PR merged for the <IP_ADDRESS> release, but I need to cut an RC ASAP.  Will it be possible for you to address the PR comments in time?

Has been rebased against latest 4.8 and the TODO comments removed. The map was left alone though.

@ProjectMoon both the Jenkins and Travis builds are failing.  Could you please investigate?

Jenkins build log has vanished into 404 oblivion. Will see what happened with Travis (https://travis-ci.org/apache/cloudstack/builds/154436801).

Have rebased to latest 4.8. Travis build failed with what looks like Unable to execute /home/travis/build/apache/cloudstack/developer/target/db/templates.simulator.sql: Unknown column 'state' in 'field list'. Don't think it's related to this. Will see what happens with the latest 4.8 code.

Until #1654 is fixed and merged, all 4.8 will fail due to db upgrade failures. /cc @jburwell

@ProjectMoon we have a code review LGTM on #1654, and have someone lined up to test it and provide the second LGTM.  We should have the second LGTM by 1 Sept 2016 at which time you can re-kick this PR.

LGTM for code review.  Do we have someone testing for the second LGTM?

Alright. I'll rebase it once #1654 has been merged.

LGTM. Thanks @ProjectMoon as soon as #1654 is merged, we'll get this merged as well. Do we have any regression tests results, especially around the changed code?

@ProjectMoon please rebase now, PR 1654 has been merged now. DB upgrades should not cause errors.

The pull request has been rebased.

Looks like it's ready for merging now.

@ProjectMoon we need a test LGTM.  I inquired yesterday -- do you have someone lined up to test it?

We can have someone test it. Are you looking for results of a manual test, reproduction tests, or something automated? A manual test is probably the best from our side because we don't really have the time to write any unit/integration tests at the moment beyond what already exists in this PR.

@blueorangutan kick

@ProjectMoon I want to get this PR into <IP_ADDRESS>, <IP_ADDRESS>, and <IP_ADDRESS> for which we will be cutting RCs on 25 Sept 2016.  Tests should be the entire Marvin smoke test suite against VMware, KVM, and XenServer, as well as, the test_account component test.
Also, is it possible to automate the test procedure described in the description?  Given the amount of change in the project, we want to keep manual testing to an absolute minimum.
Finally, is there a JIRA ticket for this bug?

I started BVT run(xenserver, advanced zone) on this PR. @cloudmonger will post the results here in approx. 4 hrs.

ACS CI BVT Run
Sumarry:
Build Number 102
Hypervisor xenserver
NetworkType Advanced
Passed=99
Failed=2
Skipped=4
Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
Failed tests:

test_service_offerings.py

ContextSuite context=TestServiceOfferings>:setup Failing since 14 runs

test_volumes.py

test_01_create_volume Failed

Skipped tests:
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_3d_gpu_support
test_deploy_vgpu_enabled_vm
Passed test suits:
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_deploy_vm_iso.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_ssvm.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_disk_offerings.py

ACS CI BVT Run
Sumarry:
Build Number 112
Hypervisor xenserver
NetworkType Advanced
Passed=101
Failed=2
Skipped=4
Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
Failed tests:

test_deploy_vm_iso.py

test_deploy_vm_from_iso Failing since 3 runs

test_vm_life_cycle.py

test_10_attachAndDetach_iso Failing since 3 runs

Skipped tests:
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_3d_gpu_support
test_deploy_vgpu_enabled_vm
Passed test suits:
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_ssvm.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_disk_offerings.py

This branch has been rebased to latest 4.8.

Iso tests failed as the iso url wasnt accessible from our test environment. All is well here.
@ProjectMoon were there any code changes in your latest rebase? (meaning, do we have to run BVT again?)

No code changes, just updating the commits under it.

@ProjectMoon can you squash your changes, and rebase against latest base branch?

The commits have been squashed, commit message updated to make sense (I think; let me know if it's not right), and rebased against latest 4.8.

I started another test run on this. If it goes through, I will merge this tonight.

ACS CI BVT Run
Sumarry:
Build Number 116
Hypervisor xenserver
NetworkType Advanced
Passed=103
Failed=2
Skipped=5
Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
Failed tests:

test_deploy_vm_iso.py

test_deploy_vm_from_iso Failing since 4 runs

test_vm_life_cycle.py

test_10_attachAndDetach_iso Failing since 4 runs

Skipped tests:
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_3d_gpu_support
test_deploy_vgpu_enabled_vm
Passed test suits:
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_snapshots.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_ssvm.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_routers_network_ops.py
test_disk_offerings.py

@blueorangutan package

@jburwell a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos6 ✔centos7 ✔debian. JID-88

Iso failures are due to URL access issues. All good here. merging this now.

This is pushed to 4.8 but not merged fwd.
looks like 4.8 is not fwd merged for some commits and there are conflicts now. Need to investigate further. Will continue on monday.

It is now fwd merged to all the branches. Thanks


Documentation Invalid Link

In the project README, you have:

See the website for detailed documentation and usage instructions.

However, that link results in a 404. Were you aiming for https://copper-leaf.github.io/kotlin-json-forms/wiki/usage-guide/ instead?

Nice catch, yes that's the correct link. I've updated the README


feat: Improve Twoslash Popover Display

Why:
Closes:#3361
I have modified the popover to appear above the code block, which was previously being obscured by it.
it has been implemented, but I would appreciate some help with refining the design details. 🙏🏻

What's being changed (if available, include any code snippets, screenshots, or gifs):
https://github.com/user-attachments/assets/3489957c-5602-4b2d-84dc-3badeeae2a58

Check off the following:

[ ] I have reviewed my changes in staging, available via the View
deployment link in this PR's timeline (this link will be available after
opening the PR).

@Zih0 I did a bit of refactoring of your implementation in https://github.com/shuding/nextra/pull/3533/commits/5004cf8705366114cdf5db7c53cdc1acded27af1
can you take a look if it looks good to you?

Sorry for the late reply, I submitted the PR in the middle of the night Korea time!
Thanks for the good review and changes 😊

I pushed a commit which fixes console warnings, would you like to try it if everything looks good for you? Also what do you think about this comment

Maybe do you know a way to improve this Popup as well?
Currently it's hidden since <pre> has overflow: auto I guess?

Yes, I think so too.
so.. I tried to completionCompose.
I tried adding { open: true } to properties and wanted to use it in the Popup component, but it seems that properties isn’t working. 😢
completionCompose: ({ cursor, popup }) => [
        {
          type: 'element',
          tagName: 'Popup',
          properties: {},
          children: [
            {
              type: 'element',
              tagName: 'PopupButton',
              properties: {},
              children: [cursor]
            },
            {
              type: 'element',
              // I think we need to add a new popup panel component with the initial value set to `true`
              tagName: 'CompletionPopup',
              properties: {},
              children: [popup]
            }
          ]
        }
      ],

@Zih0 I think they just added comments to have more lines
https://github.com/user-attachments/assets/9d0e2f16-155c-4eb6-bec9-5afcb73d2082
https://shiki.style/packages/twoslash#rendererrich
https://github.com/shikijs/shiki/blob/main/docs/packages/twoslash.md#rendererrich

@dimaMachina Thank you for maintaining Nextra! 👍

@Zih0 Thanks for the good words and amazing contributions like that! Nextra 4 will come very soon with App Router and Turbopack support, Nextra 3 is just a bridge to the future 😅


python310Packages.pymavlink: 2.4.31 -> 2.4.33

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pymavlink is: "Python MAVLink interface and utilities"
meta.homepage for python310Packages.pymavlink is: "https://github.com/ArduPilot/pymavlink"
meta.changelog for python310Packages.pymavlink is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 2.4.33 with grep in /nix/store/qx7lr9y1wb3g8mmv1b0kdz7ybrdam1dg-python3.10-pymavlink-2.4.33
found 2.4.33 in filename of file in /nix/store/qx7lr9y1wb3g8mmv1b0kdz7ybrdam1dg-python3.10-pymavlink-2.4.33

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
mavproxy
python310Packages.pymavlink
python39Packages.pymavlink

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qx7lr9y1wb3g8mmv1b0kdz7ybrdam1dg-python3.10-pymavlink-2.4.33
ls -la /nix/store/qx7lr9y1wb3g8mmv1b0kdz7ybrdam1dg-python3.10-pymavlink-2.4.33/bin

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

3 packages built:

mavproxy
python310Packages.pymavlink
python39Packages.pymavlink

Maintainer pings
cc @lopsided98 for testing.

#186868


Response structure

Deriv api has some standard fields that would be nice to replicate for consistency:

echo should return original request in response body
passthrough we return as is in response body

it also should be applied to errors that we forwarding(when on of steps failing for aggregation calls)

Last point about forwarding extra fields from error response is not relevant anymore, in current implementation we only forward error field


[TC-IDM-10.4] Giving error on "PICS OTAR.xxxx" was not found" which are not included in the pics list.

Summary Title:
An element found on the device, but the corresponding PICS OTAR.S.A0001 was not found in pics list.
Logs:
[MatterTest] 03-07 05:07:50.612 INFO
Problem: ProblemSeverity.ERROR
test_name: PICS check
location:
Endpoint: 0,
Cluster:  42 (0x2a) OtaSoftwareUpdateRequestor
problem: An element found on the device, but the corresponding PICS OTAR.S was not found in pics list
spec_location:
[MatterTest] 03-07 05:07:50.613 INFO
Problem: ProblemSeverity.ERROR
test_name: PICS check
location:
Endpoint: 0,
Cluster:  42 (0x2a) OtaSoftwareUpdateRequestor,
Attribute:0 (0x00)
problem: An element found on the device, but the corresponding PICS TC-IDM-10.4-fail-endpoint0.txtA0000 was not found in pics list
spec_location:
[MatterTest] 03-07 05:07:50.613 INFO
Problem: ProblemSeverity.ERROR
test_name: PICS check
location:
Endpoint: 0,
Cluster:  42 (0x2a) OtaSoftwareUpdateRequestor,
Attribute:1 (0x01)
problem: An element found on the device, but the corresponding PICS OTAR.S.A0001 was not found in pics list
spec_location:
[MatterTest] 03-07 05:07:50.614 INFO
Problem: ProblemSeverity.ERROR
test_name: PICS check
location:
Endpoint: 0,
Cluster:  42 (0x2a) OtaSoftwareUpdateRequestor,
Attribute:2 (0x02)
problem: An element found on the device, but the corresponding PICS OTAR.S.A0002 was not found in pics list
spec_location:
[MatterTest] 03-07 05:07:50.614 INFO
Problem: ProblemSeverity.ERROR
test_name: PICS check
location:
Endpoint: 0,
Cluster:  42 (0x2a) OtaSoftwareUpdateRequestor,
Attribute:3 (0x03)
problem: An element found on the device, but the corresponding PICS OTAR.S.A0003 was not found in pics list
spec_location:
[MatterTest] 03-07 05:07:50.615 INFO
Problem: ProblemSeverity.ERROR
test_name: PICS check
location:
Endpoint: 0,
Cluster:  42 (0x2a) OtaSoftwareUpdateRequestor,
Command:  0 (0x00)
problem: An element found on the device, but the corresponding PICS OTAR.S.C00.Rsp was not found in pics list
spec_location:

Or we manually add it to the pics xml

For 1.3 SVE, please ignore this specific failure. If a device fails with only this error message mark the test case as passed.
Second option is to manually add this PICS to the pics XML package and participants will select this PICS as well. For the official 1.3 release we could follow this option.

@xilizhang1  can you try to manually update the PICS XML package and try to run and see if the test passes ? For the official release we will update the PICS XML package.. cc @Survensa @cjandhyala

we can pass the testcase after try to manually add these pics items.

I put up a PR to ignore these pics for now. https://github.com/project-chip/connectedhomeip/pull/32510. @raju, it's up to you how you want to fix this. I think this seems reasonable for now. We'll just have to know that the PICS files for 1.3 devices won't have OTA marked, but that's not any worse than what we have currently.


Compare-Object returns incorrect results

Compare-Object returns incorrect results
Steps to reproduce
I have run through several permutations of the steps below, but no matter how I change things around, I keep getting the wrong results from the Compare-Object cmdlet.
Import-Module -Name MicrosoftPowerBIMgmt -MaximumVersion 1.0.613;
Get-Command -Module MicrosoftPowerBIMgmt* -CommandType Cmdlet | SELECT Name, Source |
Export-Excel Import-Excel C:\temp\PowerBI_Commands.xlsx -WorksheetName 1.0.613;
Remove-Module MicrosoftPowerBIMgmt*

Import-Module -Name MicrosoftPowerBIMgmt -MinimumVersion 1.0.726;
Get-Command -Module MicrosoftPowerBIMgmt* -CommandType Cmdlet | SELECT Name, Source |
Export-Excel Import-Excel C:\temp\PowerBI_Commands.xlsx -WorksheetName 1.0.726

$613Commands = Import-Excel C:\temp\PowerBI_Commands.xlsx -WorksheetName 1.0.613 | SELECT Name
$726Commands = Import-Excel C:\temp\PowerBI_Commands.xlsx -WorksheetName 1.0.726 | SELECT Name

$Diffs = Compare-Object -ReferenceObject $613Commands -DifferenceObject $726Commands -PassThru

$Diffs

Expected behavior
Export-PowerBIDataflow
Get-PowerBIDataflow
Get-PowerBIDataflowDatasource
Set-PowerBIDataset
Get-PowerBIWorkspaceMigrationStatus

Actual behavior
Name                             SideIndicator
----                             -------------
Set-PowerBICapacityEncryptionKey =>
Set-PowerBIDataset               =>
Set-PowerBITable                 =>
Set-PowerBIWorkspace             =>
Switch-PowerBIEncryptionKey      =>

Environment data
I can repro this on both PSCore 6.2.2 & PSCore 7-Preview3
Name                           Value
----                           -----
PSVersion                      7.0.0-preview.3
PSEdition                      Core
GitCommitId                    7.0.0-preview.3
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0ΓÇª}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Since you're using Select-Object and not Select-Object -ExpandProperty, you're comparing arrays of [pscustomobject] instances (that have a .Name property), not strings (mere names).
You have two options:

Use Select-Object -ExpandProperty Name

Add -Property Name to your Compare-Object call.

As for the specific symptom:
[pscustomobject] instances as a whole (which is what you did) currently all compare the same, irrespective of their specific structure:
PS>  Compare-Object ([pscustomobject] @{ foo = 1 }) ([pscustomobject] @{ bar = 2 }
# no output, because the [pscustomobject] instances are considered equal

I have not verified this, but I think that it is a consequence of #6163 (.ToString() invoked on [pscustomobject] instances returns the empty string, and since all reference-type instances are compared by their .ToString() values, all [pscustomobject] instances compare the same).

Excellent info @mklement0, thanks for the assist!  Looks like I have 3 options.  I added  -Property Name to my Compare-Object and it came back with the correct results.
Compare-Object -ReferenceObject $613Commands -DifferenceObject $726Commands -PassThru -Property Name


Release version 2.1.0 on Puppet Forge

The latest available version on Puppet Forge currently is 2.0.0 but in VCS it is 2.1.0. Please release version 2.1.0 on Puppet Forge too.

Also consider integrating puppet-blacksmith to automate this.

Released: https://forgeapi.puppetlabs.com/v3/files/petems-swap_file-2.1.0.tar.gz

Thanks. :-)


Circular should be determined by type and not circular component

A design should be circular when there is the circular SO type and not by the presence of a special circular component.

Punting this to 2.3 due to time constraints.

Not sure about.  Need to think because backbone is a part.

Not sure about.  Need to think because backbone is a part.


Kirki utility functions producing unexpected results

Issue description:
I have been using Kirki color functions for a while and have noticed since the last update the colors being generated are substantially different from what they were before.
Here's how I usually use them:
.woocommerce-checkout-review-order
            {
                background: <?php echo Kirki_Color::adjust_brightness($page_bg, 15); ?>;
            }

The goal here is to take the bg color and brighten up a bit to ensure contrast to the background. What im getting now is the exact opposite, im getting a much darker color than the original im modifying.
Version used:
2.2.3
Using theme_mods or options?
theme_mod
Code to reproduce the issue (config + field(s))
Kirki::add_field( 'kirki_options', array(
	'type' => 'color',
	'section' => 'colors_generic',
	'settings' => 'page_bg',
	'default' => '#f2f3f0',
	'label'    => __( 'Page Background', 'wip' ),
	'description' => __( 'Sets the main background for entire page.', 'wip' ),
	'output' => array(
		array(
			'element'  => '
                .site-container
				',
			'property' => 'background-color'
		),
	),

) );

function mw_dynamic_colors_css() {

    $page_bg          = kirki_get_option('page_bg');

?>

<style type="text/css">
.woocommerce-checkout-review-order
            {
                background: <?php echo Kirki_Color::adjust_brightness($page_bg, 15); ?>;
            }
}
</style>

    <?php

}

add_action( 'wp_head', 'mw_dynamic_colors_css' );

@lmartins can you pelase try replacing the class-kirki-color.php file with this one and let me know if that fixes your issue? https://gist.github.com/aristath/8126c745e1ea908bdd05

It does change something, but still getting weird results.
For example, I would expect that the following code to brighten the $page_bg substantially:
background: <?php echo Kirki_Color::adjust_brightness($page_bg, 230); ?>;

Instead it gets darker. I was under the impression the amount passed as the second parameter was a 0..100 value, tried with values under 100 and still not the results expected.

In the old implementation steps were from -255 (darken) to 255 (lighten).
In the new implementation I switched to a new colors-calculation class for greater versatility and performance (see https://aristath.github.io/ariColor/) and the new class uses values 0-100 for brightness values - just like the previous one should do, but it was ill-conceived when I started Kirki 2 years ago... so now I just have to make some conversions to make sure the old implementation will still accept values ranging from -255 to 255, then convert them to the right brightness level for the new class, and then pass them on to the new class.
It's not hard... just something I did not think of originally.
Can you please try again? I just updated the gist with a couple more changes... should be better now.
P.S. Sorry for using you as a lab-rat here, but some things I can't do without help.

@aristath no need to be sorry, really. Thank you so much for your help here.
The weird thing about it is that this line:
https://www.dropbox.com/s/ztypvobsn775xta/Screenshot 2016-03-20 16.08.27.png?dl=0
now outputs a dramatic change to the original color:
https://www.dropbox.com/s/356swj0yydvl7ei/Screenshot 2016-03-20 16.09.16.png?dl=0
The original color being passed to the function is what defines the main background. The function is changing the color of the table now displaying black.

OK, I believe I just fixed this.
I tested the old implementation and the new one with random colors side-by-side and they return the exact same results now. :+1:
Can you please verify it?
I just pushed a commit to the develop branch.

It might be a problem on my end, but im seeing a strange behaviour:
With both:
background: <?php echo Kirki_Color::adjust_brightness($page_bg, 100); ?>;

or:
background: <?php echo Kirki_Color::adjust_brightness($page_bg, -10); ?>;

I get the same output on the front-end:
https://www.dropbox.com/s/7ftg52is7l48s1i/Screenshot 2016-03-20 16.28.57.png?dl=0
Considering that $page_bg has the light grey visible in the page background, I would expect the first one to output white and the second one a slightly darker grey.
The $page_bg variable is created with:
$page_bg          = kirki_get_option('page_bg');

Can this have any relation with the problem?

Can you try using this instead?
$page_bg = get_theme_mod( 'page_bg', '#ffffff' );

replacing #ffffff with your default value

It behaves the same way.

Can you send me a copy of your theme? It'll be easier for me to debug that way

Reverted the Kirki_Color class to its previous implementation.
I'll leave the new implementation for the future...

Ok, pulling from dev makes things work as expected again.
If you want help testing the new class please let me know.

:+1: thanks, I'll definitely take you up on that when the time is right.


Required Node version?

Hi all,
the README currently requires Node 14 to build the wallet. However, using 14 gives the following error on yarn install:
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module.
Expected version ">=16". Got "14.19.0"
error Found incompatible module.

Is this ignore-able, or has the required version shifted to 16?

Hi @dmitrizagidulin Yeah sorry about the confusion. We moved to version 16 but the README is pretty explicit about not using version 16 🤷
You should be able to ignore it, but I suggest to use v16 as we soon will have an  updated version that will for sure need at least v16. The README is updated in the https://github.com/Sphereon-Opensource/ssi-mobile-wallet/tree/feature/VDX-165_siop branch


Constraint programming

Is your feature request related to a problem? Please describe.
Implement Work force planning for House construction from attached PDF
Describe the solution you'd like
Build a module to implement constraint programming using CP optimizer
Expected input(s)
Input data

Expected output(s)
Output data

Additional context
No response
Acceptance criteria
Generate workforce planning solution
Version
v0.5.0 (Default)

CP Slides Not Small (1).pdf
PDF for house hold work force planning


Add compatibility with dates before 1970 on Windows

See issue: https://github.com/ranaroussi/yfinance/issues/949
In order to avoid any issues, I simply created an alternative implementation of time.mktime. This implementation is then used where the original had been.
Of course, you could also make it so it's only used when running on Windows, or only when time.mktime raises an error. If this is deemed to be a better alternative, let me know so I can change the code.

Closing as this has been fixed by #1048


Develop

Q
A

Bug fix?
Y

New feature?
Y

BC breaks?
N

Deprecations?
Y

Fixed tickets
N

PHP 7.4 phpstan fix (about a regex) + S3 Support

I would like to release it (so we would be able to fully test S3 on AWS)


Rename package @iov/core

Depends on https://github.com/iov-one/iov-core/issues/917

The package name @iov/core is misleading, as IOV-Core is the name for a whole set of npm packages.
What we really need is a name for high level functionality that is in there.
I suggest @iov/multichain, but am happy for better ideas.

It would be good to have this on the MVP track to avoid painful renamings afterwards.


[20624] Fix open correct chat from deeplink.

Details
When coming from a deeplink which points to a chat, if another one was visible before, the new one would not open. Changed the navigation type as to replace the visible one with the new one.
Fixed Issues
$ https://github.com/Expensify/App/issues/20624
PROPOSAL: https://github.com/Expensify/App/issues/20624#issuecomment-1590023343
Tests
Same as QA Steps.

[X] Verify that no errors appear in the JS console

Offline tests
Same as QA Steps.
QA Steps
Test 1 - native Android & iOS:

Open any of your existing chats and copy its url from the address bar (like https://staging.new.expensify.com/r/1242891003534332);
Paste it in any external app (Slack, Telegram, Whatsapp, etc);
Log in with same account(from which you copied've the url) in native app(if you are not already);
In the native app, open any other chat(not the one from Step 1);
Go to the external app from Step 2 and tap on the link which you've pasted;
Verify that the report from the url opens.

Test 2 - Web, Mobile Chrome, Mobile Safari, Desktop:

Open any of your existing chats and copy its url from the address bar (like https://staging.new.expensify.com/r/1242891003534332);
Send it as a message in any other chat;
Click on the link which you've sent;
Verify that the report from the url opens.

[X] Verify that no errors appear in the JS console

PR Author Checklist

[X] I linked the correct issue in the ### Fixed Issues section above
[X] I wrote clear testing steps that cover the changes made in this PR

[X] I added steps for local testing in the Tests section
[X] I added steps for the expected offline behavior in the Offline steps section
[X] I added steps for Staging and/or Production testing in the QA steps section
[X] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[X] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[X] I included screenshots or videos for tests on all platforms
[X] I ran the tests on all platforms & verified they passed on:

[X] Android / native
[X] Android / Chrome
[X] iOS / native
[X] iOS / Safari
[X] MacOS / Chrome / Safari
[X] MacOS / Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[X] I followed proper code patterns (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[X] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I followed the guidelines as stated in the Review Guidelines
[X] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] I verified that if a function's arguments changed that all usages have also been updated correctly
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@allroundexperts

All Screenshots/Videos added;
Improved QA Steps as to correctly cover all platforms.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/pecanoro in version: 1.3.41-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.41-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
cancelled 🔪

🍎 iOS 🍎
cancelled 🔪

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/pecanoro in version: 1.3.42-0 🚀

platform
result

🤖 android 🤖
cancelled 🔪

🖥 desktop 🖥
cancelled 🔪

🍎 iOS 🍎
cancelled 🔪

🕸 web 🕸
cancelled 🔪

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.41-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.42-26 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Weaving issues about ninja

Ninja can cast 2 actions in a gcd.  of course, one of them must have a faster attack animation, like jugulate, bhavacakra or smoke screen, etc.

Double weaving is extremely ping-dependent and is usually only reliable if your ping is in the 25-30 range (or lower). If your ping is sufficiently low that you can double weave comfortably, you can ignore the weaving suggestion, but for the average user I'd prefer to keep the recommendation at single weaving. I suppose it might be worth adding a small disclaimer to the module, but I'd prefer not to make logic changes, especially not this close to the huge combat overhaul anyway. If ease of double weaving changes in ShB, I'll definitely revisit this.

Double weaving is extremely ping-dependent and is usually only reliable if your ping is in the 25-30 range (or lower). If your ping is sufficiently low that you can double weave comfortably, you can ignore the weaving suggestion, but for the average user I'd prefer to keep the recommendation at single weaving. I suppose it might be worth adding a small disclaimer to the module, but I'd prefer not to make logic changes, especially not this close to the huge combat overhaul anyway. If ease of double weaving changes in ShB, I'll definitely revisit this.

Thank you very much for your reply. Got it.


Allow for gaussian component due to atomic physics in spectral models

Original report by Galen O'Neil (Bitbucket: oneilg, GitHub: oneilg).

Joe’s L lines measurements will have this, and Mooney’s low Z measurements already have this (we just aren’t incorporating it yet).

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Removing milestone: v0.7 (automated comment)

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Okay, now you are reading Mooney’s data sheets the same way I did: the “minus scan” tells them the beam width, which they can then fix when fitting Voigts. We will need to handle this problem if we ever were to use our 2019 metrology results to fit lanthanide L lines, of course.

Original comment by Galen O'Neil (Bitbucket: oneilg, GitHub: oneilg).

Regarding Mooney’s lines needing gaussian_atomic_physics I no longer believe that. Here is an annotated screenshot of Mooney’s fits to the KCl Cl KAlpha. He fits the minus position scan (related to resolution of system) with a 0.778e-2 degree gaussian, then fits the plus position scan with the same width gaussian holding the width fixed. Her also fits the minus-position scan with a voigt profile, but doesn’t use the value from that anywhere.

We should still do this, but it doesn’t appear to be a high priority yet.


Reduce logging when external compactions are cancelled

Also only shows stack traces in FileCompactor on file writer close errors when debug is enabled.
This closes #3023

I think these changes are okay, but I'm not sure it's going to help folks who typically leave the debug logs enabled. In fact, it may make things worse for them, because now there's extra log statements, the basic one at warn and the more detailed stack trace at debug.

I suppose one thing we could do is only log one statement regardless depending on what is enabled so we don't have the second log statement. We could add back in the debug is enabled check, and if it is, then only log the full stack trace (either at debug level or even error/warn level) and if it's not enabled then just log the 1 line statement and no stack trace.
But, in my opinion, that isn't necessary and the change here should be ok as is. I'm not really worried about the extra log statements because if someone turns on debug then they should expect to get flooded with log statements and information as that is the entire point. To me this is about fixing the non-debug use case (ie not development but production) where you don't want see a bunch of extra stuff that isn't a big deal and you wouldn't leave debug turned on.

But, in my opinion, that isn't necessary and the change here should be ok as is. I'm not really worried about the extra log statements because if someone turns on debug then they should expect to get flooded with log statements and information as that is the entire point. To me this is about fixing the non-debug use case (ie not development but production) where you don't want see a bunch of extra stuff that isn't a big deal and you wouldn't leave debug turned on.

In revisiting the original issue that prompted this, I'm thinking about what I, as a user, would want the behavior to be. I think that when a tablet split causes an external compaction task to be cancelled, I would want to see a single warning per cancelled task, at most, if there's something I should do about it (like issue a new compaction command), or just a single debug message if there's nothing for me to do about it (in the case of an automatic retry or something). In the message, I would want to see compaction identifying information (compaction id?) and information about the tablet that split, but I don't think it would be helpful to see a stack trace at all in this situation. I'm not sure if there are any other situations where this code is called, though, so I'd be careful to check that before suppressing the stack trace for all callers.

The CompactionEnv implementation that is used in External Compactions is ExtCEnv. When CompactionJobHolder.cancel() is called, then ExtCEnv.isCompactionEnabled() returns false. CompactionJobHolder.cancel() is called from several places in Compactor.java. When it's called from Compactor.checkIfCanceled, then it's not an error, the compaction is being canceled because the tablet split, the table was deleted, or the user canceled the compaction. I think in this case, it warrants a debug message. When CompactionJobHolder.cancel is called via Compactor.cancel(String) from Compactor.run(), it's preceded by an error message.
I'm thinking that when env.isCompactionEnabled() returns false in FileCompactor.compactLocalityGroup() and a CompactionCanceledException is thrown, then FileCompactor.call() should log a debug message in the exception handler and suppress logging in the finally block.

compactLocalityGroup

Thanks for the explanation, I can catch the CompactionCanceledException in FileCompactor.call() here and log a debug instead of an error since it would be expected and in the finally block can update the logging to check if cancelled to supresss logging on file close.
And just to make sure I am following you, I think I would also want to only log a debug inside compactLocalityGroup() here and get rid of the error also as it's trying to close because compaction was cancelled and it's checking the flag using env.isCompactionEnabled(). ?
Lastly, I assume we still want/need to rethrow the CompactionCanceledException from call() so  that Compaction.createCompactionJob() gets it so it knows it didn't finish. It would log another debug there currently with the way the PR is.

Thanks for the explanation, I can catch the CompactionCanceledException in FileCompactor.call() here and log a debug instead of an error since it would be expected and in the finally block can update the logging to check if cancelled to supresss logging on file close.

Yes, this is what I'm thinking.

And just to make sure I am following you, I think I would also want to only log a debug inside compactLocalityGroup() here and get rid of the error as it's trying to close because compaction was cancelled and it's checking the flag using env.isCompactionEnabled(). ?

So, I'm not sure. We may want to change this to a warn or info. I would be interested in other opinions here. It's possible that there could be other cases outside of external compaction cancellation where we would want to know this happened.

Lastly, I assume we still want/need to rethrow the CompactionCanceledException from call() so that Compaction.createCompactionJob() gets it so it knows it didn't finish. It would log another debug there currently with the way the PR is.

Yes, I don't think we want to mess with the exceptions here, just the logging.

@dlmarion  - thanks, I'll make some changes and push up a new commit today and then we can discuss, etc.

It appears I have screwed up the history here with trying to merge main/reverts so I'm just going to reset from 2.1 and force push

Ok I forced pushed up the latest, let me know what you think.

This looks good. Suggest testing it on single node to see what happens in the monitor when compactions are canceled. I saw it when the ci table split when using external compactions and running continuous ingest. If you want to test single node, and need help with the configuration, let me know.

This looks good. Suggest testing it on single node to see what happens in the monitor when compactions are canceled. I saw it when the ci table split when using external compactions and running continuous ingest. If you want to test single node, and need help with the configuration, let me know.

Yeah I think testing would be good and I can report back how things look with log examples. I can message you on chat to get some info on setting up a good test.

Sure that is fine, makes more sense that way now that I think about it.

I ran this against Uno for a while with ingest running and a small split threshold to induce cancellations on tablet spltis and saw the following in the logs:
2022-11-10T06:24:05,091 [compaction.FileCompactor] DEBUG: Compaction canceled 7;683c;664
...
2022-11-10T06:26:55,021 [compaction.FileCompactor] DEBUG: Compaction canceled 7;0214<

No more stack trace or verbose output and I didn't see anything show up in the Monitor.


fix: decrease npm build, bundle size

This redirects the build source to reference .npmignore instead of the package.json -> files. I haven't done the exact size comparison, but were looking at a decrease in size by probably 60-70%.
All the tests will now be removed, as well as test-helpers.

Just checked the before and after for packages/txwrapper-core, and we are roughly looking at the following, which is a giant improvement.
Before
compressed uncompressed  ratio uncompressed_name
      270425      1630720  83.4% package.tar

After
compressed uncompressed  ratio uncompressed_name
       18439       150528  87.7% package.tar


Add bundler

:clipboard: Add associated issues, tickets, docs URL here.
Overview
Describe what your Pull Request is about in a few sentences.
Add bundler package
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Add bundler, account-abstraction, bundler-sdk and bundler-util
Add bundler test in CircleCI

Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.
Run the following commands
make devnet-up
make devnet-aa-up

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

Project coverage is 0.62%.  Consider uploading reports for the commit 66e0eba to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #185       +/-   ##
===========================================
- Coverage    28.21%   0.62%   -27.59%
===========================================
  Files          168      94       -74
  Lines         7294    2396     -4898
  Branches      1311     546      -765
===========================================
- Hits          2058      15     -2043
+ Misses        5130    2381     -2749
+ Partials       106       0      -106

Flag
Coverage Δ

cannon-go-tests
?

chain-mon-tests
?

common-ts-tests
?

contracts-bedrock-tests
0.62% <ø> (ø)

contracts-ts-tests
?

core-utils-tests
?

sdk-next-tests
?

sdk-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 74 files with indirect coverage changes

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

Project coverage is 0.62%. Comparing base (5b13622) to head (b5ffd55).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #185       +/-   ##
===========================================
- Coverage    28.21%   0.62%   -27.59%
===========================================
  Files          168      94       -74
  Lines         7294    2396     -4898
  Branches      1311     546      -765
===========================================
- Hits          2058      15     -2043
+ Misses        5130    2381     -2749
+ Partials       106       0      -106

Flag
Coverage Δ

cannon-go-tests
?

chain-mon-tests
?

common-ts-tests
?

contracts-bedrock-tests
0.62% <ø> (ø)

contracts-ts-tests
?

core-utils-tests
?

sdk-next-tests
?

sdk-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 74 files with indirect coverage changes

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

Project coverage is 0.62%.  Consider uploading reports for the commit 88b2e52 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #185       +/-   ##
===========================================
- Coverage    28.21%   0.62%   -27.59%
===========================================
  Files          168      94       -74
  Lines         7294    2396     -4898
  Branches      1311     546      -765
===========================================
- Hits          2058      15     -2043
+ Misses        5130    2381     -2749
+ Partials       106       0      -106

Flag
Coverage Δ

cannon-go-tests
?

chain-mon-tests
?

common-ts-tests
?

contracts-bedrock-tests
0.62% <ø> (ø)

contracts-ts-tests
?

core-utils-tests
?

sdk-next-tests
?

sdk-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 74 files with indirect coverage changes

adding as a reminder to add this commit (after this PR) fc598b5 for consistent addresses

Added

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

Project coverage is 18.95%. Comparing base (5b13622) to head (2bcd813).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #185      +/-   ##
===========================================
- Coverage    28.21%   18.95%   -9.27%
===========================================
  Files          168      158      -10
  Lines         7294     6226    -1068
  Branches      1311     1311
===========================================
- Hits          2058     1180     -878
+ Misses        5130     4971     -159
+ Partials       106       75      -31

Flag
Coverage Δ

cannon-go-tests
?

chain-mon-tests
27.14% <ø> (ø)

common-ts-tests
26.72% <ø> (ø)

contracts-bedrock-tests
0.62% <ø> (ø)

contracts-ts-tests
12.25% <ø> (ø)

core-utils-tests
44.03% <ø> (ø)

sdk-next-tests
38.59% <ø> (ø)

sdk-tests
38.59% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 10 files with indirect coverage changes

This PR is really huge -- it's hard for me to understand what's original code, and what's been copied in, and or what's been copied in and modified. A few questions:

Is it possible to pull any of this in via something like an NPM package? And if so, why aren't we?
There seem to be a lot of hardhat dependencies here, but the upstream repo seems to be moving away from hardhat and to foundry.  I know we needed hardhat to deploy the legacy network to practice the migrations, but I was kind of hoping we'd be able to remove it eventually.  Do we want to keep having both?
Maybe it would be helpful to add a top level README to the packages/boba dir to help explain what the components are, where they came from, and if they're copied, how to update them?

I don't have any preferences here since it's the local dev environment for AA, and I haven't been involved in AA development in the past. @souradeep-das, what do you think about these questions?

I don't have any preferences here since it's the local dev environment for AA, and I haven't been involved in AA development in the past. @souradeep-das, what do you think about these questions?

We have added in quite some changes from the upstream repo's to have this work on Boba (v2, and some that may still be relevant to v3 - this includes changes to bundler, bundler-sdk etc) Our custom created paymasters are also part of the repo. We have also restructured the repos a bit different from upstream. So I think maintaining this separately makes sense.
Re -documentation, some of those bundler-api, bundler-sdks docs in our repo are updated to include the changes we have introduced. But there's definitely scope for more docs/ and documenting all diffs from upstream.


How come stream-js does not support unix timestamp as time field

let activity = {
          actor: accounts[userId],
          verb: 'reply',
          object: 'reply:' + replies[posts[tokens[j]][i]][k],
          foreign_id: 'reply:' + replies[posts[tokens[j]][i]][k],
          time: moment().unix(),
          to: ['comment:' + posts[tokens[j]][i]]
        }

(node:53785) UnhandledPromiseRejectionWarning: Error: {"detail":"The activity.time field is required","status_code":400,"code":4,"exception":"InputException","duration":"0.19ms"} with HTTP status code 400

a date object works though, so just moment() should do the trick


Suggesting we use Bozhidar Batsov's style guide.

This guy publishes a great ruby style guide, I read through it and
don't have any significant changes.

Ruby is still objectively terrible.


TypeError: Cannot read property 'getStratumServer' of undefined

I am getting follwing error when connecting nheqminer to my pool -
/home/ubuntu/z-nomp-bitcoin-gold/libs/poolWorker.js:274
pools[initalPool].getStratumServer().handleNewClient(socket);
^
TypeError: Cannot read property 'getStratumServer' of undefined
at Server. (/home/ubuntu/z-nomp-bitcoin-gold/libs/poolWorker.js:274:47)
at Server.emit (events.js:160:13)
at Object.onconnection (net.js:1582:8)
at onconnection (internal/cluster/child.js:168:12)
at Worker.onmessage (internal/cluster/child.js:43:7)
at process.onInternalMessage (internal/cluster/utils.js:42:8)
at process.emit (events.js:165:20)
at emit (internal/child_process.js:790:12)
at process._tickCallback (internal/process/next_tick.js:152:19)
2018-02-13 05:27:03 [Master]    [PoolSpawner] Fork 5 died, spawning replacement worker...
nheqminer show following error -
[10:57:22][0x00001270] stratum | Starting miner
[10:57:22][0x00001270] stratum | Connecting to stratum server <IP_ADDRESS>:3333
[10:57:23][0x00001270] stratum | Connected!
[10:57:23][0x00001270] stratum | read_until: End of file
[10:57:23][0x00001270] stratum | Reconnecting in 3 seconds...
btg.txt
config.txt
pool.txt

did you ever figure this out?

Have you solved the problem yet?


Update custom-schedule.html

Made sure the breakout rooms match with our breakout room schedule and facilitator assignments, listed here

@MathewBiddle @jdpye I noticed that the link to Animal Telemetry in the schedule is non-actionable, but I'm not sure why - any thoughts?


Dependabot/npm and yarn/nanoid 3.3.1

by by

ljfq3by4r364niy74 gh56fni43y7yhub87ceryumu9

njyht

https://github.com/apps/azure-pipelines

https://github.com/apps/azure-pipelines@azure-pipelines
facebook.create-react-app (Simple LinuxNode14) Successful in 5m — Simple LinuxNode14 succeeded
Details
@azure-pipelines
facebook.create-react-app (Simple LinuxNode16) Successful in 6m — Simple LinuxNode16 succeeded
Details
This branch has conflicts that must be resolved
Only those with write access to this repository can merge pull requests.
@Aadideshwal12345


fix: parsing mention wrapped with styles inside link text

Fixed Issues
$ https://github.com/Expensify/App/issues/19997
Tests

Go to a chat and add a comment

[_@username@expensify.com_](expensify.com)

Verify that the text<EMAIL_ADDRESS>of link is not rendered as mention and is italic

QA
Same as test

Wasn't I suppose to be assigned?

I think so, not sure why Melvin assigned me instead 🤔

I think auto assignment never worked correctly cross repos.


Add version: JetBrains.Kotlin.Compiler version 1.8.20-Beta

Pull request has been created with Komac v1.9.1 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116170&drop=dogfoodAlpha

@wingetbot waivers Add Validation-Executable-Error


Improve Helm Chart

Improve Helm Chart in order to make it easier to onboard:

Provide a README with more info: (see CHART LICENSE, README AND NOTES)

A description of the application or service the chart provides
Any prerequisites or requirements to run the chart
Descriptions of options in values.yaml and default values
Any other information that may be relevant to the installation or configuration of the chart

License

That said, I would do copy the repo license into the chart folder during the build & package stage of the release.

I'm happy to pick this up if you want.

Related: #102

The chart configuration is documented via #265

I can pick up the notes as well - My suggestion would be to drop a small note that ScaledObjects need to be installed or do you have other suggestions?
The license is just a file in the folder structure which I would copy during the release process rather than duplicating it. Thoughts?

+1 to the note idea. The notes should cover anything required for KEDA to function that doesn't happen in the helm install command

Well, it was your good idea as part of #102 :D
From my initial POC with it there wasn't much more to do than deploy app & scaled object so will just do that then maybe?

I think what's left open is the license. Feel free to assign this to me

Notes.txt could include:

A link to the scaled objects ref doc or quickstart
How to view any scaled objects
How to view any HPA that gets created
Info on the dashboard

Closed in #315


Reference the deploying users PrincipalId / Account Information

I am deploying a new KeyVault and want to be able to create a key in the keyvault all in the same deployment.
If i try to do this with just owner permission then i receive this error

[ForbiddenByRbac (Forbidden)] Caller is not authorized to perform action on resource.

My existing RBAC on the Resource Group is owner. If i grant myself Key Vault Crypto Officer on the resource group before deployment then it works great (however this isn't my use case).
In order to create the key in the same deployment as the vault, i need to assign myself as RBAC CryptoOfficer during the deployment.  eg;

Create KeyVault
Assign myself Crypto Officer
Wait for propagation
Create key in vault

In order to do step 2, i need to pass in my user PrincipalId as a parameter to the bicep.
It would be much cleaner if i could reference this within bicep itself, eg;
param kvPrincipalId string = deployment().initiator.PrincipalId

I would also need to be able to distinguish between users and service principals;
param kvPrincipalType string = deployment().initiator.type

Dup of #4959


removed sleep() from fetch data loop

is this to prevent rate-limiting?
i realized the program sends a get request to an api of some sort with changing id number
I only ran this once if its of concern.
cuts down raw_data.py runtime to 1 minute, from 25 minutes (on a desktop 5600G)

It was to prevent rate limit. And, yes, SRS uses some hashed routes for api requests.
Client creates hashed path for item data.
Example,  material id is 2000. It will create a hashed path for en/materials/2000.json.
make a request to
https://starrailstation.com/O_VALUE/{HASHED_PATH}
see constants.py for O_VALUE
Should not be problem eitherway, as its cached.


write stream function params solved

This Pr aim is to solve the write stream and create write stream functions parameters if the encoding param was missed, it has to replace the encode with callback parameter. 🤖

thank you, published as @hasnat/s3fs:2.5.2


Restock

any way to specify the item quantity for restock? i didn t find it in the code and it just replenishes everything by 1.

Well the stock keeping of it, after i enter the categories and subs for it i don t have an option for quantity or somethjng else but i have in the /admin the restock announcement option

@kiljorn1109 To be honest, I don't understand what you want. Can you please explain what you expect to get from the bot, and what you actually get. Also describe what you do to get it.

So the git i cloned, i have the bot the contact cards the products, everything but in the products.json let s say i don t have the quantity of the specified product, but when i enter from a buyer account i see that i have a quantity, is there any way i could set that ?

If you want to set the quantity of items manually, there is no such functionality. The quantity of items means all items that have the "is_sold == False" field. If you plan to sell items that you have in infinite quantity, it will be easier to generate 999+ such records, and add "contact admin" or something like that to the "private_data" field.
{
	"items": [
		{
			"category": "Category#1",
			"subcategory": "Subcategory#1",
			"price": 50,
			"description": "Mocked description",
			"private_data": "Contact Admin"
		},
		{
			"category": "Category#1",
			"subcategory": "Subcategory#1",
			"price": 50,
			"description": "Mocked description",
			"private_data": "Contact Admin"
		}
		........... 999+ records
		,
		{
			"category": "Category#1",
			"subcategory": "Subcategory#1",
			"price": 50,
			"description": "Mocked description",
			"private_data": "Contact Admin"
		}
	]
}

@kiljorn1109 Is your issue still relevant?

Sorry for placing that comment here, just dont want create new issue. Dont have any option to get you. Can you please answer me in tg!

What do you mean ?
On Thu, Aug 1, 2024, 11:51 PM baz0okq @.***> wrote:

Sorry for placing that comment here, just dont want create new issue. Dont
have any option to get you. Can you please answer me in tg!
—
Reply to this email directly, view it on GitHub
https://github.com/ilyarolf/AiogramShopBot/issues/42#issuecomment-2263689077,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADYVKRVCNT6KT2DROJCAJHLZPJ4DNAVCNFSM6AAAAABJ34VI5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGY4DSMBXG4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Few months ago we speak about business in telegram. Can you answer me there?

Can you reply on telegram
I can not find you
On Fri, Aug 2, 2024, 12:25 PM baz0okq @.***> wrote:

Few months ago we speak about business in telegram. Can you answer me
there?
—
Reply to this email directly, view it on GitHub
https://github.com/ilyarolf/AiogramShopBot/issues/42#issuecomment-2264693433,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADYVKRWGMUBRUN4M3YNXUZLZPMUODAVCNFSM6AAAAABJ34VI5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRUGY4TGNBTGM
.
You are receiving this because you commented.Message ID:
@.***>

Hmm, maybe you have new one. It shows that you was online " last seen within a month "
Try add me https://t.me/didluh

@baz0okq Hi, I replied to you on telegram on August 9 at 8:27 UTC. @Dimu001 is an imposter

Refreshing this discussion: would it be okay to raise this as feature request? Let's say you have developed a software and want to offer 20 implementation services for the next months. All services are identical from the costumer's perspective while the logic of this shop is to have each service offering unique and identifiable, e.g. to keep track of a customer's purchase history. As shop admin, it would be convenient to have an additional field "quantity" available so that you can simply define one article (o.e. subcategory) once but you can add the same article n times according to the field "quantity". This would make the handling of adding articles to the shop as it is implemented now a bit easier for the admin.
Maybe this would be a good feature request.


WaitFor fails for web element

What happened?
await waitFor(web.element(by.web.xpath("//a[@class='pcc-client-content-feed__panel-wrapper-title-link' and contains(text(), 'Following')]"))).toBeVisible().withTimeout(5000);
-->  [object Object] is not a Detox matcher. More about Detox matchers here: https://wix.github.io/Detox/docs/api/matchers
What was the expected behaviour?
Waiter function should work and not through bug
Was it tested on latest Detox?

[X] I have tested this issue on the latest Detox release and it still reproduces.

Did your test throw out a timeout?

[X] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much.

Help us reproduce this issue!
No response
In what environment did this happen?
Detox version: 20.20.1
React Native version: 0.72.0
Has Fabric (React Native's new rendering system) enabled: yes
Node version: >=16
Device model: iPhone 15
iOS version: 17.2
macOS version: 14.4
Xcode version: 15.2
Test-runner (select one): jest
Detox logs
Detox logs
   [object Object] is not a Detox matcher. More about Detox matchers here: https://wix.github.io/Detox/docs/api/matchers

Device logs
Device logs
paste your device.log here!

More data, please!
No response

Is there any other method to wait for element till it exist? Or can this be fixed for web view elements, to work as well with waitfor() ?

Hey @alexandravychytill, unfortunately there's no wait-for API for Web elements in Detox (yet.. → Contributions are welcome!)
You can do some async-await sleep before the action (await new Promise(r => setTimeout(r, 2000));)

@alexandravychytill - You may use such function, to wait for web elements. I use such and work pretty fine for me:
It uses basic timeout function + detox element check state: toExist()
  static async pause(value: number = 30000) {
    return new Promise(resolve => {
      setTimeout(resolve, value)
    })
  }

private async waitForWebElement(webElement: Detox.IndexableMaybeSecuredWebElement & Detox.SecuredWebElementFacade, maxWaitTime = 30000) {
    const startTime = Date.now()

    while (Date.now() - startTime < maxWaitTime) {
      try {
        await expect(webElement).toExist()
        await Helper.pause(1000)
        return
      } catch (error) {
        if (Date.now() - startTime >= maxWaitTime) {
          throw error
        }
        await Helper.pause(100)
      }
    }
  }

    const loginInput = web.element(by.web.id('Login'))
    await this.waitForWebElement(loginInput)