Update build.gradle Fixing Issue with Flurry

Currently the dependencies for 'com.flurry.android.analytics:+@arr' is not working, so now it is working with the 7.0.0 version.

@AugustoAleGon Thanks! I have no time for support the project now!


fix(preserveModules): add external deps

Co-authored-by: Jack Shelton<EMAIL_ADDRESS>What is it?

[ ] Feature / enhancement
[ ] Bug
[ ] Docs / tests
[ ] Other

Why is it needed?

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have ran pnpm change and documented my changes
[ ] I have add necessary docs (if needed)
[ ] Added new tests to cover the fix / functionality

why not dependencies?


Added init.py files to providers

This PR is intended to fix #102 by adding init.py files to each of the architectures providers so that they can be discovered by setuptools.find_packages during the release process.
This will cause a dramatic decrease in code coverage as each of these packages were not previously being tested since they all basically work in a similar way.

Merging my own code, so of course I'm okay with this.


Statements Page Doc Update - discuss stats collection with threshold

Re: Statements Page
In a recent version, the Statements Page got the ability to request diagnostics for a statement corresponding to an execution that takes over a duration threshold. We should mention this in the docs, and in particular highlight that using this threshold feature means that we'll trace all queries with the respective fingerprint until the threshold is hit. This can be expensive. This is in contrast with what the page currently says for the non-threshold case.

Tip:
Diagnostics will be collected a maximum of N times for a given activated fingerprint where N is the number of nodes in your cluster.

This is already in progress here: https://github.com/cockroachdb/docs/pull/13623


Resizing window breaks the chat UI

Not sure what level priority this should have, but this is pretty high for me. Resizing the window breaks the formatting and makes it impossible to read the output in the terminal.

We should prioritize fixing this sooner than later if we don't know how this will affect the overall structure of the code. This way, we still have some flexibility before going deeper into specific UI/UX details.

This is expected because we have no means to repaint the entire UI with the increase or decrease of the rows and columns of the terminal(i.e change in dimensions of the terminal app). But yes. I will give it a thought and I think we will end up using Textual eventually.

Update: I tried using Textual and it is a bit of a learning curve for me. Also it has CSS elements for styling. However I can't get it to work the "LLM token streaming generation" for some reason. For now I think we should remove the frame. In this way it won't break if the window is resized.

Wow! It's like you read my mind! haha.
I tried playing around with textual a few days ago and it's not something we'll pick up and integrate over night. I think we should focus on core features and keep the UI light and we can slowly enhance the UI/UX over time.
I found textual to be completely unintuitive with respect to input and output. I know it's possible, I just don't have any experience with it.
What I did learn is that we'll need to implement our own custom panels and labels.
So, for output we would use Label and could use Label.update, but I could not for the life of me figure out how to gracefully handle input.
There are the Input and TextArea widgets, but they don't necessarily behave as expected and really depend on events as a result.
The CSS seems to be a custom, watered down, implementation as well. So instead of referencing an HTML element, we would reference a class identifier instead.
I also have been running into limitations with rich as well. There's no option to remove a border at all. A Box must be defined and passed to a Panel. After multiple attempts at it on my own and spending a couple of days on it, I finally threw the towel in and broke down and just asked ChatGPT. It had no idea how to do it either. After a bit of back and forth, this what ChatGPT and I came up with.
# Define a custom Box style with no visible characters
no_border_box = box.Box(
    "    \n"  # top
    "    \n"  # head
    "    \n"  # head_row
    "    \n"  # mid
    "    \n"  # row
    "    \n"  # foot_row
    "    \n"  # foot
    "    \n",  # bottom
    ascii=True,  # Setting ascii to True to emphasize the lack of box characters
)

Then we would just instantiate any panels with our custom border.
self.console.print(
    Panel(
        Markdown(message["content"]),
        title=title.upper(),
        title_align="left",
        box=no_border_box,
    )
)

I really don't like this approach because it feels really hacky, but the following is a direct copy and paste from a test I just finished running.

11:39:26 | /mnt/valerie/rich-chat
(.venv) git:(textualize | Δ) λ python -m rich_chat.rich_chat_cli --server 'http://localhost:8080' -m 'My name is StableLM and I am your helpful assistant!' --temperature 0.7 --topp 0.9 --topk 50 --minp 0.1 --n-predict -1 -n "stablelm-1b-test"
SYSTEM
My name is StableLM and I am your helpful assistant!
HUMAN
Hello! My name is Austin. What is your name?
ASSISTANT
Hi there, my name is StableLM and it's a pleasure to meet you, Austin! How can I assist you today?
HUMAN
Can you show me an example of how to get a list of prime numbers in Python?
ASSISTANT
Sure! Here's an alternative approach using Python:
def is_prime(n):
    if n <= 1:
        return False
    for i in range(2, int(n**0.5) + 1):
        if n % i == 0:
            return False
    return True

primes = [n for n in range(2, 100) if is_prime(n)]
print(primes)

In this solution, the is_prime function checks whether a given number is prime by iterating from 2 to the square root of the number and checking if
there's any divisor. If it finds any divisor, it returns False; otherwise, it returns True.
Then, we iterate through numbers starting from 2 up to 100 (since you mentioned the smallest prime number as 2) using a list comprehension. For each
number, we check if it is prime by calling the is_prime function and append it to the primes list if it's a prime number.
Finally, when the script runs, it prints out this list containing all the prime numbers up to 100.

Not completely ideal because we can't remove the padding, otherwise it just results in a ValueError due to the missing spaces rich expects.
I'm honestly considering just building a custom interface that places LLM's as first class citizens. All of the existing frameworks were not built with any of this tech in mind so it's all very convoluted and difficult to implement and manage. I'd prefer to not repeat the same mistakes I made with my pygptprompt project.

I have got an idea. Will come back to you after trying.

Update:
Oh well!
upload.webm


Add some more explanation text to the about page

Fixes #182

Coverage remained the same at 81.56% when pulling fdd75f57d7345a264f838030b9d89ba451814e31 on call-to-action into 128d4ceb0237710973ac386cbb7493cf065a9710 on master.


About Resharding

Is JedisCluster provide the resharding function like redis-trib.rb
Thank you very much, Best Wishs

No,
redis-trib is a command line tool that helps to manage / setup redis in many different ways. Jedis on the other hand is just a client with implements the specs proposed by redis.
redis-trib.rb is NOT a redis client library, that's why it's important to understand why you don't have to mix the two things. Having said that, you can use redis-trib.rb to manage your cluster and still use JedisCluster as a client library for your app.


[Idea] Hide label Options

Hey! Handy mod, love it, some options would be a nice touch if you feel like juicing it up a bit

Wall sight | only show player names when they are behind walls (makes it easier to find your friends when exploring together,
hide friendly | Only hide players on your team
toggle hide | Show names when shifting

Thanks for all your hard work

Sorry for some reason github unsubscibed me from updates on just this repo, had no clue this issue was submitted
I only just found out by chance since i'm updating the mod
sure will look into making those options what do you mean by on your team though, wasn't aware mineecraft has a team mechanic?


FR: Notification: display center as Modal\Lightbox

Description
When displaying a Notification on the center of the page, a user still has access to the dashboard below. It would be very helpfull to be able to display a (center or all) Notification in such a way that access to the dashboard page is not possible anymore until the Notification disappears (either by user action or on time-out).
Have you provided an initial effort estimate for this issue?
I am no FlowFuse team member

Duplicate of https://github.com/FlowFuse/node-red-dashboard/issues/193 and https://github.com/FlowFuse/node-red-dashboard/issues/627


Added e2e tests for page.tag.attached webhook

ref #15537
Got some code for us? Awesome 🎊!
Please include a description of your change & check your PR against this list, thanks!

[x] There's a clear use-case for this code change, explained below
[x] Commit message has a short title & references relevant issues
[ ] The build will pass (run yarn test:all and yarn lint)

We appreciate your contribution!
Also, if you'd be interested in writing code like this for us more regularly, we're hiring:
https://careers.ghost.org

Hi @naz, Thanks for your feedback. I've made another changes. I've tried to run yarn lint but there is an error saying that:
Oops! Something went wrong! :(

ESLint: 8.25.0

No files matching the pattern "'core/server/**/*.js'" were found.
Please check for typing mistakes in the pattern.

error Command failed with exit code 2.

Do you have any idea for this? I also made a changes on tagSnapshot, please let me know if there's more feedback. Thank you.

Hi @naz, I've updated the tagSnapshot and made some changes. Please let me know if there's any more feedback, cheers!

Hey @leonyangela , just a heads up there are some linting errors that need to be fixed. The rest of the code is heading in a right direction 👍

Hi @naz, the lint test flow keeps failing, I have no idea on this, any suggestions?

ah great, thank you @naz.

Hi @leonyangela  thanks so much for this PR. It has now been merged 🎉  FYI I had to rebase it as it conflicted with changes made to add the page.tag.detached tests.
I'm not sure if you found this through hacktoberfest, but I've added the hacktoberfest-accepted label to this PR to make sure it counts. We have plenty of open issues and ongoing projects for hacktoberfest and beyond. We would love to see you around again 👋

Hi @ErisDS, thank you. Yes, I found this from hacktoberfest, thanks for adding the hacktoberfest-accepted label, cheers :beers:.


Missing support for underscores in identifier names

I wonder why we did not notice this earlier, but CCom currently does not support underscores in identifiers, which is definitely not the intended solution.
The problem is that isalnum() does not return true when the input is an underscore.

As far I have seen, the Java compiler is also affected by this issue.

thanks for noticing, will fix this


Isolated Functions

The examples here are provided for In-Proc functions.  How do I do it in an Isolated Function?
Sincerely,
Keith

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

ID: 62bbedb6-d4c5-a809-31ad-b8c843ac0f52
Version Independent ID: 07c4822d-0aad-5a8a-7f16-56835f325a42
Content: Fan-out/fan-in scenarios in Durable Functions - Azure
Content Source: articles/azure-functions/durable/durable-functions-cloud-backup.md
Service: azure-functions
Sub-service: durable
GitHub Login: @ggailey777
Microsoft Alias: azfuncdf

@keithnicholson
Thanks for your feedback! We will investigate and update as appropriate.

@keithnicholson Check out Migration guide to convert the sample from In-process to Isolated function.
If you are looking for a full sample, refer https://github.com/microsoft/durabletask-dotnet/tree/main/samples/AzureFunctionsApp and make the changes for your scenario accordingly. Currently, Isolated samples are not integrated in many tutorials and will pass the feedback to our doc team.
I hope this helps and let me know if any questions.


Can't Open YouTube

If I try open youtube I am getting white screen.

This has already been fixed. You need to update your php-proxy-plugin-bundle package via "composer update" or manually:
https://github.com/Athlon1600/php-proxy-plugin-bundle/commit/b09920be6759728088893ed402545b1b57b65863

I updated YouTube plugin and I uploaded to my hosting but I'm getting "Couldn't resolve host" error all time.

Link me to your proxy site

http://fatihweb.ml
2017-09-24 19:04 GMT+03:00 Athlon1600<EMAIL_ADDRESS>
Link me to your proxy site
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Athlon1600/php-proxy/issues/78#issuecomment-331719617,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGH_vEcpCmBc57HLFhPuX6faSODVN4Zaks5sln2QgaJpZM4PhjQC
.

Seems to work fine for me?
https://preview.ibb.co/kF0vok/Untitled_1.png

I am getting error on normal mode but work fine in incognito mode.
https://preview.ibb.co/fA9xjQ/hata.png

Are you on mobile or some weird desktop browser with special addons? I literally typed that same "https://youtube.com" string into your proxy, clicked "Git" and it worked.

Thanks for help. I fixed issue.


protocol: Link ivi-application library with wayland-client library

ivi-application library uses wayland-client library symbol:
aarch64-linux-gnu-objdump -TC libivi-application.so | grep wl_
0000000000000000      D  *UND*<PHONE_NUMBER>000000              wl_surface_interface

but couldn't observe it in the library's 'Dynamic Section':
aarch64-linux-gnu-objdump -p libivi-application.so | grep NEEDED
  NEEDED               libc.so.6

Link libivi-application.so with libwayland-client.so to prevent undefined symbol errors.

I tested the pull request with list test cases. All has passed.


Rework parameter files in validation directory to work with new file format

I recommend that set "startRadius" to "2.0" so that at the second epoch synapses connections will be created and we can validate the synapses creation code.

It this fixed now?

All parameters files in validation directory are now work with the new file format.


Font "jumping" when they stay in place but camera is moving.

Godot version:
3.1 35bb520
OS/device including version:
Windows 10
Issue description:
When I move a Player with camera, then in background I can see that names of fonts are jumping strangely.
Steps to reproduce:
Move player outside a camera no-move area
https://streamable.com/xhqrj
Minimal reproduction project:
https://github.com/qarmin/Sea-of-Ground

Controls (including their fonts) are snapped to pixels by default, so this is expected. To disable this behavior, uncheck Gui > Common > Snap Controls To Pixels in the Project Settings. This should solve the issue, at the cost of making the UI blurrier overall.


holdSubject should should buffer inputs even without listeners

I feel like https://github.com/mostjs-community/most-subject/blob/master/src/HoldSubjectSource.ts#L30 should be moved above the if(!this.isActive...) line.  Currently the @cycle/storage driver emits item streams using a startWith.  That item is currently pushed into a basic most Subject using adapt during the initial wiring of the stream, which means the values that are sent are being dropped since there are no active listeners.
I hacked the most-adapter code to start using a holdSubject to see if that fixed things but it doesn't because holdSubject doesn't buffer the value that is sent into it unless it has listeners.  I think that's wrong. I think a hold subject should buffer values sent in even when there are no listeners.  The purpose of a holdSubject is "value over time" so shouldn't it maintain the values it receives so the first listener gets a value immediately without having to wait for a follow-on emission?

I propose the function should look something like this:
    HoldSubjectSource.prototype.next = function (value) {
        if (this.scheduler === void 0) {
          return;
        }

        var time = this.scheduler.now();
        this.buffer = util_1.dropAndAppend({ time: time, value: value }, this.buffer, this.bufferSize);

        if (!this.active) {
            return;
        }

        this._next(time, value);
    };

This is a recent change that occurred when I submitted a PR to fix another issue. It was something we needed to discuss that I probably should have been clearer about. I did it that way because it is currently how most/hold behaves, but maybe it is something we need to correct. Your expectation is more intuitive to me personally.
@TylorS and @briancavalier What are your thoughts?

I'm not super familiar with the current most-subject implementation, but I'll try to offer some perspective.
One essential difference between holdSubject and @most/hold stems from the fact that streams (non-subjects) only have a producer when they also have a consumer, whereas subjects always have a producer--the party who created the subject or another party to whom the subject has been given--even when there is no consumer.  The consequence is that streams don't have to deal with the (often tricky) situation of producing events when there is no consumer, and subjects do.
So, I think it's perfectly reasonable for holdSubject to do something different from @most/hold in order to handle that difference in an intuitive way.  It does seem like holdSubject would need to buffer events even when there's no consumer.
I hope that's helpful!

This has been fixed :+1:


[tool, xcel] Support dumping the array of struct in shm/vcd

Add -memories switch into probe command that enables dumping the arrays of struct
into the shm/vcd waveform database of the Xcelium simulation
Thanks to @rasmus-madsen
Signed-off-by: Tung Hoang<EMAIL_ADDRESS>

Assuming you have tried running both, --waves shm and --waves vcd, this LGTM.

@sriyerg yes, those are options we are using

@sriyerg I think was premature!
do we always want to dump memories?
I assumed that was why you created the probe_flags option.
maybe just add away to actually set this with the dvsim command?
I think that would have been a better and cleaner way to go!

@sriyerg I think was premature!
do we always want to dump memories?
I assumed that was why you created the probe_flags option.
maybe just add away to actually set this with the dvsim command?
I think that would have been a better and cleaner way to go!

Ohh, sorry about that. With VCS we do dump MDAs and haven't seen a noticeable degradation in performance. Our testbenches are fairly small enough. But I agree there should be a cleaner way to do it. Lets discuss on this in the DV meeting.


Lint reenable

This PR reenables linting on build so we can run linter via github workflows. I am not sure why the linter got disabled in the first place, probably some changes overwritten that.

@superbuggy addressed your suggestions


Include binary?

May you please provide compiled binary?

Check the releases page

Thank you. Apologies, wasn't aware of the 'releases' link.


ALVR: Pitch black view in headset

Describe the bug
After connecting the headset to ALVR and launching SteamVR the view in the headset goes completely black. The VR view on the laptop screen shows SteamVR and the image moves correctly with the movement of the headset and controllers.
Steps To Reproduce
Steps to reproduce the behavior:

Have Quest 2 (larger storage version) with ALVR app 20.11.1 (latest right now) installed
Have my system: https://codeberg.org/balint/nixos-configs#tuxedo
Open ALVR dashboard
Connect headset
Start SteamVR from ALVR
Enable SteamVR VR view to observe the corrrect image being generated
Look in the headset to see black

Expected behavior
VR views should show on the headset
Additional context
I tried adding ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command% to SteamVR's launch settings as suggested in this comment but then SteamVR just ends up crashing every time the headset connects. I tried a couple of different settings in ALVR for resolution, refresh rate, encoding, sound, etc, but didn't try everything.
I realised that the ALVR version on my device is 20.11.1 but the one in nixpkgs unstable is 20.11.0 so I forked nixpkgs and bumped the version but the result was the exact same after adding my fork to my system flake and rebuild-switching.
My computer is a Tuxedo Pulse 14 Gen 4 laptop: AMD Ryzen 7 8845HS, no dedicated GPU, no nvidia
My nixpkgs is nixos-24.11 with some packages - like ALVR - pulled from nixos-unstable. Steam should come from 24.11 so it should not have the issue the one on unstable has, unless I misunderstood what is in 24.11 now.
I haven't used ALVR on NixOS before so I don't have a version that worked that I could bisect between.
Metadata

system: "x86_64-linux"
host os: Linux 6.11.9-xanmod1, NixOS, 24.11 (Vicuna), 24.11.20241123.0c58267
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.24.10
nixpkgs: /nix/store/fnbr9s78sy4islw83vsaf0hgf88hih5v-source

Notify maintainers
Tagging people participating in the source build PR or having similar issues
@jopejoe1
@NovaViper
@eyJhb
@DaRacci
@LuNeder
Add a :+1: reaction to issues you find important.

I want to add that the error after adding ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command% launch setting (as stated here in ALVR wiki) that I got is:
ERROR Encoder: cu->cuMemcpy2DAsync(&cpy, cuda_dev->stream) failed
ERROR Encoder:  -> CUDA_ERROR_INVALID_VALUE: invalid argument
ERROR Encoder:
ERROR error in encoder thread: Failed to transfer Vulkan image to CUDA frame Generic error in an external library

If you Force Software encoder in Video settings, you can stream image.
It seems to be an error related to Nvidia drivers in my case. I'm using 560.35.03 Nvidia driver with CUDA version 12.6.

This is a known issue, see here.
Currently, hardware encoding doesn't work for nvidia drivers on the nixpkgs derivation. Try forcing software encoding.

I don't have nvidia drivers or hardware, not that I know of at least. Where did you see that error output? In ALVR log?

Also enabling force software encoding didn't help, still crashes

20:59:45.687 INFO Initial socket buffer size: send: 130560B, recv: 131072B
20:59:45.709 INFO Initial socket buffer size: send: 212992B, recv: 212992B
20:59:45.709 INFO Set socket send buffer succeeded: 425984
20:59:45.709 INFO Set socket recv buffer succeeded: 425984
20:59:45.712 INFO Render Target: 4288 2336
20:59:45.712 INFO Refresh Rate: 72
20:59:45.713 INFO CEncoder::Run
20:59:45.713 INFO CEncoder Listening
20:59:45.726 INFO CEncoder client connected, pid 22049, cmdline /home/balint/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor
20:59:45.755 INFO Using Vulkan device AMD Radeon Graphics (RADV GFX1103_R1)
20:59:45.762 INFO Using device path /dev/dri/renderD128
20:59:45.813 WARNING Failed to set cursor to Default
20:59:45.813 WARNING Failed to set cursor to Text
20:59:45.880 INFO Client disconnected. Cause: Interrupted system call (os error 4)
20:59:45.880 INFO Client disconnected. Cause: Interrupted system call (os error 4)
20:59:45.893 WARNING Failed to set cursor to Text
20:59:45.894 WARNING Failed to set cursor to Default
20:59:46.690 INFO Server disconnected

Ah, sorry. @aboglioli added their error message, which is the result of nvidia HW encoding currently not working. But that issue has nothing to do with what you're struggling with.

I tried adding ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command% to SteamVR's launch settings as suggested in this comment but then SteamVR just ends up crashing every time the headset connects.

I have the same issue here. Been talking for a while in the nixos gaming Matrix channel, but haven’t been able to fix this.
Related to https://github.com/alvr-org/ALVR/issues/2476. Back then a kernel update had fixed it, but then after a few days and a flake update it broke again.

I’d recommend changing the issue title tho. The black view without the vrmonitor launch args is a thing on ALVR.
The NixOS issue here is that ALVR shouldn’t crash when you add the vrmonitor launch args thing.

Same issue on NixOS unstable trying to connect a Quest 1.


Carthage support

All is in the title !
Carthage is growing fast as it can, and more and more dev are using it.
How-To Support Carthage
Great work by the way dude =)

Thanks!
Carthage will be supported.

I did something on a branch on my side : develop-carthage
I Will cleanup it a bit, re-check tests and double check if really have to delete all cocoapods ref/folder ...
But it works

Sounds good, thanks for helping out!


Handle applyTo properly for parameter sources, when the output doesn't exist yet

When a parameter has its source set to an output, there is a bit of an awkward question of how to handle the install action. The output won't exist yet. So either the user must supply a value for the install action, the author must make the parameter optional by setting a default or the bundle author must use applyTo to list all the actions except install.
One option is that porter can default the applyTo for authors when the parameter source is set to an output, excluding the install action, when the author hasn't set a default or applyTo themselves. If they wanted the parameter to be required on install, they would need to set applyTo explicitly.
Transforming this:
parameters:
  - name: tfstate
    type: file
    path: config.json
    source:
      output: config.json

into this in the bundle.json
parameters:
  - name: tfstate
    type: file
    path: config.json
    source:
      output: config.json
    applyTo:
      - upgrade
      - uninstall

This would let authors write what I think will come more naturally to them (most won't think about the install lacking the output edge case and want to list out the applyTo by hand and maintain it if they have custom actions).

Ah, an interesting problem for sure.  While I definitely like the approach of building for the common use case and in this scenario keeping the yaml config to a minimum, I still worry about the potential pitfall for users expecting the parameter (with source of type output) to apply to their custom actions (when/if they don't set up applyTo for the param) but it ends up being unapplied by Porter behind the scenes.
Perhaps instead of the bundle.json mod behind the scenes, we could add a bit of logic in the install action code to support circumventing the issue described above.  Maybe, for each param that depends on a source of type output, unapply this param for this install action only.  Like an "on-the-fly unapply" ™ instead of manual/permanent updates to the bundle.json.
My other thought would be to introduce (even if behind the scenes and not in the manifest itself) the inverse of applyTo: ignoreFor or some such, to specify a subset of actions that the parameter should not apply to.

I still worry about the potential pitfall for users expecting the parameter (with source of type output) to apply to their custom actions (when/if they don't set up applyTo for the param) but it ends up being unapplied by Porter behind the scenes.

Can we walk through that a bit to make sure I understand? This is what I was thinking for porter's defaulting of applyTo:
Porter will default the applyTo when:

A source output is set AND
No default is set AND
No applyTo is set

The applyTo will be defaulted to all defined actions, built-in and custom, excluding install. If they need something more exciting than that then they need to define applyTo themselves. For instance, if they have a custom action that is intended to be executed before install, they would need to define applyTo manually and also exclude it. I definitely see the use case for an exclude so that you could just say exclude "install" and "preflight" and not have to list everything. That would be an alternative way to do this, but I think this has merit as a default.
Here's an example that includes a custom action:
name: wordpress
version: 0.1.0

mixins:
- terraform

parameters:
  - name: tfstate
    type: file
    path: /cnab/app/tfstate
    source:
      output: tfstate

outputs:
  - name: tfstate
     type: file
     path: /cnab/app/tfstate

install:
  - terraform:
       description: Install the world
       # this creates /cnab/app/tfstate

status:
  - terraform:
        description: Check up on world
        # this uses /cnab/app/tfstate

upgrade:
  - terraform:
       description: Upgrade world
       # this uses and updates the tfstate output

uninstall:
  - terraform:
     description: Sorry world
     # This uses and updates the tfstate output

The parameter written to the bundle.json would look like this:
parameters:
  - name: tfstate
    type: file
    path: config.json
    source:
      output: config.json
    applyTo:
      - status
      - upgrade
      - uninstall

Do you think this would be a safe default as long as it was documented that by default source outputs exclude the install output and that you need to manually configure applyTo if you have custom actions that are meant to be executed before install?

Ohh, I see: The applyTo will be defaulted to all defined actions, built-in and custom, excluding install.  With that clarification, I'm definitely on board.  (Had misunderstood that detail in the original description).  Yup, I'm now in support with the direction here.  Thank you!


[FEATURE]  executeAsync

Are you using the latest version of this library?

[X] I verified that the issue exists in the latest next-safe-action release

Is there an existing issue for this?

[X] I have searched the existing issues and found nothing that matches

Suggest an idea
I would like to await my execute and get the result inline instead of using the callbacks. Like e.g. mutate and mutateAsync in react-query. Was this already thought about / why is this not possible?
I would like to do something like this:
const result = await executeAsync(input)

Additional context
No response

You can await the Server Action by directly calling it. If you want to await execute from useAction/useOptimisticAction hooks this is currently not possible, due to a React limitation discussed in #72. This limitation will go away when useActionState will land in Next.js.

Ah I see thank you @TheEdoRan so its because useTransition is used under the hood and that currently cannot be awaited?
The thing is I would like to still keep the loading and error states of the useAction hook thats why I was asking. :)

so its because useTransition is used under the hood and that currently cannot be awaited?

Yes, exactly.

The thing is I would like to still keep the loading and error states of the useAction hook thats why I was asking.

Yeah, hopefully this will be fixed with useActionState hook, unfortunately React APIs for Server Actions are still pretty unstable (and undocumented) at this time.

Hey, I also miss this feature, if someone wants to have the execute async, there is my custom hook to handle it:
import { useRef } from 'react';

import { SafeAction } from 'next-safe-action/.';
import { HookCallbacks, useAction } from 'next-safe-action/hooks';
import { Schema, z } from 'zod';

export const useSafeAction = <const S extends Schema, const Data>(
  safeAction: SafeAction<S, Data>,
  callbacks?: HookCallbacks<S, Data> | undefined,
) => {
  const promiseResolveRef =
    useRef<(values: Data | PromiseLike<Data>) => void>();
  const promiseRejectRef = useRef<(reason?: any) => void>();

  const action = useAction(safeAction, {
    ...callbacks,
    onSettled: (result, input, reset) => {
      if (result.data) {
        promiseResolveRef.current?.(result.data);
      } else {
        const message =
          result.fetchError || result.serverError || 'Unknown error';
        promiseRejectRef.current?.(message);
      }

      promiseResolveRef.current = undefined;
      promiseRejectRef.current = undefined;

      callbacks?.onSettled?.(result, input, reset);
    },
  });

  const execute = async (input: z.infer<S>) =>
    new Promise<Data>((resolve, reject) => {
      promiseResolveRef.current = resolve;
      promiseRejectRef.current = reject;

      action.execute(input);
    });

  return {
    ...action,
    execute,
  };
};

@kriziu awesome, that works! But be aware that Next.js recommends to use useTransition or useOptimistic for non-form elements, and form related hooks for forms. This will be hopefully solved by useActionState once for all.


New Network Steward Vote system

This does NOT introduce any consensus changes, however the documentation speaks about consensus changes as through they were real, based on the assumption that winner of an election will be a consensus-critical matter. Detailed description of the changes for your review is to be found in docs/network_steward_vote_2.md
https://github.com/cjdelisle/PKT-FullNode/blob/ns-election4/docs/network_steward_vote_2.md

Reading over the docs and a quick glance at code, it looks good.  I will try get around to running it and playing with voting in next few days.


Quad IO without continuous mode/mode bits ...

Hello, I've been looking at an upstream project pico-boot2-generator which uses your database to auto-generate second-stage boot code for the RP2040.  I am trying to figure out ways to support the Winbond W25Q128JW 1.8v flash chip.
According to the datasheet, this chip supports Fast Read Quad I/O command (0xEB), but it does not support using the Continuous Mode bits that tell the flash to stay in that command forever. So the SSI needs to issue the 0XEB command on every read. No big deal, I can see how to support that in hand-written code, but I'm interested in getting it to work with pico-boot2-generator.
However, in all of the flash support code I've seen so far there seems to be an assumption that Continuous Mode is supported wherever Quad I/O is supported.  And yet this appears not to be the case for my chip.
Basically it seems to me that there's a feature of flash chips, Continuous Mode Supported (true/false), that's missing from your schema. If it was in the schema, then tools like pico-boot2-generator could use it to auto-generate proper code for chips like the W25Q128JW.
But I may be wrong?  Is there some existing field in your schema that covers this?

I'd be happy to merge a PR that adds a new field for that.


Pass models in predict rather than their methods

Previously we would pass around Estimator.predict methods.  These methods are
opaque to serialization heuristics used in dask.distributed that are used to
determine what should move and how to serialize it.
Now we pass around bare functions that take in estimators as parameters.

I would also like to replace this code in this PR if sensible: https://github.com/dask/dask-ml/issues/399

+1 removing apply_partitionwise.
FYI, I'm debuging the CI failures now. I don't have a minimal example for tests.feature_extraction.test_text.py::test_hashing_vectorizer[bag] yet. It's failing in the new atop-fusion code. This doesn't hit it unfortunately
In [28]: X = da.random.uniform(size=(10, 10), chunks=5)

In [29]: X.map_blocks(scipy.sparse.csr_matrix).blocks[0].compute()
Out[29]:
<5x10 sparse matrix of type '<class 'numpy.float64'>'
        with 50 stored elements in COOrdinate format>

I'm happy to take a look if you like
On Thu, Oct 11, 2018 at 10:54 AM Tom Augspurger<EMAIL_ADDRESS>wrote:

+1 removing apply_partitionwise.
FYI, I'm debuging the CI failures now. I don't have a minimal example for
tests.feature_extraction.test_text.py::test_hashing_vectorizer[bag] yet.
It's failing in the new atop-fusion code. This doesn't hit it unfortunately
In [28]: X = da.random.uniform(size=(10, 10), chunks=5)
In [29]: X.map_blocks(scipy.sparse.csr_matrix).blocks[0].compute()
Out[29]:<5x10 sparse matrix of type '<class 'numpy.float64'>'
with 50 stored elements in COOrdinate format>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-ml/pull/400#issuecomment-428982275, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszFa7hof7WuPaq2wOOhgDun80SZ9vks5uj1uHgaJpZM4XXhpZ
.

Hmm yeah I might appreciate that :)
It seems that all 3 are atop-fusion related... tests/preprocessing/test_data.py::TestQuantileTransformer::test_basic seems like the easiest. The other two involve cross dataframe or bag -> dask array boundaries.

Cool.  I'll finish up what I'm working on now (more of this PR) and then
switch to that.  Should be there in 10min or so
On Thu, Oct 11, 2018 at 11:07 AM Tom Augspurger<EMAIL_ADDRESS>wrote:

Hmm yeah I might appreciate that :)
It seems that all 3 are atop-fusion related...
tests/preprocessing/test_data.py::TestQuantileTransformer::test_basic
seems like the easiest. The other two involve crossing dataframe or bag ->
dask array boundaries.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-ml/pull/400#issuecomment-428988426, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszAX_ZYOVuz3AWdXgHdMwu-CYbKEEks5uj17LgaJpZM4XXhpZ
.


Change zookeeper helm chart dependency

The current zookeeper helm chart component of Pinot's Kubernetes deployment is deprecated as of Nov 13, 2020.
Consider changing to the more up-to-date, better documented helm chart from bitnami: https://github.com/bitnami/charts/tree/master/bitnami/zookeeper

The switch to Bitnami’s ZooKeeper chart was made in #7955 (chart v7.0.0, ZooKeeper v3.7.0). Later updated to v9.2.7 version of the chart (ZooKeeper v3.8.0) in #8936. I think the issue can be closed now.


Expo publish fails on fresh install

On a brand new ignite expo project, running expo publish results in the following error
Processing asset bundle patterns:
- /Users/user/Documents/projects/PizzaApp/**/*

Cannot read properties of undefined (reading 'forEach')
TypeError: Cannot read properties of undefined (reading 'forEach')
    at _configureExpForAssets (/Users/alexanderlindkjaer/.nvm/versions/node/v16.14.0/lib/node_modules/expo-cli/node_modules/xdl/src/ProjectAssets.ts:168:26)
    at exportAssetsAsync (/Users/alexanderlindkjaer/.nvm/versions/node/v16.14.0/lib/node_modules/expo-cli/node_modules/xdl/src/ProjectAssets.ts:229:3)
    at Object.publishAsync (/Users/alexanderlindkjaer/.nvm/versions/node/v16.14.0/lib/node_modules/expo-cli/node_modules/xdl/src/project/publishAsync.ts:93:3)
    at actionAsync (/Users/alexanderlindkjaer/.nvm/versions/node/v16.14.0/lib/node_modules/expo-cli/src/commands/publish/publishAsync.ts:103:18)

This is an old expo-cli issue but one that should not happen in newer sdk's.
Non of the solutions from the original issue works.
in app.json you can change assetBundlePatterns from **/* to assets/* to make it run without error, but none of the assets will be uploaded or available in the build. Furthermore the ignite boilerplate places assets in lots op places, not only in the assets folder.
Im thinking it has something to do with dependencies or babel setup 🤔
Installing a clean expo TS project (non-ignite)  with the same sdk from ignite, does not produce the error.

Steps to reproduce
You need to have a logged in expo account to publish.
npx ignite-cli new PizzaApp --expo
cd PizzaApp
expo publish

npx ignite-cli doctor results:
System
  platform           darwin
  arch               arm64
  cpu                8 cores      Apple M1
  directory          PizzaApp     /Users/alexanderlindkjaer/Documents/LindkjaerProjects/PizzaApp

JavaScript (and globally-installed packages)
  node               16.14.0      /Users/alexanderlindkjaer/.nvm/versions/node/v16.14.0/bin/node
  npm                8.3.1        /Users/alexanderlindkjaer/.nvm/versions/node/v16.14.0/bin/npm
    corepack         0.10.0
    expo-cli         5.2.0
    npm              8.3.1
  yarn               1.22.17      /opt/homebrew/bin/yarn
  pnpm               -            not installed

Ignite
  ignite-cli         7.10.5       /Users/alexanderlindkjaer/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite
  ignite src         build        /Users/alexanderlindkjaer/.npm/_npx/e31027f378

Found the culprit after hours of poking at files. It's the metro.config.js file.  I took the advice from the comments in that file and deleted the file and the dependencies it used. Now Expo published assets fine.
So thats a workaround to get i working 🙂 Will leave the issue open, as the default boilerplate should work with expo publish out-of-the-box.

Hey @AlexanderLindkjaer, thanks for solving that! Do you have any idea which part of that config was the issue?

@robinheinze
The whole makeMetroConfig() call makes it not publish
module.exports = (async () => {
  const defaultConfig = await getDefaultConfig()
  //   return makeMetroConfig({ <--- commenting this out will make it publish
  //     projectRoot: __dirname,
  //     resolver: {
  //       resolveRequest: MetroSymlinksResolver(),
  //       assetExts: [...defaultConfig.resolver.assetExts, "bin"],
  //     },
  //   })
})()

If you do it a more traditional way of just exporting an object, instead of a async function returning  makeMetroConfig(...)
it publishes fine. the const defaultAssetExts is i bit dirty, but skips the async await.
// get defaults assetExts array
const defaultAssetExts = require("metro-config/src/defaults/defaults").assetExts

module.exports = {
  projectRoot: __dirname,
  resolver: {
    resolveRequest: MetroSymlinksResolver(),
    assetExts: [...defaultAssetExts, "bin"],
  },
}

Disclaimer: I dont use pnpm or any monorepo stuff, so i dont know if the provided solution still gives the desired results 🙂

:tada: This issue has been resolved in version 7.10.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Board cann't be compatible with upgrade and downgrade version

In GitLab by @sokril on Nov 16, 2017, 08:42
If you are reporting a problem, please make sure the following information are provided:

Version of board (last git commit number) , docker engine and docker-compose.
Config files of board, you can get them by packaging "board.cfg" and files in the same directory, including subdirectory.
Log files, you can get them by package the /var/log/board/.
Other necessery information.

In GitLab by @sokril on Nov 8, 2019, 08:14
assigned to @yhua123

In GitLab by @luotian-github on Dec 17, 2019, 09:05
assigned to @sokril and unassigned @yhua123

In GitLab by @luotian-github on Mar 4, 2020, 12:16
assigned to @wknet123 and unassigned @sokril

In GitLab by @luotian-github on Mar 25, 2020, 02:19
If there is no change in DB, support upgrade and downgrade Board Now.
If there is some changes in DB, need to consider some DB trans tool


javac not found

I am  trying to compile Openni or Arm architecture. However build fails due to missing Java libraries. Following to tutorial I've tried to install Java6 but it seems like it is not longer available and I can't get it.
How can I solve it ?
Thanks Chris

Dude Javac comes with the JDK, you need that, not the JRE.
you probably have JRE.


Feat/code snippet

Overview
Adds code snippets to Graph Explorer
Demo

Notes
This PR uses Hooks. Learn more about hooks here
Testing Instructions

Launch Graph Explorer
Observe a Code Snippets tab
Click on it
Observe that snippets are loaded for the supported languages.

@cwahome

Show syntax highlighting for code snippets in Java and Objective-C

Monaco highlights keywords. I am not sure if the Java and Objective-C snippets have keywords. To be certain that syntax highlighting works, type a keyword in the Java snippet.

Truncation of the query parameters now works.


Custom Authorizer

Now that AWS API Gateway has introduced Custom Authorizer, does the approach described here change in anyway ?

No. Sigv4 continues to work exactly as it did before. Customer authorizers allow you to leverage bearer tokens such as JWT tokens or SAML assertions. It's an alternative approach.


Allow timestamp to be set

Link to issue #7.

Add timestamp as a parameter of send in  tsdb_client.py
Add timestamp as a parameter of set in metrics.py
Fix test and README

And add an useful .gitignore :)

Hi, @scarchik sry to be insistent, do you think this PR is ok and don't break anything in your project ? :)
I really need it in the coming weeks.

I'm on vacation now. I will be able to review and answer on next week.
пн, 13 мая 2019 г., 10:46 Bouchoucha Jordan<EMAIL_ADDRESS>
Hi, @scarchik https://github.com/scarchik sry to be insistent, do you
think this PR is ok and don't break anything in your project ? :)
I really need it in the coming weeks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scarchik/opentsdb-py/pull/8#issuecomment-491733491,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGRP7W76PWMW3U4NSCAX3DPVETHLANCNFSM4HLG4KHA
.

Hi, any news about this PR ?


Hot reloading on v6

Is hot reloading that maintains state possible? I can't see any reference to elm-live in v6.

Hot reloading is not supported with the built-in elm-spa server.
You can still use elm-spa with the elm-live dev server, and it should be used alongside elm-spa watch, as shown in the Vite example.
This general technique also allows you to use Parcel, Webpack, or any other dev server you prefer!

I'll check this out. Thanks


Location of Teams data at rest diagram needs to be updated with new OneDrive and SPO locations for recordings

Hi,
With the new ODfB and SPO location as an option for storing meeting recording, I believe this diagram needs to be updated?
Link : https://docs.microsoft.com/en-us/microsoftteams/location-of-data-in-teams#location-of-teams-data-at-rest
Thanks

@DevJonBirkett Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@DevJonBirkett thank you for reaching out and helping improve MS Docs. Do you perhaps have the recommended updated screenshot?

Hi,
It looks like the location-of-teams-data-at-rest section has been removed?
It used to include the attached diagram.

With a possible updated version being:

Hi,
It looks like the location-of-teams-data-at-rest section has been removed?
It used to include the attached diagram.

With a possible updated version being:

@MicrosoftHeidi @SerdarSoysal please can you confirm if this screenshot needs to be added to the article.

@MicrosoftHeidi @SerdarSoysal please can you confirm if this screenshot needs to be added to the article.

Hi @MicrosoftHeidi Hope you are well. Wanted to follow up here to see if there is an update? Please let us know if there is anything we can do to help. Thanks.

Hi @MicrosoftHeidi Hope you are well. Wanted to follow up here to see if there is an update? Please let us know if there is anything we can do to help. Thanks.

@MicrosoftHeidi Wanted to follow up on this request. Please let us know if there is anything we can do to help.

@MicrosoftHeidi Wanted to follow up on this request. Please let us know if there is anything we can do to help.

@MicrosoftHeidi Wanted to follow up on this request. Please let us know if there is anything we can do to help.

@MicrosoftHeidi Wanted to follow up on this request. Please let us know if there is anything we can do to help.

@MicrosoftHeidi Wanted to follow up on this request. Please let us know if there is anything we can do to help.

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Ability to add screenshots to an issue

It'd be nice to have the ability to attach screenshots to individual findings.  The age-old adage "a picture is worth a thousand words" often applies.
And thanks for the great tool!

I'm able to upload a test.png file, view it when I click on "List Current Attachments" but when the report is generated it does not show up.


Update renovatebot/github-action action to v34.152.5

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
minor
v34.149.0 -> v34.152.5

Release Notes

renovatebot/github-action
v34.152.5
Compare Source
See the the changelog for changes in all releases.
34.152.5 (2023-02-26)%0A%0A%0A### Bug Fixes%0A%0A* deps: update renovate/renovate docker tag to v34.152.5 (db243d3)%0A%0A
v34.152.4
Compare Source
See the the changelog for changes in all releases.
34.152.4 (2023-02-24)
Bug Fixes

deps: update renovate/renovate docker tag to v34.152.4 (4e061f6)

v34.152.3
Compare Source
See the the changelog for changes in all releases.
34.152.3 (2023-02-24)
Bug Fixes

deps: update renovate/renovate docker tag to v34.152.3 (0b9819c)

v34.152.2
Compare Source
See the the changelog for changes in all releases.
34.152.2 (2023-02-23)
Bug Fixes

deps: update renovate/renovate docker tag to v34.152.2 (121f0ae)

v34.152.0
Compare Source
See the the changelog for changes in all releases.
34.152.0 (2023-02-23)
Bug Fixes

deps: update renovate/renovate docker tag to v34.152.0 (3807d5f)

Configuration
📅 Schedule: Branch creation - "before 5am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Branch automerge failure
This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


Command: IBM i: Compare with Selected and readonly open tabs does not remove readonly attribute

Command: IBM i: Compare with Selected and readonly open tabs does not remove readonly attribute.  When the context menu command Select for Compare and the command IBM i: Compare with Selected are selected the tool chooses the active tab in which to preload the input box for the member to compare to.  If this active tab happens to be for a member opened in read only mode the readonly attributes are appended to the open member string.

Expectations would be that the text ?readonly%3Dtrue not appear in the input string.
This is a low priority for me as I can easily just remove that string or not open members in readonly when comparing.

Context
Version

Code for IBM i version
2.4.0

Visual Studio Code version
1.83.0

Operating System
win32_x64

Active extensions
Code Spell Checker (code-spell-checker): 3.0.1
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.3.2
Db2 for IBM i (vscode-db2i): 0.5.0
ESLint (vscode-eslint): 2.4.2
Emmet (emmet): 1.0.0
Error Lens (errorlens): 3.14.0
Extension Authoring (extension-editing): 1.0.0
Git (git): 1.0.0
Git Base (git-base): 1.0.0
GitHub (github): 0.0.1
GitHub Authentication (github-authentication): 0.0.2
IBM i Notebooks (vscode-ibmi-notebooks): 0.0.6
JSON Language Features (json-language-features): 1.0.0
Markdown Language Features (markdown-language-features): 1.0.0
Markdown Math (markdown-math): 1.0.0
Markdown Preview Enhanced (markdown-preview-enhanced): 0.8.5
Merge Conflict (merge-conflict): 1.0.0
Node Debug Auto-attach (debug-auto-launch): 1.0.0
Overtype (overtype): 0.5.0
Partial Diff (partial-diff): 1.4.3
RPGLE (vscode-rpgle): 0.21.4
SQL Formatter VSCode (sql-formatter-vsc): 2.1.1
Text Marker (Highlighter) (text-marker): 1.11.0
Todo Tree (todo-tree): 0.0.226
TypeScript and JavaScript Language Features (typescript-language-features): 1.0.0
WSL: Recommender (remote-wsl-recommender): 0.0.19
classdiagram-ts (classdiagram-ts): 0.1.67
macros (macros): 1.2.1
undefined (indent-rainbow): 8.3.1

Remote system

Setting
Value

IBM i OS
V7R5M0

Tech Refresh
2

CCSID
37

SQL
Enabled

Source dates
Enabled

Enabled features

/QOpenSys/pkgs/bin
/usr/bin
/QSYS.lib/ILEDITOR.lib
/QSYS.LIB
/QIBM/ProdData/IBMiDebugService/bin

bash
attr
GENCMDXML.PGM
QZDFMDB2.PGM
startDebugService.sh

git
iconv
GETNEWLIBL.PGM

grep
setccsid

ls

md5sum

sort

stat

tar

tn5250

Shell env

Variants
{
  "american": "#@$",
  "local": "#@$"
}

Errors

I'll look into that, I need some distraction 😅

There you go 😉


Metropolis font metrics backtick fix

Regression found on Unicode character 0060 width allocation and fixed
New metrics revised and a 303-glyph set supplied as a replacement for the inline Clarity CSS. This is a complete Latin encoding.
Font packaging sidenote:
Highly recommend: removing all inlined BASE 64 chunks. Not only does this add to the overload payload size of Clarity, but it is perhaps inefficient because a text format is used to carry not one, but multiple fonts. Newer font encoding methodologies have since been released, such as WOFF2 for modern browsers. I understand Issue #3269 was recently made, hope it gets in soon. As for dealing with FOUT issue, if and when it occurs, I can recommend clean workarounds in the browser.

Signed-off-by: Matt<EMAIL_ADDRESS>

This change seems to have had an affect on all of the visual regression suites.
You can run run visual regression tests locally. Here is how light theme, set one could be run:
npm run test:visual:light set1

If the failures that are reported are something that should be included with the changes to the font, we need to update the reference images. Reference image updates can be done via:
npm run visual:fix:light set1```

This is only being applied to one font (regular), shouldn’t it be applied to all instances? I’m also curious why there are so many visual diff failures here, something we’ll need to analyze very closely.

@mattmutt Do you have any follow up on this? We would need to see the fix not break the visual diff testing and also be applied to all font weights.

I have not done any deeper visual difference checking on the font metrics. Can the team report back on their assessment with examples of broken/missing characters? Since there may be variations on the weights, I'll leave it to the visual designers to consider the other font permutations; didn't want to incur other changes.

Hey Matt, to see whats going on you can run npm run test:visual:light setX for each of the 4 sets.
I'm sorry I am not a font expert so its difficult so correlate the changes to characters.
The change as provided seems to have a dramatic effect on all of the visual regression sets. I would have expected them to remain unaffected by this change as I'm assuming it only related to the backtic character.

@hippee-lee Here are some visual diffs. Because font rasterization engines are different, the subpixel aliasing differences will become apparent. Now I do challenge a human to be able to hand pick these subtle differences when placed side by side. Ultimately one would correctly guess that engines that transform OTF to WOFF have different mathematical libraries. For the changes here, I only modified the metric on the backtick.

Our images don't use the backtick character in nearly any place, so seeing so many broken image diffs is concerning. One of the images shows more significant differences (the info alert) and I would have to inspect every image to know what else might be affected. The fact its only applied to one of the fonts doesn't really address the problem the whole way, so if people need this fix
We've discussed this internally, and are concerned about the fallout of the changes. Also, we have plans for addressing this in a more holistic manner soon that would allow teams to opt-into fixes so we don't get caught in a situation where this could accidentally break an application.
Projects can opt into this as a workaround for the backtick issue if the differences don't impact their project, but we're not comfortable shipping this change. Thanks @mattmutt for digging into this, and we'll point people to this if they need to patch it on their side until our next stage is ready.


Add continuous logging in AWS Lambda

Currently, the lambda function is not logging the output of the executed command. We need this logs for longer running jobs where the CLI might timeout. Also, we would like these logs to be written to Logwatch continuously instead of the end of the command execution.
:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/vast, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
We are limited to specific "threading" libraries on AWS lambda. multiprocessing for instance usually doesn't work with the pool and queue interfaces. This is why we use the basic threading module with a small adapter to get the return values from the threaded function.
Also modified logging.basicConfig(level=logging.INFO) because it seems that it is not working properly on Lambda because of some pre-initialization of the logger in the Lambda python runtime.

@dominiklohmann not sure why the "Check Labels" workflow is hanging :-\

@dominiklohmann not sure why the "Check Labels" workflow is hanging :-\

The label on this PR pre-dated this new check. I just removed it and added it back.


Is visual tracking against privacy?

Hi
Just a question about visual tracking/heatmaps/hotjar/etc.  Is this against privacy?
If so, how?  I've seen a few articles about this, but nothing explaining how.

Privacy is not a term that is too well defined, so this will be a subjective take.
I'd argue that all tracking is against privacy, always. If you want perfect privacy for your users, mute your server logs and remove all analytics software of all kinds. However, sometimes this is not a feasible scenario so it's about making tradeoffs. Building Offen we selected a subset of data that seems to be a good compromise between being useful and still respecting user privacy. Visual tracking is not something we'll ever do as for us, it's not justifiable to collect a lot of data that is unique to a certain user when you compare it to the insights it can give operators.
That being said, one thing all tracking ever should be doing is: do not use 3rd party services, it's just never ok to share such data with others (no matter the TOS) and it's also not needed.


Operating system support: Take 3

We now support all of the Linux distros that Screenfetch supports!
(Excluding discontinued distros)
In this issue I'm aiming to support all of the Distro Requests in
Screenfetch's issue tracker. These distros will be harder to add
support for due to availability and ease of use.
Those wanting to contribute can pick a distro from the list below.

exherbo Linux
coreos
Red Hat Enterprise Linux 7 Beta
ChromeOS
ChromiumOS

I'm downloading exherbo Linux.

Added support for exherno Linux.

Red Star OS is discontinued, right?
It was renamed to Estrella Roja and that one is discontinued.

Removed it from the list, thanks.

From what I know ChromeOS and ChromiumOS are based on Gentoo, so they should work.

Yup, we still need to provide ascii art though. Having a look at
Screenfetch, they're both named like this:
Chrome OS
Chromium OS

If we add the ascii art and colors then in theory it should work
just fine.

Added Chrome OS ascii art and colors.

Installing a VM right now.

But here's a question: why would a CrOS user need fetch support?

What do you mean by CrOS?

ChromeOS.

If it's simple to add support then why not? The more distros we
support the more people will be able to use fetch and that's a
win.

Chromium OS now uses the same ascii as ChromeOS as it's
difficult to add Chromium colors since they're various shades
of blue and we're limited in the colors we can use.

Well the majority of people are using ChromeOS and then ChromiumOS, so there's no problem. ChromiumOS is mostly used by enthusiasts to see what's the fuss about.

I couldn't get Chromium OS to work in a virtual machine btw,
if you also can't get it working then we'll still tick Chrome OS
and Chromium OS off the list. They should work just fine if
we compare our implementation to Screenfetch.

Due to the difficulty in installing / obtaining the distros above
I'm going to close this issue. If anyone running these distros
wants support added then they'll need to open an issue them-
selves.

I've had a crack at CoreOS... https://github.com/dylanaraps/neofetch/pull/832


Quickstart command

What this PR does / why we need it:
This PR adds pipectl quickstart command and removes the previous test command pipectl install controlplane
The current usage:
$ pipectl quickstart
$ pipectl quickstart --uninstall

Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

Add pipectl quickstart command

Umm, I agree with removing the previous command but I don't think this is essential.
If these prerequisites were reduced, it would be a nice improvement but this looks just like a rapper.
Is there a specific meaning for preparing this command?

since the install controlplane is just a wrapper to helm command and not bring a well defined enough interface, to me it just add complexity to the usage of the pipectl command, that why I think it's better to remove it. Besides, we haven't officially introduced it yet, so remove it don't cause any issue to our users, I guess.
If it's really a need to have that kind of sub command, I will rethink and add it later, wdyt?

And for the new pipectl quickstart I omit the fact that we need to preinstall helm so that helm not familiar users can easily make a try with PipeCD in their local, that's the point 👀

I separated the removing pipectl install command to this PR, lets merge it first before this PR 🙏
https://github.com/pipe-cd/pipecd/pull/3933

...helm not familiar users can easily make a try with PipeCD in their local

I suppose many users will copy and paste the code when installing a quickstart.
Hence I think the users don't need to be familiar with helm.

And for the new pipectl quickstart I omit the fact that we need to preinstall helm

However, this seems enough value to add a new command because this is an effective way to reduce the user's labor and get rid of any barriers like allergic reactions.

However, this seems enough value to add a new command because this is an effective way to reduce the user's labor and get rid of any barriers like allergic reactions.

yes, that's my point 👍


Add HeapSnapshotGenerator crash patch

Pulls in https://codereview.chromium.org/2669393002 to prevent crashes when taking heap snapshots, https://bugs.chromium.org/p/chromium/issues/detail?id=661223
This can be dropped once Chrome 58 is upgraded to.
Refs https://github.com/electron/electron/issues/8791

:bow:, this has been trolling me


[Snyk] Security upgrade mkdocs-material from 8.5.11 to 9.5.32

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.
Snyk changed the following file(s):

vendor/github.com/urfave/cli/v2/mkdocs-requirements.txt

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting (XSS)

Checkmarx One – Scan Summary & Details – 8192cbaa-0a48-4dc6-8246-b628067fe534
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2023-45288
Go-golang.org/x/net-v0.7.0
Vulnerable Package

CVE-2024-24786
Go-google.golang.org/protobuf-v1.28.1
Vulnerable Package

CVE-2024-40641
Go-github.com/projectdiscovery/nuclei/v2-v2.7.7
Vulnerable Package

Passwords And Secrets - Generic Password
/mallgard.json: 26
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/zabbix-default-password.json: 12
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/Alibaba Nacos 控制台默认弱口令.json: [54](https://github.com/TheRedHatter/scan4all/blob/snyk-fix-6ad95e0fe1710a24549bfe7f8ff38e61//lib/goby/goby_pocs/Alibaba Nacos 控制台默认弱口令.json#L54)
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/Hsmedia_Hgateway_Default_account.json: 28
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/showdoc-default-password.json: 12
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/D-Link_AC_management_system_Default_Password.json: 32
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/Mallgard_Firewall_Default_Login_CNVD_2020_73282.json: 34
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/Alibaba_Nacos_Default_password.json: 56
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/Alibaba Nacos 控制台默认弱口令.json: [28](https://github.com/TheRedHatter/scan4all/blob/snyk-fix-6ad95e0fe1710a24549bfe7f8ff38e61//lib/goby/goby_pocs/Alibaba Nacos 控制台默认弱口令.json#L28)
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/SDWAN_Smart_Gateway_Default_Password.json: 32
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/ZhongXinJingDun_Information_Security_Management_System_Default_Login.json: 69
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/Wayos_AC_Centralized_management_system_Default_Password_CNVD_2021_00876.json: 34
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/ZhongXinJingDun_Default_administrator_password.json: 65
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/Alibaba_Nacos_Default_password.json: 29
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/XXL_JOB_Default_password.json: 28
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/Wayos AC集中管理系统默认弱口令  CNVD-2021-00876.json: [28](https://github.com/TheRedHatter/scan4all/blob/snyk-fix-6ad95e0fe1710a24549bfe7f8ff38e61//lib/goby/goby_pocs/Wayos AC集中管理系统默认弱口令  CNVD-2021-00876.json#L28)
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/WAVLINK_WN535G3_POST_XSS_CVE_2022_30489.json: 67
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Password
/WAVLINK_WN535G3_POST_XSS_CVE_2022_30489.json: 32
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Token
/cve_2022_1388_goby.json: 73
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Token
/cve_2022_1388_goby.json: 35
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Token
/shtermQiZhi_Fortress_Arbitrary_User_Login.json: 22
Query to find passwords and secrets in infrastructure code.

Passwords And Secrets - Generic Token
/H3C SecParh堡垒机任意用户登录.json: [11](https://github.com/TheRedHatter/scan4all/blob/snyk-fix-6ad95e0fe1710a24549bfe7f8ff38e61//config/poc/h3c/H3C SecParh堡垒机任意用户登录.json#L11)
Query to find passwords and secrets in infrastructure code.

CVE-2024-0406
Go-github.com/mholt/archiver-v3.1.1
Vulnerable Package

CVE-2024-6104
Go-github.com/hashicorp/go-retryablehttp-v0.7.1
Vulnerable Package

Fixed Issues

Severity
Issue
Source File / Package

CVE-2023-42818
Go-golang.org/x/crypto-v0.0.0-20220829220503-c86fa9a7ed90

Passwords And Secrets - Generic API Key
/CVE-2022-24112.yaml: 43

Passwords And Secrets - Generic Password
/db_tests: 3191

Passwords And Secrets - Generic Password
/jira-servicedesk-signup.yaml: 45

Passwords And Secrets - Generic Password
/CVE-2020-17456.yaml: 28

Passwords And Secrets - Generic Password
/simple-crm-sql-injection.yaml: 20

Passwords And Secrets - Generic Password
/CVE-2007-4556.yaml: 25

Passwords And Secrets - Generic Password
/lutron-iot-default-login.yaml: 14

Passwords And Secrets - Generic Password
/db_tests: 1355

Passwords And Secrets - Generic Password
/CVE-2022-34590.yaml: 29

Passwords And Secrets - Generic Password
/grafana-default-password.yml: 12

Passwords And Secrets - Generic Password
/CVE-2019-17444.yaml: 29

Passwords And Secrets - Generic Password
/CVE-2020-6637.yaml: 31

Passwords And Secrets - Generic Password
/db_tests: 1113

Passwords And Secrets - Generic Password
/CVE-2022-29009.yaml: 28

Passwords And Secrets - Generic Password
/coldfusion-cve-2010-2861-lfi.yml: 11

Passwords And Secrets - Generic Password
/zms-auth-bypass.yaml: 28

Passwords And Secrets - Generic Password
/vmware-operation-manager-log4j.yaml: 35

Passwords And Secrets - Generic Password
/db_tests: 2888

Passwords And Secrets - Generic Password
/wp-xmlrpc-brute-force.yaml: 36

Passwords And Secrets - Generic Password
/CVE-2022-34048.yaml: 30

Passwords And Secrets - Generic Password
/dahua-cve-2021-33044-authentication-bypass.yml: 10

Passwords And Secrets - Generic Password
/top-xss-params.yaml: 21

Passwords And Secrets - Generic Password
/minio-default-password.yml: 12

Passwords And Secrets - Generic Password
/CVE-2022-29007.yaml: 28

Passwords And Secrets - Generic Password
/tomcat-pathnormalization.yaml: 25

Passwords And Secrets - Generic Password
/chinaunicom-modem-default-password.yml: 10

Passwords And Secrets - Generic Password
/graylog-log4j.yaml: 34

Passwords And Secrets - Generic Password
/ricoh-weak-password.yaml: 23

Passwords And Secrets - Generic Password
/CVE-2020-7136.yaml: 29

Passwords And Secrets - Generic Password
/CVE-2015-7245.yaml: 26

Passwords And Secrets - Generic Password
/3com-nj2000-default-login.yaml: 23

Passwords And Secrets - Generic Password
/cvms-sqli.yaml: 27

Passwords And Secrets - Generic Password
/CVE-2022-31269.yaml: 49

Passwords And Secrets - Generic Password
/db_tests: 6754

Passwords And Secrets - Generic Password
/wifisky-default-password-cnvd-2021-39012.yml: 10

Passwords And Secrets - Generic Password
/optilink-ont1gew-gpon-rce.yaml: 27

Passwords And Secrets - Generic Password
/CVE-2019-16097.yaml: 28

Passwords And Secrets - Generic Password
/db_tests: 1187

Passwords And Secrets - Generic Password
/minio-default-password.yml: 22

Passwords And Secrets - Generic Password
/nuclei_esConfig.yaml: 15

Passwords And Secrets - Generic Password
/CVE-2022-29006.yaml: 28

Passwords And Secrets - Generic Password
/db_tests: 2889

Passwords And Secrets - Generic Password
/ruijie-eg-password-leak.yaml: 20

Passwords And Secrets - Generic Password
/db_tests: 1244

Passwords And Secrets - Generic Password
/db_tests: 1109

Passwords And Secrets - Generic Password
/kingsoft-v8-default-password.yml: 10

Passwords And Secrets - Generic Password
/vmware-nsx-log4j.yaml: 32

Passwords And Secrets - Generic Password
/CVE-2020-13167.yaml: 25

Passwords And Secrets - Generic Password
/vpms-auth-bypass.yaml: 26

Passwords And Secrets - Generic Password
/CVE-2022-2467.yaml: 30

Passwords And Secrets - Generic Password
/CVE-2019-14223.yaml: 28

Passwords And Secrets - Generic Password
/db_tests: 6768

Passwords And Secrets - Generic Password
/db_tests: 6753

Passwords And Secrets - Generic Password
/CVE-2019-1010287.yaml: 29

Passwords And Secrets - Generic Password
/db_tests: 2887

Passwords And Secrets - Generic Password
/CVE-2021-46073.yaml: 37

Passwords And Secrets - Generic Password
/db_tests: 523

Passwords And Secrets - Generic Password
/db_tests: 1128

Passwords And Secrets - Generic Password
/db_tests: 952

Passwords And Secrets - Generic Password
/ruijie-information-disclosure.yaml: 21

Passwords And Secrets - Generic Password
/CVE-2022-0968.yaml: 42

Passwords And Secrets - Generic Password
/db_tests: 6698

Passwords And Secrets - Generic Password
/CVE-2022-32094.yaml: 29

Passwords And Secrets - Generic Password
/db_tests: 6755

Passwords And Secrets - Generic Password
/vmware-hcx-log4j.yaml: 35

Passwords And Secrets - Generic Password
/CVE-2019-9733.yaml: 32

Passwords And Secrets - Generic Password
/db_tests: 1099

Passwords And Secrets - Generic Password
/CNVD-2020-23735.yaml: 19

Passwords And Secrets - Generic Private Key
/CVE-2020-7136.yaml: 29

Passwords And Secrets - Generic Secret
/api-petfinder.yaml: 22

Passwords And Secrets - Generic Secret
/CVE-2022-2546.yaml: 34

Passwords And Secrets - Generic Secret
/CVE-2022-2546.yaml: 52

Passwords And Secrets - Generic Token
/h3c-secparh-any-user-login.yml: 9

Passwords And Secrets - Generic Token
/db_tests: 6731

Passwords And Secrets - Generic Token
/CVE-2018-19892.yaml: 36

Passwords And Secrets - Generic Token
/chinaunicom-modem-default-password.yml: 10

Passwords And Secrets - Generic Token
/CVE-2022-1388.yaml: 34

Passwords And Secrets - Generic Token
/ofbiz-default-login.yaml: 23

Passwords And Secrets - Generic Token
/dedecms-cve-2018-7700-rce.yml: 11

Passwords And Secrets - Generic Token
/top-xss-params.yaml: 20

Passwords And Secrets - Generic Token
/db_tests: 6247

Passwords And Secrets - Generic Token
/.coveralls.yml: 1

Passwords And Secrets - Generic Token
/CVE-2020-16846.yaml: 24

Passwords And Secrets - Generic Token
/ricoh-weak-password.yaml: 23

Passwords And Secrets - Generic Token
/hue-default-credential.yaml: 62

Passwords And Secrets - Generic Token
/rainloop-default-login.yaml: 43

Passwords And Secrets - Generic Token
/top-xss-params.yaml: 21

Passwords And Secrets - Generic Token
/CVE-2022-1388.yaml: 47

Passwords And Secrets - Password in URL
/cloudinary.yaml: 16

Host Namespace is Shared
/docker-compose.yml: 4

Host Namespace is Shared
/docker-compose.yml: 27

Host Namespace is Shared
/docker-compose.yml: 4

Host Namespace is Shared
/.drone.yml: 47

Networks Not Set
/docker-compose.yml: 27

Networks Not Set
/docker-compose.yml: 4

Networks Not Set
/.drone.yml: 47

Networks Not Set
/docker-compose.yml: 4


BF(DOC): point to numpy.select instead of plain (python) .select

Also added spaces into an example invocation to keep encoraging
consistent (PEP8) formatting, and moved period outside of verbatim
quotes - it is not part of the code
Note: didn't check if docs build/reference numpy correctly yet, doing it ATM ;)

yes that looks good. interesting, we check that all references resolve, but can't tell we got the Python rather than the NumPy intersphinx link. thanks @yarikoptic


Add Charter

This is a copy of the current Hyperledger Charter.
Signed-off-by: Ry Jones<EMAIL_ADDRESS>

A rendered version is here: https://ryjones.github.io/tsc/
Please note, which making this file, I found two typos in the version published on the website. That version may not yet be updated when you attempt to compare them

One could argue that this doc doesn't belong to the TSC and therefore shouldn't be in the TSC repo but other than that, LGTM.

My thought was this is a governing document, and to include it for reference. Not that the TSC would be amending it here.

Per request


If the service takes a long time to start,admin checkd upstream fail,it can't be registed

Describe the bug

Environment

Soul version(s): [e.g. 2.2.1]

Steps to reproduce
Expected behavior

Debug logs

Click to expand
replace this line with your debug logs

can you fix it？

Duplicate of https://github.com/dromara/soul/issues/1113


new submission: get started with grafana alerting part 3

looks good in my Scenarios

@jdbaldry
hi Jack ! Could you please review/approve this PR since Jay is out ? 🙏🏼


X-Frame-Options header

X-Frame-Options header

This issue was imported from Google Moderator
Moderator votes: +4
Issue added by Kevin on 2012-11-07
To vote this issue up or down, simply include +1 or -1 in your comment.

Duplicate of #1138.


Headline with h2 element has broke IMG link

Challenge Name

https://www.freecodecamp.com/challenges/headline-with-the-h2-element
Issue Description
IMG link to Cat's Photo App is broken
Browser Information

Browser Name, Version: Chrome Version 56.0.2924.87 (64-bit) and Firefox  52.0 32bit
Operating System: Windows 7 64bit
Mobile, Desktop, or Tablet: Dell E7470 Laptop

Your Code
NA
Screenshot

Hey, it renders fine for me. Looks like imgur is blocked in your case? Are you behind a firewall or something?
Can you check on a alternate network?

Very possible.  I'll check when I'm off the domain.

Closing. We strongly believe this has to do with your network and not the code base. Please feel free to continue on the thread should you need any assistance.


Genefunk v1.1 Fixes several roll and calculation bugs

Submission Checklist
Required

[X] The pull request title clearly contains the name of the sheet I am editing.
[X] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[X] The pull request makes changes to files in only one sub-folder.
[X] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description
Bug Fixes

[X] When attacks are made, the following message appears for both PCs and NPCs
[X] Attacks with weapons display the fluff text (description of the weapon) every time an attack is made, which isn't necessary and clutters up the chat window.  Maybe this text was intended to appear when you click the equipment instead? Or only appear in the compendium?
[X] Claws (trait) successfully appears under “Attacks” when dragged, but nothing happens when you click the attack
[X] The Initiative bonus displayed isn’t auto-calculating for PCs, and seems stuck at 0. Passive Perception and Passive Insight also do not auto-calculate.
[X] The Sleight of Hand, Life Science, Physical Science, and Social Science skill checks don’t work when clicked, seemingly due to character length
[X] Some traits for NPCs and PCs display “undefined” text in a couple of spots when clicked. For example, [images in attached document]
[X] Attack mod displayed in collapsed view was not calculated correctly

Character Sheet Info Roll20 Internal Use only.


RAND_DRBG: Implement randomness generation for UEFI

This issue has been braught up in the recent OSTIF Security Audit of the OpenSSL 1.1.1 Random Number Generation and still needs to be addressed.
The following text is a minimally redacted excerpt from opensslrng-audit-report.pdf:
E. UEFI randomness generation
In rand_unix.c the following defines are made:
https://github.com/openssl/openssl/blob/23d221b771348e3e3ee316cd1190a4a344d145fc/crypto/rand/rand_unix.c#L91-L94
The UEFI specification from 2.4 upwards supports generating random numbers using the protocol
EFI_RNG_PROTOCOL. The implementation details are in a driver called rngdxe and can be
summarized as “uses RDRAND plus various DRBGs as specified in SP800-90.
We have not audited this code ourselves. We mention this as one of two possible alternatives to “none” on
UEFI platforms:

Use it.
Since it is based on RDRAND anyway, use that to collect randomness for the seed value

Related to: #7945 #7946

cc @veorq

For x86 and x86/64, I don't see a need to support this.  We have hooks for RDRAND and RDSEED already.  Having a second way to access RDRAND seems pointless.  It might even be detrimental -- we choose RDSEED over RDRAND but do UEFI platforms or are they limited to RDRAND?
For ARM, ARM/64 and Itanium, I can see some benefit.  Remember that these platforms do not have RDRAND, so some investigation will be required to see if what they do is meritorious.

@paulidale as far as I understand it, this issue is not about UEFI in general, but rather about the case when OPENSSL_SYS_UEFI is defined and in which OPENSSL_RAND_SEED_NONE is enforced. I did not dig into the sources yet to find out when this case precisely applies.

Cleaning up old neglected issues...


The shaders implicitly convert Standard Alpha to Premultiplied

calculatePixel() function from ShaderShared.cginc multiplies color by alpha, thus making semitransparent sprites much darker than with Unity default sprite shader (which keeps pixel format intact).
Is it intentional or not? I think the color-blending function is not supposed to also convert pixel format, so I changed e.g.
finalPixel.a = texureColor.a * color.a;      finalPixel.rgb = (texureColor.rgb * color.rgb) * finalPixel.a;
to
finalPixel = texureColor * color;
But I have to ask, what was the original rationale behind the conversion?

Hey! Good catch, that is a mistake - I've checked in a fix for it (it was also multiplying the color by the alpha in some other places when using standard alpha blending).
Thanks!


5.1 channels not detected in EAC3 file

Using this sample file from the FFMpeg library I found this.

I don't get the issue: MediaInfo displays "6 channels" and the layout "L C R LFE Ls Rs" is fine (and same as FFmpeg: Ls and Rs are "side", LFE is ".1") and coherent (6 channels are listed everywhere, in both MediaInfo and FFmpeg:  5 "normal" channels + 1 "LFE" = 6 channels).
Which discrepancy are you talking about?

Maybe I can't find it or there isn't supposed to be this line but the ChannelPositions/String2 seems missing and that's what would give information such as 3/2/0.1 or 3/2/2.1 which clearly identifies 5.1 and 7.1 channels.

Ha, OK, I see now, issue is that ChannelPositions/String2 is missing for E-AC-3, and you rely on it for LFE channel presence. Not difficult to add.
Note that is is not a discrepancy as MediaInfo output is not wrong, and there are other means to clearly identify ".1" e.g. LFE word in ChannelPositions or ChannelLayout

Should be OK in Snapshots, reopen the ticket if something is missing.


Update AE standard method blacklist to use a whitelist

The code that performs inspections for disallowed java calls (shows red squiggly lines in the IDE) is using a blacklist of a few methods. We should look into instead using the official whitelist that AE uses so that users don't mistakenly think their code will deploy when it won't.
https://cloud.google.com/appengine/docs/java/jrewhitelist

We may want to move this into app-tools-lib-for-java since Eclipse does this too. See https://github.com/GoogleCloudPlatform/gcloud-eclipse-tools/blob/master/plugins/com.google.cloud.tools.eclipse.appengine.whitelist/src/com/google/cloud/tools/eclipse/appengine/whitelist/AppEngineJreWhitelist.java

Yea I think it makes sense too:
https://github.com/GoogleCloudPlatform/app-tools-lib-for-java/issues/166

Closing this. The integrated JB plugin already used a whitelist, I just missed it the first time around: AppEngineForbiddenCodeInspection#visitReferenceElement
The only modification needed is to pull the whitelist class from the common lib instead of the appcfg jar - this will happen as part of the SDK refactoring.


✨[feature Request]: LOGO FOR RETRO

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description

for retro, this first logo would look great which is designed by me!
or second one is ai generated...
I'd like to add to any of  these...or change with any of your desirable inputs
can you assign this to me @l
Use Case

the above logo can be replaced
this can be replaced in the retro name ( in nav bar )
this would create an aesthetic unique sense for users
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24EXTD contributor
[X] I have starred the repository

@laxmikandivalasa  go ahead.


Single interface registered incase of Multiple interface implementation to service

I used 2.7.12 & 2.7.14 & 3.0.4 versions of Dubbo for maven multi module project, the problem is while the serviceImpl(UserService) is implementing 3 interfaces, only the one in the first gets registered with the service discovery (Nacos)
If I change the FetchUser interface next to implements keyword (UserService implements FetchUser) then fetchuser gets registered.
Am I missing something here? Or is it something a limitation to apache dubbo? Any help is appreciated. Thanks
My Service class implements multiple interfaces like below
package com.business.usermanagement.usecaseImpl

@Component @DubboService
public class UserService implements UserOnboarding, FetchUser, ModifyUser {

}

Base Application class as below
@SpringBootApplication
@DubboComponentScan("com.business.usermanagement")
public class UserManagementApplication {

    @DisableLog
    public static void main(String[] args) {
        SpringApplication.run(UserManagementApplication.class, args);
    }

}

and below is the dubbo configuration
dubbo:
  protocol:
    name: dubbo
    port: -1
  registry:
    address: nacos://${nacos.discovery.server-addr}/?username=${nacos.discovery.username}&password=${nacos.discovery.username}
  metadata-report:
    address: nacos://${nacos.discovery.server-addr}
  application:
    name: ${spring.application.name}

You can Dubbo ServiceConfig API or <dubbo:service> definition to define multiple service. Dubbo only support a service with one interface. You should register each interface to Dubbo even those target implementation are the same.

Thanks @AlbumenJ Is it possible for you to provide some reference for the same? I am unaware of this approach.

ServiceConfig serviceConfig1 = new ServiceConfig<>();
serviceConfig1.setInterface(UserOnboarding.class);
serviceConfig1.setTarget(xxx);
serviceConfig1.export();
ServiceConfig serviceConfig2 = new ServiceConfig<>();
serviceConfig2.setInterface(FetchUser.class);
serviceConfig2.setTarget(xxx);
serviceConfig2export();
ServiceConfig< ModifyUser > serviceConfig3 = new ServiceConfig<>();
serviceConfig3setInterface(ModifyUser.class);
serviceConfig3.setTarget(xxx);
serviceConfig3.export();


(3.0) txn: Check lock's TTL when doing cleanup (#5471)

What have you changed?
This PR cherry-picks #5471 , which is part of refinement of pessimistic transactions, to release-3.0 branch. For more details please view #5471 .
What is the type of the changes?

New feature (a change which adds functionality)

How is the PR tested?

Unit test
Integration test

Does this PR affect documentation (docs) or should it be mentioned in the release notes?

No.

Does this PR affect tidb-ansible?
No.
Refer to a related PR or issue link (optional)

Cherry-picks: #5471
Corresponding PR in TiDB: pingcap/tidb#12417

Also PTAL @coocood @tiancaiamao

LGTM


[PDI-13875] Update Google Analytics plugin to v3 APIs

forward port (via cherry-pick) of 3 PRs from the 5.4 branch

Should this wait before merging on the master->future merge?

Merge it, there is a lot of ppl looking fowarding for this step to work again.

@lucboudreau I think it should go before, so that the forward-port to 6.0 is automatic. I am testing now locally to make sure it will work in master, then it should port without trouble to future.

Self-merge with approval from @dkincade , dev tested successfully in master


Output JSON

Is your feature request related to a problem? Please describe.
I want to pipe the output of this tool to other CLI commands, or perform a complex formatting.
Describe the solution you'd like
I'd like a flag --json which makes the output display as JSON to sdout.

ponyrep --json tweag/ponyrep is now a thing
[
  {
    "url": "https://api.github.com/repos/tweag/ponyrep/issues/1",
    "when": "2022-11-10 11:44:51 UTC",
    "who": "GuillaumeDesforges",
    "category": "OPEN 1",
    "what": "Output JSON"
  }
]

Format will certainly evolve because it's currently simplistic.


[New Port Request] LibCrypto++

Library name: LibCrypto++
Library description: Crypto++ Library is a free C++ class library of cryptographic schemes.
Source repository URL: https://github.com/weidai11/cryptopp
Project homepage (if different from the source repository): https://cryptopp.com/
Anything else that is useful to know when adding (such as optional features the library may have that should be included):  I've tried several cryptographic libraries for C++ and this one seems to provide the most convenient features.

I was reading the Install.txt file and noticed that it's already available as "cryptopp", without the "lib" prefix.


feat(doc-site): Adding doc-site

Overview
This is part 1 of the doc-site update CR, which was having numerous test/build issues.
this only consists of the testing-util changes
UPDATE : merged the doc-site changes to this CR
Legal
This project is available under the Apache 2.0 License.

@mnischay What's the plan for this PR?

@mnischay What's the plan for this PR?

good to merge, after Luci's approval, had a merge conflict


Set DOCKER_TIMEOUT for squashing

When squashing an image, the default docker-scripts timeout is 10 minutes. It would be nice to be able to tweak that as needed, by setting the DOCKER_TIMEOUT environment variable from a configuration setting.

the easiest thing to do is probably tweak dockerfile of the build image

Closing due to lack of interest and activity. If you're still interested feel free to reopen it.
Also, the plan is to move away from docker completely.


Move to 2.0 branch for security plugin

Description
Move to 2.0 branch for security plugin
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2003 (355f14a) into main (1c05b1a) will increase coverage by 5.58%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main     #2003      +/-   ##
=============================================
+ Coverage     94.41%   100.00%   +5.58%
=============================================
  Files           187         6     -181
  Lines          3739       105    -3634
  Branches         29        19      -10
=============================================
- Hits           3530       105    -3425
+ Misses          203         0     -203
+ Partials          6         0       -6

Impacted Files
Coverage Δ

src/ci_workflow/ci_test_manifest.py

src/git/git_repository.py

src/test_workflow/perf_test/perf_test_cluster.py

src/ci_workflow/ci_manifests.py

src/run_ci.py

...ests/jenkins/jobs/AssembleManifest_tar_Jenkinsfile

...enkins/jobs/BuildDockerImage_Qualifier_Jenkinsfile

...rkflow/integ_test/service_opensearch_dashboards.py

...ts/jenkins/jobs/uploadMinSnapshotsToS3_Jenkinsfile

...est_workflow/bwc_test/bwc_test_start_properties.py

... and 171 more

Continue to review full report at Codecov.

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


6.0 Feedback:  6.0.0-alpha.0 - app settings text is repeated

Overview
The text is repeated twice on the App Software Version section of App Settings > General

Current Behavior
No response
Expected Behavior
No response
Steps To Reproduce
No response
Operating system
No response
Robot setup or anything else?
No response

verified


Yelp Ratings Urls seems to have poorly edited photos

Hi, upon using your api to search for businesses within my application I noticed that some of the ratings images have a non-transparent background.  Normally this wouldn't be a problem if you display them on a white background; however, our site has a dark background and it becomes increasingly noticeable.  I see that you also have some ratings image resources available to download, but those are using an image map and even on the api demo site you are using relative background positioning of the map to display an individual row.  I'd like to avoid that over-engineering if possible in my situation and am wondering if maybe you all can just update your cdn image links? Here is an example:

Let me know if there is an alternate solution as well.
Thanks,
Thomas

@tomelm , want to have a quick look?

Hey @SchlegelThomas! We're looking into this.

thanks! let me know when you have an update.

Any Updates?

@SchlegelThomas , this is still on are todo list, but not near the top. In my own personal project I got around this by downloading the image map from the display requirements page, chopped it up manually saving them as 1.png, 1.5.png, etc so that I could serve them directly based on the rating field of a business. Of course using the image map itself is probably a more elegant solution, but I liked the simplicity of cutting it up into separate images.

@watterso Would you mind if I created my own local resource based off of what you've already got then?  I can submit it here for review if you'd like.  I just wanted to make sure we weren't breaking any terms and conditions as far as usage goes.

Hey @SchlegelThomas,
After some internal discussion, we've decided that if you want those new stars you should download them from the display requirements page. As mentioned on that page, you are not allowed to alter them. The kind of alterations that are forbidden are those that change the physical look of the image. So you can cut out the rows of stars from the image map and serve them how you want, but you can't make them green, sparkly, more red or more yellow, or anything of that sort.
TL;DR: use the stars from the display requirements page, but don't change how they look.
Closing this out now :)


Mouse location on plot

I'm new to scottplot so if this is mentioned elsewhere please let me know. Is there a way to find the location of the mouse on the plot and put the values in the plot?
Ideally I'd like it to be pinned to the curve its plotting.

Hi @AndrewN199
ScottPlot will plot values in a double array. You cannot use the mouse to change the content of the array (so no adding values of moving values) using ScottPlot, but you can write your own event handlers to do this if it is necessary for your application.
You can convert between pixel locations and coordinates using plt.CoordinateFromPixel() and plt.CoordinateToPixel()
If your goal is to interact with the mouse (a slightly different topic), you'll find the "show value on hover" demo (in the demos folder) useful.
Hope it helps!