UART will not pair when "disable periodic reports" is selected

UPDATE: 2022-05-01 still testing may not be 100% accurate.
I am using v<IP_ADDRESS> with a Hubitat Hub.  The hub will pair to zha1.2 and zll profile devices.  My Zigbee board is a "generic" cc2530.  I am using these boards with my Hub (but different firmware on the board) in 3 other locations and have been working for > 1 year.
I have configured the firmware to use a UART at 9600 on pins 2 and 3.  No other capabilities are programmed.

If I set the periodic report to "disable periodic reports" (i.e. default periodic reports is checked and set to 0), the board will not pair with my Hub.  Tried numerous times both with power on and with a reset\ input (pushbutton).

If I leave periodic reports at some number (I've tried 60 and 65500) the board will pair with my hub and work.  There is an issue however.   Periodically the Hub will receive messages with the payload split between two messages in quick succession.  In the below the two messages are only 5m apart (I've seen a smaller time delta).  My hub driver does nothing but log the raw message.

In the expert tab the only box checked is  "set default reporting interval[s]"
My payload is sent from an Arduino the message terminator is ETX.  I have not tried with a different terminator.  That will be next.
I don't know what else I can provide that will help.  I've tested various combinations many times and with v<IP_ADDRESS> and v<IP_ADDRESS> all with the with the same result.
Thanks
John
Log showing the periodic split payload
`2022-04-30 06:04:32.015 pm info Raw Description  read attr - raw: F376010014140E00410601061A150404, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 0601061A150404
2022-04-30 06:09:42.485 pm info Raw Description  read attr - raw: F376010014140E004106010619160504, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value:<PHONE_NUMBER>0504
see these log lines:
2022-04-30 06:14:52.951 pm info Raw Description  read attr - raw: F3760100140A0E00410104, dni: F376, endpoint: 01, cluster: 0014, size: 0A, attrId: 000E, encoding: 41, command: 0A, value: 0104
2022-04-30 06:14:52.956 pm info Raw Description  read attr - raw: F376010014100E00410401061915, dni: F376, endpoint: 01, cluster: 0014, size: 10, attrId: 000E, encoding: 41, command: 0A, value:<PHONE_NUMBER>
2022-04-30 06:20:03.346 pm info Raw Description  read attr - raw: F376010014140E00410601061A150004, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 0601061A150004
2022-04-30 06:25:13.601 pm info Raw Description  read attr - raw: F376010014140E00410601061A150904, dni: F376, endpoint: 01, cluster: 0014, size: 14, attrId: 000E, encoding: 41, command: 0A, value: 0601061A150904
`

Hello,
I've tested this issue with Z2M and I cannot repeat it. Unfortunately, I do not have this hub for testing.

Thank you.   I believe I've solved the lack of pairing issue.  Physically it was difficult to create the 2seconds on three times.  I made some hardware modifications and I can now pair with the 2 sec X 3 procedure.   Still it was odd the firmware with report times was able to pair on the initial power up and not needed the 2sec x 3 procedure.
However I am still getting partial messages periodically.  My messages are initiated every 5 minutes.  When I last reflashed the cc2530 the messages were correct for 6 hours then started to send periodic partial messages. (see attached, oldest is on the bottom).  I increased the Baud rate from 9600 to 38400 with not change in the short messages.  My message source is an Arduino µP with no interrupts so I expect the message to be the same everytime. Any thoughts on what I might test to find a solution?
Thanks
John

@JonRobert I do not know the reason of a wrong message length. Probably, low signal strength and LQI.

Thank you for looking into this.  I will keep testing. Next test will be to change the power supply and add filtering.
I doubt it's due to low signal as the board is only 3 meters from the hub with nothing in between.  And the BME280 implementation does not have any dropped messages.


No "Annotation tool" can be selected on the Processing step of the Create event page.

I followed the installation instructions to install this tools for my opencast-7-allinone instance, and add the annotation configuration in the /etc/opencast/workflows/fast.xml just after the publish-engage operation:
<operation
  id="publish-configure"
  exception-handler-workflow="partial-error"
  description="Publish to preview publication channel">
  <configurations>
    <configuration key="source-tags">preview</configuration>
    <configuration key="channel-id">annotation</configuration>
    <configuration key="url-pattern">http://localhost:8080/annotation-tool/index.html?id=${event_id}</configuration>
  </configurations>
</operation>

And I systemctl restart opencast. Then manually add an event, at the processing step, there is still no "Annotation tool" can be selected, just as the screenshot below:

I still finished the event creation, and after Opencast successfully finished processing the event,  Then I tried to forcely open the annotation tool of the event. The page stuck as the screenshot below:

My version: Opencast 7.2.0 - 8bb9948
BTW:  the publication.channel config file for 7.2 is listproviers/publication.channels.properties. The config format is a little different. I appended the annotation tool the way as others:
api={"label":"EVENTS.EVENTS.DETAILS.PUBLICATIONS.EXTERNAL_API", "order":1}
oaipmh-default={"label":"Default OAI-PMH Repository", "order":2}
engage-player={"icon":"img/engage_2x.png", "order":3}
youtube={"icon":"img/youtube_2x.png", "order":4}
engage-player={"icon":"img/engage_2x.png", "order":5}
annotation={"label":"Annotation Tool", "order":6}

The fact that there is no option for the Annotation Tool in the configuration panel is totally expected, from what you told me. It does not appear by you just adding the publish-configure-option. If you want something like that, you can add the corresponding HTML to the configuration_panel tag of your workflow. See here for more details on that.
Next, the console output you posted shows a 500 error code. That's a server error. Do you see anything interesting in the Opencast logs?

@JulianKniephoff Now I truncate /var/log/opencast/opencast.log  file and run systemctl restart opencast. The page shows no 500 error but a few 404 errors as the screenshot below:

I then check there is nothing yet in my /var/log/opencast/opencast.log  file

That particular error message occurs when the tool can't get the media package from Opencast's search service. Did you publish your event to Engage? Or does your user not have read permissions on it?

@JulianKniephoff Thank you for your tip. Now I insteadly use the "Process upon upload and schedule" workflow ( I added annotation operation config in the schedule-and-upload.xml), and checked publishToEngage, and granted "manage annotations" & "annotate" permissions to all roles. Now, I can see the annotation tool as the screenshot below:

When I click the green play button, the stucking page shows again as below:

The 2 404 errors can be neglected, it's due to lack of interface translation files. But when I right click the 500 error link (that is /extended-annotations/users) and open in the new tab, it shows up 404.
I deploy a Nginx as the reverse proxy, so I replace the localhost:8080 with the nginx server name in the section of annotation in the workflow XML file. If I don't replace, the annotation page will go to localhost:8080/****, which is not accessible.

Is there anything in the Opencast logs? A status code of 500 indicates a server-side error.

@JulianKniephoff There is nothing in the /var/log/opencast/opencast.log nor in /var/log/nginx/error.log, for I use Nginx reverse proxy.

I'm not sure why this would lead to a 500 (I would expect a 403), but another common trap is to not enable access to the annotation tool APIs in the security/mh_default_org.xml file (or the corresponding file of your organization, should you run a multi tenant setup). At least ROLE_USER needs to be able to at least GET, POST, PUT and DELETE stuff under /extended-annotations.
If that doesn't help, it could be useful to see the full request and response. You should be able to get that from the "Network" tab of your development tools in the browser.

@JulianKniephoff I don't use multi tenant setup. There is no

/extended-annotations

settings in my

security/mh_default_org.xml

file. So I added these 4 lines under the /annotation section:
    <!-- Enable anonymous access to the annotation and the series endpoints -->
    <sec:intercept-url pattern="/series/**" method="GET" access="ROLE_ANONYMOUS, ROLE_CAPTURE_AGENT" />
    <sec:intercept-url pattern="/annotation/**" method="GET" access="ROLE_ANONYMOUS" />
    <sec:intercept-url pattern="/annotation/**" method="PUT" access="ROLE_ANONYMOUS" />
    <sec:intercept-url pattern="/extended-annotations/**" method="PUT" access="ROLE_ADMIN, ROLE_USER, ROLE_ANONYMOUS" />
    <sec:intercept-url pattern="/extended-annotations/**" method="GET" access="ROLE_ADMIN, ROLE_USER, ROLE_ANONYMOUS" />
    <sec:intercept-url pattern="/extended-annotations/**" method="POST" access="ROLE_ADMIN, ROLE_USER, ROLE_ANONYMOUS" />
    <sec:intercept-url pattern="/extended-annotations/**" method="DELETE" access="ROLE_ADMIN, ROLE_USER, ROLE_ANONYMOUS" />

Is it right? After systemctl restart opencast, the error still exists.

@JulianKniephoff I followed your instruction, under the tab of Network, it's a xhr 500 error,

and furtherly in the tab of Sources, the error occured on this line: xhr.send( ( s.hasContent && s.data ) || null );

Could you check whether the Annotation Tool -impl bundle is actually running in your Karaf container? And maybe restart it?

Also: I would like to keep the issue tracker somewhat clean. We are far away from the original issue now. Could you please create a new one if this is still a problem for you?

@JulianKniephoff Could you pls tell me how to checkAnnotation Tool -impl bundle is actually running in my Karaf container? I googled nothing relevant.

In the Karaf console you can type bundle:list. It should show up in the resulting list.

I have tried to install opencast 9.9, getting

URI:
/

404

Not Found

org.ops4j.pax.web.service.spi.model.ServletModel-445

Can anyone help me

@uday5650 this is really not the place for general Opencast installation support. You might want to check any of these channels for that.


fix: bucket reponse should be typed as string array

What kind of change does this PR introduce?
Bug fix https://github.com/supabase/cli/issues/1674
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.03%) to 58.151%

Files with Coverage Reduction
New Missed Lines
%

internal/gen/keys/keys.go
5
12.31%

Totals

Change from base Build<PHONE_NUMBER>:
-0.03%

Covered Lines:
5775

Relevant Lines:
9931

💛  - Coveralls


Guide for linux myst cli users

A guide on how to use myst cli as a linux user.
Includes:

Install instructions
Setup and usage instructions for the myst cli

Updates: https://github.com/mysteriumnetwork/node/issues/2773

We have easy installation way for Ubuntu/Debian.
sudo add-apt-repository ppa:mysteriumnetwork/node
sudo apt-get update
sudo apt install myst

So, if you address mine and mantas comments, feel free to merge. After new CLI will be finished, you will simply update this description.


"Have you considered using Tensor Cores for acceleration?"

"Have you considered using Tensor Cores for acceleration?"

Considering the hardware characteristics, using the four-step algorithm is a good choice.


[Minor] Make Constants final

What changes were proposed in this pull request?

Make Constants class final.
Make public static fields in Constants final.
Make default constructor of Constants private.

Why are the changes needed?
Code quality.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing CI.

Codecov Report

Merging #501 (351e684) into master (9646a6f) will decrease coverage by 0.51%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #501      +/-   ##
============================================
- Coverage     59.34%   58.83%   -0.51%
+ Complexity     1747     1528     -219
============================================
  Files           206      184      -22
  Lines         11508     9668    -1840
  Branches       1030      871     -159
============================================
- Hits           6829     5688    -1141
+ Misses         4274     3618     -656
+ Partials        405      362      -43

Impacted Files
Coverage Δ

...java/org/apache/uniffle/common/util/Constants.java
0.00% <0.00%> (ø)

...storage/handler/impl/DataSkippableReadHandler.java
83.78% <0.00%> (-2.71%)
:arrow_down:

...pache/hadoop/mapreduce/task/reduce/RssShuffle.java

...che/spark/shuffle/writer/BufferManagerOptions.java

...pache/hadoop/mapreduce/task/reduce/RssFetcher.java

...e/spark/shuffle/reader/RssShuffleDataIterator.java

...apache/hadoop/mapreduce/v2/app/RssMRAppMaster.java

...org/apache/spark/shuffle/RssSparkShuffleUtils.java

...pache/spark/shuffle/writer/WriteBufferManager.java

...preduce/task/reduce/RssRemoteMergeManagerImpl.java

... and 14 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks @zuston for the review.


Tweak loadgoa module to handle plant goa data file

I still need to run tests but just wanted a quick review of the design update to the module to load goa annotations.

See: #99

@PhillipsOwen That is what I already did in the pull request mentioned above. #99


Can't import Bestiary - Sea Hag

Can't import statblock:
Sea Hag      CR 4
XP 1,200
Male sea hag (Pathfinder RPG Bestiary 243)
CE Medium monstrous humanoid (aquatic)
Init +3; Senses darkvision 60 ft.; Perception +11
Aura horrific appearance (60 ft., DC 14)
Defense
AC 16, touch 13, flat-footed 13 (+3 Dex, +3 natural)
hp 38 (4d10+16)
Fort +5, Ref +7, Will +5
SR 15
Offense
Speed 30 ft., swim 40 ft.
Melee 2 claws +8 (1d6+4)
Special Attacks evil eye
Statistics
Str 19, Dex 16, Con 18, Int 12, Wis 13, Cha 15
Base Atk +4; CMB +8; CMD 21
Feats Skill Focus (Bluff), Skill Focus (Perception)
Skills Bluff +9, Knowledge (Enter Choice) +5, Perception +11, Stealth +10, Swim +19
Languages Common, Giant
SQ amphibious
Ecology
Environment any aquatic
Organization solitary or coven (3 hags of any kind)
Treasure standard
Special Abilities
Amphibious (Ex) You can survive indefinitely on land.
Darkvision (60 feet) You can see in the dark (black and white only).
Evil Eye (DC 14) (Su) Gaze staggers and curses single target within 30 ft.
Horrific Appearance (DC 14) (Su) Appearance weaknens, inflicting 1d6 Str damagae (Fort neg.)
Spell Resistance (15) You have Spell Resistance.
Swim (40 feet) You have a Swim speed.

I got this statblock from Hero Lab.  You might benefit from retesting with aonprd.com.  Sometimes Hero Lab truncates some of the descriptions.
I used the latest Pathfinder system and your latest module to test this.


Jagged Edges

Hi! Really enjoying this plugin, started playing around with it as an outage calendar to be used in conjunction with worldPing.
Noticed that when increasing the cell radius, the edges get pretty jagged - but ironically, shape-rendering: crispedges; makes it jagged:

https://github.com/NeoCat/grafana-cal-heatmap-panel/blob/master/src/bower_components/cal-heatmap/cal-heatmap.css#L19
Before submitted a PR to remove it, is there another scenario where that's required? When configured to be squares (cell radius 0), it seemed to make no difference.

This is from an default option of cal-heatmap.js which has been specified at the very first version committed to GitHub, so I couldn't track down why this is added.
In my opinion, it is okey to be overridden by this plugin if it won't obviously break something.


Streaming from OBS to NMS via rtmp, after several hours OBS tries to re-connect & publish - error "Already has a stream"

I'm not sure if maybe my connection is a little flakey or if OBS is deciding to republish the stream after a set amount of time (seemingly around 4 hours each time) but NMS doesn't seem to be handling it correctly.
The stream if being viewed or relayed, simply stops at the point and the old session doesn't die, so when it tries to create a new session with the same stream path, it fails with "Already has a stream"
Any ideas how I can get around this issue, or some explanation as to what is going on?

I faced the same problem today. I used mobile phone to publish stream, after a while, maybe because of weak connection, it lost the stream and try to re-connect. But server rejected it with "Already has a stream"

I faced the same problem today. I used mobile phone to publish stream, after a while, maybe because of weak connection, it lost the stream and try to re-connect. But server rejected it with "Already has a stream"

+1.
Any luck on this issue?

Same here..

same issue for me also


Fixes #39: You can use minishift start

--internal-registry=true --router=true

From travis:
Checking gofmt...
--- /dev/fd/63	2016-08-24 09:24:52.120691328 +0000
+++ /dev/fd/62	2016-08-24 09:24:52.120691328 +0000
@@ -0,0 +1,2 @@
+cmd/minikube/cmd/start.go
+pkg/minikube/cluster/cluster.go
make: *** [test] Error 1

Please make sure you run gofmt on all files. If you're using an IDE then you should set this up on save (go-vim is awesome for this btw).
Also I think you'll need to run make gendocs to ensure docs are up to date.

With #52 this means that it the created registry works ootb.

Awesome thanks!


SSO using this approach

How would SSO work in this scenario.  If PVA wanted to authenticate the user, would the SSO context flow correctly from the end-user?  In the example above, the "user" is the bot calling PVA using direct-line.  Just not sure if SSO is supported correctly in the example above.

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

ID: e7a1322f-8123-d498-1a5c-431ad816c389
Version Independent ID: a5f4b3d4-2a1a-edcc-c9fa-b3e2154e65ff
Content: Use a Microsoft Bot Framework bot with Power Virtual Agents - Power Virtual Agents
Content Source: power-virtual-agents/advanced-use-dispatcher.md
Service: dynamics-365-ai
GitHub Login: @pawant-ms
Microsoft Alias: iawilt

// Adding @Bo<EMAIL_ADDRESS>Our implementation of SSO (releasing in a few weeks) will be supporting Skills as well. @Bo<EMAIL_ADDRESS>can deep dive into it if you like.
Thank you,
Pawan
From: robertwood62<EMAIL_ADDRESS>Sent: Friday, May 15, 2020 11:29 AM
To: MicrosoftDocs/power-platform<EMAIL_ADDRESS>Cc: Pawan Taparia<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [MicrosoftDocs/power-platform] SSO using this approach (#226)
How would SSO work in this scenario. If PVA wanted to authenticate the user, would the SSO context flow correctly from the end-user? In the example above, the "user" is the bot calling PVA using direct-line. Just not sure if SSO is supported correctly in the example above.

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

ID: e7a1322f-8123-d498-1a5c-431ad816c389
Version Independent ID: a5f4b3d4-2a1a-edcc-c9fa-b3e2154e65ff
Content: Use a Microsoft Bot Framework bot with Power Virtual Agents - Power Virtual Agentshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpower-virtual-agents%2Fadvanced-use-dispatcher&data=02|01|pawan.taparia%40microsoft.com|8bbf81228604454a518f08d7f8fdc99d|72f988bf86f141af91ab2d7cd011db47|1|0|637251641211329552&sdata=tUl6vJ9UaDyqPStmadtz6eX27%2F8RswQw9CLmBK6gzIM%3D&reserved=0
Content Source: power-virtual-agents/advanced-use-dispatcher.mdhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpower-platform%2Fblob%2Fmaster%2Fpower-virtual-agents%2Fadvanced-use-dispatcher.md&data=02|01|pawan.taparia%40microsoft.com|8bbf81228604454a518f08d7f8fdc99d|72f988bf86f141af91ab2d7cd011db47|1|0|637251641211339547&sdata=aUq8eAD58VRPc55mo%2BQFE%2BQ6oiXO5%2FxLAvUCnrHhx1U%3D&reserved=0
Service: dynamics-365-ai
GitHub Login: @pawant-mshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpawant-ms&data=02|01|pawan.taparia%40microsoft.com|8bbf81228604454a518f08d7f8fdc99d|72f988bf86f141af91ab2d7cd011db47|1|0|637251641211349542&sdata=zX%2Fq83bePaOmBXFcaYNfIkgPqHKFQJun%2BVLBvOrfoH4%3D&reserved=0
Microsoft Alias: iawilt

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpower-platform%2Fissues%2F226&data=02|01|pawan.taparia%40microsoft.com|8bbf81228604454a518f08d7f8fdc99d|72f988bf86f141af91ab2d7cd011db47|1|0|637251641211349542&sdata=Ct4c6rHjm8IAsva%2FajXLUrgo0Wy9g%2FrOHWfUqZ70jpo%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKSLXSDYCO5MCV5RZ564E7TRRWCVLANCNFSM4NBZJQ5Q&data=02|01|pawan.taparia%40microsoft.com|8bbf81228604454a518f08d7f8fdc99d|72f988bf86f141af91ab2d7cd011db47|1|0|637251641211359537&sdata=9J8eWF4%2BPkF2q2gw46hVuC9iTJWGq0iuiDsU%2BcMzHjg%3D&reserved=0.

Our SSO documentation is now live: https://docs.microsoft.com/en-us/power-virtual-agents/configure-sso


TSCppDefineClassFunc defines all functions

Steps to reproduce

Select single function declaration via V.
:TSCppDefineClassFunc

Expected behavior
Definition for only selected function.
Current behavior
Definition for all functions in the class.

Hi @Shatur ,
Thanks for the bug report. Currently all the functions of the class is implemented by the plugin. But I will add this feature soon

Added the feature to create only the specified class functions in visual mode.


DisableIEFirstRun

Hi there, it's me again.
Is it possible to integrate this little tweak?
It helps people who never open IE but want to use Invoke-Webrequest in Powershell :-)

i will make a new pr....


All versions of calx.js seem to be breaking Google Analytics 4 and causing all the javascript to fail.

All versions of calx.js seem to be breaking Google Analytics 4 and causing all the javascript to fail.
I've tried using v 1.1.9, 2.0.0 and 2.2.6 and they all seem to cause errors with the new Google Analytics 4. When the legacy analytics becomes deprecated in June of 2023, I'll have to make the decision to not collect analytics or not use the calc plugin. They both seem valuable in different ways.

I ran into the same problem and my solution is below.  Hope this helps.

https://github.com/xsanisty/calx.js/blob/main/jquery-calx-2.2.8.js

Line #37 has an issue:  if (typeof Array.indexOf !== "function") {

The left side of the argument returns undefined.  At least it returns undefined at the point where the file was loaded in my pages.   Executing this typeof Array.indexOf from the dev tools browser console does return "function" so my assumption is the file was loading before the brower's native indexOf function was there.  The plugin is setting the prototype.indexOf for browsers that do not need it which causes the error in gtag.js

Change Line #37 to if (!Array.prototype.indexOf) {

All done.  Now the plugin only sets prototype.indexOf for browsers that actually need it.  Which aren't very many and old ones like IE8 that nobody should be concerned about.  I'm pretty sure gtag.js won't work in browsers that would access the code in this if block anyway.

Thank you so much! This did the trick. I actually did it on the v1.x version of the plugin as well - been using this before 2.0 came along and I haven't converted the particular site over. MUCH APPRECIATED


Having more than one internal schema on schema isolation is confusing

Problem
Related to https://postgrest.org/en/stable/explanations/schema_isolation.html
See: https://matrix.to/#/!YGChDzXeYxtlBZqVsc:gitter.im/$V_mpHPVIPg_QJ2YMWWu7s3K5d1_WGmbcBwrdm2oaRxU?via=gitter.im&via=matrix.org&via=matrix.freyachat.eu

A PostgREST instance exposes all the tables, views, and stored procedures of a single PostgreSQL schema(a namespace of database objects). This means private data or implementation details can go
I think I understand using an 'api' as the schema that is exposed to the outside work. It makes sense to have a separate schema for the actual implementation. I do not understand why you would have more than one (core + internal + private).
... more that one implementation schema.
My assumption is that "core", "internal" and "private" are just examples of names where your implementation would go. Is this correct?

Solution
Just have one internal schema. Maybe add another one for "extensions".

Thank you!
Here are my ignorant thoughts regarding what makes sense to me:

private schema to hold internal representations
api schema to hold rest interface (usually behind authentication)
public schema to expose htmx functions (might or might not involve authentication)

One quick question I have is how to manage different versions of an API. Here is my assumption:

Each API version gets it own schema, and therefore its own postgrest config and therefore its own port.
Use nginx to map a port to a specific 443 url path (example: https://someurl.com/v1/sometable gets mapped to port 3000 vs https://someurl.com/v2/sometable gets mapped to port 3001)

I am including this thought in this thread because the assumption is that we can separate versions in different schemas.
I believe this works if you adopt the practice of where you allow the public/exposted versions of the schema to introduce breaking changes; however, you ensure the private schema does not break any actively supported public schema versions.
Curious to hear thoughts... Chuck


Use -Dskip.preview when building WildFly on GH Actions

Follow-up on https://github.com/wildfly-extras/wildfly-cloud-tests/pull/18.
This can wait until WildFly stabilises again

Preview isn't as time consuming as it used to be now that we no longer do transformation


Slack slash commands that use attachments don't populate the user who initiated the command

Environment
Version: 1.9.0
Operating system: linux/amd64
Please describe the expected behavior.
When a Slack user runs a slash command that returns a message with an attachment (i.e. /giphy), the bridge should relay the original user name of the person who ran the command instead of the Slack app's user.
Please describe the actual behavior.
When a Slack user runs a slash command that returns a message with an attachment (i.e. /giphy), the Slack message handler determines the user name improperly. It fills in the app name ("giphy" in this case) instead of the user who initiated the command.
Any steps to reproduce the behavior?
In a bridged Slack/Discord, have a Slack user run "/giphy ". When the message is posted to Discord, observe that the username is reported as "giphy" instead of the user.
Please add your configuration file
[general]
MediaDownloadSize=10485760
[discord.dudegroup]
Token=""
Server=""
RemoteNickFormat="{NICK}: "
[slack.dudegroup]
Token=""
RemoteNickFormat="{NICK} ({PROTOCOL})"
[[samechannelgateway]]
name="dg2dg"
enable=true
accounts = ["discord.dudegroup","slack.dudegroup"]
channels = ["dude_group"]

Is merged, so let's close this


check whether the current device is still valid during login

Example fix. I want to review this with @patrickxb.

This LGTM and much safer than relying just on the config file.

Landed bdfde6aed1f859b91b6a8bbdd8e9626ab6ebd723 with the force flag.


chore: add linux ci test spec

:tada: This PR is included in version 4.3.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


MAID-2000: chore/all: cleanup/improve CI scripts and README

fixed some outdated URLs
removed mention of a version of the Contributor Agreement
improved AppVeyor and Travis scripts

r? @dirvine
(maidsafe_highfive has picked a reviewer for you, use r? to override)


hand-cleaned changes to Build Runner

For some reason git closed #87 but this is the rebased and hand-cleaned version for this, resolving #86.

I know this one takes more review, but it does important stuff like making sure "Run All" doesn't destroy loadouts without prompting and (I'm pretty sure) tries to avoid the reload race condition by blocking it from running simultaneously.


Add NAPTR client support (again)

Great work! Can you squash the commits to drop the intermediate modifications?

@gera2ld done!


Banner font

What's the font used in the banner for the names of the colour schemes?

Hi,
The font used is VictorMono's italic variant (which is a gorgeous font that I also use on my terminal/IDE)
-Louise


Is it possible to obtain the original image?

I have an image (original.jpeg) processed by sharp using the following code:
  const img = sharp(bufferStream);
  const out = await img.toBuffer();
  fs.writeFile('./out.jpeg', out, (err) => {});

the output image is out.jpeg. when i run md5sum on both images it shows different hashes:
86e554644c690468c52dfdb4b20281b1  original.jpeg

49cd573be5036b3c264dfc031e2bf180  out.jpeg

Is there a way to process out.jpeg and get the original image and produce the same hash as original.jpeg ?

JPEG is lossy, so any decode/encode roundtrip will always result in the output differing from the input.


printing data to console w/ getLastTrialData

I am trying to save data to a db after each trial, and am testing this by printing the last trial's data to the console in the on_finish callback.  This seemed to be working fine in 5.0.3... but when I pulled down the most recent repo I am now only getting an empty {} in place of the data...
Thoughts?
I've read through a few closed issues... but am also unclear on the callback order of .on_finish, .on_trial_finish and write data.     What is the expected behavior?           Thanks!

The jsPsych.data module was overhauled for version 6 (master branch) but I haven't written the documentation yet.
This should still work:
var trial = {
  // ...
  on_finish: function(data){
    console.log(JSON.stringify(data));
  }
}

Yup! That works. I was not passing data to the function, rather accessing it as global.
Thank you!


base level metadata

I uploaded one of my generations, with just the pure front-end, to civitAI, and was surprised it picked up NOTHING about creation info.
Would be nice if, when using the plain non-custom-workflow generator, it saved the first-run generation info in standard format, in the metadata.
Just the basics like model name, seed, and the rest of the standard stuff please?
Saves a bit of time when uploading to civitai.
Please note that I'm using the user defaults. So, image format = JPG, and "save metadata" IS checked already.
given that, technically, i suppose this is a bug report rather than a feature request.

probably related to this, is if I view an image in history, it shows it in the center panel, anmd offers button to "reuse parameterss".
But if I press it.,. it then pops up, "No parameters to copy!"

the history one seems to work, if I change to .PNG instead of jpeg.
So i figure either you need to update the "save metadata" to also put it in the jpeg, or you need to have an auto-disable (with popup or something) for "save metadata" if format is jpg

Oh, woops, my bad - I updated the code for for jpeg metadata is saved to be a bit closer to how auto webui does it (to be more often detected by external programs) but forgot to update the reading to do the same.
I've updated it now to recognized jpegs clearly too.
re civitai, that's primarily a matter of civitai adding recognition for the metadata - should probably make a feature request to them.
Alternately, it's theoretically possible to add a "metadata format" option that lets you emit in fake-auto-webui format to trick external software that doesn't recognize swarm metadata to parse it anyway.

for civitai: I don tknow how specifically they do it. but I did a comparison of what comfy /stableswarm saves (using an external exiftool thing).. and it uses exif DIFFERENTLY for the two formats.
In one, it saves it as "Parameters", and in the other, it saves it as "User Data", I think?
That doesnt seem appropriate to me.
Maybe civit is already looking in both jpg and png, but its looking for the same exif name?

I went ahead and submitted the suggestion to civitai myself: https://feedback.civitai.com/submissions/6556764e01b92ee15f1efe5f

well.. unfortunately, i cant see your post.
however, civitai already has a working jpg info reader, that presumably is whatever A1111 writes.
Take a look at the exif info in
https://civitai.com/images/862136
then also download, and pretend to make an image post, using that image.
civit automatically picks up the info from the jpg

The post wasn't visible immediately, as civitai's feedback site goes through moderation before being public. It's visible now.
I'm well aware they have a system to read auto webui metadata inplace. Thus the suggestion that they add support for Swarm's metadata as well.

oh very cool.
I added my vote for it.


⚠ TROJAN 🇸🇬 Singapore SGP 1 has degraded performance

In f43f38f, TROJAN 🇸🇬 Singapore SGP 1 (https://sgt-2.opensvr.net/) experienced degraded performance:

HTTP code: 200
Response time: 13875 ms

Resolved: TROJAN 🇸🇬 Singapore SGP 1 performance has improved in 02914cb.


When we navigate using TAB key inside the "Available Authorization" dialog keyboard focus moves to background content after the 'Close' button: A11y_VS Code extension for API Center_Definition_OpenAPIDocumentation_Keyboard.

"Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier."
Please do not close this bug. This bug should only be closed by Trusted Tester after verification.
GitHub Tags
#A11yTCS; #A11yMAS; #A11ySev2; #WCAG2.4.11; #GH_VSCodeextensionforAPICenter_Linux_Apr2024; #DesktopApp; #VS Code Extension for API Center; #Keyboard; #Linux; #FTP; #A11yWCAG2.2;
Environment Details:
Application Name: VS Code Extension for API Center
OS: Linux- Ubuntu 22.04.4
Repro Steps:

Create an API center in azure portal.
Open Visual studio Code.
Tab till API center extension in the left side panel and press enter.
Tab till definition under the Api name which you have created, and press enter.
The name which you have provided to the definition will appear for ex-"openapi4", right click on it.
Go to "Open API Documentation" using the down arrow and press enter.
Demo conference API screen will appear. TAB to "Authorize" button and hit ENTER key.
"Available Authorization" dialog will open. Navigate using TAB key and observe the issue.

Actual Result:
When we navigate using TAB key inside the "Available Authorization" dialog keyboard focus moves to background content after the 'Close' button. Also, with "ESC" key not able to close the dialog.
Expected Result:
When we navigate using TAB key inside the "Available Authorization" dialog keyboard focus should not move to background content after the 'Close' button. Also, with "ESC" key we should be able to close the dialog.
User Impact:
Keyboard users will face difficulty here as they will not be able to understand where the focus is and will not be able to interact with the required controls.
Attachment:
https://github.com/microsoft/vscode-azureapicenter/assets/90901519/93dbbdb9-ecaf-4dab-87d3-1888d7d814b6

IRT Bug logged: https://dev.azure.com/CSS-IRT/CSS IRT/_workitems/edit/222928

Github Tags:
#External;#External:SwaggerUI;#eDAD:3p:222928;#ThirdParty;

External bug: https://dev.azure.com/CSS-IRT/CSS IRT/_workitems/edit/222928


Azure Managed IR "Compute Infrastructure"

This page states "Azure Integration runtime has properties related to Data Flow runtime, which defines the underlying compute infrastructure that would be used to run the data flows on.". Existing documentation does not make it clear how to do so. Neither [How to create and configure Azure Integration Runtime](https://docs.microsoft.com/en-us/azure/data-factory/create-azure-integration-runtime) nor [Set-AzDataFactoryV2IntegrationRuntime](https://docs.microsoft.com/en-us/powershell/module/az.datafactory/set-azdatafactoryv2integrationruntime?view=azps-2.8.0) contain useful information.

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

ID: d1a34b3c-a9b8-29ce-1eca-86f7f42981a1
Version Independent ID: 61d6e6b3-ec54-552d-1bef-86bbcbfea8ff
Content: Integration runtime in Azure Data Factory
Content Source: articles/data-factory/concepts-integration-runtime.md
Service: data-factory
GitHub Login: @nabhishek
Microsoft Alias: abnarain

@nabhishek Could you please help with @ssteinbauer 's question about Integration runtime in Azure Data Factory? Shane, so sorry for the long delay!

No action on this issue for over 6 months.
#please-close


[Types] Use DateOnly and TimeOnly

For the Cyphertypes Date and time there are matching types in .net 6.
Considering an upgrade DateOnly and TimeOnly could be used to to reflect these types.

@WhatzGames, these types are now available in 5.X drivers.


Keep thresholded counties for future calculations

Description
Fix bug where rows in thresholded counties are dropped in megacounty creation. When dropped, the signal backfill is incorrectly computed on 0-padded dates.
Changelog

extract megacounties and concatenate to original data in geo_maps::county_to_megacounty
update unit test test_geo_map::test_county_to_megacounty

Unit tests pass. Checks on state/msa/hrr match exactly to current behavior. More counties are produced (due to increased denominator from backwards padding).
@krivard Do we need to regenerate past issues of DV, up till when we switched to the geomapper? The data isn't wrong, but it is different, since it would have been produced only on larger counties, without the correct dynamic backwards padding.

Do we need to regenerate past issues of DV

hmm. I'd rather not, but I also don't want people using past issues for training to get a nasty surprise. How obnoxious is it to produce them?

Would take an afternoon to regenerate the files, but then I'd have to hand off to someone else to correctly insert issues into the database. I'm happy to help, but not sure if this is a priority at the moment.

let's hold off then -- if you finish your december okrs then pick it up, otherwise it can wait either until january, or until someone inquires, whichever comes first.
(loading them into the db is my job 🙂 )

Sounds good -- will put it on my list so I don't forget. Just a note that the automation has been updated -- so hopefully tomorrow we see better behavior!

DV from 2020-11-09 to 2020-12-13 will be reuploaded as part of a database fix.


iris tracking using mediapipe

Hello,
I have recently find this library: https://blog.tensorflow.org/2020/11/iris-landmark-tracking-in-browser-with-MediaPipe-and-TensorFlowJS.html
and my concern is to use its updated version, which does the iris detection (in the webpage, the second GIF, the comparison of the older and newer version), I want to use the right side one because:

the model works more robust in this version
there is no shaking in face mesh
no facemesh disappearing during extreme head poses
does iris detection
it shows how eyes are closed or open via eye region landmarks, when eyes are closed the eye landmarks come very close to each other to show that eyelids are closed.

But this library is for JavaScript which I don't know that language and of course I can't install and use it in my python scripts. I am looking for its python version or a converter to convert it from JS to python.
Would you please help/guide me through this issue?
Does your model give me what I am looking for?
Thank you

@lghasemzadeh Did you find a solution?


Add support for package dependency relationships

What would you like to be added:
Support tracking the full dependency graph for packages in the form of relationships, for the ecosystems that support extracting this information.
Why is this needed:
An SBOM is useful for at least listing what makes up a software artifact. However, it is more useful to know how a dependency is related to the artifact (is it a direct dependency? or a transitive dependency? is this dependency used by several other packages, or just one?).
Ecosystems that should be considered (not implying that these should minimally be implemented):

python: could be problematic for requirements.txt
java:
npm:
rust:
gem: gemfile.lock has this information, but not gemspec
rpm: supported
dpkg: supported
apk: supported
go: I don't think this is possible as is (either for binary or go.mod cataloger), but confirm this

Notes:
This assumes that https://github.com/anchore/syft/issues/556 is implemented, allowing for package catalogers to return relationships as first class evidence.

@wagoodman I started to play with the package dependencies for cyclonedx https://github.com/hectorj2f/syft/tree/hectorj2f/add_dependencies_to_cyclonedx. I am only generating the dependencies for the components as cyclonedx format recommends. Let me know if you prefer to open a PR for that.

Some detail here regarding which ecosystems this will be feasible for in a static-analysis sense (not reaching out to external data sources, such as maven central).
SPDX 2.2 relationships are used to describe what will be added to the artifact package in terms of new relationship types. The used relationships in the breakdown below are:

RUNTIME_DEPENDENCY_OF
DEV_DEPENDENCY_OF
BUILD_DEPENDENCY_OF
DEPENDENCY_OF

Question: we might not be able to accurately determine build-vs-runtime dependency depending on the lack of context (e.g.
python). Should we just use DEPENDENCY_OF instead in these cases? (final answer: yes)
apk
Summary: direct runtime dependencies

The D: section lists pull dependencies, which is a space delimited list of package names and categorized dependencies. E.g. D:scanelf so:libc.musl-x86_64.so.1.
One problem is being able to figure which of the dependencies are package names, and which are other requirements.
Relationships:
RUNTIME_DEPENDENCY_OF for any packages listed as pull dependencies
question: should we make package-to-file relationships for so: dependencies that are found by the resolver?

dpkg
Summary: direct runtime dependencies

The Depends and Pre-Depends sections hold information about dependencies: "Both depends and pre-depends mention the dependencies a package needs before installing but pre-depends forces the installation and configuration of the dependency packages before even starting with the package that needs the dependencies" source

Relationships:

RUNTIME_DEPENDENCY_OF for any packages listed as dependencies

golang
go.mod
Summary: flat-subset of transitive build dependencies.

go.mod contains a subset of transitive dependencies (but possibly more than direct dependencies). Cannot reason about dependency-to-dependency relationships

Relationships:

BUILD_DEPENDENCY_OF  for any package listed in the go.mod
For go.mod, we currently cannot determine if a dependency is for testing or not.

go binary buildinfo section
Summary: flat-transitive build dependencies.

go binary buildinfo section contains transitive dependencies. Cannot reason about dependency-to-dependency relationships

Relationships:

BUILD_DEPENDENCY_OF  for any package listed in the binary buildinfo section.

java
pom.xml
Summary: flat-direct build dependencies.

There is a <dependencies> section which describes direct build dependencies

Relationships:

BUILD_DEPENDENCY_OF  for any package listed the dependency section.

manifest
Does not contain dependency information
javascript
yarn.lock
Summary: flat psuedo-transitive runtime dependency pins

Each package has a "dependencies" section, which lists only direct dependencies. Dependencies of these dependencies is NOT tracked. Also the dependencies are not pinned versions

Relationships:

RUNTIME_DEPENDENCY_OF for any packages listed in the yarn.lock
cannot use the "dependencies" section within each package (since it is not a pin)

package.lock
Summary: transitive dependency pins with full dependency-to-dependency graph

Under the "dependencies" each pinned version specifies a loose version requirements for any packages that the pinned dependency requires under the "requires" section.
The requires section always has names that map back to the same name in the "dependencies" section.

Relationships:

RUNTIME_DEPENDENCY_OF for any packages listed as dependencies
full dependency graph possible (dependency-to-dependency relationships)

package.json
Summary: flat-direct runtime and dev dependency version ranges.

The "dependencies" section has a map of name:version values for direct dependencies
The "devDependencies" section has name:version values for direct dev dependencies
Note: version values are not pins, but range specifiers

Relationships:

RUNTIME_DEPENDENCY_OF for any packages listed as dependencies
DEV_DEPENDENCY_OF for any packages listed in  devDependencies

php
composer.lock
Summary: direct dependency version pins

Direct dependencies only within the "packages" and "packages-dev" sections
versions are pinned

Relationships:

RUNTIME_DEPENDENCY_OF for any packages listed as dependencies
DEV_DEPENDENCY_OF for any packages listed in  devDependencies

installed.json
Summary: No relationships possible

list of installed package versions and their required packages, required packages are only loose version specifiers

Relationships:

it's not clear that any relationships can be supported.

python
poetry
Summary: flat-transitive dependency dev and runtime relationships

Lists transitive dependencies in flat fashion (no dependency-to-dependency relationships)
Each dependency can be categorized (main and dev)
Relationships:
Can only describe that the main package relates to packages described within the poetry.lock (not a full transitive dependency graph)
DEV_DEPENDENCY_OF for packages with a "dev" category
~BUILD_DEPENDENCY_OF  for packages with a "main" category (question: should this be RUNTIME_DEPENDENCY_OF  since these dependencies are not required in the python compile step for generating pycs?)~ We cannot really distinguish these in all cases, so it is safer to use DEPENDENCY_OF

pipfile
Summary: flat-transitive dependency dev and runtime relationships

Lists transitive dependencies in flat fashion (no dependency-to-dependency relationships)
Each dependency goes underneath one of two json sections: default and develop
Relationships:
Can only describe that the default package relates to packages described within the lockfile (not a full transitive dependency graph)
DEV_DEPENDENCY_OF for packages with a "develop" category
~BUILD_DEPENDENCY_OF  for packages with a "default" category (question: should this be RUNTIME_DEPENDENCY_OF  since these dependencies are not required in the python compile step for generating pycs?)~ We cannot really distinguish these in all cases, so it is safer to use DEPENDENCY_OF

egg / dist metadata
Does not describe any relationships
rpmdb
TODO
ruby
TODO
rust
TODO

Can you elaborate more on the why for this feature? From my reading of it, what you are trying to do is to determine why a package foo of version bar made it into the thing you are scanning with syft.
If so, I fear dumping the dependency tree might not answer that question. Parsing the package manager operations log can approximate an answer, but the only deterministic way I’m aware of to do this is to perform actual process introspection during the image build to know exactly what ended up calling e.g. dpkg -i over a file on disk.
Conversely, with a purl that is differentiated enough you can augment the syft output with dependencies and much more metadata that is publicly known and available. If syft says nano version 1.2 is in this Ubuntu container of release foo, anyone can readily obtain the dependencies of that package from public sources.
Don’t get me wrong, I’m a fan of taking as much primary source data from the package manager in the scanned instance as possible. And I think flat SBOMs can be limited in many scenarios. But I think how the feature surfaces, what it tries to solve and how it changes the syft experience for people that are expecting a flat output might be worth additional consideration.
Thank you for working on syft and for helping syft users and the industry realize better outcomes through a thoughtful approach to the existing package manager metadata.

Adding one thing to my comment above. It’s possible that the “why” for this feature is not “what other binary depended on this binary/made this binary materialize” but more of a transitive “what other software was needed to make this binary that then went into my image” and that’s where Build-Depends and Built-Using (in the case of dpkg) would be more useful but the in-artifact package manager metadata might not contain that information. Ideally, that information would carry in each packages own SBOM but in practice the trend seems to be that metadata will live in publicly queriable services. Meaning that maybe this augmentation of syft output could be a post-analyze stage?

@bureado thanks for your thoughts on this --we chatted a lot about this at a recent community meeting and internally as well... I wanted to expose some of these conversations here in the issue as well.
Why do this feature? That's a fair question, and one that we've been exploring before trying to take it on. Squarely put, a list of packages without how they relate won't be able to answer questions about what could have introduced a package into the artifact.
Take for example, knowing that you have log4j installed is very useful, though if your intent is to remove it you need to know how it got introduced. Is it a direct dependency of your application? Did another package bring it in? Maybe both? It happens that for java packages the syft pkg.metadata.virtualPath is a good indicator for some of this, but it's heavily encoded... and the same equivalent field isn't present for all ecosystems. Bringing in relationships to raise up common descriptions of what is in the underlying data makes sense in this case.
Same can be said for vulnerability analysis. I see that I'm vulnerable to CVE-X-Y for this package, when combing this with VEX information in the future that can indicate applicability of a CVE from the publisher's perspective, knowing through which path in the dependency tree the vulnerability match is for starts to matter... this is only achievable by knowing the relationships between packages.
External data has richer relationship information. This is generally (nearly universally) true. Many ecosystems don't express full connectivity information between packages, however, their public repository (e.g. PyPI, Maven central, rubygems.org, etc) have this information and with some external querying you can get a better understanding of package-to-package relationships.
Sometime in the near future we want to add in features that allow syft to leverage external data in an opt-in capacity. However, we do have enough raw information from the underlying artifact to convey package-to-package connectivity in most ecosystems (and we're trying to be forward with the limitations for each ecosystem in https://github.com/anchore/syft/issues/572#issuecomment-1000412163).
Does the existence of better connectivity data externally indicate that we should not express package-to-package relationships? Or that we should hold off until we do have this ability to query external sources? My take is that we can introduce this feature but allow for configurability of it (be able to change behavior or the source of this connectivity information, or turn it off altogether).

But I think how the feature surfaces, what it tries to solve and how it changes the syft experience for people that are expecting a flat output might be worth additional consideration.

I 100% agree with this. We still want to provide a flat list of packages, so no change there. This would add additional elements in the relationships section of the SBOM. If it's the sheer number of additional relationships that would be the problem, then that future points to having configuration to turn off or augment this functionality.
Sorry for the radio silence on this @bureado , but happy to continue chatting about this.

from refinement:

this issue should not get picked up directly for work, but instead we should be creating new issues to account for each ecosystem... not byte them all off at once.

We'd love for this to be supported! How far is this on the roadmap ?

+1. would love to see this feature on Syft. Is this feature on the roadmap?

@wagoodman

External data has richer relationship information

This is something that is easily available now for public use (deps.dev). Are there any plans for incorporating the same ?

Ditto - I find that this feature would be incredibly helpful, particularly when using tools like DependencyTrack to visualize the dependency graph.  Trivy has support for maintaining dependency relationships

@wagoodman so I was looking at the parsing of java archives, in the context of an effort to think about Vex document hierarchies and cycloneDX over a particular dataset of containers.
As far as I can tell, currently Syft doesn't provide any "Relationship" information package-to-package with java archive parsing, currently the archive parser recursively takes a known java archive object and checks what's inside based on the manifest files -- anecdotally the archive parser seems to be what's most commonly invoked when handed a production container running java.  But there certainly IS a relationship if you are only reporting on the presence of one library because it was shipped inside the archive for another.
While opinions vary, generally from an SBOM perspective when we talk about a "dependency" we mean "if there's a problem with this, there may be a problem with thing depending on it", or for use cases about bringing it in, as discussed elsewhere.  And in THAT sense, the hierarchical information derived from the archive parsing seems like its valid dependencies, even if you don't go into the next level of sorting out the pom files.  That doesn't mean that the extra compile-scope issues in the pom couldn't be relevant.  But knowing, when processing an SBOM that the issue reported in jc-core is because that's a library inside the netty-common uberjar... is actually pretty valuable.
Changing syft to output the hierarchy when extracting from java archives isn't that hard.  I could maybe PR it (I built a POC of it after I found issue #1972 because I needed an example of maven for my purposes). Then you get into the different TYPES of relationships, should this be dependencyOf or Contains...
One thing I do think about is that from a CyloneDX perspective, I would be inclined to say that any package-to-package relationship counts as a "Dependency" for its purpose.  Although anecdotally, in terms of current syft output this seems to mostly just arise in OS packages containing library package types such as python etc.
As a note, processing NPM seems a bit harder within the current code framework.   Right now for NPM the standard behavior of cataloger is to parse a package json to retrieve a single package, so as I understand the code architecture, to get the list of all npm packages for relationships to correctly display one bomref to another you'd need to do it at the end of the run, and then process the dependencies?

I want to revisit this statement for a bit:

SPDX 2.2 relationships are used to describe what will be added to the artifact package in terms of new relationship types. > The used relationships in the breakdown below are:

RUNTIME_DEPENDENCY_OF
DEV_DEPENDENCY_OF
BUILD_DEPENDENCY_OF
DEPENDENCY_OF

Question: we might not be able to accurately determine build-vs-runtime dependency depending on the lack of context (e.g.
python). Should we just use DEPENDENCY_OF instead in these cases?
...final answer: yes

I think there could be a compromise here to get the best of both worlds. The main problem with using all 4 relationship types is that it makes it a little harder for consumers to use (they need to know about all types and union the graph together). The problem with using only DEPENDENCY_OF is that it's lossy, which isn't ideal when you're trying to discern nuance.
The compromise I propose is this: In syft JSON use DEPENDENCY_OF , but annotate the Data field of the relationship with additional dependency qualities (such as is it a dev dependency, runtime, build, etc):
https://github.com/anchore/syft/blob/da31eed6374de15a4b684c34fa7e63c770878190/syft/artifact/relationship.go#L37-L42
Even if the struct was something simple like:
type DependencyKind struct {
  Runtime bool
  Development bool
  BuildTime bool
}

would be a step forward, since it would allow for multiple options to be true without muddling the graph with more edges than necessary.
I feel that this would make a good trade off in terms of making graph traversal easier to grok without loosing information.

Linking the latest and greatest SPDX 3.0 relationship types as a dev note for those picking this up on a per ecosystem basis:
https://spdx.github.io/spdx-spec/v3.0/model/Core/Vocabularies/RelationshipType/#

Team consensus from our weekly gardening meeting is to not tackle https://github.com/anchore/syft/issues/572#issuecomment-1932781666 , meaning we will only have DEPENDENCY_OF. Note: this means that if something is a dev, build, or dependency then it will still be captured as DEPENDENCY_OF.


update products when sales is disabled

@ericsaupe, @jeffreyfuchang

@ericsaupe better ?

Yup. Thanks

closing because of #28


[BUG] Longhorn Manager can't start after deleting volumes/stuck

Describe the bug
After deleting a few volumes, which are now stuck in deleting, 3 out of 5 longhorn managers are in a restart loop.
Log or Support bundle
longhorn-support-bundle_55903fa6-26ed-4355-a4bf-17d3650572cc_2022-02-17T11-24-39Z.zip
`ime="2022-02-17T11:14:50Z" level=debug msg="Can't find share manager, may have been deleted" controller=longhorn-share-manager node=pax-p-96 shareManager=pvc-78321e92-5090-424b-b939-2d8fe51710f5
time="2022-02-17T11:14:50Z" level=warning msg="Error syncing Longhorn backup longhorn-system/backup-272a790321bc48d6" controller=longhorn-backup error="longhorn-backup: fail to sync backup longhorn-system/backup-272a790321bc48d6: cannot get client for engine pvc-b377393f-f5f4-4b99-aac1-2d92009f1d35-e-08080876: engine is not running" node=pax-p-96
time="2022-02-17T11:14:50Z" level=debug msg="Start monitoring instance manager instance-manager-r-9c410d90" controller=longhorn-instance-manager instance manager=instance-manager-r-9c410d90 node=pax-p-96
time="2022-02-17T11:14:50Z" level=warning msg="Error syncing Longhorn backup longhorn-system/backup-bdfd1847958b4fca" controller=longhorn-backup error="longhorn-backup: fail to sync backup longhorn-system/backup-bdfd1847958b4fca: cannot get client for engine pvc-b377393f-f5f4-4b99-aac1-2d92009f1d35-e-08080876: engine is not running" node=pax-p-96
E0217 11:14:50.203577       1 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
goroutine 1297 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic(0x1931a20, 0x2c92950)
/go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:74 +0xa3

k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
/go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:48 +0x82

panic(0x1931a20, 0x2c92950)
/usr/local/go/src/runtime/panic.go:967 +0x166

github.com/longhorn/longhorn-manager/controller.(*BackupController).getEngineClient(0xc000845780, 0xc0015139e0, 0x28, 0x0, 0x0, 0x0, 0x0)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:416 +0x7d

github.com/longhorn/longhorn-manager/controller.(*BackupController).checkMonitor(0xc000845780, 0xc005541180, 0xc005492800, 0xc0000acb60, 0x0, 0x0, 0x0)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:469 +0x182

github.com/longhorn/longhorn-manager/controller.(*BackupController).reconcile(0xc000845780, 0xc003225810, 0x17, 0x0, 0x0)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:305 +0x1263

github.com/longhorn/longhorn-manager/controller.(*BackupController).syncHandler(0xc000845780, 0xc003225800, 0x27, 0x0, 0x0)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:170 +0x182

github.com/longhorn/longhorn-manager/controller.(*BackupController).processNextWorkItem(0xc000845780, 0x203000)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:136 +0xcc

github.com/longhorn/longhorn-manager/controller.(*BackupController).worker(0xc000845780)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:126 +0x2b

k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0xc0017a6db0)
/go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:155 +0x5f

k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc0017a6db0, 0x1e6faa0, 0xc0007a1320, 0x1, 0xc0003a4000)
/go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:156 +0xa3

k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc0017a6db0, 0x3b9aca00, 0x0, 0x6207594d00000001, 0xc0003a4000)
/go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 +0x98

k8s.io/apimachinery/pkg/util/wait.Until(0xc0017a6db0, 0x3b9aca00, 0xc0003a4000)
/go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:90 +0x4d

created by github.com/longhorn/longhorn-manager/controller.(*BackupController).Run
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:120 +0x1c9

panic: runtime error: invalid memory address or nil pointer dereference [recovered]
panic: runtime error: invalid memory address or nil pointer dereference

[signal SIGSEGV: segmentation violation code=0x1 addr=0x1f0 pc=0x161662d]
goroutine 1297 [running]:
k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
/go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:55 +0x105

panic(0x1931a20, 0x2c92950)
/usr/local/go/src/runtime/panic.go:967 +0x166

github.com/longhorn/longhorn-manager/controller.(*BackupController).getEngineClient(0xc000845780, 0xc0015139e0, 0x28, 0x0, 0x0, 0x0, 0x0)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:416 +0x7d

github.com/longhorn/longhorn-manager/controller.(*BackupController).checkMonitor(0xc000845780, 0xc005541180, 0xc005492800, 0xc0000acb60, 0x0, 0x0, 0x0)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:469 +0x182

github.com/longhorn/longhorn-manager/controller.(*BackupController).reconcile(0xc000845780, 0xc003225810, 0x17, 0x0, 0x0)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:305 +0x1263

github.com/longhorn/longhorn-manager/controller.(*BackupController).syncHandler(0xc000845780, 0xc003225800, 0x27, 0x0, 0x0)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:170 +0x182

github.com/longhorn/longhorn-manager/controller.(*BackupController).processNextWorkItem(0xc000845780, 0x203000)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:136 +0xcc

github.com/longhorn/longhorn-manager/controller.(*BackupController).worker(0xc000845780)
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:126 +0x2b

k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0xc0017a6db0)
/go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:155 +0x5f

k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc0017a6db0, 0x1e6faa0, 0xc0007a1320, 0x1, 0xc0003a4000)
/go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:156 +0xa3

k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc0017a6db0, 0x3b9aca00, 0x0, 0x6207594d00000001, 0xc0003a4000)
/go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 +0x98

k8s.io/apimachinery/pkg/util/wait.Until(0xc0017a6db0, 0x3b9aca00, 0xc0003a4000)
/go/src/github.com/longhorn/longhorn-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:90 +0x4d

created by github.com/longhorn/longhorn-manager/controller.(*BackupController).Run
/go/src/github.com/longhorn/longhorn-manager/controller/backup_controller.go:120 +0x1c9`

If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment

Longhorn version: 1.23
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Rancher Catalog App
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: RKE

Number of management node in the cluster: 3
Number of worker node in the cluster: 5

Node config

OS type and version: Ubuntu 20.04
CPU per node: 8
Memory per node: 32GB
Disk type(e.g. SSD/NVMe):
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster: ~50 active

Additional context

Update: After ~5 hours the managers recovered and the volumes got deleted.

Thank you for reporting. This issue is a duplication of https://github.com/longhorn/longhorn/issues/3484. And it's already fixed.


please update podspec

podspec's version is 1.0.2
please update 1.1.0
Thank you 👍

+1

+1

@mRs- Could you release the latest version of v1.1.0 to Cocoapods? We also hope that the current develop for RxSwift 6.0 will be released as well.


Migrate docs client to webpack-dev-server.

webpack-dev-server was deprecated, but then undeprecated and the replacement webpack-serve itself is deprecated.
Also adds a redirect to the path with a trailing slash to help with the confusing behavior we saw a while ago.

@anuraaga Thanks for nice work!
Could you update the license file?
yarn licenses generate-disclaimer --prod > ../licenses/web-licenses.txt

This only affects dev dependencies so the bundle's dependencies, and therefore licenses, aren't changed.

@anuraaga Ahh, I see. Thank you for migrating  webpack-dev-server!

Thanks a lot, @anuraaga !


同一个视频存在不同码率的版本会导致下载失败

cid：53dv01524,53dv01332,53dv01289,53dv01266,53dv01174,53dv01041

Thanks you, I have fixed the error.
The error happens because the ikoa can't get any input to choose which part of the query results to download. I add echo 1  to always choose the first part to download(higher bitrate). It's just a hack, but
can work anyway.

Thanks you, I have fixed the error.
The error happens because the ikoa can't get any input to choose which part of the query results to download. I add echo 1 to always choose the first part to download(higher bitrate). It's just a hack, but
can work anyway.

Thanks a lot, bro!


expect_only_one raises in partition_text if you pass in an empty string

Currently, expect_only_one raises if you pass in an empty string to partition_text. Better behavior for this would be to default the text kwarg in partition_text to None and return [] if text == "" (since there's no text to partition). It's likely the same behavior holds for partition_html as well.

Addressed in #413. expect_only_one no longer raises under this condition because an empty string now returns [].


[FIX] Add Arabic Support to Slugify

ping @EngHazem

Great @akazorg
Working perfectly.

This is more a fix then adding new features. Ŵhy isn't this merged? xD

@akazorg this still works for English like it used to, correct?

@abdgad, yes, supports english.
I've changed the expression, it was only supporting [a-z0-9].

Okay thanks (Y)


VS2022 Compile: Cannot resolve metadata for WinUI types. Please ensure that Nuget Restore was successful

Hi
Has this ever happened to you? how do i solve?

@evelynwu-msft any known issues that explain this?

Same issue here after updating to the new Microsoft.WindowsAppSDK (1.0.1)

Same here after updating to the new Microsoft.WindowsAppSDK (1.0.1)

Same here after updating to the new Microsoft.WindowsAppSDK (1.0.1)

Same here after updating to the new Microsoft.WindowsAppSDK (1.0.1)

Have a look at your csproj file. Because upgrading to 1.0.1 adds a reference there which is not being removed when downgrading again. As soon as you remove the additional line you should be good to go.

Same here after updating to the new Microsoft.WindowsAppSDK (1.0.1) . Downgrade to 1.0.0,don,t resolve it

@ajgarciaj ajgarciaj
Have a look at your csproj file. Because upgrading to 1.0.1 adds a reference there which is not being removed when downgrading again. As soon as you remove the additional line you should be good to go.

I've done these steps before to get past a similar problem:

Visual Studio > Build > Clean Solution > Close VS
Project Folder > Delete bin & obj folders
User Folder > Delete .nuget folder (or at least the microsoft.windows*.* folders inside)

FYI, I'm running 1.01 right now just fine and didn't run into this problem - unclear on the cause.

Same here after updating to the new Microsoft.WindowsAppSDK (1.0.1) . Downgrade to 1.0.0,don,t resolve it

@ajgarciaj ajgarciaj Have a look at your csproj file. Because upgrading to 1.0.1 adds a reference there which is not being removed when downgrading again. As soon as you remove the additional line you should be good to go.

This seemed to be not working for me, i changed 2 references in csproj file and the error persist. Thanks.

I've done these steps before to get past a similar problem (that is to say I couldn't compile after a package upgrade, and could do so after cleaning house):

Visual Studio > Build > Clean Solution > Close VS
Project Folder > Delete bin & obj folders
User Folder > Delete .nuget folder (or at least the microsoft.windows*.* folders inside) - note: this is just the default location of the folder

FYI, I'm running 1.01 right now just fine and didn't run into this problem - unclear on the cause.

Thnks, it's working

Make sure your <TargetFramework> points to a Windows-specific (-windows) target framework moniker (e.g. net6.0-windows10.0.17763.0).

Also tried what @kmgallahan suggested. Can build windows, but not android or ios, keep getting this Error	WMC1007	Cannot resolve metadata for WinUI types. Please ensure that Nuget Restore was successful. ! !

Uninstall 1.01 version from Nuget packets administrator works fine finally. Now i can build with alls platforms.

Same here. Problems for months. David and James are always very excited in their videos. But my enthusiasm isn't that big anymore.
Uninstalling the SDK was the solution.

Make sur you have this in you .csproj
01837340-F8F7-4005-8980-CE617BD87B29
clean solution and rebuild is
that works for me

To clarify, I got it working by doing the following.
Add this line to the .csproj:
<ApplicationId Condition="$(TargetFramework.Contains('-windows'))">1CD0A983-580B-459D-9F18-2C2B97BC38FB</ApplicationId>

Remove any references to WindowsAppSDK outside the Windows condition itemgroup, so only the below code should be there:
<ItemGroup Condition="$(TargetFramework.Contains('-windows'))">
	  <!-- Required - WinUI does not yet have buildTransitive for everything -->
	  <PackageReference Include="Microsoft.WindowsAppSDK" Version="1.0.0" />
	  <PackageReference Include="Microsoft.Graphics.Win2D" Version="<IP_ADDRESS>" />
</ItemGroup>

Then clean the solution and start the application again.

Solved it by doing this
01837340-F8F7-4005-8980-CE617BD87B29
and

Getting this in a maui app -- but only if I want to run the app on Android rather than Windows. I tried this from the previous comment some time before, it seems:
	<ItemGroup Condition="$(TargetFramework.Contains('-windows'))">
		<!-- Required - WinUI does not yet have buildTransitive for everything -->
		<PackageReference Include="Microsoft.WindowsAppSDK" Version="1.1.4" />
	</ItemGroup>

Thing is, if a new version of WindowsAppSDK is updated via NuGet, I get a dupe in the regular PackageReference ItemGroup. (Of course I have forgotten all the details by then.) So I add this comment -- just as a reminder to myself. :)
Maybe this should be forwarded to the Visual Studio 2022 team...?

This issue still persists.

I faced same error. After removing PackageReference part above, I works now.


Optimization of XLIFF format, wishes and suggestions from the point of view of translators

I have to add a few wishes and suggestions about the XLIFF format used by Dynamics NAV, which is known to replace all ML texts.

the format itself is well suited for direct distribution to translation agencies. You don't have to convert all the texts into a readable format like before.

if you use several identical texts in an object, e. g. in text constants, now labels, these are not cumulated in XLIFF, but added individually. That doesn't make any sense. Why is a text added more than once when it is used several times? Couldn't this be simplified by saving only DISTINCT in this file?

naming: That is a very big criticism, which I have already heard several times. The created names simply don't make any sense. Even the specified object IDs do not exist. Much more, some other values seem to be inserted into the key. Why not use the real object names and IDs, or let the user decide for himself what the key of the text is. This would also make it possible to implement point 2.

creation only when creating packages. Why is there no separate menu option for creating the XLF file to update only it. So far, you always have to compile the complete extension.

preparation of new languages or revision. If you are working on an extension, there are always cases where new texts are added or existing changes occur. If you create a new file anyway. Couldn't you then prepare the existing other languages XLF files accordingly? So add new strings, and delete deleted ones? Then the files would all be synchronized. Otherwise, it is very difficult to work out the differences.

These are some of the points I took up and wanted to pass on. Maybe one or two points are also interesting for others here. Please send me further feedback.

I will try to address your issues:

I'm not sure what the question is
It's hard to say when using the same word in 2 places really is the identical thing. Maybe the translation changes depending on the context. That's why we keep things separate.
The generated hashes for the IDs are a result of some tools having issues when the ID is too long. We would have to have the ID contain 3 names to make sure the ID is unique: The name of the application object, name of the containing control and the name of the control itself. This, together with the types of each of the symbols can take up to about 400 characters which could cause issues.
Right now we try to have one action which updates everything. This makes sure nothing is stale when you build the extension. I understand you might want to update just the generated translation file or the report layout, this command is something we have on our backlog.
This is not as simple feature as it may seem. This would require us to consume all the existing xliff files in the extension and do the diffing and updating and removing. While we do not have the feature right now we do have it on our long term backlog.
This is a good suggestion. I might start adding the type of the field as well.
@SirBETE are you talking about table fields? I can see that once you specify a caption it is used in the translation file instead of the field name. Could you try using a newer version of the compiler and check if it's still happening and then open a separate issue for it?
We are misssing a feature to generate xliff files for other languages when doing txt2al. It requires a significant amount of effort so we haven't done it yet but we have it on the backlog.
ToolTipML, InstructionML, textcost and old report labels are not included in the xliff files. You need to change them to the new syntax to have them included in the xliff files. Please take a look at the https://docs.microsoft.com/en-gb/dynamics-nav/developer/devenv-work-with-translation-files to better understand.

@DominikDitoIvosevic
Thank you for the answers from the Microsoft team. I would like to make a few comments on certain points, because I do not quite understand the choices here:
To point 2:
If a string is used twice, the user should be able to decide for himself whether it is the same string. Couldn't it be made configurable? So far, we have not really had the problem that in different contexts, the same text had a different meaning. I just find it rather clumsy to say that this is not the case.
Point 3:
The given IDs don't make any sense at all! What does a translation agency care about the Method ID or another ID there? If at least the method name were used here. In everyday life, these strings are not to be used by anyone.
To point 5:
I am well aware that this is not an easy requirement. But it would greatly simplify the handling of such files. And from the user's point of view, this makes sense. The previous solution is not really acceptable.
To point 8:
I believe that this would not be as bad as it is described. This would presuppose, however, that this would require optimizations in XLIFF format. With the IDs and fields you are currently only in your own way. Why is it not possible to reconsider the whole behaviour of this file?
From my point of view, the user-friendliness is a little bit too short here. Essential points that would make it easier for end users and developers are almost exclusively blocked in this case on the grounds that this would not be easy to implement. User friendliness is never easy to implement, but as it runs so far it is just a little bit 1. confusing and 2. not always useful. In addition, the XLF files created cannot be compared easily. This means that if I received a language from the translation agency, for example, I would have to compare the files in order to determine the differences.

@FSharpCSharp

We are aware of advanced features of xliff format and have it on our backlog but we can't give you a timeline right now

As I said, the IDs were put there because of limitations of existing tooling. We are looking into placing the names there directly.

This is on our long term backlog and we are having discussions about the right approach

This story is not finished. There are many areas to improve. Right now we got up until here but we plan on adding more features.

I appreciate your questions as they give us more insight into what is important for our users. I hope that you understand that we still need to prioritize things and hence cannot give all features at once.

Just to add a comment on point 2) Identical texts from objects added as separate entries:

in our experience, there are quite a few cases where the translation of the same text is different based on the context. So this is not a theoretical, but an actual real world scenario. Having identical texts as different entries in the translation file is the proper approach.
grouping the text instances which should be translated the same way is a nice idea, but maybe this should be handled by the translation tool and not NAV source. Such grouping would be, again, language dependent.

@vytjak @DominikDitoIvosevic
Of course, it can happen that a text has different meanings in different contexts. However, this has not yet been the case with all our modules. We checked our code base with the help of translation exports, and it turned out that we always had the same translations for our languages (in our case, German and English) for the same texts. We only had 2 - 3 cases in a module with about 1000 texts. For this reason, this is the exception rather than the rule for us. I cannot therefore judge how it is with other languages. That is why, by default, my proposal was to carry out a grouping and, in special cases, to make a distinction when there really is another meaning.  You can't write a comment everywhere, because our office used to only go by the key. Various colleagues have already said the same thing to us, and I have been asked to pass on this criticism. It does not, therefore, represent my personal opinion, but rather summarises points of different views on this subject. Everyone sees the subject differently. Actually, I only wanted to start a discussion, because the status as it is so far anything but comfortable, be it for the developer or the full-time translator.

I have another suggestion: on-the-fly (or on-the-code) translations
It will help for those developers that do the translations themselves, and are not going to give it to an agency.
I just created a request here: https://github.com/Microsoft/AL/issues/1702
Salut!
Laura Nicolàs


Add Vehicle.CanUseSiren and the getter of Vehicle.IsSirenSilent

I'm not a fan of adding that Log2 hack to be honest. But also what's the difference between HasSiren and CanUseSiren?


[JSV-2] Validator binary update pr action is not correctly naming files

The file names included in the PR should be based on the os and arch.  Looking at https://github.com/tablelandnetwork/js-validator/pull/117/files you can see that linux-amd64 and darwin-amd64 are correctly being updated, but there is a new file called api.exe that should be replacing the current windows-amd64.exe executable.
Also the arm builds are not being included in the update
JSV-2

Fixed by #106


Fix: ToB-05 (destination chain agent root)

Description

Fixed ToB-05 by allowing the contract owner to set the Agent Merkle Root in LightManager. This could be used to resolve disputes or update the agent root in general, if no active Notaries exist under the current one.

Function uses the same "no fresh data for X minutes" check as resolveStuckDispute used to have.

resolveStuckDispute is moved to BondingManager, as it is no longer necessary in LightManager.
resolveStuckDispute was renamed into resolveDisputeWhenStuck for consistency.

Summary by CodeRabbit
Release Notes:

New Feature: Introduced resolveDisputeWhenStuck function in InterfaceBondingManager and AgentManager to handle stuck disputes.
New Feature: Added setAgentRootWhenStuck function in InterfaceLightManager and LightManager to set agent root when the contract is stuck.
Refactor: Removed resolveStuckDispute function from IAgentManager and AgentManager.
Refactor: Renamed setAgentRoot to _setAgentRoot in LightManager and changed its visibility to internal.
Test: Added new tests for resolveDisputeWhenStuck and setAgentRootWhenStuck functions.
Chore: Updated error handling in Errors.sol, AgentManager, BondingManager, and LightManager.

@mikeyrf the two-step process is now implemented. Will fix the merge conflict once I merge some of the other PRs into master.


Does not build - error E0793

> cargo build --release

[...]

**   Compiling backtrace v0.3.59
error[E0793]: reference to packed field is unaligned
    --> C:\Users\myuser\.cargo\registry\src\index.crates.io-6f17d22bba15001f\ntapi-0.3.6\src\ntexapi.rs:2785:52
     |
2785 |         *tick_count.QuadPart_mut() = read_volatile(&(*USER_SHARED_DATA).u.TickCountQuad);
     |                                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
     |
     = note: packed structs are only aligned by one byte, and many modern architectures penalize unaligned field accesses
     = note: creating a misaligned reference is undefined behavior (even if that reference is never dereferenced)
     = help: copy the field contents to a local variable, or replace the reference with a raw pointer and use `read_unaligned`/`write_unaligned` (loads and stores via `*p` must be properly aligned even when using raw pointers)

error[E0793]: reference to packed field is unaligned
    --> C:\Users\myuser\.cargo\registry\src\index.crates.io-6f17d22bba15001f\ntapi-0.3.6\src\ntexapi.rs:2809:25
     |
2809 |         ((read_volatile(&(*USER_SHARED_DATA).u.TickCountQuad)
     |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
     |
     = note: packed structs are only aligned by one byte, and many modern architectures penalize unaligned field accesses
     = note: creating a misaligned reference is undefined behavior (even if that reference is never dereferenced)
     = help: copy the field contents to a local variable, or replace the reference with a raw pointer and use `read_unaligned`/`write_unaligned` (loads and stores via `*p` must be properly aligned even when using raw pointers)
**

This looks like a problem in one of the dependencies, not in the code. Nevertheless, decided to report.

How can I fix this issue?

I've updated the cargo.toml file to allow other versions of egui/glium. Rant: why have versions, if it breaks anyway, anyway, tt builds now, but it won't run. Some things are deprecated. And a rewrite would be needed.
Now, I'm questioning if I should archive this project. Arquivos RTP changed the way they stream videos and all of them have DRM protections - videos will become corrupted on download.


Fix broken link

Fixing broken Logitech SmartDock link

@tonysmit
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


"go test" for nats: 5 test failures against gnatsd

5e5b726926cb1640630fb80c3420187be0b45da8 : on OSX 10.10.2/amd64. go1.5.1.
Five nats tests fail out of the box against gnatsd. Details below.
NB, I didn't want to mess with ruby and the ruby nats server, so I changed conn_test to use gnatsd. Shouldn't this be the default since the ruby version is deprecated?
failed tests:
--- FAIL: TestServerSecureConnections (10.04s)
	conn_test.go:47: Timed out trying to connect to gnatsd
...
--- FAIL: TestServerAutoUnsub (0.00s)
	sub_test.go:29: Received 0 msgs, wanted only 10
...
--- FAIL: TestClientASyncAutoUnsub (0.00s)
	sub_test.go:75: Received 0 msgs, wanted only 10
...
--- FAIL: TestAsyncErrHandler (2.54s)
	sub_test.go:197: Failed to call async err handler
...

Moved to gnatsd per 6d6f2c4f31f6bba97cefafed57929153eb475196


Fixed exception where cookies[] was nil in consent banner

A simple check that cookies is not nil before checking cookies['cookie_eu_consented'].

Tnx :)


[TRIVIAL] remove deprecated usage of @disable for an overridden method

I also encountered that. On one hand, if you're calling through Stream base class, @disable is meaningless, however if you have a SocketStream reference, you get compile-time error, instead of run-time exception, which is marginally better. Given that undeaD is for deprecated functionality, investing is such type-safety is not worth much, so I'm ok with making the build less spammy.


Errors with Angular 2 and up

Hello,
I want to use this with Angular project, but I get an error because It uses a custom tag and Angular also uses the same, Angular throws an error 'img-2' is not a known element:.

Try to add the Custom Elements Schema in your angular module :
https://angular.io/api/core/CUSTOM_ELEMENTS_SCHEMA


Fix issue #939

Fix the issue #939

Coverage increased (+22.3%) to 73.695% when pulling 83a90a7498082a1b4938bd14bc4cfae2bf34d281 on yuye/kubelet-deploy-issue into 22ee0968f696247727df0cb56b757bed6ac5e33e on master.


[BEAM-2204] support TUMBLE/HOP/SESSION_START

*_START function is supported for TUMBLE/HOP/SESSION window, however *_END is not available due to some issue with Calcite relational expressions, need a follow up with Calcite team.

R: @xumingming @takidau
CC: @iemejia

retest this please

Changes Unknown when pulling 1d33e7ba1a0efe27d5b38ded15f7e3f4b85b0869 on XuMingmin:BEAM-2204 into ** on apache:DSL_SQL**.

Changes Unknown when pulling 3bb339a5214861434a579fe44c830546fe5bf506 on XuMingmin:BEAM-2204 into ** on apache:DSL_SQL**.

Thanks, merging!

Merged, feel free to close.

Btw, I messed up the original push by forgetting to git fetch before merging, hence the double push from asfgit after I reconciled things and patched up the history.

seems the code is merged successfully right? I'll take care of it in a following PR in case any error.

Code is merged successfully now, correct. I fixed things and revised the history accordingly.

Awesome, thanks!


Error compiling rp2_common/hardware_irq/irq.c

Using GCC 10.3.0 (arm-none-eabi), compiling the source file rp2_common/hardware_irq/irq.c yields an error:

Assembler messages:
Error: invalid offset, value too big (0x0000040C)

The culprit is the function slot_diff(), which implements pointer difference in inline assembly. I could pinpoint the problematic instruction being "ldr  %0, =0xaaaa\n".
I'm not proficient enough in ARM Cortex assembly to judge, but it looks like this offset would be too large for a LDR instruction on a Cortex-M0/+. Not sure why it would fail to assemble in my case, and apparently not for you guys.
I'd also like to understand the statement in the comment:

GCC produces horrible code for subtraction of pointers here, and it was bugging me

How horrible could have it been really?

How horrible could have it been really?

pretty odious, and enough for me to want to change it when it is inlined a bunch
I also tried on 10.3-2021.07 and that seem fine. either way it seems like a compiler bug, however this is equivalent and maybe will help

    int32_t result = 0xaaaa;
    // return (to - from);
    // note this implementation has limited range, but is fine for plenty more than -128->127 result
    asm (".syntax unified\n"
         "subs %1, %2\n"
         "adcs %1, %1\n" // * 2 (and + 1 if negative for rounding)
         "muls %0, %1\n"
         "lsrs %0, 20\n"
        : "+l" (result), "+l" (to)
        : "l" (from)
        :
        );

yeah it is weird because ldr , = is an assembler thing, so the assembler gets to pick where to put the data, so doesn't usually put it somewhere it won't work!

ah actually now i give it a moment's thought it may be a question of .ltor placement, so perhaps not to blame the compiler/assembler entirely.

OK, glad I could "help" improve this.
Now I have experience with Cortex-M4 and -M7, but none with -M0/+, and I realized that the latter don't have any hardware divider. I suppose the inefficient code produced by the compiler is due to an inefficient software implementation of division here.
I guess GCC is better at producing efficient code for constant dividers for some dividers and less for others. Here we have a division by 12. AFAIR, divisions by 10 were handled efficiently by GCC - actually generating something similar to your assembly. But that may depend on the divider and on versions of GCC, regressions are not uncommon.

yeah, it is probably also doing a multiply by reciprocal also, however the big failing in GCC on CortexM0+ is there is no way to tell it you have 1 cycle multiply (which RP2040 does), so it insists on doing a serious of shifts and adds.


Add links to donate to charities

README.md
Feedback page inside extension
Create dedicated charity page, e.g. https://schmich.github.io/marinara/charity.html
Which charities? Cancer research, breast cancer research, mental health, LGBT
International non-profits?

@schmich I would like to contibute to this project. Can you guide me on things like, what I need to learn, is there any slack or discord community etc.


Remove impl<T: AsRef<[u8]>> From<T> for Buffer  that easily accidentally copies data

Which issue does this PR close?

Rationale for this change
This API makes it easy to accidentally copy data as described in #6033. For example
let data = vec![...]
let buffer = Buffer::from(vec);

Would copy the bytes in the vec rather than taking ownership.
#6039 removed uses of this API in the arrow-rs codebase.
We should also remove the API
What changes are included in this PR?

Removes impl<T: AsRef<[u8]>> From<T> for Buffer
Add some APIs to ease the migration for existing codebase (like impl From<[u8]>)

Are there any user-facing changes?

Incorporated comments from https://github.com/apache/arrow-rs/pull/6039#issuecomment-2226852353

Per discussion on https://github.com/apache/arrow-rs/issues/6050 I am going to merge this branch to the 53.0.0-dev feature branch, where we are collecting PRs with breaking changes before master opens


Double Chromecast name listed

The issue is caused by microg

Proof if

It is cause by gmscore.. but don't worry I will just stop using it and revanced. Thank you anyway you are very very kind!

Sei un ritardato
Il gio 4 apr 2024, 20:19 oSumAtrIX @.***> ha scritto:

Proof if
—
Reply to this email directly, view it on GitHub
https://github.com/ReVanced/GmsCore/issues/46#issuecomment-2037888206,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR5JZB6Y7Q5FFKVO7AIFKFTY3WKSZAVCNFSM6AAAAABFXXMD4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZXHA4DQMRQGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Screenshot?

Screenshot?

@DaddyNix Is correct. The previous version had an option to fix the duplicate cast names.
Steps:
Open YouTube (ReVanced) -> Click Name/Profile in top right corner -> Settings: https://ibb.co/mvxzG9W
After clicking on MicroG Settings: https://ibb.co/ysKfScf
I have an old phone running the previous version of ReVanced YouTube where the setting from the screenshots above was taken.
ReVanced Manager version: 1.17.1 (not sure what version of patches was used)
Patched Youtube version: 18.37.36
Vanced MicroG version: <IP_ADDRESS>220
Hope that helps!


Update _index.md

updated new end of life date

@omer-cloudflare the update was already merged with https://github.com/cloudflare/cloudflare-docs/pull/8447 I think we can close this.


Installer script popd issue in later versions of bash

./seekrets-install: line 93: popd: /tmp/tmp.7kBP85AYOb: invalid argument
popd: usage: popd [-n] [+N | -N]

I don't see it in osx: GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin16)
But do on debian: GNU bash, version 4.4.5(1)-release (x86_64-pc-linux-gnu)

Should be closed by https://github.com/18F/laptop/pull/130

@cmc333333 Can you verify now that above PR has been merged?

Yeppa, all looks good. Thanks!


TODO: Extract & simplify private2public function

Would be nice to extract and simplify the code necessary only for the private to public key conversion from itay/CryptoPHP's repo.
There may be other necessary functions required.

see commit 2f61d21edb300b892be51539737421cfcafa247b

Base58 and other functions are here

Awesome!  The math is starting to make more sense now that I can focus in closer on it.
I'll close this for now.