DBZ-630 Unifying common start-up logic across connectors

https://issues.jboss.org/browse/DBZ-630

@gunnarmorling - thanks, a great improvement again!
Unfortunately I think it also confuses things a little bit - wrt the naming. Partly are the problems inherited from current basecode and partly are new issues introduced. Please let me explain.
Every task has associated context of type SourceTaskContext. You create a new context calld ConnectorTaskContext. This context is associated with task but the naming implies it can be assocatied with connector too. And how do those two types of TaskContexts differ? I'd like to see a clear name that would distinct those two types. If possible I'd like to neither use expression Task nor Connector. Maybe the plain Context would be enough?
For postgres I see you are using the context in exact way how I think it is envisioned. There is a PostgresTaskContext that is associated with task.
For MongoDB it is less ideal. How is a ConnectionContext that by name says it is something related to connection derived from task? And where is the link between task and its context?
And MySQL is completely confusing now - the task has three! contexts

SourceTaskContext
MySQLTaskContext
MySqlJdbcContext whose name implies it relates to a db connection but inherits from ...TaskContext!

Ideally every task will contain reference to

SourceTaskContext
another context derived from renamed ConnectorTaskContext and this one will contain an optional reference to a context related to connection

This brings me one more question - a task context has 1:1 relationship between task and context. What are rules that defines what should be defined as attributes in task itself and what should go into the context?
I am sorry for the long comment but I hope you understand why I see there are now separate cross-cutting concerns entnagled together.

Hey @jpechane, lots of good questions, and I fully agree it's not ideal yet. But I hope we're on the right path. I did it the proposed way to not be derailed too much from what I'm actually working on, but I'm happy to revisit this and improve it further. I think the following would be a good structure eventually:

Every task (PostgresConnectorTask etc.) has a reference to a corresponding context class, which contains those objects/metadata scoped to the task lifecycle, i.e. a Clock, a XyzConnectorConfig etc.)
These specific context classes should be derived from a common base context which keeps commonalities; that's the ConnectorTaskContext from this PR. We can rename it, SourceTaskContext might work, but it'll conflict with KC's class of the same name. Perhaps CdcSourceTaskContext?
These specific context classes may optionally have references to other contexts, e.g. the ConnectionContext; i.e. there should be a delegation relationship, not an inheritance relationship; this would address your concern for MySQL above; In fact, I had the same concern, I just shied away from doing this right now due to the effort. But it shouldn't be too much, so I guess I'll just do it.

What are rules that defines what should be defined as attributes in task itself and what should go into the context?

I think it's not black and white, but I'd keep an attribute in the task itself if it's just needed there and I'd add it to the context if it's consumed in multiple places, which gets simplified by adding it to the context which can be passed around.
Does that make sense?

@gunnarmorling +1 on all points, that was exatly on my mind, thanks!

@jpechane Pushed an update as per our discussion and rebased, too.

@gunnarmorling Great work, thanks!


Tests: Generator.vue and Generator.spec.ts

Currently, the Generator.vue + Generator.component.ts are covered by Generator.spec.ts
Generator.spec.ts contains some clicks + fill fields etc
But I wonder if we should use create and maintain Generator.component.spec.ts instead
I think about this:

Generator.component.spec.ts would be used to test function in Generator.component.ts
the Cypress part would be used to test click

I created this ticket, because with the current implementation, I found Cypress tests useless as it would do the clicks, like Generator.spec.ts already does
What do you think?
cc @seraphinandrieux @Franceq34 @nonomoho

I totally agree with you.
If we can only test methods into component, go to do it into Generator.component.spec.ts.
Like that, cypress tests will only test user's interactions and displaying.

I agree with you, developping with TDD approach should lead to a Generator.component.spec.ts file that only tests the component. Then, cypress tests will test the html by doing the actions (clicks, forms fill..)

No need it anymore as the main page will be the module one, and it's dynamic


Add variants as data- attributes

Is your feature request related to a problem? Please describe.
This is more of a connivence feature, but it would be great if we could add the value of the variant as a data-.  I tend to make fairly composable objects, and being able to style a child component based on the properties of its parent makes this easier.
An example would be a size variant on a button, with an icon as a child.  The size of the icon needs to change in response to the size on the parent.
Describe the solution you'd like
This is probably more beneficial as an option, maybe in createClassed that allows setting the variants as attributes.
For example if I had
const Button = classed('button', {
  variants: {
    size: {
      normal: 'text-sm',
      small: 'text-xs
    },
  }
})

The usage of the component would stay the same
<Button size='normal' />

But the html that it emits would have data-size="normal"
<button class="text-sm" data-size="normal" />

Thanks for the issue :) I definitely agree this would be a good feature. Especially in terms of testing and css styling. I'll be putting it behind a flag in createClassed useDataVariants or addDataVariants.
It takes a little work to do though as the internals don't expose the matched variants (they actually delete them outright) to avoid React errors.
It will make the lib less performant to allocate extra memory to the matched objects, but only when the feature is enabled.
If you want you can start this work, otherwise I'll start it once I have some time on my hands.

Ya I can take a first pass.
Another idea that I just had was to be selective about which variants we add this for.
At least in my use-case, there are only a couple places where I would need to add it for styling purposes, so it doesn't need to be applied on every attribute.
What are your thoughts on adding a property to the classed call instead.
const Foo = classed('div', {
  variants: {
    size: {lg: '', sm: ''},
    color: {blue: '', red: ''}
  },
  dataAttributes: {
    size: true,
  }
})

This should negate the performance cost unless you actually need it for the specific property.
dataAttributes could probably just be an array or keys as well.
dataAttributes: ['size']

This allows for fine-grained control on which generates the attributes.

Excellent idea!
Fyi if you're getting started. The main variants grouper where dataAttributes gets collected is in the core folder. Only collection needs to happen here, rest can be done in the react directory

I finally found some time to get started on this. I should have a rough, first pass up shortly

v1.5.0.rc-0 is out! All thats missing is documentation of the feature. I have a pretty packed week so wont be able to get it up before sunday I think.


Firefox Support? How to Limit Search Scope?

Would you consider adding Firefox browser functions? I noticed you had an edge function to be able to search just the document area.
I'm trying to do search the "document" area for something but when I do it takes a very long time because I have hundreds of tabs open in the Sidebar--which is considered a "document" area too.
Normally the search through tabs should be quick--it works quickly when I have a browser window open with few tabs.
But I use "Tree Style Tabs" which is an addon that helps manage all these tabs in a side-bar (similar to Edge's vertical tabs feature).
Unfortunately, these are both in the "document" group in the tree... But, the Sidebar document property  is null:
Sidebar document area:

Actual document area:

So if I can do a search to return descendents only where the document is not null, then the search should be much faster. If you see any other way to explicitly define the actual “document” area that would be great, too.
Can you provide examples of limiting the find scope to specific parts of the tree based on various criteria (so that it looks for descendents with the matching scope and doesn’t waste time on other nodes that it should ignore)?

Hello,
Currently I have no plans of supporting Firefox, but I have plans of rewriting the UIA_Browser class to be able to add support for other browsers with less work (to create new classes that extend UIA_Browser, like UIA_Edge and UIA_Firefox).
I have tested Firefox a little bit and had a few thoughts on how to get the browser element:

Easiest way would be to use a bottom-up approach with ElementFromPoint and then normalize to the document element. This is implemented in UIA_Interface as GetChromiumContentElement(WinTitle, False): try documentEl := cUIA.GetChromiumContentElement("ahk_id " cUIA.BrowserId, False). The drawback is that the browser must be at least partially visible for this to work.

The tab names match the document names, so you could first get the selected tab name, and then try to find the document element. If you inspect Firefox with the UIATreeinspector tool, then you can see that the document elements for all tabs seem to be in a regular order: children of the window element are Custom elements with no name and AutomationId of "panel-n-m", for which the first children is a Pane element and then the Document element. So what I would do is first get the selected tab name; then try to FindAll Custom elements (Treescope_Children:=2), and for each of the found elements get the first childs first child (Document element) and check whether the name matches. Speed optimizations might be possible by determining the number of the selected tab, so you could perhaps filter for "AutomationId=panel-1-n".

Okay, UIA_Browser is now rewritten to be more easily extendable to other browsers. I also added some custom methods to support Firefox (inside UIA_Mozilla class), but I still don't plan to fully support it. I don't use Firefox myself, and it was the hardest and most annoying to automate: Javascript cannot be executed through the URL bar; tabs can't be closed with UIA because the close button isn't an UIA element etc... Though it does have the bonus of being able to access non-active tabs' content, other browsers let you access only the active tab.

I am so sorry, I thought I had tested this but obviously not thoroughly enough. It should be fixed now.
Also cUIA.WaitPageLoad("New Tab", 3000) will probably not work, because the title of the browser (for me) is "Mozilla Firefox" not "New Tab", so this will just wait 3 seconds. Also, sometimes WinWaitActive will say the browser is active, but actually the content (buttons, URL bar) hasn't loaded yet, so it's best to add a small sleep as well.
browserExe := "firefox.exe"
Run, %browserExe%
WinWaitActive, ahk_exe %browserExe%
Sleep, 1000
cUIA := new UIA_Browser("ahk_exe " browserExe)
cUIA.WaitPageLoad("Mozilla Firefox", 3000)
cUIA.Navigate("google.com")
cUIA.WaitPageLoad()
MsgBox

@megamorphg, WaitPageLoad doesn't require any parameters: if nothing is provided then in addition to waiting for the page to load (stop button to change back to reload button), the method will also wait for the title to change to the correct one.

I think this might be related to what I mentioned earlier: sometimes WinWaitActive will say the browser is active, but actually the content (buttons, URL bar) hasn't loaded yet, so it's best to add a small sleep after WinWaitActive. Perhaps Sleep 1000 isn't enough? You could try Sleep 2000 for example. This issue is in my "will eventually try to fix" pile, I haven't figured out a good way to achieve it yet.


Abstract over layout

Stage and Actions could also be abstracted away using Group + some Button component.
and configurations api needs to be polished a bit more.


[Release-1.27] overlapping cluster/service address ranges

Backport: https://github.com/k3s-io/k3s/issues/8911

Validated using latest commit id 9edb565d5ea8fe5e1d5d23e0e2c7bc88ff5b5581 on master release-1.27
Results from the dualstack test run
E2E_NODE_ROLES="server-0 agent-0" E2E_NODE_BOXES="generic/ubuntu2004 generic/ubuntu2004"  vagrant up server-0 &> vagrant.log
CLUSTER CONFIG
OS: generic/ubuntu2004
Server Nodes: [server-0]
Agent Nodes: [agent-0]
{"state":"passed","name":"Starts up with no issues","type":"k3s test","time":214401249093}•agent-0    Ready   <none>                      9s     v1.27.8+k3s-9edb565d   <IP_ADDRESS>   <IP_ADDRESS>   Ubuntu 20.04.6 LTS   5.4.0-163-generic   containerd://1.7.11-k3s2.27
server-0   Ready   control-plane,etcd,master   109s   v1.27.8+k3s-9edb565d   <IP_ADDRESS>   <IP_ADDRESS>   Ubuntu 20.04.6 LTS   5.4.0-163-generic   containerd://1.7.11-k3s2.27
{"state":"passed","name":"Checks Node Status","type":"k3s test","time":185289084}•kube-system   coredns-77ccd57875-drssd                 1/1   Running     0     94s   <IP_ADDRESS>   server-0   <none>   <none>
kube-system   helm-install-traefik-crd-s652t           0/1   Completed   0     94s   <IP_ADDRESS>   server-0   <none>   <none>
kube-system   helm-install-traefik-rzlwg               0/1   Completed   2     94s   <IP_ADDRESS>   server-0   <none>   <none>
kube-system   local-path-provisioner-957fdf8bc-5rffz   1/1   Running     0     94s   <IP_ADDRESS>   server-0   <none>   <none>
kube-system   metrics-server-648b5df564-bgc2j          1/1   Running     0     94s   <IP_ADDRESS>   server-0   <none>   <none>
kube-system   svclb-traefik-bf412e29-9lnl6             2/2   Running     0     9s    <IP_ADDRESS>   agent-0    <none>   <none>
kube-system   svclb-traefik-bf412e29-rjl6h             2/2   Running     0     57s   <IP_ADDRESS>   server-0   <none>   <none>
kube-system   traefik-768bdcdcdd-tswbl                 1/1   Running     0     57s   <IP_ADDRESS>   server-0   <none>   <none>
{"state":"passed","name":"Checks Pod Status","type":"k3s test","time":176457556}•{"state":"passed","name":"Verifies that each node has IPv4 and IPv6","type":"k3s test","time":84366382}•{"state":"passed","name":"Verifies that each pod has IPv4 and IPv6","type":"k3s test","time":96671821}•
Deploying dualstack_clusterip.yaml
{"state":"passed","name":"Verifies ClusterIP Service","type":"k3s test","time":30507144989}•
Deploying dualstack_ingress.yaml
{"state":"passed","name":"Verifies Ingress","type":"k3s test","time":566472291}•
Deploying dualstack_nodeport.yaml
{"state":"passed","name":"Verifies NodePort Service","type":"k3s test","time":2665074577}•
Deploying pod_client.yaml

Deploying netpol-fail.yaml

Deploying netpol-work.yaml
{"state":"passed","name":"Verifies podSelector Network Policy","type":"k3s test","time":5821589550}•

Ran 9 of 9 Specs in 263.009 seconds
SUCCESS! -- 9 Passed | 0 Failed | 0 Pending | 0 Skipped

Pods and svcs have different address range
vagrant@server-0:~$ k3s -v
k3s version v1.27.8+k3s-9edb565d (9edb565d)
go version go1.20.11
vagrant@server-0:~$ kubectl get nodes
NAME       STATUS   ROLES                       AGE     VERSION
agent-0    Ready    <none>                      30s     v1.27.8+k3s-9edb565d
server-0   Ready    control-plane,etcd,master   2m10s   v1.27.8+k3s-9edb565d
vagrant@server-0:~$ kubectl get pods -A -o wide
NAMESPACE     NAME                                     READY   STATUS      RESTARTS   AGE    IP          NODE       NOMINATED NODE   READINESS GATES
default       ds-clusterip-pod-f4b45cd86-4qsg4         1/1     Running     0          26s    <IP_ADDRESS>   agent-0    <none>           <none>
default       ds-clusterip-pod-f4b45cd86-6qgms         1/1     Running     0          26s    <IP_ADDRESS>   server-0   <none>           <none>
kube-system   coredns-77ccd57875-drssd                 1/1     Running     0          2m1s   <IP_ADDRESS>   server-0   <none>           <none>
kube-system   helm-install-traefik-crd-s652t           0/1     Completed   0          2m1s   <IP_ADDRESS>   server-0   <none>           <none>
kube-system   helm-install-traefik-rzlwg               0/1     Completed   2          2m1s   <IP_ADDRESS>   server-0   <none>           <none>
kube-system   local-path-provisioner-957fdf8bc-5rffz   1/1     Running     0          2m1s   <IP_ADDRESS>   server-0   <none>           <none>
kube-system   metrics-server-648b5df564-bgc2j          1/1     Running     0          2m1s   <IP_ADDRESS>   server-0   <none>           <none>
kube-system   svclb-traefik-bf412e29-9lnl6             2/2     Running     0          36s    <IP_ADDRESS>   agent-0    <none>           <none>
kube-system   svclb-traefik-bf412e29-rjl6h             2/2     Running     0          84s    <IP_ADDRESS>   server-0   <none>           <none>
kube-system   traefik-768bdcdcdd-tswbl                 1/1     Running     0          84s    <IP_ADDRESS>   server-0   <none>           <none>
vagrant@server-0:~$ kubectl get svc -A
NAMESPACE     NAME               TYPE           CLUSTER-IP      EXTERNAL-IP                                                             PORT(S)                      AGE
default       ds-clusterip-svc   ClusterIP      <IP_ADDRESS>    <none>                                                                  80/TCP                       32s
default       ds-nodeport-svc    NodePort       <IP_ADDRESS>    <none>                                                                  80:30096/TCP                 1s
default       kubernetes         ClusterIP      <IP_ADDRESS>       <none>                                                                  443/TCP                      2m22s
kube-system   kube-dns           ClusterIP      <IP_ADDRESS>      <none>                                                                  53/UDP,53/TCP,9153/TCP       2m18s
kube-system   metrics-server     ClusterIP      <IP_ADDRESS>    <none>                                                                  443/TCP                      2m17s
kube-system   traefik            LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>,<IP_ADDRESS>,fd11:decf:c0ff:ee::10,fd11:decf:c0ff:ee::11   80:32246/TCP,443:30911/TCP   91s


Update Binder target to microsoft:main for GDPCIR dataset

Currently the binder button clones the ClimateImpactLab/PlanetaryComputerExamples fork. This updates to point to the mcirosoft repo's main branch. I just tested this by navigating to the URL and the updated link works correctly.
Parsing the components of the link:
# "launch binder" image
[![Binder](https://mybinder.org/badge_logo.svg)](
    # binder env is a repo we put together with the env alone to minimize build time
    https://mybinder.org/v2/gh/ClimateImpactLab/downscaleCMIP6-binder-env/main?
       # specify git-pull on open
       urlpath=git-pull%3F
            # pull the microsoft/PlanetaryComputerExamples repo
            repo%3Dhttps%253A%252F%252Fgithub.com%252Fmicrosoft%252FPlanetaryComputerExamples%26
            # open jupyterlab
            urlpath%3Dlab%252F
            # open at PlanetaryComputerExamples/datasets/cil-gdpcir/README.md
            tree%252FPlanetaryComputerExamples%252Fdatasets%252Fcil-gdpcir%252FREADME.md%26
            # on branch: main
            branch%3Dmain
)

I put this together with the nbgitpuller tool: https://jupyterhub.github.io/nbgitpuller/link?tab=binder

Thanks!


Invalid path on launching ChocolateyGui

I have recently installed the chocolateygui (from powershell) in Windows 10 Technical Preview 10547 and when I try to launch it it gives me the following error.

Can you help?

In the .config file for ChocolateyGUI, what is the value of the chocolatyInstall variable?  Does this match with where chocolatey is installed on your system?

<appender name="DebugFileAppender" type="log4net.Appender.RollingFileAppender">
  <filter type="log4net.Filter.LevelMatchFilter">
    <levelToMatch value="DEBUG"/>
  </filter>
  <file value="${APPDATA}\\ChocolateyGUI\\Logs\\Chocolatey.gui.debug"/>
  <appendToFile value="true"/>
  <rollingStyle value="Size"/>
  <maxSizeRollBackups value="2"/>
  <maximumFileSize value="10MB"/>
  <staticLogFileName value="true"/>
  <param name="ImmediateFlush" value="true"/>
  <layout type="log4net.Layout.PatternLayout">
    <conversionPattern value="%date [%thread] %level %logger [%ndc] - %message%newline"/>
  </layout>
</appender>

<appender name="FileAppender" type="log4net.Appender.RollingFileAppender">
  <filter type="log4net.Filter.LevelRangeFilter">
    <levelMin value="INFO"/>
    <levelMax value="FATAL"/>
  </filter>
  <file value="${APPDATA}\\ChocolateyGUI\\Logs\\Chocolatey.gui.log"/>
  <appendToFile value="true"/>
  <rollingStyle value="Composite"/>
  <datePattern value="yyyy-MM-dd"/>
  <maximumFileSize value="1MB"/>
  <layout type="log4net.Layout.PatternLayout">
    <conversionPattern value="%date [%thread] %-5level %logger [%ndc] - %message%newline"/>
  </layout>
</appender>

Chocolatey|https://chocolatey.org/api/v2

Chocolatey

@gueland  Actually, sorry, I sent you on a wild goose chase there...
Can you check for the existence of an environment variable called "chocolateyInstall".  What is it's value, and does that path exist on your machine?

No, I don't. The only variable is ChocolatelyPath and the value is C:\Chocolately , which does exist on my machine.

@gueland hmm, this is very strange.  How did you install Chocolatey?  This variable should have been created, and is required in order for both Chocolatey and ChocolateyGUI to function correctly.

I installed it using the git version of the command line (using powershell) package manager.

Sorry, I am really not sure if I follow what you mean.  Can you list out all the steps that you have taken? Thanks!

I have same issue. Installed through OneGet with Chocolatey as a provider(e.g.: Install-Package chocolateygui). Getting exact error on launch.

How did you install chocolatey itself though?

By adding it as a provider for OneGet.

I honestly don't know if we work with Chocolatey installed via OneGet. @ferventcoder ?

You won't need to - Once you have the lib implemented, you have a valid version of a Chocolatey client just as a GUI (I did not read this entire convo).

And we will have the official Chocolatey OneGet provider available coming in the next couple of months, until then consider it a CTP and YMMV.

Installing the ChocolateyGUI through PowerShell PackageManagement with the Chocolatey provider, that is a thing and will work when the official provider is released. HTH.

Good to know. Let me know if this is still broke in the beta version of ChocolateyGUI 0.14!


TaskPlaning App _With Good UI

Hey I want to make Task planing app _flutter , with Good UI
Which contains User Sign In , Sign up with firebase authentication , firebase as backend; and all crud operations !!!
User can plan their tasks like todo , and he can edit , delete , update and create .
Each user has their own tasks to do that's why after user logged in he will get his existed tasks if any from the firebase backend , if not he can create and plan his tasks and also edit , update .
Can you assign this to me , I am interested to contribute myself in hacktoberfest_23 : )

Sure here you go

hey I resolved this issue and I made a PR #108  in this Task_planning app once go through this and merge it _hacktoberfest_23 : )

Hi ,
In the hacktoberfest_23 website it is showing that this repo is excluded or against the rules of hacktoberfest_23 can you please change and maintain the repo according to the rules of hacktoberfest

Hi.
Can you change the repo rules so that it will obey the rules of hacktoberfest_23 , My PR is excluded due to this repo is not obeying the laws or rules of hacktoberfest_23


Display "estimated time" for withdraw

We should have time estimation for withdrawing TOMO after unvote or resign.
We can calculate time estimation from block number.

Implementation pull request:
https://github.com/tomochain/tomomaster/pull/184


[Cosmos] Added HttpLoggingPolicy to pipeline

Rebased version of #8537
Also includes some repo cleanup

Can one of the admins verify this patch?

@bryevdv and @srinathnarayanan
Sorry to bother you with this again, but I just noticed that I never merged this PR you both signed-off on back in November:
https://github.com/Azure/azure-sdk-for-python/pull/8537
I've rebased and reopened - it would be great if you could take a last look so we can merge before GA :)

/azp run python - cosmos - tests


Update 117001.json

Updated "readOnly" values to be writable as per the actual product.

There seems to be have been an error when we created the entry on Zwave Alliance. The config params should be writable.

@kizza42

If the params are read only, remove the attribute entirely.
Its only needed, if the param is read only

You need to use  a Semantic PR title : fix(config): correct readOnly values


Adapt the training data reader and emulator for LUIS to their latest format

Proposed changes:

fix the LUIS part of #6474 and #6993 and #6994 and #6991
update emulator to latest format
update LUIS training data reader to latest format
update documentation (replace screenshot + change some phrases because of recent UI changes)

Status (please check what you already did):

[x] added some tests for the functionality
[x] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

Just seen this now 🙈  Will have a look on Monday! Blazing fast - wanted to hand that over to Joseph actually 😆

@wochinge we actually are still compatible with old ones so we can keep them. What do you think?


Feature: Added detection for Seadrive cloud

Resolved / Related Issues
Items resolved / related issues by this PR.

Closes #9758

Validation
How did you test these changes?

[x] Built and ran the app

Thank you for the PR, can you add this to the documentation site as well?

Yeah, forgot to do it

It's basically the same as #10890


error: could not find Cargo.toml

hello guys!
I've just started to code on Rust and I have a problem)))
I set up PATH for cargo, rustc and rustup like ~\.cargo\bin
and
Problem
I launched VS Code and created a new project and

all code in Cargo.toml in was underlined with a red line (like on the picture)
when I tried to run the project I meet this error
error: could not find Cargo.toml in C:\Users\Green Eagle\Desktop\progr\rust or any parent directory

I would be very grateful if you can help me
thank you)))

and

I would suggest if you're having problems getting started to ask on https://users.rust-lang.org/ or one of the chat channels or other forums.
From a brief glance at your screenshot, it looks like you created a project in a directory named "ggg".  Cargo needs to run within the directory that contains the file Cargo.toml.

thanks, I'll try to ask at the site you mentioned.


Implement Priority Queue visualisations for Dijkstra's Algorithm

The current implemtation of the original Dijkstra's uses a PriorityQueue to order the vertices by it's distance value during the algorithm. When a vertex is polled from the PriorityQueue, it will be highlighted in the animations, however, it may not be clear as to why that specific vertex was chosen. To better represent this, it would benefit users if there could be some sort of ordered list of the vertices as the algorithm progresses.
The ordered list of vertices should ideadly look like the representations of the vertices, colour and all. It would be great if the positions of the vertices could be animated to their final positions (would look cooler + help users identify a change in the state of the pq). The purpose of this is to notify users of the change in distances and choice of vertex to be branched from next, not to represent a heap.

This would be a key defining feature of this project, as far as I am aware, no other simulation tool offers such a visualisation!

dc4e14ccbf4c7b8a77b5f2d9c3ec0f7b6058a678 resolves this.


! Not Loaded after updating Home Assistant

I'm suddenly getting !Not Loaded in the integrations list after updating home assistant. I did also update HACS and the integration and restarted but no luck. I am also unable to remove the integration so I can't force a re-configure. I have tried a "redownload" through HACS also to no avail.
To Reproduce

Simply update Home Assistant to: core-2021.12.0b6, supervisor-2021.12.1

Expected behavior
Alexa media player to load or at least be removable
Screenshots

System details

Home-assistant (version): core-2021.12.0b6, supervisor-2021.12.1
Hassio (Yes/No): YES
alexa_media  (version from const.py or HA startup): 3.10.12
alexapy (version from pip show alexapy or HA startup): Can't seem to sort how to see this
Amazon 2FA is enabled (y/n). YES

Logs
These two errors in the logs are almost certainly pointing at the problem. I'm just not sure how to sort it out since I can't seem to remove the integration
This error originated from a custom integration.
Logger: homeassistant.setup
Source: custom_components/alexa_media/init.py:16
Integration: Alexa Media Player (documentation, issues)
First occurred: 3:37:41 PM (1 occurrences)
Last logged: 3:37:41 PM
Setup failed for alexa_media: unknown error
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 181, in _async_setup_component
component = integration.get_component()
File "/usr/src/homeassistant/homeassistant/loader.py", line 522, in get_component
cache[self.domain] = importlib.import_module(self.pkg_path)
File "/usr/local/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/config/custom_components/alexa_media/init.py", line 16, in
from alexapy import (
File "/usr/local/lib/python3.9/site-packages/alexapy/init.py", line 16, in
from .alexaapi import AlexaAPI
File "/usr/local/lib/python3.9/site-packages/alexapy/alexaapi.py", line 21, in
from alexapy.aiohttp import ClientConnectionError, ClientResponse
File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/init.py", line 6, in
from .client import (
File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/client.py", line 35, in
from . import hdrs, http, payload
File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/http.py", line 7, in
from .http_parser import (
File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/http_parser.py", line 15, in
from .helpers import NO_EXTENSIONS, BaseTimerContext
File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/helpers.py", line 667, in
class CeilTimeout(async_timeout.timeout):
TypeError: function() argument 'code' must be code, not str
This error originated from a custom integration.
Logger: aiohttp.server
Source: custom_components/alexa_media/init.py:16
Integration: Alexa Media Player (documentation, issues)
First occurred: 3:40:54 PM (1 occurrences)
Last logged: 3:40:54 PM
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
resp = await request_handler(request)
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_app.py", line 504, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.9/site-packages/aiohttp/web_middlewares.py", line 117, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 98, in forwarded_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 78, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 181, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 137, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 71, in delete
result = await hass.config_entries.async_remove(entry_id)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 831, in async_remove
await entry.async_remove(self.hass)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 487, in async_remove
component = integration.get_component()
File "/usr/src/homeassistant/homeassistant/loader.py", line 522, in get_component
cache[self.domain] = importlib.import_module(self.pkg_path)
File "/usr/local/lib/python3.9/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/config/custom_components/alexa_media/init.py", line 16, in
from alexapy import (
File "/usr/local/lib/python3.9/site-packages/alexapy/init.py", line 16, in
from .alexaapi import AlexaAPI
File "/usr/local/lib/python3.9/site-packages/alexapy/alexaapi.py", line 21, in
from alexapy.aiohttp import ClientConnectionError, ClientResponse
File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/init.py", line 6, in
from .client import (
File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/client.py", line 35, in
from . import hdrs, http, payload
File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/http.py", line 7, in
from .http_parser import (
File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/http_parser.py", line 15, in
from .helpers import NO_EXTENSIONS, BaseTimerContext
File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/helpers.py", line 667, in
class CeilTimeout(async_timeout.timeout):
TypeError: function() argument 'code' must be code, not str

Same errors here, after updating to 2021.12.1

same her after updating to 2021.12
Not loaded

Dupe of #1446

I fixed it with re-download the integration (3.10.15) in HACS and restart HA

After you apply the HA update go into HACS and you should see a pending update for Alexa Media Player, update AMP and restart HA. Afterwards AMP should load properly.


Collect PodDisruptionBudgets in Cluster Agent

What does this PR do?
Collect PodDisruptionBudgets in Cluster Agent.
Motivation
Collect PDB information.
Describe how to test/QA your changes
Tested locally:

Created Minikube cluster
Deployed cluster agent with image build from the code in the PR
Created cluster role and binding to give PDB get, list, and watch permissions to the cluster agent
Configured the agent to collect PDBs
Created a PDB in the cluster

The agent reports observing the PDB, doesn't crash.
TDB: verify no change in CPU load.
Possible Drawbacks / Trade-offs
Additional Notes
Needs https://github.com/DataDog/agent-payload/pull/351 to be submitted and pulled in properly before this can be submitted.

/merge


Unable to submit iOS app to Apple with cordova-plugin-googlemaps

I'm submitting a ...  (check one with "x")
[ ] question
[x] any problem or bug report
[ ] feature request
If you choose 'problem or bug report', please select OS:  (check one with "x")
[ ] Android
[x ] iOS
Current behavior:

I make build from https://build.phonegap.com and try to upload from x-code application loader and got this error.
ERROR ITMS-90596: "Invalid Bundle. The asset catalog at 'Payload/Default.app/GoogleMaps.bundle/GMSCoreResources.bundle/Assets.car' can't be read. Try rebuilding the app with a non-beta version of Xcode and submit it again."
cordova information:
<gap:plugin name="cordova-plugin-geolocation" source="npm" />
<gap:plugin spec="https://github.com/mapsplugin/cordova-plugin-googlemaps.git" source="git" >

</gap:plugin>

Please ask to PhoneGap build team. Not plug-in's problem.


bug(python): querying multiple vectors in local python sync SDK gives error

LanceDB version
v0.16.0
What happened?
https://github.com/lancedb/lancedb/pull/1811 added this for async (remote and local) and remote sync, but not local sync.
Are there known steps to reproduce?
Unit test you can add to test_query.py:
def test_query_multiple(table):
    results = table.search([np.array([1, 2]), np.array([4, 5])]).limit(1).to_list()
    assert len(results) == 2

It's not urgent to fix this, as users can add their own threadpool. We should probably just wait until we do https://github.com/lancedb/lancedb/issues/1792, as we need to do that migration anyways, and that migration will delete all sync-API specific implementations anyways.


Traceback issue:

For some of the APKs, I get this:
`Traceback (most recent call last):
File "LibRadar/libradar.py", line 215, in
res = lrd.analyse()
File "LibRadar/libradar.py", line 195, in analyse
self.unzip()
File "LibRadar/libradar.py", line 87, in unzip
zf = zipfile.ZipFile(self.apk_path, mode='r')
File "/usr/lib/python2.7/zipfile.py", line 770, in init
self._RealGetContents()
File "/usr/lib/python2.7/zipfile.py", line 811, in _RealGetContents
raise BadZipfile, "File is not a zip file"
zipfile.BadZipfile: File is not a zip file
`

As we all know that apk file is a kind of Zip.
you could use zip tools to unzip any apk file.
If an apk could not be unzipped, it must be broken.


Fixing some RooArgSet assignments

This fixes the addition of parameters to existing RooArgSets (can only add to an existing RooArgSet, not assign the contents of another RooArgSet)

Can this also be injected into the main branch?

I don't think it's broken on the main branch, the problem was only introduced by the addition of some new features on comb2017

Merging this since once we pull the bugged feature into the main branch, this will fix it


[Bug]: memgraph containers not running with least privilege security context

What happened?
I'd like to suggest a couple of improvements to the securityContext in the StatefulSet of standalone memgraph helm chart. I've successfully tested these in our installation with the chart version 0.1.3:
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: residency
spec:
  template:
    spec:
      initContainers:
        - name: init-volume-mounts
          securityContext:
            # Runs only chown on the mounted PVC so no need to write to root fs
            readOnlyRootFilesystem: true
            # `ALL` instead of `all` - case matters, see https://github.com/kubernetes/pod-security-admission/issues/11
            capabilities:
              drop:
                - ALL
      containers:
        - name: memgraph
          securityContext:
            allowPrivilegeEscalation: false
            runAsNonRoot: true
            runAsUser: 101
            capabilities:
              drop:
                - ALL

In addition it may be helpful to add the securityContext settings to the default values to make it more transparent and allow users to change them in case of edge cases that may not work with the defaults.
Chart type
Standalone
Chart version
0.1.3
Environment
Kubernetes 1.27
Relevant log output
No response

Hi @tmyhu, thanks for bringing this to our attention and opening the issue, I will take a look.

The security context set to privileged: true prevents the helm chart from running on Google Kubernetes Engine (GKE)

HI @ricker-flow thanks for communicating this, this is currently true for running the init-containers before Memgraph is being run and setting the ownership of volumes, I wasn't aware GKE blocks this.
 I guess we should look at how to fix that permission issue.

There is no need to run containerInit. Instead set securityContext.
This is the entire stateful set spec that works on GKE. No privileges needed. File ownership is automatic.
spec:
  podManagementPolicy: OrderedReady
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/instance: memgraph
      app.kubernetes.io/name: memgraph
  serviceName: memgraph
  template:
    metadata:
      labels:
        app.kubernetes.io/instance: memgraph
        app.kubernetes.io/name: memgraph
        app.kubernetes.io/version: 2.20.0
    spec:
      securityContext:
        runAsUser: 1000
        runAsGroup: 3000
        fsGroup: 2000
      containers:
        - args:
            - --also-log-to-stderr=true
          image: memgraph/memgraph:2.20.0
          imagePullPolicy: IfNotPresent
          name: memgraph
          ports:
            - containerPort: 7687
              name: bolt
            - containerPort: 7444
              name: websocket
            - containerPort: 9091
              name: http
          securityContext:
            allowPrivilegeEscalation: false
          volumeMounts:
            - mountPath: /var/lib/memgraph
              name: memgraph-lib-storage
            - mountPath: /var/log/memgraph
              name: memgraph-lib-storage
      terminationGracePeriodSeconds: 1800
      volumes:
        - name: memgraph-lib-storage
          persistentVolumeClaim:
            claimName: memgraph-lib-storage
        - name: memgraph-log-storage
          persistentVolumeClaim:
            claimName: memgraph-log-storage

My mind is telling me that we had a similar configuration at some point, but something was not working. Let me give this another shot.
Thanks for sharing this. 🚀  @ricker-flow


node request package using in synth

Good evening Jon Abrams.
I have one task.
I have to make http request in back-end to the api of backendless.com with "request" package of nodejs. I do such action, because front-end user shouldn't see api keys of backendless from any js file.
When i print recieved data to node console i see data, but when i return this data to front-end i don't see anything printing it to console.
Could you help with this issue?
Back-end code:
var request = require('request');
exports.getIndex = function(db) {
    request({
        uri: "https://api.backendless.com/v1/data/ib_companies?where=index_slider%3Dtrue", //o`
        method: "GET",
        headers: global.BackendlessApp
    }, function(error, response, body) {
        console.log(response);
        return response;

    });

};

Front-end code:
$http.get('/api/home' + $location.path()).then(function(res) {
    console.log(res);
});

You'll need to use a promise friendly version of request, such as request-promise.
Your code would look something like:
var request = require('request-promise');
exports.getIndex = function(db) {
    return request({
        uri: "https://api.backendless.com/v1/data/ib_companies?where=index_slider%3Dtrue", //o`
        method: "GET",
        headers: global.BackendlessApp
    }).then(function (body) {
        return JSON.parse(body);
    });
};


Security hardening article should have stronger warning against using actions secrets

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions and/or https://docs.github.com/en/actions/security-guides/encrypted-secrets
What part(s) of the article would you like to see updated?
Actions secrets are extremely risky to use in a public repo because they could potentially be exfiltrated by anyone who's allowed to run a PR build. The articles linked above should more explicitly mention this risk and strongly recommend moving sensitive secrets (such as npm tokens) to environments or another solution, as well as requiring approval for outside collaborators to run PR workflows.
In the mitigation suggestions, it would be very helpful to include an example of how to use an environment solely to control secret access. The terms "environment" and "deployment" are confusing in the context of something like npm publishing which isn't typically thought of in those terms (especially for anyone who's worked on a service in the past), so developers may not realize environments can be used for that and how simple it is to set up. (I've worked on build systems in open source repos for multiple years, and despite having read through the security articles at some point, I didn't figure this out until last week.)
The "security hardening" article has also gotten extremely long, so it would probably be more readable as an overview article with multiple sub-pages.
Additional information
No response

@ecraig12345 Thanks so much for opening an issue! We appreciate the depth of info and details in supporting the issue. I'll triage this for the team to take a look :eyes:

Hey @ecraig12345 ✨
Thank you for making this issue and helping keep our docs updated with some security best practices. I read through your suggestion and am curious if what you're asking for is currently written in the documentation. Let me know if I'm mistaken here!
Examples

Actions secrets are extremely risky to use in a public repo because they could potentially be exfiltrated

The docs do have a section specifically about exfiltration.

could potentially be exfiltrated by anyone who's allowed to run a PR build

Under "Using secrets" there is a strong, red warning box that says, "Any user with write access to your repository has read access to all secrets configured in your repository. Therefore, you should ensure that the credentials being used within workflows have the least privileges required."
Does this warning box is cover the scenario you're asking about for public repositories?

and strongly recommend moving sensitive secrets (such as npm tokens) to environments or another solution

The first paragraph under "Using secrets" explains that secrets can be set at the environment level for the repository and links to the relevant documentation. Do you think this approach should be a stronger recommendation?

as well as requiring approval for outside collaborators to run PR workflows.

One of the bullet points in "Using secrets" says "Consider requiring review for access to secrets." The section also talks about environment secrets and links out to the relevant docs. Which is closely related to your suggestions about recommending environment secrets.
My questions
It might be that the right information does exist in the article, but it needs to be highlighted differently or reworded. Or it might be that important information is missing entirely. It'll be helpful for me to know the case either way.
Is there specific information that is totally missing in Security hardening for GitHub Actions or "Encrypted secrets" articles?
Or is it that certain important information about secrets should be displayed/highlighted better?
Let me know what you think!


Question on branches

Hi there,
I just noticed Aidstream has +500 branches. (https://github.com/younginnovations/aidstream/branches)
Is there a specific reason to have that many?
Thanks, Siem

@anjesh bump.

@siemvaessen apologies for the long silence. you are right about the branches, the number is high, which people don't have to know. They are our part of the internal gitflows and we have mirrored our internal repo with github and hence you are seeing them. We are planning to enable mirror for the master branch only, rather than entire repo. Thanks for noticing :)


Ember build -prod --> Error: Broken @import declaration of "theme.css"

When made a build in ember-cli 2.6.1
On OS X El Capitan and Windows 10 I try to build Ember build -prod and produce Error: Broken @import declaration of "theme.css"

Are you compiling the css from the semantic less?

No semantic less, it could be closed, was related to ember-cli broccoli, now updated and working great

Great thanks


How can i print center align barcode?

I need print center align barcode on the bill (barcode on the top). How can help me?
Thanks for your support

the first, I print barcode on the top. Then i print image, after.

I was not able to print the barcode with the given command , the function only prints text which is mention in barcode ,   @tranhung148 can you please tell me some details how you printed the barcode using this lib.

How about the demo? Besides, plz provide more information about what your are attending to print.
发自我的 iPhone

在 2019年3月7日，下午4:52，VISHAL GUPTA<EMAIL_ADDRESS>写道：
I was not able to print the barcode with the given command , the function only prints text which is mention in barcode , @tranhung148 can you please tell me some details how you printed the barcode using this lib.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

i am using this function BluetoothEscposPrinter.printBarCode('1234', 128, 20, 20, 1, 2);

only 1234 is printed

And for this
            width: 40,
            height: 30,
            gap: 20,
            direction: BluetoothTscPrinter.DIRECTION.FORWARD,
            reference: [0, 0],
            tear: BluetoothTscPrinter.TEAR.ON,
            sound: 0,
            text: [{
                text: finalString,
                x: 20,
                y: 0,
                encoding: 'GBK',
                fonttype: BluetoothTscPrinter.FONTTYPE.SIMPLIFIED_CHINESE,
                rotation: BluetoothTscPrinter.ROTATION.ROTATION_0,
                xscal: BluetoothTscPrinter.FONTMUL.MUL_1,
                yscal: BluetoothTscPrinter.FONTMUL.MUL_1,
            }],

            barcode: [{
                x: 120,
                y: 96,
                type: BluetoothTscPrinter.BARCODETYPE.CODE128,
                height: 40,
                readable: 1,
                rotation: BluetoothTscPrinter.ROTATION.ROTATION_0,
                code: '1234567890',
                wide: 30,
                narrow: 30,

            }],

        };
BluetoothTscPrinter.printLabel(options)
            .then(
                 () => {
                 // success
                 },
                 (err) => {
                 // error
                 },

     );

for this only value<PHONE_NUMBER> is being printed

@januslo thank you so much for this lib dude it works.

I suffers the same problem in ESC/POS .

thanks so much


Better exception message for unsupported Layout kdim combinations

Right now we don't support a Layout of a HoloMap over one dimension (say 'Time') and another with a different dimension (say 'Duration'). This is something we hope to improve in the future so it is allowed but in the meantime it would really be helpful to raise a better exception when such illegal combinations are attempted.

This is now supported for DynamicMap and two HoloMap objects combined into a Layout raise this error:
hv.HoloMap({i: hv.Curve([]) for i in range(3)}, kdims=['X']) +\
hv.HoloMap({i: hv.Curve([]) for i in range(3)}, kdims=['Y'])

ValueError: When combining HoloMaps into a composite plot their dimensions must be subsets of each other.

I think that does address this issue. Closing.


add link to health chart

We really need to parameterize this, but until then, put it by the other link.

Maybe also put this inline at http://submit-queue.k8s.io/#/info?

It's kind of ugly for an inline chart.

I actually just put it inline now. I can't figure out the magic CSS incantation to make it shrink down nicely in the amount of time I'm willing to spend on CSS (hint: not much).

OK inlined in two places now.

Actually maybe inlining is bad unless it also refreshes occasionally?

It doesn't refresh automatically. You probably want style="max-width: 800px" or something on the element to resize it (but it might be ugly).

I tried max-width: 100% and that didn't seem to work...
On Mon, Jun 20, 2016 at 3:03 PM, Ryan Hitchman<EMAIL_ADDRESS>wrote:

It doesn't refresh automatically. You probably want style="max-width:
800px" or something on the element to resize it (but it might be ugly).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/contrib/pull/1243#issuecomment-227283798,
or mute the thread
https://github.com/notifications/unsubscribe/AAnglouLtAb1dLKX_dTXWqZqii2R_UlTks5qNw4ygaJpZM4I6H9t
.

style="max-width:100%"  appears to work for me?

hm, I'll try again

Seems to work now. Not sure what I did before.

LGTM


Can we anonymize the PGP key configuration?

Is there a way that we can anonymize (or use a dedicated key not from an individual at IBM)?
tools/pgp_key_gen.conf
Showing the top two matches Last indexed 6 days ago
Name-Real: Vincent Hou
Name-Comment: Release manager of OpenWhisk
Name-Email<EMAIL_ADDRESS>Expire-Date: 0
Passphrase: openwhisk
%commit
%echo done

tools/travis/import_pgp_key.sh
Showing the top two matches Last indexed 12 hours ago
gpg --allow-secret-key-import --import $PARENTDIR/key_sec.gpg

expect -c "spawn gpg --edit-key<EMAIL_ADDRESS>trust quit; send \"5\ry\r\"; expect eof"

@mrutkows I am wondering if we have a dedicated account, which is able to access apache svn. I would like to remove my credentials as well.
@csantanapr Do we have one?

I gave the following feedback:
Do the testing of the release in Travis. (deploy openwhis, run some tests)
Do the zip/tar, md5 and sign on Apache Jenkins.
Apache Jenkins nodes are already configure with svn
Here is an example of a Job https://builds.apache.org/view/Incubator Projects/job/incubator-netbeans-html4j-release
I suggest to create a jenkins job, where release manager for the week can enter some form fields if necessary and start jenkins job, this will kick Travis to run testing, then when done, continue with tar/zip, sign, md5, and copy to svn.
Or have release manager tag the repo, and this kicks Travis, and then Travis kicks jenkins to do zip/tar, sign, md5, and copy to svn
The PGP key can be generated with apache id of one of the PPMC member<EMAIL_ADDRESS>like
Like netbean project
Signed with my<EMAIL_ADDRESS>key approved for NetBeans project with command:
$ gpg -u f4c8f51d -ab incubating-netbeans-html4j-1.5.1.zip
$ cat incubating-netbeans-html4j-1.5.1.zip.asc

@csantanapr I think it is more straight forward that we can manage all the steps here in Travis. Otherwise, it is complicated to trigger another Jenkins job in Travis job. It will be more difficult to maintain.
Currently, I encrypt personal credentials to sign and update the SVN. As long as we have a general SVN account(usernane and password), I can encrypt it in travis. For PGP signature, I can change it to an apache id.

For SVN, I currently encrypted my username and password in Travis to access the SVN.
For PGP signature, I can change the name and email address to any name and address, even virtual ones, because they have just been used as an identity marker to indicate who signed the artifacts.

Yeah encrypting the all the bits in Travis also works for me


[AMQ-9218] Jakarta transition module for activemq-client

#983 should merge first, and we can re-base this without j2ee spec

Cleaned up the dependency:tree for application users to have a cleaner transitive dependency tree.

[x] Set activemq-client as 'provided'
[x] Directly depend on slf4j
[x] Directly depend on hawtbuf

[INFO] org.apache.activemq:activemq-client-jakarta:bundle:5.18.0-SNAPSHOT
[INFO] +- org.apache.activemq:activemq-client:jar:5.18.0-SNAPSHOT:provided
[INFO] +- jakarta.jms:jakarta.jms-api:jar:3.1.0:compile
[INFO] +- org.fusesource.hawtbuf:hawtbuf:jar:1.11:compile
[INFO] +- org.slf4j:slf4j-api:jar:1.7.36:compile
[INFO] +- com.thoughtworks.xstream:xstream:jar:1.4.20:provided
[INFO] |  \- io.github.x-stream:mxparser:jar:1.2.2:provided
[INFO] |     \- xmlpull:xmlpull:jar:<IP_ADDRESS>:provided
[INFO] \- junit:junit:jar:4.13.2:test
[INFO]    \- org.hamcrest:hamcrest-core:jar:1.3:test

@mattrpav - going forward instead of always force pushing it's probably better to just push new commits. The issue is any comments/history get blown away every time you force push so I can't see what you changed from the last time. This is ok for small stuff but is annoying for larger commits.
The best workflow I have found is what is used on Apache Accumulo:

Push new commits as you make changes, don't force push
If you want to get the latest changes from the original branch (ie main) don't rebase off main as then you'd have to force push. Instead just merge main into this branch periodically and push up the commit. ie "git merge main"
When it comes time to do the final merge, pick the "Squash and merge" option. This will squash everything into 1 commit and add it to the end so we essentially get the same effect as if you had force pushed and re-based but the history doesn't always get blown away. When you pick this option it allows you to modify the commit message so you can change it before the final merge.


Error: bsp_download.sh: No such file or directory

I am following the Hello tutorial for MyNewt and while executing command:
newt load nrf 52_boot
I am getting an error:
Error: /bin/bash: C:\Workspace\myproj\repos\apache-mynewt-core\hw\bsp\nordic_pca10040\nordic_pca10040_download.sh: No such file or directory
even though the file exists.
I am working on Windows 10 and that happens in CMD, GitBash, MSYS bash and VSCode bash.

Not sure if there is any path related issue on windows. It may help if you paste the output with debug enabled
newt load -ldebug nrf52...

Not sure if there is any path related issue on windows. It may help if you paste the output with debug enabled
newt load -ldebug nrf52...

Here is the output with debug enabled:
https://semcon-my.sharepoint.com/:t:/p/krzysztof_dabek/EUbQbm37t7NHryZgVF-q8tcBdc8xFDwfk9ZHLpJLDUkLEA?e=b7jrk3

From your logs, it seems like you are missing
https://github.com/apache/mynewt-newt/pull/403. That change is for executing .sh scripts with bash on windows.
You could try building the latest mynewt-newt (See: https://github.com/apache/mynewt-newt/blob/master/INSTALLING.md)

Same issue on the latest version 1.9.0 dev

commit 8330e7f8bd6570e2bccb73377b115ab78541933d
Author: J. Ipanienko<EMAIL_ADDRESS>Date:   Wed Feb 19 13:19:16 2020 -0800

    Execute .sh scripts with bash on windows

This commit is newer than 1.9.0-dev (c5d1e422bfa335b3b58589eca2401ec3616e889e) release. I suspect you may have to try with the HEAD of master branch. @jipanienko could you please see if this issue is addressed by your fix?

Still no luck. Anything I could have missed?

I've just tested with msys (64 bit) and it seems to be working just fine on Windows 10.
It is weird that path in error message from bash is with windows slash instead of unix backslash...

How do you build newt from master ? I'm using go installed in msys via pacman (not Windows one)
run msys64 shell with admin privileges (otherwise symlinks are not working correctly)

@nkaje no, unrelated problem.
More like strange (non msys) bash in PATH


Add support for reporting references to discontinued specs

Dry-running it gives the following output (to be compared with https://github.com/w3c/webref/issues/1096)
Downloading HTML spec fragments data…

done
Opening crawl results ../webref/ed/index.json and ../webref/tr/index.json…
done
Running references analysis…
done
Compiling discontinuedReferences report for HTML Standard…

Would add issues/html-discontinuedreferences.md with
Repo: 'https://github.com/whatwg/html'
Tracked: N/A
Title: Normative references to discontinued specs in HTML Standard
While crawling HTML Standard, the following normative referenced were detected as pointing to discontinued specifications:

[ ] HTTP has been obsoleted by rfc9110,rfc9112

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Navigational-Tracking Mitigations…
Would add issues/nav-tracking-mitigations-discontinuedreferences.md with
Repo: 'https://github.com/privacycg/nav-tracking-mitigations'
Tracked: N/A
Title: >-
Normative references to discontinued specs in Navigational-Tracking
Mitigations
While crawling Navigational-Tracking Mitigations, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7234 has been obsoleted by rfc9111

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Media Feeds…
Would add issues/media-feeds-discontinuedreferences.md with
Repo: 'https://github.com/WICG/media-feeds'
Tracked: N/A
Title: Normative references to discontinued specs in Media Feeds
While crawling Media Feeds, the following normative referenced were detected as pointing to discontinued specifications:

[ ] rfc7231 has been obsoleted by rfc9110

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Network Information API…
Would add issues/netinfo-discontinuedreferences.md with
Repo: 'https://github.com/WICG/netinfo'
Tracked: N/A
Title: Normative references to discontinued specs in Network Information API
While crawling Network Information API, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7231 has been obsoleted by rfc9110

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Save Data API…
Would add issues/savedata-discontinuedreferences.md with
Repo: 'https://github.com/WICG/savedata'
Tracked: N/A
Title: Normative references to discontinued specs in Save Data API
While crawling Save Data API, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7231 has been obsoleted by rfc9110

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Loading Signed Exchanges…
Would add issues/webpackage-discontinuedreferences.md with
Repo: 'https://github.com/WICG/webpackage'
Tracked: N/A
Title: Normative references to discontinued specs in Loading Signed Exchanges
While crawling Loading Signed Exchanges, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7230 has been obsoleted by rfc9110,rfc9112
[ ] RFC7231 has been obsoleted by rfc9110

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for A Well-Known URL for Changing Passwords…
Would add issues/change-password-url-discontinuedreferences.md with
Repo: 'https://github.com/w3c/webappsec-change-password-url'
Tracked: N/A
Title: >-
Normative references to discontinued specs in A Well-Known URL for Changing
Passwords
While crawling A Well-Known URL for Changing Passwords, the following normative referenced were detected as pointing to discontinued specifications:

[ ] HTTP-SEMANTICS has been obsoleted by rfc9110

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Clear Site Data…
Would add issues/clear-site-data-discontinuedreferences.md with
Repo: 'https://github.com/w3c/webappsec-clear-site-data'
Tracked: N/A
Title: Normative references to discontinued specs in Clear Site Data
While crawling Clear Site Data, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7230 has been obsoleted by rfc9110,rfc9112
[ ] RFC7234 has been obsoleted by rfc9111

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Content Security Policy Level 3…
Would add issues/CSP3-discontinuedreferences.md with
Repo: 'https://github.com/w3c/webappsec-csp'
Tracked: N/A
Title: Normative references to discontinued specs in Content Security Policy Level 3
While crawling Content Security Policy Level 3, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7231 has been obsoleted by rfc9110

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for EPUB Reading Systems 3.3…
Would add issues/epub-rs-33-discontinuedreferences.md with
Repo: 'https://github.com/w3c/epub-specs'
Tracked: N/A
Title: >-
[epub-rs-33] Normative references to discontinued specs in EPUB Reading
Systems 3.3
While crawling EPUB Reading Systems 3.3, the following normative referenced were detected as pointing to discontinued specifications:

[ ] rfc7230 has been obsoleted by rfc9110,rfc9112

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Mathematical Markup Language (MathML) Version 4.0…
Would add issues/mathml4-discontinuedreferences.md with
Repo: 'https://github.com/w3c/mathml'
Tracked: N/A
Title: >-
Normative references to discontinued specs in Mathematical Markup Language
(MathML) Version 4.0
While crawling Mathematical Markup Language (MathML) Version 4.0, the following normative referenced were detected as pointing to discontinued specifications:

[ ] HTTP11 has been obsoleted by rfc9110,rfc9112

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Navigation Timing Level 2…
Would add issues/navigation-timing-2-discontinuedreferences.md with
Repo: 'https://github.com/w3c/navigation-timing'
Tracked: N/A
Title: Normative references to discontinued specs in Navigation Timing Level 2
While crawling Navigation Timing Level 2, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7234 has been obsoleted by rfc9111

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Network Error Logging…
Would add issues/network-error-logging-discontinuedreferences.md with
Repo: 'https://github.com/w3c/network-error-logging'
Tracked: N/A
Title: Normative references to discontinued specs in Network Error Logging
While crawling Network Error Logging, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7230 has been obsoleted by rfc9110,rfc9112
[ ] RFC7231 has been obsoleted by rfc9110
[ ] RFC7232 has been obsoleted by rfc9110
[ ] RFC7234 has been obsoleted by rfc9111

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Push API…
Would add issues/push-api-discontinuedreferences.md with
Repo: 'https://github.com/w3c/push-api'
Tracked: N/A
Title: Normative references to discontinued specs in Push API
While crawling Push API, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7231 has been obsoleted by rfc9110

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Referrer Policy…
Would add issues/referrer-policy-discontinuedreferences.md with
Repo: 'https://github.com/w3c/webappsec-referrer-policy'
Tracked: N/A
Title: Normative references to discontinued specs in Referrer Policy
While crawling Referrer Policy, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7231 has been obsoleted by rfc9110

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Resource Timing…
Would add issues/resource-timing-discontinuedreferences.md with
Repo: 'https://github.com/w3c/resource-timing'
Tracked: N/A
Title: Normative references to discontinued specs in Resource Timing
While crawling Resource Timing, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7230 has been obsoleted by rfc9110,rfc9112

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Server Timing…
Would add issues/server-timing-discontinuedreferences.md with
Repo: 'https://github.com/w3c/server-timing'
Tracked: N/A
Title: Normative references to discontinued specs in Server Timing
While crawling Server Timing, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7230 has been obsoleted by rfc9110,rfc9112

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Service Workers Nightly…
Would add issues/service-workers-discontinuedreferences.md with
Repo: 'https://github.com/w3c/ServiceWorker'
Tracked: N/A
Title: Normative references to discontinued specs in Service Workers Nightly
While crawling Service Workers Nightly, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7230 has been obsoleted by rfc9110,rfc9112
[ ] RFC7231 has been obsoleted by rfc9110

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Subresource Integrity…
Would add issues/SRI-discontinuedreferences.md with
Repo: 'https://github.com/w3c/webappsec-subresource-integrity'
Tracked: N/A
Title: Normative references to discontinued specs in Subresource Integrity
While crawling Subresource Integrity, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7234 has been obsoleted by rfc9111

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Scalable Vector Graphics (SVG) 2…
Would add issues/SVG2-discontinuedreferences.md with
Repo: 'https://github.com/w3c/svgwg'
Tracked: N/A
Title: >-
[SVG2] Normative references to discontinued specs in Scalable Vector Graphics
(SVG) 2
While crawling Scalable Vector Graphics (SVG) 2, the following normative referenced were detected as pointing to discontinued specifications:

[ ] DOM-Level-2-Style is discontinued, no known replacement reference

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Upgrade Insecure Requests…
Would add issues/upgrade-insecure-requests-discontinuedreferences.md with
Repo: 'https://github.com/w3c/webappsec-upgrade-insecure-requests'
Tracked: N/A
Title: Normative references to discontinued specs in Upgrade Insecure Requests
While crawling Upgrade Insecure Requests, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7231 has been obsoleted by rfc9110

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for WebDriver…
Would add issues/webdriver2-discontinuedreferences.md with
Repo: 'https://github.com/w3c/webdriver'
Tracked: N/A
Title: Normative references to discontinued specs in WebDriver
While crawling WebDriver, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7230 has been obsoleted by rfc9110,rfc9112
[ ] RFC7231 has been obsoleted by rfc9110
[ ] RFC7232 has been obsoleted by rfc9110
[ ] RFC7234 has been obsoleted by rfc9111
[ ] RFC7235 has been obsoleted by rfc9110

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Tracking Preference Expression (DNT)…
Tracking Preference Expression (DNT) is discontinued, skipping

(compared to https://github.com/w3c/webref/issues/1096 the report only focuses on normative references, not links in general; I think it probably is the sufficient result for actually removing the specs from webref unless I'm mistaken, although maybe informative references should be checked as well)

https://github.com/w3c/browser-specs/pull/1143 would likely lead to having more specs identified (e.g. the ones in JSON-LD)

(compared to w3c/webref#1096 the report only focuses on normative references, not links in general; I think it probably is the sufficient result for actually removing the specs from webref unless I'm mistaken, although maybe informative references should be checked as well)

I would also check informative references.
I'm not sure how to define sufficient result but the motivation to keep these specs in Webref right now is that removing them would break the generation of some specs. If the outdated RFCs disappear from the list of references, that should mean that the spec no longer targets sections in them. If the outdated RFCs disappear from the list of normative references but still exist in the list of informative references, the spec may still target sections in them, and thus generation will continue to fail if the spec uses Bikeshed.

I'm not sure I would want to have strudy automatically submit issues for informative references on an ongoing basis, since in general, there may be good reasons to refer informatively to an outdated specs.
We may still want to use it to automate filing issues for this particular transition though (maybe filtering it only to bikesped specs). The list generated for informative references would be:
Downloading HTML spec fragments data…

done
Opening crawl results ../webref/ed/index.json and ../webref/tr/index.json…
done
Running references analysis…
done
Compiling discontinuedReferences report for Navigational-Tracking Mitigations…

Would add issues/nav-tracking-mitigations-discontinuedreferences.md with

Repo: 'https://github.com/privacycg/nav-tracking-mitigations'
Tracked: N/A
Title: >-
Normative references to discontinued specs in Navigational-Tracking
Mitigations
While crawling Navigational-Tracking Mitigations, the following normative referenced were detected as pointing to discontinued specifications:

[ ] TRACKING-DNT is discontinued, no known replacement reference

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Compression Streams…
Would add issues/compression-discontinuedreferences.md with

Repo: 'https://github.com/WICG/compression'
Tracked: N/A
Title: Normative references to discontinued specs in Compression Streams
While crawling Compression Streams, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7230 has been obsoleted by rfc9110,rfc9112

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Mitigating Browser Fingerprinting in Web Specifications…
Would add issues/fingerprinting-guidance-discontinuedreferences.md with

Repo: 'https://github.com/w3c/fingerprinting-guidance'
Tracked: N/A
Title: >-
Normative references to discontinued specs in Mitigating Browser
Fingerprinting in Web Specifications
While crawling Mitigating Browser Fingerprinting in Web Specifications, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7231 has been obsoleted by rfc9110
[ ] TRACKING-DNT is discontinued, no known replacement reference

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Compiling discontinuedReferences report for Upgrade Insecure Requests…
Would add issues/upgrade-insecure-requests-discontinuedreferences.md with

Repo: 'https://github.com/w3c/webappsec-upgrade-insecure-requests'
Tracked: N/A
Title: Normative references to discontinued specs in Upgrade Insecure Requests
While crawling Upgrade Insecure Requests, the following normative referenced were detected as pointing to discontinued specifications:

[ ] RFC7234 has been obsoleted by rfc9111

This issue was detected and reported semi-automatically by Strudy based on data collected in webref.

Among those:

informative references to DNT are probably meant as such
fingerprinting-guidance is respec, the 3 others bikeshed
privacycg/nav-tracking-mitigations is not using auto-sections
WICG/compression seems to already know the ref is obsolete, although I'm not sure I understand the underlying intent https://github.com/WICG/compression/blob/1d6b643e776bf1972e9a49a84406c218d52ae084/index.bs#L72; it's not using sections in any case
w3c/webappsec-upgrade-insecure-requests is not using sections either

So it looks like none of them would a priori benefit https://github.com/w3c/webref/issues/1096

Overall, that's fine. For the sake of documenting limits of the approach:

informative references to DNT are probably meant as such

It would make sense to exclude DNT and other hardcoded specs that we keep crawling precisely so that people can still reference them informatively.

privacycg/nav-tracking-mitigations is not using auto-sections

That's a good example of a spec for which a link-based approach would trap more problems than a reference-based approach. The spec links to RFC7231 (normatively) but does not have it in its list of references.
A simple link analysis would report the missing reference... and then this analysis would report the discontinued reference. Ideally, we'd manage to combine the reports!

w3c/webappsec-upgrade-insecure-requests is not using sections either

... but that's because they turned them into definitions.