Change the size of the canvas dynamically based on screen resolution.

Hello,
Is it possible to adjust the size of the canvas based on screen resolution (something like viewport in html)?
When I run the application on my laptop, the canvas looks pretty normal. But when I try to use it on an ipad or mobile, the canvas looks enlarged and its not so convenient to use it. It would be really great if the canvas could adjust automatically to screens of different resolutions.

Hello @murtazabasu ,
Not yet possible and a dupe of #39 :) I'll have to get back to it sometime this month. Hope you don't mind if I close this in favor for the original one!
Have a nice day,
Fanilo


Conflict with Leaflet.heat (heatmap don't show up)

It resumes to a CSS problem.
If vue-material.css is loaded (regardless of loading order), Leaflet.heat simply won`t show up.
Any ideas?

It has something to do with canvas...
font-family:Roboto,Noto Sans,Noto,sans-serif}ul:not(.md-list)>li+li{margin-top:8px}audio,canvas,embed,iframe,img,object,svg,video{max-width:100%;
Removing that canvas reference, the error is gone.

Try override max-width for that element i thinks help, max-width:none!important

Solved! Thanks :)

I'm going to close this issue. If you feel that there's an actual change that needs to be made to vue material (better css scoping, probably), please open a separate issue.


add section that showcases projects using conventionalcommits

It would be good to showcase a few projects using conventional commits (yargs and istanbuljs are the ones I work on).

Done., would be great to have folks (@stevemao, @Tapppi, @jameswomack, etc) submit a few of their links to good example projects using the convention.

@bcoe will do


Update kafka-client to at-least 3.4.0 to remediate  CVE-2023-25194

zipkin is getting flagged in our security scans due to the presence of org.apache.kafka:kafka-clients which has CVE-2023-25194.
Is there any plan to upgrade kafka-clients to at least 3.4.0 to get around this?

Ping @jeqo
On Thu, 13 Apr 2023, 14:15 Debraj Manna, @.***> wrote:

zipkin is getting flagged in our security scans due to the presence of
org.apache.kafka:kafka-clients which has CVE-2023-25194
https://www.cve.org/CVERecord?id=CVE-2023-25194.
Is there any plan to upgrade kafka-clients to at least 3.4.0 to get around
this?
—
Reply to this email directly, view it on GitHub
https://github.com/openzipkin/zipkin/issues/3522, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYAQ342KB77TQ4RQSHZDXA7U6JANCNFSM6AAAAAAW47ZHDM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


advanced search fields: With the latest version I don't get any results

With the latest demo I don't get a result. I have to change the selection first.
To reproduce

Reload the page
search for term: "fields"
-> no results
I have to deactivate the "all" filter and select "title" "text" fields

I would expect, that "title" and "text" are preselected, similar to the TW default setting

Thank you Mario!
I confirm this is a bug! The issue is with default selection!

It is expected to use *all -[excluded] as default
and also show nothing if user uncheck the  *all -[excluded]

I address this in v0.7.0 will be pushed within an hour!

Fixed in v.0.7.0


AddDataAPIBuilder() doesn't support multiple configuration files.

The current syntax:
var builder = DistributedApplication.CreateBuilder(args);

// Add Data API Builder using dab-config.json
var dab = builder.AddDataAPIBuilder("dab")
    .WithReference(sqlDatabase)
    .WaitFor(sqlServer);

builder.Build().Run();

This does not make it clear how to include configuration files.
I suggest two important methods:

Method
Intent

WithConfigurationFile(string)
Mounts the file in the container

WithConfigurationFiles(string[])
Mounts multiple files in the container

var dab = builder.AddDataAPIBuilder("dab")
    .WithConfigurationFile("./dab-config.json") // new
    .WithReference(sqlDatabase)
    .WaitFor(sqlServer);

and
var dab = builder.AddDataAPIBuilder("dab")
    .WithConfigurationFiles("./dab-config.json", "./dab-config-2.json") // new
    .WithReference(sqlDatabase)
    .WaitFor(sqlServer);

This is important because:

Multiple data source support in DAB requires multiple configuration files.
Azure Cosmos DB support requires multiple configuration files (schema files).

Workaround:
I realize this can be done today with Mount() but this undermines the simplicity of the integration.
var dab = builder.AddDataAPIBuilder("dab")
    .WithReference(sqlDatabase)
    .WaitFor(sqlServer);

// configuration
var config = "path";
var internalPath = $"/App/{System.IO.Path.GetFileName(config)}"
dab.WithBindMount(config, internalPath)

and (multiple configuration files)
var dab = builder.AddDataAPIBuilder("dab")
    .WithReference(sqlDatabase)
    .WaitFor(sqlServer);

// configurations
var configs = new[] { "path", "path", "path" };
foreach (var config in configs)
{
    var internalPath = $"/App/{System.IO.Path.GetFileName(config)}"
    dab.WithBindMount(config, internalPath)
}

At the moment config-file can be added manually as a second parameter of AddDataAPIBuilder() has stated in the docs.
Looking at the signature method:
 public static IResourceBuilder<DataApiBuilderContainerResource> AddDataAPIBuilder(this IDistributedApplicationBuilder builder,
        [ResourceName] string name,
        string configFilePath = "./dab-config.json",
        int? port = null)

we simply made the default value as dab-config to make it easier to config DAB when the config file has the standard name dab-config and is placed in the AppHost folder.
Following down this path, though, we can create another signature for AddDataAPIBuilder accepting multiple configFiles:
 public static IResourceBuilder<DataApiBuilderContainerResource> AddDataAPIBuilder(this IDistributedApplicationBuilder builder,
        [ResourceName] string name,
        string[] configFilesPath,
        int? port = null)


[release 1.3] VMRestore: create DVs before creation/update of restored VM

This is a manual backport of PR https://github.com/kubevirt/kubevirt/pull/12764
NOTE On top of the backport Im adding another commit that was not introduced in the original PR since after the original PR a flake started to happen more frequently. The commit I added should be added in mine by the PR https://github.com/kubevirt/kubevirt/pull/12835

Fixes # Jira-ticket: https://issues.redhat.com/browse/CNV-47105
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

bugfix: vmrestore create DVs before creation/update of restored VM

/hold
Seems like the flake is still happening. I want to fix it before the backport merges

/unhold
Can't find a quick fix for the flake, add the tests to quarantine to not block the bug backport.

/retest

/lgtm
/approve


CLA Corporate Console - Error when signing ccla

organization.lfx.linuxfoundation.org When a user navigates to choose a project and then selects 'yes' to be cla manager and 'yes' to be cla signatory, when generating the document, it fails with " CLA System is not able to support your request. Please Click here to open a support ticket."
The only failed api is ""requestCorporateSignature":{"code":403,"message":"EasyCLA - 403 Forbidden - user  does not have access to Request Corporate Signature with Project|Organization scope of ","success":false,"data":null,"__typename":"RequestCorporateSignatureResult"}}}"
This issue is seen even when manually adding the cla-signatory, cla-manager, or both roles, before trying to sign the document.

{data: {requestCorporateSignature: {code: 422,…}}}
data: {requestCorporateSignature: {code: 422,…}}
requestCorporateSignature: {code: 422,…}
code: 422
data: null
message: "authority_name in body should match '^[a-zA-Z0-9][a-zA-Z0-9 ',.;:-_&@\#\$\(\)\+]*$'"
success: false
__typename: "RequestCorporateSignatureResult"

Created PR: https://github.com/communitybridge/easycla/pull/3394

Deployed to DEV. Included as part of the release: https://github.com/communitybridge/easycla/releases/tag/v2.0.102

this is resolved.


Support is select operator

Want to add is select and is selectattr operators as supported in Rulebook.
https://ansible.readthedocs.io/projects/rulebook/en/stable/conditions.html#supported-operators
is select: check if an item exists in the list, that satisfies the test defined by operator and value
is not select: check if an item does not exist in the list, that does not satisfy the test defined by operator and value
is selectattr: check if an object exists in the list, that satisfies the test defined by key, operator and value
is not selectattr: check if an object does not exist in the list, that does not satisfy the test defined by key, operator and value

This issue has been fixed with the PR https://github.com/ansible/ansible-policy/pull/51.


Buttons marked up as links [Android]

The “You can read the Data and Privacy Policy here” button found on the Help Improve This App and Delete My Data screens are incorrectly conveyed to TalkBack users as links. The link role is only appropriate for interactive elements that open a webpage in Chrome.
Help Improve This App screen

Delete My Data screen

Remediation Guidance
Use the Button role for these controls.

@jonnyjames Hopefully this is fixed now.

@floridemai Confirming this issue is fixed. Closing issue.


Address new package.json license property guidelines

@othiym23 recently landed a PR of mine to update npm's guidelines on license metadata for packages without licenses and with nonstandard license terms.
The relevant release notes are here: https://github.com/npm/npm/releases/tag/v2.12.0
The updated guidelines are: https://docs.npmjs.com/files/package.json#license
I see that you're using "LicenseRef-LICENSE", but also that there isn't any LICENSE file in the package. If there is a license file you'd like to include, the correct package.json license field value is now SEE LICENSE IN <filename>, where <filename> is the name of the file holding the license terms.
I'd be happy to send a quick PR to fix package.json, but don't want to presume to know what license terms you want to apply.
Thanks so much for caring about licensing enough to read the previous guidelines and use LicenseRef-LICENSE. I know guidelines changes aren't fun, but the new approach is, I think, very much better, and there aren't yet so many packages in the registry using LicenseRef-LICENSE, as you are.
Best,
K

Hi @kemitchell I believe I've updated per your request

Thanks so much. Again: Sorry for back-and-forth on the guidelines!

Thank you for notifying me about it.


'Segment' object has no attribute 'imagesequences' (neo 0.8.0)

Dear neos,
I have a problem while filtering a block with neo 0.8.0. Previously, with neo 0.7.2, I don't have such a problem. The data is resting state if it makes any sense for you.
    fpath = os.path.join(DATA_DIR, "block_rst.pkl")
    f = neo.io.PickleIO(fpath)
    block = f.read_block()
    analog_signals = block.filter(objects="AnalogSignal")

Traceback
  File "/home/ulianych/PycharmProjects/elephant/examples/granger_example.py", line 207, in granger_example_resting_state
    analog_signals = block.filter(objects="AnalogSignal")
  File "/home/ulianych/anaconda3/envs/elephant/lib/python3.7/site-packages/neo/core/container.py", line 426, in filter
    children.extend(self.data_children_recur)
  File "/home/ulianych/anaconda3/envs/elephant/lib/python3.7/site-packages/neo/core/block.py", line 115, in data_children_recur
    return tuple(unique_objs(super(Block, self).data_children_recur))
  File "/home/ulianych/anaconda3/envs/elephant/lib/python3.7/site-packages/neo/core/container.py", line 350, in data_children_recur
    self.container_children]
  File "/home/ulianych/anaconda3/envs/elephant/lib/python3.7/site-packages/neo/core/container.py", line 349, in <listcomp>
    childs = [list(child.data_children_recur) for child in
  File "/home/ulianych/anaconda3/envs/elephant/lib/python3.7/site-packages/neo/core/container.py", line 351, in data_children_recur
    return self.data_children + tuple(sum(childs, []))
  File "/home/ulianych/anaconda3/envs/elephant/lib/python3.7/site-packages/neo/core/container.py", line 321, in data_children
    self._data_child_containers]
  File "/home/ulianych/anaconda3/envs/elephant/lib/python3.7/site-packages/neo/core/container.py", line 320, in <listcomp>
    childs = [list(getattr(self, attr)) for attr in
AttributeError: 'Segment' object has no attribute 'imagesequences'

Andrew ? any idea ?

@dizcza Did you generate the file with Neo version 0.7.2 or 0.8.x?

The file was generated with neo 0.7.2

The reason why I used PickleIO is because NixIO threw exceptions when I tried to save it. Don't remember which exceptions they were and I've not checked if NixIO is improved since then.

We could in principle handle this, but PickleIO is not expected to work across different versions, and I don't think we should encourage its use.
The docstring for PickleIO says:
"Note that files in this format may not be readable if using a different version
of Neo to that used to create the file. It should therefore not be used for
long-term storage, but rather for intermediate results in a pipeline."
Having said that, if you have a lot of 0.7.2 files in this format @dizcza we could provide a temporary solution to migrate them to 0.8.0. Please let us know.

I would like to see a version control check while loading a file in neo using a file format that is not cross-version compatible.
If the current version of neo does not match with the neo version of the file I'm loading, show a warning.
In particular for PickleIO.

That's a good idea. I've created a ticket: #856


[pod-gateway]: The container will not get persistance mounts

I need to mount eg /dev to the gluetun container, but the template doesn't allow for that.
(Talos 1.8 alpha)

adding ressources definition possibilities to the template would fix that with a device-plugin as documented here: https://www.talos.dev/v1.8/kubernetes-guides/configuration/device-plugins/
but due to the chart not exposing resources in values we can not add the device to the container and pod-gateway does not work in recent runc implementations


rust: length-delimited -> dynamically-sized

Renames "length delimited" in docs and the API to "dynamically sized", both because that's clearer terminology (at least to Rust developers), but also to account for sequences, which use a slightly different length delimiter (TLV-ish).

Codecov Report

Merging #90 into develop will decrease coverage by 0.09%.
The diff coverage is 68.42%.

@@            Coverage Diff             @@
##           develop      #90     +/-   ##
==========================================
- Coverage    78.66%   78.57%   -0.1%
==========================================
  Files           14       14
  Lines          628      630      +2
==========================================
+ Hits           494      495      +1
- Misses         134      135      +1

Impacted Files
Coverage Δ

rust/src/encoder.rs
69.87% <ø> (ø)
:arrow_up:

rust/src/field/length.rs
0% <0%> (ø)
:arrow_up:

rust/src/decoder/decodable.rs
52% <100%> (ø)
:arrow_up:

rust/src/decoder/message/body.rs
85.71% <100%> (ø)
:arrow_up:

rust/src/field/wire_type.rs
70.58% <100%> (ø)
:arrow_up:

rust/src/decoder/message/value.rs
65.21% <50%> (ø)
:arrow_up:

rust/src/decoder/message.rs
86.47% <75%> (-0.44%)
:arrow_down:

rust/src/decoder/sequence.rs
78.57% <75%> (ø)
:arrow_up:

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 548d442...e5a9b55. Read the comment docs.


RadioButtons Up and Down keyboard navigationnot working

Describe the bug
When a RadioButtons control is focused, the user cannot use the Up and Down keys to change the selected item, whilst the Left and Right keys work within the current row.
Steps to reproduce the bug

Create a WinUI for Desktop solution (Preview 4 used).
Declare a RadioButtons control on the MainWindow, constrain max columns.
Add multiple RadioButton elements.

    <RadioButtons HorizontalAlignment="Center"
                  VerticalAlignment="Center"
                  MaxColumns="3">
        <RadioButtons.Items>
            <RadioButton Content="Red" />
            <RadioButton Content="Blue" />
            <RadioButton Content="Green" />
            <RadioButton Content="Cyan" />
            <RadioButton Content="Magenta" />
            <RadioButton Content="Yellow" />
            <RadioButton Content="Black" />
        </RadioButtons.Items>
    </RadioButtons>

Run the app and try keyboard navigation of the radio buttons using the arrow keys, left/right work, up/down don't :-(

Expected behavior
The user should be able to navigate the RadioButtons control using all four arrow keys
Screenshots

Version Info

NuGet package version:

    <PackageReference Include="Microsoft.WinUI" Version="3.0.0-preview4.210210.4" />

Windows app type:

UWP
Win32

Yes

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

October 2020 Update (19042)
Yes

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context

This issue has been fixed but it was not in time for the preview 4 release.


Can't load plugin after installing

Added the plugin, restarted obsidian and still can't load.
 Just kidding. There are three plugins that show up when you search confluence in the community plugin browser and I was mistaking two of them.
This issue should have been filed here: https://github.com/markdown-confluence/obsidian-integration
But issues are disabled there... :/


Unable to record for more than 1 minute in ios mobile safari browser

Description
I tried to record for more than 1 min in "video/mp4" format in safari  (version 15.2) using videojs and then used player.stop() methos to stop recording. Then its reloading the page automatically. If I record it for 30secs its working as expected.
Using videojs 7.5.5
videojs-record 4.5
Results
Expected
It should record for whatever the duration that we want to
Actual
Safari browser is reloading if we record for more than 1 minute and stops the recording using player.stop()
versions
videojs
7.5.5
videojs-record
4.5
browsers
Safari 15.2
OSes
ios device

Could be related to 'significant' memory usage: https://discussions.apple.com/thread/252519170

When streaming a movie (happens every time on Disney Plus, not always but often on Netflix) Safari automatically refreshes the page due to it using "significant memory".

@pradeepaanumalla perhaps this helps: https://github.com/collab-project/videojs-record/issues/627#issuecomment-1022804200

@thijstriemstra  This is also not working. Because I reduced the audiobytespersecond and videobytespersecond  to 81920(1/10th) and recording it for 180 seconds. The browser freezes and unable to play what was recorded also.

I would give up on iOS for now. Maybe someday Apple will invest some of their trillions in making Safari a good browser.


chore: restructure src mock to appropriate folders

Changes

Move CustomInput and spec to own directory
Move MockedWrappedComponent to own directory
Update References

Issue
Fixes #39

Plz Merge thanks


Saving Episodes in Season Folders

Hi! Firstly, great, clean app! Really efficient :-)
Was wondering how easy it would be to implement a feature to further organise media downloaded into separate season folders within the show folders (i.e. ShowName > Season1 > Episode1).
Keep up the good work! :-)

Hmm, the database does hold structured data but there isn't a well-defined way of structuring it. It varies between day shows (ie. Colbert Report), specials, season specials, multi-episode (S01E21E22), so a XML representation is feasible but as far as I know there's no standard yet.

Hmm, the database does hold structured data but there isn't a well-defined way of structuring it. It varies between day shows (ie. Colbert Report), specials, season specials, multi-episode (S01E21E22), so a XML representation is feasible but as far as I know there's no standard yet.


fix(version): ec v3.0.0 added suffix v

The release of v3.0.0 introduce a breaking change:

BREAKING:
Releases and tags now have a leading v.
Marked as breaking because this may needs adjustments in the specific wrapper tools for other languages.

cf. https://github.com/editorconfig-checker/editorconfig-checker/releases/tag/v3.0.0
This PR fixes the asdf extension to make it work again

@Gabitchov


Fix IOContext to use default

Lucene changed IOContext.Read with IOContext.Default in https://github.com/apache/lucene/pull/13242

Can you split this to just cover the main changes?
I would prefer not to pull the benchmarking tools into main?


LaTeX PDF documentation fails

Is there a way to generate documentation of poliastro ver. 0.15.0 as a pdf file? When I attempted to so I get:
(base) user@Mac-Pro docs % make latexpdf
sphinx-build -b latex -d build/doctrees   source build/latex
Running Sphinx v4.0.1
Extension error:
Could not import extension autoapi.extension (exception: No module named 'autoapi')
make: *** [latexpdf] Error 2
(base) user@Mac-Pro docs %
Any suggestions?
Sam Dupree.

Hello @OrbitalMechanic , sorry for the delay!
After reading your request I went to Read the Docs because I though they were generating the PDF for us, but apparently not. So I opened an issue about it https://github.com/readthedocs/readthedocs.org/issues/8253
On the other hand, to generate the PDF, these are the steps:
(base) $ pip install .[dev]  # From the `pyproject.toml` directory
(base) $ cd docs
(base) $ make latexpdf

In other words, you were missing the [dev] extra dependencies, that install the documentation dependencies.
I am generating the PDF myself now, I'll attach it here.

(Edit: added one extra set of dependencies)

Well, it turns out that our PDF documentation with LaTeX is a bit broken :)
! Package inputenc Error: Unicode character ♁ (U+2641)
(inputenc)                not set up for use with LaTeX.

See the inputenc package documentation for explanation.
Type  H <return>  for immediate help.
 ...

l.544 ...ound Earth (♁) at epoch J2000.000 (TT)}

?

I typed S to skip the errors.

And finally, I got it! I am not 100 % sure that this is complete, but it's a start. poliastro.pdf
Noting this as a bug, thanks as always @OrbitalMechanic 🙏🏽

I also tried generating the PDF with rinohtype, but it failed: https://github.com/brechtm/rinohtype/issues/267

Juan,
Thank you responding to my posting. I tried to generate the PDF using
your procedure below. The result I get is the error message:
(base) user@Mac-Pro poliastro % pip install .[dev]
zsh: no matches found: .[dev]
From the posting on GitHub I tried |pip install .[dev,cesium] and got
the following error message|
(base) user@Mac-Pro poliastro % pip install .[dev,cesium]
zsh: no matches found: .[dev,cesium]
Now I checked the poliastro GitHub download file and got
(base) user@Mac-Pro poliastro % ls -l
total 224
-rw-r--r--   1 user  staff  3132 Jun  6 22:31 CODE_OF_CONDUCT.md
-rw-r--r--   1 user  staff  5124 Jun  6 22:31 CONTRIBUTING.md
-rw-r--r--   1 user  staff  1132 Jun  6 22:31 COPYING
-rw-r--r--   1 user  staff   166 Jun  6 22:31 MANIFEST.in
-rw-r--r--@  1 user  staff   373 Jun  6 22:31 Makefile
-rw-r--r--   1 user  staff  8720 Jun  6 22:31 README.md
-rw-r--r--   1 user  staff  2212 Jun  6 22:31 azure-pipelines.yml
drwxr-xr-x   3 user  staff   102 Jun  6 22:31 binder
-rw-r--r--   1 user  staff  5824 Jun  6 22:31 codemeta.json
drwxr-xr-x   5 user  staff   170 Jun  6 22:31 contrib
drwxr-xr-x   5 user  staff   170 Jun  6 22:32 docs
-rw-r--r--   1 user  staff  4288 Jun  6 22:31 index.ipynb
-rw-r--r--   1 user  staff    87 Jun  6 22:31 mypy.ini
-rw-r--r--   1 user  staff  2961 Jun  6 22:31 pyproject.toml
-rw-r--r--   1 user  staff   378 Jun  6 22:31 setup.cfg
drwxr-xr-x   3 user  staff   102 Jun  6 22:31 src
drwxr-xr-x  20 user  staff   680 Jun  6 22:31 tests
-rw-r--r--   1 user  staff  2165 Jun  6 22:31 tox.ini
There is no pyproject.toml, but as you'll see I have pyproject.toml
directory.
Please advise.
Sam Dupree.
On June/11/2021 05:30:46, Juan Luis Cano Rodríguez wrote:

Hello @OrbitalMechanic https://github.com/OrbitalMechanic , sorry
for the delay!
After reading your request I went to Read the Docs because I though
they were generating the PDF for us, but apparently not. So I opened
an issue about it readthedocs/readthedocs.org#8253
https://github.com/readthedocs/readthedocs.org/issues/8253
On the other hand, to generate the PDF, these are the steps:
|(base) $ pip install .[dev] # From the pyproject.toml directory
(base) $ cd docs (base) $ make latexpdf |
In other words, you were missing the |[dev]| extra dependencies, that
install the documentation dependencies.
I am generating the PDF myself now, I'll attach it here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/poliastro/poliastro/issues/1242#issuecomment-859444123,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEO353OPTI5TYH2I53F62TTSHJUNANCNFSM46GWFNVQ.

I see! The command I gave you needs to be tweaked according to https://stackoverflow.com/a/30539963
Please try pip install '.[dev,cesium]'

I came back to this. Yes, PDF documentation build is failing with obscure LaTeX syntax errors. I have no idea how to fix them, but if anyone wants to dig deep enough, you're welcome to do so.
Good starting point:
diff --git a/.readthedocs.yaml b/.readthedocs.yaml
index 9f6a399e..ded872c2 100644
--- a/.readthedocs.yaml
+++ b/.readthedocs.yaml
@@ -15,3 +15,7 @@ python:

 sphinx:
   fail_on_warning: true
+
+formats:
+  - html
+  - pdf
diff --git a/docs/source/conf.py b/docs/source/conf.py
index adbe8f54..56322d41 100644
--- a/docs/source/conf.py
+++ b/docs/source/conf.py
@@ -177,3 +177,6 @@ exclude_patterns.extend(["autoapi/index.rst", "autoapi/poliastro/index.rst"])
 # Ignore sphinx-autoapi warnings on reimported objects
 # See https://github.com/readthedocs/sphinx-autoapi/issues/285
 suppress_warnings.append("autoapi.python_import_resolution")
+
+# LaTeX settings for PDF generation
+latex_engine = "xelatex"

Attempted to build the latexpdf document for poliastro ver. 0.17.0 under Mac OS X version 12.4 (Monterey), and it fails with the message:
Latexmk: Missing input file 'tgtermes.sty' (or dependence on it) from following:
  '! LaTeX Error: File `tgtermes.sty' not found.'
Latexmk: Errors, so I did not complete making targets
Collected error summary (may duplicate other messages):
  pdflatex: Command for 'pdflatex' gave return code 1
      Refer to 'poliastro.log' for details
Latexmk: If appropriate, the -f option can be used to get latexmk
  to try to force complete processing.
make[1]: *** [poliastro.pdf] Error 12
make: *** [latexpdf] Error 2
(base) user@Mac-Pro docs %

See the attached file for details.
poliastro_latexpdf_build_log.txt

Hi @OrbitalMechanic, thanks for trying it out!
I did a quick search and the root cause seems to be a missing TeX package, possibly tex-gyre or similar. I'm not sure how did you install LaTeX/TeXLive on macOS, could you try finding this package and updating us?
I'd love to bring PDF/static documentation back but LaTeX is a mess. Thinking about exporting the HTML as a static document or similar, would that work for you?

See my responses below.
Sam Dupree.
On July/11/2022 21:51:22, Juan Luis Cano Rodríguez wrote:

Hi @OrbitalMechanic https://github.com/OrbitalMechanic, thanks for
trying it out!
I did a quick search and the root cause seems to be a missing TeX
package, possibly |tex-gyre| or similar. I'm not sure how did you
install LaTeX/TeXLive on macOS, could you try finding this package and
updating us?

*/Used the TeXLive utility to install the TeX packages I needed on a
package by package basis. However, I still get errors using latexpdf. / **
*

**
I'd love to bring PDF/static documentation back but LaTeX is a mess.
Thinking about exporting the HTML as a static document or similar,
would that work for you?

/I was able to build the HTML-based documentation successfully. In
addition, I was able to build the epub based documentation as well.
Either of these solutions will work for me.//
/

//
—
Reply to this email directly, view it on GitHub
https://github.com/poliastro/poliastro/issues/1242#issuecomment-1181222555,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEO3545GKCUFS4MCQWSIQTVTTFRVANCNFSM46GWFNVQ.
You are receiving this because you were mentioned.Message ID:
@.***>


⚠ Bofrost.es has degraded performance

In ae4b1e9, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1519 ms

Resolved: Bofrost.es performance has improved in 69e9b65 after 18 minutes.


Syncing from upstream patroni/patroni (master)

bt_gitbot

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.875%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
14354

Relevant Lines:
14372

💛  - Coveralls


328dfd2 (JTAG reset) breaks STM32F217 programming

I'm having trouble programming/debugging a STM32F217 chip using the STLink/V2 in JTAG mode.
It always worked before and I'm able to bisect the problem to the recent commit 328dfd2, which introduced changes to JTAG reset. Removing the calls to jtag_reset() in that commit makes it work again.

2013-07-18T16:09:40 INFO src/stlink-common.c: Starting Flash write for F2/F4
2013-07-18T16:09:40 INFO src/stlink-common.c: Successfully loaded flash loader in sram
size: 32768
2013-07-18T16:09:44 ERROR src/stlink-common.c: flash loader run error
2013-07-18T16:09:44 ERROR src/stlink-common.c: run_flash_loader(0x8000000) failed! == -1
stlink_fwrite_flash() == -1

Should be fixed by now.


onchange listener for store?

I'm using this with Svelte, and am trying to use a localStorage solution from here that looks like this:
export default function useLocalStorage(store, key) {
  const json = localStorage.getItem(key);
  if (json) {
    store.set(JSON.parse(json));
  }

  store.onchange(state => {
    localStorage.setItem(key, JSON.stringify(state));
  });
}

is there a way to easily grab any change to the redux-zero store, something equivalent to the onchange from the Svelte's store?

@mspanish
You can do same thing with middleware like this.
let myKey;

function setLocalStorage(store) {
    localStorage.setItem(myKey, JSON.stringify(store.getState()));
    // console.log("local-storage-middleware - state after change", store.getState());
}

const middleware = store => next => action => {
    let result = next(action);
    if (result && result.then) {
        // setLocalStorage(store);
        return result.then(() => setLocalStorage(store));
    }
    setLocalStorage(store);
    return result;
}

(middleware as any).init = function(store, key) {
    const json = localStorage.getItem(myKey = key);
    if (json) {
        store.setState(JSON.parse(json));
        // console.log("local-storage-middleware - init store", store.getState());
    }
}

export default middleware;

And you can set it up in store https://github.com/Kiho/redux-zero/blob/master/examples/svelte/middleware/src/store.ts#L15

Hi @mspanish
Thanks for the question. I'm closing this right now, but if you have any more questions please feel free to ask.

thanks that is very helpful - I hacked the update() fn to do this, but I'm sure that's  a better method! One question though - right now I"m not using actions - just using setState - would this only work if you are using actions?

Hi @mspanish, this might be hack too but if you construct root component in this way then it works.
<div>
	<CounterComponent/>
</div>

<script>
import CounterComponent from "./components/Counter.html";
import store from "./store";

let myKey = 'my-app-1';
let unsubscribe;
let listener;

function setLocalStorage(state) {
    localStorage.setItem(myKey, JSON.stringify(state));
    console.log("App.html - setLocalStorage(state)", state);
}

export default {
	components: {
		CounterComponent
	},
	oncreate() {
		const json = localStorage.getItem(myKey);
		if (json) {
			store.setState(JSON.parse(json));
			console.log("App.html - oncreate()", store.getState());
		}
		listener = setLocalStorage.bind(store);
		unsubscribe = store.subscribe(listener);
	},
	ondestroy () {
		unsubscribe(listener);
		console.log('App.html - ondestory()');
	}
}
</script>

https://github.com/Kiho/redux-zero/blob/local-storage/examples/svelte/counter/src/App.html

thank you :)


feat: expose playback functions

Summary
Allow to play/pause video from component reference
closes #3097
Example
// For internal use case
const paused = true;
videoRef.current.setPlayerStatus(paused) // Pause video

// For users
videoRef.current.pause()
videoRef.current.play()

Test plan

[x] Functions are working on iOS
[x] Functions are working on Android

additionally, can you remove changes in sample please ?
I agree that linter is not correctly configured in samples, but it makes this change difficult to review

@KrzysztofMoch can you fix conflicts please ? This is Ok to be merged on my side, Thank you


Is this project alive?

Title says it all

It depends. I think some would say so, but see https://github.com/mopidy/mopidy-youtube/issues/87#issuecomment-414153256

In terms of development the readme states:

Mopidy-YouTube is currently kept on life support by the Mopidy core developers. It is in need of a more dedicated maintainer.

Thanks God for that, I forgot how to read. On 25 Feb 2019 10:11, Nick Steel<EMAIL_ADDRESS>wrote:In terms of development the readme states:
Mopidy-YouTube is currently kept on life support by the Mopidy core developers. It is in need of a more dedicated maintainer.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

And on that note I think we are done here. If you have a specific bug report or feature request then open another issue.


Californium DTLS failed to handshake

Question
Here is my test setup for two scenarios:
I did test for both release versions:
1.5.0 and 2.0.0-M16
And the sam result happened on both releases.
May you help if configuration to DTLS so that the BS server will not interfere with the Registration Update.
I am looking forward to hear from and Thank for your help in advanced. Henry Nguyen

BS and DM application run on different servers: DID NOT work
BS Server (bootstrap) run on bs.local=192..68.68.57/wp=8080/lp=5683/slp=5684
BS is configured to support Id=IOTS-01 PSK=1A2B3C4D and coaps://bs.local:5684/coaps://dm.local:5684

DM server (Device Management runs on dm.local=<IP_ADDRESS>/lp=5683/slp=5684
DM is configured to support  Id=IOTS-01 PSK=1A2B3C4D
DTLS for bootstrap works
DTLS for registration update failed. It the Client IOTS-01 send Client Hello but the BS sends Hello Verify to IOTS-01. The Client IOTS-01 expects the DM to send the Hello Verify.

BS and DM application run on the same server: work
BS Server (bootstrap) run on bs.local=192..68.68.57/wp=8080/lp=5683/slp=5684
BS is configured to support Id=IOTS-01 PSK=1A2B3C4D and coaps://bs.local:6684/coaps://dm.local:6684

DM server (Device Management runs on bs.local=<IP_ADDRESS>/wp=9080/lp=6683/slp=6684
DM is configured to support  Id=IOTS-01 PSK=1A2B3C4D
DTLS for bootstrap works
DTLS for registration update  works. It the Client IOTS-01 send Client Hello and the DM sends Hello Verify to IOTS-01.
LeshanPoCSetup.pdf
captureinpcapngaa.zip
captureinpcapngab.zip
captureinpcapngac.zip

Hi,

Why using 2.0.0-M6 and not most recent one ?
Which client are you using ?

I try to donwload your captures but :

22 Mo for a capture about a simple use case like this ... .
try to open the smaller one 1.2 Mo :  file in the archive has no extensions and does not work with wireshark.

Please provide more clean captures :pray:
Using same ID/PSK for bootstrap server and dm server is OK for test but not really a good idea in production.

Hi Leshan Gatekeepers,

Why using 2.0.0-M6 and not most recent one ? I am using 2.0.0-M16

2 Which client are you using? I am using the  lesion-demo-client code provided.

Using same ID/PSK for bootstrap server and dm server is OK for test but not really a good idea in production - Thank you for remind about using different PSK ID/KEY for Production.

I will provide you better Wireshark capture.

Do you have a chance to look at the PDF file with few diagrams to illustrate the issue. I am sure that DTLS failed to handshake. Why? it is because if I set up both Bootstrap application and Device Management application running in the same server. Everything works fine but If I set up Bootstrap application and Device Management application the Bootstrap will interfere with the DTLS process. I will try to set up another scenarios where the PSK ID/KEY will be different for Bootstrap and Device Management if possible.

Regards, Henry

Hi Leshan Gatekeepers,
Here is my Wireshark file.
capturefile.pcapng.zip

Just to let you know, it is not recommended to use 2.0.0-M6 for security reason.
See : https://github.com/eclipse-leshan/leshan/security/policy#versions-security-state
As you said,  the source address IP of HELLO_VERIFY_REQUEST seems not good.
You get the capture at client side right ?
My guess this is a network configuration issue and this is not related to Leshan or Scandium (the DTLS library used).

I will try to set up another scenarios where the PSK ID/KEY will be different for Bootstrap and Device Management if possible.

I doubt this will solve the issue.
Just to be sure, I tested with a leshan-client-demo 1.5.0 on Leshan sandbox and it works as expected :
❯ java -jar leshan-client-demo-1.5.0.jar  -n "IOTS-01" -i "IOTS-01" -p "1A2B3C4D" -b -u "leshan.eclipseprojects.io:5784"

2024-11-15 11:22:53,850 INFO LeshanClientDemo - Commands available :

  - create <objectId> : to enable a new object.
  - delete <objectId> : to disable a new object.
  - update : to trigger a registration update.
  - w : to move to North.
  - a : to move to East.
  - s : to move to South.
  - d : to move to West.

2024-11-15 11:22:53,851 INFO LeshanClient - Starting Leshan client ...
2024-11-15 11:22:53,858 INFO LeshanClient - Leshan client[endpoint:IOTS-01] started.
2024-11-15 11:22:53,858 INFO DefaultRegistrationEngine - Trying to start bootstrap session to coaps://leshan.eclipseprojects.io:5784 ...
2024-11-15 11:22:54,490 INFO CaliforniumEndpointsManager - New endpoint created for server coaps://leshan.eclipseprojects.io:5784 at coaps://[0:0:0:0:0:0:0:0]:46774
2024-11-15 11:22:54,522 INFO LeshanClientDemo - DTLS Full Handshake initiated by client : STARTED ...
2024-11-15 11:22:54,794 INFO LeshanClientDemo - DTLS Full Handshake initiated by client : SUCCEED
2024-11-15 11:22:54,874 INFO DefaultRegistrationEngine - Bootstrap started
2024-11-15 11:22:55,077 DEBUG Security - Write on Security resource /0/0/0
2024-11-15 11:22:55,077 DEBUG Security - Write on Security resource /0/0/1
2024-11-15 11:22:55,078 DEBUG Security - Write on Security resource /0/0/2
2024-11-15 11:22:55,078 DEBUG Security - Write on Security resource /0/0/3
2024-11-15 11:22:55,078 DEBUG Security - Write on Security resource /0/0/4
2024-11-15 11:22:55,078 DEBUG Security - Write on Security resource /0/0/5
2024-11-15 11:22:55,078 DEBUG Security - Write on Security resource /0/0/6
2024-11-15 11:22:55,078 DEBUG Security - Write on Security resource /0/0/7
2024-11-15 11:22:55,078 DEBUG Security - Write on Security resource /0/0/8
2024-11-15 11:22:55,078 DEBUG Security - Write on Security resource /0/0/9
2024-11-15 11:22:55,079 DEBUG Security - Write on Security resource /0/0/11
2024-11-15 11:22:55,079 DEBUG Security - Write on Security resource /0/0/12
2024-11-15 11:22:55,157 DEBUG Security - Write on Security resource /0/1/0
2024-11-15 11:22:55,157 DEBUG Security - Write on Security resource /0/1/1
2024-11-15 11:22:55,158 DEBUG Security - Write on Security resource /0/1/2
2024-11-15 11:22:55,158 DEBUG Security - Write on Security resource /0/1/3
2024-11-15 11:22:55,158 DEBUG Security - Write on Security resource /0/1/4
2024-11-15 11:22:55,159 DEBUG Security - Write on Security resource /0/1/5
2024-11-15 11:22:55,159 DEBUG Security - Write on Security resource /0/1/6
2024-11-15 11:22:55,159 DEBUG Security - Write on Security resource /0/1/7
2024-11-15 11:22:55,160 DEBUG Security - Write on Security resource /0/1/8
2024-11-15 11:22:55,160 DEBUG Security - Write on Security resource /0/1/9
2024-11-15 11:22:55,161 DEBUG Security - Write on Security resource /0/1/10
2024-11-15 11:22:55,161 DEBUG Security - Write on Security resource /0/1/11
2024-11-15 11:22:55,161 DEBUG Security - Write on Security resource /0/1/12
2024-11-15 11:22:55,232 DEBUG Server - Write on Server resource /1/0/0
2024-11-15 11:22:55,233 DEBUG Server - Write on Server resource /1/0/1
2024-11-15 11:22:55,233 DEBUG Server - Write on Server resource /1/0/2
2024-11-15 11:22:55,234 DEBUG Server - Write on Server resource /1/0/6
2024-11-15 11:22:55,234 DEBUG Server - Write on Server resource /1/0/7
2024-11-15 11:22:55,380 INFO DefaultRegistrationEngine - Bootstrap finished coaps://leshan.eclipseprojects.io:5784.
2024-11-15 11:22:55,384 INFO CaliforniumEndpointsManager - New endpoint created for server coaps://leshan.eclipseprojects.io:5684 at coaps://[0:0:0:0:0:0:0:0]:39580
2024-11-15 11:22:55,385 INFO DefaultRegistrationEngine - Trying to register to coaps://leshan.eclipseprojects.io:5684 ...
2024-11-15 11:22:55,388 INFO LeshanClientDemo - DTLS Full Handshake initiated by client : STARTED ...
2024-11-15 11:22:55,560 INFO LeshanClientDemo - DTLS Full Handshake initiated by client : SUCCEED
2024-11-15 11:22:55,614 INFO DefaultRegistrationEngine - Registered with location '/rd/FudLE87GM6'.
2024-11-15 11:22:55,615 INFO DefaultRegistrationEngine - Next registration update to coaps://leshan.eclipseprojects.io:5684 in 53s...
2024-11-15 11:23:00,721 INFO LeshanClient - Destroying Leshan client ...
2024-11-15 11:23:00,722 INFO DefaultRegistrationEngine - Trying to deregister to coaps://leshan.eclipseprojects.io:5684 ...
2024-11-15 11:23:00,778 INFO DefaultRegistrationEngine - De-register response DELETED null.
2024-11-15 11:23:00,781 INFO LeshanClient - Leshan client destroyed.

And here I the trace for the 1.5.0 failed after bootstrap as well.
The Client ran in the Windows laptop.
C:\DevTools\Java\jdk11.0.21_9\bin\java.exe -javaagent:C:\DevTools\Jetbrains2024\idea\lib\idea_rt.jar=53904:C:\DevTools\Jetbrains2024\idea\bin -Dfile.encoding=UTF-8 -classpath C:\Users\henry\IdeaProjects\sew-poc-oma-v1.0\leshan-client-demo\target\classes;C:\Users\henry\IdeaProjects\sew-poc-oma-v1.0\leshan-client-cf\target\classes;C:\Users\henry\IdeaProjects\sew-poc-oma-v1.0\leshan-core-cf\target\classes;C:\Users\henry\IdeaProjects\sew-poc-oma-v1.0\leshan-core\target\classes;C:\Users\henry.m2\repository\com\eclipsesource\minimal-json\minimal-json\0.9.5\minimal-json-0.9.5.jar;C:\Users\henry\IdeaProjects\sew-poc-oma-v1.0\leshan-client-core\target\classes;C:\Users\henry.m2\repository\org\eclipse\californium\californium-core\2.8.0\californium-core-2.8.0.jar;C:\Users\henry.m2\repository\org\eclipse\californium\californium-legal\2.8.0\californium-legal-2.8.0.jar;C:\Users\henry.m2\repository\org\eclipse\californium\element-connector\2.8.0\element-connector-2.8.0.jar;C:\Users\henry.m2\repository\net\i2p\crypto\eddsa\0.3.0\eddsa-0.3.0.jar;C:\Users\henry.m2\repository\org\eclipse\californium\scandium\2.8.0\scandium-2.8.0.jar;C:\Users\henry.m2\repository\commons-cli\commons-cli\1.5.0\commons-cli-1.5.0.jar;C:\Users\henry.m2\repository\commons-io\commons-io\2.11.0\commons-io-2.11.0.jar;C:\Users\henry.m2\repository\org\apache\httpcomponents\httpcore\4.3\httpcore-4.3.jar;C:\Users\henry.m2\repository\org\apache\httpcomponents\httpclient\4.3.1\httpclient-4.3.1.jar;C:\Users\henry.m2\repository\commons-logging\commons-logging\1.1.3\commons-logging-1.1.3.jar;C:\Users\henry.m2\repository\commons-codec\commons-codec\1.6\commons-codec-1.6.jar;C:\Users\henry.m2\repository\org\slf4j\slf4j-simple\1.7.36\slf4j-simple-1.7.36.jar;C:\Users\henry.m2\repository\org\slf4j\slf4j-api\1.7.36\slf4j-api-1.7.36.jar org.eclipse.leshan.client.demo.LeshanClientDemo -i IOTS-01 -p 1a2b3c4d -n IOTS-01 -b -u ubs.local:5684
2024-11-18 16:29:07,325 INFO LeshanClientDemo - Commands available :

create  : to enable a new object.
delete  : to disable a new object.
update : to trigger a registration update.
w : to move to North.
a : to move to East.
s : to move to South.
d : to move to West.

2024-11-18 16:29:07,326 INFO LeshanClient - Starting Leshan client ...
2024-11-18 16:29:07,381 INFO LeshanClient - Leshan client[endpoint:IOTS-01] started.
2024-11-18 16:29:07,381 INFO DefaultRegistrationEngine - Trying to start bootstrap session to coaps://ubs.local:5684 ...
2024-11-18 16:29:07,661 INFO CaliforniumEndpointsManager - New endpoint created for server coaps://ubs.local:5684 at coaps://<IP_ADDRESS>:54803
2024-11-18 16:29:07,705 INFO LeshanClientDemo - DTLS Full Handshake initiated by client : STARTED ...
2024-11-18 16:29:07,872 INFO LeshanClientDemo - DTLS Full Handshake initiated by client : SUCCEED
2024-11-18 16:29:07,911 INFO DefaultRegistrationEngine - Bootstrap started
2024-11-18 16:29:08,097 DEBUG Security - Write on Security resource /0/0/0
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/1
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/2
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/3
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/4
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/5
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/6
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/7
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/8
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/9
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/10
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/11
2024-11-18 16:29:08,098 DEBUG Security - Write on Security resource /0/0/12
2024-11-18 16:29:08,125 DEBUG Security - Write on Security resource /0/1/0
2024-11-18 16:29:08,125 DEBUG Security - Write on Security resource /0/1/1
2024-11-18 16:29:08,126 DEBUG Security - Write on Security resource /0/1/2
2024-11-18 16:29:08,126 DEBUG Security - Write on Security resource /0/1/3
2024-11-18 16:29:08,126 DEBUG Security - Write on Security resource /0/1/4
2024-11-18 16:29:08,126 DEBUG Security - Write on Security resource /0/1/5
2024-11-18 16:29:08,126 DEBUG Security - Write on Security resource /0/1/6
2024-11-18 16:29:08,126 DEBUG Security - Write on Security resource /0/1/7
2024-11-18 16:29:08,126 DEBUG Security - Write on Security resource /0/1/8
2024-11-18 16:29:08,126 DEBUG Security - Write on Security resource /0/1/9
2024-11-18 16:29:08,126 DEBUG Security - Write on Security resource /0/1/10
2024-11-18 16:29:08,126 DEBUG Security - Write on Security resource /0/1/11
2024-11-18 16:29:08,126 DEBUG Security - Write on Security resource /0/1/12
2024-11-18 16:29:08,138 DEBUG Server - Write on Server resource /1/0/0
2024-11-18 16:29:08,139 DEBUG Server - Write on Server resource /1/0/1
2024-11-18 16:29:08,139 DEBUG Server - Write on Server resource /1/0/2
2024-11-18 16:29:08,139 DEBUG Server - Write on Server resource /1/0/6
2024-11-18 16:29:08,139 DEBUG Server - Write on Server resource /1/0/7
2024-11-18 16:29:08,183 INFO DefaultRegistrationEngine - Bootstrap finished coaps://ubs.local:5684.
2024-11-18 16:29:08,187 INFO CaliforniumEndpointsManager - New endpoint created for server coaps://udm.local:5684 at coaps://<IP_ADDRESS>:54804
2024-11-18 16:29:08,188 INFO DefaultRegistrationEngine - Trying to register to coaps://udm.local:5684 ...
2024-11-18 16:29:08,207 INFO LeshanClientDemo - DTLS Full Handshake initiated by client : STARTED ...
2024-11-18 16:29:39,263 INFO LeshanClientDemo - DTLS Full Handshake initiated by client : FAILED (Handshake flight 1 failed! Stopped by timeout after 4 retransmissions!)
2024-11-18 16:29:39,267 INFO DefaultRegistrationEngine - Registration failed: Timeout.
2024-11-18 16:29:39,284 INFO CaliforniumEndpointsManager - Clear DTLS session for resumption for server coaps://udm.local:5684
2024-11-18 16:29:39,284 INFO DefaultRegistrationEngine - Trying to register to coaps://udm.local:5684 ...
2024-11-18 16:29:39,285 INFO LeshanClientDemo - DTLS Full Handshake initiated by client : STARTED ...
2024-11-18 16:30:10,341 INFO LeshanClientDemo - DTLS Full Handshake initiated by client : FAILED (Handshake flight 1 failed! Stopped by timeout after 4 retransmissions!)
2024-11-18 16:30:10,342 INFO DefaultRegistrationEngine - Registration failed: Timeout.
2024-11-18 16:30:10,342 INFO DefaultRegistrationEngine - Try to register to coaps://udm.local:5684 again in 600s...

I am using the lesion-2.0.0-M16 (M16 sixteen not M6 six).

Very sorry about that I don't know why I read M6 instead of M16 ... 🙇♀

I believe that the problem may be happening at the registration update not at the bootstrap.

Probably a detail, but the device will probably do a REGISTER request, not a registration UPDATE request.
Reading your capture, I didn't see any issue in bootstrap process too.

The client performs the bootstrap operation correctly but when the client performs registration update the DTLS fails to function because the bootstrap server interferes with the DTLS in shaking, please refer to the PDF document for the setup and Wireshark trace to see the DTLS failure.

I read the PDF document twice.
I don't think the "server interfere", this sounds clearly a network issue.
Bootstrap server doesn't not send HELLO_VERIFY_REQUEST spontaneously,
I also read the capture several time and I understand the problem is the source address of HELLO_VERIFY_PACKET.
You client log is expected looking at wireshark capture.
So again,  with current information, I see nothing which makes me think this is not a network (configuration?) issue.
Did you try to use Leshan sandbox ?

https://leshan.eclipseprojects.io
https://leshan.eclipseprojects.io/bs

Hi Leshan Gatekeepers,
The reason that I deploy the Bootstrap Application to run on one server and the Device Management Application to run on another server because I think in production we will deploy Leshan this way. The Bootstrap Application is used to authenticate the device. The Device Management Application is used to authorise the device.
I dont think it is because of the network issue as the Bootstrap operation works fine:
The DTLS handshake works fine
The Bootstrap operation works fine

However, when the Device performs the Registration Update
The DTLS handshake fails because I believe the DTLS logic is faultly code to use the Bootstrap server configuration. That explains why the Bootstrap Application sends the DTLS Hello Verify

I believe that the issue is likely at the Californium layer.
And no I have not tried your sandbox yet:
https://leshan.eclipseprojects.io/
https://leshan.eclipseprojects.io/bs

All my setup is done using Jetbrains IntelliJ for both Leshan-2.0.0-M16 and Leshan-1.5.0.
All non-security work fines for both versions.
All PSK seceurity partially works, that is the bootstrap operation works well but the device registration update fails at the DTLS.

Regards, Henry

6527 17.289198      <IP_ADDRESS>         <IP_ADDRESS>         DTLS     119    Client Hello
   // Client says Hello to the dm.local
   6528 17.289770      <IP_ADDRESS>         <IP_ADDRESS>         DTLSv1.2 102    Hello Verify Request
  // Bootstrap says Hello Verify Request -- It should be the DeviceManagement says Hello Verify Request
   6551 19.295199      <IP_ADDRESS>         <IP_ADDRESS>         DTLS     119    Client Hello
 // Client now says Hello to the Bootstrap
   6552 19.296286      <IP_ADDRESS>         <IP_ADDRESS>         DTLSv1.2 102    Hello Verify Request
// Bootstrap says Hello Verify Request to the Client.

If the Client Hello is sent to <IP_ADDRESS> but the Hello Verify Request is then from <IP_ADDRESS>, you obviously have an issue with your network setup. The error is related to that, not to Californium.

Hi Leshan Gatekeepers,
If both the DTLS/Bootstrap and DTLS/Registration Update fail to work, then it is the network issue. But here the DTLS/Bootstrap works and DTLS/Registration Update fail. Network is an issue...Ummm I think it is the DTLS and Bootstrap/Device Management IP addresses logic may be the issue and which layer handle the swapping of the Bootstrap and Device Management IP addresses...You would know more than me.
My Bootstrap operation works fine at the DTLS handshake and Bootstrap.If it is the network issue then the DTLS handshake MUST fail at the Bootstrap operation.
6431 12.156966      <IP_ADDRESS>         <IP_ADDRESS>         DTLSv1.2 119    Client Hello
6432 12.162438      <IP_ADDRESS>         <IP_ADDRESS>         DTLSv1.2 102    Hello Verify Request
6433 12.164259      <IP_ADDRESS>         <IP_ADDRESS>         DTLSv1.2 151    Client Hello
6434 12.165444      <IP_ADDRESS>         <IP_ADDRESS>         DTLSv1.2 162    Server Hello, Server Hello Done
6435 12.184449      <IP_ADDRESS>         <IP_ADDRESS>         DTLSv1.2 143    Client Key Exchange, Change Cipher Spec, Finished
6436 12.192381      <IP_ADDRESS>         <IP_ADDRESS>         DTLSv1.2 109    Change Cipher Spec, Finished
6437 12.193665      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     105    CON, MID:24550, POST, TKN:34 a4 59 57 23 19 38 d8, /bs?pct=112&ep=IOTS-01
6438 12.195977      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     83     ACK, MID:24550, 2.04 Changed, TKN:34 a4 59 57 23 19 38 d8, /bs
6439 12.197246      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     85     CON, MID:63682, DELETE, TKN:f0 a3 81 eb 66 4a 6c ad, /0
6440 12.203849      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     83     ACK, MID:63682, 2.02 Deleted, TKN:f0 a3 81 eb 66 4a 6c ad, /0
6443 12.211932      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     85     CON, MID:63683, DELETE, TKN:d8 54 cb e5 82 8e ec 58, /1
6444 12.212601      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     83     ACK, MID:63683, 2.02 Deleted, TKN:d8 54 cb e5 82 8e ec 58, /1
6445 12.222322      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     157    CON, MID:63684, PUT, TKN:14 c3 c4 fb ef 70 5c 20, /0/0
6446 12.227191      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     83     ACK, MID:63684, 2.04 Changed, TKN:14 c3 c4 fb ef 70 5c 20, /0/0
6447 12.244935      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     157    CON, MID:63685, PUT, TKN:1c e2 5a 3e 82 c8 44 cd, /0/1
6448 12.247268      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     83     ACK, MID:63685, 2.04 Changed, TKN:1c e2 5a 3e 82 c8 44 cd, /0/1
6449 12.251552      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     107    CON, MID:63686, PUT, TKN:20 98 9f 39 aa ab 2d ce, /1/0
6450 12.252736      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     83     ACK, MID:63686, 2.04 Changed, TKN:20 98 9f 39 aa ab 2d ce, /1/0
6451 12.257932      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     86     CON, MID:63687, POST, TKN:78 b3 4e 12 bc be 7e df, /bs
6458 12.259032      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     75     ACK, MID:63687, Empty Message
6459 12.260470      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     83     CON, MID:24551, 2.04 Changed, TKN:78 b3 4e 12 bc be 7e df, /bs
6460 12.263188      <IP_ADDRESS>         <IP_ADDRESS>         CoAP     75     ACK, MID:24551, Empty Message
After the Bootstrap operation the Device will perform Registration Update, here the DTLS handshake fails.
6527 17.289198      <IP_ADDRESS>         <IP_ADDRESS>         DTLS     119    Client Hello
// Client says Hello to the dm.local
6528 17.289770      <IP_ADDRESS>         <IP_ADDRESS>         DTLSv1.2 102    Hello Verify Request
// Bootstrap says Hello Verify Request -- It should be the DeviceManagement says Hello Verify Request
6551 19.295199      <IP_ADDRESS>         <IP_ADDRESS>         DTLS     119    Client Hello
// Client now says Hello to the Bootstrap
6552 19.296286      <IP_ADDRESS>         <IP_ADDRESS>         DTLSv1.2 102    Hello Verify Request
// Bootstrap says Hello Verify Request to the Client.
Regards, Henry

If both the DTLS/Bootstrap and DTLS/Registration Update fail to work, then it is the network issue.

Just a detail but this is not a registration UPDATE but a REGISTER, anyway ...

My Bootstrap operation works fine at the DTLS handshake and Bootstrap.If it is the network issue then the DTLS handshake MUST fail at the Bootstrap operation.

This is not true...
We (you, boaks and me) see that the source IP Hello Verify Request is not good (expected <IP_ADDRESS> but was <IP_ADDRESS>). We all agree that's why it fails.
For bootstrap, all packet are well formed so of course it works.
As boaks says :

The handshake fails, because the Client Hello is sent to <IP_ADDRESS> but the Hello Verify Request as response is from <IP_ADDRESS>. Any compliant RFC6347 implementation will fail on the address change during the handshake.

So looking at received packet, we can say that at application level (Leshan/Californium/Scandium) all works as expected...
Also, it fails only in your environment. I was not able to reproduce and Leshan is largely used and nobody reports that kind of issue... (having bootstap server and DM server on different host is a very common use case)
So please stop repeat : "it works on bootstrap and not on register, so this is not a network issue"... boaks (Californium/Scandium main contributor) and me (Leshan main contributor) explain a lot why we think this is not a good argument and why there is strong hint this is a network issue.

Ummm I think it is the DTLS and Bootstrap/Device Management IP addresses logic may be the issue and which layer handle the swapping of the Bootstrap and Device Management IP addresses...You would know more than me.

I don't know what you are talking about ? you mean at client side ? The issue is not a client side as it sends packet to the right address ... I don't get your point...
If you want to move forward on this :

if you don't trust us, I can understand but just try to ask to someone you trust about network question.
please test with sandbox.
answer to question : Did you configure two network interfaces on the same host?

Hi Gatekeepers,

Did you configure two network interfaces on the same host? Yes I did initially. It is puzzling me a little bit here about two process runs in the memory using two seperate NICs and the DTLS Client Hello sends from the Client to the Device Management server an d the DTLS Verity Client Hello sends from the Bootstrap server.
After your last discussion with you I actually separated out the Bootstrap Application to run on the first host/physical server and the Devie Management Application to run on the second host/physical server. The first Register failed with the same issue but then the next 600 sec the Device performs Bootstrap again and the Register works.

All is kind of working on separate hosts making the development environment for both Bootstrap Application and Device Management Application slightly more complex.
As for the so-called network issue. I don't know enough about it until I can debug down to the Californium to see what really happen there.
I have my solution and we can close the issue. I move to implement the Leshan Client Demo to the Android and test out all the features like Bootstrap/Register/Register Update (my apology on this confusion) to see how Leshan Device Management handle IP Address changes together with Queue to work.
Thank for all your helping on solving the issue.
Regards, Henry Nguyễn

All is kind of working on separate hosts making the development environment for both Bootstrap Application and Device Management Application slightly more complex.

If you want to run that on the same host, you may be better off using different ports (different service => different port).
If two interfaces are configure, there may be more issues with that.
But one common is to open the UDP socket as "wildcard" (not bound to a specific local network interface). We have been faced similar issues with IPv6, where it's more common to have several network interfaces. To overcome that, it's required to bind the UDP socket to a specific network interface. But you need to test, if that helps. I'm, not common to leshan, so I don't know, how to start that listening on an specific local network interface. If you want just to test, if that would works, you may also use Californium/Plugtest-Server. Just run that on both network interfaces with
java -jar target/cf-plugtest-server-3.13.jar --interfaces-pattern "<IP_ADDRESS>"
java -jar target/cf-plugtest-server-3.13.jar --interfaces-pattern "<IP_ADDRESS>"

You will not be able to register successful, but you will see, if the dtls handshake works reliable.

If you want to run that on the same host, you may be better off using different ports (different service => different port).

I agree with that.
Demo can easily be launch with different port :
      -lp, --coap-port=<localPort>
                        Set the local CoAP port of the Server.
                        Default: COAP_PORT value from 'Californium.properties'
                          file or 5683 if absent
      -slp, --coaps-port=<secureLocalPort>
                        Set the secure local CoAP port of the Server.
                        Default: COAP_SECURE_PORT value from 'Californium.
                          properties' file or 5684 if absent

To overcome that, it's required to bind the UDP socket to a specific network interface. ...
... I don't know, how to start that listening on an specific local network interface

 -lh, --coap-host=<localAddress>
                        Set the local CoAP address of the Server.
                        Default: any local address.
 -slh, --coaps-host=<secureLocalAddress>
                        Set the secure local CoAP address of the Server.
                        Default: any local address.

To get all arguments :
  -h, --help            Display help information.


Add initial UAC bypass with RPC rule

Quick rule to detect UAC bypass using RPC.
One query on the inclusion of the byte version of the GUID. This does appear in the reference sample (at 0x140020EC0) and is referenced in the function that we expect test cases to hit. However, the reference is not direct because the code references a MIDL_STUB_DESC structure (at 0x140020D60) which then references the bytes in an RpcInterfaceInformation structure.
Advice on how to handle this appreciated - would it be worth moving the bytes to file scope?

Needs mandiant/capa-testfiles#144 merged to pass CI.

Thanks a lot for the sample, rule, and the details.
Unfortunately, we cannot fully express this with current capa features. The bytes feature is not supported at the file scope and the indirect reference is not caught. However, this rule looks good to me here.


fix(stream): add assertion to ensure pk indices consistency

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
As title.
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

You may need to rebase this branch. :)


Research Image  storage

Will store images on file system and link to image in DB.  Prototype File get routes are working for whisky controller to return image of whisky.


Redirect back to homepage when person cancels twitter signin

Fixes #271
I'm fairly certain this works. It was a bit hard for me to test, because when running locally, the twitter sign-in didn't work well. It would be good to have another person test this.

@alonpeer seems to work. I will deploy it and test it on production. Could not get worse then now. Sorry that this PR stayed open for so long.


fix chalk links

According to the CI, we should update more links.

You should update the links in this file (https://github.com/rust-lang/rustc-guide/blob/master/src/macro-expansion.md) from ext/tt to ext/mbe.

Ok, was only focused on chalk links... will fix those also.

Thanks! Looks good to me.


Add shortcuts to TabbedPanel & enhence JumpPosition

#1085
hello, I added some shortcuts for codeArea

- n for rename
- x for usage search
- d / double clicks for goto declaration
- tab for switching between java and smali
- ctrl + tab for swtching between current tab and the previous one

and some improvements

a line-wrap toggle for codeArea, when code lines is too long it's handy.
record caret position in JumpPosition, so the caret can be set rigth at the node not just the start of the line, e.g. when
click on a search result the caret goes to the matched place not the line head.

Wow. Thank you @LBJ-the-GOAT. Great work!

Wow. Thank you @LBJ-the-GOAT. Great work!

@LBJ-the-GOAT Thank you so much for implementing these shortcuts!

@LBJ-the-GOAT Thank you so much for implementing these shortcuts!


Merge MONDO:0008940 and MONDO:0013722[Merge]

Mondo term (ID and Label)
MONDO:0008940  endosteal sclerosis-cerebellar hypoplasia syndrome
Reason for deprecation
Per OMIM: ^ 213002
MOVED TO 614381
And endosteal sclerosis-cerebellar hypoplasia syndrome is now an alternate name for OMIM:614381
Term to be merged with
MONDO:0013722 hypomyelinating leukodystrophy 8 with or without oligodontia and-or hypogonadotropic hypogonadism
(Apologies if this is redundant, I did not see the merged OMIM number in the "OMIM slurp" ticket)
Your nano-attribution (ORCID)
If you don't have an ORCID, you can sign up for one here

sh run.sh owltools --use-catalog mondo-edit.obo  --obsolete-replace MONDO:0008940 MONDO:0013722 -o -f obo mondo-edit.obo


Added Helm chart release adapter for EAP XP 5

Description
Added Helm chart release adapter for EAP XP 5, also added build mode manipulation methods to other Helm chart release adapters.
Closes #179
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] Feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change
[ ] Chore (non-breaking change which doesn't affect codebase;
test, version modification, documentation, etc.)

Checklist

[x] Code contributed by me aligns with current project license: Apache 2.0
[x] Pull Request contains a description of the changes
[x] Pull Request does not include fixes for multiple issues/topics
[x] Code is self-descriptive and/or documented
[x] I have implemented unit tests to cover my changes
[x] I tested my code in OpenShift

Thanks for addressing my comments, @honza-kasik
Internal CI validation runs show identical failures between this PR branch and main, which will be tracked separately:

Infinispan issues are due to deprecated APIs in 8.5.0
Issues affecting the legacy RH-SSO Operator provisioning tooling (which is deprecated already in Intersmash) are most likely due to changes to the Operator channel names.
The remaining issues with WildFly provisioners, which in this case are used for XP deployments, are most likely not working due to the fact that a POM property is not set, neither propagated to OpenShift s2i builds in the XP 5 case.

With all that being said, I am approving your changes, which LGTM, and merging this PR into main.
Thanks again for adding features to Intersmash!


Building LXD 3.15 from tarball fails with dependency issue

Required information
Distribution: Ubuntu
Distribution version: 18.04.2
Issue description
Trying to build from tarball lead to the following error message:
root@:/tmp/lxd-3.15# go get -t -v -d ./...
github.com/cpuguy83/go-md2man (download)
package github.com/cpuguy83/go-md2man/v2/md2man: cannot find package "github.com/cpuguy83/go-md2man/v2/md2man" in any of:
        /usr/lib/go-1.10/src/github.com/cpuguy83/go-md2man/v2/md2man (from $GOROOT)
        /root/go/src/github.com/cpuguy83/go-md2man/v2/md2man (from $GOPATH)
github.com/russross/blackfriday (download)
package github.com/russross/blackfriday/v2: cannot find package "github.com/russross/blackfriday/v2" in any of:
        /usr/lib/go-1.10/src/github.com/russross/blackfriday/v2 (from $GOROOT)
        /root/go/src/github.com/russross/blackfriday/v2 (from $GOPATH)
Makefile:18: recipe for target 'default' failed
make: *** [default] Error 1

Steps to reproduce

Clear GO cache
Download and extract 3.15 tarball
make deps; export ... ; make

I'm not sure why your version of Go would fail to download those packages, but when building from the release tarball, it's usually best to see your GOPATH with what's in dist/src so that you're building with the exact versions we included. One way to do that is:
tar zxf lxd-3.15.tar.gz
cd lxd-3.15
mv dist _dist
export GOPATH=$(pwd)/_dist/
cd _dist/src/github.com/lxc/lxd
make deps
<follow instructions for export>
make

I'm pushing a branch which will simplify this process quite a bit too. So far mostly distributions have been dealing with our dist/ directory and clearly worked around the rough edges on their side :)

My fix effectively removes that awkward mv dist _dist and also changes the way we ship the C deps so that they don't get re-downloaded during make deps.

Wonderful, this is working like a treat !


Create our own helm chart for Prometheus Operator

We use Prometheus Operator helm chart from the charts repo which is going to be deprecated in November. More info about it is here: https://github.com/helm/charts#deprecation-timeline.
Now I think it makes sense to piece together the sub-components of Prometheus Operator and maintain a chart on our own.

I'm 99% sure someone else will pick up the maintenance of this helm chart, as it is widely used. Should we ask in https://github.com/coreos/prometheus-operator perhaps? I'd really like avoid maintaining such a large helm chart.

The maintainers of the project prometheus-operator and the helm chart prometheus-operator are different.

We can use the bitnami chart but it does not provide grafana we might need to add that manually.

The maintainers of the project prometheus-operator and the helm chart prometheus-operator are different.

Right now, yes, but I think eventually they should be at least governed by the same people. I think we should use the upstream chart until it's clear that it has been deprecated and will no longer be supported.
Right now only the stable helm repo is deprecated, not the charts itself (though some of them are abandoned).

Right now, yes, but I think eventually they should be at least governed by the same people. I think we should use the upstream chart until it's clear that it has been deprecated and will no longer be supported.

Most folks who maintain the project prometheus-operator don't use Helm for app management hence they don't feel comfortable in maintaining a helm chart themselves. But yes we should keep track of that issue.

I think we can close/rename this issue, as the chart will be now maintained in https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack, so we should migrate to it.

WIP migration path: https://github.com/prometheus-community/helm-charts/pull/119


Role assigned to scope not returned unless scope is specified

Describe the bug
When I assign a role to an SP at a given scope that role is not returned with the az role assignment list command.

Doesn't work in both CLI and Portal, works in REST API

Both
az role assignment list --assignee [objectId]
az role assignment list --assignee [appId]

Do not return roles that are assigned.

The portal does not show roles

But, if I add a scope, roles are returned:

The REST API does not require scope. Roles are returned without scope.
https://management.azure.com/subscriptions/{{subscriptionId}}/providers/Microsoft.Authorization/roleAssignments?api-version=2020-04-01-preview&$filter=assignedTo('aae06f9f-3c90-442b-bdc4-f688818132c6')

If I create a new SP and assign it the Tag Contributor role, then that roles is returned when using the CLI without scope.
To Reproduce

Create a new SP
az ad sp create-for-rbac --skip-assignment
Assign a role with scope
az role assignment create --assignee 32c6eeab-6338-4bdb-b21f-69836b2d99c4 --role "Tag Contributor" --scope /subscriptions/25fd0362-aa79-488b-b37b-d6e892009fdf/resourceGroups/aztagsync1
Query for roles
az role assignment list --assignee 32c6eeab-6338-4bdb-b21f-69836b2d99c4

Zero results are returned.
Expected behavior
Roles are returned without specifying a scope.
This is also true for the Azure portal, but I'm not sure where to report that bug.  If you know, Please let me know.
Environment summary

azure-cli                          2.8.0
WSL2
Additional context
I'm Microsoft, so ping me on Teams to diagnose further.
azsdke2e

add to S173

Possibly related to https://github.com/Azure/azure-cli/pull/13762. @qianwens, could you help take a look as well?

@jongio @jiasli , this behavior is by design that CLI will build a subscription level scope if there is no scope specified https://github.com/Azure/azure-cli/blob/dev/src/azure-cli/azure/cli/command_modules/role/custom.py#L181
You need to specify --all to list all the assignments under the current subscription.
I agree that this behavior is not intuitive for the customer, but fix this issue may cause a breaking change.

I have confirmed that using the --all switch returns the role:
Do we have tests in place to see if this will cause a breaking change to make --all the default?
I personally, an avid CLI user and my customer, a novice CLI user, could not figure this out.  I strongly suggest that we make --all the default to avoid these types of situations. In fact, I had to engage multiple on-call support teams, which involved many hours of their time, plus my time, plus the customer uncertainty of not knowing why the Tag update was working without (what we thought) was no roles assigned.
If we have tests in place, then we can try to make --all the default and see what breaks and then determine if it is worth it to make the change.
Thanks,
Jon

@qianwens, Nice analysis. In other words, by default CLI only lists assignments at the subscription level. With --all specified, all assignments at sub-resource levels are also listed.
I am able to reproduce with
> az role assignment create --assignee baf0218a-2f6b-44b0-9e3e-9118f8ad5979 --role "Tag Contributor" --scope /subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourceGroups/rg1

> az role assignment list --assignee baf0218a-2f6b-44b0-9e3e-9118f8ad5979
[]

> az role assignment list --assignee baf0218a-2f6b-44b0-9e3e-9118f8ad5979 --all
[
  {
    "canDelegate": null,
    "id": "/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourceGroups/rg1/providers/Microsoft.Authorization/roleAssignments/142298ff-27ac-41c5-868d-96accdb08801",
    "name": "142298ff-27ac-41c5-868d-96accdb08801",
    "principalId": "c726656d-b23f-4f6f-b01e-9db96e3f0c4f",
    "principalName": "http://azure-cli-2020-07-20-04-29-35",
    "principalType": "ServicePrincipal",
    "resourceGroup": "rg1",
    "roleDefinitionId": "/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/providers/Microsoft.Authorization/roleDefinitions/4a9ae827-6dc8-4573-8ac7-8239d42aa03f",
    "roleDefinitionName": "Tag Contributor",
    "scope": "/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/resourceGroups/rg1",
    "type": "Microsoft.Authorization/roleAssignments"
  }
]

This is also indicated in the help message:
> az role assignment list -h

Command
    az role assignment list : List role assignments.
        By default, only assignments scoped to subscription will be displayed. To view assignments
        scoped by resource or group, use `--all`.

Arguments
    --all                            : Show all assignments under the current subscription.

The lines responsible for this behavior are at
https://github.com/Azure/azure-cli/blob/4c28536a6db8c8e43b7182d0aaf202ac2b4ab777/src/azure-cli/azure/cli/command_modules/role/custom.py#L176-L182
https://github.com/Azure/azure-cli/blob/4c28536a6db8c8e43b7182d0aaf202ac2b4ab777/src/azure-cli/azure/cli/command_modules/role/custom.py#L511
However, I do think what @jongio suggests makes sense. Let's do some evaluation internally. + PM @achandmsft

Just started messing around with the Azure CLI for the first time and I noticed this weirdness;

When listing roles using az role assignment list --subscription xyz it gives me only the directly assigned roles, guess that makes sense
Azure docs tell me: you should use --include-inherited to view inherited assignments, okay sounds cool.
I run the query with --include-inherited and I see direct assignment and root-inherited assignments, but not assignments inherited via Management Groups ??? This behavior is very odd.

I'm happy the --all fixes it, but it's not intuitive at all...

az role assignment list by default only lists role assignments exactly at the subscription level.
The original issue @jongio faces is that resource-group-level role assignments (below subscription-level, such as on /subscriptions/25fd0362-aa79-488b-b37b-d6e892009fdf/resourceGroups/aztagsync1) are not listed by az role assignment list.
@Jelledb, your issue is that management-group-level role assignments (above subscription-level) are not listed by az role assignment list --include-inherited. Let's track this in https://github.com/Azure/azure-cli/issues/25078.

An excerpt from email: Role assigned to scope not returned unless scope is specified
The problem is that CLI doesn’t have a nice mapping of $filter=atScope(), which limits the assignment to the specified scope. See https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-list-rest
In CLI's implementation, --all only works at subscription level. --scope is bound to atScope().
When --all is provided, --resource-group or --scope is disallowed:
https://github.com/Azure/azure-cli/blob/38eaebb6936a32be13e2c4afba8e600ce9c91513/src/azure-cli/azure/cli/command_modules/role/custom.py#L221-L223
When --resource-group or --scope is provided, atScope() is forced:
https://github.com/Azure/azure-cli/blob/38eaebb6936a32be13e2c4afba8e600ce9c91513/src/azure-cli/azure/cli/command_modules/role/custom.py#L550-L551
In other words, even though --all can be used as the default and to list all sub-scope assignments under the subscription, it is not possible to list sub-scope assignments under a user-specified --scope, such as a resource group.
Proposal: Replace --all with the opposite, more general --at-scope, so that CLI is elegantly consistent with the REST API and covers the full functionality of the REST API.

Another issue: Even though principalId and atScope() are mutually exclusive, principalId and scope are not. Forcefully binding atScope() to scope also forbids using principalId with scope.
To work around this, CLI does a client-side filtering:
https://github.com/Azure/azure-cli/blob/38eaebb6936a32be13e2c4afba8e600ce9c91513/src/azure-cli/azure/cli/command_modules/role/custom.py#L576-L579
But the issue itself is caused by the bad design of --all and can be avoided from the very beginning.


Python: KernelArguments should be optional if there are no arguments

When there are no arguments the developer wants to pass in, the arguments parameter should be optional
This is what it looks like today
result = (await chat_completion.get_chat_message_contents(
    chat_history=history,
    settings=execution_settings,
    kernel=kernel,
    arguments=KernelArguments(),
))[0]

I should be able to write instead...
result = (await chat_completion.get_chat_message_contents(
    chat_history=history,
    settings=execution_settings,
    kernel=kernel,
))[0]

@matthewbolanos they are actually only needed when doing auto invoke function, calling, changing that to use a default when not supplied.


operator: Migrate Cilium Endpoint GC to hive

operator: Migrate Cilium Endpoint GC to hive

@pippolo84 FYI

/test

The conflicts with the main branch is due to this recently merged PR: https://github.com/cilium/cilium/pull/28166
@alan-kut I solved the conflicts removing the legacy metrics in legacy.go and fixing the test in operator/api/metrics to use a test-only metric. To do that, I had to change your last commit, here a preview: https://github.com/cilium/cilium/compare/main...pippolo84:cilium:pr/pippolo84/operator-endpointgc-metrics?expand=1
Is it ok for you if I force-push this branch with these changes?

It's ok, go ahead

It's ok, go ahead

Done. Let me know your thoughts about this, and then I'd say we're good to go :+1:

It's ok, go ahead

Done. Let me know your thoughts about this, and then I'd say we're good to go 👍

Everything looks good to me

Pushed again just to address this comment setting a low timeout.

/test

I think the Conformance Runtime failure is related: https://github.com/cilium/cilium/actions/runs/6418834513/job/17427580426#step:16:276
@alan-kut could you please take a look?

Done. I removed the wait for all 8 CEPs to be in the Store. There may be a race in which the CEPs are deleted before we can check all of them were created.

/test

Integration Tests (ci-integration): github.com/cilium/cilium/operator/pkg/lbipam  test failed. It's a flake.

The other tests failure logs don't show me any good reason why they failed.


Museeks 1.0

Ok, let's talk about serious business now 😝
Museeks 1.0
This document is a draft, imagine the best codebase possible, all the features you'd like, best back-end/front-end implementation, everything... and let's discuss it here. I'm locking the discussion for now to avoid some pollution, and let's talk about it on specific issues/Gitter.
If the whole codebase has to change to have a nice software, I don't see any problem (Whole app IPC Q/A for example, external binaries... Everything can be discussed)
Put a +1 on the first post of any issue if you'd like to see it included.
Disclaimer
The first goal of Museeks is to focus on music, not tons add tons of heavy add-ons.
The focus of Museeks are:

Simplicity
Elegance
Decent features

What we (understand "I") don't want are:

Tons of features slowing down things
Ultra-specific features you can find on your favourite player

Essential features
These features must be done before Museeks 1.0 is released.

Reorderable columns in TracksList #62
Reorderable playlists #175
Installers #100

Great to have
Almost essential features, but not as important. They'd better be done to have a serious piece of software. They may need serious specifications though.

Use the Web Audio API instead of the Audio API #128
Equalizer #127
Tracks transitions #31

Good to have
Would be good to have them, but they are not "absolutely" mandatory.

FLAC support #53
Translations #137
Better system integration on Ubuntu/Gnome #93
Make it possible to associate supported file types with museeks #154
Support for playing files without adding to the library #155

Bonus
The development will not be focused on theses issues, and/or these issues need discussions first, but they remain good ideas.

Editable id3 #101
Smart playlist #214
m3u support #146
External stream support #217
Minimizable windows to tray #219

To be discussed

...

2.0 ?

...

I'd like to discuss some UI polish, I think current UI does it's job, but I kinda miss some space.
So, request from me:

Update UI to make it more modern and spacious. /cc @Suriteka - ideas?

Reorderable columns in TracksList #62

Does that includes the ability to sort by clicking on them? If not, we should add it.

Use the Web Audio API instead of the Audio API #128

I think this is needed for 1.0. Doing this change in 1.x can be risky. Also, it is kind of prerequisite for #114, in which I'm personally really interested.

Better system integration on Ubuntu/Gnome #93

Kind of stalled on work needed to be done in mpris-service module. /cc @emersion ?
I doubt we want to interact with dbus directly.
But we can at least add Tray icon.

Installers #100

I thought this is for 0.8, but yeah, that would help people to get up and running anyway, I'm all in.


Enable the vulkan dGPU render

Check the dGPU through whehter has local memory.
Tracked-On: OAM-118065

Program name for this pr is not compatable with other dependent prs, for more details please check tracked_on

Program name for this pr is not compatable with other dependent prs, for more details please check tracked_on


I have too many style tags in my head tag

Steps to reproduce
Link to live example: https://ocasoyali.com/
Steps:

Go to link.
Open DevTools
Look at the head tag.

Current behavior
There are many style tags on production mode.

Expected behavior
According to what I researched, this behavior should only occur in development mode. But for some reason I don't know, my project is also in production mode.
Context
It would actually be nice if it looked like this.

Your environment

npx @mui/envinfo
Chrome 126.0.6478.127
System:
    OS: Windows 10 10.0.19045
  Binaries:
    Node: 21.1.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.2.5 - ~\AppData\Roaming\npm\npm.CMD
    pnpm: Not Found
  Browsers:
    Chrome: 126.0.6478.127
    Edge: Chromium (126.0.2592.81)
  npmPackages:
    @emotion/react: ^11.11.4 => 11.11.4
    @emotion/styled: ^11.11.5 => 11.11.5
    @mui/base:  5.0.0-beta.40
    @mui/core-downloads-tracker:  5.15.15
    @mui/icons-material: ^5.15.14 => 5.15.15
    @mui/material: ^5.15.14 => 5.15.15
    @mui/private-theming:  5.15.14
    @mui/styled-engine:  5.15.14
    @mui/styled-engine-sc: ^6.0.0-alpha.18 => 6.0.0-alpha.18
    @mui/system:  5.15.15
    @mui/types:  7.2.14
    @mui/utils:  5.15.14
    @types/react:  18.3.1
    react: ^18 => 18.3.1
    react-dom: ^18 => 18.3.1
    styled-components: ^6.1.8 => 6.1.8

Search keywords: style tags

https://mui.com/material-ui/integrations/nextjs/#pages-router
After following the steps in this link the problem was fixed.


Shift to 4.7 candidate url instead nightly

Now 4.7 is available as candidate better to shift from nightly to
candidate now.

/retest


Refactor/update deps

:tada: This PR is included in version 1.10.1-rc.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[bug]: A dependency doesn't support Next 15 or React 19

Describe the bug
https://github.com/radix-ui/icons/issues/190
Affected component/components
toast,radio-group,pagination,navigation-menu,drowdown-menu,dialog,command,
How to reproduce

upgrade to Next 15
run npm install

For Codesandbox link, run npm add @radix-ui/react-icons
Codesandbox/StackBlitz link
https://codesandbox.io/p/devbox/busy-breeze-go8s7s
Logs
npm error Could not resolve dependency:
npm error peer<EMAIL_ADDRESS>|| ^17.x || ^18.x" from<EMAIL_ADDRESS>npm error node_modules/@radix-ui/react-icons
npm error<EMAIL_ADDRESS>from the root project

System Info
Linux subsystem for Windows, Archlimux

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

@jefer94 Does the following help? https://ui.shadcn.com/docs/react-19#using-npm

@jefer94 We now have a new release of @radix-ui/react-icons which should've fixed this issue. Please reopen if not. thank you.

Running force install is a terrible idea, even knowing that this installation works, I'm installing that in production, and you will produce a lot of issues in production environment in future by being lazy


Wallpaper should be set to scale

Switching from the original low resolution to 4K, the image should scale.
Low-ish priority issue.

This has already been fixed in the updated version of the Lumina port (missing the auto-update of the background on screen change).
In the meantime, you can quickly bypass this issue by manually triggering a wallpaper refresh via the wallpaper settings (add or remove an item from the list and then save the changes).


Zoom Issue

Hi guys,
Would you mind checking this bug?
http://screencast.com/t/quy3wkpbHiv
Have you experienced this issue before?
Any comment and help from you is very much appreciated.
Thanks.

The current demo doesn't let you zoom out to bigger than the original image size?

Were you able to check the screencast that I attached in my previous comment?

I was, but a video is not very useful to figure out the problem.
If you look at the jquery-cropbox demo, that problem is not there, at least I couldn't get it to show up.
Please look at the bug reporting section at the bottom of the readme to open useful issues.
Summarizing: Create a MINIMAL jsfiddle that exhibits the problem and I'll look into it. You should not copy and paste your entire application and expect me to debug it for you, instead just provide me with a very simple example that exhibits a problem with jquery.cropbox and not with your app.


Add ARO as a K8S/container option

why not to add Azure Redhat OpenShift  as a K8S/container option ?
Thank you,
Steve

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

ID: 04491fb9-6ca7-c21a-5372-a966c8ee72be
Version Independent ID: 97fa3784-c1b4-0097-1ec9-223edaa768bc
Content: Comparing Container Apps with other Azure container options
Content Source: articles/container-apps/compare-options.md
Service: app-service
GitHub Login: @jeffhollan
Microsoft Alias: jehollan

Thanks for the feedback! I have assigned the issue to the content author to evaluate and update this doc as appropriate.

Added to docs. Thanks for the feedback - it should roll out in next 24 hours. #please-close


Setter is updating property when styles are being detached

Repro
In ControlCatalog, MainWindow.xaml:

Remove Icon="..." (line 5).
Add the following markup at the start of the Window body:

  <Window.Styles>
    <Style Selector="Window">
      <Setter Property="Icon" Value="/Assets/test_icon.ico" />
    </Style>
  </Window.Styles>

Then run.
Now, when closing control catalog, it will throw a NullReferenceException (which shows other possible issue: Window.Icon cannot be set to null).
The exception is thrown from a property changed handler, which I think is invoked when styles are being detached.

Removing the style when the window is closed is correct behavior I think. The problem is that Window.Icon cannot be set to null.


[bug] Test runner crashes

Describe the bug
When I try to execute test-storybook, I get this error:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Jest: Got error running globalSetup -<EMAIL_ADDRESS>reason: Package subpath './lib/adapters/http' is not defined by "exports" in /Users/me/my-project/node_modules/axios/package.json

System
Storybook Environment Info:

  System:
    OS: macOS 14.0
    CPU: (8) arm64 Apple M1
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.13.0 - ~/.asdf/installs/nodejs/18.13.0/bin/node
    Yarn: 3.6.4 - ~/my-project/node_modules/.bin/yarn <----- active
    npm: 8.19.3 - ~/.asdf/plugins/nodejs/shims/npm
    pnpm: 8.6.9 - ~/.config/local/share/pnpm/pnpm
  Browsers:
    Chrome: 119.0.6045.159
    Safari: 17.0
  npmPackages:
    @storybook/addon-a11y: ^7.5.3 => 7.5.3
    @storybook/addon-essentials: ^7.0.9 => 7.5.3
    @storybook/addon-interactions: ^7.0.23 => 7.5.3
    @storybook/addon-toolbars: ^7.5.3 => 7.5.3
    @storybook/core-common: ^7.0.9 => 7.0.24
    @storybook/core-server: ^7.0.9 => 7.5.3
    @storybook/jest: ^0.1.0 => 0.1.0
    @storybook/react-vite: ^7.0.9 => 7.0.26
    @storybook/test-runner: ^0.15.1 => 0.15.1
    @storybook/testing-library: ^0.2.0 => 0.2.0

@ganlhi Getting the same issue after bumping axios from 0.25.0 to 1.6.1. Have you come across any solution?

I updated @storybook/test-runner to version 0.16.0, and this seems to be fixed!

Great to know! Thanks for using the test-runner!


Do not load everything in memory for bookkeeping

This adds some more data in sqlite to keep memory usage down and reduce time-to-start-syncing considerably.

Converting to draft because we should persist the gaps as soon as we detect a gap.


Utilize lock-free queue for worker thread pool

I think it would be far more efficient to utilize a lock-free queue (e.g. using compare-and-swap) to hand work off to the worker threads rather than using a mutex. Has this even been considered and/or benchmarked against a lock-free queue for applications that are heavily utilizing the worker thread pool for blocking file I/O, etc.?
mirror of https://github.com/joyent/libuv/issues/1598

Atomic operations may be helpful for uv_async_send() (avoiding a system call when the target thread is awake) but workers in the thread pool should suspend when there is no work.  That means you're going to need some kind of synchronizing primitive to sleep on, like the current mutex + condition variable.
A lock-free list may or may not help as a fast path but you'd have to convince me with numbers. :-)

I'm happy to replace the current list with a lock-free list in a fork and run some benchmarks.  I agree the threads should sleep when not busy; we can still have a wait condition when the queue is empty, but when the queue is not empty the wait condition can be skipped.  The condition can be signaled every time an entry is added to the queue.
I agree this is more for a fast path when the queue is never empty.  For never-ending blocking I/O requests, I am confident (but again am happy to provide results to be certain) CAS would be far more performant than the syscalls on the mutex.  I'll report results soon.

Closing as this is not really an issue. Please open a PR if you manage to implement what you proposed and have some numbers to share! :-)


support multi bank mappers

output file has to match input, even if banks are kept as data

[x] asm6
[ ] ca65
[ ] nesasm

Banking still does not work. The two problems: this substring "a:" is unnecessarily added, and [ISC, oper,X] is listed in the output file. However, this illegal opcode is not usable with asm6f.
Using the latest release of asm6f and tested this with the smb3 pal rom.


Fatal error: Uncaught Error: Class "OpenSwoole\Core\Psr\Middleware\StackHandler" not found when trying to use psr-7 server with openswoole 22

I'm experimenting on updating an app to openswoole 22, by using its psr-7 support.
I have set-up a very simple start script, called openswoole-worker.php, which is basically the same example in the docs:
<?php

declare(strict_types=1);

use OpenSwoole\Core\Psr\Middleware\StackHandler;
use OpenSwoole\Core\Psr\Response;
use OpenSwoole\HTTP\Server;
use Psr\Http\Message\ResponseInterface;
use Psr\Http\Message\ServerRequestInterface;
use Psr\Http\Server\MiddlewareInterface;
use Psr\Http\Server\RequestHandlerInterface;

require __DIR__ . '/../vendor/autoload.php';

$server = new Server('<IP_ADDRESS>', 8080);
$server->on('start', function (Server $server) {
    echo "OpenSwoole http server is started at http://<IP_ADDRESS>:8080
";
});

$stack = (new StackHandler())
    ->add(new class implements MiddlewareInterface
    {
        public function process(ServerRequestInterface $request, RequestHandlerInterface $handler): ResponseInterface
        {
            return (new Response('aaaa'))->withHeader('x-a', '1234');
        }
    });

$server->setHandler($stack);

$server->start();

When I try to run it via php openswoole-worker.php, it throws the next error:
Fatal error: Uncaught Error: Class "OpenSwoole\Core\Psr\Middleware\StackHandler" not found in /home/app/openswoole-worker.php:21
Stack trace:
#0 {main}
  thrown in /home/app/openswoole-worker.php on line 21

I have also tried using my own handler, instead of the StackHandler, but then it fails to find another class:
Invalid callback \OpenSwoole\Core\Helper::setHandler, class "\OpenSwoole\Core\Helper" not found.
I have also noticed that I don't get a proper autocompletion for neither of those classes even when my project depends on "openswoole/ide-helper": "~22.0.1", but since those are basically stubs, I thought the definition would just not be up to date yet.
Is there anything that needs tobe done for openswoole 22 to support PSR-7?

Ok, I just found this article https://openswoole.com/docs/psr, and realized there's actually a composer package required for psr-7 compatibility. I thought it would be built-in, for dinner reason.
I'll close this for now. Sorry for the noise!


Remove topojson from deps

precalc everything and provide a json file for the person load.

do not include json files in the published app, expect user to copy over json and fetch/import themselves


FOUC due to ReactQueryDevtools?

It looks like font is changing during hydration, which seems to be coming from
https://github.com/hi-ogawa/vite-plugins/blob/fd3c5c53745d352e80126c302ae2b062d67ba55a/packages/demo/src/utils/react-query-utils.tsx#L39

This looks fine now.