SubjectAttrs: Fix mismatched o/organisation subject attribute name

Hi @bradleybeddoes , I found a minor nit when looking at passing the org name through RapidConnect:
rapid_connect.rb login handler (L142) was storing the attribute as "o",
while attributes_claim.rb L12 was expecting it to be stored as
"organization".
Make both use "organization" (as this is also what the spec code uses).
This is a trivial fix (and all checks pass), but it opens a slightly bigger question: would it be OK to also pass the organisation name (o attribute) as part of the attribute set?
I see that RapidConnect receives it all fine (and uses it with Freshdesk and Zendesk), but explicitly filters it out for research / auresearch attribute sets:
https://github.com/REANNZ/rapidconnect/blob/master/rapidconnect/app/models/claims_set.rb#L16
Was there a specific reason for this filtering?  Given there's already information about the institution passed in eduPersonScopedAffiliation, I would not consider the human readable organization name in any way sensitive.  And one of our members has asked for it....
Would you be OK with merging this fix and a change allowing o through at least for auresearch?   What are your thoughts on this?
Cheers,
Vlad

Thanks for this, seems fine to merge on review.
In terms of your question around shipping o to auresearch I'd not be keen to progress that. We've defined the attribute bundle as essentially being that defined by https://refeds.org/category/research-and-scholarship. It has been the same set since ~2013 and I'm not wanting to change it on the off chance we break something up stream (that is someone with very poor JSON parsing code who couldn't handle a new entry).
You could of course define a nzresearch (or similar) that does what you need and I would be willing to look at a PR for that.


AMBARI-25390. Disable indexing in /resources endpoint and sub-directory

GET /resources gives back the directory content of /var/lib/ambari-server/resources. The directory doesn't contain any sensitive information, only files which are already visible on github. But it might freak out security guys therefore it's best to disable the listing.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5468/
Test FAILed.
Test FAILured.

We will also need to delete the index.html from server.xml


Add support for Metasploit Framework console output

First time trying to create a definition for highlight.js, I think I'm doing it right, but I also think I'm abusing the built-in classnames.
What I think is more correct is to  invent a className of print_good and say that it should inherit from literal but I haven't figured out how to do that (ditto for the other classnames).
Anyway, my whole goal here is to provide minimal highlighting for Metasploit Framework output without it getting mistaken as shell/bash output (which is usually the case, so weird literals get highlighted).

If a miracle occurs and this gets added, it'll resolve rapid7/metasploit-framework#8832.

Heya @isagalaev , is this still under active development? No snark intended -- I know how it gets with open source projects -- but I just notice the last commit (as of this writing) was back in June of 2017.
If this isn't under active development, maybe I can help out with that?

I'm trying to find time to finally wrap up the post about looking for a new maintainer with explanations about the state of things and what's needed to be done. Since a few people asked the same question recently, I think I'm going to be shamed enough into finally doing it the week after next :-)

Hooray for public shame!
Good luck! It's tough maintaining a 11,000 ⭐ project all by your lonesome. :)

@todb-r7
First of all, truly sorry for the long delay in getting back to you regarding this PR. I see you and isagalaev did communicate a bit previously at least.
Thank you so much for desiring to contribute and writing a language grammar.  Unfortunately, we currently are no longer accepting new languages into the core repository.  The existing maintainers simply don't have time to maintain new languages (fixing bugs, dealing with issues, etc).  We'd still love to host your language as a 3rd party module though - if you're willing to help maintain it.
It's easy to turn your language into a module that anyone who likes can easily integrate with Highlight.js using a single line of code:
<script src="/path/to/highlight.min.js"></script>
<!-- they'd simply add your language modules -->
<script src="/path/to/highlightjs-metasploit.js"></script>
<script>hljs.initHighlightingOnLoad();</script>

Of course, it's also possible for users to build a custom highlight.js library including specific 3rd party modules - all in a single file (vs loading a bunch of 3rd party languages one at a time).
If you'd like to become the maintainer for this language then we're happy to create a new repository in the highlightjs organization and host the repository there.  That assumes you'd be open to reviewing issues and fixing bugs as they arise.  You're also welcome to host the repo yourself and we'll link to it from our README.
There isn't much in the way of how to docs on this yet, but there are sample repositories and it's honestly pretty easy.  We're still fleshing out an official "spec" for 3rd party modules, but even after that's done it should require minimal changes from the examples we have already.  IE, if you wanted to get started now there isn't any big reason to wait.
My own robots.txt grammar repository is a great, simple example:
https://github.com/highlightjs/highlightjs-robots-txt
If you have any questions feel free to ask.

Closing for inactivity; (also finally cleaning all these old PRs out for the new year).
As mentioned above if you're interested in becoming the maintainer of a 3rd party module, please respond [whenever you find time] and we'd be happy to help you get started.

Hi! Yes, I’m totally interested in maintaining this. Hopefully with our Ghost blog platform (which uses highlight.js) can actually make use of 3rd party plugins, but even if not, I assume there are other bloggers out there who want to share Metasploit output from time to time.
Thanks @yyyc514!

Good luck. Repo created:
https://github.com/highlightjs/highlightjs-metasploit


Cilium agent restart causes dns requests failure

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

We have the CiliumClusterwideNetworkPolicy that allows all pods to access coreDNS to resolve any domain names:

---
apiVersion: cilium.io/v2
kind: CiliumClusterwideNetworkPolicy
metadata:
  name: default-allow-egress-to-kube-dns
spec:
  endpointSelector:
    matchLabels: {}
  egress:
    - toEndpoints:
        - matchLabels:
            k8s:io.kubernetes.pod.namespace: kube-system
            k8s:k8s-app: kube-dns
      toPorts:
        - ports:
            - port: "53"
              protocol: ANY
          rules:
            dns:
            - matchPattern: "*"
    - toEndpoints:
        - matchLabels:
            k8s:io.kubernetes.pod.namespace: kube-system
            k8s:k8s-app: node-local-dns
      toPorts:
        - ports:
            - port: "53"
              protocol: ANY
          rules:
            dns:
            - matchPattern: "*"

Pod A and Pod B run on node workerA. Pod C runs on node workerB. CoreDNS runs on node infraA.
I run the following command inside Pod A: while true; do dig kubernetes.default.svc.cluster.local +tries=1 +time=5 +noall +answer +stats; done. It works as expected all the time.
I run the following command inside Pod B: while true; do curl --silent --output /dev/null --show-error http://$POD-C-IP; done. It works as expected all the time.
I then restart cilium agent on node workerA. Until new cilium agent is up and running, Pod A gets connection timed out; no servers could be reached for dig command. At the same time Pod B has no problem with curl.
If I deliberately break cilium agent on workerA (e.g. define illegal option inside cilium-config and restart agent) all dns traffic from that node is broken.
This behavior takes place on any node in the cluster.
I checked tcpdump on workerA and infraA (where coreDNS runs): I see outgoing packets from workerA and I see no incoming packets from workerA on infraA.
I checked cilium monitor -t drop on workerA and infraA and I saw no drops.
If I delete dns rules in my cnnp the problem is gone:

---
apiVersion: cilium.io/v2
kind: CiliumClusterwideNetworkPolicy
metadata:
  name: default-allow-egress-to-kube-dns
spec:
  endpointSelector:
    matchLabels: {}
  egress:
    - toEndpoints:
        - matchLabels:
            k8s:io.kubernetes.pod.namespace: kube-system
            k8s:k8s-app: kube-dns
      toPorts:
        - ports:
            - port: "53"
              protocol: ANY
          # rules:
          #   dns:
          #   - matchPattern: "*"
    - toEndpoints:
        - matchLabels:
            k8s:io.kubernetes.pod.namespace: kube-system
            k8s:k8s-app: node-local-dns
      toPorts:
        - ports:
            - port: "53"
              protocol: ANY
          # rules:
          #   dns:
          #   - matchPattern: "*"

with the policy above there is no dns traffic problem during cilium agent restart.
What is the reason of this behavior and how can we resolve it?
Cilium Version
1.11.4
Kernel Version
5.4.0-100-generic
Kubernetes Version
v1.20.15
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

cilium-sysdump-20220824-122715-dns.zip
In this sysdump workerA=ds-stage-7847-nld-infra-md-64bdfd64cb-zp298 and infraA=ds-stage-7847-nld-infra-md-64bdfd64cb-hv4ll.

if I remember correctly and if it is still the case, part of DNS function is delegated to cilium agent, so it might be expected DNS not function when cilium agent is restarting.

@egsysoev @pastukhov What Vincent wrote is correct. That is the expected behavior in Cilium OSS. Some enterprise editions offer HA of FQDN policy enforcement.


Blazor - How to read .json file in client side synchronous way or have any callback function for Http.GetJsonAsync method

In blazor client side application, can read and data from json file async way.
protected override async Task OnInitAsync()
{
        DBModel data = await Http.GetJsonAsync<DBModel>("sample-data/data.json");
}

But i want to do it in synchronous approach, because i need to do route the page after data fetch completed.  I have tried like this below code
protected override void OnInit()
{
        DBModel data = Http.GetJsonAsync<DBModel>("sample-data/data.json");
        UriHelper.NavigateTo('Dashboard');
}

Getting below error message
Error CS0029 - Cannot implicitly convert type System.Threading.Tasks.Task<Application1.Models.DBModel>' to 'Application1.Models.DBModel'
Or advice how to route a page after data fetch got success. Is any callback handler available for achieve my case?
Thanks in advance.

What is wrong with this:
protected override async Task OnInitAsync()
{
DBModel data = await Http.GetJsonAsync("sample-data/data.json");
    UriHelper.NavigateTo('Dashboard');

}
UriHelper.NavigateTo is called only after the GetJsonAsync is completed.

What is wrong with this:
protected override async Task OnInitAsync() { DBModel data = await Http.GetJsonAsync("sample-data/data.json"); UriHelper.NavigateTo('Dashboard'); }
UriHelper.NavigateTo is called only after the GetJsonAsync is completed.

What is wrong with this:
protected override async Task OnInitAsync() { DBModel data = await Http.GetJsonAsync("sample-data/data.json"); UriHelper.NavigateTo('Dashboard'); }
UriHelper.NavigateTo is called only after the GetJsonAsync is completed.

What is wrong with this:
protected override async Task OnInitAsync()
{
DBModel data = await Http.GetJsonAsync("sample-data/data.json");
UriHelper.NavigateTo('Dashboard');
}

UriHelper.NavigateTo is called only after the GetJsonAsync is completed.

I advice you to take some time to learn more about async/await. https://www.youtube.com/watch?v=2moh18sh5p4

@wrkettlitz, won't it be easier if you'd bother yourself to explain what is wrong with this code... Please do it if you can, so that I'll be sure that I need some practice, or just remove the link.

Await = stop here and wait for the task to finish and return the result (if any)
I assume you want the value for data before you want to go the a different page, so what you had before is already correct.

Await = stop here and wait for the task to finish and return the result (if any)
No, no ,no:  await means yield execution to the calling code ( don't block) while the task is in progress. When the task completes, continue execution; that is, call UriHelper.NavigateTo('/Dashboard') synchronously.
Now read what you wrote again:
Await = stop here and wait for the task to finish and return the result (if any)
Oh, yeah, stop here and wait for the task to finish !!! How long to wait (TO BLOCK) a year or two ?

The rest of your post is really obscure...however, it seems as though you are the one who should spend some time practicing the asynchronous programming model and Blazor. I do hope that you're not the presenter in the video. Please, remove your advertisement. You should have not try to belittle me just in order to post this video.

Hi. It looks like this is a question about how to use ASP.NET Core. While we do our best to look through all the issues filed here, to get a faster response we suggest posting your questions to StackOverflow using the asp.net-core-mvc tag.

What is wrong with this:
protected override async Task OnInitAsync()
{
DBModel data = await Http.GetJsonAsync("sample-data/data.json");
UriHelper.NavigateTo('Dashboard');
}

UriHelper.NavigateTo is called only after the GetJsonAsync is completed.

@enetstudio :  Actually i am using client side blazor application, your solution not work with my scenario.
Page restricted and some time after only data assigned specified parameter

Finally, i solve this issue by following way in my project
`
protected async Task GetData()
{
return await Http.GetJsonAsync("sample-data/data.json");
}
protected override async Task OnInitAsync()
{
    DBModel data = await GetData();
    Console.WriteLine(DBModel data.PersonalData[0].Name); // Used to ensure data fetch or not
    UriHelper.NavigateTo("Dashboard");
}

`
Above way page routing happened once data fetch complete.
Thanks guys, sharing your valuable suggestion.

@pandiyaraj678, this is not my solution. This is your code, a copy of your code, which is why it is "("Dashboard")" instead of "("/Dashboard")". Do you get it ? I just copy paste your code, and said that there is nothing wrong with it. This is how it should be, though I would design my code much differently.
Anyhow, your new code snippet, which you say is working, is actually the first code snippet  implemented in two methods, and thus, if it works as two methods, it should work as a single combined method.
And that is what I've said that there in nothing wrong with your code...
As suggested above, you'd better post such questions in StackOverflow
Good day...

@pandiyaraj678, this is not my solution. This is your code, a copy of your code, which is why it is "("Dashboard")" instead of "("/Dashboard")". Do you get it ? I just copy paste your code, and said that there is nothing wrong with it. This is how it should be, though I would design my code much differently.
Anyhow, your new code snippet, which you say is working, is actually the first code snippet implemented in two methods, and thus, if it works as two methods, it should work as a single combined method.
And that is what I've said that there in nothing wrong with your code...
As suggested above, you'd better post such questions in StackOverflow
Good day...

As per below documentation, i have used route as ("Dashboard")
https://docs.microsoft.com/en-us/aspnet/core/blazor/routing?view=aspnetcore-3.0#uri-and-navigation-state-helpers


Iterator

Is there an iterator that allows me to pick a random spinner?

Hi, there currently isn't anything like this implemented in spinoff. I feel it isn't necessary to be included in the library itself when it could be implemented to your needs by yourself.


[Edge Agent] short poll request failed

Hello guys,
I have a problem and I do not know how to fix it.  I have 2 portainer edge agents running on 2 different machines. Everything was working fine for a long time. Since a week or two I get this error on all edge agents:
an error occured during short poll | error="short poll request failed" stack_trace=[{"func":"(*PortainerEdgeClient).GetEnvironmentStatus","line":"133","source":"portainer_edge_client.go"},{"func":"(*PollService).poll","line":"214","source":"poll.go"},{"func":"(*PollService).startStatusPollLoop","line":"150","source":"poll.go"},{"func":"goexit","line":"1594","source":"asm_amd64.s"}]
What does it mean?
I can access the portainer server on my host. Even the heartbeat is okay for both agents. But that's all. I can not connect to anyone.
I use the deployment command from the web interface for the agents.
Any ideas?

@Sveeeeeen
Can you provide the following:
[1] Version of Portainer Server
[2] Version of Portainer Agents
[3] Portainer Server Environment:  Docker Standalone, Swarm, K8s?
[4] Anything change in your environment recently?  Networking, etc...
Thanks!

@tamarahenson
Thanks for your support.

Ok

2023/04/05 08:17PM INF github.com/portainer/agent/cmd/agent/main.go:83 > agent running on Docker platform | 2023/04/05 08:17PM INF github.com/portainer/agent/edge/key.go:144 > edge key loaded from options | 2023/04/05 08:17PM INF github.com/portainer/agent/edge/registry/server.go:101 > starting registry credential server | 2023/04/05 08:17PM INF github.com/portainer/agent/http/server.go:100 > starting Agent API server | api_version=2.17.1 server_addr=<IP_ADDRESS> server_port=9001 use_tls=false 2023/04/05 08:17PM INF github.com/portainer/agent/edge/edge.go:138 > setting endpoint ID | endpoint_id=0 2023/04/05 08:17PM ERR github.com/portainer/agent/edge/poll.go:152 > an error occured during short poll | error="short poll request failed" stack_trace=[{"func":"(*PortainerEdgeClient).GetEnvironmentStatus","line":"133","source":"portainer_edge_client.go"},{"func":"(*PollService).poll","line":"214","source":"poll.go"},{"func":"(*PollService).startStatusPollLoop","line":"150","source":"poll.go"},{"func":"goexit","line":"1594","source":"asm_amd64.s"}]
4. Error still exists. Heartbeat is OK. But can not access the environment:

What address is the short poll trying to access?

@Sveeeeeen
When the issue started happening, were any network changes made?  Can you ping the machines both ways?
Thanks!

@tamarahenson
I am able to ping all machines. Heartbeat is working on portainer Edge Agent. I can access the API using curl too.
Not network changes are made. I think the problem happened when I tried the new scheduler to update the edge agents. But unfortunately I am not able to get it to work with an older version of the edge agent.
I am able to get the response from the portainer server using curl: curl https://domain.tld/ or curl https://domain.tld:9443/

@Sveeeeeen
I tested the Edge Agent upgrade feature and am unable to reproduce.  Can you provide more information:
[1] Screenshot of the Home page
[2] What version of the Edge Agents are running?
[3] Can you try the Edge Agent upgrade feature again (if not running 2.17.1)?
Thanks!

@tamarahenson

See 1.
See 1.

@Sveeeeeen
Thank you for the additional information.
Note:  Please do not attempt to upgrade the Edge Agents via the Schedule Update.  We have a known issue that is currently being resolved.  https://github.com/portainer/portainer/issues/8807
Thanks!

I think I am experiencing a similar issue for a couple weeks now, I hope this can aid in resolving the issue.
Configuration
Recent Changes
I updated both the portainer host as well as my working edge-agent instance recently from 2.17.x, not sure which one exactly. I also updated the broken edge agent docker image by pulling the latest image, but it has been and still is broken. I also updated the Host kernels to a newer patch on stable ubuntu, but that should hopefully be irrelevant.
I already rebooted both machines and restarted the docker containers. I also deleted the docker volume to freshly install the edge agent which also did not change anything.
Portainer
Docker version 23.0.4, build f480fb1
Portainer Version 2.18.1, build 29776 (linux-arm64-2.18.1)
Running on Ubuntu aarch64 GNU/Linux
3 Nodes (1 daemon on this host and two edge agents)
Edge Agent 1
Docker version 23.0.4, build f480fb1
Portainer Agent Version 2.18.1 (linux-amd64-2.18.1)
Running on Ubuntu x86_64 GNU/Linux
Note, that I have a second Edge Agent connected to my instance which works without any issues, so pretty much the exact same configuration as @Sveeeeeen .
Behaviour
The Edge Node shows up in the environments list on my host and a heartbeat was received recently (within seconds). However the docker version shows up as 23.0.1 which was a long time ago (since the day the edgeagent has not been properly working anymore). It also shows up as connected after pressing the new "Live Connect" button, but i just get the "Failed connecting to Edge-Node-Name" error every 10 seconds.
Solution Attempts

[X] Restart the Edge Agent: sudo docker stop portainer_edge_agent
[X] Check the Edge Agent logs: sudo docker logs portainer_edge_agent (see above)
[X] Access Edge Agent Environment on Portainer (see behaviour)
[X] Resolved or still Error? (still errored)

Screenshots
Connection failure in second environment (first edge agent in the list).

Edge environment showing up as live connected but no connection can be established.

Logs
Edge Agent
2023/04/18 07:52PM INF github.com/portainer/agent/edge/edge.go:140 > setting endpoint ID | endpoint_id=6
2023/04/18 07:52PM INF github.com/portainer/agent/edge/edge.go:140 > setting endpoint ID | endpoint_id=0
2023/04/18 07:52PM ERR github.com/portainer/agent/edge/poll.go:152 > an error occured during short poll | error="short poll request failed" stack_trace=[{"func":"(*PortainerEdgeClient).GetEnvironmentStatus","line":"149","source":"portainer_edge_client.go"},{"func":"(*PollService).poll","line":"214","source":"poll.go"},{"func":"(*PollService).startStatusPollLoop","line":"150","source":"poll.go"},{"func":"goexit","line":"1594","source":"asm_amd64.s"}]

Portainer
{"time":1681867844,"message":"http: proxy error: dial tcp <IP_ADDRESS>:51594: connect: connection refused"}
{"time":1681867844,"message":"http: proxy error: dial tcp <IP_ADDRESS>:51594: connect: connection refused"}
{"time":1681867854,"message":"http: proxy error: dial tcp <IP_ADDRESS>:60712: connect: connection refused"}
{"time":1681867855,"message":"http: proxy error: dial tcp <IP_ADDRESS>:0: connect: connection refused"}
{"time":1681867855,"message":"http: proxy error: dial tcp <IP_ADDRESS>:0: connect: connection refused"}

@Sveeeeeen
Thank you for the additional information.
Note: Please do not attempt to upgrade the Edge Agents via the Schedule Update. We have a known issue that is currently being resolved. #8807
Thanks!

@tamarahenson Any workaround to fix that, because I tried to test it out with the scheduled edge agent update?

If you try to upgrade using the Schedule Update feature in 2.18.1, it will not upgrade the Agent.  The workaround is to delete the Update and Rollback schedule.  And, upgrade when 2.18.2 is available.

@Sveeeeeen
Can you perform the following:
[1] Edge Agent Node
[2] docker stop portainer_edge_agent
[3] docker rm portainer_edge_agent
[4] Portainer Server >> verify "red" heartbeat
[5] Redeploy the Edge Agent.  You will need the original command that includes the EDGE ID and KEY
[6] Provide update
Thanks!

@tamarahenson
Thanks.
I tried this already. I get the same result. After deploying the new portainer_edge_agent. Hearbeat changes from red to green, but trying to access the server, I get the error:
There was an issue connecting to edge agent via tunnel. Click 'Retry' below to retry now, or wait 10 seconds to automatically retry.

Update:
Can you please add --log-level=DEBUG to the Portainer Server and Edge Agent?  The additional logs might help further troubleshoot the issue.
Thanks!

@tamarahenson
Edge Agent:
`
023/05/02 05:30PM INF github.com/portainer/agent/edge/edge.go:140 > setting endpoint ID | endpoint_id=0
2023/05/02 05:30PM ERR github.com/portainer/agent/edge/poll.go:152 > an error occured during short poll | error="short poll request failed" stack_trace=[{"func":"(*PortainerEdgeClient).GetEnvironmentStatus","line":"149","source":"portainer_edge_client.go"},{"func":"(*PollService).poll","line":"214","source":"poll.go"},{"func":"(*PollService).startStatusPollLoop","line":"150","source":"poll.go"},{"func":"goexit","line":"1594","source":"asm_amd64.s"}]
2023/05/02 05:30PM DBG github.com/portainer/agent/edge/edge.go:258 > Docker runtime configuration check | engine_status=1 leader_node=false
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/edge.go:258 > Docker runtime configuration check | engine_status=1 leader_node=false
2023/05/02 05:31PM INF github.com/portainer/agent/edge/edge.go:140 > setting endpoint ID | endpoint_id=41
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/client/portainer_edge_client.go:126 > sending timeZone header | timeZone=UTC
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/client/portainer_edge_client.go:129 > sending agent platform header | header=1
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/client/portainer_edge_client.go:145 > poll request failure] | response_code=500
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/client/error_response.go:22 > poll request failure | error_response_details="Unable to retrieve edge stack from the database" error_response_message="Unable to retrieve edge stack from the database" status_code=500
2023/05/02 05:31PM INF github.com/portainer/agent/edge/edge.go:140 > setting endpoint ID | endpoint_id=0
2023/05/02 05:31PM ERR github.com/portainer/agent/edge/poll.go:152 > an error occured during short poll | error="short poll request failed" stack_trace=[{"func":"(*PortainerEdgeClient).GetEnvironmentStatus","line":"149","source":"portainer_edge_client.go"},{"func":"(*PollService).poll","line":"214","source":"poll.go"},{"func":"(*PollService).startStatusPollLoop","line":"150","source":"poll.go"},{"func":"goexit","line":"1594","source":"asm_amd64.s"}]
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/edge.go:258 > Docker runtime configuration check | engine_status=1 leader_node=false
2023/05/02 05:31PM INF github.com/portainer/agent/edge/edge.go:140 > setting endpoint ID | endpoint_id=41
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/client/portainer_edge_client.go:126 > sending timeZone header | timeZone=UTC
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/client/portainer_edge_client.go:129 > sending agent platform header | header=1
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/client/portainer_edge_client.go:145 > poll request failure] | response_code=500
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/client/error_response.go:22 > poll request failure | error_response_details="Unable to retrieve edge stack from the database" error_response_message="Unable to retrieve edge stack from the database" status_code=500
2023/05/02 05:31PM INF github.com/portainer/agent/edge/edge.go:140 > setting endpoint ID | endpoint_id=0
2023/05/02 05:31PM ERR github.com/portainer/agent/edge/poll.go:152 > an error occured during short poll | error="short poll request failed" stack_trace=[{"func":"(*PortainerEdgeClient).GetEnvironmentStatus","line":"149","source":"portainer_edge_client.go"},{"func":"(*PollService).poll","line":"214","source":"poll.go"},{"func":"(*PollService).startStatusPollLoop","line":"150","source":"poll.go"},{"func":"goexit","line":"1594","source":"asm_amd64.s"}]
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/edge.go:258 > Docker runtime configuration check | engine_status=1 leader_node=false
2023/05/02 05:31PM DBG github.com/portainer/agent/edge/edge.go:258 > Docker runtime configuration check | engine_status=1 leader_node=false
`
Portainer server:
2023/05/02 05:38PM INF main.go:568 > encryption key file not present | filename=portainer 2023/05/02 05:38PM INF main.go:602 > proceeding without encryption key | 2023/05/02 05:38PM INF github.com/portainer/portainer-ee/api/database/boltdb/db.go:124 > loading PortainerDB | filename=portainer.db 2023/05/02 05:38PM DBG github.com/portainer/portainer-ee/api/useractivity/cleanup.go:16 > starting logs cleanup process | check_interval_seconds=86400 2023/05/02 05:38PM DBG github.com/portainer/portainer-ee/api/useractivity/cleanup.go:61 > removed old auth logs | count=0 2023/05/02 05:38PM DBG github.com/portainer/portainer-ee/api/useractivity/cleanup.go:68 > removed old user activity logs | count=0 2023/05/02 05:38PM INF github.com/portainer/portainer-ee/api/cloud/cluster_setup.go:93 > starting cloud cluster setup service | 2023/05/02 17:38:11 server: Reverse tunnelling enabled 2023/05/02 17:38:11 server: Fingerprint a3:d7:b6:ef:0c:cb:ff:ff:58:5e:dc:06:8b:ab:98:36 2023/05/02 17:38:11 server: Listening on <IP_ADDRESS>:8000... 2023/05/02 05:38PM DBG github.com/portainer/portainer-ee/api/chisel/service.go:183 > starting tunnel management process | check_interval_seconds=10 2023/05/02 05:38PM DBG github.com/portainer/portainer-ee/api/datastore/migrate_post_init.go:66 > failure migrating endpoint ingresses | error="unsupported environment type" stack_trace=[{"func":"(*ClientFactory).CreateClient","line":"165","source":"client.go"},{"func":"(*ClientFactory).createCachedAdminKubeClient","line":"140","source":"client.go"},{"func":"(*ClientFactory).GetKubeClient","line":"82","source":"client.go"},{"func":"(*ClientFactory).MigrateEndpointIngresses","line":"248","source":"client.go"},{"func":"(*PostInitMigrator).PostInitMigrateIngresses","line":"64","source":"migrate_post_init.go"},{"func":"(*PostInitMigrator).PostInitMigrate","line":"44","source":"migrate_post_init.go"},{"func":"buildServer","line":"819","source":"main.go"},{"func":"main","line":"893","source":"main.go"},{"func":"main","line":"250","source":"proc.go"},{"func":"goexit","line":"1594","source":"asm_amd64.s"}] 2023/05/02 05:38PM DBG github.com/portainer/portainer-ee/api/datastore/migrate_post_init.go:66 > failure migrating endpoint ingresses | error="unsupported environment type" stack_trace=[{"func":"(*ClientFactory).CreateClient","line":"165","source":"client.go"},{"func":"(*ClientFactory).createCachedAdminKubeClient","line":"140","source":"client.go"},{"func":"(*ClientFactory).GetKubeClient","line":"82","source":"client.go"},{"func":"(*ClientFactory).MigrateEndpointIngresses","line":"248","source":"client.go"},{"func":"(*PostInitMigrator).PostInitMigrateIngresses","line":"64","source":"migrate_post_init.go"},{"func":"(*PostInitMigrator).PostInitMigrate","line":"44","source":"migrate_post_init.go"},{"func":"buildServer","line":"819","source":"main.go"},{"func":"main","line":"893","source":"main.go"},{"func":"main","line":"250","source":"proc.go"},{"func":"goexit","line":"1594","source":"asm_amd64.s"}] 2023/05/02 05:38PM INF main.go:902 > starting Portainer | build_number=29776 go_version=1.19.4 image_tag=linux-amd64-2.18.1 nodejs_version=18.16.0 version=2.18.1 webpack_version=5.65.0 yarn_version=1.22.19 2023/05/02 05:38PM DBG github.com/portainer/portainer-ee/api/adminmonitor/admin_monitor.go:51 > start initialization monitor | 2023/05/02 05:38PM INF github.com/portainer/portainer-ee/api/http/server.go:411 > starting HTTPS server | bind_address=:9443 2023/05/02 05:38PM INF github.com/portainer/portainer-ee/api/http/server.go:396 > starting HTTP server | bind_address=:9000 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error=Unauthorized msg="A valid authorisation token is missing" status_code=401 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error=Unauthorized msg="A valid authorisation token is missing" status_code=401 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error=Unauthorized msg="A valid authorisation token is missing" status_code=401 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error=Unauthorized msg="A valid authorisation token is missing" status_code=401 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error=Unauthorized msg="A valid authorisation token is missing" status_code=401 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:38PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 {"time":1683049167,"message":"http: proxy error: context canceled"} {"time":1683049168,"message":"http: proxy error: context canceled"} {"time":1683049171,"message":"http: proxy error: dial tcp <IP_ADDRESS>:0: connect: connection refused"} 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 {"time":1683049182,"message":"http: proxy error: dial tcp <IP_ADDRESS>:63615: connect: connection refused"} {"time":1683049182,"message":"http: proxy error: dial tcp <IP_ADDRESS>:63615: connect: connection refused"} 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500 2023/05/02 05:39PM DBG github.com/portainer/libhttp@v0.0.0-20230206214615-dabd58de9f44/error/error.go:34 > HTTP error | error="Unable to retrieve edge stack from the database" msg="Unable to retrieve edge stack from the database" status_code=500

@Sveeeeeen @bitwon
I wanted to follow up on this request.  Would you instant message me a copy of your backup in our Slack Community?  I would like to further investigate.
https://join.slack.com/t/portainer/shared_invite/zt-190q9nm5v-uT0p0WFkn~K1yv2QlnHJNQ
Interim, did either of you have an Edge Stack that had previously been deleted?  Or, do you have Edge Stacks and are no longer retrievable?
Thanks!

@tamarahenson
I was able to fix my issue yesterday.
All I just did was deleting every server using the Portainer GUI -> Environments.
After I just added both server again and now it's working.

@Sveeeeeen @bitwon
I wanted to follow up on this request. Would you instant message me a copy of your backup in our Slack Community? I would like to further investigate. https://join.slack.com/t/portainer/shared_invite/zt-190q9nm5v-uT0p0WFkn~K1yv2QlnHJNQ
Interim, did either of you have an Edge Stack that had previously been deleted? Or, do you have Edge Stacks and are no longer retrievable?
Thanks!

Done.

@tamarahenson Still not fixed and no feedback in the Slack channel.

are this issues has been fixed ? because im having the same issues as well ..

@Anmirazik Not really, I made a reinstallation in the past, because I had no chance to solve the problem without.


How to get from user mode?

How can topology be queried from user mode?

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

ID: cb6fdb5b-5b6d-4926-b55d-3d128a6c4c50
Version Independent ID: 0f749787-7efb-7a6a-1776-b0b0facd8348
Content: IOCTL_INTERNAL_USB_GET_TOPOLOGY_ADDRESS
Content Source: wdk-ddi-src/content/usbioctl/ni-usbioctl-ioctl_internal_usb_get_topology_address.md
Product: windows-hardware
GitHub Login: @windows-driver-content
Microsoft Alias: windowsdriverdev

Getting the HubPortNumber array from the USB_TOPOLOGY_ADDRESS really needs to be supported from user-mode; otherwise, the user will have to enumerate the entire USB device tree to calculate it!

Hi @BrianCatlin,
I’ve created an internal work item for myself to investigate this with the USB team, and I’ll make a note here when I complete the changes. In the meantime, I’m closing the GitHub issue while it’s tracked in the bug. Thanks again for helping to improve the docs.


Feature Request: ("live") global label (set) management

Gitea version (or commit ref): 1.13.0
Git version: n/a
Operating system: Linux

Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No

Log gist:

Description
I'd like to see organization labels-like functionality at the global level. The use case for this is we have several users in a single gitea instance, with each having their own different repositories, some of which share certain organizational attributes. For example, multiple users may have repositories that contain customer-specific data (possibly along with generic data in the same repo). Being able to share "live" customer labels across these repositories would make management so much easier than having to remember to go to each affected repository and add/edit/delete one or more labels when that time comes, all while keeping the repository ownership as-is.
Ideally this feature would include:

Making all label sets "live", like an organization's label set
A proper web UI for managing label sets, probably via somewhere in the site admin settings (instead of having to manage files on disk in custom/)
For each label set, a web UI identical to that of organization labels: ability to add/edit/delete any labels, see how many issues/PRs are using each label with a link to those issues/PRs, ability to sort labels, etc.
Global labels (from global label sets) would of course be visible to all repositories and like organization labels, would not be mutable in each repository

Yeah a system label set would help us too. We have an org for each customer and we likle to share some general labels like issue type / state / prio ...


🍒 Cherry pick PR #7955 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/7955 to staging 🍒

🚀 Cherry-picked to staging by @OSBotify in version: 1.1.41-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @francoisl in version: 1.1.41-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Move local run to MiniKube

It seems that running everything in minikube is extremely slow as I found out when I was developing save-demo. The idea is to add configuration fake-kubernetes that would allow to use kubernetes orchestration when running spring service outside the cluster.

when running spring service outside the cluster.

It is desired solution: only mysql/s3 and save-agent/save-demo-agent should be run in minikube -- the rest components should be run outside


Feedback functions

Not an issue, but I use your module in church for our resi decoder. Is there any chance of getting feedback functions for countdowns to cues, cue names, things like that. What I wanted to do was have it so that when companion receives the feedback that the cue “Keys Up” has been received, it takes the countdown and sends it in a message (have the message part set up already). Please let me know if it is possible. If it’s easier feel free to email me -<EMAIL_ADDRESS>

We haven't used our Resi decoder for some time now and I no longer maintain
the repository myself. From what  I have read, Resi does not support
feedback. If you can find  some documentation on where they do provide
feedback, I would be happy to work on an implementation of it.
Jake
On Sun, Feb 5, 2023 at 2:49 AM alpale3 @.***> wrote:

Not an issue, but I use your module in church for our resi decoder. Is
there any chance of getting feedback functions for countdowns to cues, cue
names, things like that. What I wanted to do was have it so that when
companion receives the feedback that the cue “Keys Up” has been received,
it takes the countdown and sends it in a message (have the message part set
up already). Please let me know if it is possible. If it’s easier feel free
to email me - @.***
—
Reply to this email directly, view it on GitHub
https://github.com/bitfocus/companion-module-resi-decoders/issues/6, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AI32LF7M27KLBUYZGZDHZZDWV5SRLANCNFSM6AAAAAAURU34CM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Formatting with more than three S tokens repeats

We don't want to support finer precision than milliseconds, but we do need to contend with working with strings containing such precision, even if we truncate.
Parsing is already supported, with any number of decimal places. But formatting has some weirdness is that it repeats the value in the formatting.
moment('2014-07-30 02:59:32.123456789','YYYY-MM-DD HH:mm:ss.SSSSSSSSS').format('YYYY-MM-DD HH:mm:ss.SSSSSSSSS')
// returns: "2014-07-30 02:59:32.1231231"
// expected: "2014-07-30 02:59:32.1230000"

See also #2022

I agree, its a bug, and its easy to fix. Will merge a PR.

Thanks!

Docs currently state only S, SS and SSS, code support SSSS, which does the same as SSS. I think I'll have to add for up to 9 Ss.

Close in favor of #2448


Install manifest

Currently the installable resources are hard coded into the riff cli binary. This makes it very difficult to test new releases. Rather than expose the URL for each resource as a cli switch, we could define a manifest file that can then reference individual yaml files. A structured manifest will make it easier to pause for validation after installing Istio, or any other component that takes time to start.
A straw man proposal:
version: 0.1
istio: https://path/to/istio.yaml
system:
- https://path/to/knative-build.yaml
- https://path/to/knative-serving.yaml
- https://path/to/knative-eventing.yaml
- https://path/to/stub-clusterbus.yaml
namespace:
- https://path/to/riff-buildtemplate.yaml

cc @trisberg

I agree we need to externalize this and a manifest seems better than overriding individual UTLs for the YAML artifacts

[ ] Switch to istio and knative arrays in the manifest
[ ] Implement 5 second delay between installs of items in the istio array
[ ] Implement more specific global changes for items in the istio and knative arrays (s/type: LoadBalancer/type: NodePort/)
[ ] Provide a sample manifest which is equivalent to the hard-coded behaviour (in the future we can sync these up using code generation)


New Rule CHECK_ROOT_VOLUME_ENCRYPTION

'''
#####################################
Gherkin
#####################################
Rule Name:
CHECK_ROOT_VOLUME_ENCRYPTION
Description:
Check whether the root volume associated with an instance is encrypted or not.
Trigger:
Configuration Change on AWS::EC2::Instance
Reports on:
AWS::EC2::Instance
Rule Parameters:
None
Feature:
In order to: protect the data contained on EC2 instances' root volumes
As: a Security Officer
I want: to verify that the root volume is encrypted on any EC2 instance in the environment.
Scenarios:
Scenario 1:
Given: The no instances are returned
Then: Return NOT_APPLICABLE
Scenario 2:
Given: The root volume has the "Encrypted" key set as False
Then: Return NON_COMPLIANT on this EC2 Instance
Scenario 3:
Given: The root volume has the "Encrypted" key set as False
And: Additional volume attachments have the "Encrypted" key set to True
Then: Return NON_COMPLIANT on this EC2 Instance
Scenario 4:
Given: The root volume has the "Encrypted" key set as False
And: Additional volume attachments have the "Encrypted" key set to False
Then: Return NON_COMPLIANT on this EC2 Instance
Scenario 5:
Given: The root volume has the "Encrypted" key set as True
Then: Return COMPLIANT on this EC2 Instance
Scenario 6:
Given: The root volume has the "Encrypted" key set as True
And: Additional volume attachments have the "Encrypted" key set to True
Then: Return COMPLIANT on this EC2 Instance
Scenario 7:
Given: The root volume has the "Encrypted" key set as True
And: Additional volume attachments have the "Encrypted" key set to False
Then: Return COMPLIANT on this EC2 Instance
'''

Please label as "feedback requested"

Hi. What is the difference with https://docs.aws.amazon.com/config/latest/developerguide/encrypted-volumes.html ?

The one you linked checks all attached volumes. This config rule checks specifically if the volume that is attached as a root volume is encrypted or not. In this rule you can have multiple attachments but the only one that matters for compliance is the root volume.

Understood, thanks.
I am not understanding the use case where this would be appropriate. Is it cost consideration to check only for root volume? Naturally, I'd recommend to encrypt all volumes. In addition, root volume tend to be OS only, and secondary volumes tend to be data.

The thought process behind this rule stemmed from government compliance rules where a control requires that a root volume of an instance is encrypted. A main difference between the linked AWS backed rule and this rule as that the AWS backed rule returns volumes as the compliance resource. This rule returns an instance as compliant or not. While the encrypted-volumes and this rule ultimately check the same metadata on the volume, this rule will be beneficial in instances where there are a significant amount of volumes attached to instances. A particular instance, instead of volume, can be quickly identified as either compliant or not and further remediation can be taken on the instance level such as shutting the instance down.

I remember we had a similar PR #174 . It check all volume though, not only the root volume.

Correct, that PR is closer to this one in that it is instance invoked rather than volume invoked and does not account for which volumes need to be compliant. If you believe that this rule is too specific, you can certainly close it out.


Missing travis.

There is a travis config but no Travis setup. Travis makes contributing easier by running tests during a pull request.

ok, this is now setup and working 👍


Problem: chainid is used instead of networkid

Unlike network id, chain id cannot be modified,
network id is more flexible for setting up a custom geth in the tests.

yes, I have testnet on both devnet and goerli, value returned is correct


One-step token

Guys, good afternoon! There is some method that already returns the TOKEN direct to me. Without I having to authorize through the site? I wanted to order and receive the token without needing a second screen.
thankful

I guess no because from my own, it is the only way to obtain the token. But my question is : is the token lifetime ?
If yes, then we can get it one and use it for ever in an app...

Hello @icomenezes  and @pollux1er  , so far we don't plan to provide an option for direct generation of access_token, your will have to go through the oauth validation process.
The access tokens doesn't expire.


Service feasibility - Business List Sorting

The business list returned in the widget seems like there is no specific order. Could we provide a configuration option for how they should be sorted? Like alphabetically for business name or even by spending on current services?

@MikeMillerGIS, @phuls
Just a thought, instead of providing a configuration option, how about we provide buttons to sort in asc or desc order on top of business list ? The list can load results by default in either asc or desc order or as returned by service.
About the configuration option, we can provide an additional dropdown with title 'sort order' below the 'Field to be displayed in Business List' parameter with options to select between asc, desc and none.
Please let us know what you think of this.

Having sort buttons on the list makes sense, this would allow the user to control how they want to view the results.  @phuls @CTLocalGovTeam

@CTLocalGovTeam @MikeMillerGIS Works for me.  I have a feeling eventually users will request the option to view multiple fields in the list and sort by either.  For example, business name and how much they spend on services, but one field and asc or desc option on the widget will solve this issue.

@MikeMillerGIS @phuls,
Please have a look at the mockup that illustrates our proposal for displaying the sort options for Business List.

We picked this up from a similar implementation in the chart widget configuration UI seen in the graphic below.

Please let us know if this is ok.
Note:
Actually, do we need the 'None' option ? We think that we should just display "Asc" or "Desc" and by default it will always be "Asc". And also, we don't feel the need to make this configurable (as suggested earlier) too as its displayed in the UI.

I like the design and agree, none is not required, by default ascending should be used and it is not required to be configured.

@MikeMillerGIS We will implement the sorting as shown in the mockup with 'Ascending' and 'Descending' options('None' is excluded), by default list is sorted in ascending order. We will include this change in next release.

verified


Console Log

Is it possible to dump console output lines to a file regarding the table data or structure changes made via interface?

Hi @darkphase
at moment is not possible but i can evaluate this as a future feature.

Maybe a general purpose approach such as Console Redirection ( > file, >network address, etc..) which can be selected from UI could satisfy more parties' needs...


Inject latest Durable Object migration state into Miniflare

What this PR solves / how to test
Fixes #[insert GH or internal issue number(s)].
Author has addressed the following

Tests

[ ] TODO (before merge)
[X] Included
[ ] Not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[X] I don't know
[ ] Required / Maybe required
[ ] Not required because:

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[x] Included
[ ] Not necessary because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s):
[X] Not necessary because: Covered by SQLite backed DOs announcement and blog post.

@penalosa I think this is ready to go. There's one failing test which seems unrelated to my change, but is only reproducible on Windows. Do we have VMs sitting around that we can validate this on?

This looks generally good! A couple small comments, but otherwise good to go.


feat: Pizza show

Description
This PR implements the pizza show command. This is the first step in developing a TUI that can be used for a centralized monitor to display metrics for an specific repository.
Current metrics:

Repository model

name, issues, forks, stars, size
New contributors table
Churned contributors table

Contributor model (interactive through repository model tables)

pr velocity, pr count, issues opened, is maintainer
The last 5 PRs made

wip
https://github.com/open-sauced/pizza-cli/assets/59541661/1689182b-cab8-4663-81f0-1a8c9c7b9bc9

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents
#9

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[ ] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

👏🏼 👏🏼 👏🏼 👏🏼 👏🏼 👏🏼 👏🏼

That would be awesome! if it wasn't for GoTags I would still be typing the structs 😂. Btw, any preference on the color palette? I picked #FF4500 which seems to be what is used in the UI, but Lipgloss has adaptive colors which can be leveraged depending on the terminal background color. Also, since I grab the repo info I can also render the size, issues and so on, anything from there that may be useful to display? Lastly, is there an endpoint to get the commits from the repo_id ? I see there is one from pizza to get it from the bake repo id.

Btw, any preference on the color palette? I picked #FF4500 which seems to be what is used in the UI, but Lipgloss has adaptive colors which can be leveraged depending on the terminal background color.

Yes, we should 100% use adaptive colors: a hard coded color value will be really rough for people on random weird color schemes.

Also, since I grab the repo info I can also render the size, issues and so on, anything from there that may be useful to display?

Good question: it's pretty open ended right now, so if something makes sense to add, go for it!

Lastly, is there an endpoint to get the commits from the repo_id ? I see there is one from pizza to get it from the bake repo id.

Yeah, good question, I was just chatting with @brandonroberts about this: there isn't currently a way to get the commits from the API based on a repo_id. Right now, baked_repos and repos are sort of siloed and we don't have a great way in the bakend to connect them.
The first thing to do here is get our ETL service to connect repo ids in the baked_repos table that are null. And if it can't find them, then go and fetch that data from github.
So, for now, commits are abit blocked, but it's ok to leave that out for now.

Can you change this PR's target branch to be beta? 👀 We recently changed the default branch to beta in support of using the releaser action
For further reading:

https://github.com/open-sauced/pizza-cli/issues/34

@k1nho - let me know when you'd like me to look at this 😄 happy to help if you need anything along the way

I think is looking good for the 1st iteration of pizza show, updated the demo at the top to reflect what I have now. Still need to do some clean up some of the error handling between cobra<-TUI and TUI<-models when doing async operations. Also, for now I just have the static data from first fetch on dashboard model, so 'reatime' is not there yet, but the contributor model is dynamic so that one is 'realtime'. @jpmcb would appreciate a review of what I have so far.

One thing I noticed is it does something weird when I resize my tmux window: the contributors disappear from the rendering. But then will re-appear if I keep resizing the window.

Nice catch 🧤! just found out why this happened. Basically the window resizing message tea.WindowSizeMsg gets triggered on every window resize which is useful for responsiveness. However, if acted upon on Update rather than View by setting a particular width to the tables on that loop it creates the glitch effect. This should now be fixed on the latest commit.

One sharp UI/UX edge I noticed is there's not much feedback as far as waiting for the next thing to happen. When I get into a contributor's view and hit , it feels like it freezes since there's no spinning wheel or something (and I'm assuming it's blocking on the API call to return).

Investigating this, need to review some elm architecture stuff with commands make sure is not the message flow. If anything, could probably throw a spinner on this one, but the cache would certainly be useful.

👀

When testing this, noticing @dev-phantom's PRs are cut off and I am not sure if scrolling is built in. Repo is open-sauced/app

Added responsiveness for contributor view in this last commit. This should now display horizontally if it does not fit in the vertical space. Also, introduced the list Model from bubbles instead of just the strings, I can see this format being more useful in the future. Now,  PR can be directly accessed with O with the browser dependency we are using for auth cmd as well.
https://github.com/open-sauced/pizza-cli/assets/59541661/2c61cf9e-e1a5-4797-98d4-ffcc8640b2f0

Wow awesome work @k1nho - huge effort! 👏🏼 a few small nits if you want to fix otherwise we can get this in a roll forward fixes for those nits

Agreed. This was a huge lift and getting this on beta would unblock a lot of future contributions and polish.
I am also featuring this briefly in my Redwoodjs conf lightning talk. It would be cool to get folks to use it after, but no rush.

Closes https://github.com/open-sauced/pizza-cli/pull/24


Unable to resolve dependencies for iOS build

Describe the bug
When making an iOS build after adding the Branch Unity SDK, there is no .xcworkspace generated, only .xcodeproj. This means that the dependency to the Branch iOS SDK is not resolved, and the build fails due to missing headers.
After investigating I can see this particular problem was reported for 1.0.0. It sounds like an issue with EDM4U.
After some more digging I can see that EDM4U is no longer bundled with the .unitypackage. The release notes mention that it was removed in favour of using UPM (via OpenUPM) however their is no package manifest in the .unitypackage and so EDM4U is not installed automatically. Is the user meant to install EDM4U manually, or is the .unitypackage supposed to have a package manifest?
I can see the docs haven't been updated for over a year, and don't seem up-to-date with release 2.0.0. There's a section at the very bottom about installing EDM4U, but it's for a different issue.
Also EDM4U seems to use Cocoapods for iOS builds, which is not installed on MacOS by default. I'm not sure if EDM4U will install Cocoapods for the user, if not then it's probably important to mention in the docs. The Branch Unity page doesn't currently have any info concerning the build process and dependencies resolution, it has to be pieced together from the platform-specific pages.
Steps to reproduce

Install BranchUnityPackage.unitypackage 2.0.0 into an existing project (that doesn't already have EDM4U installed) and follow the rest of the [instructions for the Unity SDK]
Notice that EDM4U is not available (eg. no Assets/External Dependency Manager menu item)
Build for iOS from Unity
Notice that the output directory has a .xcodeproj but no .xcworkspace
Open the .xcodeproj and attempt to build/archive
Notice build errors from missing headers (eg. Branch.h)

Expected behavior
EDM4U should be installed automatically after importing BranchUnityPackage.unitypackage.
After building for iOS from Unity Editor the output directory should contain a .xcworkspace with details of the Branch iOS SDK dependency.
Building in XCode should succeed and not fail on missing header errors.
SDK Version
2.0.0
Unity Version
2021.3.38
Make and Model
Macbook Pro (M3 Pro)
OS
MacOS 14.6.1
Additional Information/Context
No response

I manually installed EDM4U via UPM and it will indeed install Cocoapods for the user if it's not installed, I tested by uninstalling Cocoapods and reopening the editor.
After:

installing EDM4U
clearing out the build output directory
building for iOS from the editor

I can successfully observe a generated .xcworkspace which successfully builds.


[core / node-sync] Get semaphore permit before launching task

Previously we got items out of a (bounded) channel, launched a task, and then tried to get a semaphore permit. This means that in practice the channel was unbounded, and so were the number of tasks we could potentially launch. In this PR we take the semaphore ticket before we launch a task, in effect bounding the number of active tasks to execute digests, and allowing the channel to apply back pressure when execution is slow.

i believe this is fine - I've promised you docs for a benchmarking process, so let me try to get that done so we can see what the effect of this is.


rs2_pipeline_wait_for_frames Error when using Unity ECS Package

Hi, I'm using the intel realsense SDK Unity Wrapper with ECS Unity packages.
Below is my error message after running the project:
ExternalException: rs2_pipeline_wait_for_frames(pipe:000002B5A4BE4320)
Rethrow as Exception: Frame didn't arrived within 5000
Intel.RealSense.ErrorMarshaler.MarshalNativeToManaged (System.IntPtr pNativeData) (at <441657b0dbbd43269996475b2c92e0df>:0)
Intel.RealSense.Pipeline.WaitForFrames (System.UInt32 timeout_ms) (at <441657b0dbbd43269996475b2c92e0df>:0)
RsDevice.WaitForFrames () (at Assets/RealSenseSDK2.0/Scripts/RsDevice.cs:165)
System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) (at <437ba245d8404784b9fbab9b439ac908>:0)
System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) (at <437ba245d8404784b9fbab9b439ac908>:0)
System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) (at <437ba245d8404784b9fbab9b439ac908>:0)
System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) (at <437ba245d8404784b9fbab9b439ac908>:0)
System.Threading.ThreadHelper.ThreadStart () (at <437ba245d8404784b9fbab9b439ac908>:0)
UnityEngine.<>c:<RegisterUECatcher>b__0_0(Object, UnhandledExceptionEventArgs)
Intel.RealSense.NativeMethods:rs2_pipeline_wait_for_frames(IntPtr, UInt32, Object&)
Intel.RealSense.Pipeline:WaitForFrames(UInt32)
RsDevice:WaitForFrames() (at Assets/RealSenseSDK2.0/Scripts/RsDevice.cs:165)
System.Threading.ThreadHelper:ThreadStart()

Related Info

Camera Model
D435

Operating System & Version
Win 10

Platform
Windows Mixed Reality

SDK Version
2.0

Language
unity

Segment
VR

Unity Version
2019.3.3

Issue Description
Everything runs normally when not installing the Unity ECS packages. In specific, these are:

Platforms Windows 0.2.1
Entities 0.7.0
Hybrid Renderer 0.3.5
Mono Cecil 0.1.6

Another warning message I have received is:
Near clipping plane is < 0.1f. This may cause hologram instability when using Windows Mixed Reality.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Hope someone can provide some insights of how to solve this or how to debug. Thank you very much for your help in advance! :)

found that maybe this is due to the conflict of our geometry shader, so deleting the shader solved the problem. This issue can be closed. Thanks!


Behavior of iterator on snapshot changes with subsequent writes to the Database

What steps will reproduce the problem?
1. Compile the attached test program against leveldb-1.13.0
2. Run as is. Notice that as we call Prev() until the iterator until it reaches
"3", then call Next() the iterator stays on "3"
3. Now comment out the Put() call. Notice that the iterator behaves
differently, on the first Next() calls it goes from "3" to "4" (as I expect is
correct).

What version of the product are you using? On what operating system?

1.13.0 on Mac OS X 10.8.3 and Android 4.2

Please provide any additional information below.

Unless I misunderstood something, I don't think inserting something to the
database should change the behavior of iterators iterating pre-write snapshots.

Also it seems wrong that iter.Next() would not actually move the iterator.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 23 Aug 2013 at 9:39
Attachments:

test.cc

The problem seems to be that when changing the iteration direction from reverse
to forward, a simple iter_->Next() is done to compensate the fact that the
iterator always points to the previous item when moving backwards. That does
not work so well if that next item happens to be either deleted or newer than
the current snapshot. In that case FindNextUserEntry() will find the same item
where the saved_key_ used to point, eg, the same entry as before.

The attached patch uses iter_->Seek() to position the iterator to saved_key_.

Original comment by<EMAIL_ADDRESS>on 26 Aug 2013 at 9:06
Attachments:

leveldb-iterator-snapshot.patch

I suggest using the fix I provided on the mailing list on Friday.  It seems
that email replies don't show up here.

The route we chose was to conditionally call "SaveKey".  I think this may be
more efficient than calling "Seek", except in cases where the iterator needs to
skip lots of data.  Our patch is here:
https://github.com/rescrv/HyperLevelDB/commit/e19fc0c34690be79dbf9f6102e9987c561
25905f

Original comment by<EMAIL_ADDRESS>on 26 Aug 2013 at 12:37

Fixed in 1.14.0

Original comment by<EMAIL_ADDRESS>on 19 Sep 2013 at 8:55

Changed state: Fixed

Hi Johann and Robert,

Thanks for the test and fix.

Would both of you mind e-signing the contributor license agreement so I can
incorporate your fix into leveldb?  The agreement is pretty simple:
   http://code.google.com/legal/individual-cla-v1.0.html

If you sign it, just drop a note to<EMAIL_ADDRESS>(or reply on this issue)
saying you have done so and I can take it from there.  If you can't we will
figure out some alternate way to fix the problem.

Thanks.

Original comment by<EMAIL_ADDRESS>on 26 Aug 2013 at 4:15


[ALLUXIO-2199] Normalize unit test method names - removing suffix

This PR addresses https://alluxio.atlassian.net/browse/ALLUXIO-2199

@aaudiber

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/11168/
Test PASSed.

LGTM


Thoroughly test Nexgen-created files against their GDA equivalents

Following the discussion in https://github.com/DiamondLightSource/nexgen/issues/219
We need:

a system test that compares all the fields, attributes and data types for a Hyperion and GDA nexus file (note there may be some differences that we're fine with but these should be explicitly ignored in the test with a comment as to why it is ok for them to be different

We have some tests that compare some parts of these files
We need to change from just comparing the specific features to compare all of it except the exceptions
We should have tests for different bit-depths too
The conclusions of https://github.com/DiamondLightSource/hyperion/issues/1350 will also dictate what we might do here
Timebox this issue for 2 days to keep writing tests around nexus files, catching as many edge cases found in the above
Make sure the tests are good documentation of what the edge cases are


[DataFrame] LoadCsv throws IndexOutOfRangeException

Using the following dataset: https://www.kaggle.com/austinreese/craigslist-carstrucks-data
The dataset itself is large (1.4 GB) and sparse.
Using the following code:
var df = DataFrame.LoadCsv("vehicles.csv");

Throws the following exception:
System.IndexOutOfRangeException: 'Index was outside the bounds of the array.'

Here is the stacktrace:
   at Microsoft.Data.Analysis.DataFrame.GetColumnName(String[] columnNames, Int32 columnIndex)
   at Microsoft.Data.Analysis.DataFrame.CreateColumn(Type kind, String[] columnNames, Int32 columnIndex)
   at Microsoft.Data.Analysis.DataFrame.LoadCsv(Stream csvStream, Char separator, Boolean header, String[] columnNames, Type[] dataTypes, Int64 numberOfRowsToRead, Int32 guessRows, Boolean addIndexColumn, Encoding encoding)
   at Microsoft.Data.Analysis.DataFrame.LoadCsv(String filename, Char separator, Boolean header, String[] columnNames, Type[] dataTypes, Int32 numRows, Int32 guessRows, Boolean addIndexColumn, Encoding encoding)
   at ConsoleApp.Program.Main(String[] args) in C:\Users\luquinta.REDMOND\Development\UsedCarCraigslistSample\ConsoleApp\Program.cs:line 16

Using similar functionality in Pandas does not throw these errors and the dataset loads successfully.

VehiclesEDA.zip

I looked at this locally and found the issue. The description column has many ,s inside it, so we're not able to parse the number of columns correctly. Instead of detecting 25 columns, we detect 150+ columns. Let me explore adding a new IO csproj to help with LoadCsv bugs such as this one

Great! Thanks @pgovind . This is a tricky dataset. I tried using LINQ and IO but ran into a similar issue so I understand the challenges. At least it's a way to see all the edge cases 🙂

Make sure only use '\t'. ',' does not work properly. If you have a string stored in a cell as "string1, string2" and you happen to use ',' as the separator, Microsoft.Data.Analysis will interpret it as two cells. This is why I have to check and convert all my comma-separated txts to tab-separated with Excel first.


Fix JDK 21 CI failure due to locale changes

@SingingBush
Please always use the description in a PR, add a URL to the JIRA ticket when there is one. TY! 😄


[Compatibility]

Related Project(s)
Traveler's Backpack
a similar problem with chest cavity
Problem
the put-on backpack is one for all shells
Feature
I don't know how, but I think it's already clear that it's necessary for the backpack to be personalized for each shell
Other Solutions
No response
Justification
I don't know, intuition
Additional Information
a similar problem with chest cavity

I don't know, intuition

It's not a very good reason to burden an infinite amount of unpaid work on someone's shoulders, don't ya think? :)
I'm not gonna implement compatibility with some random mods without strongly defined APIs that were not created to be used like that. Therefore, I will leave this to developers of the said mods, because this project has an API that was designed to be used like that, so, better luck with them :)


I2858-init-cond-sundials

Description

feed initial conditions for the sensitivity vectors to the idaklu solver (before was just initialised to 0)
call idagetsens after idacalcic to get the corrected initial conditions for sensitivity vectors
make the FD h a bit smaller to reduce numerical errors in sensitivity validation for models

Fixes #2858
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[x] No style issues: $ pre-commit run (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[x] All tests pass: $ python run-tests.py --all
[x] The documentation builds: $ python run-tests.py --doctest

You can run unit and doctests together at once, using $ python run-tests.py --quick.
Further checks:

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests added that prove fix is effective or that feature works

I'm thinking I can ignore the benchmark failures for now (https://github.com/pybamm-team/PyBaMM/issues/2954). What do you think @tinosulzer?

Yeah, I've been ignoring these


Meet 'cffi.api.CDefError: parse error' when make apps

hello:
when I make 3.12 version project ,I met the follow error:
make[1]: Entering directory /home/sheshou/hue-3.12.0/desktop' make -C core env-install make[2]: Entering directory /home/sheshou/hue-3.12.0/desktop/core'
--- Building egg for cryptography-1.3.1
Traceback (most recent call last):
File "", line 1, in
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/sandbox.py", line 238, in run_setup
raise
File "/usr/lib64/python2.7/contextlib.py", line 35, in exit
self.gen.throw(type, value, traceback)
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/sandbox.py", line 191, in setup_context
yield
File "/usr/lib64/python2.7/contextlib.py", line 35, in exit
self.gen.throw(type, value, traceback)
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/sandbox.py", line 162, in save_modules
saved_exc.resume()
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/sandbox.py", line 137, in resume
compat.reraise(type, exc, self._tb)
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/sandbox.py", line 150, in save_modules
yield saved
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/sandbox.py", line 191, in setup_context
yield
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/sandbox.py", line 235, in run_setup
DirectorySandbox(setup_dir).run(runner)
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/sandbox.py", line 265, in run
return func()
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/sandbox.py", line 234, in runner
_execfile(setup_script, ns)
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/sandbox.py", line 46, in _execfile
exec(code, globals, locals)
File "setup.py", line 335, in
**keywords_with_side_effects(sys.argv)
File "/usr/lib64/python2.7/distutils/core.py", line 112, in setup
_setup_distribution = dist = klass(attrs)
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/dist.py", line 269, in init
_Distribution.init(self,attrs)
File "/usr/lib64/python2.7/distutils/dist.py", line 287, in init
self.finalize_options()
File "/home/sheshou/hue-3.12.0/build/env/lib/python2.7/site-packages/setuptools/dist.py", line 325, in finalize_options
ep.load()(self, ep.name, value)
File "/usr/lib64/python2.7/site-packages/cffi/setuptools_ext.py", line 187, in cffi_modules
add_cffi_module(dist, cffi_module)
File "/usr/lib64/python2.7/site-packages/cffi/setuptools_ext.py", line 49, in add_cffi_module
execfile(build_file_name, mod_vars)
File "/usr/lib64/python2.7/site-packages/cffi/setuptools_ext.py", line 25, in execfile
exec(code, glob, glob)
File "src/_cffi_src/build_constant_time.py", line 26, in
extra_link_args=extra_link_args(compiler_type()),
File "src/_cffi_src/utils.py", line 73, in build_ffi
ffi.cdef(cdef_source)
File "/usr/lib64/python2.7/site-packages/cffi/api.py", line 105, in cdef
self._cdef(csource, override=override, packed=packed)
File "/usr/lib64/python2.7/site-packages/cffi/api.py", line 119, in _cdef
self._parser.parse(csource, override=override, **options)
File "/usr/lib64/python2.7/site-packages/cffi/cparser.py", line 299, in parse
self._internal_parse(csource)
File "/usr/lib64/python2.7/site-packages/cffi/cparser.py", line 304, in _internal_parse
ast, macros, csource = self._parse(csource)
File "/usr/lib64/python2.7/site-packages/cffi/cparser.py", line 262, in _parse
self.convert_pycparser_error(e, csource)
File "/usr/lib64/python2.7/site-packages/cffi/cparser.py", line 291, in convert_pycparser_error
raise api.CDefError(msg)
cffi.api.CDefError: parse error
:7:1: Illegal character '\r'
I'm using centos 7.2.
Waiting for your help ,thanks.

Problem solved, it is caused by difference between win's and unix's line feed. I edit some file in hue-3.12.0/desktop/core and the file's line feed style turn to win's style, just change it back and everything is ok.


sample merger & readcount_QC NA warning done

The output of rnaseqc sample merger can run within readcount_QC up to a point where mahalanobis  was calculated to identify outlier.
Error in solve.default(cov, ...) :
  Lapack routine dgesv: system is exactly singular: U[1,1] = 0
Calls: mahalanobis -> solve -> solve.default
Execution halted

The reason for this error is that there the three samples are too similar to each other, so that the covariance matrix of genes are all zero.
However, the fact that the output of readcount_QC can pass the data integrity check indicates that the merging is successful

Thanks @hsun3163 I believe that issue will be resolved with updated MWE (@floutt ).


Add 'running tests' comment for /test-extended

Update condition in pr-comment-bot.yml so that the "Running tests..." comment is also output for /test-extended

/test-force-approve
not tested by PR bot


Max number of Input file names

Hi!
trying to implement the solution ( over 2k sql table and sprocs)  to our sql project, I got the following message
Option 'Argument: table.sql' expects no more than 255 arguments, but 463 were provided.

Looking at the code I couldn't find a way to increase this limit, but it seems that it's probably defined in the dotnet commandline dependency .
Do you know if there is an easy way to change this limit?

Hi @leohinojosa. First of all, thanks for giving it a try. To be honest I wasn't expecting this. I'll have to dig into this a little bit. It could be related to dotnet/command-line-api#863, which looks to be fixed. Maybe I'll just need to update the dependency.

Ah it seems they merged it a couple of weeks ago,
I'll monitor the next release of command-line-api and send you a PR with the change
Thank you @jmezach

Looks like a new version of System.CommandLine has been released which should include the necessary fix for this. I've just pushed some changes for #9 which includes the update. Could you give this beta package a try to see if that fixes your issue?

Hi @leohinojosa, just a heads-up that 1.1.0 is out now on NuGet which should include the fix for this issue. I'll go ahead and close this now, but don't hesitate to re-open if it still doesn't work for you.

Will do! Thanks for the heads up!

New version works correctly,
however in my legacy project we have over 5k sql files, and in macos, we hit a limit on the max number of arguments passed to an executable.
I'll try to figure out a way to split this or to change the ulimits at the os level
Thank you !


Plan to TREs for comment

Questions for TRE's to discuss

Is it ok that the. query results don't get written to file until the usr calls acro.finalise()?

Has implications for our renaming functionality
but what if the user forgets! how do we prompt them?

Imagine a user goes off home, or for lunch etc., so calls finalise to save their work so far.

When they come back, do we want to do we want be able to restart a session or start a new one?
This has implications for being able to delete things if they decide they don't want them.
could we have functionality that let them have a choice here?

Do they prefer word doc then copy into their own python environment?
or python code with comments?
---We need a set of questions for them to think about

Goes to
Kate O'Sullivan at Dash/Aberdeen
Amy Tilbrook at Data loch
Pete Stokes & Seb Bacon at OpenSafely (Oxford)
Shahzad and Chris Cole at Dundee/HIC
Michael Sibley at eDRIS (Public Health Scotland)

Closed via email to partners 03/05/2023


Prevent package reference RabbitMQ.Client v 6.x

As we don't have support for RabbitMQ.Client 6.x #92, we should prevent that version. This fixes #89.

Thanks for sending the PR. We have upgraded RabbitMQ client version to 6.2.2 (#174) so this PR won't be needed. We should get 2.0.0 pre-release version of extension out in early February.


truffle init in VM shared folder

[ ] I've asked for help in the Truffle Gitter before filing this issue.

Issue
With Truffle 3.1.1, when I run truffle init in a folder that is shared between the VM and its host, I get an error message about cross-device link not permitted.
Steps to Reproduce

Create a VirtualBox VM with Ubuntu Trusty 64, in this case with Vagrant
Share a folder between host and VM, in this case named '/home/vagrant/DAPPS in VM
Install Truffle 3.1.1 in VM
Go to a subfolder of the shared folder in VM, in this case '/home/vagrant/DAPPS/temp1
run truffle init in VM

Expected Behavior
I expect it to create the MetaCoin project.
Actual Results
$ truffle init
        Downloading project...
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: EXDEV: cross-device link not permitted, rename '/home/vagrant/DAPPS/temp1/1486478769218-3521399717528142/truffle-init-default-master' -> '/tmp/default-11717-22397-hs20ew.pvdy8hbyb9'
    at Error (native)

Environment

Operating System:

VM: Linux vagrant-ubuntu-trusty-64 3.13.0-107-generic #154-Ubuntu SMP Tue Dec 20 09:57:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Host: MacOS 10.12.3
VirtualBox 5.1.14

Truffle version: 3.1.1
Ethereum client: TestRPC 3.0.3 but should be irrelevant
node version: 6.9.5
npm version: 3.10.10

I've found this error on a Windows machine but I'm surprised you're seeing it on Linux. The issue is that the system-wide temp directory exists on a different physical device than your project directory. During init, the example project is downloaded to the temp directory and then moved to your project directory. I'm not entirely sure why this is an error, and why you can't have cross device links. I'll have to look further into it, but any help would be much appreciated.

It looks like some people have covered it in at least one package:

https://www.npmjs.com/package/mv
https://www.npmjs.com/package/node-mv

I actually have this issue in a stock linux-mint-17 system (my /tmp is on a different partition from /home).
I thought
npm config set tmp /home/scott/tmp
should fix things, but it seems to have a hard coded /tmp somewhere in the code.

I saw this as well on ubuntu with /home and /tmp in different partitions.
simple workaround is to set the TEMP env var, e.g.
TEMP=~/tmp truffle init

Fixed this by creating our own temporary directory within the current working directory (I'd use the mv module, but unfortunately the issue is in the github downloader dependency). Since this was fixed in one of Truffle's dependencies, you can get the updated version by uninstalling then reinstalling Truffle. Truffle's version number will remain the same.
Cheers! Thanks for the report!


Fix downgrade from Cilium 1.2 to earlier versions

Commits 607b8179ff7a ("option: Refactor BoolOptions into IntOptions")
and 8f0279e3788e ("endpoint: Rename Opts -> Options") reworked the
options for an endpoint to be based on integers rather than booleans. To
avoid introducing upgrade problems, the field was renamed. However, this
introduced downgrade problems: If an endpoint is created when running
Cilium 1.2 or later, then the Cilium version is set to 1.1 or earlier,
then the earlier version of Cilium will attempt to restore the endpoints
that were serialized to the lxc_config.h from Cilium 1.2.
Since Cilium 1.2 doesn't serialize the Opts field (as map[string]bool)
the earlier version of Cilium can't restore the options correctly, and
as a result may dereference the options field of such restored endpoints
and even crash.
To avoid this, on newer versions of Cilium we will always serialize both
forms of the options: the Opts (map[string]bool) from earlier
versions, and Options (map[string]int) from newer versions. This means
that older versions can restore using Opts, and newer versions can
restore using Options.
In a subsequent Cilium release, perhaps 1.5 or later, we can consider
dropping support for downgrade to 1.1 or earlier and remove this code.
Fixes: #4899
Manually tested via cilium/cilium:fix-options-downgrade image on DockerHub, then following v1.0 upgrade instructions.

This change is

test-me-please

test-me-please

Green build, I'll rebase and do a comment update to address @ianvernon's comment.


Route not loading in some cases

Route-lädt-nicht-logs (1).txt
Route-lädt-nicht-2 (1).txt
Route-lädt-nicht-3 (1).txt

Did not observe this bug anymore in the last weeks, can be reopened when the bug appears again.


Add buildTime cli flag

issue #8787
If I understand @regisphilibert 's comment properly, with the flag, users want to check

future/expired content's manners
now in template
hugo list output

If so, we can implement this flag by just replacing a few of time.Now() without changing internal time of go.
This PRs add buildTime flag in order to fake hugo's build datetime like so
hugo --buildTime 2021-11-06
hugo --buildTime 2021-11-06 server
hugo --buildTime 2021-11-06 list future
hugo --buildTime 2021-11-06 list expired

Close #8787

This is a feature that would make my life a lot easier. What are the chances of getting this reviewed and rebased any time soon?

This is a feature that would make my life a lot easier. What are the chances of getting this reviewed and rebased any time soon?

Thumbs up and useful contributions tend to do that ;)
The "build time" moniker is slightly misleading but I like the concept. If it has enough testing to make sure it works as expected and when the "conflicts that must be resolved" are resolved (probably just a fetch of the current HEAD and re-check) our little conversation here will put it in the TODO pile again and someone who knows Golang will surely have a look.

@satotake Are you still interested in this issue/PR?  If not, I'd be happy to take it over and do a rebase in a new PR.

Honestly, this PR has been a dim memory for me but rebasing and resolving were not so tough.
Thanks for your offer, @flimzy .
If you do not mind, could you review this PR or have any idea, @bep?
Especially, my concern is flag name as @davidsneighbour said.

OK, I have thought some more about this, and I think we need to do an adjustment.
The thing is, when we're changing the build time, I also suspect people would also expect the clock to change in other situations, e.g.:
{{ ge .PublishDate now }}

Should always print true.
With that in mind, I think we need a ... clock.
What I suggest is that we

rename the buildTime flag to clock (?)
rework the implementation in this PR to also consider the system clock. I have toyed around with this package tonight, which I thinks should be simple enough to reason about: https://github.com/bep/clock
Replace all usage of time.Now with htime.Now

Thoughts?

rename the buildTime flag to clock (?)

Looks good. I thought just time or date might be ambiguous for this.

rework the implementation in this PR to also consider the system clock. I have toyed around with this package tonight, which I thinks should be simple enough to reason about: https://github.com/bep/clock

I have presumed fixed time for this. yes but it is ok to make it running. I will check it your package.

Replace all usage of time.Now with htime.Now

Not sure but I suspect that they are not all but most. For example, values for logging and so on? Anyway, I will check it, too.

Thanks, I have rebased this into a new PR and will finish this in #9864

ok
I replaced time.Now with htime.Now as much as possible (including logging) for now.
except for

values in tests
seed value for random
cloudfront deploy


What if i have to append multiple html table to the same sheet, how can i achieve it?

Hi, thanks for job. What if i have to append multiple html table to the same sheet, how can i achieve it? Thanks.

In our Pro builds, we have a separate sheet_add_dom function for this use case, we'll merge it here in the next release


FourierMMD Refactor + Optimization

This PR changes some of the data structures in the FourierMMD metric codebase to better align with Java principles, as well as changes some algorithm flows to better optimize computation.

/test trustyai-explainability-e2e


Add best practice encryption requirements.

Hello David, what do you think about adding requirements for the type of encryption they're using?

I love the idea of adding specific requirements for encryption - but they need to be specific.  The proposal here reads:
"Encryption mechanisms must make use of open standards and follow best practices such as strong cipher suites and perfect forward secrecy whenever possible."
A few points:

We'd need to define "open standards" (presumably by pointing to a definition).  However, I suspect many definitions would exclude Bernstein's Curve25519, yet OpenSSH and GPG use Curve25519-based ECDH.  Ugh.  Perhaps you mean "not patented" but since the US patent office (at least) doesn't spend serious time reviewing applications, all sorts of pre-existing algorithms are (re)patented, and some things are patented but freely licensed.  Perhaps instead require that they support at least algorithm and protocol that is defined in some specification that meets the "Open Standards Requirement for Software" as define in http://opensource.org/osr.
I don't know what 'best practices' means here.  Everyone says that they follow best practices.  Either throw away the phrase or point to a specific definition.
What's a "strong" cipher suite?  I know what you mean in principle, but again, we need to be specific.  Probably better to point to somebody - or a group of somebodies - who defines that.  I nice site for this is http://www.keylength.com/.  We could pick specific lengths, and justify them via that site.
"Perfect forward secrecy whenever possible" - NOW we're talking!  The "whenever possible" wiggle room might not be enough (if it's impractical but possible, who cares?).  Still, that is a nice specific term that is easy to test... either it has it, or it doesn't.

Could you whip up a more detailed draft requirement based on this?  Feel free to include text to justify it (particularly any keylength requirements).

Here's my shot.  I'll add this to the draft criteria.  Please take a look and suggest improvements...!
Uses basic good cryptographic practices.
The cryptographic mechanisms used by the software, and its delivery mechanisms, implement the following basic good practices:
1.  Cryptographic protocols and algorithms used by default MUST be publicly published and reviewed by experts.
2.  Application software that is not itself a cryptographic system/library MUST NOT implement its own cryptographic functions, but MUST instead call on software specifically designed for the purpose.
3.  All functionality that depends on cryptography MUST be implementable using OSS because its specification meets the Open Standards Requirement for Software by the Open Source Initiative
4.  The keylengths MUST meet NIST requirements through the year 2030. For example, symmetric keys must be at least 112 bits, factoring modulus must be at least 2048 bits, and elliptic curve must be at least 224 bits.  See http://www.keylength.com for a comparison of keylength recommendations from various organizations.
5.  Any key agreement protocol MUST implement perfect forward secrecy where practical so a session key derived from a set of long-term keys cannot be compromised if one of the long-term keys is compromised in the future.
6.  Security mechanisms MUST NOT depend on MD4, MD5, or single DES, as these algorithms are broken or have overly short key lengths.  It is RECOMMENDED that SHA-1 not be used (we are well aware that git uses SHA-1).  Recommended algorithms include AES and SHA-256 (or higher).  Implementations SHOULD support multiple cryptographic algorithms, so users can quickly switch if one is broken.
7.  If passwords for later authentication are stored, they must be stored as iterated hashes with per-user salt.
8.  All keys and nonces MUST be generated using cryptographically random functions, and not through non-cryptographically random functions.

Sounds good to me!

David, this is an impressive start, and it's somewhat surprising to think
that there's not an RFC or other document we can reference that provides
this level of guidance. I would suggest explicitly asking for help from
crypto experts at cii-corps and cii-all, and particularly Brian Green.
Under "The keylengths MUST" you may want "The default keylengths MUST"
because I believe a number of crypto libraries still (unfortunately)
support less.
--
Dan Kohn<EMAIL_ADDRESS>tel:+1-415-233-1000
On Mon, Aug 24, 2015 at 5:35 PM, David A. Wheeler<EMAIL_ADDRESS>wrote:

Here's my shot. I'll add this to the draft criteria. Please take a look
and suggest improvements...!
Uses basic good cryptographic practices.
The cryptographic mechanisms used by the software, and its delivery
mechanisms, implement the following basic good practices:

Cryptographic protocols and algorithms used by default MUST be publicly
published and reviewed by experts.
Application software that is not itself a cryptographic system/library
MUST NOT implement its own cryptographic functions, but MUST instead call
on software specifically designed for the purpose.
All functionality that depends on cryptography MUST be implementable
using OSS because its specification meets the Open Standards Requirement
for Software by the Open Source Initiative http://opensource.org/osr
The keylengths MUST meet NIST requirements through the year 2030. For
example, symmetric keys must be at least 112 bits, factoring modulus must
be at least 2048 bits, and elliptic curve must be at least 224 bits. See
http://www.keylength.com for a comparison of keylength recommendations
from various organizations.
Any key agreement protocol MUST implement perfect forward secrecy where
practical so a session key derived from a set of long-term keys cannot be
compromised if one of the long-term keys is compromised in the future.
Security mechanisms MUST NOT depend on MD4, MD5, or single DES, as
these algorithms are broken or have overly short key lengths. It is
RECOMMENDED that SHA-1 not be used (we are well aware that git uses SHA-1).
Recommended algorithms include AES and SHA-256 (or higher). Implementations
SHOULD support multiple cryptographic algorithms, so users can quickly
switch if one is broken.
If passwords for later authentication are stored, they must be stored
as iterated hashes with per-user salt.
All keys and nonces MUST be generated using cryptographically random
functions, and not through non-cryptographically random functions.

—
Reply to this email directly or view it on GitHub
https://github.com/linuxfoundation/cii-best-practices-badge/pull/3#issuecomment-134387640
.

Dan: Fair point.  I modified the text to say "default... MUST", and in addition, I added that the software MUST be configurable so that it would reject the shorter lengths.  I think we're of the same mind - shorter lengths are bad, but sometimes you HAVE to accept them for interoperability's sake.  (Otherwise you force the communication to go into the clear, which is even worse.)
See commit 85de9b63.


Dynamic Theme

There is no Dynamic theme available in aniyomi for A12,
Idk if it wasn't added from mainstream or just not caught yet to date.

Closing as mpv beta has it already.