Add ability to plot current, force and actuation voltage (Trac #49)

Migrated from http://microfluidics.utoronto.ca/ticket/49
{
    "status": "new",
    "changetime": "2014-04-17T19:40:13",
    "description": "\n",
    "reporter": "ryan",
    "cc": "",
    "resolution": "",
    "_ts": "1397763613851119",
    "component": "microdrop",
    "summary": "Add ability to plot current, force and actuation voltage",
    "priority": "minor",
    "keywords": "",
    "version": "0.1",
    "time": "2012-02-20T03:47:13",
    "milestone": "Microdrop 1.1",
    "owner": "ryan",
    "type": "enhancement"
}

Trac update at 20120220T04:04:55: ryan changed summary from "Add ability to plog current, force and actuation voltage" to "Add ability to plot current, force and actuation voltage"

Trac update at 20120801T15:49:39: ryan changed milestone from "0.2" to "0.3"

Trac update at 20140417T19:40:13: ryan changed component from "gui" to "microdrop"

This was implemented a long time ago in the dmf-control-board-plugin.


Zombie Servers

Hola!
Great start! So many ideas to take this further, why don't you start with zombie servers? E.g. VMs that are officially in use but have not shown any business activity for the last X months?
Tom

Hi,
I think it depends a little bit on the definition. Low CPU utilization could be an indication, but it might also just be overprovisioning. There has been some research from Koomey (the researcher behind Koomey's Law) about how many VMs  we're talking about, and some way's how to recognize them. The research is a bit older, but still getting referenced now and then: https://www.anthesisgroup.com/zombie-servers-hunting-down-the-lost-capital/
In short: focus on a lack of connectivity to the machine, are these metrics you are already collecting?
Tom


chore: v0.0.1

Description
chore: v0.0.1

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[x] 🗑 Chore

I am self approving this.

Well, I shouldn't have


Future of apt-cyg

Hi, I see your last commit, regarding the message in README.
-STATUS UPDATE 1-24-2016:
 ------------------------
 +And now back to apt-cyg ;)

 -Over the weekend apt-cyg lost it's only active maintainer. Since I am working on other things now,
 -this project is basically read-only. That means I won't be responding to bug reports or issues.
 -
 -If you have a problem with apt-cyg:
 -
 -1. You might be able to fork it and fix it yourself, if you enjoy BASH programming
 -2. Look for forks with an active maintainer, pick one that works for you, vote it up.
 -
 -And now back to apt-cyg...

Should we consider transcode-open/apt-cyg to be main repo of apt-cyg and continue to report issues/pull reqs here, or should we actively look for another home of apt-cyg?
Do you need volunteers?
What do you propose?

Any news on this one? Is the project dead?

https://github.com/svnpenn/sage/issues/14

I don't think it's dead.  It's fairly mature and stable.  It lacks some advanced features that would be nice to have.  They can be added someday.  Pull requests are welcome, I'm sure.  e.g. adding the upgrade function probably wouldn't be that difficult.

@alphapapa check this https://github.com/svnpenn/sage/issues/2 https://github.com/svnpenn/sage/issues/3 It seems we should abandon apt-cyg, use sage instead.

@jingsam I don't recommend that.  See https://github.com/transcode-open/apt-cyg/issues/73#issuecomment-225156152

I do some digging, trying to figure out what happened. I definitely agree with that transcode-open owns this repo. However, I doubt that how much he contribute to apt-cyg. Let's check his commit history:

6 commits over last year! It seems that what transcode-open actually own is the name of this repo. He did not respond to users, not maintain the code, just let this project die.
I am happy to see svnopen fork this project and actively maintain it. I think the owner of apt-cyg should be the one who cares about it.

@jingsam I feel like you didn't read very much of the comment I linked.
What Mr. Jungels owns is the copyright to the original code (perhaps most of the current code, as well), this repo, and the copyright on the name.  What Mr. Penny owns is the copyright to the code he has contributed.
The phrase "the owner of apt-cyg" may mean different things to different people.  But since this is Free Software, it's not very relevant--at least, until someone starts making false legal claims to attempt a hostile takeover of the project.
If you feel comfortable with the actions of the fork's author, you're welcome to use the fork.  That's the point of Free Software: to empower users.

https://github.com/kou1okada/apt-cyg appears to be the most active fork.

@alphapapa I noticed kou1okada used setup*.exe.  I tried using a secondary root idea with an in-place post-install script invocation as a last step in my pull https://github.com/transcode-open/apt-cyg/pull/88.

Alternatively, @transcode-open can invite collaborator(s) to maintain the project in his stead.


Make console output visible for hclient in command line mode

On Windows 7 using VS 2017 when using hclient no console output was visible. This patch makes the console output visible again.

@jovermann, do you have any insights on why it doesn't work on Win7 using VS2017? Is it the problem on Win7 or VS2017? Does the same binary (built using VS2017) work on Win8+?


Add links to hosted traces on Explorer

This PR adds links to the agentdojo results as hosted on Invariant Explorer.
The links to each run are added to the Results table in the documentation. I also added some more pointers to the results page in the README and documentation. I hope that's ok.

Results on Explorer look like this: https://explorer.invariantlabs.ai/u/invariant/agentdojo-meta-llama_Llama-3-70b-chat-hf/t/1

this was merged prematurely due to a wrong push. I undid that and created a separate PR.


Experiment with building route graphs over n-grams

We might well be able to solve the problems of:

Ambiguity in circular routes
Deciding which "direction" a journey is

By building a graph over bigrams/trigrams of locations.
That however would mean that the topological sort for station ordering yields bigrams, so we'll need to find a way to coalesce them. We might be able to do that with a custom topological sort mechanism.

Looking at the north kent circular routes that start and end at Cannon St. This query seems to imply that bigrams of public stops form a directed acyclic graph:

Query
with stns as (
  select
  m.key,
  first_value(elt.value ->> 'tpl') over journey_w as first_stop,
  last_value(elt.value ->> 'tpl') over journey_w as last_stop,
  coalesce(lag(elt.value ->> 'tpl') over journey_w, '_') as tiploc_prev,
  elt.value ->> 'tpl' as tiploc,
  coalesce(lead(elt.value ->> 'tpl') over journey_w, '_') as tiploc_next
  from raw_journeys as m
    join lateral jsonb_array_elements(m.value -> 'points') WITH ORDINALITY AS elt on true
  where m.key like 'raw-journey/20200102%'
  and m.value ->> 'toc' = 'SE'
  and coalesce(elt.value ->> 'pta', elt.value ->> 'ptd') is not null
  window journey_w as (partition by m.key order by elt.ordinality ROWS BETWEEN UNBOUNDED PRECEDING and UNBOUNDED FOLLOWING)
)
select '"' || tiploc_prev || '-' || tiploc || '"' || ' -> ' ||  '"' || tiploc || '-' || tiploc_next || '"'
from stns
where first_stop = 'CANONST' and last_stop = 'CANONST'
group by tiploc_prev, tiploc, tiploc_next;

It's probably worth having a fiddle with a:

Transitive reductions
Alloy for any algorithmic fanciness

So to turn this into a meaningful topological order of stations, it's sorta kinda ranking problem. If we treat each vertex label as a two-tuple (ie: station and successor) we want to find an ordering where:

Each rank contains one station
Each rank may reference multiple successors
We maximise the number of vertexes mapped to each rank

Sounds like it might be a case for … integer programming! Or similar.

We should probably split this into two bits:

Represent the route structure as n-grams

Ingest to a set of ngrams
Naive topological sort over the ngrams (eg: pick first / last element of n-gram as "location") to produce layout.

Figure out how to optimise the layout.

We might be able to use Coffman–Graham here.
Or mess about with constraint solvers some more.

https://github.com/cstorey/nrod/pull/90 does the first part.

One thing that might be an issue is attempting to compare ranks for nodes in disjoint parts of the graph. So It's probably worth pre-processing to find disjoint-sets before hand to avoid that issue.


eth_call errors out when transaction.to is set to null

Description
Currently, eth_call will reject requests that have transaction.to set to null. However, it should accept nullable transaction.to in the cases of contract deployment.
Steps to reproduce

Run below cURL request

curl --location 'https://testnet.hashio.io/api' \
--header 'Content-Type: application/json' \
--data '{
    "id": "test_id",
    "jsonrpc": "2.0",
    "method": "eth_call",
        "params": [{
            "from":"0x05fba803be258049a27b820088bab1cad2058871",
            "to": null,
            "data":"0x60806040"}, "latest"]
}'

Observe the response to see the error like below

{"error":{"code":-32602,"name":"Invalid parameter","message":"[Request ID: b2a2c4cf-1ce4-4a56-bbc3-c25e51c51c53] Invalid parameter 'to' for TransactionObject: Expected 0x prefixed string representing the address (20 bytes), value: null"},"jsonrpc":"2.0","id":"test_id"}

Additional context
No response
Hedera network
mainnet, testnet, previewnet, other
Version
latest
Operating system
None

Blocking by https://github.com/hashgraph/hedera-mirror-node/issues/8072

The ArianeLabs team identified a problem when trying to use Brownie with Hedera Testnet. It appears that before executing a transaction, Brownie tries to execute an eth_call with the same params to check if the transaction would cause a revert. When they tried to deploy a smart contract, Hedera responded with "Invalid Contract Address: undefined" for such a call.

cc. @arianejasuwienas
After investigation, we realized this problem is caused by the non-nullable to field.


docs(i18n): Add translation mechanism

Description
Chinese documentation is so important !
Problem Statement/Justification
There are a large number of developers in China who are limited by their English level and cannot use many advanced and powerful libraries.
Proposed Solution or API
good
Alternatives
No response
Additional Information
No response
Proposed workflow

[ ] Check if localization works
[ ] Check the language switcher
[ ] Bring back the i18n config in Next.js
[ ] Create a new LOCALIZATION.md document that outlines how to contribute to the localization
[ ] Create a new folder in i18n to keep the alternative-language docs
[ ] Modify the getStaticProps, get the locale property from the ctx and return the corresponding mdx file
[ ] Figure out a way to notify translations when changes occur in the existing English pages

I will be taking this!

Not stale :D

Not stale, assigning this on @noobinthisgame since he has a PR open about this.


Using Microsoft.Powershell.SDK 7.4.5 (.NET Core 8) on Ubuntu 24.04 fails loading libpsl-native

Steps to reproduce
Using Microsoft.PowerShell.SDK fails on Ubuntu 24.04 with the following exception
Unhandled exception. System.TypeInitializationException: The type initializer for 'System.Management.Automation.Tracing.PSEtwLog' threw an exception.
 ---> System.TypeInitializationException: The type initializer for 'System.Management.Automation.Tracing.PSSysLogProvider' threw an exception.
 ---> System.DllNotFoundException: Unable to load shared library 'libpsl-native' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace.

The Microsoft.PowerShell.Native Nuget package containing the missing libpsl-native.so is available on the system. If I check the /runtimes folder, instead of
/home/<appPath>/runtimes/unix/lib/net8.0/libpsl-native.so
as the stacktrace implies, libpsl-native.so is located in
/home/<appPath>/runtimes/linux-x64/native/libps-native.so
So it seems, something is off with the nuget package(s).
The package used is Microsoft.Powershell.SDK 7.4.5
Expected behavior
.NET Core application is able to create a runspace to run powershell commands

Actual behavior
An exception is thrown pointing out that libpsl-native.so cannot be found

Error details
Unhandled exception. System.TypeInitializationException: The type initializer for 'System.Management.Automation.Tracing.PSEtwLog' threw an exception.
 ---> System.TypeInitializationException: The type initializer for 'System.Management.Automation.Tracing.PSSysLogProvider' threw an exception.
 ---> System.DllNotFoundException: Unable to load shared library 'libpsl-native' or one of its dependencies. In order to help diagnose loading problems, consider using a tool like strace. If you're using glibc, consider setting the LD_DEBUG environment variable:
/usr/lib/dotnet/shared/Microsoft.NETCore.App/8.0.8/libpsl-native.so: cannot open shared object file: No such file or directory
/home/<appPath>/runtimes/unix/lib/net8.0/libpsl-native.so: cannot open shared object file: No such file or directory
/usr/lib/dotnet/shared/Microsoft.NETCore.App/8.0.8/liblibpsl-native.so: cannot open shared object file: No such file or directory
/home/<appPath>/runtimes/unix/lib/net8.0/liblibpsl-native.so: cannot open shared object file: No such file or directory
/usr/lib/dotnet/shared/Microsoft.NETCore.App/8.0.8/libpsl-native: cannot open shared object file: No such file or directory
/home/<appPath>/runtimes/unix/lib/net8.0/libpsl-native: cannot open shared object file: No such file or directory
/usr/lib/dotnet/shared/Microsoft.NETCore.App/8.0.8/liblibpsl-native: cannot open shared object file: No such file or directory
/home/<appPath>/runtimes/unix/lib/net8.0/liblibpsl-native: cannot open shared object file: No such file or directory

   at System.Management.Automation.Tracing.NativeMethods.OpenLog(IntPtr ident, SysLogPriority facility)
   at System.Management.Automation.Tracing.SysLogProvider..ctor(String applicationId, PSLevel level, PSKeyword keywords, PSChannel channels)
   at System.Management.Automation.Tracing.PSSysLogProvider..cctor()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Tracing.PSSysLogProvider..ctor()
   at System.Management.Automation.Tracing.PSEtwLog..cctor()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Tracing.PSEtwLog.LogOperationalInformation(PSEventId id, PSOpcode opcode, PSTask task, PSKeyword keyword, Object[] args)
   at System.Management.Automation.Remoting.RemoteSessionNamedPipeServer.ProcessListeningThread(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

Environment data
Name                           Value
----                           -----
PSVersion                      7.4.5
PSEdition                      Core
GitCommitId                    7.4.5
OS                             Ubuntu 24.04.1 LTS
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

Hi, fortunately I have a project ready to go to demo this.
Check the environment
$ grep ID /etc/os-release
VERSION_ID="24.04"
ID=ubuntu
ID_LIKE=debian

First compile and run in one step....
$ dotnet run --framework net8.0 -OutputString echo foo
foo

That works, so now run the dll with dotnet
$ dotnet bin/Release/net8.0/pwshexec.dll  -OutputString echo foo
foo

That works, so run the compiled program
$ bin/Release/net8.0/pwshexec -OutputString echo foo
foo

So all present and correct
$ find bin -name "libpsl*.so"
bin/Release/net8.0/runtimes/linux-arm/native/libpsl-native.so
bin/Release/net8.0/runtimes/linux-x64/native/libpsl-native.so
bin/Release/net8.0/runtimes/linux-arm64/native/libpsl-native.so
bin/Release/net8.0/runtimes/linux-musl-x64/native/libpsl-native.so

So lets remove those shared libraries
$ find bin -name "libpsl*.so" | xargs rm

Now try and run and we get a similar list as you get searching for a library. Except it alternates looking for unix and linux-x64 which seems appropriate. Now yours only looks under unix which is odd.
The only dotnet-sdk I have on my machine is dotnet-sdk-8.0 provided by Ubuntu.
Is your app compiled for 'any' or for a specific architecture?

Turns out, the assembly that called "my" code had a custom AssemblyLoadContext implementation that had a Bug. Issue is resolved. Thanks for your input.


Multiple nodes span up non stop

Version

Karpenter: v0.13.0

Kubernetes: v1.20.0
Expected Behavior

Deployment with 1 replica should scale 1 node
Actual Behavior

Started spining up non stop
Steps to Reproduce the Problem

kind: Deployment
metadata:
  name: k8s
  namespace: karpenter
spec:
  replicas: 1
  selector:
    matchLabels:
      app: curl
  template:
    metadata:
      labels:
        app: curl
    spec:
      containers:
        - name: redis
          image: jshimko/kube-tools-aws:3.8.1
          command:
            - /bin/sh
            - '-c'
            - |
              chmod u+x /scripts/script.sh
              /scripts/script.sh
      tolerations:
        - key: "sample-taint"
          operator: "Exists"
          effect: "NoSchedule"
      nodeSelector:
        sample: karpenter
---
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  name: sample
  namespace: karpenter
spec:
  requirements:
    - key: karpenter.sh/capacity-type
      operator: In
      values: ["spot"]
    - key: "node.kubernetes.io/instance-type"
      operator: In
      values: [ "m5a.large", "m5a.2xlarge" ]
  limits:
    resources:
      cpu: 1000
      memory: 1000Gi
  providerRef:
    name: sample
  ttlSecondsAfterEmpty: 3000
  ttlSecondsUntilExpired: 2592000
  taints:
    - key: sample-taint
      effect: NoSchedule
  labels:
    sample: karpenter
---

apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
  name: sample
  namespace: karpenter
spec:
  amiFamily: AL2
  instanceProfile: eks-nodes-us-east-1
  subnetSelector:
    kubernetes.io/cluster/research-us-east-1: shared
  securityGroupSelector:
    kubernetes.io/cluster/research-us-east-1: owned
  userData:  |
    MIME-Version: 1.0
    Content-Type: multipart/mixed; boundary="BOUNDARY"

    --BOUNDARY
    Content-Type: text/x-shellscript; charset="us-ascii"

    #!/bin/bash
    yum install -y amazon-ssm-agent
    systemctl enable amazon-ssm-agent && systemctl start amazon-ssm-agent

    --BOUNDARY--

Resource Specs and Logs

2022-06-28T17:36:09.792Z	INFO	controller.provisioning.cloudprovider	Launched instance: i-04e4c54f11f2bd4b9, hostname: ip-10-209-176-136.ec2.internal, type: m5a.large, zone: us-east-1c, capacityType: spot	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:09.799Z	INFO	controller.provisioning	Created node with 1 pods requesting {"cpu":"110m","pods":"5"} from types m5a.large, m5a.2xlarge	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:09.799Z	INFO	controller.provisioning	Waiting for unschedulable pods	{"commit": "37c8653"}
2022-06-28T17:36:09.799Z	DEBUG	controller.events	Normal	{"commit": "37c8653", "object": {"kind":"Pod","namespace":"karpenter","name":"k8s-5f99fffc65-h4hmv","uid":"759d772f-5ecf-4620-b7fb-ef5acc7e9241","apiVersion":"v1","resourceVersion":"91337062"}, "reason": "NominatePod", "message": "Pod should schedule on ip-10-209-176-136.ec2.internal"}
2022-06-28T17:36:12.684Z	INFO	controller.provisioning	Found 1 provisionable pod(s)	{"commit": "37c8653"}
2022-06-28T17:36:12.684Z	INFO	controller.provisioning	Computed 1 new node(s) will fit 1 pod(s)	{"commit": "37c8653"}
2022-06-28T17:36:15.850Z	INFO	controller.provisioning.cloudprovider	Launched instance: i-0d73aa909aecca2d9, hostname: ip-10-209-189-176.ec2.internal, type: m5a.large, zone: us-east-1c, capacityType: spot	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:15.855Z	INFO	controller.provisioning	Created node with 1 pods requesting {"cpu":"110m","pods":"5"} from types m5a.large, m5a.2xlarge	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:15.856Z	INFO	controller.provisioning	Waiting for unschedulable pods	{"commit": "37c8653"}
2022-06-28T17:36:15.856Z	DEBUG	controller.events	Normal	{"commit": "37c8653", "object": {"kind":"Pod","namespace":"karpenter","name":"k8s-5f99fffc65-h4hmv","uid":"759d772f-5ecf-4620-b7fb-ef5acc7e9241","apiVersion":"v1","resourceVersion":"91337062"}, "reason": "NominatePod", "message": "Pod should schedule on ip-10-209-189-176.ec2.internal"}
2022-06-28T17:36:17.864Z	INFO	controller.provisioning	Found 1 provisionable pod(s)	{"commit": "37c8653"}
2022-06-28T17:36:17.864Z	INFO	controller.provisioning	Computed 1 new node(s) will fit 1 pod(s)	{"commit": "37c8653"}
2022-06-28T17:36:19.906Z	INFO	controller.provisioning.cloudprovider	Launched instance: i-0a641aaadf08dd410, hostname: ip-10-209-182-63.ec2.internal, type: m5a.large, zone: us-east-1c, capacityType: spot	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:19.913Z	INFO	controller.provisioning	Created node with 1 pods requesting {"cpu":"110m","pods":"5"} from types m5a.large, m5a.2xlarge	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:19.913Z	INFO	controller.provisioning	Waiting for unschedulable pods	{"commit": "37c8653"}
2022-06-28T17:36:19.913Z	DEBUG	controller.events	Normal	{"commit": "37c8653", "object": {"kind":"Pod","namespace":"karpenter","name":"k8s-5f99fffc65-h4hmv","uid":"759d772f-5ecf-4620-b7fb-ef5acc7e9241","apiVersion":"v1","resourceVersion":"91337421"}, "reason": "NominatePod", "message": "Pod should schedule on ip-10-209-182-63.ec2.internal"}
2022-06-28T17:36:22.687Z	INFO	controller.provisioning	Found 1 provisionable pod(s)	{"commit": "37c8653"}
2022-06-28T17:36:22.687Z	INFO	controller.provisioning	Computed 1 new node(s) will fit 1 pod(s)	{"commit": "37c8653"}
2022-06-28T17:36:25.006Z	INFO	controller.provisioning.cloudprovider	Launched instance: i-0e26da07b325fe270, hostname: ip-10-209-176-81.ec2.internal, type: m5a.large, zone: us-east-1c, capacityType: spot	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:25.010Z	INFO	controller.provisioning	Created node with 1 pods requesting {"cpu":"110m","pods":"5"} from types m5a.large, m5a.2xlarge	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:25.010Z	INFO	controller.provisioning	Waiting for unschedulable pods	{"commit": "37c8653"}
2022-06-28T17:36:25.010Z	DEBUG	controller.events	Normal	{"commit": "37c8653", "object": {"kind":"Pod","namespace":"karpenter","name":"k8s-5f99fffc65-h4hmv","uid":"759d772f-5ecf-4620-b7fb-ef5acc7e9241","apiVersion":"v1","resourceVersion":"91337421"}, "reason": "NominatePod", "message": "Pod should schedule on ip-10-209-176-81.ec2.internal"}
2022-06-28T17:36:27.874Z	INFO	controller.provisioning	Found 1 provisionable pod(s)	{"commit": "37c8653"}
2022-06-28T17:36:27.874Z	INFO	controller.provisioning	Computed 1 new node(s) will fit 1 pod(s)	{"commit": "37c8653"}
2022-06-28T17:36:29.888Z	INFO	controller.provisioning.cloudprovider	Launched instance: i-08faff28e54394003, hostname: ip-10-209-182-33.ec2.internal, type: m5a.large, zone: us-east-1c, capacityType: spot	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:29.895Z	INFO	controller.provisioning	Created node with 1 pods requesting {"cpu":"110m","pods":"5"} from types m5a.large, m5a.2xlarge	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:29.895Z	INFO	controller.provisioning	Waiting for unschedulable pods	{"commit": "37c8653"}
2022-06-28T17:36:29.895Z	DEBUG	controller.events	Normal	{"commit": "37c8653", "object": {"kind":"Pod","namespace":"karpenter","name":"k8s-5f99fffc65-h4hmv","uid":"759d772f-5ecf-4620-b7fb-ef5acc7e9241","apiVersion":"v1","resourceVersion":"91337796"}, "reason": "NominatePod", "message": "Pod should schedule on ip-10-209-182-33.ec2.internal"}
2022-06-28T17:36:32.686Z	INFO	controller.provisioning	Found 1 provisionable pod(s)	{"commit": "37c8653"}
2022-06-28T17:36:32.686Z	INFO	controller.provisioning	Computed 1 new node(s) will fit 1 pod(s)	{"commit": "37c8653"}
2022-06-28T17:36:35.015Z	INFO	controller.provisioning.cloudprovider	Launched instance: i-08a28b6ca20504ffe, hostname: ip-10-209-180-67.ec2.internal, type: m5a.large, zone: us-east-1c, capacityType: spot	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:35.033Z	INFO	controller.provisioning	Created node with 1 pods requesting {"cpu":"110m","pods":"5"} from types m5a.large, m5a.2xlarge	{"commit": "37c8653", "provisioner": "sample"}
2022-06-28T17:36:35.033Z	INFO	controller.provisioning	Waiting for unschedulable pods	{"commit": "37c8653"}```

This was an artifact of two separate PRs that merged and conflicted, it was fixed in https://github.com/aws/karpenter/pull/2010 . We should have a patch release out soon.

Closing as this has been released now.


[BUG] ChatRequestUserMessage content is binaryData

There is a bug where ChatRequestSystemMessage.content is a String, while ChatRequestUserMessage.content is binaryData. Due to this, OpenAI cannot decode text in UTF-8 when sending ChatRequestUserMessage with russian or kazakh languages.
Response from OpenAi:
I am sorry, but I cannot recognize your message. Please describe your question in Russian or Kazakh so that I can help you.
To Reproduce
Give non-English text in ChatRequestUserMessage to OpenAi
Expected behavior
I expected both ChatRequestSystemMessage and ChatRequestUserMessage contents to be interpreted as String, allowing OpenAI to correctly process text in Russian or Kazakh.
Code Snippet:
        chatMessages.add(new ChatRequestSystemMessage("You're an assistant who helps answer user questions. Decode the user's message. The user writes questions in Russian or Kazakh, answer in the language in which the user wrote. "));
        chatMessages.add(new ChatRequestUserMessage("Как у тебя дела?"));

Setup:
OS: macOS
IDE: IntelliJ
Library/Libraries: azure-ai-openai:1.0.0-beta.9
Java version: 17
App Server/Environment: Tomcat
Frameworks: Spring Boot 3.2.0
If you suspect a dependency version mismatch (e.g. you see NoClassDefFoundError, NoSuchMethodError or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:

verbose dependency tree (mvn dependency:tree -Dverbose)
exception message, full stack trace, and any available logs

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x]  Bug Description Added
[x]  Repro Steps Added
[x]  Setup information Added

@BorangaziyevA Can you upgrade the version to beta.10 and try out?
We have a fix for this issue.


Cannot delete a user token

Description
Deleting a user token with a different one (an admin account for examples), may end up in failure (404 in my case).
Gitea Version
1.21.0
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
linux
How are you running Gitea?
Self-hosted, dockerized.
Database
PostgreSQL

Duplicate of  #27598
Please backport ae419fa49403537725c806a5f3f1e5b274f52eb7 to the 1.21 branch

Closed as the backport #28099 is merged


Fix tooltip position, allow to set max and startDate

Really like this library, but encountered 1 bug and missed two features, so I tried to fix that. 😊
Summary of changes:

Bugfix: fix position of tooltip (now captured in position:relative container)
Style choice: Use inherit font color (defaults to black)
Cleanup: Remove border css for day-cells (no effect)
Feature: Allow user-set max value (not required)
Feature: Allow user-set start date (not required)

The latter two features are also described in the README. Hope this is useful!

Thanks Peter - some great additions here. I'll merge it now


Correct two issues found when testing CMake 3.27 rc2

Description
Corrects two small logic errors that became exposed due to changes in ExternalProject in CMake 3.27 which made it less robust to invalid inputs.
The rapids_cpm_thrust function now properly supports the DOWNLOAD_ONLY parameter, and rapids_cpm_rmm now propagates arguments correctly to the underlying CPMFindPackage.
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The cmake-format.json is up to date with these changes.

/merge


about training 4M dataset and the loss converge slowly

I collected the 4M datasets with some imgs urls failed (about 1.5%) , which causes 146 tags missing. I regenerate the label embedding, ram_tag_list_en(cn)/threshold according to the missing tags (get 4439 tags in total) and retrain the model. however, the loss converge slowly and the loss_tag/align/diss increase rapidly in some iterations during the first epoch. During the training process, the loss_tag and loss-align are oscillating, but overall they are decreasing. What's more, i found that the loss_diss drop to about 0.28 at the first epoch and almost stop decreasing even the training finished.
I only adjust the hyper-parameter batch_size from 52 to 26 as the reason of OOM(40g A100), while it should not be the key-point causing my problem. I evaluate on Openimages v6 common with my training ckpt and find the results is bad. Can you please offer some suggestions about my question or release the training log or the 4M ckpt for reference. Thank you very much!
pic of  loss increase rapidly and loss-align is oscillating

pic of average loss at epoch 5

pic of evaluation on Openimages v6 common with my training ckpt

I check the provided 4M data json files and find that only 4441 tags exists, which is smaller than the 4585 tags as claimed in the paper. May be the other 144 tags are in the 12M dataset? Will the missing labels cause bad effects on the training of 4M dataset training? As mentioned above, i relabel the json file and the model can't perform well.
I would be truly grateful if the author could offer any insights or responses to the questions I've presented.

I also raise two more questions. In Appendix A in paper, batch_size is 720. However, the batch_size in config file "pretrain" is set to 52. According to the paper, the model is trained by 8 A100, so the batch_size should be 52X8=416? Also, the loss is computed as the sum of (loss_tag+loss_diss+loss_align). However, i observe the magnitudes of the three losses are in the hundreds, tens, and less than one, respectively. I'm curious if simply adding losses with such significant differences in magnitude without balancing them with any weights will affect the training? Sincerely awaiting for your reply.

Did you load the ImageNet-pretrained image encoder weights? It is fixed by subsequent PR.


Java reflection tutorial project

Hi @egimaben This branch has conflicts on it. I cannot merge until they are resolved. Please would you please resolve. Cheers Alex.


How do I write config json files for other pretrained VITS models?

As title, I'm trying to make a Japanese model work with piper by modifying json file for supported model(en_US-lessac-medium.onnx.json), but I keep getting the errors such as Unknown phoneme table: '' or Invalid phoneme code XX where XX is some number in phoneme_id_map
PS. Here's the json for the model that I'm using if that matters

Hi @dic1911 ,
VITS configs don't work in piper, and it uses a different phonemizer and unicode conversion method, so it's best to train your datasets from scratch. Running piper_train.preprocess creates the configuration file.

@rmcpantoja Okay, thanks for replying

@dic1911 Hi did you get it working in Japanese?


[Feat]:Adding AOS,js scrolling animation to the website

Description
Adding AOS,js scrolling animation to the website
Screenshots

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[ ] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[ ] I am willing to work on this issue (optional)

@RamakrushnaBiswal share demo screen record of your changes

I would like to work on this feature. Could you assign this to me.

Sorry @gnjayasekara, please don't be discouraged, but this issue is already assigned to someone. Only one person can work on a single issue at a time. You can raise another issue, and I will be happy to assign it to you, but make sure that the issue you raise is valid and really needs to be addressed on our website; otherwise, invalid issues will be closed. Thank you!


Node-Webkit manifest format support

Hi, guys.
I use electron & node-webkit to create desktop apps.

Node-webkit has more clear and powerful manifest format than electron.
Electron might to have same (and more scalable) manifest format as in node-webkit.
Electorn might be compatible with nw.js manifest format.

In nw.js format we can declare window and window properties in package.json. It's very usable and i would like that the Electron also can create window without launcher *.js file provided.
We could provide ".js" and ".html" file with the main decaration. And get node-main property for js launcher also.
For example:
{
"main": "index.html",   // when specified HTML we SHOULD create new BrowserWindow
"window": {
// Here is window PROPERTIES to create browserWindow.
},
"node-main": "index.js" // javascript application launcher (starts after "main").
}
Now this my feature request to listen your opinion. I would like to help to create this functionality.

I'm not sure why someone would want to do that, but you should create a node.js module that will parse nw.js manifests and run them, I don't think this needs to be built into Electron (and tbh I question its utility)

We may support using html file for main field, since it is useful for simple apps and is very easy to implement, but supporting full node-webkit manifesto format is impossible because the underlying architecture is completely different.

We may support using html file for main field

I think this will be enough


Fix broken links

Hey, I thought it would be nice to have these links fixed.

@1inuxoid this project was moved from GS Collections to Eclipse Collections
The training material is hosted under Eclipse Collections Kata
Website of the project: https://www.eclipse.org/collections/
Please switch to use Eclipse Collections!


New linter: SublimeLinter-contrib-slim-lint

https://github.com/elstgav/SublimeLinter-slim-lint
This linter provides an interface to slim-lint

Please fix the 3rd install instruction in the README and make your first release. Thanks!

Done

Nice work, looking forward to this one.
@skj3gg could you please add it?

@Zyphrax Until it has been added to the Package Control registry, you can install it just like any other custom Sublime Text plugin. Clone the repository in your Packages directory.

@jawshooah Thanks! I knew that installation method for regular Sublime packages, but I didn't know that it would work for Sublime Linters :)
@elstgav Thanks for creating the linter, works great!

Forgot to update this, this has been pushed. Thanks!
https://github.com/SublimeLinter/package_control_channel/commit/ea09bf76e9436f815c3b08d3d5b6cba90e86a560


#9 add linting

Pull request questions
Which issue does this address
Issue number: #9
Why was change needed and what does change improve

maintain consistency in documentation and code while making communication and collaboration across the company a more productive experience
prevent broken code from being uploaded to main branches
help establish coding best practices across multiple languages
build guidelines for code layout and format
automate the process to help streamline code reviews

#9


Add Kubernetes

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md

I am:

[ ] Suggesting edits to an existing Topic page
[x] Curating a new Topic page

CURATING A NEW TOPIC PAGE

[x] I've formatted my changes as a new folder directory, named for the topic as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME])
[x] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please explain why you think this Topic page should be curated:
Because Kubernetes is on fire and github.com/topics/kubernetes needed some 💚

Thanks @adamstac 👋. Two minor changes: https://travis-ci.org/github/explore/builds/315186342#L541-L545

Thanks for your first contribution to github/explore, @adamstac!  You rock!


problem when opening a gallery with fiv-gallery created dynamicly by *ngFor

when one of the pictures is opened, the correct one is shown first, but after a couple of seconds it changes to the first one
Video
  private info: IPostFull;
  public episode: string[];
  private spiner: any;

  public stats: {
    readed: string[],
    inprogress: string[]
    last: string
  };

Page template
<ion-content fullpage>

  <fiv-gallery>
    <fiv-gallery-toolbar [position]="'top'">
      <fiv-gallery-toolbar-content></fiv-gallery-toolbar-content>
    </fiv-gallery-toolbar>
    <ion-grid fixed no-padding>
      <ion-row class="large">
        <ion-col size="4" *ngFor="let img of episode">
          <fiv-gallery-image [src]="img"></fiv-gallery-image>
        </ion-col>
      </ion-row>
    </ion-grid>

    <fiv-gallery-toolbar [position]="'bottom'">
      <ion-toolbar color="transparent">
        <ion-text>
          {{ info?.name }}<br>
          Глава: {{ stats?.last }}
        </ion-text>

      </ion-toolbar>
    </fiv-gallery-toolbar>

  </fiv-gallery>

</ion-content>

Hey @deissh
I updated the Image Gallery Demo Page with some galleries using *ngFor. I don't seem to have the problem you show in the video but I would like to find out what's causing the bug on your side. Could you please share a minimal repro of the bug?
Cheers
Gary

@garygrossgarten
html:
https://github.com/deissh/anibe.app/blob/84ec7f8e442a386e159a2f42314cdef00e722287/src/app/pages/reader/reader.page.html
ts:
https://github.com/deissh/anibe.app/blob/84ec7f8e442a386e159a2f42314cdef00e722287/src/app/pages/reader/reader.page.ts

Please provide a small repository with a reproduction of the bug. I forked your project but I don't seem to be able to work with it.

ok, there will be time on weekends and I will make a repository

I found that the problem occurs only when the list with pictures is created after the template is drawn, that is, after the page has loaded, it receives carinks via the http request and only then they are written to a variable, for example imgs

I'll see what i can do about it ;)

you can just add .update commant to reload all component and his childrens.


Sidebar form "Reset" isn't reflected in rendered content

Clicking "Reset" while editing content doesn't reset the rendered content's state.

@logan-anderson I'm not sure where you ended up with this but putting it in progress FYI


The data is ascii

Just thought i wanted to mention that the data you send is pure ascii data.
"1234Luft-Aus" to turn of fan
"1234Luft-1-" to set to speed 1.
Couldn't see that you mentioned that anywhere in your code. Have started playing around with a real home assistant integration. Will see if i finish it :)

You can follow along here if you are curious: https://github.com/home-assistant/core/compare/dev...elupus:fjaraskupan?expand=1


[SourceKit] Merge local rename and related identifiers

The related identifiers request was sufficiently similar to local rename that we can implement it in terms of local rename.

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please SourceKit stress test

While looking at open issues regarding related idents and local rename, we found that there are still a few issues here, one of them is that NameMatcher currently assumes that it’s iterating in source order while in-fact it isn’t because it’s an ASTVisitor. This causes us to skip references that have a postfix operator after them.
The proper solution here is to write NameMatcher in terms of SwiftSyntax but since ResolvedLoc contains a vector of CharSourceRange, writing a C bridging layer is a pain. So, we decided to punt this until we enable C++ interop inside the compiler.
The next steps to do then are:

Rewrite NameMatcher in SwiftSyntax
Ensure that the following issues are fixed

rdar://108267794
rdar://101556709
rdar://84061868

Delete the local rename refactoring action. Renaming should always go through the sourcekitd requests
When we remove the rename refactoring, I think we also don’t need OldName and NewName in RenameLoc anymore, which means that we can also remove the StringScratchSpace in RenameLocs and replace RenameLocs by std::vector<RenameLoc>.

Superseded by https://github.com/apple/swift/pull/70008


On-chain balance not showing new confirmed tx

On-chain balance has not updated after my confirmed on-chain tx to Mutiny. Trying to add more funds to my Mutiny lightning balance. Tx has >10 confirmations, and I closed and relaunched Mutiny.

It's weird that it shows up in the transaction list but not in the balance, esp if it is confirmed. In the "admin tools" section of the settings, there's a "resync wallet" button. Maybe try that, restart, and then wait a few minutes to see if balance becomes accurate?
Otherwise, some logs would help.

The resync solved my issue. Here's the logs from after the resync in case you're interested.
mutiny-logs (7).txt


"Post deleted" on posts which aren't

As reported by Rob:
https://chat.stackexchange.com/transcript/11540?m=48812470#48812470
Sent with GitHawk

The 2nd discussion that lead to the creation of this report has this reply from me, explaining the problem further:

tripleee That's OK. If we can accumulate a few examples we can post them there. It's a problem because you think that the post is deleted, so there's no purpose clicking the link unless you are 10K (2K on some sites), but the post is there and never has been deleted; we are simply offering extraneous false information. Thanks for the brief bug report, it's sufficient.

This is in fact a duplicate of Charcoal-SE/SmokeDetector#2172

@iBug I agree. After checking with @Tripleee could we move these comments there, or post a comment there referencing this bug report, as this contains more info than @Glorfindel83 wrote.

fixed, will not backport.


ESP32C3 (Devkit-M1) crash after triggering door sensors

Everything is functional testing a light service.
I've tried with both the garagedooropener and door services.  4-5 seconds after pressing "open" the micro crashes with the following (please ignore the windowshade; I was testing that to see if it could be used instead for my purpose):
Build:Feb  7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0xc (SPI_FAST_FLASH_BOOT)
Saved PC:0x403d0f8a
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x484
load:0x403ce000,len:0x90c
load:0x403d0000,len:0x2398
SHA-256 comparison failed:
Calculated: e0c357829f601add6a50d6ea19f89687ec5acf531610506a38b33d09b4a71c7e
Expected: 77332826ec7bc491df854452f675071e3a094e80858dd7d91dd7e27940204216
Attempting to boot anyway...
entry 0x403ce000
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x1 (POWERON),boot:0x4 (DOWNLOAD(USB/UART0/1))
waiting for download

Welcome to HomeSpan!
Apple HomeKit for the Espressif ESP-32 WROOM and Arduino IDE

** Please ensure serial monitor is set to transmit
Message Logs:     Level 0
Status LED:       Pin -  *** WARNING: Status LED Pin is UNDEFINED
Device Control:   Pin -  *** WARNING: Device Control Pin is UNDEFINED
Sketch Version:   n/a
HomeSpan Version: 1.4.1
Arduino-ESP Ver.: 2.0.1
ESP-IDF Version:  4.4.0
ESP32 Chip:       ESP32-C3 Rev 3 single-core 4MB Flash
ESP32 Board:      esp32c3
PWM Resources:    6 channels, 4 timers, max 14-bit duty resolution
Sodium Version:   1.0.12-idf  Lib 9.4
MbedTLS Version:  mbed TLS 2.16.11
Sketch Compiled:  Nov 21 2021 17:17:06
Device Name:      HomeSpan Bridge
Configuring Garage Door Opener
Configuring Motorized Window Shade
*** HomeSpan Info ***
➤ Accessory:  AID=1
➟ Service AccessoryInformation:  IID=1, UUID="3E"
⇨ Characteristic Name("Bridge #1"):  IID=2, UUID="23"
⇨ Characteristic Manufacturer("HomeSpan"):  IID=3, UUID="20"
⇨ Characteristic SerialNumber("123-ABC"):  IID=4, UUID="30"
⇨ Characteristic Model("HS Bridge"):  IID=5, UUID="21"
⇨ Characteristic FirmwareRevision("0.9"):  IID=6, UUID="52"
⇨ Characteristic Identify(0):  IID=7, UUID="14"
➟ Service HAPProtocolInformation:  IID=8, UUID="A2"
⇨ Characteristic Version("1.1.0"):  IID=9, UUID="37"
➤ Accessory:  AID=2
➟ Service AccessoryInformation:  IID=1, UUID="3E"
⇨ Characteristic Name("Garage Door"):  IID=2, UUID="23"
⇨ Characteristic Manufacturer("HomeSpan"):  IID=3, UUID="20"
⇨ Characteristic SerialNumber("123-ABC"):  IID=4, UUID="30"
⇨ Characteristic Model("Door"):  IID=5, UUID="21"
⇨ Characteristic FirmwareRevision("0.9"):  IID=6, UUID="52"
⇨ Characteristic Identify(0):  IID=7, UUID="14"
➟ Service GarageDoorOpener:  IID=8, UUID="41"
⇨ Characteristic CurrentDoorState(1):  IID=9, UUID="E", Range=[0,4]
⇨ Characteristic TargetDoorState(1):  IID=10, UUID="32", Range=[0,1]
⇨ Characteristic ObstructionDetected(0):  IID=11, UUID="24"
➤ Accessory:  AID=3
➟ Service AccessoryInformation:  IID=1, UUID="3E"
⇨ Characteristic Name("Window Shade"):  IID=2, UUID="23"
⇨ Characteristic Manufacturer("HomeSpan"):  IID=3, UUID="20"
⇨ Characteristic SerialNumber("123-ABC"):  IID=4, UUID="30"
⇨ Characteristic Model("Shade"):  IID=5, UUID="21"
⇨ Characteristic FirmwareRevision("0.9"):  IID=6, UUID="52"
⇨ Characteristic Identify(0):  IID=7, UUID="14"
➟ Service WindowCovering:  IID=8, UUID="8C"
⇨ Characteristic CurrentPosition(0):  IID=9, UUID="6D", Range=[0,100]
⇨ Characteristic TargetPosition(0):  IID=10, UUID="7C", Range=[0,100]
⬌ Set Range for TargetPosition with AID=3, IID=10: Min=0, Max=100, Step=10
✘ Characteristic PositionState *** WARNING!  Required Characteristic for this Service not found. ***
Range Check: No Warnings
*** CAUTION: There is 1 WARNING associated with this configuration that may lead to the device becoming non-responsive, or operating in an unexpected manner. ***
Configured as Bridge: YES
Service                         UUID         AID  IID  Update  Loop  Button  Linked Services

AccessoryInformation              3E           1    1     YES    NO      NO  -
HAPProtocolInformation            A2           1    8      NO    NO      NO  -
AccessoryInformation              3E           2    1     YES    NO      NO  -
GarageDoorOpener                  41           2    8     YES   YES      NO  -
AccessoryInformation              3E           3    1     YES    NO      NO  -
WindowCovering                    8C           3    8     YES   YES      NO  -
*** End Info ***
Accessory ID:      DE:4D:C6:6D:9E:65                               LTPK: F2A9F1AB111BCD96F9D8718382A3A2B1C3C6FBCD5B7238E13C5C4D28E3678535
Paired Controller: C553F9AF-164F-49AC-9C39-620A5B5D5EBA   (admin)  LTPK: 88BBA7418460055EBA5E930AA20FD7A4570D68E35D48BDA613088A44D196F584
Accessory configuration has changed.  Updating configuration number to 13
HomeSpan Bridge is READY!
Successfully connected to SSID! IP Address: <IP_ADDRESS>
Starting MDNS...
HostName:      HomeSpan-DE4DC66D9E65.local:80
Display Name:  HomeSpan Bridge
Model Name:    HomeSpan-ESP32
Setup ID:      ASDF
Starting Web (HTTP) Server supporting up to 8 simultaneous connections...
Guru Meditation Error: Core  0 panic'ed (Load access fault). Exception was unhandled.

I'm not sure I'm following from the above.  As an initial test, can you first check that an example sketch (one of the tutorials) works as expected.  If it does, then that suggests something in your specific code - please provide a link to, or copy of, the code and I can try to debug.  It also may be something related to version 2.0.1 of the board manager - I have not yet tried the latest build from Espressif.

Apologies, this was done using and adapting a demo file.  Please see attached -- .ino renamed to .txt
DualGarageOpener.txt

Are you running under 2.0.0 or 2.0.1?

I'm running 2.01, but if 2.0 supports the C3 chip, I'll gladly downgrade.

Since HS won't compile under 2.0.1 without a patch for the Blinker class, if you are running under 2.0.1 did you use your patch?  If so, that might be the problem - as noted in the separate issue you posted, I need to review the Blinker class given the changes between 2.0.0 and 2.0.1.

Yes, please use 2.0.0 for now until I can address the 2.0.1 issue.

Much appreciated!

Okay, I can confirm the crash still occurs under 2.0.0 using the example file I uploaded (basically no I/O)

I have been able to reproduce this issue.  The code works fine on an ESP32 but seems to be failing on an ESP32-C3.  Will debug.

I have identified the problem and fixed a long-standing latent bug in how TimeWrite processes work (these are used only for certain Services related to open/closing of doors and locks).  Frankly, I'm not sure why this issue never surfaced on the ESP32 and only affects the ESP32-C3.  Must have something to with the slight variations in compiler logic.
In any case, the issue is fixed and I will release in a small patch this weekend.  In the interim, you can download the dev branch, which contains the fix (as well as a few other additions that will be part of 1.4.2).   Will also try to fix the compilation issue that arises when using Arudino-ESP32 version 2.0.1.
Thanks for catching this issue and providing the example!

Wow, huge thanks.  I'm admittedly very rusty in programming, but where/when I can contribute, I will!


Sidebar selection before ready

Feature Request
Desired behaviour
Currently the sidebar expansion panels are shown and can be interacted with immediately.  Afterwards, there is panel expansion logic that is executed afterwards.  Between these two, a user can potentially expand a different panel and then have their action overridden by the panel expansion logic.  Ideally, this should not happen
Possible solutions:

Make the sidebar not interact-able until the panel expansion logic has been executed.
Do the panel expansion logic first before showing the sidebar.

┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.7
┆Issue Number: DOCK-423

Check if still a thing, otherwise punt

Not sure why, but it's less of an issue now.  Still possible I think but doesn't seem humanly possible to do so

Ok, closed


V5X Test pass PR

This won't be active so DO NOT MERGE

Hey Cruncher, what's up? It's github, a public repo -- you can remove
yourself. Try the "unwatch" button on this page
https://github.com/safarijv/ifpress-solr-plugin/pull/3
On Tue, Nov 21, 2017 at 3:00 PM, Derek James<EMAIL_ADDRESS>wrote:

Please remove my access from this repo, I am an ex O'Reilly/Pubfactory
employee and do not want these notifications.
On Tue, Nov 21, 2017 at 2:39 PM, Robert Ivey<EMAIL_ADDRESS>wrote:

This won't be active so DO NOT MERGE
You can view, comment on, or merge this pull request online at:
https://github.com/safarijv/ifpress-solr-plugin/pull/3
Commit Summary

SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
catching up
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
schema modification
SPIDR-94
SPIDR-94
SPIDR-94
comment fix
SPIDR-94
SPIDR-94
SPIDR-94
SPIDR-94
build on commit and MultiSuggestTest additions
SPIDR-122
troubleshooting the assertSuggestions routine
SPIDR-122
SPIDR-122
SPIDR-122
SPIDR-122
SPIDR-122
compose the iterator object
disable the Merge Fields since the upgrade isn't

File Changes

M pom.xml
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-0
(2)
M solr/collection1/conf/solrconfig.xml
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-1
(2)
M solr/heron/conf/schema.xml
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-2
(2)
M solr/heron/conf/solrconfig.xml
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-3
(1)
M src/main/java/com/ifactory/press/db/solr/HitCount.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-4
(25)
M src/main/java/com/ifactory/press/db/solr/processor/
FieldMergingProcessor.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-5
(14)
M src/main/java/com/ifactory/press/db/solr/processor/
MultiSuggesterProcessor.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-6
(2)
M src/main/java/com/ifactory/press/db/solr/processor/
UpdateDocValuesProcessor.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-7
(5)
M src/main/java/com/ifactory/press/db/solr/search/
SafariBlockJoinQuery.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-8
(172)
A src/main/java/com/ifactory/press/db/solr/search/
SafariDocIdSetIterator.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-9
(130)
M src/main/java/com/ifactory/press/db/solr/search/
ScoringParentQParser.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-10
(8)
M src/main/java/com/ifactory/press/db/solr/spelling/
suggest/MultiDictionary.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-11
(4)
M src/main/java/com/ifactory/press/db/solr/spelling/
suggest/MultiSuggester.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-12
(10)
M src/main/java/com/ifactory/press/db/solr/spelling/
suggest/SafariInfixSuggester.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-13
(8)
M src/main/java/com/ifactory/press/db/solr/spelling/suggest/
SafeInfixLookupFactory.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-14
(2)
M src/test/java/com/ifactory/press/db/solr/HeronSolrTest.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-15
(4)
M src/test/java/com/ifactory/press/db/solr/SolrTest.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-16
(4)
M src/test/java/com/ifactory/press/db/solr/highlight/
PostingsHighlighterTest.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-17
(23)
M src/test/java/com/ifactory/press/db/solr/highlight/
SolrPostingsHighlighterTest.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-18
(13)
M src/test/java/com/ifactory/press/db/solr/processor/
FieldMergingProcessorTest.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-19
(20)
M src/test/java/com/ifactory/press/db/solr/processor/
UpdateDocValuesTest.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-20
(17)
M src/test/java/com/ifactory/press/db/solr/search/
SafariBlockJointest.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-21
(8)
M src/test/java/com/ifactory/press/db/solr/search/
SafariQueryParserTest.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-22
(2)
M src/test/java/com/ifactory/press/db/solr/spelling/
suggest/MultiSuggesterTest.java
https://github.com/safarijv/ifpress-solr-plugin/pull/3/files#diff-23
(110)

Patch Links:

https://github.com/safarijv/ifpress-solr-plugin/pull/3.patch
https://github.com/safarijv/ifpress-solr-plugin/pull/3.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/safarijv/ifpress-solr-plugin/pull/3, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/
AFso6BW0RX50hVhYuSeeSS6LTUmfwZmxks5s4yb7gaJpZM4QmYVF>
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/safarijv/ifpress-solr-plugin/pull/3#issuecomment-346143865,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA56QRz4Z6P8bQNdaC0-SKATgjAfomPYks5s4yvsgaJpZM4QmYVF
.

If this is what I think it is, this is super exciting. :D

I have no idea what it is but I'm excited

Heheh @abrookins and @msokolov nice to see you folks still lurkin around :)


refactor: generic NetworkInfoProvider.ledgerTip

Context
Implementing new providers for SingleAddressWallet requires resolving all fields defined in core package. This is not always possible.
Proposed Solution
This PR demonstrates a generic parameter-based approach for more flexible types. It only implements the approach for NetworkInfoProvider.ledgerTip as a means to evaluate the approach. A full refactor would introduce a lot more changes, adding many more generic parameters to ObservableWalllet and SingleAddressWallet. See this test for usage example.
Relevant commits: 0632420abca4e9cd680bed26df37124dbd2a72b9 2e254cf7b1e4e8742e7849740f6d913215d41b64
Other Changes Introduced

chore(wallet): convert types.ts into directory module with index 485728f8e6d60c2b1a8b863ddeeb771f0d1ac83e

Closing in favor of #319


feat: Math captcha

Implement an option for math captcha and generate math captcha accordingly.
Example:

Captcha :  4 + 8 , Valid : 12
Captcha :  9 - 3 , Valid : 6
and many more.

NOTE : Implement an option to choose between text and math captcha.
Text captcha is already been there.

Hello!
I would like to work on it.


Map AdviserStatusId from Candidate

We were not mapping the AdviserStatusId to the request model from the Candidate, so when used to pre-fill the TTA sign up the field was missing and the behaviour was not correct on the subsequent form submission.

Github actions got stuck so I had to force-push the same commit; no changes since last approval so just going to merge down.


Methods for qubit name to index and back

Makes IQMBackend more user friendly
adds some important tests

Can you add a section in the docs about how the qubit mapping / routing works? I mean from user-made circuits with arbitrary qregs, to routed circuits, to IQM qubit names.

Can you add a section in the docs about how the qubit mapping / routing works? I mean from user-made circuits with arbitrary qregs, to routed circuits, to IQM qubit names.

I don't think it deserves a section, since most of it is typical functionality of Qiskit, and our documentation is not intended for teaching Qiskit. But I can perhaps add a sentence or two about IQM-style qubit names in the user guide and/or the docstring of IQMBackend


Dimension field shows invalid-value

I using the latest version of Kirki, and trying to use the dimension field.
But when changing it's value, I get the invalid value warning.
The value I change to is: 41px
Using the following code:
 my_config_kirki_add_field(
     array(
         'type'        => 'dimension',
         'settings'    => 'widget_footer_padding',
         'label'       => esc_html__( 'Widget Footer padding', 'kirki' ),
         'section'     => 'footer_section',
         'default'     => '0px',
         'choices'     => [
             'accept_unitless' => false,
         ],
         'transport'   => 'auto',
         'output'      => [
             [
                 'element' => '#footer-widgets',
                 'property' => 'padding-top',
             ],
         ],
         'active_callback' => [
             [
                 'setting'  => 'footer_widgets_enabled',
                 'operator' => '==',
                 'value'    => '1',
             ]
         ],
     )
);

So what is wrong here?

Hello and thank you for reporting this issue.
We are closing most open GitHub issues with the release of Kirki 4 to start fresh with this major release.
If you are still running into issues after you have tested your theme with Kirki 4, please let us know so we can reopen the issue.
Please note that Kirki 3 is no longer actively supported. Moving forward, we will only provide support the very latest version of Kirki.
Thank you for your understanding.
Best,
David


Fixing issue 1857

I'm not sure if this is the entirety of the problem in #1857, but an obvious mistake was not actually using the nb_worker and nb_val_worker arguments, which this patch fixes.

Indeed. Please rebase and squash your commits.

I hope that worked, it turns out I was "rebasing" incorrectly.

No, it seems that unrelated commits from master are included with this PR. You could restart this from scratch...


Remove false annotation

I'd love to add annotations letting people know that this function and a few others take SyntheticEvents but that may be inconsistent with the rest of the docs. For now, this particular annotation should be removed

Thanks!
This is the code that renders this element in the docs. If you can come up with a way to annotate those it would be great :)
https://github.com/facebook/react-native/blob/master/website/layout/AutodocsLayout.js#L66


Apply install-deps.sh script changes from 0.2.x branch for enabling GNU/Debian support. Thanks @ssta.

…

@christianparpart
I know only enough about cmake to do
mkdir build ; cd build ; cmake .. ; make

When I did that today on Debian -- after running install-deps as root and then chown'ing the local packages back to my user because I'm not a sudo'er by default -- I get this:
-- [Version] Git branch: master
-- [Version] Git SHA: 21c4dab7
-- [Version] version source: git & /home/autumn/t/contour/Changelog.md
-- [Version] version triple: 0.3.0
-- [Version] version string: 0.3.0-unreleased-master-21c4dab7
-- [ccache] Disabled.
-- [clang-tidy] Disabled.
-- [FilesystemResolver]: Using standard C++ filesystem API
-- addr2line: /usr/bin/addr2line
-- No sanitizer enabled.
-- Embedding 3rdparty libraries ...
-- [ccache] Disabled.
-- [clang-tidy] Disabled.
-- Performing Test fdiagnostics-color=always
-- Performing Test fdiagnostics-color=always - Success
-- Adding compiler flag: -fdiagnostics-color=always.
-- Enabling pedantic compiler options: no
-- [ccache] Disabled.
-- [clang-tidy] Disabled.
-- Adding compiler flag: -fdiagnostics-color=always.
-- Enabling pedantic compiler options: no
-- [code coverage] Disabled.
-- ------------------------------------------------------------------------------
--     libunicode (version 0.0.1)
-- ------------------------------------------------------------------------------
-- Build type:                  RelWithDebInfo
-- Build unit tests:            OFF
-- Build tools:                 OFF
-- Using ccache:                CCACHE-NOTFOUND
-- Using UCD source:            OFF
-- Enable clang-tidy:           OFF ()
-- ------------------------------------------------------------------------------
CMake Error at cmake/ThirdParties.cmake:68 (find_package):
  By not providing "FindMicrosoft.GSL.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "Microsoft.GSL", but CMake did not find one.

  Could not find a package configuration file provided by "Microsoft.GSL"
  with any of the following names:

    Microsoft.GSLConfig.cmake
    microsoft.gsl-config.cmake

  Add the installation prefix of "Microsoft.GSL" to CMAKE_PREFIX_PATH or set
  "Microsoft.GSL_DIR" to a directory containing one of the above files.  If
  "Microsoft.GSL" provides a separate development package or SDK, be sure it
  has been installed.
Call Stack (most recent call first):
  CMakeLists.txt:81 (include)

-- Configuring incomplete, errors occurred!
See also "/home/autumn/t/contour/build/CMakeFiles/CMakeOutput.log".
See also "/home/autumn/t/contour/build/CMakeFiles/CMakeError.log".

Is there something else I should be doing here?

It's actually been a long time since I was able to compile contour from source.  And I'd like to, because it's a nice terminal, and I want to be able to test with it. :)

It's actually been a long time since I was able to compile contour from source.  And I'd like to, because it's a nice terminal, and I want to be able to test with it. :)

Hey. Oh that is nice to hear. Please give me some time to look into it, as we a certainly busy with important family duties for at least until tomorrow night.
If not someone else did chime in until then, I certainly will try to improve the setup procedure so that it also works for you.

What is your precise distro and version you are on?

Family first!  I'm not urgent at all.  :-)

Debian bullseye, currently version 11.1.  g++ 10.2.1, cmake 3.18.4.

I figured I wasn't using cmake correctly.


to_affine() should return a result instead of panicking when z is 0

to_affine() should return a result instead of panicking when z is 0

What should the Result contain?

can i be assigned to this ?

can i work on this??

I’d like to work on this.


Support golang1.17+ arguments

Is your feature request related to a problem? Please describe.

Golang-1.17 was released in 2021/08/17. It's calling conventions changed, and current bpftrace argN does't support the new calling conventions well. Since golang is a popular language, support go1.17+ will be really helpful. Do we need   some new arguments?
Here is the new calling convention in x86_64 platform, refered from Go internal ABI specification.

param
argN
go1.17+

1
rdi
rax

2
rsi
rbx

3
rdx
rcx

4
rcx
rdi

5
r8
rsi

6
r9
r8

7
stack
r9

8
stack
r10

9
stack
r11

10
stack
stack

Describe the solution you'd like

refered from: https://github.com/iovisor/bpftrace/issues/740, maybe some new aliases like:

goarg0==ctx->rax
goarg1==ctx->rbx
etc
will helps.

Describe alternative solutions or features you've considered

The other alternative solution is support ctx->rax, ctx->rbx like arg-rax, arg-rbx, and the new calling conventions can be supported.
Much thanks for your time.

Good idea.
And do you think provide direct register access parameters in bpftrace, like rax, rbx, r10, etc, as I mentions above, is acceptable?
Looking forward a proper solution.

I think adding language into the probe as a modifier would imply we have to detect the golang version, right? In practice I think this is possible (eg go version $binary) will report the version of go that $binary is compiled with. Mechanically you could refer to:

https://github.com/golang/go/blob/b441eb3f978b8b7d4f09f8e583d419d8f4e40af6/src/cmd/go/internal/version/version.go#L143-L162
https://github.com/golang/go/blob/master/src/debug/buildinfo/buildinfo.go#L177-L186

But do we think it's feasible to maintain a decoder / mapping forever? Perhaps another option like @liyan-ah suggested is to expose direct register access.

I don't think we have to. Golang used to be stackbased, now register based (https://go.dev/doc/go1.17#compiler). So users had to use sarg and now have to update programs to arg anyway. Detection would be a nice extra, can warn users that sarg isn't going to work anymore.
We can already access registers, reg("r15") should just work https://github.com/iovisor/bpftrace/blob/a2c23086a97cffc31fe2d78feeae211c9df6b155/man/adoc/bpftrace.adoc

Thanks for your reply. I would try to access register directly latter, and this do solve my problem.
Also, sarg is still very important, or if we have another methods to access memory directly, when it comes to stack passing argument, even in go-1.17+ as I mentioned above.
Do you think providing some guides for different languages' argument reading in some place (a readme file or a blog link) is a good idea ? That would help new learners.

I don't think we have to. Golang used to be stackbased, now register based (https://go.dev/doc/go1.17#compiler). So users had to use sarg and now have to update programs to arg anyway. Detection would be a nice extra, can warn users that sarg isn't going to work anymore.

Ah, ok. I thought they had changed the register based calling convention after the initial switch from stack -> register.

We can already access registers, reg("r15") should just work https://github.com/iovisor/bpftrace/blob/a2c23086a97cffc31fe2d78feeae211c9df6b155/man/adoc/bpftrace.adoc

Whoops, right. I forgot about that helper :)

Do you think providing some guides for different languages' argument reading in some place (a readme file or a blog link) is a good idea ? That would help new learners.

Yeah absolutely. A doc file in this repo would be nice. Possibly with tables like the one you provided in the issue.

goarg0==ctx->rax
goarg1==ctx->rbx

This is, unfortunately broken for arguments that occupy two registers such as strings. So ctx->rbx can point to the length of arg0, not the second function argument.

@myaut Right, it requires a bit of awareness from person doing the tracing. For example, you can pass aggregates in C as well: https://godbolt.org/z/67a4Yde5e


Unable to switch Icon and show icon

I follow the description. At the Environment Variables, I set the light_icons to both true and false, also tried both export and dont export. The icon won't show up. By the way, this workflow is great! Thank you guys!

Can you see if [v5.0.0]*https://github.com/kejadlen/pirate-weather.alfredworkflow/releases/tag/v5.0.0) works for you?

Sill not showing... Tried both enabled light icons and not enabled.

Ah, okay, I think I found the problem, try 5.0.1 please!

Yes! It works!! It looks so good now!
Just one small thing. Im not sure if it is intentional. When i pick Light theme, the icon is in black color. When i pick Dark theme, the icon is in white color.
Thank you so much! Such a great workflow!

Oh, that's a good point - I was thinking the OS/Alfred theme rather than the workflow theme. I might adjust it in a later release, we'll see.


Add Mender OTA Update Support

Thanks for creating and sharing the meta-tegra project!  Amazing work here!
These commits add capabilities related to support for mender, a project which adds OTA firmware update support.
Other required changes for mender support are found in the layer at meta-mender-tegra, however I can move any changes into this layer if requested.
I've only tested on the sumo branch thus far, and I only have a Jetson TX2 development board for testing.
I wanted to send the pull request to understand if/how you'd like these merged before I test on other branches and I could use volunteers who could test on other hardware.  I'm especially interested in feedback about:

The way the data partition change support is implemented.  I'd like to make this less platform specific and not require a specific .xml configuration file as is currently done with the flash_l4t_t186.custom.xml file.  Perhaps a patch to the xml file which could apply across platform.  I'm curious how much of this customization you want to support in meta-tegra and how much I should put in a different layer like the one I've created.  I've put minimal support in meta-tegra as-is.
Likely related to the questions above, any ideas to streamline the configuration detailed here.  I'm wondering if the KERNEL_ROOTSPEC default could be changed to reference ${distro_bootpart} here which would remove this step.  The u-boot environment offset calculation is a bit of a hack as well.

Thanks for considering and thanks again for sharing this project!

Other required changes for mender support are found in the layer at meta-mender-tegra, however I can move any changes into this layer if requested.

Based on the suggestion from Mirza Krak on the Mender dev team in mender hub, I'll move any changes you would like from meta-mender-tegra into meta-tegra on this PR and put the rest in meta-mender-community.

Thanks for this!
On the flash layout customization: I'd like to keep this layer as close to stock L4T as I can, so keeping a custom XML file in the other layer is probably best.  I don't think a patch would work across platforms, since the L4T XML files vary a bit from platform to platform.  NVIDIA also changes the layouts from version to version of L4T, which further complicates things.
The KERNEL_ROOTSPEC change you suggest sounds right - I'd be happy to take a PR for that, or I'll make the change myself when I get a chance.
I'm fine with taking the u-boot-fw-utils recipe addition.  I don't think you need to allocate a separate partition for the u-boot environment, though.  On both the TX1 and TX2, the NVIDIA u-boot places the environment at the end of the /dev/mmcblk0boot1 partition, and I already have the kernel patches in place to make that partition visible to Linux.  All you need is an /etc/fw_env.config file for use by u-boot-fw-utils:
/dev/mmcblk0boot1    0x3fe000   0x2000

I've used this on my custom TX1 and TX2 devices.  The only thing to watch out for is that on the TX2 (but not the TX1), the NVIDIA bootloaders also put a pseudo-GPT into boot1 that maps their layout of the boot partitions in boot0 and boot1. I only ran into problems with this when I enabled environment redundancy for my customized u-boot - the second environment area started overwriting that pseudo-GPT, bricking my TX2.
As for the other configuration customization... some of the customizations are machine-specific, some are distro-specific.  For the machine-specific ones, you could add a jetson-tx2-mender.conf machine config file to your mender-tegra layer that does a require conf/machine/jetson-tx2.conf and then does the other additions/modifications.  For the distro-related config changes, just create a .inc file and have people include that in either their local.conf or distro config file to have it apply.
Finally, for handling the flashing of the data partition, I'd recommend creating an image_types_mender-tegra.bbclass (or whatever) in your mender-tegra layer that inherits image_types_tegra.bbclass and then add a tegraflash_create_flash_config_append_tegra186 that does a sed -i to make your modifications.  Then use the reference the new bbclass in your IMAGE_CLASSES setting.
Thanks again!

Thank you very much for the comments and suggestions @madisongh, especially the notes about u-boot environment and mmcblk0boot1 partition which I didn't catch in my first implementation.  I'll work on updating the PR for u-boot-fw-utils and KERNEL_ROOTSPEC changes this week and move the rest into my layer and eventually meta-mender-community.

On the flash layout customization: I'd like to keep this layer as close to stock L4T as I can, so keeping a custom XML file in the other layer is probably best. I don't think a patch would work across platforms, since the L4T XML files vary a bit from platform to platform. NVIDIA also changes the layouts from version to version of L4T, which further complicates things

What do you think about using xmlstarlet or a similar XML command line tool to add relevant partition sections?  I worry keeping standalone files working with new platforms and L4T versions will be difficult to maintain.

What do you think about using xmlstarlet or a similar XML command line tool to add relevant partition sections? I worry keeping standalone files working with new platforms and L4T versions will be difficult to maintain.

Unfortunately, just about everything about L4T is difficult to maintain, since NVIDIA sometimes makes incompatible and seemingly gratuitous changes from release to release, making upgrades/downgrades a bit of a pain.
No matter which approach you take - modifying the XML on the fly, patching it, or just providing a customized copy - it will have to be reviewed with each L4T update to make sure it's still going to be compatible.  And NV's flashing tools are different between TX1 and TX2, and seem to interpret the specific XML sections differently, so I'm not sure you could do this generically across platforms. Looks like Xavier shares the same tools with the TX2, but the layouts and specifics of the XML used are different. (Also, the TK1 doesn't use XML at all.)

Thank you for the suggestions @madisongh.  I believe I've completed all requested changes and I've tested on the sumo branch with T2 dev board and my meta-mender-community changes, see this pull request for associated mender-community changes.
Let me know if you'd like me to do any other testing of this standalone without mender layers and with my TX2 development board, or if you want me to do a new PR for a different branch.

Turns out that the use of the ${distro_bootpart} variable in an extlinux.conf file doesn't actually work for the default case, because that variable is not actually in the environment - it's a local variable in U-Boot's "hush" shell, and the function that parses the APPEND line is the "simple" parser that only understands environment variables.
I have added a patch to our U-Boot sources so we can use it - if distro_bootpart is not set in the environment, but is present in the hush local variables, it will set it in the environment before parsing the APPEND line, then clear it afterwards.
It looks like you are setting distro_bootpart in the environment as part of your Mender integration, so this change shouldn't have any effect on how that works.
I have also added a suitable /etc/fw_env.config file for the TX1 and TX2, so fw_printenv and fw_setenv locate the environment correctly, and I had to work in an addition to the kernel command line for the TX1 so that the boot partitions would be accessible.
With these tweaks, I think we're good to go.  I've tested the changes on both TX1 and TX2 dev kits, and they look like they're doing the right things.

Merged manually, with the above-mentioned tweaks.

The NVIDIA bootloaders also put a pseudo-GPT into boot1 that maps their layout of the boot partitions in boot0 and boot1. I only ran into problems with this when I enabled environment redundancy for my customized u-boot - the second environment area started overwriting that pseudo-GPT, bricking my TX2.

I ran into this same issue over the weekend, and created a post [https://devtalk.nvidia.com/default/topic/1063652/jetson-tx2/mmcblk0boot1-usage-at-address-4177408-and-u-boot-parameter-storage-space-availability/](on the forum) to ask about this.


Introduce core.gardener.cloud/v1beta1.InternalSecrets API

How to categorize this issue?

/area dev-productivity usability
/kind enhancement
Motivation
End-users can read or write Secrets in their project namespaces in the garden cluster. This prevents Gardener components from storing certain "Gardener-internal" secrets related to the Shoot in the respective project namespace (since end-users would have access to them).
E.g., gardener can't store the client CA key needed for signing short-lived client certificates in the shoots/adminkubeconfig subresource in a project Secret. Instead, gardener-apiserver (mis)uses the ShootState for retrieving the client CA key.
Goals

introduce a store for shoot-related internal secrets
allow using the same machinery for secrets and internal secrets (e.g., owner references, secrets manager)
drop current workarounds for a missing internal secrets store
keep current end-user permissions in project namespaces

Proposal
Let's introduce a new API resource: core.gardener.cloud/v1beta1.InternalSecrets.
The resource is defined like the core/v1.Secrets resource, behaves exactly like it, and can be used in the same manners. The only difference is, that it is a dedicated resource exposed by gardener-apiserver.
This allows gardener to separate access to usual secrets and internal secrets by the usual RBAC means.
For this, we copy the respective Secret API types, validation, conversion, and registry code from k/k, and adapt the new InternalSecret naming everywhere.
Steps

[ ] Introduce core.gardener.cloud/v1beta1.InternalSecrets API
[ ] Make secretsmanager reusable for InternalSecrets
[ ] Sync client CA to InternalSecret in project namespace and use it from there in shoots/adminkubeconfig subresource

This proposal is an outcome of the gardener hackathon in May 2023: https://github.com/gardener-community/hackathon/blob/main/2023-05_Leverkusen/README.md#-introducing-internalsecret-resource-in-gardener-api
Tests, documentation, and a bit of cleanup is missing for making the implementation ready for opening PRs.
Moving forward, I will take care of this topic.
/assign

All tasks have been completed.
/close


UI fix - update the job title field on the profile page

Job Title can be confusing for recruiters. We need to update it something less confusing.

#199 fixes this.


Could I see a complete example?

Hi!
Could I ask you to create a complete integration example? Like on codepan or similar? Or even in a repo itself?
Thanks!

Hello
Sorry, we won't provide support on this lib as it's for internal use. It's pretty straighforward to use though, it's designed to be used with @codingame/monaco-editor-react, you can have a look at it as well

Ok, thanks, I will check @codingame/monaco-editor-react too.
One more question, please. Have you tried adding successfully using this lib (or @codingame/monaco-editor-react) along with monaco-graphql ? I just try to understand if they can work together at all?
Or any other way to add support for graphql language?

I don't see why it would prevent it to work, did you try and have an error ?
If it does work, the alternative is to use the vscode graphql extension but it would requires to include it in this lib


Some ideas for GTA SA

First: probably everyone knows that if you zoom the map in the menu, half a lifetime will pass before the map zooms to the required size. I think it's a bug, but who knows
Second: if possible, add support for palette texture formats. A very useful thing when the quality breaks in DXT, and in BGRA it weighs too much. (interesting point - the "txd" folder easily reads textures in the pal format)
Third: support for mipmaps for player.img (if possible)

if you zoom the map in the menu, half a lifetime will pass before the map zooms to the required size

I think this works okay at 30 FPS and so it's probably a FPS bug (which is more in scope of FramerateVigilante)

My laptop is pretty weak, I have a good menu if 30 FPS, maybe less. As I understand it, it also does not depend on the screen resolution, which is long in Full HD, which is long in 640x480

You almost certainly have more than 30FPS in the map menu. Zoom works fine at an intended framerate, so it is highly likely that.


Question: where are Exceptions gone in extra threads?

I need to call an API in one of my scripts. The documentation discusses this and suggests task.executor(). It does not seem to manage exceptions, though.
Consider the code below, which does not use threading and works correctly (but this is not the right thing to do for I/O tasks):
class MyEx(Exception):
    pass

def raise_ex():
    log.info("in raise function")
    try:
        raise MyEx()
    except MyEx:
        log.warning("caught MyEx")

def raise_ex2():
    raise MyEx()

@service
def testing_raise(**data):
    raise_ex()
    raise_ex2()

Calling the service pyscript.testing_raise gives
2020-12-04 16:17:25 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling raise_ex(, {})
2020-12-04 16:17:25 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling info("in raise function", {})
2020-12-04 16:17:25 INFO (MainThread) [custom_components.pyscript.file.dash__meteo.testing_raise] in raise function
2020-12-04 16:17:25 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling MyEx(, {})
2020-12-04 16:17:25 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling warning("caught MyEx", {})
2020-12-04 16:17:25 WARNING (MainThread) [custom_components.pyscript.file.dash__meteo.testing_raise] caught MyEx
2020-12-04 16:17:25 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling raise_ex2(, {})
2020-12-04 16:17:25 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling MyEx(, {})
2020-12-04 16:17:25 ERROR (MainThread) [custom_components.pyscript.file.dash__meteo.testing_raise] Exception in <file.dash__meteo.testing_raise> line 39:
        raise MyEx()
              ^
MyEx:

This is fone, the exception is caught once and then thrown out.
Now the version with task.executor and standard threading:
class MyEx(Exception):
    pass

def raise_ex():
    log.info("in raise function")
    try:
        raise MyEx()
    except MyEx:
        log.warning("caught MyEx")

def raise_ex2():
    raise MyEx()

@service
def testing_raise(**data):
    task.executor(raise_ex)
    task.executor(raise_ex2)
    threading.Thread(target=raise_ex).start()
    threading.Thread(target=raise_ex2).start()

It outputs:
2020-12-04 16:25:21 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling executor(<custom_components.pyscript.eval.EvalFuncVarAstCtx object at 0x7fe8ec485c10>, {})
2020-12-04 16:25:21 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling executor(<custom_components.pyscript.eval.EvalFuncVarAstCtx object at 0x7fe8ec485d90>, {})
2020-12-04 16:25:21 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling Thread(, {'target': <custom_components.pyscript.eval.EvalFuncVarAstCtx object at 0x7fe8ec4855e0>})
2020-12-04 16:25:21 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling start(, {})
2020-12-04 16:25:21 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling Thread(, {'target': <custom_components.pyscript.eval.EvalFuncVarAstCtx object at 0x7fe8ec485af0>})
2020-12-04 16:25:21 DEBUG (MainThread) [custom_components.pyscript.eval] file.dash__meteo.testing_raise: calling start(, {})

Nothing about the exceptions (caught or not).
This is a bit problematic with calls such as requests (that are in the documentation) because it is not known whether they succeed or not.

You've run into some of the less used pieces of pyscript. So, congrats. :)
If you look at what is being returned by task.executor you'll see that it is a coroutine. This is the root of the problem. The exception is never raised because the method you expect to have run (raise_ex) is never actually run.
In pyscript, even though def raise_ex(): doesn't look like you're making a coroutine (async function) you actually are, through a few hoops. Every method you define ends up being a "class" internally to pyscript. And this particular class is callable and, when called, returns a coroutine. So, task.executor "calls" that class, gets the returned coroutine, and returns it to you, but never runs it.
The short solution to all of this is, if you need to run functions in the executor, then those functions have to exist WITHOUT all the features pyscript brings. They have to be pure python with no access to log., state., service.call, etc. It's almost as though it's not even connected to Home Assistant. And, to write such functions, you have to take a few extra steps.
They are outline in the docs. You can jump down to the paragraph that starts with "So if you plan to run large chunks of code in pyscript".
If you would like to use pyscript functionality (like service.call, for instance) and do I/O and use the task.executor() then you need to break the job up into pieces that don't do I/O and use pyscript, and pieces that do I/O and don't use pyscript.
In most cases, the easiest solution is to do what you want to do with an async capable library or code. But, if that isn't possible, these are the tools available.
Pyscript does this to make it EASIER on the end user. But, when doing more advanced things, ultimately, it makes it little be harder. It makes it easier by not requiring the end user to know what async is, or when to await, or any of that business when writing MOST automations. But, in your case, you need specific control over async, and await, and all of that in order to properly hand data from the async event loop, into the executor, and back again.

Speaking specifically to using requests, the docs mention this as the "better" method (in a "bad", "better", "best") scale:
import requests

url = "https://raw.githubusercontent.com/custom-components/pyscript/master/README.md"
resp = task.executor(requests.get, url)

This works fine because requests.get is provided by a separate module. Because that module exists OUTSIDE of pyscript, it's a real module with real functions instead of having the "everything gets turned into a class" treatment that a method you write inside of pyscript gets.
An example of where this can get you is like this. The below code is wrong:
import requests

def does_google_say_google():
  res =requests.get('http://google.com')
  if "google" in res.text:
    return True
  return False

@time_trigger('startup')
def dothething():
  result = task.executor(does_google_say_google)
  if result:
    log.info('google says google')

The reason this doesn't work is because of where the "task.executor" is issued. Use it at the closest possible point of task execution, like so:
import requests

def does_google_say_google():
  res = task.executor(requests.get,'http://google.com')
  if "google" in res.text:
    return True
  return False

@time_trigger('startup')
def dothething():
  result = does_google_say_google()
  if result:
    log.info('google says google')

Sorry, I've been busy working on rewriting reload.
One important point is that threading most definitely doesn't work with pyscript.  Pyscript is not thread safe, and many of the HASS primitives it calls aren't thread safe either (ie, they need to run in the main event loop).

Thank you very much for the detailed explanations.
I am not a developer but casually use Python for 10 years and having always had used threading, I see it is time to move to more modern solutions.
I, for now, wanted to try the subfolder solution outlined in the docs @dlashua pointed to (to separate the non-pyscript code), but I have a hard time having it recognized in imports.
My folders structure is the following:
/etc/docker/data/hass/pyscript # tree
.
├── automation__fuite_eau.py
├── automation__lights.py
├── automation__volets.py
├── automation__zigbee_rf433.py
├── dash
│   ├── dash__darkmode.py
│   ├── __init__.py
│   └── meteo.py
├── dash__darkmode.py
├── dash.py
├── requirements.txt
└── test1.py

The dash directory will have all kinds of microservices that power a homemade dashboard (something independent of HA, written in JS). They used to be in different places (running in their own docker containers, then in one big, then in AppDaemon but I feel that their best place will be in pyscript as they may set some information useful to HA through MQTT (so no HA/pyscript specific calls are needed there, the code is standalone).
dash.py is expected to trigger these microservices, via pyscript mechanisms (usually time or mqtt based). I imagined it to be something like:
/etc/docker/data/hass/pyscript # cat dash.py

import sys
if "config/dash" not in sys.path:
    sys.path.append("config/dash")

from dash.meteo import meteo

@service
def run_meteo(**data):
    meteo()

I tried all possible combinations of the first part if ... (with config and without - not sure why it was there in the docs), and of the import from dash.meteo import meteo  (this one makes the most sense to me as I am importing the function meteo() from the module meteo.py located in dash - but I tried also others just in case.)
I always end up with an import error such as
2020-12-06 14:11:43 ERROR (MainThread) [custom_components.pyscript.file.dash] Exception in </config/pyscript/dash.py> line 5:
    from dash.meteo import meteo
    ^
ModuleNotFoundError: No module named 'dash'

The meteo.py module itself is below for completeness (it is a draft and won't work as it - but the problem for now is that I am not even able to import it)
/etc/docker/data/hass/pyscript # cat dash/meteo.py

import requests
import json
import logging as log
import paho.mqtt.publish

def meteo():
    try:
        r = requests.get(
            "https://api.darksky.net/forecast/b...1?lang=fr&units=si",
            timeout=10
        )
        r.raise_for_status()
    except Exception as e:
        log.warning(f"cannot connect to weather API: {e}")
    else:
        log.debug(r.json())
        paho.mqtt.publish.single(
            topic=f"dehors/meteo",
            payload=json.dumps(r.json()),
            retain=True,
            hostname="mqtt.myserver"
        )

I think the import solution is not working for you because of a paths issue.
'config/' as mentioned in the docs is your Home Assistant config directory. So your tree should look something like this:
config/
  configuration.yaml
  pyscript/
    somescript.py
  pyscript_modules/
    somemodule.py

With this in place, your import would look like this:
import sys
if "config/pyscript_modules" not in sys.path:
    sys.path.append("config/pyscript_modules")

Take note that the pyscript_modules directory is NOT under pyscript.


Added base Quarkus CI tekton pipeline

This is a helm chart to install the Tekton pipeline for a quarkus application for issue #1

Agreed.
Done.


Namespace default configuration file location

src/config.h.in:
Namespace the default configuration file location with the project's
name "umurmur", as in that location also the required certificates are
expected by default and using a namespaced location makes sense as to
not clutter the SYSCONFDIR (e.g. /etc/) with more files, as a namespace
is necessary anyways.
CMakeLists.txt:
Install the default configuration file to a "umurmur" namespaced
location.
Fixes #169

@fatbob313 can this be merged?
From a packaging perspective a namespaced location is the only thing that makes sense, as that way arbitrary configuration related files such as TLS certificates can be added (e.g. in the context of certbot deply hooks) and made available specifically for the umurmur application while rendering them inaccessible to other applications and users.


Embedding image(s) in a custom layout results in an unnecessary warning about the public folder

I created a custom layout cover.vue. To add an image to the layout, I used an  tag. Since the layout is stored in the layouts folder, I need to reference ../public/img/ for the image filepath instead of ./img (like one would in a Slidev Markdown file).
However, this results in a (well-intentioned) warning about referencing the public folder that prints for each slide. Ideally, this warning would only apply to Slidev Markdown files.

Example custom cover layout:
<template>

</template>

Results in these warnings:
Files in the public directory are served at the root path.
Instead of /public/img/logos/PSU_Engineering.png, use /img/logos/PSU_Engineering.png.
Files in the public directory are served at the root path.
Instead of /public/img/logos/PSU_Aero.png, use /img/logos/PSU_Aero.png.
Files in the public directory are served at the root path.
Instead of /public/img/logos/PURL.png, use /img/logos/PURL.png.

This issue is platform-agnostic, but:

OS: Windows 11
Browser: Brave, Firefox, Edge
Slidev version: 0.48.8

The usage of the public folder is:

Wherever the Markdown or Vue file is.

The usage of the public folder is:

Wherever the Markdown or Vue file is.

I see my issue now, thanks - I had missed the note about the leading slash in the docs, and had tried using "./", instead of "/".

Suggested a clarification for this in #1489 to prevent others from making the same mistake.


Implement generic data for data scripts

Implementation plan:

Write generic Data type.
Rewrite our examples so they use Data everywhere.

This should iron out any kinks in the representation, and reveal how awkward it is to work with.

Change the ledger representation of data scripts to be serialised Data

The validator scripts shouldn't change at this stage.

Remove Sealed, put data scripts into PendingTx as Data.

I plan to PR 1+2, then 3, then 4.

Ah, and
5. Make PendingTx into Data.

Is there any pressing reason to make PendingTx into Data?  I don't have any objections, I'm just curious; I suppose it'd be nice for consistency though.  If you do this it'd be interesting if you could compare how big/complicated the corresponding Plutus Core is before and after the change.

Apart from that, a big thumbs up for this.

It makes specifying the system easier, no? As we discussed before, as long as we have something the validating node has to lift as a Haskell type we have an implicit dependency on Haskell.

I'll make more issues for other things, so I'll close this when the other PR is in.


No license

Hello
Thank you for your project, it helped greatly in my own one.
Could you please specify a license so your code could be more easily reused?

@eqv Gentle nudge -- any thoughts on a license? My team of academic researchers will soon release a FOSS tool where gdb-mi-parser is a dependency :)

fixed #2, let me know if MIT doesn't work for you for some reason.


nftables fails to restart after libvirtd gets started

Describe the bug
libvirtd seems to be able to bring up iptables and load the ip_tables module even when it's in the blacklist, this seems to be similar to what was happening in #24318, and the libvirtd module is in fact including pkgs.iptables instead of config.networking.firewall.package which I guess would make it work when using pkgs.iptables-nftables-compat.
To Reproduce
Steps to reproduce the behavior:

Enable nftables.
nixos-rebuild switch
Enable libvirtd.
nixos-rebuild switch
BOOM

Expected behavior
For libvirtd to use the right firewall package and not load the ip_tables module.
Additional context
I've used libvirtd before with iptables-nft on Arch, and it was working properly.
Notify maintainers
@globin @fpletz
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.41, NixOS, 20.09pre226148.0f5ce2fac0c (Nightingale)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.4`
 - channels(root): `"nixos-20.09pre226148.0f5ce2fac0c"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module: nixos/modules/virtualisation/libvirtd.nix

Wait, I'm a dummy, digged a little deeper and iptables-nftables-compat is just iptables, and it's the same for iptables-nft in Arch, is the issue just the way the check is done in the nftables service?

I'm still waiting for this to get merged https://github.com/NixOS/nixpkgs/pull/81172 I guess this will fix nftables+docker for me and might be related to your issue

Since iptables and nftables work completely fine together, I'm seriously questioning the value of having the ip_tables check in nixpkgs/nixos/modules/services/networking/nftables.nix at all.
Simply removing the checkScript portion of the service would obviously solve this problem, as well as any future "bad piece of software decided to load ip_tables and now I can't update my firewall" issues.

With the switch to iptables-nft, the nftables NixOS module should probably be revisited. I opened https://github.com/NixOS/nixpkgs/issues/161428 as a proposal.