rkt push

rkt push was promised at v 1.0 announcement
currently it is not on the road map or any milestones
https://github.com/coreos/rkt/milestones
https://github.com/coreos/rkt/blob/master/ROADMAP.md
please put rkt push on the map along with acserver

Thanks for the report, I think the details here are still a bit too fuzzy on the spec side.
Did you have a look at acpush and the related spec discussion?

@lucab thanks for getting back. is acpush supposed to work with quay.io now?

@Andrei-Pozolotin acpush is on hold at the moment in favour of the work going on in the OCI Image Specification - we're hopeful that an end-to-end story for rkt pushing images will emerge out of that.

@jonboulle thanks. then: can you please comment on  your plans for rkt support of aci,
i.e. how long projects such as dgr will continue to be viable?

@Andrei-Pozolotin we will certainly continue to support ACI for the foreseeable future - backwards compatibility is paramount (for now it's used by rkt as its internal format anyway). As of today there is still work happening in ACI to fulfil needs that aren't being met elsewhere - we just expect that new development effort will start to focus around OCI instead as that format gains traction and becomes stable.

@jonboulle great, good to know. at first sight (quick attempt to switch away from docker) it surely looked like oci was a clever misdirect designed to delay rkt acceptance :-)

proposed to merge into rkt build
https://github.com/coreos/rkt/issues/2949


Use all CPUs when building from source

Cut down time it takes to build PHP from source by number of CPUs :smile:.

Thanks

Hi will you release it soon?


Bower support?

Love the project! Could you add bower support.
Thanks,

I will look at getting this added in the next few days :)


Cannot register agent in HA mode with Rancher v1.0.0

Rancher	v1.0.0
Cattle	v0.159.2
User Interface	v0.100.3
Rancher Compose	v0.7.3
Trying to add a host to a default cattle environment, it just restarts indefinitely.
The only error I can see is this one: 2016-03-30 16:44:59,686 ERROR root [140088540576816] [_logging.py:54] error from callback <function on_error at 0x7f68e759da28>: Received websocket error: [Handshake status 400]
Websocket proxy is up and running, it is a whole new cluster (for testing purpose actually), and this error remains the same even if the websocket-proxy is not running.
The whole docker logs (this logs are printed indefinitely, as the agent can not register):
INFO: Starting agent for AA94549D254158D9AD6F
INFO: Access Key: AA94549D254158D9AD6F
INFO: Config URL: http://<IP_ADDRESS>/v1
INFO: Storage URL: http://<IP_ADDRESS>/v1
INFO: API URL: http://<IP_ADDRESS>/v1
INFO: IP: <IP_ADDRESS>
INFO: Port:
INFO: Required Image: rancher/agent:v0.11.0
INFO: Current Image: rancher/agent:v0.11.0
INFO: Using image rancher/agent:v0.11.0
INFO: Downloading agent http://<IP_ADDRESS>/v1/configcontent/configscripts
INFO: Updating configscripts
INFO: Downloading http://<IP_ADDRESS>/v1//configcontent//configscripts current=
INFO: Running /var/lib/cattle/download/configscripts/configscripts-1-f0f3fb2e1110b5ada7c441705981f93a480313a324294321cff467f0c3e12319/apply.sh
INFO: Sending configscripts applied 1-f0f3fb2e1110b5ada7c441705981f93a480313a324294321cff467f0c3e12319
INFO: Updating pyagent
INFO: Downloading http://<IP_ADDRESS>/v1//configcontent//pyagent current=
INFO: Running /var/lib/cattle/download/pyagent/pyagent-1-9e3dcab12585149a65d818082279708965cd826df1937a55b24f48428f8f0c0673b9f37ae03c16234efdd22657d02b33/apply.sh
INFO: Updating host-api
INFO: Downloading http://<IP_ADDRESS>/v1//configcontent//host-api current=1-076f245550ef0d977e9dcfe411ef2faebde6b6277c93a3a02a17e69ef6c42c85
INFO: Already up to date
INFO: Sending host-api applied 1-076f245550ef0d977e9dcfe411ef2faebde6b6277c93a3a02a17e69ef6c42c85
INFO: Updating agent-binaries
INFO: Downloading http://<IP_ADDRESS>/v1//configcontent//agent-binaries current=1-4200f9b686342da8e941359211b1d8c5f98877ae293d0ead231d43507f1c9eae
INFO: Already up to date
INFO: Sending agent-binaries applied 1-4200f9b686342da8e941359211b1d8c5f98877ae293d0ead231d43507f1c9eae
INFO: Updating python-agent
INFO: Downloading http://<IP_ADDRESS>/v1//configcontent//python-agent current=1-a91ca3edd3ab1b58766de4c4206feefa9123274d9b7b999ab48766ca58609528
INFO: Already up to date
INFO: Sending python-agent applied 1-a91ca3edd3ab1b58766de4c4206feefa9123274d9b7b999ab48766ca58609528
INFO: Updating cadvisor
INFO: Downloading http://<IP_ADDRESS>/v1//configcontent//cadvisor current=1-21c3283c2bb12833be339f90a0c9a64d933464e475045636b8a43412ad630347
INFO: Already up to date
INFO: Sending cadvisor applied 1-21c3283c2bb12833be339f90a0c9a64d933464e475045636b8a43412ad630347
INFO: Sending pyagent applied 1-9e3dcab12585149a65d818082279708965cd826df1937a55b24f48428f8f0c0673b9f37ae03c16234efdd22657d02b33
INFO: Starting agent /var/lib/cattle/pyagent/apply.sh
INFO: Executing /var/lib/cattle/pyagent/main.py
INFO: Updating host-config
INFO: Downloading http://<IP_ADDRESS>/v1//configcontent//host-config current=host-config-1-371b266ecf109c459e5dfbb769f39ad299ec61522390d1639815b5d535d38249
INFO: Already up to date
INFO: Sending host-config applied 1-371b266ecf109c459e5dfbb769f39ad299ec61522390d1639815b5d535d38249
2016-03-30 16:44:59,686 ERROR root [140088540576816] [_logging.py:54] error from callback <function on_error at 0x7f68e759da28>: Received websocket error: [Handshake status 400]
time="2016-03-30T16:44:59Z" level="info" msg="Starting event router."
time="2016-03-30T16:44:59Z" level="info" msg="Watching state directory: /var/lib/rancher/state/containers"
time="2016-03-30T16:44:59Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"5e510ba9533ef9621a2de929bfc38c31a0b73f9d129fa876e7672b067805781e\", From:\"-simulated-\", Time:0}"
Monitoring mount context of PID 3318
time="2016-03-30T16:44:59Z" level="info" msg="Host not registered yet. Sleeping 1 second and trying again." Attempt=0 reportedUuid="96e84e7f-4c45-4f43-bf60-2c811408afcd"
I0330 16:44:59.765186    6812 storagedriver.go:45] Caching stats in memory for 2m0s
I0330 16:44:59.765351    6812 manager.go:168] cAdvisor running in container: "/docker/5e510ba9533ef9621a2de929bfc38c31a0b73f9d129fa876e7672b067805781e"
I0330 16:44:59.892575    6812 fs.go:109] Filesystem partitions: map[/dev/disk/by-uuid/f8d7dbed-bbe2-466c-a50f-a6a728ac2b15:{mountpoint:/ major:8 minor:1 fsType: blockSize:0}]
I0330 16:44:59.896015    6812 manager.go:205] Machine: {NumCores:1 CpuFrequency:2600000 MemoryCapacity:3880513536 MachineID:1d8c0fe54cdc30954896d68756e722ae SystemUUID:75CF3E35-ECD9-8D5F-1B8F-11489BF02876 BootID:166fffa5-1d4c-4380-ad06-9d6a8cf3a545 Filesystems:[{Device:/dev/disk/by-uuid/f8d7dbed-bbe2-466c-a50f-a6a728ac2b15 Capacity:26387738624 Type:vfs Inodes:1638400}] DiskMap:map[8:0:{Name:sda Major:8 Minor:0 Size:26843545600 Scheduler:noop}] NetworkDevices:[{Name:eth0 MacAddress:42:01:0a:84:00:05 Speed:0 Mtu:1460}] Topology:[{Id:0 Memory:3880513536 Cores:[{Id:0 Threads:[0] Caches:[{Size:32768 Type:Data Level:1} {Size:32768 Type:Instruction Level:1} {Size:262144 Type:Unified Level:2}]}] Caches:[{Size:20971520 Type:Unified Level:3}]}] CloudProvider:GCE InstanceType:n1-standard-1 InstanceID:8304563495402384072}
I0330 16:44:59.911848    6812 manager.go:211] Version: {KernelVersion:3.19.0-56-generic ContainerOsVersion:Ubuntu 14.04.4 LTS DockerVersion:1.10.3 CadvisorVersion:0.22.0 CadvisorRevision:}
I0330 16:45:00.038204    6812 factory.go:233] Registering Docker factory
I0330 16:45:00.038712    6812 factory.go:97] Registering Raw factory
I0330 16:45:00.188858    6812 manager.go:1039] Started watching for new ooms in manager
I0330 16:45:00.188887    6812 oomparser.go:198] OOM parser using kernel log file: "/var/log/kern.log"
I0330 16:45:00.189495    6812 manager.go:292] Starting recovery of all containers
I0330 16:45:00.198329    6812 manager.go:297] Recovery completed
I0330 16:45:00.200242    6812 cadvisor.go:106] Starting cAdvisor version: 0.22.0- on port 9344
time="2016-03-30T16:45:00Z" level="info" msg="Host not registered yet. Sleeping 1 second and trying again."  Would you be willing to wait to try that out? We shared how it will look in our latest meetup (today) that should be on our website in the next couple of days.

Ok that is fine, thank you. Too bad I could not attend the meetup!

As soon as v1.0.1 ships, the docs link will be updated and provided. If you follow our announcements category in our Forums, you will receive a note about the latest release and the link to the docs will be in those release notes.  We are still testing out our RC candidates for v1.01.


PCA don't return Axes

https://github.com/theislab/scanpy/blob/8d9eec4c4763edb4a522dbec3fa5ea48832ff0f8/scanpy/plotting/_tools/__init__.py#L139
Cant use mpl axis after pca_variance_ratio and other PCA plots in my code, because they never returns from function

@djbios you should be able to work around this by getting the current figures via plt.gca() (get current axis) and plt.gcf() (get current figure).
@fidelram, how should we handle this?
The documentation suggests that these functions will return Axes, though many of them don't operate on single Axes and instead have GridSpecs/ Figures.
Could we do a pass over all plotting functions and normalize the behaviour for these arguments?

@djbios you should be able to work around this by getting the current figures via plt.gca() (get current axis) and plt.gcf() (get current figure).
@fidelram, how should we handle this?
The documentation suggests that these functions will return Axes, though many of them don't operate on single Axes and instead have GridSpecs/ Figures.
Could we do a pass over all plotting functions and normalize the behaviour for these arguments?

Thanks, thats works


Updating known issues

OPS Build status updates of commit 74f9cdb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/hololens-known-issues.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Change the type of the keys

Now, the keys can be either a str, or a tuple (str, type) when the type of the value needs to be specified. This ambiguity needs to be handled in multiple places in the package.
To fix this, introduce an abstract class Key with abstract methods __str__, __hash__, __eq__. The value returned by __str__ is used to access the value in the nested dict. The methods __hash__ and __eq__ allow the keys to be stored in a set.
Implement the the abstract class Key in a class Typed which stores the type information inside the key. Make PydanticFabric require the keys to be Typed.

The class Key must also implement a method .match(self, other) which returns True if the set of accepted values of self is a subset of the set of accepted values of other.


noise is just a pattern now

see https://sketchplugins.com/d/1331-setting-a-shapeobject-to-the-new-noise-property-will-crash-sketch

Warnings

:warning:

Source/dom/style/Fill.js changed, but not:

📚 its docs

That's OK as long as you're refactoring.

:warning:

Source/dom/style/Style.js changed, but not:

🧪 its tests

That's OK as long as you're refactoring.

  Generated by :no_entry_sign: dangerJS


UX design for conditional mapping

We need an UXD help to achieve #848.
The points I have seen so far are:

A widget to write a math formula expression at the Sources pane. Auto completion is also requested, maybe add fields by clicking it in the tree. We might not want to show its full path (e.g. SomeOrderDocument:/Order/Item/name) in the formula because it's always too long.
Highlight fields those are involved in conditional mapping, in a different way. @pleacu suggested to have a green background in contrast to a blue one for regular mapping.

@dongniwang could we get some help from your team?

@igarashitm thanks Tomo! I see you marked this for 7.4, let me take a look at the requirement with @amysueg, @gaughan and @heiko-braun, and I'll get back to you!

Latest POC update:

We got a +1 on our prototype from UXD team, let's continue with what we have and raise separate UXD issues once we hit concrete one.


About the parameters of the round "Cold Night"

The round type parameter returned at the start of a “cold night” is probably set to 0.
The round name is also listed as “Intermission” in the Save Manager.
Please check if you would like to confirm this.
「ラウンドタイプ : 休憩時間」=「Round Type : Intermission」

Seems like the name for Cold Night changed to コールドナイト internally for JP. I might be able to fix this next update.

Thank you for your reply.
I would appreciate it if you could also check the parameters just to be sure, as the “ToN_RoundType” value seemed to be 0 when I checked it on the OSC debugging board.

I would need a log file with a Cold Night round encounter to properly test this out.

I encountered this about 3 hours ago and can provide the log file.
How do I give it to you?

You can join the discord found in the README.md of this repo, then you can message me directly on there.

I joined the dicord server.
Is it OK if I send you the text file of the log by DM?

Yeah, DMs are okay.

Feel free to open this issue again if this problem still persists.


feat: add temporary MAS architecture diagram for the catalog tile

Description
A placeholder architecture diagram to use for the pre-release MAS catalog tile.

Updated the url in catalog json in latest commit.

/pipeline run

/run pipeline

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


route: improve route entry for matcher

Commit Message: route: improve route entry for matcher

support dynamic clusters for matcher
run route callback after route match for matcher

Additional Description:
There are 2 problems in RouteAction and RouteList of matcher:

After route matches, the route in the config will be returned directly. But we should return the result of matches. Otherwise, the dynamic cluster(like cluster header) won't work.
They doesn't handle the route callback logic.
(I hit the first problem, but found the second when I fixes the first)

Without the fix, the tests will fail:
[ RUN      ] RouteMatcherTest.TestMatchTreeDynamicCluster
external/envoy/test/common/router/config_impl_test.cc:1430: Failure
Expected equality of these values:
  "www2"
  route->clusterName()
    Which is: ""

[ RUN      ] RouteMatcherTest.TestRouteListDynamicCluster
external/envoy/test/common/router/config_impl_test.cc:1585: Failure
Expected equality of these values:
  "www2"
  route->clusterName()
    Which is: ""

[ RUN      ] RouteMatchOverrideTest.RouteListVerifyRouteOverrideStops
external/envoy/test/common/router/config_impl_test.cc:10748: Failure
Expected equality of these values:
  accepted_route->routeEntry()->clusterName()
    Which is: "foo_bar"
  "foo"

Risk Level: Low
Testing: unit tests
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/assign-from @envoyproxy/first-pass-reviewers

Thanks! Conflicts resolved.

/retest


Write a Ruby program to convert miles to inches

Description
Write a Ruby program to convert miles to inches
1 mile = 63360 inches
Input  : 5
Output : 316800

How to contribute

Save the solution in program/ConvertMilesToInches.rb file
Add ConvertMilesToInches.rb file in convert-miles-to-inches folder

!asign

!assign


Subscriber example

Can you provide an example of using the subscriber option?  I'm not clear on how to do that from the documentation.

It's just the function that connects the plugin with the store's mutations;
store => handler => store.subscribe(handler)

See https://vuex.vuejs.org/api/#subscribe for more information.


Cannot install Material UI stable

I get this error:
>npm i @material-ui/core
npm ERR! code EINVALIDPACKAGENAME
npm ERR! Invalid package name "@@material-ui/core/core": name can only contain URL-friendly characters

I had to delete package-lock.json to fix the issue.


"running" is never set to "false"

The only method setting "running" variable to "false" (after "render()" sets it to "true") is "abort()"; I think render() should set running to false once finished.

I did this: call gif.abort() in the callback function of gif.on("finished") and then running is reset to false

To properly launch multiple time the gif rendering without issues, I had to do the following:
gif.abort();  gif.frames = [];  delete gif.imageParts;  delete gif.finishedFrames;  delete gif.nextFrame;

Yes, I found that there would be problems when rendering a new gif after calling gif.abort(), so I replaced gif.abort() with
// ...
gif.running = false;
gif.frames = [];
// ...


Improved time parsing

This addresses https://github.com/simonpoole/OpeningHoursParser/issues/50
The changes seem to have no real negative effect out side of being substantially more tolerant of whitespace in the time specifications and one clear regression parsing 24.7 as hours:minutes which needs to be addressed.
Tests are currently expected to fail because of the differences.
diff.txt
diff-strict.txt
Format: original result - new result - input string
As the tests typically generated a parse exception before, the original result is typically a "1".

https://github.com/simonpoole/OpeningHoursParser/pull/54/commits/083f7c8d35dec9c1fed63d3aa5e1b23c53c07398 reduces the differences in strict mode to 103:
diff-strict.txt

https://github.com/simonpoole/OpeningHoursParser/pull/54/commits/083f7c8d35dec9c1fed63d3aa5e1b23c53c07398 reduces the differences in strict mode to 103:
diff-strict.txt


HM-Sec-Key "Entriegeln" / "Verriegeln" reversed

custom_component/hahomematic version (if applicable):
0.37.7
CCU version:

Model (CCU2/3, Raspi3/4, NUC, ProxmoxVE, ...):
OS (Original, RaspberryMatic, debmatic/...):
Version: <IP_ADDRESS>20226

HM-SEC-Key shows the correct status in Home Assistant but the actions "Lock" / "Unlock" are reversed.
Example: Device is unlocked, Lovelace status icon shows an open lock, the shortcut states "Verriegeln", everything correct.
If you click on "Verriegeln", the device confirms with two short beeps, so obvious it is receiving the command "Entriegeln".
If you send the "Entriegeln" command to the unit, the motor starts and locks the device.
Please let me know if you need a system log or more info.

Thanks for reporting.
@danielperna84 you have this device too. Please confirm.

I can confirm. Visually it's looking correct, but the actions are inverted.

Please retest with 0.38.1

Work now as expected, many thanks!

Thanks for feedback


Please Fix This!

 Please fix the new update dialog window.

@mkoryak There's no reason to be a prick.
@cyian-1756

Agreed, being a prick is ridiculous!

Agreed, being a prick is ridiculous!

So by your logic: no one is allowed to bring up a problem, and must fix it themselves.

No, it's all in the tone.
On Sat, Dec 8, 2018, 1:00 AM Jouni Järvinen<EMAIL_ADDRESS>wrote:

Agreed, being a prick is ridiculous!
So by your logic: no one is allowed to bring up a problem, and must fix
it themselves.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RipMeApp/ripme/issues/1026#issuecomment-445434269,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXbSW9q89_6oe53PZjBV3pInKdsu47Wks5u21VkgaJpZM4X-GrP
.

Yeah. For example, start with giving your issue a proper title.

@Tush-r Testing out your changes they work fine, make a PR and I'll merge it in


Enhance shenyu-plugin-grpc module unit test.

issues: #1460
Enhance shenyu-plugin-grpc module unit test
include：
client
context
proto
resolver
response

Codecov Report

Merging #1516 (00111d0) into master (1c48831) will decrease coverage by 0.72%.
The diff coverage is n/a.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1c48831...00111d0. Read the comment docs.


READONLY and READWRITE commands are not supported

Can I attempt to Implement this?

Hello @theodesp - sure, please free to do so.


Add code style checkers to Crawler

Add code style checkers pmd, checkstyle, findbugs to Crawler. And refactoring code to pass

@vaa25 where is PR?

@AndriyBaibak 4hours


How run test for mac (intel) ?

Describe the bug / error
$> go test ./...

src/internal/goarch/goarch_wasm.go:8:2: _ArchFamily redeclared in this block
src/internal/goarch/goarch_amd64.go:8:2: other declaration of _ArchFamily
src/internal/goarch/goarch_wasm.go:9:2: _DefaultPhysPageSize redeclared in this block
src/internal/goarch/goarch_amd64.go:9:2: other declaration of _DefaultPhysPageSize
...

What is the SDK version?
v0.23.0
What is your TinyGo version?
tinygo version 0.31.2 darwin/amd64 (using go version go1.22.2 and LLVM version 17.0.1)

That's a question about TinyGo, and don't belong here


Access model_fields on the model class

In V3, the instance attribute access will not work anymore.

Thanks!


processContent: placeholder like <%= pkg.version %> is not replaced

Maybe I do something wrong. I tried to replace a custom string by my path to a javascript file.
processContent: function(content, filename) {
content = content.replace(/(${jquery_path})/gmi, '<%= pkg.version %>');
return content;
}
Output:

Any ideas?
Thank you!

https://github.com/gruntjs/grunt-contrib-jade/issues/106#issuecomment-49046102


I'm using the caching system of nitro, which use the redis driver. If my redis connection fails, is there a way to make defineCachedEventHandler not report an error and not use the cache?

Describe the feature
defineCachedEventHandler works normally
Additional information

[ ] Would you be willing to help implement this feature?

I was looking into this myself and was wondering if there is a way to skip cache if the driver gives an error.  Happy to help impelmenting this if somebody would point me in the right direction.

I was looking into this myself and was wondering if there is a way to skip cache if the driver gives an error.  Happy to help impelmenting this if somebody would point me in the right direction.

This seems like quite an important issue, I'm surprised it hasn't got any love! I would also expect that should the caching mechanism fail it should fall back to calling the function and logging the error

For a reproduction you can use the starter app and adjust the config:
// https://nitro.unjs.io/config
export default defineNitroConfig({
  srcDir: "server",
  storage: {
    redis: {
      driver: "redis",
      url: "redis://localhost:6379",
      maxRetriesPerRequest: 3, // give up sooner and return an error
    },
  },
  routeRules: {
    "/**": { cache: { maxAge: 60 * 60, base: "redis" } },
  },
});

@pi0 I think this can be marked as fixed


Broken link

Using with Scala/SBT

    Add the Snowplow maven repository as a resolver: "Snowplow Analytics Maven repo" at "http://maven.snplow.com/releases/"
    Check for the newest version <- ===>>>this one <===============
    Add this the relevant version of the schema you want as a dependency: "com.snowplowanalytics" % "collector-payload1" % "0.2.0"

It returns something like
404 Not Found

    Code: NoSuchKey
    Message: The specified key does not exist.
    Key: releases/com/snowplowanalytics/snowplow-thrift-raw-event/index.html

@alexanderdean  - Updated the page on my local fork

Thanks @ihortom !

Hey @ihortom - can you cherry-pick this into a branch in snowplow/snowplow (rather than your own fork)?


Multiple issues after 1.5.0

Describe the bug
Having the following issues with the container:

Cron Jobs not functioning
Server no longer prompts for password when connecting
Getting the following repeating message in the log:

cli: config: parse file: yaml: line 1: did not find expected key
cli: config: parse file: yaml: line 1: did not find expected key
To Reproduce
Steps to reproduce the behavior:
I am using the following environment variables:
  environment:
     - PUID=1000
     - PGID=1000
     - PORT=8211 # Optional but recommended
     - PLAYERS=4 # Optional but recommended
     - SERVER_PASSWORD="XXXX" # Optional but recommended
     - MULTITHREADING=true
     - RCON_ENABLED=true
     - RCON_PORT=25575
     - TZ=UTC
     - ADMIN_PASSWORD="XXXX"
     - COMMUNITY=false  # Enable this if you want your server to show up in the community servers tab, USE WITH SERVER_PASSWORD!
     - SERVER_NAME="XXXX"
     - BACKUP_ENABLED=true
     - BACKUP_CRON_EXPRESSION=0 3 * * 3,7
     - OLD_BACKUP_DAYS=30
     - DELETE_OLD_BACKUPS=true
     - AUTO_UPDATE_ENABLED=true
     - AUTO_UPDATE_CRON_EXPRESSION=0 6 * * *
     - AUTO_UPDATE_WARN_MINUTES=5
     - AUTO_REBOOT_ENABLED=true
     - AUTO_REBOOT_WARN_MINUTES=5
     - AUTO_REBOOT_EVEN_IF_PLAYERS_ONLINE=true
     - AUTO_REBOOT_CRON_EXPRESSION=0 12 * * *
     - DISCORD_WEBHOOK_URL=https://discord.com/api/webhooks/XXXX
     - DEATH_PENALTY=None
     - ENABLE_NON_LOGIN_PENALTY=false

Expected behavior
Server should prompt for a password when connecting.
Server should reboot/update/backup according to cron

Please use server Password and admin password without the quotations if you are using KEY=VALUE.
You can use quotations but you have to use the new way of setting variables as shown in the docker-compose.yml https://github.com/thijsvanloef/palworld-server-docker/blob/main/docker-compose.yml

Also just noticed that you use a comma in your cron expression, this has not been tested and may not work according to https://crontab.guru/#0_3___3,7

Apparently I need to go back to cron school, the cron should be 0 3 * * 3,0  (days are 0-6 not 1-7)
Removing the quotes fixed the password, which was strange because it did work before...
Thanks! :octocat:


Make using runtime activity unnecessary for complex numbers

As discussed with @wsmoses.
  Expression: ≈(collect(Enzyme.gradient(Enzyme.Forward, f, x)), finitediff, rtol = rtol, atol = atol)
  Enzyme execution failed.
  Mismatched activity for:   ret [2 x double] [double 0.000000e+00, double 1.000000e+00], !dbg !19 const val: [2 x double] [double 0.000000e+00, double 1.000000e+00]
  Type tree: {}
   llvalue=double 0.000000e+00
  You may be using a constant variable as temporary storage for active memory (https://enzyme.mit.edu/julia/stable/faq/#Activity-of-temporary-storage). If not, please open an issue, and either rewrite this variable to not be conditionally active or use Enzyme.API.runtimeActivity!(true) as a workaround for now

Fixed by JLL bump

MWE that used to provoke this:
module MWE

using FiniteDifferences
using Enzyme

#Enzyme.API.runtimeActivity!(true)

struct G{T}
    this_field_does_nothing::T
    b::T
end

G() = G{Float64}(0.0, 1.0)

function f(vec)
    x = vec[1]
    empty = []
    d = G(empty...)
    return x ≤ d.b ? x * d.b : zero(x)
end

vec = [0.5]

finitediff = FiniteDifferences.grad(central_fdm(5, 1), f, vec)[1]
reverse_grad = Enzyme.gradient(Enzyme.Reverse, f, vec)
forward_grad = Enzyme.gradient(Enzyme.Forward, f, vec)
@show finitediff
@show reverse_grad
@show forward_grad

end


Add seed modification possibility

UCP patcher now creates a gameseeds folder in the SHC root direction in which match seeds will be stored.
There are 2 options in this mod:

the gameseeds/live file is read and the seed will be used in every match (if found).
the game saves seeds in the gameseeds folder at the start of every match. These seed files are only created if the gameseeds/live file is not found, the filenames are the seed names (a random number) and their content is the same number.

Game created seed file:

Its content:

Test build:
https://we.tl/t-CJetMYnwu7

testing the patcher:

the top option sets two suboptions. Please make them radioboxes, so only one can be set  at a time! (setting both makes no sense...)
there is no obvious description about how this 'live' file should look like, nor which kind of format it should have (maybe make the description a bit more verbose on how the seed is a document without any file ending, or we could provide a sample file with the release?)
also make the description maybe more verbose on what the seed does like:

The seed is used to generate random numbers throughout the game, leading to the same game everytime, if the settings and input isn't changed.
other than that works great!!
I might do the description stuff tomorrow, but the boxes should be fixed hopefully!

-Enable Game Seed
Setting the Game seed will allow AI-only games to play out the same way if the same map settings are used.
For player-AI games, it will ensure the same start conditions in the map (AIV selection for example)
To set the game seed, enable this option and create a file called 'live' with a 6 digit number in the game install/gameseeds directory.
--Save game seeds
This option will save the seed from games that do not have a live seed set, so you can rename them to 'live' in order to recreate the match afterwards.
prefered behavior: have only one box with one suboption box, main box tick means same as now first suboption ticked. subbox ticked, means save enabled.

Currently, both the host and the client need to have this patch installed and the same seed set to make it work in multiplayer.
Normally, in multiplayer, the seed is shared after it is generated based on the current computer time before the game is launched.
I suggest as an improvement to hijack the function at 0x0046a740 (which sets the time based seed).
This will probably make it work in multiplayer too.

Currently, both the host and the client need to have this patch installed and the same seed set to make it work in multiplayer.
Normally, in multiplayer, the seed is shared after it is generated based on the current computer time before the game is launched.
I suggest as an improvement to hijack the function at 0x0046a740 (which sets the time based seed).
This will probably make it work in multiplayer too.

Conversation from Discord for this change:
[23:22] Krarilotus: i now changed the description for the seed change option to GRhin's suggestion, however, while testing this more and more, i noticed, that you need to restart the game to ensure to get exactly the same game every time. Which is still better than nothing, like i would still want this option anyways, but it concerns me, that we might have missed something with the random number generator in the game.
Any ideas how we could fix this?
@gynt i know you were also working with this seed change, did you notice soemthing similar? And if so, how did you circumvent this, like do you have any idea how we could get this working without a game restart?
[23:40] Heroesflorian: Phrased differently: Without restarting the game, when re-running a single skirmish match a couple times, the match and endscreen statistics differ in each subsequent run.
But when then restarting the game and doing the same again, that will result in the same sequence of matches / endscreen statistics being generated as for the previous game session.
[23:42] Heroesflorian: So it seems the match seed / match RNG is derived from a seed that is set when starting the game (not match) and does not get reset after a match.
[23:43] Heroesflorian: Oh, and... @Krarilotus were SHC and SHC-E differing with same seed or not?
[23:44] Krarilotus: yes
[23:44] Krarilotus: SHC and SHC-E produced different games with the same seed


This keeps crashing my game, anybody know what it means?

Describe your problem here.
Whenever i try and load into accelerant, it says
Conductor.hx (line 117)
PlayState.hx (line 381)
flixel/FlxGame.hx (line 637)
flixel/FlxGame.hx (line 724)
flixel/FlxGame.hx (line 677)
flixel/FlxGame.hx (line 551)
openfl/events/EventDispatcher.hx (line 402)
openfl/display/DisplayObject.hx (line 1399)
Uncaught Error: Null Object Reference
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.


 For instance, the light client spec has the CSV file 001bmc-apalache.csv that captures the experiments with apalache. We could run them with a timeout of 5 min for each experiment.

I'll assign this to myself, just so I can track these issues. Don't mean to stop anyone else working on it if they're inclined :)


Self referencing schema causing an error

This particular piece of self referencing and reflects the actual API response.
Context

components:
  schemas:
    content:
      type: object
      properties:
        text:
          type: string
          description: Text content
        type:
          type: string
          description: Content type (e.g. text, link, image)
        metadata:
          type: object
          description: Content metadata (e.g. href, src, alt)
        children:
          type: array
          description: sub-content
          items:
            $ref: '#/components/schemas/content'

Current Behavior

{
    "type": "https://stoplight.io/prism/errors#UNKNOWN",
    "title": "Error: Prop not found: paths (#/paths/~1coreapi~1recent-news~1v1~1search/get/responses/200/content/application~1json; charset=utf-8/schema/allOf/1/properties/articles/items/properties/body/items)\n    at Object.getLocalRef (/home/node/app/node_modules/json-schema-faker/dist/main.cjs.js:932:17)\n    at recursiveUtil.resolveSchema (/home/node/app/node_modules/json-schema-faker/dist/main.cjs.js:2252:25)\n    at traverse (/home/node/app/node_modules/json-schema-faker/dist/main.cjs.js:2079:16)\n    at Object.arrayType [as array] (/home/node/app/node_modules/json-schema-faker/dist/main.cjs.js:1567:25)\n    at traverse (/home/node/app/node_modules/json-schema-faker/dist/main.cjs.js:2155:44)\n    at /home/node/app/node_modules/json-schema-faker/dist/main.cjs.js:2188:52\n    at Array.forEach (<anonymous>)\n    at traverse (/home/node/app/node_modules/json-schema-faker/dist/main.cjs.js:2184:27)\n    at Object.objectType [as object] (/home/node/app/node_modules/json-schema-faker/dist/main.cjs.js:1851:14)\n    at traverse (/home/node/app/node_modules/json-schema-faker/dist/main.cjs.js:2155:44) in /properties/articles/items/0/properties/body/items/0/properties/children",
    "status": 500,
    "detail": ""
}

Expected Behavior

Expect prism to create the mock request and response here
Possible Workaround/Solution

Steps to Reproduce

Create a self referencing component
Run prism mock server on the spec
Hit the api with the expected schema on it
Witness the response like below

Environment

Version used:
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop or mobile):
Link to your environment/workspace/project:

Hey team! Please add your planning poker estimate with ZenHub @brendarearden @chohmann @EdVinyard @fcasad

Doc todo: Add information about the maximum depth that prism will analyze recursively.

hey @brian-geoghegan - i just added a couple tests in #2086 to cover this case using your sample (assuming oas 3.x). they passed locally for me. can you review these to see if they fit your use case?

I think this is the same issue but I'm not totally sure.
We get this traceback:
[1:16:12 PM] › [HTTP SERVER] post /recursion/shared/responses/mutual-a ✖  error     Request terminated with error: Error: Error: Prop not found: __bundled__ (#/__bundled__/schema)
    at Object.getLocalRef (/Users/ralex/code/stainless/node_modules/json-schema-faker/dist/main.cjs.js:932:17)
    at Object.recursiveUtil.resolveSchema (/Users/ralex/code/stainless/node_modules/json-schema-faker/dist/main.cjs.js:2252:25)
    at /Users/ralex/code/stainless/node_modules/json-schema-faker/dist/main.cjs.js:2307:39
    at Array.forEach (<anonymous>)
    at recursiveUtil.resolveSchema (/Users/ralex/code/stainless/node_modules/json-schema-faker/dist/main.cjs.js:2305:26)
    at traverse (/Users/ralex/code/stainless/node_modules/json-schema-faker/dist/main.cjs.js:2079:16)
    at Object.objectType [as object] (/Users/ralex/code/stainless/node_modules/json-schema-faker/dist/main.cjs.js:1851:14)
    at traverse (/Users/ralex/code/stainless/node_modules/json-schema-faker/dist/main.cjs.js:2155:44)
    at /Users/ralex/code/stainless/node_modules/json-schema-faker/dist/main.cjs.js:2188:52
    at Array.forEach (<anonymous>) in /properties/b

With this OAS:
paths:
  /responses/mutual-a:
    post:
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SharedModelMutualRecursionA'
components:
  schemas:
    SharedModelMutualRecursionA:
      type: object
      properties:
        b:
          $ref: '#/components/schemas/SharedModelMutualRecursionB'
      required: []

    SharedModelMutualRecursionB:
      type: object
      properties:
        a:
          $ref: '#/components/schemas/SharedModelMutualRecursionA'
      required: []

It looks like an issue in json-schema-faker, so I'll see about reporting there, but it may be good to wrap calls to that library in a try/catch if possible.


Not working on iOS 9

Expected Behaviour
To work on iOS 9 or to be documented that it doesn't work on iOS 9
Actual Behaviour
Doesn't work on iOS 9 (not even ask for push permission)
Reproduce Scenario (including but not limited to)
Current master uses UNUserNotificationCenter, which is only available for iOS 10+, but doesn't seem to have code for older versions.
Cordova still supports iOS 9, so I expect the plugin to also support it or at least document that it doesn't.
Steps to Reproduce
Use this sample app but with master version of the plugin and run on iOS 9 device
https://github.com/jcesarmobile/phonegap-plugin-push-sample
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
iOS 9
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Cordova CLI version and cordova platform version
cordova --version                                   8.0.0
cordova platform version ios                    4.5.4

Plugin version
current master (appears as 2.2.3)

Sample Push Data Payload
not relevant
Sample Code that illustrates the problem
https://github.com/jcesarmobile/phonegap-plugin-push-sample
Logs taken while reproducing problem

@jcesarmobile Yeah, the latest commits to master will end up in a 3.0.0 version because of the iOS 10+ requirement. I'll branch off a v2.x off of the last 2.2.3 commit in case we need to do bug fixes. Supporting iOS 10, 11 and soon 12 should be good enough.

@macdonst what version of the plugin do we need to be using in order to support iOS 9?  My testers are reporting that my app fails to even install on iOS9 so I am wondering if this plugin is the issue?
Using version 2.2.3 with Cordova-IOS 4.5.5 (an Ionic app)
We used version 1 of the Plugin originally but because we migrated from GCM to FCM on the Android side we need to use version 2.  We still use APNS on the iOS side - should version 2 of the plugin support iOS9 ?

@macdonst I just found our install problem had nothing to do with the plugin as an app without the plugin would not install either.  However, I would like conformation of whether version 2.2.3 of the plugin does support iOS 9?  thanks

Thanks @jcesarmobile that's good to know.

Was this ever resolved?

3.x is not released yet, but won’t support iOS 9.
2.x works fine, so there is nothing to resolve, other than documenting that iOS 9 is not supported before doing the release


🐛 Bug Report: Gerrit Integration broken in 1.17.0

📜 Description
PR #17492 Breaks Gerrit Integration for many installations.
(Though it is an really awesome PR)
The issue seems to boil down to how the authentication URL is built.
https://github.com/backstage/backstage/pull/17492/files#diff-99fdaa7f50c400f0721fd917db2ddeeb1a105f26d7d12c5a6b13859b5dd5d5acR156
👍 Expected behavior
If the gitilesBaseUrl is not host only, the /a/ will be appended directly after the root:
E.g. getGitilesAuthenticationUrl('https://gerrit-instance.com/gerrit/') will yield https://gerrit-instance.com/a/gerrit/ and not the correct https://gerrit-instance.com/gerrit/a/.
👎 Actual Behavior with Screenshots

👟 Reproduction steps
set config.gitilesBaseUrl to include a path.
📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

aww, thats unfortunate. I think that we will probably want to get your PR merged in today and then cut a bonus release with the fixes in it. Thanks for contributing the fix too! :tada:

Ugh. Sorry. It's still possible to generate bad Gitiles-links. I pushed a new PR here: #19488
This PR also includes better tests. Sorry.

@GLundh can we close the issue?

Yes. 1.17.4 seems to work in our staging environment.


⚠ Bofrost.de has degraded performance

In b7675c7, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1343 ms

Resolved: Bofrost.de performance has improved in 70ba740 after 311 days, 11 hours, 12 minutes.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v2.6.27 to before v4.14.240",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5e3ca0ec76fce92daa4eed0d02de9c79b1fe3920",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=50b51460f59acbd403475510ad423bb5ea7a4c97"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "5e3ca0ec76fce92daa4eed0d02de9c79b1fe3920",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "50b51460f59acbd403475510ad423bb5ea7a4c97",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "seq_buf: Fix overflow in seq_buf_putmem_hex()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.14.240 by commit 50b51460f59acbd403475510ad423bb5ea7a4c97, it was introduced in version v2.6.27 by commit 5e3ca0ec76fce92daa4eed0d02de9c79b1fe3920. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001427


Ordered List after List will be List

Hi. I want to parse markdown text includes list and ordered list.
example input
- item
- item
- item

1. item
1. item
1. item

expect result
- item
- item
- item

1. item
2. item
3. item

result
-   item
-   item
-   item

-   item
-   item
-   item

Why is this result? And can I solve it?

What settings do you use?

I set no options. Only exec % ./node_modules/.bin/remark < input.md

I run into the same issue.
Workarounds would be:

inserting two blank lines between lists, or
enable CommonMark option


fix(es/plugin): Fix starter template main field (#6814)

Description:
Replace - with _ in generated package.json main field to match what cargo names the output .wasm file. Allows swc-core to load the plugin at runtime.
Related issue (if exists):
#6814

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Alex Dixon seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Alex Dixon seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


"lxc delete" sometimes freezing

Lots of my "lxc" commands are automation. Unfortunately sometimes "lxc delete" does not work as expected.
The usage case is:

have a base container, say "base-container"
copy it to a new one ("test-env-12345"), run tests, and if they are successful - remove all previous "test-env-*" containers

Unfortunately, this is where it fails for me. In process list ("ps"), I would just see "lxc delete ... --force" as a process which runs for 20, 30 and more minutes (until I kill it).
In "lxc list", I would see the container which should be removed in "FREEZING" state:
| z-testing-a19ea622182c63ddc19bb22cde982b82-2016-02-15-00-17-14 | FREEZING
Why is it even in FREEZING state if we remove it?
When the container is in this state, I'm no longer able to do anything with it - these just never return:
lxc delete z-testing-a19ea622182c63ddc19bb22cde982b82-2016-02-15-00-17-14 --force
lxc stop z-testing-a19ea622182c63ddc19bb22cde982b82-2016-02-15-00-17-14
Don't see any errors in the log.
# dpkg -l|grep lxd
ii  lxd                                      2.0.0~beta2-0ubuntu1~ubuntu14.04.1~ppa1 amd64        Container hypervisor based on LXC - daemon
ii  lxd-client                               2.0.0~beta2-0ubuntu1~ubuntu14.04.1~ppa1 amd64        Container hypervisor based on LXC - client

# uname -a
Linux backup01.sys.timedoctor.com 4.4.0-040400-generic #201601101930 SMP Mon Jan 11 00:32:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

# dpkg -l|grep criu
ii  criu                                     1.7.2-2~ubuntu14.04.1~ppa1              amd64        checkpoint and restore in userspace

This is how it looks in processlist:
root     31827  0.0  0.0  82916  4936 ?        Ss   00:17   0:07 [lxc monitor] /var/lib/lxd/containers z-testing-a19ea622182c63ddc19bb22cde982b82-2016-02-15-00-17-14 100000   31855  0.0  0.0  33256  1128 ?        Ds   00:17   0:00  \_ /sbin/init 100000   32271  0.0  0.0  36892   616 ?        D    00:17   0:00      \_ @sbin/plymouthd --mode=boot --attach-to-session 100000   32276  0.0  0.0  27656  1012 ?        D    00:17   0:00      \_ mountall --daemon 100000     374  0.0  0.0  72860 17068 ?        Ds   00:17   0:00      \_ /usr/bin/python /usr/bin/cloud-init init --local 100000    1363  0.0  0.0  19480   180 ?        D    00:17   0:00      \_ upstart-udev-bridge --daemon 100000    1383  0.0  0.0  15528   672 ?        D    00:17   0:00      \_ upstart-socket-bridge --daemon 100000    1385  0.0  0.0  49276   700 ?        Ds   00:17   0:00      \_ /lib/systemd/systemd-udevd --daemon
If I kill process 31827 - I'm able to remove the container.
However, the other processes stay in the process list (claimed by /sbin/init from the host). It's interesting why they would be in D state and that perhaps explains why the command freezes.
Using btrfs filesystem.

LXD freezes the container before killing it and removing it, that's an optimization so that it's possible to destroy a container which is currently running a forkbomb where a normal kill would never work due to the processes going away and re-appearing constantly.
The reason why it's stuck in freezing state here is because of those I/O wait (D state) processes. They seem to be stuck on some kind of blocking I/O and so the kernel cannot freeze them until said I/O is unblocked. As soon as they get out of D state they'll get frozzen (T state) and the container will be killed and deleted.
I suspect that the reason why those processes are stuck in D state is some kind of storage related kernel bug on your machine. I wouldn't be surprised if "dmesg" showed a bunch of long hung processes that the kernel can't do anything about.

LXD freezes the container before killing it and removing it,

Makes sense, thanks for the explanation.
Nothing about I/O in dmesg. But yes, I agree it might be hanging due to some bug in kernel (btrfs or process freezing).
echo w > /proc/sysrq-trigger gives me (did not paste in full) - however, this doesn't say much to me. Might be a kernel issue with process freezing.
Feb 15 05:12:12 backup01 kernel: [1882944.058297] sysrq: SysRq : Show Blocked State
Feb 15 05:12:12 backup01 kernel: [1882944.058329]   task                        PC stack   pid father
Feb 15 05:12:12 backup01 kernel: [1882944.058370] init            D ffff880054f5bd00     0 13757      1 0x00000104
Feb 15 05:12:12 backup01 kernel: [1882944.058376]  ffff880054f5bd00 dead000000000200 ffff8801014e0000 ffff8807ffa4b700
Feb 15 05:12:12 backup01 kernel: [1882944.058379]  ffff880054f5c000 ffff8807ffa4b700 ffff8807ffa4b700<PHONE_NUMBER>000001
Feb 15 05:12:12 backup01 kernel: [1882944.058382]<PHONE_NUMBER>000000 ffff880054f5bd18 ffffffff817f9925 ffff8807ffa4b700
Feb 15 05:12:12 backup01 kernel: [1882944.058386] Call Trace:
Feb 15 05:12:12 backup01 kernel: [1882944.058394]  [<ffffffff817f9925>] schedule+0x35/0x80
Feb 15 05:12:12 backup01 kernel: [1882944.058399]  [<ffffffff810e5d1a>] __refrigerator+0x7a/0x140
Feb 15 05:12:12 backup01 kernel: [1882944.058404]  [<ffffffff8108d131>] get_signal+0x5e1/0x600
Feb 15 05:12:12 backup01 kernel: [1882944.058408]  [<ffffffff81016517>] do_signal+0x37/0x6f0
Feb 15 05:12:12 backup01 kernel: [1882944.058412]  [<ffffffff81136c4f>] ? seccomp_phase1+0x9f/0x280
Feb 15 05:12:12 backup01 kernel: [1882944.058416]  [<ffffffff810800e6>] ? do_wait+0x116/0x220
Feb 15 05:12:12 backup01 kernel: [1882944.058421]  [<ffffffff8100320c>] exit_to_usermode_loop+0x8c/0xd0
Feb 15 05:12:12 backup01 kernel: [1882944.058425]  [<ffffffff81003c2e>] syscall_return_slowpath+0x4e/0x60
Feb 15 05:12:12 backup01 kernel: [1882944.058429]  [<ffffffff817fdb18>] int_ret_from_sys_call+0x25/0x8f
Feb 15 05:12:12 backup01 kernel: [1882944.058431] upstart-socket- D ffff88055bbefd00     0 15313  13757 0x00000104
Feb 15 05:12:12 backup01 kernel: [1882944.058435]  ffff88055bbefd00 ffff88030581a080 ffff8807ffa4a940 ffff880105098dc0
Feb 15 05:12:12 backup01 kernel: [1882944.058438]  ffff88055bbf0000 ffff880105098dc0 ffff880105098dc0<PHONE_NUMBER>000001
Feb 15 05:12:12 backup01 kernel: [1882944.058441]<PHONE_NUMBER>000000 ffff88055bbefd18 ffffffff817f9925 ffff880105098dc0
Feb 15 05:12:12 backup01 kernel: [1882944.058444] Call Trace:
Feb 15 05:12:12 backup01 kernel: [1882944.058447]  [<ffffffff817f9925>] schedule+0x35/0x80
Feb 15 05:12:12 backup01 kernel: [1882944.058450]  [<ffffffff810e5d1a>] __refrigerator+0x7a/0x140
Feb 15 05:12:12 backup01 kernel: [1882944.058453]  [<ffffffff8108d131>] get_signal+0x5e1/0x600
Feb 15 05:12:12 backup01 kernel: [1882944.058456]  [<ffffffff81016517>] do_signal+0x37/0x6f0
Feb 15 05:12:12 backup01 kernel: [1882944.058459]  [<ffffffff81136c4f>] ? seccomp_phase1+0x9f/0x280
Feb 15 05:12:12 backup01 kernel: [1882944.058462]  [<ffffffff810800e6>] ? do_wait+0x116/0x220
Feb 15 05:12:12 backup01 kernel: [1882944.058465]  [<ffffffff8100320c>] exit_to_usermode_loop+0x8c/0xd0
Feb 15 05:12:12 backup01 kernel: [1882944.058469]  [<ffffffff81003c2e>] syscall_return_slowpath+0x4e/0x60
Feb 15 05:12:12 backup01 kernel: [1882944.058472]  [<ffffffff817fdb18>] int_ret_from_sys_call+0x25/0x8f
Feb 15 05:12:12 backup01 kernel: [1882944.058474] upstart-udev-br D ffff880661973d00     0 15617  13757 0x00000104
Feb 15 05:12:12 backup01 kernel: [1882944.058477]  ffff880661973d00 ffff88000a1a4280 ffff88080befa940 ffff880807463700
Feb 15 05:12:12 backup01 kernel: [1882944.058480]  ffff880661974000 ffff880807463700 ffff880807463700<PHONE_NUMBER>000001
Feb 15 05:12:12 backup01 kernel: [1882944.058483]<PHONE_NUMBER>000000 ffff880661973d18 ffffffff817f9925 ffff880807463700
Feb 15 05:12:12 backup01 kernel: [1882944.058486] Call Trace:
Feb 15 05:12:12 backup01 kernel: [1882944.058489]  [<ffffffff817f9925>] schedule+0x35/0x80
Feb 15 05:12:12 backup01 kernel: [1882944.058492]  [<ffffffff810e5d1a>] __refrigerator+0x7a/0x140
Feb 15 05:12:12 backup01 kernel: [1882944.058495]  [<ffffffff8108d131>] get_signal+0x5e1/0x600
Feb 15 05:12:12 backup01 kernel: [1882944.058498]  [<ffffffff81016517>] do_signal+0x37/0x6f0
Feb 15 05:12:12 backup01 kernel: [1882944.058501]  [<ffffffff81136c4f>] ? seccomp_phase1+0x9f/0x280
Feb 15 05:12:12 backup01 kernel: [1882944.058503]  [<ffffffff810800e6>] ? do_wait+0x116/0x220
Feb 15 05:12:12 backup01 kernel: [1882944.058507]  [<ffffffff8100320c>] exit_to_usermode_loop+0x8c/0xd0
Feb 15 05:12:12 backup01 kernel: [1882944.058510]  [<ffffffff81003c2e>] syscall_return_slowpath+0x4e/0x60
Feb 15 05:12:12 backup01 kernel: [1882944.058513]  [<ffffffff817fdb18>] int_ret_from_sys_call+0x25/0x8f
Feb 15 05:12:12 backup01 kernel: [1882944.058515] systemd-udevd   D ffff880516593d00     0 15666  13757 0x00000104
Feb 15 05:12:12 backup01 kernel: [1882944.058518]  ffff880516593d00 ffff88082fb16b30 ffff880105108dc0 ffff8807ea8c8000
Feb 15 05:12:12 backup01 kernel: [1882944.058521]  ffff880516594000 ffff8807ea8c8000 ffff8807ea8c8000<PHONE_NUMBER>000001
Feb 15 05:12:12 backup01 kernel: [1882944.058524]<PHONE_NUMBER>000000 ffff880516593d18 ffffffff817f9925 ffff8807ea8c8000
Feb 15 05:12:12 backup01 kernel: [1882944.058536] Call Trace:
Feb 15 05:12:12 backup01 kernel: [1882944.058538]  [<ffffffff817f9925>] schedule+0x35/0x80
Feb 15 05:12:12 backup01 kernel: [1882944.058550]  [<ffffffff810e5d1a>] __refrigerator+0x7a/0x140
Feb 15 05:12:12 backup01 kernel: [1882944.058553]  [<ffffffff8108d131>] get_signal+0x5e1/0x600
Feb 15 05:12:12 backup01 kernel: [1882944.058556]  [<ffffffff81016517>] do_signal+0x37/0x6f0
Feb 15 05:12:12 backup01 kernel: [1882944.058558]  [<ffffffff817f9925>] ? schedule+0x35/0x80
Feb 15 05:12:12 backup01 kernel: [1882944.058561]  [<ffffffff817fce94>] ? schedule_hrtimeout_range_clock+0x34/0x40
Feb 15 05:12:12 backup01 kernel: [1882944.058566]  [<ffffffff8124e64b>] ? ep_poll+0x37b/0x3d0
Feb 15 05:12:12 backup01 kernel: [1882944.058569]  [<ffffffff8100320c>] exit_to_usermode_loop+0x8c/0xd0
Feb 15 05:12:12 backup01 kernel: [1882944.058572]  [<ffffffff81003c2e>] syscall_return_slowpath+0x4e/0x60
Feb 15 05:12:12 backup01 kernel: [1882944.058575]  [<ffffffff817fdb18>] int_ret_from_sys_call+0x25/0x8f
Feb 15 05:12:12 backup01 kernel: [1882944.058578] dbus-daemon     D ffff8807546e7d00     0 16242  13757 0x00000104
Feb 15 05:12:12 backup01 kernel: [1882944.058581]  ffff8807546e7d00 ffff88082fbd6b30 ffff88080befe040 ffff8808099c5280
Feb 15 05:12:12 backup01 kernel: [1882944.058584]  ffff8807546e8000 ffff8808099c5280 ffff8808099c5280<PHONE_NUMBER>000001
Feb 15 05:12:12 backup01 kernel: [1882944.058587]<PHONE_NUMBER>000000 ffff8807546e7d18 ffffffff817f9925 ffff8808099c5280
Feb 15 05:12:12 backup01 kernel: [1882944.058590] Call Trace:
Feb 15 05:12:12 backup01 kernel: [1882944.058592]  [<ffffffff817f9925>] schedule+0x35/0x80
Feb 15 05:12:12 backup01 kernel: [1882944.058595]  [<ffffffff810e5d1a>] __refrigerator+0x7a/0x140
Feb 15 05:12:12 backup01 kernel: [1882944.066548]   .load                          : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066549]   .load_avg                      : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066551]   .runnable_load_avg             : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066552]   .util_avg                      : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066554]   .removed_load_avg              : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066555]   .removed_util_avg              : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066557]   .tg_load_avg_contrib           : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066558]   .tg_load_avg                   : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066560]   .throttled                     : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066561]   .throttle_count                : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066563]   .se->exec_start                :<PHONE_NUMBER>.879780
Feb 15 05:12:12 backup01 kernel: [1882944.066565]   .se->vruntime                  : 155757266.927065
Feb 15 05:12:12 backup01 kernel: [1882944.066566]   .se->sum_exec_runtime          : 25.239032
Feb 15 05:12:12 backup01 kernel: [1882944.066568]   .se->statistics.wait_start     : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.066570]   .se->statistics.sleep_start    : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.066571]   .se->statistics.block_start    : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.066573]   .se->statistics.sleep_max      : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.066574]   .se->statistics.block_max      : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.066576]   .se->statistics.exec_max       : 2.104138
Feb 15 05:12:12 backup01 kernel: [1882944.066578]   .se->statistics.slice_max      : 0.023345
Feb 15 05:12:12 backup01 kernel: [1882944.066579]   .se->statistics.wait_max       : 0.088920
Feb 15 05:12:12 backup01 kernel: [1882944.066581]   .se->statistics.wait_sum       : 0.112526
Feb 15 05:12:12 backup01 kernel: [1882944.066582]   .se->statistics.wait_count     : 469
Feb 15 05:12:12 backup01 kernel: [1882944.066584]   .se->load.weight               : 2
Feb 15 05:12:12 backup01 kernel: [1882944.066585]   .se->avg.load_avg              : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066587]   .se->avg.util_avg              : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066590]
Feb 15 05:12:12 backup01 kernel: [1882944.066590] cfs_rq[0]:/lxc/z-testing-a19ea622182c63ddc19bb22cde982b82-2016-02-15-00-17-14
Feb 15 05:12:12 backup01 kernel: [1882944.066592]   .exec_clock                    : 195.718750
Feb 15 05:12:12 backup01 kernel: [1882944.066594]   .MIN_vruntime                  : 0.000001
Feb 15 05:12:12 backup01 kernel: [1882944.066595]   .min_vruntime                  : 2875.257150
Feb 15 05:12:12 backup01 kernel: [1882944.066597]   .max_vruntime                  : 0.000001
Feb 15 05:12:12 backup01 kernel: [1882944.066598]   .spread                        : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.066600]   .spread0                       : -155764595.454204
Feb 15 05:12:12 backup01 kernel: [1882944.066602]   .nr_spread_over                : 6
Feb 15 05:12:12 backup01 kernel: [1882944.066603]   .nr_running                    : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066604]   .load                          : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066606]   .load_avg                      : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066607]   .runnable_load_avg             : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066609]   .util_avg                      : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066610]   .removed_load_avg              : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066612]   .removed_util_avg              : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066613]   .tg_load_avg_contrib           : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066615]   .tg_load_avg                   : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066616]   .throttled                     : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066618]   .throttle_count                : 0
Feb 15 05:12:12 backup01 kernel: [1882944.066620]   .se->exec_start                :<PHONE_NUMBER>.951647
Feb 15 05:12:12 backup01 kernel: [1882944.066621]   .se->vruntime                  : 282863085.373346
Feb 15 05:12:12 backup01 kernel: [1882944.066623]   .se->sum_exec_runtime          : 195.718750
Feb 15 05:12:12 backup01 kernel: [1882944.066625]   .se->statistics.wait_start     : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.066626]   .se->statistics.sleep_start    : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.066628]   .se->statistics.block_start    : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.066629]   .se->statistics.sleep_max      : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.066631]   .se->statistics.block_max      : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.066633]   .se->statistics.exec_max       : 4.004930
Feb 15 05:12:12 backup01 kernel: [1882944.121818]   .nr_running                    : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121819]   .load                          : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121820]   .load_avg                      : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121821]   .runnable_load_avg             : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121822]   .util_avg                      : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121824]   .removed_load_avg              : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121825]   .removed_util_avg              : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121826]   .tg_load_avg_contrib           : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121827]   .tg_load_avg                   : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121828]   .throttled                     : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121830]   .throttle_count                : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121831]   .se->exec_start                :<PHONE_NUMBER>.472892
Feb 15 05:12:12 backup01 kernel: [1882944.121832]   .se->vruntime                  : 120831165.461998
Feb 15 05:12:12 backup01 kernel: [1882944.121834]   .se->sum_exec_runtime          : 1.401791
Feb 15 05:12:12 backup01 kernel: [1882944.121835]   .se->statistics.wait_start     : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.121836]   .se->statistics.sleep_start    : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.121838]   .se->statistics.block_start    : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.121839]   .se->statistics.sleep_max      : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.121840]   .se->statistics.block_max      : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.121841]   .se->statistics.exec_max       : 0.078656
Feb 15 05:12:12 backup01 kernel: [1882944.121843]   .se->statistics.slice_max      : 0.000000
Feb 15 05:12:12 backup01 kernel: [1882944.121844]   .se->statistics.wait_max       : 0.080708
Feb 15 05:12:12 backup01 kernel: [1882944.121845]   .se->statistics.wait_sum       : 0.080708
Feb 15 05:12:12 backup01 kernel: [1882944.121846]   .se->statistics.wait_count     : 55
Feb 15 05:12:12 backup01 kernel: [1882944.121848]   .se->load.weight               : 2
Feb 15 05:12:12 backup01 kernel: [1882944.121849]   .se->avg.load_avg              : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121850]   .se->avg.util_avg              : 0
Feb 15 05:12:12 backup01 kernel: [1882944.121852]

Can you paste "ls -lh /proc/<pid of one of the stuck PIDs>/fd"? I'm starting to wonder if maybe the I/O wait is coming from lxcfs as any other kind should really have triggered the kernel monitoring feature.

100000   26227  0.0  0.0  33392     4 ?        Ds   Feb01   0:00 /sbin/init
100000   27730  0.0  0.0  15396     4 ?        D    Feb01   0:00  \_ upstart-socket-bridge --daemon

# ls -lh /proc/26227/fd
total 0
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 0 -> /null
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 1 -> /null
l-wx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 10 -> /var/log/upstart/php5-fpm.log.1 (deleted)
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 11 -> socket:[25791518]
l-wx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 13 -> /var/log/upstart/acpid.log.1 (deleted)
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 14 -> socket:[25794768]
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 15 -> socket:[25790417]
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 16 -> /pts/ptmx
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 18 -> /pts/ptmx
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 2 -> /null
lr-x------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 3 -> pipe:[25786059]
l-wx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 4 -> pipe:[25786059]
lr-x------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 5 -> anon_inode:inotify
lr-x------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 6 -> anon_inode:inotify
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 7 -> socket:[25786060]
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 8 -> socket:[25785181]
l-wx------ 1<PHONE_NUMBER>00 64 Feb 16 05:10 9 -> /var/log/upstart/systemd-logind.log.1 (deleted)

# ls -lh /proc/27730/fd
total 0
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:12 0 -> /null
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:12 1 -> /null
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:12 2 -> /null
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:12 3 -> anon_inode:[eventpoll]
lrwx------ 1<PHONE_NUMBER>00 64 Feb 16 05:12 4 -> socket:[25791514]
lr-x------ 1<PHONE_NUMBER>00 64 Feb 16 05:12 5 -> pipe:[25791515]
l-wx------ 1<PHONE_NUMBER>00 64 Feb 16 05:12 6 -> pipe:[25791515]

Hmm, then no, that's not lxcfs... or at least not in an obvious way.
Can you also paste the content of "/proc/<pid>/stack"?

# cat /proc/26227/stack
[<ffffffff810e5d1a>] __refrigerator+0x7a/0x140
[<ffffffff8108d131>] get_signal+0x5e1/0x600
[<ffffffff81016517>] do_signal+0x37/0x6f0
[<ffffffff8100320c>] exit_to_usermode_loop+0x8c/0xd0
[<ffffffff81003c2e>] syscall_return_slowpath+0x4e/0x60
[<ffffffff817fdb18>] int_ret_from_sys_call+0x25/0x8f
[<ffffffffffffffff>] 0xffffffffffffffff

# cat /proc/27730/stack
[<ffffffff810e5d1a>] __refrigerator+0x7a/0x140
[<ffffffff8108d131>] get_signal+0x5e1/0x600
[<ffffffff81016517>] do_signal+0x37/0x6f0
[<ffffffff8100320c>] exit_to_usermode_loop+0x8c/0xd0
[<ffffffff81003c2e>] syscall_return_slowpath+0x4e/0x60
[<ffffffff817fdb18>] int_ret_from_sys_call+0x25/0x8f
[<ffffffffffffffff>] 0xffffffffffffffff

That very much smells like a kernel bug to me...
What kernel version are you running and does that happen pretty reliably after a clean boot?

Running 4.4.0 (need to run a very recent kernel, because I'm running btrfs which is still semi-stable, and even less stable with older kernels).
It's not something which happens very reliably. Perhaps few percent of "lxd delete" runs.
I'll upgrade to 4.4.2 when it's released and report back if I'm still seeing it.

Have you been seeing more of this issue?

No, but I think I know what was causing this now - "fork bomb", sort of.
Some of the containers I've been launching were running supervisord, which was starting lots of processes per second (which were exiting then immediately) under some circumstances. After disabling this behaviour, I'm no longer seeing this issue.

Ah, the new pid cgroups may be interesting for you then, it was introduced with the 4.2 kernel I believe and LXD recently grew support through the limit.processes config key. It would allow you to set a reasonable process limit for your containers which should in turn make freezing and deleting them much easier.
Anyway, based on your feedback, I'll consider this issue closed for now.
Thanks


chore(build): create standalone validator during install

published files will be bundled but not standalone
standalone validator is created in postinstall script, using the schema version available to npm

Not sure if postinstall helps us here.
From what I understand we'd need to re-build the validator every time we update a schema:
install validator <-- build schema
update schema <-- does validator#postinstall pick this up?

Another one to think about: Does building the schema require development dependencies? And how does it affect our build times.
The alternative is to keep our existing strategy, but ensure that renovate and friends are appropriately configured and so forth.

From what I understand we'd need to re-build the validator every time we update a schema:

I have not thought about it initially, but played around with scripts locally a bit. postinstall scripts are run again when subtree dependency modifications happens. I did find some forum entries confirming this, but no primary source so I validated this locally:
% NPM_CONFIG_REGISTRY=http://localhost:4873 npm update nested --verbose
npm verb cli /home/stamm/.nvm/versions/node/v16.13.1/bin/node /home/stamm/.nvm/versions/node/v16.13.1/bin/npm
[...]
npm info run<EMAIL_ADDRESS>postinstall ../child echo "postinstall in child called"
npm info run<EMAIL_ADDRESS>postinstall { code: 0, signal: null }
npm timing build:run:postinstall:../child Completed in 11ms
[...]

So while the current implementation would not update it (as it overrides the source file), it is possible to update to the latest version after an update commands with a postinstall script

Does building the schema require development dependencies

No, as the bundeling is already done during the build step, creating the standalone version only requires ajv (prod dependency) and node internals like fs.

And how does it affect our build times.

It adds ~350ms to the install time for downstream libraries

One thing I'm not certain of before this is ready for review:
with a36bbf6 we could make the schema versions a peer dependency, so the integrating library can chooses the schema version explicitly. Con: we need both C7 and Zeebe schemas even if the downstream library only uses one of those, which is rather unexpected.
Alternatives:

Have the schema version as a normal dependency, updates can be done through npm update on the downstream lib.
We would still need to release update for this lib for breaking changes in the schema repo.

Refactor the code to work with missing dependencies (e.g. don't build the validator if schema is not provided) using peerDependenciesMeta. This would also allow this library to be installed without any schemas without error, which would be unexpected when the code then fails when you try to validate it.

I'm a fan of this:

Have the schema version as a normal dependency, updates can be done through npm update on the downstream lib.
We would still need to release update for this lib for breaking changes in the schema repo.

Did you validate with https://github.com/bpmn-io/element-templates-validator/pull/15#issuecomment-1415617946 that a upstream dependency update rebuilds things in this library:
element-templates-validator
  - actual-schema <--- UPDATE

I verified earlier that postinstall scripts are called in this structure:
root
  - child <== postinstall run again
     - nested <== update

I also validated again with
root
  - @bpmn-io/element-templates-validator <== postinstall run again
     - @camunda/zeebe-element-templates-json-schema <== update

with the same result.
Note: I did not test this against the actual npm registry but on a local registry. On monday, I might try with some test packages tags on the npm registry to verify it actually works. The generated manifests can have influence on the install scripts being run.

Unfortunately, it seems that the behavior is different when the package is loaded from the actuall npm registry 😞
It does not run the postinstall script when the package was already installed, so this is not a viable method of solving the problem. You would have to delete node_modules and reinstall everything to get the desired result. I don't know why it behaves different locally
Guess we have to stick with bundeling for now


Setup Deepstream server and config file.

The Deepstream server has been configured and setup in the /servers folder. The Deepstream server will be running as a Node process.


Have anyone reproduce the reaults shown on paper ?

Have anyone reproduce the AP reaults shown in paper ?
I mean in paper , not the AP results on github.

Hi, the differences between the results on github and paper are only some tricks we have not used in the released codes, such 2x training schedule, dcn, soft-nms, etc.


failFast causes process to exit before always.afterEach hooks complete

Description
If I try and do something asynchronous (or just slow?) from an always.afterEach() function while the failFast flag is set in my package.json the process won't wait for it to complete when the test fails. My specific case if is that I'm trying to do some database cleanup after each test and even though the afterEach hook gets called it doesn't seem to be given a chance to finish before the process exits.
I've tried to distill this down to a simple example:
import test from 'ava'

test.afterEach.always('CLEANUP', async t => {
  console.log('START', t.title)

  await new Promise(resolve => setTimeout(resolve, 5000))

  console.log('END', t.title)
})

test('Test', async t => {
  console.log('START', t.title)
  t.plan(1)

  t.is(1, 2)
  console.log('END', t.title)
})

This is the output I get:
START Test
END Test
  ✖ Test 1 === 2
START CLEANUP for Test

  1 test failed [10:42:18]

  1. Test
  AssertionError: 1 === 2
    _callee2$ (cleanup-test.js:15:5)
    Test.fn (cleanup-test.js:11:1)

I would expect to see END CLEANUP printed
Environment
Node.js v5.11.0
darwin 15.3.0
(Originally asked on SO: From http://stackoverflow.com/questions/37118762/ava-aftereach-callback-not-completing)

Fail fast causes the worker to be torn down without regard for test hooks.
I think we should add a gracefulStop() (or something like that) to the runner, which prevents new serial tests from being started and waits for any asynchronous tests to complete, including their after hooks. Any further test results should be discarded.
Tests won't fail as fast as before, but cleanup will be more reliable.

I'm of the opinion that using after / afterEach for cleanup is a bad plan. I think you should have a conditional cleanup in a before / beforeEach instead.
It's impossible to provide both fast failure and reliable post-test hooks, and I would rather not crippple the fast fail behavior in favor of something I think is an antipattern

I'm of the opinion that using after / afterEach for cleanup is a bad plan.

Why? I've always done cleanups in the after hooks too.

I think you should have a conditional cleanup in a before / beforeEach instead.

It doesn't sound very atomic to have to clean up after the previous test in the before hooks.

I've always done cleanups in the after hooks too.

I did for a long time too, but things just work better the other way. I have more than once gotten myself into a situation where failing tests leave bad state on the file system that would be cleaned up in an after hook, but after hooks never get called because tests don't complete.  This means you need to do a run you know will fail, just to cleanup state (or manually cleanup).
Cleaning up in a beforeEach also has a distinct advantage over always.afterEach when using fail-fast, in that the offending state is left in tact so you can examine it.

It doesn't sound very atomic to have to clean up after the previous test in the before hooks

Don't think of it as cleanup of the past state, think of it as ensuring a start state for the current one. Relying on the test before you to properly cleanup after itself is what isn't atomic.

For what it's worth I've moved my cleanup to the before hook for basically the exact reasons @jamestalmage points out here.

Cleaning up in a beforeEach also has a distinct advantage over always.afterEach when using fail-fast, in that the offending state is left in tact so you can examine it.

fail-fast failing so fast that your code doesn't have a chance to clean up actually sounds like a feature. @vdemedes @sindresorhus @jamestalmage @sotojuan what do you think? If you agree we should document it as such.

That's a good point, but definitely needs good docs on that as it can be surprising behavior.
I guess what I'd like is a hook that is run both before and after, so I can ensure it's cleaned up no matter what. Not a big problem for me though, as I've learned to use temp files for fixtures instead of putting them in the current directory, and they don't need cleaning up.

@novemberborn I think fail-fast should quit asap. If we allow cleaning up or running after hooks, other parallel tests will continue to execute. I agree with you!

I've learned to use temp files for fixtures instead of putting them in the current directory, and they don't need cleaning up

Yes, that's pretty much what I always do now. Especially with AVA, since you need unique temp dirs/files for each test if you want to take advantage of concurrency. The only downside is that it is harder to find and inspect that temp location (requires adding a logging statement and cd-ing into the system temp folder).

#858 documents this. The issue is now closed since it's expected (and one might say desired) behavior.


chore(greenkeeper<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build 329

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.1%) to 97.516%

Totals

Change from base Build 308:
1.1%

Covered Lines:
105

Relevant Lines:
107

💛  - Coveralls

:tada: This PR is included in version 3.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


@broskoski: Remove Fusion url from artwork model

Fusion is this little service that keeps a stale copy of Gravity's artwork data for the sake of serving sitemaps. Pre-metaphysics it would help keep its data fresh by being swapped in place of /api/v1/artwork/:id requests (it also falls back to proxying Gravity). Now-a-days it just crawls the latest artworks daily and lets the data eventually get somewhat in sync.
Ashkan noticed an issue in staging where it was requesting from Fusion (which doesn't have a staging version) and therefore returning a 404. So just simply removing it from the artwork model to address this.

👋
Goodbye Fusion. It's been real.


Don't append a --sysroot argument to RUSTFLAGS if it already contains one

Appending the flag a second time leads to a "Option 'sysroot' given more than once" error.
This problem occurs because the user might set the RUSTFLAGS environment manually, for example for getting RLS to work.

Published as 0.5.14


Update versions in bundle install command

Fixes https://github.com/aspnet/IISIntegration/issues/384

@tdykstra @Rick-Anderson Stand-by for just a sec on this. The OP is still having a problem getting the executable or getting it to run correctly. I'll ping back when we know the issue is resolved there.

@tdykstra @Rick-Anderson Ok, we're good. It wasn't working because the installer was in a different folder from where the command was being executed on the command line. This is ok to review+merge.


PSB GCFA amendments

Describe the Issue
Procurement Services Branch (PSB) to provide CP and LSB with a written (email) recommendation regarding the acceptability of the GCFA or required contract amendments.
Definition of Done

SO with GCFA amendments or email confirming non necessary

@ZachWoodward - I moved this to Blocked since there's still prior work to be done in order to start this. Let me know if I'm wrong.

@sid-gov, I don't think this is blocked. I believe we have verbal confirmation, just need written.

@paulroberts68 @ZachWoodward - can this be closed?

Resolved.


Make ShipItCreateNewRepoPhase respect destination branch option.

Rather than create a new repo with a "master" orphan branch, create the new repo with an orphan branch of whatever was specified in "--destination-branch".

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


Write a ssrs report automatically to PDF

I've used Alan Judens code to view an ssrs report in my web app. What I would like to do is from a button press run this report an save to pdf in a specific location without having to preview then selecting export. Any help would be appreciated.
Thanks

@achester75, I have done something similar but streamed the file out to the user instead of placing it in a specific location somewhere.
If you call into the /Report/ExportReport/?reportPath=path%20to%20your%20report&format=pdf then it will stream down to the end user.
The only other thing you'll need to deal with is if you need to pass a report parameter you'd just tack it onto the end of your url (or pass it into a POST).

Hi Alan
Thanks for the reply. This works but isn’t quite what I want to do.
Ideally the user would have the option via a button press to select any combination of report see below: They then press send email. This runs each report, writes to a specific location, then is attached the email.
The creating the PDF the way you have advised creates the PDF but saves in the client download folder. I can create an e-mail and add files, but the bit I’m missing is saving the report pdf to a location the server can see.
<EMAIL_ADDRESS>Alan Chester
IT Development Engineer
T:+44 (0)1352 793 245
Unit 15 | Manor Farm Industrial Estate | Flint | Flintshire | CH6 5UY
www.tvcl.co.ukhttp://www.tvcl.co.uk
[https://www.tvcl.co.uk/wp-content/uploads/sites/2/2018/11/TVC-email-footer-V2.jpg]
From: Alan Juden<EMAIL_ADDRESS>Sent: 30 July 2019 19:52
To: alanjuden/MvcReportViewer
Cc: Alan Chester; Mention
Subject: Re: [alanjuden/MvcReportViewer] Write a ssrs report automatically to PDF (#90)
@achester75https://github.com/achester75, I have done something similar but streamed the file out to the user instead of placing it in a specific location somewhere.
If you call into the /Report/ExportReport/?reportPath=path%20to%20your%20report&format=pdf then it will stream down to the end user.
The only other thing you'll need to deal with is if you need to pass a report parameter you'd just tack it onto the end of your url (or pass it into a POST).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/alanjuden/MvcReportViewer/issues/90?email_source=notifications&email_token=AKRIKE42N7V3A5TYP2NX4ALQCCEV5A5CNFSM4IH35Y3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3E6HLI#issuecomment-516547501, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKRIKE4VFCHERF723AMYSODQCCEV5ANCNFSM4IH35Y3A.
Legal Disclaimer: Any views expressed by the sender of this message are not necessarily those of Thames Valley Controls Limited. Information contained in this e-mail may be confidential and is for the use of the intended recipient only, no mistake in transmission is intended to waive or compromise such privilege. Please advise the sender if you receive this e-mail by mistake.


Fix TxQ LastLedgerSequence handling & add tests

I left the fix and the tests as separate commits so anyone interested can revert the fix commit locally and verify the one test fails.
According to the code coverage report, the only things in TxQ left untested after this are logging, the fallbacks when the feature is disabled, the RPC command function, a few edge cases, and stuff that I can't really test without support for multiple transactions per account.
Reviewers: @nbougalis @seelabs

Current coverage is 49.37%

Merging #1394 into develop will increase coverage by +0.12% as of cfb15e9

@@            develop   #1394   diff @@
=======================================
  Files           963     963
  Stmts         66853   66942    +89
  Branches          0       0
  Methods           0       0
=======================================
+ Hit           32931   33053   +122
  Partial           0       0
+ Missed        33922   33889    -33

Review entire Coverage Diff as of cfb15e9

Powered by Codecov. Updated on successful CI builds.

:+1:

Ping @nbougalis.

Forgot to leave a comment when I did it, but pushed another commit moving the misplaced lock we discussed on Friday.

:+1: On moving the lock. The only concern I had was if something called back into TxQ and tried to relock the mutex., but I didn't find anything.

@seelabs Thanks for checking on that. I was careful to avoid recursion, but confirmation is the whole idea.

:+1:

Rebased to 0.30.1-b7. No weirdness encountered.

Merged as 9c8204f945512fa7663495e2064fae5c9c62eeb9 and b87eff2115647cc4d8ed24b751f1077dfb99c326.


drop special config for 126

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Drop special config for 126 due to not tests covering that anymore. 1.26 is out of support.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/assign @trasc

/approve
Thanks


Is there any way to be sure that store is loaded from storage?

Is there any flag or promise that you can check to be ensure that state loaded from storage?

Is there any flag or promise that you can check to be ensure that state loaded from storage?
For what ? You can check update state with watching vuex state.

@KBoyarchuk Cause I want to be sure, that i fully initialize state from localstorage before I start use it.
For example:
I have jwt token in storage.
In background script i have API call that must be called ASAP after background script starts (it can be called with or without jwt).
If I use vuex .watch API (doc). It can be not called (In case when there are no jwt in localstorage, and state never be updated).
If i use vuex .watch API with immediate option. It always starts first call without jwt (cause it starts immediatly). And if jwt exist in localstorage, it loads into state and then I do second call.

No, there isn't a proc on localstorage initialization, maybe related with #13, he report that watchers don't work on persistent states, it occurs because im using the replaceState mehod of vuex api on initialization, probably this don't send any event that fire the watch method.
Well, the solution present on #13 require set setters to all objects on the state, it solve this problem but I didn't implement it because I want to make the plugin the more simple possible for devs.
I think that the best option are proc the event that fire the watch method on the state objects that change, but isn't documented and possible unaccessible through plugin api, I should check it a deep.

For now as workarround, you can wait for a value loaded from localstorage, for example:
Put the data object "lsLoaded" as "false" on your default vuex store initialization, include it on the persistent stores array config and then when you write the required data on load (the jwt token on your example) change the isLoaded to "true".
Then on your script:
With the last explanation, you only should implement a retry with delay (always with delay, for example 300ms because performance) and check for "lsLoaded == true", then fire your API call and stop the

@MitsuhaKitsune Thank you for reply.
Workaround with isLoaded will not work. If it fresh install of extenstion, there are no data in localstorage. So isLoaded will not change in this case.
My workaround:
I remove all persistentStates. And load data from localstorage into state manualy. I also subscribe for mutations and update localstorage manually.

@MitsuhaKitsune This feature can't be implemented ?

I should test a few things, but I trying to move the replaceState method to a global mutation that replace the whole state, this should fix both issues, but I should test first if I can inject the custom mutation to current store through plugin API and if I can replace the whole state on with single mutation.

Finally work with a little workarround, if you like to watch when the data are fully loaded just set a watcher for 'VWE_ReplaceState' mutation.
Sorry for the delay, I really do my best to find a proper solution for this.


Workflow ID detection is broken in v4.1.2

Hi dear NX team 👐
In the newest release (v4.1.2), the nx-set-shas action started to fail due to an error fetching workflow_id via the GH API.

I restarted WF ~10 times, and it failed with the same error.
Rollback to v4.1.1 temporarily fixed the issue.
I assume something is changed in the oktokit new version.

Step configuration to reproduce
      - name: Derive appropriate SHAs for base and head for `nx affected` commands
        uses: nrwl/nx-set-shas@v4
        with:
          main-branch-name: ${{ github.base_ref }}
          last-successful-event: schedule # for 'master' workflow (only 1 can be specified. workflow_dispatch - skipped)

Error screenshots

Thanks! 🙏

UPDATE: We still have NodeJS version v18.10.0 (we're going to upgrade soon); maybe it'll work on v20.
(I've just read your disclaimer)

NOTE: The v4 does no longer support deprecated Node versions. The supported version is Node v18+.

 Using workflow 'undefined'
Error: Process completed with exit code 1.

runs:
  using: "composite"
  steps:
    - name: Derive appropriate SHAs for base and head for `nx affected` commands
      id: setSHAs
      uses: nrwl/nx-set-shas@v4
      with:
        main-branch-name: "master"
        last-successful-event: "pull_request"
        workflow-id: ${{ github.run_id }}


NIM anywhere control panel view and config file terms don't align

This is probably me being a newbie but I don't understand what I'm looking at on this screen.
What are the names in the diagram correlated to in config.yaml?

The diagram shows

Retrieval NIM
Reranker NIM
LLM NIM

config.yaml contains

chat_model
embedding model
reranking model

Also...
Chain Server Configuration
The bottom half of the image shows the Chain Server Configuration but I don't see anything called "chain server" in the diagram above. I'm assuming that it is one of the NIMs? chain.py mentions a bunch of components so I'm not sure why the bottom diagram only includes the chat_model.

Very interesting feedback. Thank you! Its good to be able to see the UI through someone else's eyes!
To answer your questions:

the architecture diagram is the internal architecture of the chain server
retrieval nim <--> embedding_model
reranker nim <--> reranking model
llm nim <--> chat_model

To make this more clear, I think we could make the following changes:

[ ] Rename the Retrieval Configuration accordion to Chain Server Architecture
[ ] In the diagram, rename Retrieval NIM to "Embedding", no NIM in name
[ ] in the diagram, rename Reranker NIM to "Reranker", no NIM in name
[ ] in the diagram, rename LLM NIM to "LLM", no nim in name
[ ] in the configuration file, rename "chat_model" to "llm_model"

That would mean the diagram would show:

Embedding
Reranker
LLM

The config would have:

embedding_model
reranker_model
llm_model

And the top diagram would be labeled as the chain server architecture.

what do you think about those proposed changes?

The "milvus" entry in config.sys is which database in the diagram?

Enterprise data
Chat History
Something else


TS-4534 Remove redundant comma-- to make the json actually valid

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/276/ for details.