Ran unifdef to remove INACTIVITY_TIMEOUT code blocks

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/293/

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/279/

AU check failed! https://ci.trafficserver.apache.org/job/autest-github/275/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1974/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1866/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/406/

clang-analyzer build failed! https://ci.trafficserver.apache.org/job/clang-analyzer-github/538/

RAT check successful! https://ci.trafficserver.apache.org/job/RAT-github/301/

clang format successful! https://ci.trafficserver.apache.org/job/clang-format-github/287/

AU check successful! https://ci.trafficserver.apache.org/job/autest-github/283/

Intel CC build successful! https://ci.trafficserver.apache.org/job/icc-github/413/

Linux build successful! https://ci.trafficserver.apache.org/job/linux-github/1874/

FreeBSD11 build successful! https://ci.trafficserver.apache.org/job/freebsd-github/1982/

clang-analyzer build failed! https://ci.trafficserver.apache.org/job/clang-analyzer-github/546/

@zwoop  Do we really want remove the codes ?
Inactivity Timeout and Active timeout have 2 types of implement in ATS.

by schedule_in

create too many event in EventQueue

by InactivityCop

makes Inactivity Timeout and Active timeout no different.

But I'm prefer InactivityCop.
+1 for the PR.

@oknet The scheduling path was a long time ago deemed too expensive to handle, but honestly, not sure if that's true any more. It's possible if @SolidWallOfCode and @PSUdaemon improves on the event system, we could do the scheduling instead? The issue being the excessive adding / deleting of events (I think).

@zwoop
With scheduling path, these 2 types of timeout event is put into EventQueue that is a priority queue.
With InactivityCop, every second we copy NetVCs from open_list to cop_list and walk through cop_list that means walk through all the NetVCs twice every second.

If someone wants to test / investigate the scheduled inactivity cop, I'd be fine with leaving this code as is. Also, remember that it's possible to tweak how often we run inactivity cop, we added a configuration for this (proxy.config.net.inactivity_check_frequency). Maybe we should bump the default for this to say 10s?
Alternatively, it could maybe be nice to take all the VCs that needs to be checked, and split them evenly out over (proxy.config.net.inactivity_check_frequency), such that you check
                    <n>
             ------------
proxy.config.net.inactivity_check_frequency

VCs every second?

I'm making this as WIP for now, since it's not clear that we want to land this.

@oknet  Have you tried running using the event handler for inactivity timeouts?

@zwoop According to the design of InactivityCop, the proxy.config.net.inactivity_check_frequency should less than or equal 1s otherwise the TIMEOUT event would be delay to SM.
@bryancall No, I have not tried it. But it is triggered by priority queue that is more efficient.
Currently, I consider the NetHandler is a NThread(Net Thread) inside of EThread(Event Thread).
NetHandler has its Protect Queue (enabled_list and ready_list)
EThread has its Protect Queue (ExternalQueue and ExternalQueue.local)
NetHandler has its Internal Queue (epoll fdset and ready_list)
EThread has its Protect Queue (EventQueue that is a priority queue)
And NetHandler has other queues: open_list, cop_list.
The NetVC has a dual identity:

SM, it could be call back by EThread and others
Event, NetHandler call back the VIO event by NetVC

An Event can not rescheduled to another EThread and also a NetVC can not rescheduled to another NetHandler since the NetVC is an 'Event' to callback SM.
An SM could be call back from any EThread and a NetVC also could be call back from any EThread before it is managed by NetHandler. Because NetHandler gives it the second identity (Event).
Therefore amc and susan designed and implement the VC migration functions.
The InactivityCop is a sub-part of NetHandler and it is not a full-featured alternative for active timeout and Inactive timeout.
We should do more for InactivityCop,

A new queue to replace open_list

to save new NetVC that did not set the timeout
to save NetVC that has read and write disabled
set inactivity_timeout_in to default (86400)
check eveny 10mins or the active_queue / keepalive_queue full.

A new priority queue to replace cop_list

to save any NetVC that has timeout set
using MIN(active_timeout_in, inactive_timeout_in) as key

schedule InactivityCop in Negative Queue

check cop_list like EventQueue in EThread::execute()

period schedule InactivityCop in EventQueue

check open_list eveny 10mins (configureable)

Hmmm, what exactly does this mean:
@zwoop According to the design of InactivityCop, the proxy.config.net.inactivity_check_frequency should less than or equal 1s otherwise the TIMEOUT event would be delay to SM.

We do
thread->schedule_every(inactivityCop, HRTIME_SECONDS(cop_freq));
Are you saying it'd be bad for the ET_NET if that schedule is > 1s? If so, we really ought to modify RecordsConfig.cc / code such that it can not be configured differently. Also, it's then really odd that this is in seconds, because the only two viable options would be 0 or 1, right ? And I can't imagine 0 is a good value. The conclusion would be that if "1" is the only viable option, we should either

Eliminate this configuration entirely.

Change it to be in milli-seconds, with a default (and max) of 1000.

@zwoop
We set timeout with set_inactivity_timeout(HRTIME_SECONDS(x)) that means ATS call back TIMEOUT event between x th and x+1 th second.
To achieve this, ATS must check timeout every second or less otherwise the TIMEOUT event will be send between (x+cop_freq) th and (x+cop_freq+1) th second at latest.

[approve ci]

@oknet What should we do here? Do this (merge) or keep it ?

@zwoop +1 merge since the event mode may not working with HttpSM now.
To operation on the timeout event, the HttpSM should acquire the lock of vc->nh or the vc->nh has been locked. I don't think the HttpSM does it as well.

[approve ci clang-analyzer]

Rebased and fixed conflicts. Please take another look.


[Event Request] Codeunit Intrastat Document Completion (331), Procedure "DefaultSalesDocuments"

Hi,
we need to transfer additional values from Intrastat Setup to the Sales Header, so would like to suggest the event "OnAfterDefaultSalesDocuments" in procedure "DefaultSalesDocuments":
OnAfterDefaultSalesDocuments(Rec, IntrastatSetup);
The Event signature should look like this:
[IntegrationEvent(false, false)]
local procedure OnAfterDefaultSalesDocuments(var SalesHeader: Record "Sales Header"; IntrastatSetup: Record "Intrastat Setup")
begin
end;

Thanks!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


enable strict mode

fixes #240
flip the switch to enforce 'use strict'; with eslint

@juttle/developers 'use strict'; everywhere!

Oh so strict... +1 on green.
One question -- did eslint --fix do this for you?

@demmer eslint wouldn't add the line but use-strict-cli did the trick!

Good to know. Thanks.
On Fri, Jan 22, 2016 at 1:36 PM, Rodney Lopes Gomes <
<EMAIL_ADDRESS>wrote:

@demmer https://github.com/demmer eslint wouldn't add the line but
use-strict-cli https://www.npmjs.com/package/use-strict-cli did the
trick!
—
Reply to this email directly or view it on GitHub
https://github.com/juttle/juttle/pull/249#issuecomment-174057421.

--
Michael Demmer
Jut - CTO / VP Engineering
<EMAIL_ADDRESS>

merging this on the +1 Demmer gave me and just a small tweak for that scoping issue in the graphi-compiler.js file.


Update ghcr.io/fluxcd/image-reflector-controller Docker tag to v0.5.0

This PR contains the following updates:

Package
Update
Change

ghcr.io/fluxcd/image-reflector-controller
minor
v0.4.1 -> v0.5.0

Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (v0.5.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.
If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.


Ports values were swapped in the UI based on Mesos data

copy of https://mesosphere.atlassian.net/browse/DCOS-9629
reported by @lloesche
I have a service that uses persistent volumes and two tcp ports.
When restarting the service it's being restarted on the same host using the same random host ports. However the mapping of container to host port might be shuffled.
E.g.
container 9090 -> host 21926
container 9093 -> host 21927
RESTART
container 9090 -> host 21927
container 9093 -> host 21926
However the DC/OS UI shows the host to container port mapping wrong every now and then.
It's correct after initial start but sometimes incorrect after the ports have been shuffled due to a restart.

state.json.txt
Example /service/marathon/v2/apps/prometheus/server output fetched when the screenshot above was taken.
{
  "app": {
    "id": "/prometheus/server",
    "cmd": null,
    "args": null,
    "user": null,
    "env": {
      "PAGERDUTY_KEY": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
      "NODE_EXPORTER_SRV": "_node-exporter.prometheus._tcp.marathon.mesos"
    },
    "instances": 1,
    "cpus": 0.5,
    "mem": 2048,
    "disk": 0,
    "gpus": 0,
    "executor": "",
    "constraints": [],
    "uris": [],
    "fetch": [],
    "storeUrls": [],
    "backoffSeconds": 1,
    "backoffFactor": 1.15,
    "maxLaunchDelaySeconds": 3600,
    "container": {
      "type": "DOCKER",
      "volumes": [
        {
          "containerPath": "prometheus",
          "mode": "RW",
          "persistent": {
            "size": 1024
          }
        }
      ],
      "docker": {
        "image": "lloesche/prometheus-dcos",
        "network": "BRIDGE",
        "portMappings": [
          {
            "containerPort": 9090,
            "hostPort": 0,
            "servicePort": 10001,
            "protocol": "tcp",
            "labels": {
              "VIP_0": "/prometheus/server:9090"
            }
          },
          {
            "containerPort": 9093,
            "hostPort": 0,
            "servicePort": 10002,
            "protocol": "tcp",
            "labels": {
              "VIP_1": "/prometheus/server:9093"
            }
          }
        ],
        "privileged": false,
        "parameters": [],
        "forcePullImage": true
      }
    },
    "healthChecks": [
      {
        "path": "/metrics",
        "protocol": "HTTP",
        "portIndex": 0,
        "gracePeriodSeconds": 300,
        "intervalSeconds": 60,
        "timeoutSeconds": 20,
        "maxConsecutiveFailures": 3,
        "ignoreHttp1xx": false
      }
    ],
    "readinessChecks": [],
    "dependencies": [],
    "upgradeStrategy": {
      "minimumHealthCapacity": 0.5,
      "maximumOverCapacity": 0
    },
    "labels": {},
    "acceptedResourceRoles": null,
    "ipAddress": null,
    "version": "2016-09-06T16:07:36.977Z",
    "residency": {
      "relaunchEscalationTimeoutSeconds": 3600,
      "taskLostBehavior": "WAIT_FOREVER"
    },
    "secrets": {},
    "taskKillGracePeriodSeconds": null,
    "ports": [
      10001,
      10002
    ],
    "portDefinitions": [
      {
        "port": 10001,
        "protocol": "tcp",
        "labels": {}
      },
      {
        "port": 10002,
        "protocol": "tcp",
        "labels": {}
      }
    ],
    "requirePorts": false,
    "versionInfo": {
      "lastScalingAt": "2016-09-06T16:07:36.977Z",
      "lastConfigChangeAt": "2016-09-06T13:33:54.912Z"
    },
    "tasksStaged": 0,
    "tasksRunning": 1,
    "tasksHealthy": 1,
    "tasksUnhealthy": 0,
    "deployments": [],
    "tasks": [
      {
        "id": "prometheus_server.9f5e60f6-7435-11e6-b7c8-70b3d5800001",
        "slaveId": "cdf14879-60f4-484e-8179-b8962c61322e-S5",
        "host": "<IP_ADDRESS>",
        "state": "TASK_RUNNING",
        "startedAt": "2016-09-06T16:07:51.070Z",
        "stagedAt": "2016-09-06T16:07:42.513Z",
        "ports": [
          21927,
          21926
        ],
        "version": "2016-09-06T16:07:36.977Z",
        "ipAddresses": [
          {
            "ipAddress": "<IP_ADDRESS>",
            "protocol": "IPv4"
          }
        ],
        "localVolumes": [
          {
            "containerPath": "prometheus",
            "persistenceId": "prometheus_server#prometheus#9f5debc5-7435-11e6-b7c8-70b3d5800001"
          }
        ],
        "appId": "/prometheus/server",
        "healthCheckResults": [
          {
            "alive": true,
            "consecutiveFailures": 0,
            "firstSuccess": "2016-09-06T16:08:37.051Z",
            "lastFailure": null,
            "lastSuccess": "2016-09-06T17:02:38.127Z",
            "lastFailureCause": null,
            "taskId": "prometheus_server.9f5e60f6-7435-11e6-b7c8-70b3d5800001"
          }
        ]
      }
    ],
    "lastTaskFailure": {
      "appId": "/prometheus/server",
      "host": "<IP_ADDRESS>",
      "message": "Container terminated",
      "state": "TASK_FAILED",
      "taskId": "prometheus_server.9f5e60f6-7435-11e6-b7c8-70b3d5800001",
      "timestamp": "2016-09-06T16:07:38.346Z",
      "version": "2016-09-06T16:07:36.977Z",
      "slaveId": "cdf14879-60f4-484e-8179-b8962c61322e-S5"
    }
  }
}

The Load balancer UI shows the correct mapping btw. it's only the Service view that doesn't

it sounds like this is a DCOS UI bug vs. a Marathon bug

I think the data source for this display is the groups api (the UI always use the groups endpoint) inside the nodes under $appId > container. I don`t think the ui manipulates this data.  @wavesoft @orlandohohmeier please confirm :)
Here an example of another app, taken from the groups api:
"container": {
"type": "DOCKER",
"volumes": [],
"docker": {
"image": "muhapp:3.1.0-RC1",
"network": "BRIDGE",
"portMappings": [
{
"containerPort": 7474,
"hostPort": 0,
"servicePort": 10000,
"protocol": "tcp"
},
{
"containerPort": 7473,
"hostPort": 0,
"servicePort": 10001,
"protocol": "tcp"
},
{
"containerPort": 7687,
"hostPort": 0,
"servicePort": 10002,
"protocol": "tcp"
}
],
"privileged": false,
"parameters": [],
"forcePullImage": true
}

Talked to @lloesche, he said that this happens only for resident tasks and this was an ui issue. The api worked as expected. I tried to reproduce this with current testing/master cluster but it did not happen within 20 restarts.

Can not reproduce. Restarted the following app over 20 times and did not observed this behavior.
{
  "id":"example",
  "cpus":1,
  "mem":4000,
  "instances":1,
  "disk": 8000,
  "container":{
    "type":"DOCKER",
    "docker":{
      "image":"nginx",
      "network":"BRIDGE",
      "forcePullImage":true,
      "portMappings":[
        {
           "hostPort":0,
           "containerPort":80,
           "name":"http",
           "protocol":"tcp"
        },
        {
           "hostPort":0,
           "containerPort":443,
           "name":"https",
           "protocol":"tcp"
        }
      ],
      "volumes":[
        {
          "containerPath":"data",
          "mode":"RW",
          "persistent":{
            "type":"root",
            "size":8000
          }
        },
        {
          "containerPath":"/data",
          "hostPath":"data",
          "mode":"RW"
        }
      ]
    }
  }
}

With the following app definition this behavior is reproducible:
{
  "id": "/sleepy",
  "cmd": "sleep 1000",
  "cpus": 1,
  "mem": 128,
  "disk": 100,
  "instances": 1,
  "executor": null,
  "fetch": null,
  "constraints": null,
  "acceptedResourceRoles": null,
  "user": null,
  "container": {
    "docker": {
      "image": "ubuntu",
      "forcePullImage": false,
      "privileged": false,
      "portMappings": [
        {
          "containerPort": 80,
          "protocol": "tcp"
        },
        {
          "containerPort": 443,
          "protocol": "tcp"
        }
      ],
      "network": "BRIDGE"
    },
    "type": "DOCKER",
    "volumes": [
      {
        "containerPath": "/data",
        "persistent": {
          "size": 100
        },
        "mode": "RW"
      }
    ]
  },
  "updateStrategy": {
    "maximumOverCapacity": 0,
    "minimumHealthCapacity": 0
  },
  "residency": {
    "relaunchEscalationTimeoutSeconds": 10,
    "taskLostBehavior": "WAIT_FOREVER"
  },
  "healthChecks": null,
  "env": null
}

UI:
{
    "type": "DOCKER",
    "docker": {
        "image": "ubuntu",
        "network": "BRIDGE",
        "port_mappings": [
            {
                "host_port": 24781,
                "container_port": 80,
                "protocol": "tcp"
            },
            {
                "host_port": 24782,
                "container_port": 443,
                "protocol": "tcp"
            }
        ],
        "privileged": false,
        "force_pull_image": false
    }
}

Docker deamon:
$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                           NAMES
eb9d70971e7f        ubuntu              "/bin/sh -c 'sleep 10"   48 seconds ago      Up 48 seconds       <IP_ADDRESS>:24782->80/tcp, <IP_ADDRESS>:24781->443/tcp   mesos-a6893e50-40a4-48cb-b4c2-b9e63bd2a08d-S0.2afc67d1-a6c9-44ae-92c5-784cdc56fcfa

Ok, investigated again:
Marathon re-uses TaskIds for resident Tasks, this means that the mesos state.json will return something like this:
[
  {
    "id":"m2.6d62fd63-be00-11e6-ba0c-d23a4f1e7619",
    ...
    "port_mappings":[
      {
        "host_port":17294,
        "container_port":80,
        "protocol":"tcp"
      },
      {
        "host_port":17295,
        "container_port":443,
        "protocol":"tcp"
      }
    ]
  },
  "id":"m2.6d62fd63-be00-11e6-ba0c-d23a4f1e7619",
  ...
  "port_mappings":[
    {
      "host_port":17295,
      "container_port":80,
      "protocol":"tcp"
    },
    {
      "host_port":17294,
      "container_port":443,
      "protocol":"tcp"
    }
  ]
}
]

and when the users clicks on a particular task in the ui, the ui tries to request the information for the task with the id m2.6d62fd63-be00-11e6-ba0c-d23a4f1e7619. But this id is present multiple times within this json array and it is not possible to decide which one to choose to display the data. Closing this in favor of this GH issue, addressing the root cause: https://github.com/mesosphere/marathon/issues/4819


cfdyndns timer does not start on 20.09

I was wondering why my dns record was not being updated and I noticed that the timer of cfdyndns appears to be broken (at least on nixos 20.09).
$ journalctl -u cfdyndns.timer
/nix/store/pxjfxdaz8cfr3n4p627p7bcavchbchvn-unit-cfdyndns.timer/cfdyndns.timer:4: Failed to parse calendar specification, ignoring: 5 minutes
cfdyndns.timer: Timer unit lacks value setting. Refusing.
cfdyndns.timer: Cannot add dependency job, ignoring: Unit cfdyndns.timer has a bad unit file setting.

The content of the timer is:
$ cat /nix/store/pxjfxdaz8cfr3n4p627p7bcavchbchvn-unit-cfdyndns.timer/cfdyndns.timer
[Unit]

[Timer]
OnCalendar=5 minutes

I do not know much about systemd, however it seems "5 minutes" may not be correct for calendar?
$ systemd-analyze calendar "5 minutes"
Failed to parse calendar specification '5 minutes': Invalid argument
Hint: this expression is a valid timespan. Use 'systemd-analyze timespan "5 minutes"' instead?

Notify maintainers
@felschr @flokli @colemickens

If I'm not misinterpreting systemd.timer (5), OnCalendar= keys may only "define realtime (i.e. wallclock) timers with calendar event expressions". 5 minutes is a monotonic timer, which can't be used for OnCalendar=.
You might want to use a calendar event spec, with some AccuracySec=, and RandomizedDelaySec= to allow for some smearing.
❯ systemd-analyze calendar "*-*-* *:0/5:00" --iterations=3
  Original form: *-*-* *:0/5:00
Normalized form: *-*-* *:00/5:00
    Next elapse: Sun 2021-03-07 20:20:00 CET
       (in UTC): Sun 2021-03-07 19:20:00 UTC
       From now: 2min 0s left
       Iter. #2: Sun 2021-03-07 20:25:00 CET
       (in UTC): Sun 2021-03-07 19:25:00 UTC
       From now: 7min left
       Iter. #3: Sun 2021-03-07 20:30:00 CET
       (in UTC): Sun 2021-03-07 19:30:00 UTC
       From now: 12min left

My workaround until the service is fixed is to add
systemd.services.cfdyndns.startAt = lib.mkForce "*:0/5";

to the config.

#140343


Stop loading default chat room initally for those outside of beta

@deetergp, please review when you get the chance
CC: @yuwenmemon
Details
There was an edge case we didn't consider when putting default rooms behind betas. If a domain has a domainAll room (which we make behind the scenes for domains that aren't in the defaultRooms beta) and a user gets created after that room is made, they will actually see that room when they first log in (i.e. it'll be their "last accessed chat report"). They should see the concierge chat first, but that chat will be created after their account is made (which happens after the domainAll room was made).
This PR makes it so new users won't land on a default domainAll room the first time they log in. This also prevents users from seeing a default room if they aren't in the beta and somehow managed to open a default chat room (to stop other edge cases we might have missed.
Also this is relevant to N6, since we're likely to see a lot of new users sign up and use NewDot with this.
Fixed Issues
$ https://github.com/Expensify/Expensify/issues/177836
Tests
Same as Web QA, but done locally. I used clitools.sh for making the domain, admin account, and second account. To test a user being outside of the default rooms beta locally, I made this line false: https://github.com/Expensify/App/blob/0e6fdbf0e3b9f87572701c90c78b2ab73540b3ff/src/libs/Permissions.js#L51
QA Steps

Find a domain whose users won't be in the freePlan beta.
Invite a new account to that domain (can be similar to amal+something@expensifail.com). Avoid signing in with the email sent to the newly created user.
Log into that account on NewDot before joining on OldDot. You can do this by entering the email in NewDot and then using the magic sign in link from there. You might have to set a password at this point too.
Verify that the first report you see is the concierge one and not

Tested On

[x] Web
[x] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web
This is what it looks like now if you try to access a report by URL (11073 is a domainAll room)

Mobile Web
Same thing is a blank screen on mobile obviously, but users should never be able to see this report anyway without manually entering into the url like I did.

🚀 Deployed to staging by @deetergp in version: 1.0.99-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by @Jag96 in version: 1.1.0-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


CFE should not allow type literals which are not compile-time constants in default values of optional parameters

The following example compiles just fine with CFE:
bar<T>([var param = T]) {
  print(T);
  print(param);
}

main() {
  bar<int>();
}

It prints
int
T

The problem is that 'T' is not a compile-time constant and should not be allowed in the default value of optional parameter.
/cc @kmillikin @askeksa-google

FYI: this error is reported by dart2js.

Closing because there is no more work to do on this except flipping the flag. This will give us a better overview of remaining issues.


Support thread command by gdb python script

Summary
Support thread command on nuttx
support arch:
sim x86
sim x86_64
arm32 all series
If we need to support more architectures in the future,
just add the 'g_tcbinfo' of the corresponding architecture
support thread command:

thread
switch thread

info thread
list all thread info

thread apply [all | id list] command
like this:
thread apply all bt
thread apply all bt full
thread apply 1 2 4 bt
thread apply all info r

nxsetregs
Set registers to the specified values.
Usage: nxsetregs [regs]
Etc:
nxsetregs
nxsetregs g_current_regs[0]
nxsetregs tcb->xcp.regs
Nxsetregs g_pidhash[0].tcb->xcp.regs
Default regs is g_current_regs[0],if regs is NULL,
it will not set registers.
Because NuttX enters exception_common during a crash,
this assembly function manipulates the stack pointer (sp),
causing GDB to be unable to trace back to the first context of the crash.
Instead, it shows the context of the interrupt stack. By using nxsetregs,
it is possible to forcefully set the first context to
the one before the interrupt occurred.

Notice:
Switching threads is achieved by setting registers,
so registers need to be restored before continue,
please use 'c' to continue instead of 'continue'
Impact
gdb debug
Testing
sim32
sim64
stm32f429i-disco with jlink
Usage
CONFIG_DEBUG_TCBINFO=y
add '-ex "souce tools/gdb/__init__.py"' in gdb command or 'souce tools/gdb/__init__.py' in gdb shell

let ignore xtensa specific ci temp broken.

@anjiahao1
I noticed that ostest with qemu-armv8a:netnsh_smp causes a deadlock.
user_main: signal handler test
sighand_test: Initializing semaphore to 0
sighand_test: Unmasking SIGCHLD
sighand_test: Registering SIGCHLD handler
sighand_test: Starting waiter task
sighand_test: Started waiter_main pid=153
waiter_main: Waiter started
waiter_main: Unmasking signal 32
waiter_main: Registering signal handler
waiter_main: oact.sigaction=0 oact.sa_flags=0 oact.sa_mask=0000000000000000
waiter_main: Waiting on semaphore
sighand_test: Signaling pid=153 with signo=32 sigvalue=42

If I rever the following commit, the deadlock disappeared.
commit 8abf803a1d7147efebc987a8ec5ac961a9a50515
Author: anjiahao<EMAIL_ADDRESS>Date:   Fri Jul 21 19:59:59 2023 +0800

    arm64:Need to store native sp pointer to tcb

    Signed-off-by: anjiahao<EMAIL_ADDRESS>

@anjiahao1

I noticed that ostest with qemu-armv8a:netnsh_smp causes a deadlock.

The ostest crashed with qemu-armv8a:nsh_smp.
user_main: signal handler test
sighand_test: Initializing semaphore to 0
sighand_test: Starting waiter task
sighand_test: Started waiter_main pid=155
waiter_main: Waiter started
waiter_main: Unmasking signal 32
waiter_main: Registering signal handler
waiter_main: oact.sigaction=0 oact.sa_flags=0 oact.sa_mask=0000000000000000
waiter_main: Waiting on semaphore
sighand_test: Signaling pid=155 with signo=32 sigvalue=42
[CPU0] nxsig_queue: pid=0x0000009b signo=32 value=42
[CPU0] nxsig_tcbdispatch: TCB=0x40378700 pid=155 signo=32 code=1 value=42 masked=NO
[CPU0] up_schedule_sigaction: tcb=0x40378700 sigdeliver=0x4028b6e0
[CPU0] up_schedule_sigaction: rtcb=0x4037d550 CURRENT_REGS=0
[CPU1] arm64_fatal_error: reason = 1
[CPU1] arm64_fatal_error: CurrentEL: MODE_EL1
[CPU1] arm64_fatal_error: ESR_ELn: 0x1fe00000
[CPU1] arm64_fatal_error: FAR_ELn: 0x0
[CPU1] arm64_fatal_error: ELR_ELn: 0x40290994
[CPU1] print_ec_cause: Trapped access to SVE, Advanced SIMD, or floating-point functionality
[CPU1] _assert: Current Version: NuttX  10.4.0 0092b3e30f Jul 24 2023 19:30:27 arm64
[CPU1] _assert: Assertion failed panic: at file: common/arm64_fatal.c:375 task(CPU1): waiter 0x402a2d24
[CPU1] up_dump_register: stack = 0x40373f30
[CPU1] up_dump_register: x0:   0x402c5ea8          x1:   0xdeaddead
[CPU1] up_dump_register: x2:   0x402bc0d0          x3:   0x40286b98
[CPU1] up_dump_register: x4:   0x402c5ee8          x5:   0x40287c94
[CPU1] up_dump_register: x6:   0x40378700          x7:   0x1
[CPU1] up_dump_register: x8:   0x402bc0d0          x9:   0x40286b98
[CPU1] up_dump_register: x10:  0x402c5ee8          x11:  0x40287c94
[CPU1] up_dump_register: x12:  0x40378700          x13:  0x1
[CPU1] up_dump_register: x14:  0x402c5ee4          x15:  0x40287cfc
[CPU1] up_dump_register: x16:  0x1                 x17:  0x0
[CPU1] up_dump_register: x18:  0x402c5000          x19:  0x40378700
[CPU1] up_dump_register: x20:  0x402c5000          x21:  0x40286f94
[CPU1] up_dump_register: x22:  0x402bc150          x23:  0x0
[CPU1] up_dump_register: x24:  0x40378bac          x25:  0x402bc150
[CPU1] up_dump_register: x26:  0x0                 x27:  0x4028c2ec
[CPU1] up_dump_register: x28:  0x402bc150          x29:  0x402bc0d0
[CPU1] up_dump_register: x30:  0x40378bac
[CPU1] up_dump_register:
[CPU1] up_dump_register: STATUS Registers:
[CPU1] up_dump_register: SPSR:      0x4008e610
[CPU1] up_dump_register: ELR:       0x402bc168
[CPU1] up_dump_register: SP_EL0:    0x40374060
[CPU1] up_dump_register: SP_ELX:    0x40374060
[CPU1] up_dump_register: TPIDR_EL0: 0x40378700
[CPU1] up_dump_register: TPIDR_EL1: 0x40378700
[CPU1] up_dump_register: EXE_DEPTH: 0x1
[CPU1] dump_tasks:    PID GROUP   CPU PRI POLICY   TYPE    NPX STATE   EVENT      SIGMASK          STACKBASE  STACKSIZE      USED   FILLED    COMMAND
[CPU1] dump_tasks:   ----   ---  ---- --- -------- ------- --- ------- ---------- -------- 0x402cb000      8192      8192   100.0%!   irq
[CPU1] dump_task:       0     0     0   0 FIFO     Kthread N-- Assigned<PHONE_NUMBER>000000 0x402d1010     16368      1360     8.3%    CPU0 IDLE
[CPU1] dump_task:       1     1     1   0 FIFO     Kthread N-- Assigned<PHONE_NUMBER>000000 0x402d5010     16368      1088     6.6%    CPU1 IDLE
[CPU1] dump_task:       2     2     2   0 FIFO     Kthread N-- Running<PHONE_NUMBER>000000 0x402d9010     16368      1088     6.6%    CPU2 IDLE
[CPU1] dump_task:       3     3     3   0 FIFO     Kthread N-- Running<PHONE_NUMBER>000000 0x402dd010     16368      1088     6.6%    CPU3 IDLE
[CPU1] dump_task:       4     4     0 192 RR       Kthread --- Waiting Semaphore<PHONE_NUMBER>000000 0x402e39f0     16320      1264     7.7%    hpwork 0x402c64f8
[CPU1] dump_task:       5     5     0 100 RR       Task    --- Waiting Semaphore<PHONE_NUMBER>000000 0x402e8000     16336      2944    18.0%    nsh_main
[CPU1] dump_task:      22    22     0 100 RR       Task    --- Running<PHONE_NUMBER>000000 0x4036c6e0     16288      2320    14.2%    ostest Arg1 Arg2 Arg3 Arg4
[CPU1] dump_task:     155   155     1 100 RR       Task    --- Running<PHONE_NUMBER>000000 0x403706c0     16336      3552    21.7%    waiter
[CPU1] dump_task:      15    15     0 100 RR       Task    --- Waiting Semaphore<PHONE_NUMBER>000000 0x40379530     16336      1984    12.1%    ostest

Could you please confirm if the latest upstream works with qemu?


Badges pt 2

https://github.com/exogen/badge-matrix#browser-matrix-badges-for-sauce-labs

Closing in favor of #63


Break iOS code into constants for all Cordova methods and events

The method names and events should be broken into its own module for the following.  This is for @softwarenerd but will be moved to David Douglas once he is working on the code actively.
Methods

StartBroadcasting
StopBroadcasting
Connect
Disconnect

Events

peerActivityChanged
networkChanged

I assume we mean move the api surface to jxCoreExtensions.m

Is this finished?


CH3 error from ad-hoc command to install Django with pip3

This is also piggybacked onto another issue at https://github.com/geerlingguy/ansible-for-devops/issues/312
But I'm highlighting here for clarity. In Chapter 3 the listed ad-hoc command
ansible app -b -m pip -a "name=django<4 state=present"
Generates as error as follows:
$ ansible app -b -m pip -a "name=django<4 state=present"
<IP_ADDRESS> | FAILED! => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    },
    "changed": false,
    "msg": "Unable to find any of pip2, pip to use.  pip needs to be installed."
}
<IP_ADDRESS> | FAILED! => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python"
    },
    "changed": false,
    "msg": "Unable to find any of pip2, pip to use.  pip needs to be installed."
}

There are a couple possible workarounds, but I used:
ansible app -b -m pip -a "executable=pip3 name=django<4 state=present"

Thanks for posting this! I'll look into it on my next round of corrections for Ansible for DevOps.

I also used the executable=pip3 to work around this. In addition to that, on the next line you have: to make sure Django is installed and working correctly: ansible app -a "python -m django --version" I had to explicitly use python3 instead of python like this: ansible app -a "python3 -m django --version" otherwise I got the following error:

<IP_ADDRESS> | FAILED | rc=1 >>
/usr/bin/python: No module named djangonon-zero return code
<IP_ADDRESS> | FAILED | rc=1 >>
/usr/bin/python: No module named djangonon-zero return code

ansible app -b -m pip -a "executable=pip3 name=django<4 state=present"

Thanks for this help, Doug.
@geerlingguy, just bought the book (and 2 others of yours today) and I'm enjoying them. Can you update the errata to at least point people to these issues? Also, Centos8 reached EOL so I had to update chapter 3 files from here in github to go back to Centos7. But hey, at least I've made it this far and on a Windows host using WSL to boot.

@robyaggie - I'll be pushing out a book update tonight. Thanks to all for validating this fix, I'll be adding it in.


Need a simpler kmer graph data structure for assembly and error correction

When working with observational data (fastq files) rather than reference data (fasta files), use a simplified kmer graph that only records # of supporting pieces of evidence as an Int rather than recording each piece of evidence (e.g. record identifier, index, orientation) individually

https://github.com/cjprybol/Mycelia/commit/c3fc4cf5d1b7f4ec80143440d82494a83320b405


[BEAM-439] Remove optional args from start/finish bundle methods

@robertwb can you please take a look?
(take II -- I abandoned previous PR due to bad merge on my part)
Technically we do not want to allow deferred side inputs but it is much simple conceptually to remove
extra arguments altogether.

LGTM now

Merged; please manually close PR.


What's the benefit of using this as opposed to stripe.js?

Is there any reason to use the native SDK as opposed to the JS SDK?
Additionally, is this stable enough to be used in production or should I stick to the JS SDK For now?

Stripe blocked my app from using stripe.js because it wasn't executed on a HTTPS host. Which is why I created this plugin. It solved that problem for me since it uses Stripe's native SDKs.
The plugin is stable enough to be used in production. But it only provides functionality to create a credit card token. It doesn't implement other native SDK features such as Apple Pay or Android Wallet support.

Perfect thanks again. That is all I need to know. :-)


Allow Anonymous Status Checks

Fixes: 297

This change enables anonymous access of the /api/status view, if the request is authenticated the response will contain version information as it does currently.  However, if the request is anonymous an empty json response is returned to avoid exposing potentially security-sensitive version information.  Another approach would be to use something like django-health-check.

Just checking, since you also opened #297 - but does this actually meet the requirements you identified in that issue? That wants the API to include information about whether the DB is working properly, for example.
I know there's a need for some sort of unauthenticated health-check API endpoint, and I understand if this is a good starting point for such a thing, but wondering if we should leave #297 open even after this PR is merged, as a feature request for a more comprehensive endpoint such as using django-health-check.

Just checking, since you also opened #297 - but does this actually meet the requirements you identified in that issue? That wants the API to include information about whether the DB is working properly, for example.

I was told it did, however after some testing, I can confirm it does not, I'm closing this PR.


[c++] Refine noexcept specifications

nullable's move constructors and set member function sometimes invoke
new_value, which may perform an allocation that may throw.
value_common's move constructor copies the input Reader, so it needs
to be conditionally noexcept on being able to make a copy.

Closing and re-opening to kick AppVeyor again.

AppVeyor, please build this PR.


Network Policies

The documentation for Network Policies has an indentation error unless I miss the point here. While I was preparing for my CKAD exam I realized that under the --from block for ingress and -to section for egress.
ingress:
  - from:
      - ipBlock:
          cidr: <IP_ADDRESS>/16
          except:
            - <IP_ADDRESS>/24
      - namespaceSelector:
          matchLabels:
            project: myproject
      - podSelector:
          matchLabels:
            role: frontend

egress:
  - to:
      - ipBlock:
          cidr: <IP_ADDRESS>/24
    ports:
      - protocol: TCP
        port: 5978

This is the page - https://kubernetes.io/docs/concepts/services-networking/network-policies/
The file name is service/networking/networkpolicy.yaml

Hi @erdogancel
I tried this one and it is working fine for me, when I applied this yaml it didn't give any error to me.
After that to view it I used: kubectl describe networkpolicy test-network-policy
$ kubectl describe networkpolicy test-network-policy
Name:         test-network-policy
Namespace:    default
Created on:   2022-11-04 14:03:58 +0530 IST
Labels:       <none>
Annotations:  <none>
Spec:
  PodSelector:     role=db
  Allowing ingress traffic:
    To Port: 6379/TCP
    From:
      IPBlock:
        CIDR: <IP_ADDRESS>/16
        Except: <IP_ADDRESS>/24
    From:
      NamespaceSelector: project=myproject
    From:
      PodSelector: role=frontend
  Allowing egress traffic:
    To Port: 5978/TCP
    To:
      IPBlock:
        CIDR: <IP_ADDRESS>/24
        Except:
  Policy Types: Ingress, Egress

I think the docs are correct.

/priority awaiting-more-evidence
/triage not-reproducible
/language en

A similar issue opened for it, see this #35102

We could add comments into the sample manifest or otherwise explain to readers that the page is correct. Unfortunately, it is easy to misunderstand what the API means and how it works.
SIG Docs can have a role in fixing that!

/close
Closing this issue as no more discussion has been done .
Also @erdogancel , you can reopen this issue in case you want to add further evidence .


Compatible with 1.20.5 / 1.20.6

doesn't set lore, background blurs text in gui, added 1.20.5 / 1.20.6 compatibility, you can no longer start your prefix with / Remember to configure this to use java 21 instead of java 17

Sorry, didn't see this pr and already updated


Mixins included in /ancestors, but not /descendants?

here's an example - this query for ancestors of NucleicAcidEntity:
curl -X GET "https://bl-lookup-sri.renci.org/bl/NucleicAcidEntity/ancestors?version=2.1.0" -H  "accept: application/json"

returns ancestors including some mixins, like PhysicalEssence:
[
  "biolink:MolecularEntity",
  "biolink:ChemicalEntity",
  "biolink:NamedThing",
  "biolink:Entity",
  "biolink:GenomicEntity",
  "biolink:ThingWithTaxon",
  "biolink:PhysicalEssence",
  "biolink:PhysicalEssenceOrOccurrent",
  "biolink:OntologyClass",
  "biolink:ChemicalOrDrugOrTreatment",
  "biolink:ChemicalEntityOrGeneOrGeneProduct",
  "biolink:ChemicalEntityOrProteinOrPolypeptide"
]

but a query for descendants of NucleicAcidEntity:
curl -X GET "https://bl-lookup-sri.renci.org/bl/NucleicAcidEntity/descendants?version=2.1.0" -H  "accept: application/json"

does not return any mixins:
[
  "biolink:NucleicAcidEntity",
  "biolink:Transcript",
  "biolink:RNAProduct",
  "biolink:NoncodingRNAProduct",
  "biolink:MicroRNA",
  "biolink:SiRNA",
  "biolink:RNAProductIsoform",
  "biolink:Exon",
  "biolink:CodingSequence"
]

is that how it's supposed to work?
I admit I'm still kind of new to the concept of mixins, so it may just be that my understanding is lacking here. but if they're supposed to be included, I'd think the descendants of NucleicAcidEntity would look something like this?
[
                "biolink:UnclassifiedOntologyClass",
                "biolink:GeneProductIsoformMixin",
                "biolink:CodingSequence",
                "biolink:OntologyClass",
                "biolink:GenomicEntity",
                "biolink:NucleicAcidEntity",
                "biolink:RNAProduct",
                "biolink:Transcript",
                "biolink:Exon",
                "biolink:SiRNA",
                "biolink:RNAProductIsoform",
                "biolink:TaxonomicRank",
                "biolink:PhysicalEssence",
                "biolink:GeneOntologyClass",
                "biolink:GeneProductMixin",
                "biolink:RelationshipType",
                "biolink:MicroRNA",
                "biolink:NoncodingRNAProduct"
            ]

And also return any categories and descendants from 3.   Now, to be clear, I didn't implement this- it's part of Biolink Model Toolkit, but this is my understanding.
I'll go ahead and close this issue, but feel free to reopen if necessary.


[BUG] Issues install with permissions via Kustomize

Describe the bug
I am getting permissions issue with argocd-operator via kustomize on this file kustomization.yaml
Logs:
{"level":"info","ts":1619630631.783934,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"argocd-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1619630631.8853924,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"argocd-controller","source":"kind source: /, Kind="}
E0428 17:23:51.893882       1 reflector.go:178] pkg/mod/k8s.io/client-go@v0.18.2/tools/cache/reflector.go:125: Failed to list *v1.ClusterRoleBinding: clusterrolebindings.rbac.authorization.k8s.io is forbidden: User "system:serviceaccount:argocd:argocd-operator" cannot list resource "clusterrolebindings" in API group "rbac.authorization.k8s.io" at the cluster scope
E0428 17:23:53.186341       1 reflector.go:178] pkg/mod/k8s.io/client-go@v0.18.2/tools/cache/reflector.go:125: Failed to list *v1.ClusterRoleBinding: clusterrolebindings.rbac.authorization.k8s.io is forbidden: User "system:serviceaccount:argocd:argocd-operator" cannot list resource "clusterrolebindings" in API group "rbac.authorization.k8s.io" at the cluster scope
E0428 17:23:56.353828       1 reflector.go:178] pkg/mod/k8s.io/client-go@v0.18.2/tools/cache/reflector.go:125: Failed to list *v1.ClusterRoleBinding: clusterrolebindings.rbac.authorization.k8s.io is forbidden: User "system:serviceaccount:argocd:argocd-operator" cannot list resource "clusterrolebindings" in API group "rbac.authorization.k8s.io" at the cluster scope
E0428 17:23:59.823528       1 reflector.go:178] pkg/mod/k8s.io/client-go@v0.18.2/tools/cache/reflector.go:125: Failed to list *v1.ClusterRoleBinding: clusterrolebindings.rbac.authorization.k8s.io is forbidden: User "system:serviceaccount:argocd:argocd-operator" cannot list resource "clusterrolebindings" in API group "rbac.authorization.k8s.io" at the cluster scope
E0428 17:24:10.046512       1 reflector.go:178] pkg/mod/k8s.io/client-go@v0.18.2/tools/cache/reflector.go:125: Failed to list *v1.ClusterRoleBinding: clusterrolebindings.rbac.authorization.k8s.io is forbidden: User "system:serviceaccount:argocd:argocd-operator" cannot list resource "clusterrolebindings" in API group "rbac.authorization.k8s.io" at the cluster scope
E0428 17:24:23.615903       1 reflector.go:178] pkg/mod/k8s.io/client-go@v0.18.2/tools/cache/reflector.go:125: Failed to list *v1.ClusterRoleBinding: clusterrolebindings.rbac.authorization.k8s.io is forbidden: User "system:serviceaccount:argocd:argocd-operator" cannot list resource "clusterrolebindings" in API group "rbac.authorization.k8s.io" at the cluster scope
E0428 17:25:06.938505       1 reflector.go:178] pkg/mod/k8s.io/client-go@v0.18.2/tools/cache/reflector.go:125: Failed to list *v1.ClusterRoleBinding: clusterrolebindings.rbac.authorization.k8s.io is forbidden: User "system:serviceaccount:argocd:argocd-operator" cannot list resource "clusterrolebindings" in API group "rbac.authorization.k8s.io" at the cluster scope
E0428 17:25:45.991909       1 reflector.go:178] pkg/mod/k8s.io/client-go@v0.18.2/tools/cache/reflector.go:125: Failed to list *v1.ClusterRoleBinding: clusterrolebindings.rbac.authorization.k8s.io is forbidden: User "system:serviceaccount:argocd:argocd-operator" cannot list resource "clusterrolebindings" in API group "rbac.authorization.k8s.io" at the cluster scope
{"level":"info","ts":1619630781.287958,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"argocd-controller","source":"kind source: /, Kind="}
{"level":"info","ts":1619630781.3895748,"logger":"controller-runtime.controller","msg":"Starting EventSource","controller":"argocd-controller","source":"kind source: /, Kind="}

Expected behaviour
We should not see those errors with permission if you are using kustomize install.
I think it is required to add 2 extra lines in the file above as a fix for these permission issues:
- cluster_role.yaml
- cluster_role_binding.yaml

Thank you.


F2 rename folder , all import package path will append the rename folder name in this TS file

Step 1: Select one foler in Source Explore
Step 2: Click "F2" and then press Enter key (don't change folder name )
The ts file will be changed like below.
New (It is error code) , absolute path "@app/page/packageComponent/document-posting/node_modules/" will be appended into import package path.
import * as Enumerable from '@app/page/packageComponent/document-posting/node_modules/linq/linq';
import * as moment from '@app/page/packageComponent/document-posting/node_modules/moment';
Original,
import * as Enumerable from 'linq/linq';
import * as moment from 'moment';
Thanks

Please include your vscode version and if this repos with extensions disabled
/needsMoreInfo

Closing as more info is needed to investigate this


Change cast to unwrap and ParameterizedRowMapper to RowMapper.

If using some sort of pool libraries (like c3p0 or HikariCP) - got ClassCastException, but unwrap always working good.
So, ParameterizedRowMapper is deprecated for now and removed from latest Spring version.
RowMapper is a legal placeholder of ParameterizedRowMapper since Spring 3.0

@Jan-M can you have a look? Or somebody of ACID?

This brings us closer then to get rid of the BoneCP dependency :-)


Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed

I am using docker version 20.10.8 in my macbook pro.
xxxx@WKMZTZQ1E459 mywork % docker -v
Docker version 20.10.8, build 3967b7d
xxxx@WKMZTZQ1E459 mywork %
When running ./minifab up, I am getting the following error:
Run the chaincode install script on cli container ***********
non-zero return code
go: downloading github.com/hyperledger/fabric v1.4.1
go: downloading github.com/spf13/viper v1.7.1
go: downloading github.com/golang/protobuf v1.3.3
go: downloading google.golang.org/grpc v1.31.1
go: downloading github.com/pkg/errors v0.9.1
go: downloading go.uber.org/zap v1.15.0
go: downloading github.com/pelletier/go-toml v1.2.0
go: downloading github.com/spf13/afero v1.1.2
go: downloading github.com/spf13/cast v1.3.0
go: downloading github.com/mitchellh/mapstructure v1.1.2
go: downloading golang.org/x/net v0.0.0-20200822124328-c89045814202
go: downloading gopkg.in/yaml.v2 v2.3.0
go: downloading golang.org/x/crypto v0.0.0-20200820211705-5c72a883971a
go: downloading github.com/op/go-logging v0.0.0-20160315200505-970db520ece7
go: downloading golang.org/x/text v0.3.2
go: finding module for package github.com/miekg/pkcs11
go: downloading go.uber.org/atomic v1.6.0
go: downloading gopkg.in/ini.v1 v1.51.0
go: downloading github.com/subosito/gotenv v1.2.0
go: downloading github.com/grpc-ecosystem/go-grpc-middleware v1.2.1
go: downloading golang.org/x/sys v0.0.0-20200420163511-1957bb5e6d1f
go: downloading github.com/hashicorp/hcl v1.0.0
go: downloading github.com/sykesm/zap-logfmt v0.0.3
go: downloading github.com/spf13/pflag v1.0.3
go: downloading go.uber.org/multierr v1.5.0
go: downloading google.golang.org/genproto v0.0.0-20200423170343-7949de9c1215
go: downloading github.com/fsnotify/fsnotify v1.4.7
go: downloading github.com/spf13/jwalterweatherman v1.0.0
go: downloading github.com/miekg/pkcs11 v1.0.3
go: downloading github.com/magiconair/properties v1.8.1
go: downloading github.com/fsouza/go-dockerclient v1.6.5
go: downloading github.com/hyperledger/fabric-amcl v0.0.0-20200424173818-327c9e2cf77a
go: downloading github.com/docker/docker v1.4.2-0.20191101170500-ac7306503d23
go: downloading github.com/Microsoft/go-winio v0.4.15-0.20200113171025-3fe6c5262873
go: downloading github.com/docker/go-units v0.4.0
go: downloading github.com/docker/go-connections v0.4.0
go: downloading github.com/containerd/continuity v0.0.0-20200228182428-0f16d7a0959c
go: downloading github.com/gogo/protobuf v1.3.1
go: downloading github.com/containerd/containerd v1.3.0
go: downloading github.com/opencontainers/image-spec v1.0.1
go: downloading github.com/opencontainers/runc v0.1.1
go: downloading github.com/sirupsen/logrus v1.4.2
go: downloading github.com/morikuni/aec v1.0.0
go: downloading github.com/Microsoft/hcsshim v0.8.7
go: downloading golang.org/x/sync v0.0.0-20190423024810-112230192c58
go: downloading github.com/Azure/go-ansiterm v0.0.0-20170929234023-d6e3b3328b78
go: downloading github.com/konsorten/go-windows-terminal-sequences v1.0.1
go: downloading github.com/opencontainers/go-digest v1.0.0-rc1
go: downloading github.com/docker/distribution v2.7.1+incompatible
go: found github.com/miekg/pkcs11 in github.com/miekg/pkcs11 v1.0.3
Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: docker build failed: docker image inspection failed: Get "http://unix.sock/images/dev-peer1.org0.example.com-simple_1.0-bb0642f7184041106dc3c495de384d3f4788ada0639be92b561461b35edffb67-7821bed4419d0df065d2627a604d7dae23d96ef012bff2b4115469327f0b87aa/json": dial unix /host/var/run/docker.sock: connect: no such file or directory
STATS *******************************************************
minifab: ok=327	failed=1
Please let me know how to fix this..
@litong01

You need to disable the docker desktop experimental feature. This is known issue. Please search the closed issues on this.

Basically do this
unchecked gRPC FUSE from docker desktop settings
Please close this issue.

Thanks @litong01 , unchecking gRPC FUSE  solved my problem.


runtime: poor error message for Goexit on C-created thread

Go version
tip
Output of go env in your module/workspace:
N/A

What did you do?
// Copyright 2024 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.

package main

/*
#include <pthread.h>

void go_callback();

static void *thr(void *arg) {
    go_callback();
    return 0;
}

static void foo() {
    pthread_t th;
    pthread_attr_t attr;
    pthread_attr_init(&attr);
    pthread_attr_setstacksize(&attr, 256 << 10);
    pthread_create(&th, &attr, thr, 0);
    pthread_join(th, 0);
}
*/
import "C"

import (
        "runtime"
)

//export go_callback
func go_callback() {
        runtime.Goexit()
}

func main() {
        C.foo()
}

What did you see happen?
runtime: mp.lockedInt = 1
fatal error: exited a goroutine internally locked to the OS thread
runtime stack:
runtime.throw({0x4851c4?, 0x600000000?})
        /usr/lib/google-golang/src/runtime/panic.go:1069 +0x48 fp=0x7fe3895c5dd0 sp=0x7fe3895c5da0 pc=0x460028
runtime.gdestroy(0xc000006700)
        /usr/lib/google-golang/src/runtime/proc.go:4324 +0x2a5 fp=0x7fe3895c5e10 sp=0x7fe3895c5dd0 pc=0x43bc85
runtime.goexit0(0xc000006700?)
        /usr/lib/google-golang/src/runtime/proc.go:4278 +0x13 fp=0x7fe3895c5e28 sp=0x7fe3895c5e10 pc=0x43b9b3
runtime.mcall()
        /usr/lib/google-golang/src/runtime/asm_amd64.s:459 +0x4e fp=0x7fe3895c5e40 sp=0x7fe3895c5e28 pc=0x46450e

goroutine 1 gp=0xc0000061c0 m=0 mp=0x4fcf20 [syscall]:
runtime.cgocall(0x46ab00, 0xc000058740)
        /usr/lib/google-golang/src/runtime/cgocall.go:167 +0x4b fp=0xc000058718 sp=0xc0000586e0 pc=0x45d60b
main._Cfunc_foo()
        _cgo_gotypes.go:43 +0x3f fp=0xc000058740 sp=0xc000058718 pc=0x46aa3f
main.main()
        /tmp/c/main.go:38 +0xf fp=0xc000058750 sp=0xc000058740 pc=0x46aa6f
runtime.main()
        /usr/lib/google-golang/src/runtime/proc.go:272 +0x28b fp=0xc0000587e0 sp=0xc000058750 pc=0x4337eb
runtime.goexit({})
        /usr/lib/google-golang/src/runtime/asm_amd64.s:1700 +0x1 fp=0xc0000587e8 sp=0xc0000587e0 pc=0x4664e1

Note that this error was improved a bit recently in https://go.dev/cl/583675. In 1.22, the error is
invalid m->lockedInt = 1
fatal error: internal lockOSThread error

runtime stack:
...

What did you expect to see?
A more clear description of the problem.
The problem here is that it is not valid to call runtime.Goexit in a cgo callback from C to Go on a C-created thread. I think that restriction is fine (it is unclear what Goexit should do if we were to allow it), but the error message here should be more clear.
I think with an additional mp.isextra check in gdestroy we could be more explicit about what the user did wrong.
We should also update the runtime.Goexit docs to mention this case.

cc @golang/runtime

Related Issues

fatal error: exitsyscall: syscall frame is no longer valid #63829 (closed)
runtime: TestCallbackPanic internal lockOSThread error #47382 (closed)
runtime: "fatal error: attempt to execute system stack code on user stack" in startTemplateThread #39098 (closed)
runtime: "runtime: unknown pc" from C abort() #47522 (closed)
runtime/race: sigsegv when using cgo callbacks with the race detector enabled #10874 (closed)
runtime: stoplockedm: inconsistent locking #21306 (closed)
runtime: cgo using programs have a goroutine marked [syscall, locked to thread]; #17384 (closed)
runtime: error on exit of program on darwin fatal error: exitsyscall: syscall frame is no longer valid #42465 (closed)
os/exec:  fatal error: runtime·unlock: lock count #30594 (closed)
testing: Example test with runtime.Goexit hangs #41084 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Reopening.  Change is being reverted.


Kek is such a scammer

Bro literally doesnt give customers dazeer back because they bought with paypal and his paypal got termed smh...
All the image links are here:
https://imagine.skid.group/Fr/x63bwj4h.png
https://imagine.skid.group/Fr/ffjm4sbs.png
https://imagine.skid.group/Fr/vjj4ob7s.png
https://imagine.skid.group/Fr/ei60uhha.png
https://imagine.skid.group/Fr/7rtbrq90.png

Such a scammer!!😡😡

says the guy who rats customers

says the guy who rats customers

proof rn

I had lost a lot of coins in some scam case just like this thanks to the best hacker in the world who helped me recover all my funds,message him on telegram his telegram username is https://t.me/Blackhathacker110


TkMethods returns 404 on unsupported method

TkMethods take returns 404 error if method is not supported.
It would be more logical to return 405: Method Not Allowed here.
new FtRemote(new TkMethods(new TkEmpty(), "PUT")).exec(
    url -> new JdkRequest(url)
        .method("POST")
        .fetch().as(RestResponse.class)
        // expecting 405: Method Not Allowed.
        .assertStatus(HttpURLConnection.HTTP_BAD_METHOD)
);
// java.lang.AssertionError: HTTP response status is not equal to 405: 404 Not Found

@0crat in

@0crat in (here)

@paulodamaso Job #861 is now in scope, role is DEV

Bug was reported, see §29: +15 point(s) just awarded to @g4s8/z

The job #861 assigned to @ypshenychka/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be a monetary reward for this job

@0crat refuse

@0crat refuse (here)

@ypshenychka The user @ypshenychka/z resigned from #861, please stop working. Reason for job resignation: Order was cancelled

Tasks refusal is discouraged, see §6: -15 point(s) just awarded to @ypshenychka/z

@0crat wait for review/merge of #875

@0crat wait for review/merge of #875 (here)

@victornoel The impediment for #861 was registered successfully by @victornoel/z

@g4s8 the PR was merged, can you close the issue? Thanks

@ypshenychka/z please review this job completed by @victornoel/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

The job #861 is now out of scope


Web search 3rd pane crash

After restart I can do 1 web search then every time I tab to the 3rd pane QS crashes
Running El Capitan (started after I updated) and QS version 1.3.1

Console says
2.10.2015 13:55:19,933 com.apple.xpc.launchd[1]: (com.blacktree.Quicksilver.59552[597]) Service exited due to signal: Segmentation fault: 11

Getting the exact same error. I use a websearch for YubNub (setup detailed here: http://www.lifeclever.com/quicksilver-yubnub-rapid-web-searches-and-more/). Sometimes I don't even get the first search before QS crashes. Has been happening since I went to El Capitan betas. Now running full El Capitan 10.11.
Error from console:
10/3/15 12:43:04.852 com.apple.xpc.launchd[1]: (com.blacktree.Quicksilver.95392[3570]) Service exited due to signal: Segmentation fault: 11

I’m not seeing anything like this. Which interface are you using? (If you don’t know, go to Preferences → Appearance)

I'm using Primer, but it happens on all of them.
On Sat, Oct 3, 2015 at 1:42 PM, Rob McBroom<EMAIL_ADDRESS>wrote:

I’m not seeing anything like this. Which interface are you using? (If you don’t know, go to Preferences → Appearance)
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/issues/2111#issuecomment-145276619

I'm using mini. This same error occurs when I try to rename files and do other opperations that make me tab to the 3rd pane. However some triggers that have the 3rd pane empty in text mode work.

Woop. Spoke too soon. Did some testing. The YubNub search I have programmed to a trigger (Command-Shift-Y) crashes on the following interfaces:
Mini
Primer
White Bezel
Window
I've successfully completed multiple searches with no crashes on the following interfaces:
Bezel (built-in)
Bezel Classic
Flashlight
Menu
Mini-Bezel
Nostromo
Same error as the previous:
10/4/15 00:06:49.557 com.apple.xpc.launchd[1]: (com.blacktree.Quicksilver.95392[3866]) Service exited due to signal: Segmentation fault: 11

I can reproduce this in the listed problem interfaces. Can’t say that I know where to start fixing it, though.

Switched interfaces and it works exept when creating triggers then it
crashes.
On Sunday, October 4, 2015, Rob McBroom<EMAIL_ADDRESS>wrote:

I can reproduce this in the listed problem interfaces. Can’t say that I
know where to start fixing it, though.
—
Reply to this email directly or view it on GitHub
https://github.com/quicksilver/Quicksilver/issues/2111#issuecomment-145368652
.

Sounds similar (in terms of the symptoms) to #2045? Does the workaround of moving the Quicksilver window to a non-retina display work for this issue too?

Not sure. My MacBook Pro doesn't have a retina screen, but it is the higher resolution one. Not 1440x900....can't remember the exact dimensions right now.
On Mon, Oct 5, 2015 at 3:46 PM, David Shepherdson
<EMAIL_ADDRESS>wrote:

Sounds similar (in terms of the symptoms) to #2045? Does the workaround of moving the Quicksilver window to a non-retina display work for this issue too?
Reply to this email directly or view it on GitHub:
https://github.com/quicksilver/Quicksilver/issues/2111#issuecomment-145663419

Sounds similar (in terms of the symptoms) to #2045?

The crash log looks very similar. Probably the same issue. And the trigger thing makes sense, since the “command builder” is pretty similar to Primer.

Having experimented some more, this seems to be caused by the interface switching to text-entry mode in any pane. I can reproduce it just by hitting . in the first pane. So hopefully that will get us closer to an answer.

I'm using primer on a retina macbook pro. Crashes.
I use primer on older macbook air (NR). No crash.

I’m going to file a bug with Apple and see where that goes.

If you comment out the two lines that make the text resizable, the crash goes away, but then you can’t see the text as you type. Fun!

Sooo glad I found this! I've been battling this for months! I wish had remembered this group instead of bugging the Twitter account.
Switched from my beloved Primer to Nostromo and my text editing woes appear to be gone!

Apple bug report 23198852.

I think I have the same issue, but on my new 11.6" Macbook Air. Instant crash on going to text mode with Primer. Bezel works fine.
Console: 2015-10-21 8:04:13.354 PM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.oneshot.0x10000012.Quicksilver[1025]) Service exited due to signal: Segmentation fault: 11
Quicksilver 1.3.2 (4014)
OSX 10.11 and 10.11.1

Switching from primer interface to bezel seems to fix the crashing issue for now as molachai stated. Looking forward to that fix :)

This was fixed in 1.3.3