Cant run tool, something wrong in default config

./prometheus_data_dump --config.file=cfg.yml -v
ts=2024-02-20T10:51:33.274Z caller=main.go:72 level=info msg="Starting prometheus data export " version="(version=v1.3.0, branch=refs/tags/v1.3.0, revision=ab5c941626702ab6ce53234f8253f77cb9766c31)"
ts=2024-02-20T10:51:33.274Z caller=main.go:78 level=info msg="show only configuration ane exit"
prometheus_export
Actual configuration:
Server:       [<IP_ADDRESS>:9090]
Data path:    [./dump]
Days back:    [2]
Sources:
[localhost.+ (false)]
Labels:       [N/A]
./prometheus_data_dump --config.file=cfg.yml
ts=2024-02-20T10:52:01.085Z caller=main.go:72 level=info msg="Starting prometheus data export " version="(version=v1.3.0, branch=refs/tags/v1.3.0, revision=ab5c941626702ab6ce53234f8253f77cb9766c31)"
ts=2024-02-20T10:52:01.085Z caller=main.go:92 level=error msg="problem with configuration" error="invalid character 's' looking for beginning of value"
Program did not start due to configuration error!
Error: invalid character 's' looking for beginning of value

Hi, can you validate your cfg.yml file in any YAML validator?
for example: https://www.yamllint.com/ or https://codebeautify.org/yaml-validator
The message is clear speak: Error: invalid character 's' looking for beginning of value

yamllint cfg.yml
cfg.yml
  1:1       warning  missing document start "---"  (document-start)

When added, still "almost" same error
./prometheus_data_dump --config.file=cfg.yml
ts=2024-02-20T13:25:07.561Z caller=main.go:72 level=info msg="Starting prometheus data export " version="(version=v1.3.0, branch=refs/tags/v1.3.0, revision=ab5c941626702ab6ce53234f8253f77cb9766c31)"
ts=2024-02-20T13:25:07.561Z caller=main.go:92 level=error msg="problem with configuration" error="invalid character '-' in numeric literal"
Program did not start due to configuration error!
	Error: invalid character '-' in numeric literal

Please, can you share your cfg.yml?

Looks promising and im getting some json out. But i want to use label to get only metrics starts with node, but still no luck. When label: section is deleted, working fine.
cat cfg.yml

---
server: localhost
path: ./dump
from: 2024-01-19 00:00
to: 2024-01-19 01:00
step: 60
storeDirect: true
sources:
  - instance: localhost:9100
  - instance: another_host:9100
labels:
  - name: node

Getting
ts=2024-02-20T21:50:16.828Z caller=main.go:72 level=info msg="Starting prometheus data export " version="(version=v1.3.0, branch=refs/tags/v1.3.0, revision=ab5c941626702ab6ce53234f8253f77cb9766c31)"
ts=2024-02-20T21:50:16.829Z caller=main.go:92 level=error msg="problem with configuration" error="invalid character '-' in numeric literal"
Program did not start due to configuration error!
	Error: invalid character '-' in numeric literal

Im not able run it without three dashes, because its give me error
ts=2024-02-21T09:24:29.675Z caller=main.go:72 level=info msg="Starting prometheus data export " version="(version=v1.3.0, branch=refs/tags/v1.3.0, revision=ab5c941626702ab6ce53234f8253f77cb9766c31)"
ts=2024-02-21T09:24:29.675Z caller=main.go:92 level=error msg="problem with configuration" error="invalid character 's' looking for beginning of value"
Program did not start due to configuration error!

And when i have this yaml and even if it valid, i have error
---
server: localhost
path: ./dump
from: 2024-01-19 00:00
to: 2024-01-19 01:00
step: 60
storeDirect: true
sources:
  - instance: localhost:9100
  - instance: another_host:9100
labels:
  - name: node
    value: '.*+'

error
ts=2024-02-21T09:31:25.140Z caller=main.go:72 level=info msg="Starting prometheus data export " version="(version=v1.3.0, branch=refs/tags/v1.3.0, revision=ab5c941626702ab6ce53234f8253f77cb9766c31)"
ts=2024-02-21T09:31:25.140Z caller=main.go:92 level=error msg="problem with configuration" error="invalid character '-' in numeric literal"
Program did not start due to configuration error!
	Error: invalid character '-' in numeric literal

without labels section it just works :)
export_data_pbs# ./prometheus_data_dump --log.level=debug --log.format=json
{"caller":"main.go:72","level":"info","msg":"Starting prometheus data export ","ts":"2024-02-21T09:34:35.769Z","version":"(version=v1.3.0, branch=refs/tags/v1.3.0, revision=ab5c941626702ab6ce53234f8253f77cb9766c31)"}
{"caller":"main.go:98","level":"info","msg":"start collect necessary data","ts":"2024-02-21T09:34:35.769Z"}
{"caller":"main.go:113","level":"info","msg":"requried time split to 1 time ranges","ts":"2024-02-21T09:34:35.770Z"}
{"caller":"api-reader.go:28","level":"debug","msg":"entry collect series data for instance localhost:9100","ts":"2024-02-21T09:34:35.770Z"}
{"caller":"api-reader.go:33","level":"debug","msg":"instance filter: {instance=~\"localhost:9100\"}","ts":"2024-02-21T09:34:35.770Z"}
{"caller":"api-reader.go:53","level":"debug","msg":"collect 0 from 0 series for instance localhost:9100","ts":"2024-02-21T09:34:35.778Z"}
{"caller":"storage.go:42","level":"debug","msg":"final main store path /data/petr/prometheus_export_data/dump","ts":"2024-02-21T09:34:35.778Z"}
{"caller":"storage.go:58","level":"debug","msg":"directory for store final data exist and accessible","path":"/data/petr/prometheus_export_data/dump/localhost9100","ts":"2024-02-21T09:34:35.779Z"}
{"caller":"storage.go:97","file":"organize-localhost9100.json","level":"debug","msg":"data successful saved to disk","ts":"2024-02-21T09:34:35.779Z"}
{"caller":"api-reader.go:28","level":"debug","msg":"entry collect series data for instance another_host:9100","ts":"2024-02-21T09:34:35.779Z"}
{"caller":"api-reader.go:33","level":"debug","msg":"instance filter: {instance=~\"another_host:9100\"}","ts":"2024-02-21T09:34:35.779Z"}
{"caller":"api-reader.go:53","level":"debug","msg":"collect 0 from 0 series for instance another_host:9100","ts":"2024-02-21T09:34:35.779Z"}
{"caller":"storage.go:42","level":"debug","msg":"final main store path /data/petr/prometheus_export_data/dump","ts":"2024-02-21T09:34:35.779Z"}
{"caller":"storage.go:58","level":"debug","msg":"directory for store final data exist and accessible","path":"/data/petr/prometheus_export_data/dump/another_host9100","ts":"2024-02-21T09:34:35.780Z"}
{"caller":"storage.go:97","file":"organize-another_host9100.json","level":"debug","msg":"data successful saved to disk","ts":"2024-02-21T09:34:35.780Z"}
{"caller":"main.go:163","level":"info","msg":"prepared GO coroutines channel data","ts":"2024-02-21T09:34:35.780Z"}
{"caller":"main.go:175","level":"info","msg":"wait to finish all 9 routines","ts":"2024-02-21T09:34:35.780Z"}
{"caller":"main.go:211","level":"debug","msg":"funish coroutine 7","ts":"2024-02-21T09:34:36.780Z"}
{"caller":"main.go:211","level":"debug","msg":"funish coroutine 1","ts":"2024-02-21T09:34:36.780Z"}
{"caller":"main.go:211","level":"debug","msg":"funish coroutine 0","ts":"2024-02-21T09:34:36.780Z"}
{"caller":"main.go:211","level":"debug","msg":"funish coroutine 2","ts":"2024-02-21T09:34:36.780Z"}
{"caller":"main.go:211","level":"debug","msg":"funish coroutine 6","ts":"2024-02-21T09:34:36.780Z"}
{"caller":"main.go:211","level":"debug","msg":"funish coroutine 3","ts":"2024-02-21T09:34:36.780Z"}
{"caller":"main.go:211","level":"debug","msg":"funish coroutine 8","ts":"2024-02-21T09:34:36.780Z"}
{"caller":"main.go:211","level":"debug","msg":"funish coroutine 5","ts":"2024-02-21T09:34:36.780Z"}
{"caller":"main.go:211","level":"debug","msg":"funish coroutine 4","ts":"2024-02-21T09:34:36.780Z"}
{"caller":"main.go:177","level":"info","msg":"all coroutines finish 1.000537309s","ts":"2024-02-21T09:34:36.780Z"}
{"caller":"main.go:125","level":"info","msg":"program successful ends after 1.010831089s","ts":"2024-02-21T09:34:36.780Z"}

It's strange. In every config.yaml dump, I see that it starts with dashes. What system do you use? What editor do you use?
server: builder03.vrane.pokornyit.cz
path: ./dump
from: "2024-02-21 12:00"
to: "2024-02-21 13:00"
step: 10
sources:
  - instance: 'local.+'
labels:
  - label: group
    value: pc
    excludeMetrics: ^go_.*

You can look to your Prometheus UI and validate labels (i.e. here is define group=pc)


"or add to your ~/.xsessionrc or ~/.xinitrc."

It would be great if you could add these steps. I am not a Linux power user and I can't find any guides on how to add GSDE to  ~/.xsessionrc or ~/.xinitrc.
I did all the other steps and they worked fine just getting blocked at this point.
I installed 64-Bit Raspberry Pi OS Lite, SSH'd into my Pi 4B and ran these commands and scripts, all worked fine I just need instructions on how to do the above.

Xsession is standard way how to start apps at Window startup.

create file .xsession file in your home directory
add /System/bin/startgsde to it
change the permissions chmod 0755 ~/.xsession

I was actually coming to comment on something similar.  I'm doing a new clean install on Debian and am trying to document every step (doing it on a 2015 Macbook Pro).
Since the Debian instructions call for doing a "no X11" then any new GSDE users will end up with a tty prompt.  My initial reaction was simply to log in as root and running apt install wdm to keep things looking relatively the same.
Perhaps adding wdm to the script install-dependencies-debian.sh would be a good idea?

I was actually coming to comment on something similar. I'm doing a new clean install on Debian and am trying to document every step (doing it on a 2015 Macbook Pro).
Since the Debian instructions call for doing a "no X11" then any new GSDE users will end up with a tty prompt. My initial reaction was simply to log in as root and running apt install wdm to keep things looking relatively the same.
Perhaps adding wdm to the script install-dependencies-debian.sh would be a good idea?

NEXTSPACE has a superb login application that I believe could be used

I improved the install_wdm.sh script and made instructions more explicit. It should make clean installation of GSDE in Debian easier.


Repo documentation links

Hi I’m just investigating tailwindcss form my django project, this looks like it might work form me but I had issues with your documentation.
All the links point to rtfs.io.me but the pages seem to be hosted on readthedocs.io

Fixed. I updated the broken links and link definitions. Thanks for reporting.


Switch Component Switches to disabled state on checked on Native

Current Behavior

Expected Behavior
https://tamagui.dev/docs/components/switch/1.28.0
should not switch to disabled state, like in the docs on web.
Tamagui Version
'latest' per the next starter 1.39.6

Reproduction
https://github.com/benschac/repo-switch-disable

System Info
npmPackages:
    @babel/runtime: ^7.18.9 => 7.21.0
    @manypkg/cli: ^0.19.1 => 0.19.2
    check-dependency-version-consistency: ^3.0.3 => 3.0.3
    eslint: ^8.21.0 => 8.39.0
    node-gyp: ^9.3.1 => 9.3.1
    prettier: ^2.7.1 => 2.8.8
    turbo: ^1.10.3 => 1.10.3
    typescript: ^5.1.3 => 5.1.3

just noticed this too, when i brought back active theme state it happened...

is it not the same on web? may be but on the site we dont show the plain light switch just the colored version...

ive tweaked themes on the latest so it doesnt look disabled!

lmk if that didnt work


Suggestion

Great job - suggestion, add commenting in/out line/s.It should be easy copy, refactoring and paste from visual studio

@lyudmilpetrov Not sure what exactly you suggest. Is it comment and uncommenting a line? That would be Ctrl + /.
Maybe add a small code example that shows before and after.

Hi Martin,
Sorry for wasting your time, it is what you suggested, I just did not know
the short key for that.
Embarrassing and keep up the great work guys,
all the best,
Lyudmil
On Tue, Nov 8, 2016 at 9:20 AM, Martin Aeschlimann<EMAIL_ADDRESS>
wrote:

@lyudmilpetrov https://github.com/lyudmilpetrov Not sure what exactly
you suggest. Is it comment and uncommenting a line? That would be Ctrl + /
.
Maybe add a small code example that shows before and after.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/15127#issuecomment-259148235,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADsRT0FyyErsMk7gIsVh_1JybLcFwoqxks5q8IUwgaJpZM4KrwlT
.

No problem, thanks for the quick reply.


check firmware version

Hi,
Currently when you flash new firmware I cant find a way to tell if the firmware was successfully updated.
I have tried to run a diff on the files on the keyboard and the ones outputted from the build but there is some binary difference
The PRO version also does not have the "status report" functionality that the wired version has so I cant find a way to output the version of firmware that is currently running or verify the version in any other way.
Is there a known way to check the firmware version currently running on the 369 PRO version?
Thanks for any feedback on this. I have been unable to locate any documentation on how to achieve this.

Right now this is not possible, but this is several new solutions in mind to improve this

One "hack" is to add a custom mapping somewhere, or you could add macro in the mod layer that has a date code or other unique build identifier. We may even look to do that at the factory.

Is there even any way to tell whether my keyboard shipped with 2.0 or 3.0? I need to know whether to run the 2.0 settings reset before applying my own build.

Thx for the information.  This would be a great improvement in the future but for now I'll work on an unsupported way of dealing with this. Appreciate everyone's input

https://github.com/KinesisCorporation/Adv360-Pro-ZMK/pull/267


Avolonia XAML Preview does not work with design time viewmodel properly occasionally

Describe the bug
The following code will result in the following error in the avolonia diagnostics window in visual studio:
System.Xaml.XamlException: 'Unable to resolve type MainViewModel from namespace using:CCA.Source.Features.Main Line 11, position 4.' Line number '11' and line position '4'.
View
<Window xmlns="https://github.com/avaloniaui"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        mc:Ignorable="d" d:DesignWidth="800" d:DesignHeight="450"
        x:Class="CCA.Source.Features.Main.MainView"
	xmlns:vm="using:CCA.Source.Features.Main"
        Title="MainView">

	<Design.DataContext>
		<vm:MainViewModel/>
	</Design.DataContext>

    <TextBlock Text="{Binding Title2}"/>

</Window>

ViewModel
namespace CCA.Source.Features.Main;

internal partial class MainViewModel : ViewModelBase
{
    [ObservableProperty]
    private string _title2;

    public MainViewModel()
    {
        Title2 = "This is a test title";
    }
}

My Folder Structure:

Removing the "Design.DataContext" attribute will show the preview again.
Also the behaviour in visual studio and rider differs:
Visual Studio 2022 Version: 17.5.4: The property "Title2" will not be suggested in visual studio

Rider 2023 Version 1.1 Build: RD-231.8770.54: Rider will show me at least the property suggestion

If i open the sample application from avalonia or create a new avalonia project without changing to a custom name eg: CCA, this error usually does not occur.
Debugging the project works without problems.

OS: Windows
Version 10.0.19045 Build 19045
Nuget Packages:
Avalonia 0.10.19
Avalonia.Desktop 0.10.19
Avalonia.Diagnostics 0.10.19
CommunityToolkit.Mvvm 8.2.0
XamlNameReferenceGenerator 1.6.1

Am i doing something wrong here ?

Removing the "Design.DataContext" attribute will show the preview again.

This bug was fixed in 11.0 previews. In 0.10 you can use full clr-assembly syntax for xmlns attributes, including assembly name. Like xmlns:custom="clr-namespace:SDKSample;assembly=SDKSampleLibrary".

Visual Studio 2022 Version: 17.5.4: The property "Title2" will not be suggested in visual studio

I don't think it was implemented in AvaloniaVS plugin.
Rider has richer functionality built in.
Closing as fixed (in 11.0 with workaround for 0.10).


Backtest

Hey, how do you implement takeprofit, stoploss, and trailing stop for the backtest in pips? Keep getting errors or not working properly.

To have stoploss and trailing stop be a fixed pip, not a volume based (ATR),
you would just modify
logic/stoploss.py and logic/trailingstop.py
In particular, you want to change GetPrice() function

Ah I see, thank you! Would you test the backtest again? I ran it with default settings, using the default CSV and received this error in the log:
AttributeError: 'Strategy' object has no attribute '_stoploss'
The stoploss and take profit are not working, even when importing the stoploss class to fix the above error.
To test this, I changed the ATR to multiply by different numbers, but the result of PnL at the end was always the same. Didn't change anything else, just wanted to make sure they were working.

I figured it out, just rewrote the strategy class. Question, how would I be able to calculate the MACDSIGNAL? I can calculate the MACD since its fast ema - slow ema, but not sure how to apply EMA to MACD with a period. I'm trying to stick to your coding method. MACDSIGNAL = (MACD, period=9)

You would do something like this:
    macd,macdsignal,macdhist = talib.MACD(numpy.array(candles_close_prices), macd_fast_period, macd_slow_period, macd_signal_period)
    macdsignal = macdsignal[-1]


Update README.md

Updated folder structure with unit test cases written in repo.

Updated folder structure with unit test cases written in repo.

Thanks for the PR!


Add Fragment block + create "schedule consult" frag.

Will add this to our repo:
https://www.hlx.live/developer/block-collection/fragment
Then create a fragment for the /documents/brief pages' section called "Ready for a consultation?"

Closing complete per https://github.com/hlxsites/merative2/pull/87

Word doc of the schedule consult fragment:
https://merative.sharepoint.com/:w:/r/sites/Merative.comWebsite/_layouts/15/Doc.aspx?sourcedoc={F5175FD5-5026-4328-B2F4-2BC37BF72B67}&file=cta-schedule-consult.docx&action=default&mobileredirect=true
https://main--merative2--hlxsites.hlx.page/fragments/cta-schedule-consult


fix admin menu does not appear in rtl langs

Issue Reference
Link: #5342
How To Test This?
Needs run vendor:publish

Hi @AmooAti,
I just tested your pull request, one issue found to have a look,

I think the arrow should be outside.

It reproducible just toggle the button.

Hi @devansh-webkul,
I fixed the issue that you mentioned also if found another issue with closing and opening side nav and the space that content-wrapper can have, also change the direction of arrows.
but I think my code is not optimum and it can be better in nav-slide-button component (two style classes and two if conditions)

Hi @AmooAti,
Please check the mentioned review.
Although functionality is working fine but in my opinion, this can be done. What's your suggestion?

Hi @devansh-webkul,
Thanks, I've made changes and used CSS for all manners, but I have doubts about the active class that I added maybe better to use display hide selector but from another point maybe it will be useful for future customization.


Invoking Cloud Functions from GKE

Hello,
Do you know how would this work now given Cloud Functions are authenticated? I see "Your client does not have permission to get URL /denyenv?timeout=30s from this server." in the kubernetes get events log. Going by https://cloud.google.com/functions/docs/securing/authenticating#function-to-function, I need to pass in an Authorization Header and not sure how would I do that in a ValidatingWebhookConfiguration.
Spotted one typo on the README. The manifest field is webhooks: and not webHooks: May be it changed between versions.
Many thanks,
Pankaj

Do not think GKE would expose this - https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/#authenticate-apiservers.


Can I port it to Bedrock edition?

Is your feature request related to a problem? Please describe.
I love this mod. It is simple but it also makes the game feel more alive
Describe the feature you'd like
I would like to get a permission to port this mod as Bedrock Edition add-on (with all of the assets that are used in the mod)

If @ArtistMonster24 is ok with it I think it should be fine.
Be aware though that you may not be able to use sound files for the ducks since I licensed them for use in the mod. I basically got asset pack and got the permission from the author to redistribute them here on github, but only for development of this mod.


Improve layout + Clean up code

Improve the layout
Free resources
Now the show/hide forecast works

Hi humdingerb,
This is the result of writing this
https://github.com/janus2/WordClock
to find some glitches in this application that bothered me

Oh, I love those WordClocks! Installed it already.
Was it on purpose to have "Height" instead of "Eight"? :)

No, it's a typo I would found in a life time...
Thanks, I'll fix it.


Allow manifest with byte order mark (BOM)

A cargo .toml file with a byte order mark is a valid UTF-8 encoded file, and should be readable by cargo.
Current behavior (Windows):
failed to parse manifest at `C:\Path\to\Cargo.toml`

Caused by:
  could not parse input as TOML
Cargo.toml:1:1 expected a key but found an empty string

The corresponding issue for the compiler (libsyntax) is https://github.com/rust-lang/rust/issues/12974
cargo --version

cargo 0.4.0-nightly (553b363 2015-08-03) (built 2015-08-03)

Should this perhaps be handled at the parser level in the toml crate? (https://github.com/alexcrichton/toml-rs)

Thanks for the PR @andersforsgren, I release a new version of toml-rs, would you like to send a PR to update the version Cargo is using?

Ah looks like there's another reason (https://github.com/rust-lang/cargo/issues/2033) to update toml, so I'll just go ahead and do so, thanks again @andersforsgren!


Made processing thread background

in order to correctly finish host processes.

@klym1 Before I merge can you poke the version number up in dispatchers.eventstore assemblyinfo?

@rcknight Done


u"Ω" errors in precompilation

MWE: write the literalu"Ω" in a package that precompiles.
caused by: LoadError: Evaluation into the closed module `UnitsParse` breaks incremental compilation because the side effects will not be permanent. This is likely due to some other module mutating `UnitsParse` with `eval` during precompilation - don't do this.
Stacktrace:
  [1] eval
    @ Core ./boot.jl:385 [inlined]
  [2] eval
    @ DynamicQuantities.UnitsParse ~/.julia/packages/DynamicQuantities/5QflN/src/uparse.jl:1 [inlined]
  [3] uparse(s::String)
    @ DynamicQuantities.UnitsParse ~/.julia/packages/DynamicQuantities/5QflN/src/uparse.jl:37
  [4] var"@u_str"(__source__::LineNumberNode, __module__::Module, s::Any)
    @ DynamicQuantities.UnitsParse ~/.julia/packages/DynamicQuantities/5QflN/src/uparse.jl:57
...

As a quick fix you could do import DynamicQuantities.Units: Ω (or .SymbolicUnits: Ω) and work with the symbols directly.
It's weird that precompilation doesn't like it. Does anything in that module jump out to you? This is the file:
https://github.com/SymbolicML/DynamicQuantities.jl/blob/a31609fa9f732ded5a863b0f9a65211d78b7d889/src/uparse.jl#L1

It's probably due to the eval in https://github.com/SymbolicML/DynamicQuantities.jl/blob/a31609fa9f732ded5a863b0f9a65211d78b7d889/src/uparse.jl#L37

Oh I see. What other options are there for implementing this?

You can evaluate the expression yourself instead of eval.

Ah. Of course 🤦♂
Thanks, will fix.

I guess we’ll need to do something a bit more complex like https://github.com/PainterQubits/Unitful.jl/blob/a09bdaac255d456e6315b77979a48956aca1d3a3/src/user.jl#L692 to get this working without eval.


LoggerConfiguration - Avoid duplicate output when same target is reused

Skip writing to the same target multiple times, eventhough configured (Since most likely by accident).
Reducing the chance of hair-loss or high-blood-pressue when using NLog.
But having this auto-repair might lead to situation where people can create very "messy" NLog.config-example that works, but suddenly when going down the road of LoggingRule-filters, then everything explodes.

Can confirm high-blood-pressure because of this.

I like this idea! Nothing wrong with fixing silly mistakes.
But would it be better if we ignore it one applying the config?
(Ps I expect a warning in the internal logger then. Maybe also log the concequense?)

I guess the validation has to be done some where near ReconfigureExistingLoggers since I believe it is the only place where one looks at all the LoggingRules.
You have a better location?


Ability to run config generation after path mapping

Describe Request:
I would like to be able to use the results of the path mapping as parameters in a script to generate my own continue config. Right now the continue step is called immediately afterwards.
This would be very powerful for monorepos as you could use a fully featured scripting language to generate the right workflows according to project dependencies.
Examples:
version: "2.1"
            orbs:
                path-filtering<EMAIL_ADDRESS>                continuation<EMAIL_ADDRESS>            workflows:
                generate-config:
                    jobs:
                        - path-filtering/filter:
                            base-revision: main
                            skip_continue: true
                            mapping: |
                                src/.* build-code true
                                doc/.* build-docs true
                        - generate-continue-config
                        # this job would read the parameters file written by path filtering and generate a continue-config.yml
                         - continuation/continue:
                              configuration_path: continue-config.yml

You can now (not sure about when the issue was created).
I was playing around and just got something like this working:
      - path-filtering/set-parameters:
          base-revision: main
          output-path: /tmp/pipeline-parameters.json
          mapping: |
            src/.* build-code true
            doc/.* build-docs true
      - run:
          name: Generate continue-config.yml file
          command: |
            poetry run gen-config -o /tmp/continue-config.yml /tmp/pipeline-parameters.json
      - continuation/continue:
          parameters: "{}"
          configuration_path: /tmp/continue-config.yml

Closing the issue as @dsansot-ru has suggested a sensible workaround. Feel free to re-open this issue if this doesn't work for you.

As per @dsansot-ru 's suggestion, using path-filtering/set-parameters should be able to address this. Closing this issue.


Add functional options for the Ark config install library

In #437, we decided we wanted to use functional options to manage Ark config details (instead of defaulting to static times). This PR adds such a capability.

LGTM


Fix for issue #51.   Stop runtime error being thrown when FQDN is used.

Hi
some quick remarks.

Could you please follow the contribution rules which states to have PSR-2 coding style and a passing test

AbstractSegment shouldn't have a special case for a special delimiter I think you should move your modification in the Host class directly.

Hello,

Yeah I was hesitant about submitting with the changes in the AbstractSegment, however when I made any changes in the Host Class, it was causing problems in other tests.  I will take another look because I understand where you are coming from.

There is a test,  however it has no assertion, it passes through a FQDN to createFromServer() and fails when a runtime exception is triggered.  I could 'assert' the object is valid, however the test is meant to show you can pass FQDN through and throw an exception.

The issue is validateSegment() explodes the string, on either '/' or '.' delimiter.   My original approach of removing the dot is no good.  It needs to keep the dot.  Maybe someone else can have a go at solving this :)

Ok, no problem I'll try to solve this issue in v4 thanks anyway. I'll let you know when this is fix


[rmlui] Add feature for SVG rendering using lunasvg

When rmlui was first added to vcpkg, the lunasvg library necessary for SVG rendering support was not yet available in vcpkg. Since lunasvg is now in vcpkg, I've added a feature flag to build rmlui with SVG support.

[X] Changes comply with the maintainer guide.
[X] SHA512s are updated for each updated download.
[X] The "supports" clause reflects platforms that may be fixed by this new version.
[X] Any fixed CI baseline entries are removed from that file.
[X] Any patches that are no longer applied are deleted from the port's directory.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

@microsoft-github-policy-service agree

Feature test passed with x64-windows triplet.


Handle mouse clicks for systray items

Description
Relocated from https://github.com/ralismark/eww/pull/6
This implements mouse button click handling for systray icons. Meanwhile, the building widgets MenuBar/MenuItem are replaced with Box/EventBox to fulfill the event hooking.
Additional Notes
gtk::Window is subclassed just to store its global coordinates, which appears to be a bit overkill, but I didn't come up with better ideas. This could be further polished.
Checklist
Please make sure you can check all the boxes that apply to this PR.

[X] All widgets I've added are correctly documented.
[ ] I added my changes to CHANGELOG.md, if appropriate.
[ ] The documentation in the docs/content/main directory has been adjusted to reflect my changes.
[X] I used cargo fmt to automatically format all code before committing

Looks great, thanks a lot!


Collect Keen Quotes Relevant To GET

Quotes can be added to most pages of the tournament.
These quotes should engender sobering reflections about humanity's future.
Some very relevant quotes pertaining to deep-time and technological progress and or risk are included in the book X-Risk by Thomas Moynihan.
Added to Backlog since non-critical.

This issue will also cover updating the description for the header image, which currently has the description, from Wikipedia:

Before the play begins, Kronos, the ruler of the pre-Olympian gods (the Titans), had been overthrown by an insurgency led by Zeus. In that revolt, Prometheus had sided with Zeus. As the new king, Zeus intended to destroy and replace humankind. Prometheus frustrated this plan, showing humans the use of fire, which Prometheus had stolen. Prometheus also taught humanity the arts. For these acts of defiance, Zeus intends to punish Prometheus by chaining him to a rock in the mountains of Scythia.


NATS Slow Consumer Mitigation

When NATS encountered a slow consumer it will drop the message, losing the report content. This has happened before extremely rarely but still have a huge potential to go wrong in the future, especially when we migrate to the k8s cluster

In my perspective when the producer is faster than the consumer, the buffer will eventually be filled fullly and the only choice is to drop messages. Anyway, just to start a single goroutine to receive messages from NATS and put them to a channel shall solve this. Other than that, we could create a thread pool like panjf2000/ants and then submit consumer tasks to it. This gives the ability to dynamically adjust goroutine count.
Not quite sure whether those work. Not familiar with NATS. :D

Yes. However the correct behavior is for NATS JetStream to store a reasonable amount of buffer when a slow-consumer is encountered, due to the fact we are not expecting those data to be temporal sequential (delivered in-order).

wontfix: NATS will not actually drop the message due to the fact we haven't ACKed it, so NATS will send us the "dropped" message just simply later than what we'd expected.


Unclear error if one of the parameters is missing

If instead of the correct command
./near-cli
    add contract-code
    network testnet
    account 1.cli2.testnet
    contract-file '~/projects/near/contract/res/contract.wasm'
    no-initialize
    sign-with-keychain

you run a command which misses a parameter, for example:
./near-cli
    add contract-code
    account 1.cli2.testnet
    contract-file '~/projects/near/contract/res/contract.wasm'
    no-initialize
    sign-with-keychain

or
./near-cli
    add contract-code
    network testnet
    contract-file '~/projects/near/contract/res/contract.wasm'
    no-initialize
    sign-with-keychain

The error is shown:
Error:
   0: add command or near-cli-add extension does not exist

Location:
   src/common.rs:1221

It is quite unclear and doesn't give any information about what parameters are missing.

Yeah, it is a deficiency of the extensions catching code. We should somehow check if the error stems from finding the top-level command and only if that is the case, search for an extension and otherwise print the original error.

FYI, @FroVolod is currently working on it


MAL Library not loading

The MAL list in library is not loading for firestick tv app.

Send your username please.

Hi, my user name is smitten85
On Thu, Feb 3, 2022, 12:32 AM deceptions @.***> wrote:

Send your username please.
—
Reply to this email directly, view it on GitHub
https://github.com/deceptions/no/issues/117#issuecomment-1028267291, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AM5TRZ7NFKZQKQBPO7ILMMTUZF5T5ANCNFSM5NED3RSA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Even after update the library is not loading . Also the MAL list is not synched either . The episodes watched are not getting updated as well

It's not updating episode progress it's telling error updating progress pls help

Try re-logging @ToxicKakashi

Try re-logging @ToxicKakashi

Thanks bro it worked for me

Tried re-logging didn't work for me.. please help

Weird it works for me using the stalk feature :thinking:

I tried that... It doesn't work with stalk either 😣


TCP connection timeout

Environment

VerneMQ Version:
OS: ubuntu 18.04
Erlang/OTP version (if building from source):

My MQTT device will send the MQTT Connect Command to the Broker after 7 to 10 seconds of successful TCP connection because of the system limitation. But the Broker seems to have opened the connection before I have done this. How do I extend this timeout time?

Hi, thank you for opening the issue. If I understand it correctly you're running into the same issue as #735 which was only partially resolved and the PR therefore wasn't merged. Are you using TLS as well?

Would you be able to try out the code in https://github.com/erlio/vernemq/pull/736 and see if that solves your problem?

Thankes this work!!
My problem is not from TSL
Just a small bug in the firmware.
then I just need to replace usr/lib/vernemq/lib/zmq_server-1.5.0/ebin/vmq_mqtt_fsm.beam  is it ok?

@dergraf do you think we should merge #736 even though it doesn't solve the issue for tls for the original issue #735?
@XiaoKaiRen I think that might work - but no guarantees - and I wouldn't recommend it as a long term solution ;)


Bug: CollaborationPlugin not working with minimal code example

Lexical version:0.2.9
browser: chrome lasted version
computer: mac
Steps To Reproduce

yarn create vite
copy the example code from https://lexical.dev/docs/collaboration/react to src/App.tsx
add dependencies then run 'yarn install' and 'yarn dev'
start a websocket server by running 'PORT=1234 npx y-websocket-server'
open two tabs in browser with link 'http://localhost:3000/' and editing on one tab

Link to code example:
https://github.com/jullite/hello-lexical

The current behavior
content of editor not sync between two tabs
The expected behavior
content of editor will sync between two tabs

Playground worked fine but I do need to use it outside, I do have tired copy the playground code to my next.js framework, but I get wrong with "should never happen" message on one of  collaboration tab console when I edit on another tab. I guess it maybe caused by the runtime environment, so I start a new vite repo to reproduce it and get this result.

I have updated code to lexical playground version(only RichTextPlugin, CollaborationPlugin and WebsocketProvider), and still don't work, did I missed something?

Hey @jullite. Were you able to resolve this?

Hey @jullite. Were you able to resolve this?

sorry, I'm quite not familiar with this codebase.

Have you made sure you're handling bootstrapping properly? I.e. the <RichTextPlugin> or <PlainTextPlugin> has null for initialEditorState? Also you'll need to make sure you are wrapping your app in the collaboration context, so it can access the docMap, and also ensure that you're not using the 'HistoryPlugin with collaboration.

All you mentioned above have been put in the right place except the collaboration context, is the SharedHistoryContext on playground?

Hello! I'm struggling with something similar myself.
I'm able to get the playground running locally with collaboration on  🎉
Local Playground

But when I try to get the same playground code to run outside of the lexical codebase, collaboration doesn't work.
I get the generic Should never happen error 😭
Note: Getting the playground to at least load and work outside of the lexical repo requires a lot of changes, you have to transform all of the imports from named imports to default imports.
Standalone Playground

I'm still debugging this ,  it seems that it fails because getOrInitCollabNodeFromSharedType is returning undefined at some point.
Hoping someone else has gotten this to work? @jullite @hustlefueled  maybe?
@trueadm Any idea why I see this error or how to fix it?
Thank you!

@iamzapata Are you ensuring that the RichTextPlugin is passing in null for initialEditorState when it is in collab?

@trueadm So I have the same code from packages/lexical-playground:
 <RichTextPlugin
  contentEditable={<ContentEditable />}
  placeholder={placeholder}
  initialEditorState={
    isCollab ? null : emptyEditor ? undefined : prepopulatedRichText
  }
/>

But even setting the intialEditorState to null, the app breaks with a different error.
I'm going to keep trying, but I feel the playground should be decoupled from the packages and work outside of it.
Thank you for lexical though, I'm really excited about it.

The playground isn’t doing anything special. Make sure you add the collaboration context too for the doc map.

I could make collaboration edit  with npm run preview(vite preview).
what I did was

transplant vite.config and  package.json from playground
transplant babel.config.js , tsconfig.json and tsconfig.build.json from lexical

But, i still fail and struggling with error when I run npm run dev(vite).
I also removed all other plugins and nodes
I think this error at console is only difference from when I run playground repo.

Yjs was already imported. Importing different versions of Yjs often leads to issues.

And I guess the key is build options, but I still trying to figure it out.
Maybe I should do same thing like that(but my repo is not next, just react).
https://github.com/yjs/yjs/issues/410#issuecomment-1127478919
code here:
https://github.com/fomachanyade/react-lexical/tree/main/lexical_react/lexical_react_ts

I still haven't been able to make collaboration work locally. I continue getting the "error while handling a Yjs update error: should never happen" error
Everything but the build setup is identical to the playground, I'm using vite though.
I extracted the playground from the lexical, can be found here: https://github.com/iamzapata/lexical-test

@trueadm Hi,
can you please check the link again.
And related to your question:

Did you resolve the issue of having multiple Yjs loaded?

I do see this warning you're mentioning:

Yjs was already imported. Importing different versions of Yjs often leads to issues.

y-websocket.js:386 WebSocket connection to 'ws://localhost:1212/playground/0/main' failed: WebSocket is closed before the connection is established.

I can open two windows, turn on collaboration on both.
Then I will type something in one window and right away, in the other window, I get this error:

Caught error while handling a Yjs update Error: Should never happen
at syncEvent

I think this seems like an issue with Vite where it's unable to handle a CJS and an ESM import of the same package. I guess this will be resolved in the future when Lexical also supports ESM, but that's quite complex to support right now (as we have DEV and PROD variants, which I'm unsure how would work in an ESM world).

@jullite @iamzapata my mate solved the vite build problem.
just added an alias for yjs and debugging collaboration worked.
vite.config.js
// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  resolve: {
    alias: {
      yjs: path.resolve("./node_modules/yjs/src/index.js"),
    },
  },
});

please try this.

@fomachanyade I confirm making this change makes the collaboration work locally. Thank you! =)

@jullite @iamzapata my mate solved the vite build problem. just added an alias for yjs and debugging collaboration worked.
vite.config.js
// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  resolve: {
    alias: {
      yjs: path.resolve("./node_modules/yjs/src/index.js"),
    },
  },
});

please try this.

Is this the only thing we need to do to get the collaboration working on a separate project? I was not able to make the collaboration work by adding this to my vite config file.

@jullite @iamzapata my mate solved the vite build problem. just added an alias for yjs and debugging collaboration worked.
vite.config.js
// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  resolve: {
    alias: {
      yjs: path.resolve("./node_modules/yjs/src/index.js"),
    },
  },
});

please try this.

Is this the only thing we need to do to get the collaboration working on a separate project? I was not able to make the collaboration work by adding this to my vite config file.

Hi @ebads67 I think so?
Check this repo out and let me know: https://github.com/iamzapata/lexical-collab/settings

Hey @ebads67 were you able to test collaboration and sync data back to your backend server?
I've tested yjs connection and it works but it outputs the binary message when I log what it's sending to the server.

Yes I did. I'd suggest checking the repo mentioned above.

Too many repos mentioned above. Would be kind to share the link again. Sorry for the trouble.
Sent via Superhuman ( @.*** )
On Fri, Jun 24, 2022 at 15:38:12, Ebad < @.*** > wrote:

Hey @ ebads67 ( https://github.com/ebads67 ) were you able to test
collaboration and sync data back to your backend server?
I've tested yjs connection and it works but it outputs the binary message
when I log what it's sending to the server.

Yes I did. I'd suggest checking the repo mentioned above.
—
Reply to this email directly, view it on GitHub (
https://github.com/facebook/lexical/issues/2153#issuecomment-1165420271 ) ,
or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AVDFMEHVHVCQXSALVX2JN2DVQWCIZANCNFSM5VXWKW7Q
).
You are receiving this because you were mentioned. Message ID: <facebook/lexical/issues/2153/1165420271
@ github. com>

Too many repos mentioned above. Would be kind to share the link again. Sorry for the trouble. Sent via Superhuman ( @.*** )
…
On Fri, Jun 24, 2022 at 15:38:12, Ebad < @.*** > wrote: > > > Hey @ ebads67 ( https://github.com/ebads67 ) were you able to test > collaboration and sync data back to your backend server? > > > > I've tested yjs connection and it works but it outputs the binary message > when I log what it's sending to the server. > > Yes I did. I'd suggest checking the repo mentioned above. — Reply to this email directly, view it on GitHub ( #2153 (comment) ) , or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AVDFMEHVHVCQXSALVX2JN2DVQWCIZANCNFSM5VXWKW7Q ). You are receiving this because you were mentioned. Message ID: <facebook/lexical/issues/2153/1165420271 @ github. com>

The one mentioned by @iamzapata. https://github.com/iamzapata/lexical-test

Thank you. 🙏
Sent via Superhuman ( @.*** )
On Fri, Jun 24, 2022 at 15:45:35, Ebad < @.*** > wrote:

Too many repos mentioned above. Would be kind to share the link again.
Sorry for the trouble. Sent via Superhuman ( @.*** )
… ( # )
On Fri, Jun 24, 2022 at 15:38:12, Ebad < @.*** > wrote: > > > Hey @
ebads67 ( https:/ / github. com/ ebads67 ( https://github.com/ebads67 ) )
were you able to test > collaboration and sync data back to your backend
server? > > > > I've tested yjs connection and it works but it outputs the
binary message > when I log what it's sending to the server. > > Yes I
did. I'd suggest checking the repo mentioned above. — Reply to this email
directly, view it on GitHub ( #2153 (comment) (
https://github.com/facebook/lexical/issues/2153#issuecomment-1165420271 ) )
, or unsubscribe ( https:/ / github. com/ notifications/ unsubscribe-auth/
AVDFMEHVHVCQXSALVX2JN2DVQWCIZANCNFSM5VXWKW7Q (
https://github.com/notifications/unsubscribe-auth/AVDFMEHVHVCQXSALVX2JN2DVQWCIZANCNFSM5VXWKW7Q
) ). You are receiving this because you were mentioned. Message ID: < / issues/
2153 ( https://github.com/facebook/lexical/issues/2153 ) /1165420271 @
github. com>

The one mentioned by @ iamzapata ( https://github.com/iamzapata ). https:/
/ github. com/ iamzapata/ lexical-test (
https://github.com/iamzapata/lexical-test )
—
Reply to this email directly, view it on GitHub (
https://github.com/facebook/lexical/issues/2153#issuecomment-1165426498 ) ,
or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AVDFMEGO63L7I64GFF2TDD3VQWDEPANCNFSM5VXWKW7Q
).
You are receiving this because you were mentioned. Message ID: <facebook/lexical/issues/2153/1165426498
@ github. com>

The fix worked for me. the initial error I was hitting was https://github.com/yjs/yjs/issues/438 Yjs was already imported. This breaks constructor checks and will lead to issues!.  @dmonad says If you see this message, make sure that you only import one version of Yjs.. However my project had a single yjs version.
It would still be useful to understand why the playground does not need that config https://github.com/facebook/lexical/blob/5d0a07a4c9fbd4d33832c824f68a7ec16e47d5f6/packages/lexical-playground/vite.config.js and why it is needed when the collab feature is used in a separated project.

@echarles Sometimes there are nested yjs packages installed. Potentially, there can be nested yjs installations in node_modules: e.g. node_modules & node_modules/@lexical/yjs/node_modules/yjs).
Another reason for the error message is that some complex build system import both the commonjs (.cjs) and the module (.mjs) version of Yjs.
You can resolve both issues by specifying explicitly which version you want to use. In webpack and other bundlers, you can set an alias: yjs: "node_modules/yjs/dist/yjs.mjs".

@echarles Sometimes there are nested yjs packages installed. Potentially, there can be nested yjs installations in node_modules: e.g. node_modules & node_modules/@lexical/yjs/node_modules/yjs).

Yeah, absolutely, I have learned that some time ago for other libraries, like e.g. React which is also sensible to mixed versions, and have a few tips to overcome that: you can specify "resolutions" package.json, if this does not work, I have a sanity bash script that manually removes mismatched packages.
In the local env case I am referring in this issue, I have double checked with a find . -name yjs to ensure a single package was present in the node_module tree.

Another reason for the error message is that some complex build system import both the commonjs (.cjs) and the module (.mjs) version of Yjs.

That  could be indeed the root cause. I don't know how to check.

You can resolve both issues by specifying explicitly which version you want to use. In webpack and other bundlers, you can set an alias: yjs: "node_modules/yjs/dist/yjs.mjs".

Yes, this is the workaround documented in this issue and it works. I found it a bit fragile, especially when you have a monorepo managed with tools like lerna, and also when that monorepo is onboarded in yet another complex other monrepo.
You don't have guarantee at which level of your tree the single yjs package will end-up.

Have you made sure you're handling bootstrapping properly? I.e. the <RichTextPlugin> or <PlainTextPlugin> has null for initialEditorState?

@trueadm is this a hard requirement for collaboration in Lexical? Is there any way to have an initial state?

@knpwrs Yes. As the initial state comes from the Y.Doc for consistency reasons.

hey have any of you managed to configure collab in nextjs?
Here I have a minimal example working without NextJS: https://codesandbox.io/s/lexical-collaboration-demo-forked-0gg0b1
Here's a minimal example with NextJS that doesn't work, even though I modified next.config.mjs, used dynamic import, and imported yjs as const Y = require("yjs");
https://codesandbox.io/p/sandbox/wild-wood-mphgyl
Is there something I'm doing wrong?

@fomachanyade I can't thank you and your mate enough for this. The alias suggestion in the vite config resolved the error of duplicate import.
I have wasted several hours today trying to work this out. I hope that lexical exposes ES6 exports to avoid Vite users to go through this..

@jullite @iamzapata my mate solved the vite build problem. just added an alias for yjs and debugging collaboration worked.
vite.config.js
// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  resolve: {
    alias: {
      yjs: path.resolve("./node_modules/yjs/src/index.js"),
    },
  },
});

please try this.

@fomachanyade I can't thank you and your mate enough for this. The alias suggestion in the vite config resolved the error of duplicate import.
I have wasted several hours today trying to work this out. I hope that lexical exposes ES6 exports to avoid Vite users to go through this..

@jullite @iamzapata my mate solved the vite build problem. just added an alias for yjs and debugging collaboration worked.
vite.config.js
// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  resolve: {
    alias: {
      yjs: path.resolve("./node_modules/yjs/src/index.js"),
    },
  },
});

please try this.

The right answer, thanks.

Guys i have an problem, i use Electron + Vite and i try to add alias but it gave me the same error: y-websocket.js?v=99465377:720 WebSocket connection to 'ws://localhost:8000/playground/0/658c4756f67c212fec0205e2' failed: WebSocket is closed before the connection is established. , here is my electron.vite.config.ts
import { resolve } from 'path'
import { defineConfig, externalizeDepsPlugin } from 'electron-vite'
import react from '@vitejs/plugin-react'

export default defineConfig({
  main: {
    plugins: [externalizeDepsPlugin()]
  },
  preload: {
    plugins: [externalizeDepsPlugin()],
  },
  renderer: {
    resolve: {
      alias: {
        yjs: resolve("node_modules/yjs/src/index.js"),
        '@renderer': resolve('src/renderer/src')
      }
    },
    plugins: [react()]
  }
})

@fomachanyade I can't thank you and your mate enough for this. The alias suggestion in the vite config resolved the error of duplicate import.
I have wasted several hours today trying to work this out. I hope that lexical exposes ES6 exports to avoid Vite users to go through this..

@jullite @iamzapata my mate solved the vite build problem. just added an alias for yjs and debugging collaboration worked.
vite.config.js
// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  resolve: {
    alias: {
      yjs: path.resolve("./node_modules/yjs/src/index.js"),
    },
  },
});

please try this.

Guys i have an problem, i use Electron + Vite and i try to add alias but it gave me the same error: y-websocket.js?v=99465377:720 WebSocket connection to 'ws://localhost:8000/playground/0/658c4756f67c212fec0205e2' failed: WebSocket is closed before the connection is established. , here is my electron.vite.config.ts
import { resolve } from 'path'
import { defineConfig, externalizeDepsPlugin } from 'electron-vite'
import react from '@vitejs/plugin-react'

export default defineConfig({
  main: {
    plugins: [externalizeDepsPlugin()]
  },
  preload: {
    plugins: [externalizeDepsPlugin()],
  },
  renderer: {
    resolve: {
      alias: {
        yjs: resolve("node_modules/yjs/src/index.js"),
        '@renderer': resolve('src/renderer/src')
      }
    },
    plugins: [react()]
  }
})


Security Issue: DOM XSS in reverse shell generator

Hi Team,
I have noticed a security issue in the reverse shell generator.
Issue Description:
An attacker can trigger the XSS vulnerability is the victim machine using the below payload
https://www.revshells.com/?#ip=%3Cimg%20src=x%20onerror=alert(document.domain)%20/%3E
https://www.revshells.com/?#ip=%3Cimg%20src=x%20onerror=alert(document.domain)%20/%3E
Ref: https://portswigger.net/web-security/cross-site-scripting/dom-based
Remediation:
Do not trust the user input. HTML escape the user input before rendering in the DOM.
Thanks,
SRK.

I appreciate the finding, and great job! You’re welcome to fix it, if you want to contribute. There’s nothing on RevShells to steal, so I can’t foresee XSS being a problem.


error in func bytes_to_df

there is a typo in the function when trying to import csv files.
instead of pd.read_read it should be pd.read_csv

This is now fixed. Thanks for the heads up.


Missing information on package resources

Hi, above it is mentioned that there are "package" resources but I cannot find any documentation about it. Can you fix that?
Thank you

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

ID: ee4ec9d0-e0d5-4fb4-7c3e-b84abfa290c2
Version Independent ID: 3e2b80d9-30e5-0c48-49f0-4fcdfedf5eee
Content: Resources - Azure Pipelines
Content Source: docs/pipelines/process/resources.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @juliakm
Microsoft Alias: jukullam

@MTomBosch  Thank you for the feedback.
Please refer to the issue https://github.com/MicrosoftDocs/azure-devops-docs/issues/7861 for further updates on the status of this.
Closing this issue now.


tax round4 (#297)

Update US19JanTaxR1.md

Docs Build status updates of commit ede74db:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-gp/payroll/US19JanTaxR1.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


New version: RestrictedBoltzmannMachines v0.2.3

Registering package: RestrictedBoltzmannMachines
Repository: https://github.com/RBMpro/RestrictedBoltzmannMachines.jl
Created by: @cossio
Version: v0.2.3
Commit: 0af3d19ee6b482f919cee27b34932e56ab6075ab
Reviewed by: @cossio
Reference: https://github.com/RBMpro/RestrictedBoltzmannMachines.jl/commit/0af3d19ee6b482f919cee27b34932e56ab6075ab#commitcomment-41973439

Please close this, in favor of https://github.com/JuliaRegistries/General/pull/20697.


[C++] misaligned-pointer-use after clang-18 upgrade

Describe the bug, including details regarding any error messages, version, and platform.
After upgrading to clang 18 we are getting a misaligned-pointer-use ubsan error firing when reading parquet table.
Tried with both arrow 16 and 17 releases.
/v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/arrow/util/ubsan.h:66:21: runtime error: load of misaligned address 0x7f0787c2d3c2 for type 'const unsigned int *', which requires 4 byte alignment
--
  | 0x7f0787c2d3c2: note: pointer points here
  | a5 bd  06 0b 40 20 0c 44 61 1c  48 a2 2c 4c e3 3c 50 24  4d 54 65 5d 58 a6 6d 5c  e7 7d 60 28 8e 24
  | ^
  | SUMMARY: UndefinedBehaviorSanitizer: misaligned-pointer-use /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/arrow/util/ubsan.h:66:21

  | [Backtrace #8]
  | __sanitizer::Abort() at /llvm/3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff/src/compiler-rt/lib/sanitizer_common/sanitizer_posix_libcdep.cpp:143
  |
  |
  | [Backtrace #9]
  | __sanitizer::Die() at /llvm/3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff/src/compiler-rt/lib/sanitizer_common/sanitizer_termination.cpp:58
  |
  |
  | [Backtrace #10]
  | __ubsan::ScopedReport::~ScopedReport() at /llvm/3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff/src/compiler-rt/lib/ubsan/ubsan_diag.cpp:402
  |
  |
  | [Backtrace #11]
  | handleTypeMismatchImpl(__ubsan::TypeMismatchData*, unsigned long, __ubsan::ReportOptions) at /llvm/3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff/src/compiler-rt/lib/ubsan/ubsan_handlers.cpp:137
  |
  |
  | [Backtrace #12]
  | __ubsan_handle_type_mismatch_v1 at /llvm/3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff/src/compiler-rt/lib/ubsan/ubsan_handlers.cpp:142
  |
  |
  | [Backtrace #13]
  | int arrow::internal::unpack32_specialized<arrow::internal::(anonymous namespace)::UnpackBits512<(arrow::internal::DispatchLevel)3> >(unsigned int const*, unsigned int*, int, int) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/arrow/util/ubsan.h:66
  |
  |
  | [Backtrace #14]
  | int arrow::bit_util::BitReader::GetBatch<int>(int, int*, int) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/arrow/util/bit_stream_utils.h:342
  |
  |
  | [Backtrace #15]
  | int arrow::util::RleDecoder::GetBatchWithDict<long>(long const*, int, long*, int) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/arrow/util/rle_encoding.h:580
  |
  |
  | [Backtrace #16]
  | parquet::(anonymous namespace)::DictDecoderImpl<parquet::PhysicalType<(parquet::Type::type)2> >::Decode(long*, int) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/parquet/encoding.cc:1634
  |
  |
  | [Backtrace #17]
  | parquet::internal::(anonymous namespace)::TypedRecordReader<parquet::PhysicalType<(parquet::Type::type)2> >::ReadValuesDense(long) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/parquet/column_reader.cc:1824
  |
  |
  | [Backtrace #18]
  | parquet::internal::(anonymous namespace)::TypedRecordReader<parquet::PhysicalType<(parquet::Type::type)2> >::ReadRecordData(long) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/parquet/column_reader.cc:1879
  |
  |
  | [Backtrace #19]
  | parquet::internal::(anonymous namespace)::TypedRecordReader<parquet::PhysicalType<(parquet::Type::type)2> >::ReadRecords(long) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/parquet/column_reader.cc:1425
  |
  |
  | [Backtrace #20]
  | parquet::arrow::(anonymous namespace)::LeafReader::LoadBatch(long) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/parquet/arrow/reader.cc:482
  |
  |
  | [Backtrace #21]
  | parquet::arrow::ColumnReaderImpl::NextBatch(long, std::__1::shared_ptr<arrow::ChunkedArray>*) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/parquet/arrow/reader.cc:109
  |
  |
  | [Backtrace #22]
  | parquet::arrow::(anonymous namespace)::FileReaderImpl::ReadColumn(int, std::__1::vector<int, std::__1::allocator<int> > const&, parquet::arrow::ColumnReader*, std::__1::shared_ptr<arrow::ChunkedArray>*) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/parquet/arrow/reader.cc:284
  |
  |
  | [Backtrace #23]
  | parquet::arrow::(anonymous namespace)::FileReaderImpl::DecodeRowGroups(std::__1::shared_ptr<parquet::arrow::(anonymous namespace)::FileReaderImpl>, std::__1::vector<int, std::__1::allocator<int> > const&, std::__1::vector<int, std::__1::allocator<int> > const&, arrow::internal::Executor*)::$_0::operator()(unsigned long, std::__1::shared_ptr<parquet::arrow::ColumnReaderImpl>) const at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/parquet/arrow/reader.cc:1252
  |
  |
  | [Backtrace #24]
  | parquet::arrow::(anonymous namespace)::FileReaderImpl::DecodeRowGroups(std::__1::shared_ptr<parquet::arrow::(anonymous namespace)::FileReaderImpl>, std::__1::vector<int, std::__1::allocator<int> > const&, std::__1::vector<int, std::__1::allocator<int> > const&, arrow::internal::Executor*) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/arrow/util/parallel.h:95
  |
  |
  | [Backtrace #25]
  | parquet::arrow::(anonymous namespace)::FileReaderImpl::ReadRowGroups(std::__1::vector<int, std::__1::allocator<int> > const&, std::__1::vector<int, std::__1::allocator<int> > const&, std::__1::shared_ptr<arrow::Table>*) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/parquet/arrow/reader.cc:1231
  |
  |
  | [Backtrace #26]
  | parquet::arrow::(anonymous namespace)::FileReaderImpl::ReadTable(std::__1::vector<int, std::__1::allocator<int> > const&, std::__1::shared_ptr<arrow::Table>*) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/parquet/arrow/reader.cc:199
  |
  |
  | [Backtrace #27]
  | parquet::arrow::(anonymous namespace)::FileReaderImpl::ReadTable(std::__1::shared_ptr<arrow::Table>*) at /v/build/v_deps_build/arrow-prefix/src/arrow/cpp/src/parquet/arrow/reader.cc:300

Component(s)
C++

So, the irony is that this is happening in a piece of code that is precisely meant to avoid UB issues:
https://github.com/apache/arrow/blob/dcc1ee5b1d4851870724ab5e4cf475bcac007b56/cpp/src/arrow/util/ubsan.h#L63-L68
@felipecrv

This seems to be https://github.com/llvm/llvm-project/pull/67766
Can you try the following diff @dotnwat ?
diff --git a/cpp/src/arrow/util/ubsan.h b/cpp/src/arrow/util/ubsan.h
index 900d8011df..ab91e88556 100644
--- a/cpp/src/arrow/util/ubsan.h
+++ b/cpp/src/arrow/util/ubsan.h
@@ -63,7 +63,7 @@ inline std::enable_if_t<std::is_trivially_copyable_v<T>, T> SafeLoadAs(
 template <typename T>
 inline std::enable_if_t<std::is_trivially_copyable_v<T>, T> SafeLoad(const T* unaligned) {
   std::remove_const_t<T> ret;
-  std::memcpy(&ret, unaligned, sizeof(T));
+  std::memcpy(&ret, reinterpret_cast<const void*>(unaligned), sizeof(T));
   return ret;
 }

@@ -73,7 +73,7 @@ inline std::enable_if_t<std::is_trivially_copyable_v<T> &&
                         U>
 SafeCopy(T value) {
   std::remove_const_t<U> ret;
-  std::memcpy(&ret, &value, sizeof(T));
+  std::memcpy(&ret, reinterpret_cast<const void*>(&value), sizeof(T));
   return ret;
 }

So, the irony is that this is happening in a piece of code that is precisely meant to avoid UB issues

AFAIU, using memcpy like this was the recommended way of avoiding UB. My guess here is that UBSAN is complaining about code that was already blessed by the x86 backend when it selected the instructions.

Judging by https://github.com/llvm/llvm-project/pull/67766#issuecomment-1754440801 , we are lacking a cast to void* or char* so as to drop the alignment requirement.
I find this utterly weird, since the memcpy signature only involves void* pointers, but apparently that implicit cast is not enough to appease clang-18.

@dotnwat Ping. Could you try the diff in https://github.com/apache/arrow/issues/44372#issuecomment-2406899429 above?

@pitrou sorry about the delay. yes, that patch works for us. tested in apache-arrow-16.1.0 tag.

Issue resolved by pull request 44468
https://github.com/apache/arrow/pull/44468


Fix compilation of Fortuna with gcc

Only Fortuna.cpp and Fortuna.h are changed. At least GNUmakefile needs to be modified to compile the entire project with gcc.

Thanks for the changes to the Fortuna files.
Oops, I just noticed I choosed the wrong abstraction layer for the AutoSeededFortuna Singleton.


deleted displaying Decision Comment when adding a risk + added verifications to avoid referring to undefined risk id

A function was executed at the wrong time so implied an error and was in fact useless + added condition to addSelectedRowData to fix issues when deleting risks could not find the risk related to a given id

To reproduce the issue:

Launch sratool
Go to Risks tab. The tab will have one risk by default. Scroll to the Risk Mitigation...

Now add a new Risk. The active risk is #1.

Scroll to the Risk Mitigation, notice that the mitigation decision is shown even when the decision = Not defined

@ThomasDThales This pull requests fixes 2 issues. Can you update the pull request title to describe the pull request more accurately

@ThomasDThales This pull requests fixes 2 issues. Can you update the pull request title to describe the pull request more accurately

Done


Mohr/daemon

For EIVE, I need the ability to continuously receive TM and still be able to send TCs at wish.
Following adaptions were necessary:
Changes to the TmTcHandler :

added a cached SequentialCommandSenderReceiver
added CONTINUOUS mode which will start the receiver thread in the SequentialCommandSenderReceiver instance and only send one TC

Changes in runner.py:

added argument in __start_tmtc_commander_cli to defer sending of command
added two functions, init_and_start_daemons and performOperation, to allow separate calls to init TmTcHandler and send TCs

Changes in SequentialCommandSenderReceiver:

added send_queue_tc_and_return function which does only that (and no tm checking)
added possibility to start a thread which checks tm

Codecov Report

Merging #65 (186523e) into main (95336de) will decrease coverage by 0.34%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##             main      #65      +/-   ##
==========================================
- Coverage   40.93%   40.59%   -0.35%
==========================================
  Files          57       57
  Lines        3530     3582      +52
==========================================
+ Hits         1445     1454       +9
- Misses       2085     2128      +43

Flag
Coverage Δ

unittests
40.59% <20.00%> (-0.35%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/tmtccmd/core/backend.py
29.78% <5.26%> (-2.76%)
:arrow_down:

.../tmtccmd/sendreceive/sequential_sender_receiver.py
21.23% <20.00%> (-0.36%)
:arrow_down:

src/tmtccmd/runner.py
26.31% <33.33%> (+0.14%)
:arrow_up:

src/tmtccmd/config/definitions.py
90.19% <100.00%> (+0.09%)
:arrow_up:

src/tmtccmd/sendreceive/tm_listener.py
23.26% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


TSC Open Meeting, Thursday 28th February 2019

NOTE: This meeting is on Thursday at 9am - 10am PT, 5pm-6pm UTC
Zoom Meeting link: https://zoom.us/j/975841675
In order to give some more visibility into the topics we cover in the TSC meetings here is the planned agenda for the next meeting.  Hopefully this will allow people to plan to attend meetings for topics that they have an interest in.  And for folks who cannot attend they can comment on this issue prior to the meeting.  Feel free to suggest other potential agenda topics.
Proposed Agenda

Topic
Owner
Decision/NextStep

Continue discussion of Overlays and Traits #1843 #1722 #445 #613
@darrelmiller / @webron / @mkistler / @MikeRalphson

/cc @OAI/tsc Please add other items as you see fit

I propose merging https://github.com/OAI/OpenAPI-Specification/pull/1779 as it should be straightforward now.

Meeting Recording:
https://zoom.us/recording/share/zE4RsZ6TM3OQk_jxPu14D55fHiRvzkY-LkvCIpLAMmSwIumekTziMw


Log sidecar pod name in Dapr Operator

At present it is impossible to tell which sidecar the operator has updated.
{"instance":"dapr-operator-6d9ffb6bd8-86bg7","level":"info","msg":"updated sidecar with component {name} (state.mongodb)","scope":"dapr.operator.api","time":"2021-11-25T12:30:03.650607344Z","type":"log","ver":"unknown"}
In what area(s)?
/area operator
Describe the feature
Add pod name to help identify sidecar
Release Note
Add sidecar pod name

Good suggestion

What version are you using?

What version are you using?

1.5.0

This feature depends on sidecar knowing the PodName to which it belongs.
We can obtain the PodName at injection time.

This feature depends on sidecar knowing the PodName to which it belongs. We can obtain the PodName at injection time.

Kubernetes calls the admission controller before the pod gets created, and at injection time it doesn't have a name yet. We can use the Kubernetes Downward API to inject the pod name, but we need to be mindful that many platforms supported by Virtual Kubelet don't honor the Downward API.

This feature depends on sidecar knowing the PodName to which it belongs. We can obtain the PodName at injection time.

Kubernetes calls the admission controller before the pod gets created, and at injection time it doesn't have a name yet. We can use the Kubernetes Downward API to inject the pod name, but we need to be mindful that many platforms supported by Virtual Kubelet don't honor the Downward API.

Yes, you warned me about Downward API in another PR. But if the platform not support Downward API well, the solution is going to be more complicated:

Watch Pod CREATE event to get POD_NAME;
Set POD_NAME to daprd;

/assign


Azure Monitor in pre-deployment gates runs forever with message "No samples have yet arrived"

Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Environment
AccountName: o365exchange.visualstudio.com
TeamProject: O365 Core/SubstrateDevX
Release pipeline Name: MetagraphCataloging-UtahAPI
Release number: 128

Agent - Hosted or Private:

Hosted agent. But issues in in the agentless phase i.e in predeployment stage.
Issue Description
I have configured monitoring an application insights alert in predeployment gate.
The pre-deployment gates runs forever with the message: "No samples have yet arrived, next sample in x min"
The logs do not give much information. The logs only has information about the agent phase of deployment. There are no instructions anywhere or support alias to help troubleshoot.

Error logs
[Insert error from the logs here]

@shkrishms , looks like the jobagent was stuck in the queued state and was not picking up any of the server tasks. I have restarted the jobagent and the issue should be fixed now. We are still investigating as to why this happened but you should be unblocked now. Please do confirm whether you are unblocked or not. Thanks for reporting the issue!

Closing this issue as the issue is fixed.

@Anumita could you restart the jobagent again? we are facing the same issue

@kpage-bentley,  I have checked the issue. I don't see jobs are stuck. Are you still facing the issue?

@vithati, tried one more time, same error

@kpage-bentley, Can you share the release link or Release pipeline Name and Release number details?

@vithati Emailed you the link...

@kpage-bentley, I looked at server logs,  it's not releated to jobs stuck issue. 'service connection' used in 'Scorecards gate' not present, either it deleted or not exist. Can you verify service conection once and try the release.  Presently UI not showing that error message. I have opened bug to show proper error messages in UI.


Support for multiple databases

It is on the plan the support for multiple databases?
We would love to help on that :)

Need to touch base about the whole base knowledge of the curriculum and the codes
Get Outlook for iOShttps://aka.ms/o0ukef

From: Iago Rodriguez Lopez<EMAIL_ADDRESS>Sent: Thursday, May 18, 2017 11:40:35 AM
To: mariusandra/insights
Cc: Subscribed
Subject: [mariusandra/insights] Support for multiple databases (#4)
It is on the plan the support for multiple databases?
We would love to help on that :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/mariusandra/insights/issues/4, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Abc5ocBM6tgNacYEi6jeunAIAPDlBhwhks5r7HSDgaJpZM4NfgSG.

Hey @asurancetturix , can you clarify what you mean? Any of these?

simultaneously connecting to multiple databases?
... without merging data from them into reports?
... and merging data from them into reports?
connecting to different database types?

What would you like help with?
Get Outlook for iOShttps://aka.ms/o0ukef

From: Iago Rodriguez Lopez<EMAIL_ADDRESS>Sent: Thursday, May 18, 2017 11:40:35 AM
To: mariusandra/insights
Cc: Subscribed
Subject: [mariusandra/insights] Support for multiple databases (#4)
It is on the plan the support for multiple databases?
We would love to help on that :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/mariusandra/insights/issues/4, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Abc5ocBM6tgNacYEi6jeunAIAPDlBhwhks5r7HSDgaJpZM4NfgSG.

Sure is
Get Outlook for iOShttps://aka.ms/o0ukef

From: Iago Rodriguez Lopez<EMAIL_ADDRESS>Sent: Thursday, May 18, 2017 11:40:35 AM
To: mariusandra/insights
Cc: Subscribed
Subject: [mariusandra/insights] Support for multiple databases (#4)
It is on the plan the support for multiple databases?
We would love to help on that :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/mariusandra/insights/issues/4, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Abc5ocBM6tgNacYEi6jeunAIAPDlBhwhks5r7HSDgaJpZM4NfgSG.

@jamesdean11 I'm not really sure what you're saying :). But for things to help with, there's a list in the README called "Coming soon". Feel free to work on anything from there... or just anything you think would make the product better.


Certain particles still use incorrect floats

Found to affect the following:

/particle particles
Particles from breaking armour stands
Particles from falling
Particles from damaging a mob
Particles from sweep attacks

i know about these; the issue is that i'd need to rewrite the particle packet to fix them, which isn't a very good thing to do when it comes to compatibility, lol

Particles from adding eyes to end portal frames also lose precision:

I've found a few more examples of particles losing precision; let me know if any of these seem reasonably fixable so I can open an issue for them.

Particles from activated conduits
Particles from end gateways
Particles from fishing (both splashes and moving fish thing)
Squid ink particles

end gateway particles should be fixed in fb5c0735fa34d5b624964f33f980966bccab0b77
another i've found: campfire particles

Conduit and end gateway particles will be fixed in the next vanilla prerelease

Almost all of them are fixed in pre4. All I can find that still exist are bone meal and eye of enderortal frame addition particles. They also fixed tnt and enchanting tables.

Since there's so few of them currently in the game now I'll probably close this ticket and create individual tickets here instead

Closing this ticket until a playable version for 1.15 or 1.16 comes out, so then I can report any cases I find individually. Having a bunch of random particle bugs in one issue just causes clutter.


Billboard sizeInMeters not accurate in Columbus View with WebMercatorProjection

I just noticed if you set a Billboard with sizeInMeters to true in Columbus View with WebMercatorProjection the size in meters is not accurate.
Bellow are screenshots from the sandcastle of AGIs parking lot where each space is about 6m x 3m. The image from the columbus view is almost 1m shorter.
Not sure if this is the expected behaviour with WebMercatorProjection?

Sandcastle example SCENE3D: https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/#c=rVNha9swEP0rwl/igCcn9Zp0qRsKWWGDboFt9JOhKPbZPipLRpKTpaP/fee4bZw2rDCqD+b09O7p6e68FoatETZg2AVTsGELsNhU/GaH+YN0t11o5QQqMIPheaIS1WVwUA4dguUiy/w/iWK0am0J04rNnqQWwjiKhIp4bnT1GQoDYP0P01N++mk6nQbs44iPorOzaBh0GiuUcqWFydjsUbVdWIkCSHbAebiLbdjdcHutC32r12Ck2PJaFYMu6SFRD+/tdzKJng2fjCdHHLP/sxywMGQZ5KKRbsYaRSEVPNtr2VJvSMqZBvrcPaHG3yCXeW7BEa/Xy+cHnfijgI2Gh1d12F4GtvBPkcinx1PK42d43EypDd63UyOXBgvslffLixO+uPr+6+rHcRkqkMP0tcjNAX5Egpg7rFc/ore9GLfG+0QC9qwNZq4k1uTNfpSARdkWKXq7dXgPX9U3cGBs18HDAfUCL7ZuK2He4ZdY1do41hjp0+Q4qGopqPrhqknvwPHU2jYtDp+S4gzXDLOLxHvxvyYeS6Wwlk7yRsqfZCTx5nFI/IM0qUWGqlh2A9lSyvH8ugM553FI29dZTmu5Eqan+Bc

Sandcastle example COLUMBUS_VIEW:
https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/#c=rVRhb9owEP0rJ74QpMyBZoWOUTSNIa0SjGms9EskZJIj8ebYke1AadX/PocUSFq0StP8IbKf3717vjtlQxVsGG5RwTUI3MIINctTsthjTjPcH0dSGMoEqqYLj6BDFDiVEfYP7PkBIaPZ5Hb6+Xa+XNyM71xIafZdyV8YGiZFv5rgDldTVCE1Up0YTgueWh8DEYjSE0FhmGGoCY0i5zEQYFcmNSvIcEw/osrYHRU+WSuZfsFYIWrnXe+SXH7o9XouvG+Ttn915bfcUmPFOF9JqiLoP6sWi6U0RivbJMTb77VXZlhOZCyXcoOK0x3JRNwsg54C8d/9drv+0fBFp3vGMfybZRc8DyJc05ybPuTCbm1Lo5OWTuTWShmVY5V7ImTsHvlsvdZooNbM44MunLYL7VY9VYmdZHCHfxXxHft4G/L8aZ03k0jFHoq55DPFYlYp79cXN2Q0/vZz/OO8jC2QYeFrkUUNPyNhmXusUj9LL3rRKYxXiRY4sbYsMolldd/sR4IsTooi+W+3jj3gjZiiQaXLDtYHtOE2BtrsOA5L/BNLM6kM5Io7dnIMphmntvreKg9/oyGh1kXYwDsEDSK2ARZdB40Xf4SgASGnWtubdc753BoJGsOBZ/m1MC5pxEQ8KweyoCSd4aQECSEDzx5fRxkp+YqqiuIf
Browser: Any
Operating System: Any

I was a bit confused at first because the Sandcastles don't zoom into the right billboard. Here's the two versions going to the billboard in the parking lot:
3D view
Columbus view
This may be related to https://github.com/AnalyticalGraphicsInc/cesium/issues/7985. @likangning93 do you know if this is expected? Would the billboard's size in meters be more or less off relative to the imagery depending on how close you are to the poles?

I don't think this is related to #7985, since that's a vector tiles thing. I think the problem is that the billboard is the correct size in meters, but 2D projections naturally distort distances and/or angles, especially when they cover very large areas. Web Mercator in particular attempts to preserve angles while allowing distances to become more distorted at latitudes further from the equator. In other words, the billboard is fine, it's the car in the imagery that isn't the right size anymore.

I'm not so sure its the car its the car imagery.
I'm using this function to determine how many meters there are per pixel to have a little scale at the bottom of the map.
function () {
	let width = this.viewer.scene.canvas.clientWidth,
		height = this.viewer.scene.canvas.clientHeight,
		left = this.viewer.scene.camera.pickEllipsoid(new Cartesian2(0, height / 2), Ellipsoid.WGS84),
		right = this.viewer.scene.camera.pickEllipsoid(new Cartesian2(width, height / 2), Ellipsoid.WGS84)

	if (!JSUtil.hasValue(left) || !JSUtil.hasValue(right) || (this.lastScalePosLeft === left && this.lastScalePosRight === right)) {
		return
	}

	this.lastScalePosLeft = left
	this.lastScalePosRight = right

	let d = Cesium.Cartesian3.distance(left, right)
	let nd = d / width

	return nd
}

This doesn't take the curvature of earth into account, but when it comes to a few meters it should be accurate enough.
Anyway, the line I drew based on the function above always seem to be accurate, and the billboard image was always too small when set to size in meters in CV & WebMercatorProjection.
I haven't tested it, but I think you are right that the billboard will be scaled correctly at the equator.


Error processing server response, Expecting value: line 1 column 1 (char 0)

We are having an issue detonating urls and file after upgrading Splunk SOAR from 5.3.1 to 5.3.3. We now receive the following error for all file and url detonations.
Error processing server response, Expecting value: line 1 column 1 (char 0)

First off, I'm really sorry for the late response.
We cannot reproduce the issue. Do you still get the error with the latest app version? If so, can you provide some logs?


Compose inside SwiftUI example

Change Chat example to use SwiftUI as the main view. And insert Compose inside.
Top NavigationView, bottom NavBar and TextField in SwiftUI elements.

When I use the SwiftUI-based text input, I don't think I can close it again without sending the message. Would it be complicated to write this up? (Tapping outside text field should close the software keyboard)

When I use the SwiftUI-based text input, I don't think I can close it again without sending the message. Would it be complicated to write this up? (Tapping outside text field should close the software keyboard)

Fixed


WSL-2 Ubuntu: [process exited with code 1] after exit

Windows Build Number
Microsoft Windows [Version 10.0.19043.1237]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.10.16
Distro Version
Ubuntu 20.04
Other Software
Windows terminal
Repro Steps
run exit
Expected Behavior
After exit to be able to open ubuntu again.
Actual Behavior
Windows terminal says [process exited with code 1]
Also if I launch ubuntu app it doesn't open.
Diagnostic Logs
No response

Yes I'm also facing the same issue


Leaderboard integration closes #130

Looks good!

It all works as expected and the code seems fine.

Looks solid.

This PR should be rebased to master in order to be mergable.

Rebased in https://github.com/MoodCat/MoodCat.me-Core/pull/145


Issue 336 migrate sohm

This pull request resolves issue 336.
Notes:

when a user has already migrated we don't show anything
when a user still needs to migrate we send them to the docs: https://docs.olympusdao.finance/using-the-website/migrate
Before this change when a user still needs to migrate we sent them to: /stake/migrate
I used an anchor tag in lieu of Link to send the user to an external url.

closing this pr since I committed off the wrong branch. Will create new PR


Find Illness command

Add Functionality - Finds patients with a certain illness.
Note:

Keywords are case-insensitive and may form part of the illness to work properly.
Tests are added.

actually can't we add this into the existing find command instead of creating another find-illness command
and i was thinking also the appointment-find command can also be merged into the find command

We can but each of them serve their own search function (and hence different predicates).  I felt will be good to decouple them for easier debugging and modification in the future.


Add ability to hide GSF apps in App store app

It would be useful to be able to hide GSF components so that I don't inadvertantly install them in my main profile.
This would be a large convenience for me and improve usability of the app store app.
I also have kids with GrapheneOS devices and it would be useful to be able to do this on their devices as they aren't yet able to fully understand why we don't have it loaded in their main profile.

This can be potentially handled by giving an option to make the filters persistent or not across app session

The UI has been greatly improved. I don't see a good reason to add a toggle for this.


Fixes several bugs

Fixes the following:
#1709, the popup now extends outside the window bounds, though only on 19h1 and higher.
#1707, listening to PreviewKeyDown fixes this issue.
#1706, removed extra tab stop on the control.
Partial fix to #1694. I copied directly from our template of TextBox instead of the style from the SDK (which caused some other updates too.) The control now has correct highlighting and the popup buttons have a border (image is from RS2):

Inline buttons still don't look great, though. Will address in a later fix.

In the photo provided in the PR description the flyout does not have rounded corners, is that another bug?

        StepValue(SmallChange());

If step value doesn't result in a change, should we still mark the event as handled? or should we let text block maybe handle the key since we didn't actually do anything.

Refers to: dev/NumberBox/NumberBox.cpp:380 in 929bd35. [](commit_id = 929bd3549254d7225c0b285dc13e20e485abab82, deletion_comment = False)

In the photo provided in the PR description the flyout does not have rounded corners, is that another bug?

Actually yes, the screenshot is from RS2 but since CornerRadius is on Grid since the beginning I can add it. :)

        StepValue(SmallChange());

If step value doesn't result in a change, should we still mark the event as handled? or should we let text block maybe handle the key since we didn't actually do anything.

Hmm, I'm not sure. I think it would be weird if someone else were getting the events only when we happened to be at min/max. So either always handle it or never do?

        StepValue(SmallChange());

If step value doesn't result in a change, should we still mark the event as handled? or should we let text block maybe handle the key since we didn't actually do anything.

Hmm, I'm not sure. I think it would be weird if someone else were getting the events only when we happened to be at min/max. So either always handle it or never do?

Sounds good


WIP: SwiftPM Extensible Build Tools proposal

This is a draft proposal for extensible build tools in SwiftPM.  It uses some ideas from a previous draft proposal and the discussion that followed, but it is not directly another version of that proposal.
Because extensibility is a broad topic and there are a wide variety of needs, this proposal takes the approach of:

Providing a way for packages to implement extensions and letting them define the capabilities of those extensions
Providing a way for packages to vend extensions to other packages (or choose to keep them as a private implementation detail of the package)
Providing an initial set of extension capabilities that is narrowly focused on source generation and analysis, which seems to be one of the most common needs today

This will hopefully focus the discussion and allow something useful to be put in place soon, while providing a path for defining additional extension capabilities in the future.  So besides the technical merits of the initially proposed capabilities, feedback and ideas about how this approach to extensions could scale to other kinds of capabilities would be very appreciated.
To keep the scope reasonably bounded, this proposal is deliberately not a reconsideration of the existing package manifest format or a proposal for large changes to SwiftPM's build system.  While all of those things are open to change, this proposal intentionally keeps the scope fairly narrow and implementable.

The target/product types have different method names:

.packageExtension in §Proposed solution.
.extension in §Detailed design.
.packageExtensionTarget in §Example 4: Custom Source Generator.


[ISSUE #1849] shenyu-admin a part of classes test code

Fixes #1849.

Codecov Report

Merging #1855 (bc1b01e) into master (1eb8d09) will increase coverage by 1.36%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##             master    #1855      +/-   ##
============================================
+ Coverage     66.06%   67.42%   +1.36%
- Complexity     2559     2637      +78
============================================
  Files           489      489
  Lines         10752    10973     +221
  Branches       1071     1076       +5
============================================
+ Hits           7103     7399     +296
+ Misses         3116     3012     -104
- Partials        533      562      +29

Impacted Files
Coverage Δ

...admin/listener/zookeeper/HttpServiceDiscovery.java
68.35% <50.00%> (+58.09%)
:arrow_up:

...pache/shenyu/admin/transfer/ConditionTransfer.java
53.65% <0.00%> (-46.35%)
:arrow_down:

.../apache/shenyu/admin/transfer/AppAuthTransfer.java
68.88% <0.00%> (-31.12%)
:arrow_down:

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
66.66% <0.00%> (-27.78%)
:arrow_down:

...enyu/client/tars/TarsServiceBeanPostProcessor.java
35.13% <0.00%> (-22.98%)
:arrow_down:

...apache/shenyu/admin/transfer/MetaDataTransfer.java
78.84% <0.00%> (-21.16%)
:arrow_down:

...g/apache/shenyu/admin/transfer/PluginTransfer.java
80.00% <0.00%> (-20.00%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
63.10% <0.00%> (-8.74%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
56.84% <0.00%> (-6.32%)
:arrow_down:

...henyu/plugin/httpclient/NettyHttpClientPlugin.java
57.14% <0.00%> (-2.05%)
:arrow_down:

... and 13 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 1eb8d09...bc1b01e. Read the comment docs.


Build issue: cython not recognized

Issue, in an isolated virtualenv with only numpy installed:
$ cython --version
Cython version 0.23.4
$ python setup.py build_ext -i
Traceback (most recent call last):
  File "setup.py", line 23, in <module>
    raise RuntimeError(msg)
RuntimeError: Cython must be installed when working with a development version of PyWavelets

Solution: bring back cythonize.py, which handled this kind of thing (and other corner cases).

this is a development-only issue, postponing till after 1.0

closing as a non-issue. The Cython dependency is now correctly declared in pyproject.toml.


Update magnolia to 0.14.1

Updates com.propensive:magnolia from 0.14.0 to 0.14.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.propensive", artifactId = "magnolia" } ]

labels: library-update, semver-patch

Codecov Report

Merging #60 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #60   +/-   ##
=======================================
  Coverage   88.30%   88.30%
=======================================
  Files          10       10
  Lines         248      248
  Branches        7        7
=======================================
  Hits          219      219
  Misses         29       29

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 86e7c12...5b9f381. Read the comment docs.


Can't implicitly compare i8 to 0

Describe the bug
A while loop with a condition that is a pointer gives the error cannot implicitly convert 'int *' to 'int'.
Expected behavior
The while loop should run while the pointer is not null.
Code

int main() {
        int *p;
        while (p);
}
<stdin>:3:17: error: cannot implicitly convert 'int *' to 'int'

The fix is to cast 0 to the type of the pointer instead of casting the pointer to int, but then we run into https://github.com/CraneStation/cranelift/issues/466:
 typedef unsigned long size_t;
    size_t strlen(char *str) {
        size_t len = 0;
        while (*str++) ++len;
        return len;
    }
thread 'main' panicked at 'should not have an error defining a function: Compilation(Verifier(VerifierErrors([VerifierError { location: inst14, message: "Branch must have an encoding" }])))', src/libcore/result.rs:1084:5

inst14 is icmp ne v8, v9, where v8 and v9 are i8.

I think inst14 is the brz instead. Counting starts at 0 and icmp is not a branch, while the message refers to a branch.

Could you please push a commit reproducing this problem?

@bjorn3 take a look at the pointer-cast branch

Ah you're right about the brz, didn't realize counting started at zero. So then the offending instruction is brz v10, ebb2, so this isn't related to i8 at all, v10 is a boolean.

In that case I can work around it by promoting v10 to an int. It would be nice to have encoding support for booleans though, I think that's vaguely https://github.com/CraneStation/cranelift/issues/922

@bjorn3 take a look at the pointer-cast branch

Thanks

t would be nice to have encoding support for booleans though

brz.b1 should work: https://github.com/CraneStation/cranelift/blob/01201b110d55142c80bc34c2832a3c8823c94e60/cranelift-codegen/meta/src/isa/x86/encodings.rs#L1359-L1360

You forgot to finalize the builder. This may result in some error (not this one though)
diff --git a/src/ir.rs b/src/ir.rs
index 39209fc..3342199 100644
--- a/src/ir.rs
+++ b/src/ir.rs
@@ -304,6 +304,8 @@ impl Compiler {
                 builder.ins().return_(&[]);
             }
         }
+        builder.seal_all_blocks();
+        builder.finalize();
         if self.debug {
             let mut clif = String::new();
             codegen::write_function(&mut clif, &func, &None.into()).unwrap();

When printing the clif ir after the verifier failed I see:
function u0:0(i64 [%7]) -> i64 [%0] system_v {
    ss0 = explicit_slot 8
    ss1 = explicit_slot 8

                                ebb0(v0: i64):
[165#808d]                          v1 = stack_addr.i64 ss0
[69#8089]                           store v0, v1
[27#b8]                             v2 = iconst.i64 0
[165#808d]                          v3 = stack_addr.i64 ss1
[69#8089]                           store v2, v3
[171#eb]                            jump ebb1

                                ebb1:
[165#808d]                          v4 = stack_addr.i64 ss0
[27#b8]                             v5 = iconst.i64 1
[88#808b]                           v6 = load.i64 v4
[23#8083]                           v7 = iadd_imm v6, 1
[69#8089]                           store v7, v4
[90#4b6]                            v17 = uload8.i32 v6
[224#00]                            v8 = ireduce.i8 v17
[33#30]                             v9 = iconst.i8 0
[223#4b6]                           v18 = uextend.i32 v8
[203#7083]                          v10 = icmp_imm ne v18, 0
[-]                                 brz v8, ebb2
[165#808d]                          v11 = stack_addr.i64 ss1
[27#b8]                             v12 = iconst.i64 1
[88#808b]                           v13 = load.i64 v11
[23#8083]                           v14 = iadd_imm v13, 1
[69#8089]                           store v14, v11
[171#eb]                            jump ebb1

                                ebb2:
[165#808d]                          v15 = stack_addr.i64 ss1
[88#808b]                           v16 = load.i64 v15
[170#c3]                            return v16
}

Somehow it shows brz v8, ebb2, instead of brz v10, ebb2.

How are you printing the IR? I've been calling it programmatically with codegen::write_function,  before verifying the function, your output looks different from mine.

I used println!("{}", ctx.func); after calling define_function, removing the .unwrap() to prevent a panic.
I also figured out the brz v8, ebb2 turning into brz v10, ebb2: it is an optimization. It causes an error as brz.i8 is not yet implemented.

ahhh so the IR I've been seeing is not the IR that's being codegen. That is good to know

Indeed, define_function first performs some optimizations and legalization (replacing one inst without encoding with a series of others which do have an encoding) in place. By printing after define_function you will see the compiled ir.

I also can't work around this because cranelift optimizes it to code it doesn't know how to generate :(
# this is the original IR
function u0:0() -> i32 system_v {
    ss0 = explicit_slot 1

ebb0:
    jump ebb1

ebb1:
    v0 = stack_addr.i64 ss0
    v1 = load.i8 v0
    v2 = iconst.i8 0
    v3 = icmp ne v1, v2
    v4 = bint.i32 v3
    brz v4, ebb2  # note that v4 is i32
    jump ebb1

ebb2:
    v5 = iconst.i32 0
    return v5
}

# after optimization
function u0:0() -> i32 [%0] system_v {
    ss0 = explicit_slot 1

                                ebb0:
[171#eb]                            jump ebb1

                                ebb1:
[165#808d]                          v0 = stack_addr.i64 ss0
[90#4b6]                            v6 = uload8.i32 v0
[224#00]                            v1 = ireduce.i8 v6
[33#30]                             v2 = iconst.i8 0
[223#4b6]                           v7 = uextend.i32 v1
[203#7083]                          v3 = icmp_imm ne v7, 0
[223#4b6]                           v4 = bint.i32 v3
[-]                                 brnz v1, ebb1  # v1 is i8
[171#eb]                            jump ebb2

                                ebb2:
[27#b8]                             v5 = iconst.i32 0
[170#c3]                            return v5
}

fatal: Compilation error: Verifier errors:
- inst6: Branch must have an encoding

This is fixed on master.


Bug: img & input are inline-block tags

Plz add a inline-block section. img & input are inline-block tags

Strictly speaking, there is no such thing as "inline-block tags", as well as there are no "inline tags" and "block tags" since HTML4/XHTML1 (where the "block and inline elements" concept came from) became outdated.
As of HTML5, there are elements with different content models and different default presentation. The latter can be changed via CSS, the former can't. There is "phrasing content", roughly corresponding to "inline elements" from HTML4, and "flow content", roughly corresponding to "inline and block elements" (all visually displayed elements). But their default presentation can be different (form controls usually behave as inline blocks, table elements have table-specific presentation rules, ruby element has its own layout model, etc.). The nesting rules are also more complicated than "inline contains inlines, block contains inlines or blocks" (e.g. the a element can contain blocks, but can't contain other interactive elements, lists can contain only list items, tr can contain only table cells, etc.). So, in my opinion, the old "inline"/"block" dichotomy shouldn't be applyed to HTML5 at all, it brings more confusion than clarity.
But even if we simply call the phrasing content "inline" and non-phrasing flow content "block" (which looks a huge oversimplification to me), some elements in the table seem to be categorized incorrectly. For example, select and ruby elements should be categorized as "inline" (they don't break text lines and can be contained in other phrasing elements), and dt element should be categorized the same way as dd and li elements (and definitely not as "inline").

Still, how can the dd element be 'inline' by any definition? Even in HTML4, although it was listed neither as inline nor as block, it had the flow content model (that includes block content), which is impossible for 'inline' elements. In HTML5, it also has the "Flow content" content model and is rendered by default as display:block.
So, in terms of inline-vs-block dichotomy (leaving aside its applicability to HTML5), it should be labelled as 'block', not 'iline' (or — even better — as none of them, just like the dt element currently is).


all-in-one: add edgemesh installation

Signed-off-by: llhuii<EMAIL_ADDRESS>

/hold
wait https://github.com/kubeedge/sedna/pull/255 to be merged to fix the E2e test checker.

Since the checker workflow yaml is still old, I try to close and reopen it to see the workflow whether update or not.
/close

Since the checker workflow yaml is still old, I try to close and reopen it to see the workflow whether update or not

Didn't work.
Need to merge and rebase on upstream/main(i.e. including #255).

/lgtm

/hold cancel
/approve