Resolve #1508, #1509 for Pipe API

Resolves #1508, #1509. WIP, still being tested.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1969/Build result: FAILURE[...truncated 16 lines...] > /home/jenkins/git2/bin/git rev-parse origin/pr/1511/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a --contains 27bfbd61210c7c232d861d0313cad70259907354 # timeout=10 > /home/jenkins/git2/bin/git rev-parse remotes/origin/pr/1511/merge^{commit} # timeout=10Checking out Revision 27bfbd61210c7c232d861d0313cad70259907354 (origin/pr/1511/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f 27bfbd61210c7c232d861d0313cad70259907354First time build. Skipping changelog.Triggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result FAILURENotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1970/Build result: FAILURE[...truncated 16 lines...] > /home/jenkins/git2/bin/git rev-parse origin/pr/1511/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a --contains a71d88fad84fb6b9b1573ed45414ccfece1cf395 # timeout=10 > /home/jenkins/git2/bin/git rev-parse remotes/origin/pr/1511/merge^{commit} # timeout=10Checking out Revision a71d88fad84fb6b9b1573ed45414ccfece1cf395 (origin/pr/1511/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f a71d88fad84fb6b9b1573ed45414ccfece1cf395First time build. Skipping changelog.Triggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result FAILURENotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1971/Build result: FAILURE[...truncated 16 lines...] > /home/jenkins/git2/bin/git rev-parse origin/pr/1511/merge^{commit} # timeout=10 > /home/jenkins/git2/bin/git branch -a --contains d90d575309a668b84adc29cdef045f3840c48096 # timeout=10 > /home/jenkins/git2/bin/git rev-parse remotes/origin/pr/1511/merge^{commit} # timeout=10Checking out Revision d90d575309a668b84adc29cdef045f3840c48096 (origin/pr/1511/merge) > /home/jenkins/git2/bin/git config core.sparsecheckout # timeout=10 > /home/jenkins/git2/bin/git checkout -f d90d575309a668b84adc29cdef045f3840c48096First time build. Skipping changelog.Triggering ADAM-prb ? 2.3.0,2.11,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.3.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.11,2.0.0,centosTriggering ADAM-prb ? 2.6.0,2.10,2.0.0,centosTriggering ADAM-prb ? 2.3.0,2.10,1.6.1,centosTriggering ADAM-prb ? 2.6.0,2.11,1.6.1,centosADAM-prb ? 2.3.0,2.11,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.3.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,2.0.0,centos completed with result FAILUREADAM-prb ? 2.6.0,2.10,2.0.0,centos completed with result FAILUREADAM-prb ? 2.3.0,2.10,1.6.1,centos completed with result FAILUREADAM-prb ? 2.6.0,2.11,1.6.1,centos completed with result FAILURENotifying endpoint 'HTTP:https://webhooks.gitter.im/e/ac8bb6e9f53357bc8aa8'
Test FAILed.

Coverage increased (+0.07%) to 81.783% when pulling 2ab065732990e6684ba4fc8011496387dee2da14 on fnothaft:issues/1508-1509-pipe-files into dbe5c97c3c1fe01b584190ab31c1539655fa22bf on bigdatagenomics:master.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1972/
Test PASSed.

@heuermh can do! I'll be testing this later today, and will add the unit test as well.

+1

@heuermh Rebased and added the test.

Coverage decreased (-0.09%) to 81.784% when pulling 7291bd877aeec7e33e51267ae99dd9083d6566e5 on fnothaft:issues/1508-1509-pipe-files into ea9ce6c9af6b77943be2fedc01e20e139da74111 on bigdatagenomics:master.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1982/
Test PASSed.

Thank you, @fnothaft


Move toward 24prs

Following from #2369 I propose moving way from Pull Requests and towards 'PRs'. Aim here is to keep the current URLs all working, just to move toward "24PR's" over 24 Pull Requests in branding.
I've registered 24prs.com and set it up in CloudFlare. But I'm not sure what needs to be done to enable redirects to prefer the new URLs and yet maintain the old.
Also if this tagline appears anywhere else then please point it out and I'll mod it.

because GH hates designers:


wrong preview image

Hey @0x5e
This can happen when the previews are generated, usually it fixes itself as you scroll around. When all the previews have been generated (this depends on your network connections) it shouldn't be an issue again.

Hi @glouel ,
This is a simple issue often appears on iOS Apps. I can help fix this when I'm free.
I'm in China and download takes a long time, this issue will make app experience really terrible.

Yep if you think you can help fix it, don't hesitate if you have some time to do so.
I think the problem is especially complicated in China as Apple servers are either slow or blocked. The thumbnails are generated by fetching the beggining of each file and that can take a lot of time in that case. Thanks !
Thanks for offering to help in any case, take care

https://github.com/JohnCoates/Aerial/blob/c2a93e3240cefd1f0be2ef4c6d57cac2cfd10a5f/Resources/MainUI/VideosViewController.swift#L725-L732
In the Thumbnails.get complete block, the cell may be reused. Maybe we can add a cell.video == video protection here?


Remove vm triggers targeted refresh

This PR changes how we process a refresh for a vm being removed from full to targeting.

@miq-bot assign @agrare

Euwe Backport details:
$ git log
commit f3ae91a4e0211513a5ebd16c00e9d3017eacd65a
Author: Adam Grare<EMAIL_ADDRESS>Date:   Tue Oct 11 15:04:00 2016 -0400

    Merge pull request #11820 from pkliczewski/vm_remove_target

    Remove vm triggers targeted refresh
    (cherry picked from commit f866bfecc3a61d42ba833541504c32f82753e069)


Interrupted system call when installing on MacOS Big Sur

I get this output and error when I attempt to build ruby:
simon@Simons-MBP ~ % time rbenv install 3.0.0
Downloading openssl-1.1.1i.tar.gz...
-> https://dqw8nmjcqpjn7.cloudfront.net/e8be6a35fe41d10603c3cc635e93289ed00bf34b79671a3a4de64fcee00d5242
Installing openssl-1.1.1i...
Installed openssl-1.1.1i to /Users/simon/.rbenv/versions/3.0.0

Downloading ruby-3.0.0.tar.gz...
-> https://cache.ruby-lang.org/pub/ruby/3.0/ruby-3.0.0.tar.gz
Installing ruby-3.0.0...
ruby-build: using readline from homebrew

BUILD FAILED (macOS 11.2.1 using ruby-build 20210119)

Inspect or clean up the working tree at /var/folders/7x/tj7wsjgj4nl1g3h6sbjdrf8m0000gn/T/ruby-build.20210226164233.16496.FWB6V6
Results logged to /var/folders/7x/tj7wsjgj4nl1g3h6sbjdrf8m0000gn/T/ruby-build.20210226164233.16496.log

The last lines of the build log are as follows:
compiling inspector.c
-e:4:in `write': Interrupted system call @ rb_sysopen - failure.failed (Errno::EINTR)
        from -e:4:in `<main>'
make[2]: *** [failure.failed] Error 1
make[1]: *** [ext/-test-/cxxanyargs/all] Error 2
make[1]: *** Waiting for unfinished jobs....
compiling profile_frames.c
compiling empty.c
linking shared-object -test-/dln/empty.bundle
linking shared-object -test-/debug.bundle
make: *** [build-ext] Error 2

Not sure why I would be getting an Interrupted system call?

Big Sur 11.2.1   rbenv install 3.0.0. also failed.
➜  ~ CFLAGS="-Wno-error=implicit-function-declaration" rbenv install 3.0.0
Downloading openssl-1.1.1i.tar.gz...
-> https://dqw8nmjcqpjn7.cloudfront.net/e8be6a35fe41d10603c3cc635e93289ed00bf34b79671a3a4de64fcee00d5242
Installing openssl-1.1.1i...
Installed openssl-1.1.1i to /Users/wangxiaofeng/.rbenv/versions/3.0.0
Downloading ruby-3.0.0.tar.gz...
-> https://cache.ruby-lang.org/pub/ruby/3.0/ruby-3.0.0.tar.gz
Installing ruby-3.0.0...
ruby-build: using readline from homebrew
BUILD FAILED (macOS 11.2.1 using ruby-build 20210119)
Inspect or clean up the working tree at /var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.czEIX7
Results logged to /var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.log
Last 10 log lines:
Check ext/readline/mkmf.log for more details.
*** Fix the problems, then remove these directories and try again if you want.
Generating RDoc documentation
/private/var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.czEIX7/ruby-3.0.0/lib/time.rb:3:in require': cannot load such file -- date (LoadError) 	from /private/var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.czEIX7/ruby-3.0.0/lib/time.rb:3:in <top (required)>'
from /private/var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.czEIX7/ruby-3.0.0/lib/rdoc/rdoc.rb:7:in require' 	from /private/var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.czEIX7/ruby-3.0.0/lib/rdoc/rdoc.rb:7:in <top (required)>'
from ./libexec/rdoc:16:in require' 	from ./libexec/rdoc:16:in '
make: *** [rdoc] Error 1
➜  ~

I also got this sometimes on Big Sur. Maybe, It's issues of Big Sur, not ruby-build.

@snibbets @csking119 @hsbt If you're having issues with Interrupted system call, you might try temporarily uninstalling or disabling security applications like Avira, Avast, ESET Endpoint Antivirus, Kaspersky, etc and then re-trying. This solved my similar issue.

Big Sur 11.2.1 rbenv install 3.0.0. also failed.
➜ ~ CFLAGS="-Wno-error=implicit-function-declaration" rbenv install 3.0.0 Downloading openssl-1.1.1i.tar.gz... -> https://dqw8nmjcqpjn7.cloudfront.net/e8be6a35fe41d10603c3cc635e93289ed00bf34b79671a3a4de64fcee00d5242 Installing openssl-1.1.1i... Installed openssl-1.1.1i to /Users/wangxiaofeng/.rbenv/versions/3.0.0
Downloading ruby-3.0.0.tar.gz... -> https://cache.ruby-lang.org/pub/ruby/3.0/ruby-3.0.0.tar.gz Installing ruby-3.0.0... ruby-build: using readline from homebrew
BUILD FAILED (macOS 11.2.1 using ruby-build 20210119)
Inspect or clean up the working tree at /var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.czEIX7 Results logged to /var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.log
Last 10 log lines: Check ext/readline/mkmf.log for more details. *** Fix the problems, then remove these directories and try again if you want. Generating RDoc documentation /private/var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.czEIX7/ruby-3.0.0/lib/time.rb:3:in require': cannot load such file -- date (LoadError) from /private/var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.czEIX7/ruby-3.0.0/lib/time.rb:3:in <top (required)>' from /private/var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.czEIX7/ruby-3.0.0/lib/rdoc/rdoc.rb:7:in require' from /private/var/folders/hc/slkwwjpn5db488pdxb1k1hb80000gn/T/ruby-build.20210227234808.1292.czEIX7/ruby-3.0.0/lib/rdoc/rdoc.rb:7:in <top (required)>' from ./libexec/rdoc:16:in require' from ./libexec/rdoc:16:in
'
make: *** [rdoc] Error 1
➜ ~

@csking119 were you able to install ?


Create an automated installer for linux.

— Creating an automated installer for Linux will help in large scale application deployments across multiple systems and regions.
Deploying this application in GCP or AWS in multi region becomes very easy with this script; you can deploy as many instances you want under 1 min.

Codecov Report

Merging #1404 (a8c343d) into main (97c1e68) will increase coverage by 0.38%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1404      +/-   ##
==========================================
+ Coverage   65.16%   65.55%   +0.38%
==========================================
  Files         119      119
  Lines       12889    12889
==========================================
+ Hits         8399     8449      +50
+ Misses       3818     3764      -54
- Partials      672      676       +4

Impacted Files
Coverage Δ

internal/core/hls_server.go
76.63% <0.00%> (-0.41%)
:arrow_down:

internal/core/webrtc_conn.go
54.56% <0.00%> (-0.34%)
:arrow_down:

internal/core/hls_muxer.go
52.36% <0.00%> (+1.18%)
:arrow_up:

internal/core/rtsp_source.go
52.12% <0.00%> (+1.21%)
:arrow_up:

internal/core/rtmp_source.go
67.80% <0.00%> (+2.05%)
:arrow_up:

internal/core/path.go
73.55% <0.00%> (+3.14%)
:arrow_up:

internal/hls/muxer_variant_fmp4_playlist.go
66.26% <0.00%> (+4.86%)
:arrow_up:

internal/core/source_static.go
72.93% <0.00%> (+6.01%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Hello, the problem here is that this PR adds a third installation method that isn't Windows-compatible and doesn't allow to choose the server version. It also installs the server as a service, which is something not everyone wants to do.
Some software use a bash-based installer, like Docker, and some doesn't, like Helm, and allow users to pick an executable from the release page.
I have to think a little about the implications of this.

Out of curiosity, why did you choose to install the server directly on the EC2 instances and you ruled out Docker / Fargate / ECS / EKS ?


chore(repo): add addon-docs, remove addon-info and storybook-readme

Closes #963
Closes #2418
~Blocked until #2359 and #2336 are merged.~
Summary

removes @storybook/addon-info
removed storybook-readme
replaces them with @storybook/addon-docs
renames all existing MD files to MDX, and uses them as the basis for the new docs tab.

Change List (commits, features, bugs, etc)
Component w/ stories using storybook-readme that were updated

ListBuilder
MapCard
MenuButton
MultSelect
OverflowMenu
Table

Acceptance Test (how to verify the PR)

Clicking the new "Docs" tab (beside "Canvas" at the top left of the main storybook window) for any of the stories above should show their current docs
The "Readme" tab should do longer appear

Regression Test (how to make sure this PR doesn't break old functionality)

All stories should still function as expected

We have a problem with the new docs and modals:

We have a problem with the new docs and modals:

nice catch! I'll copy the MDX file from Carbon to prevent it and give better docs--this probably something we'll need to do eventually anyway, I assume. We were hoping carbon would bundle the MDX and we could just use then, but I don't know if that's going to happen or not.

We have a problem with the new docs and modals:
...
nice catch! I'll copy the MDX file from Carbon to prevent it and give better docs--this probably something we'll need to do eventually anyway, I assume. We were hoping carbon would bundle the MDX and we could just use then, but I don't know if that's going to happen or not.

It is not just the modal, but all stories that use the modal as well :-)


Unable to sign into UI in Ambari after HDF Upgrade - HTTPS issue

Hello,
We have upgraded from HDF <IP_ADDRESS> to HDF <IP_ADDRESS> and the upgrade was successful. We upgraded to use Schema Registry and we successfully added Schema Registry 0.3.0 using Ambari. The existing cluster components were configured to use SSL before we upgraded to <IP_ADDRESS> (Ambari, Ranger, NIFI, Ambari Infra, Ambari Metrics UI's are all using SSL successfully).  When I try to use the Schema Registry UI from Ambari I am not able to bring up the web page.  It looks like the UI link is pointing to https even though we have not configured Schema Registry with SSL.  Example of the URL which Ambari is pointing me to - https://servername.domain.com:7788/  If I try http it reverts back to a https page.
I do not see any documentation about how to configure Schema Registry for SSL.  Normally would point to a keystore or truststore but I cannot seem to find any documentation on the settings for this.
In the registry.log file I see the following error:
WARN   [08:42:25.288] [dw-26] o.e.j.h.HttpParser -  Illegal character 0x16 in state=START for buffer HeapByteBuffer@5d7b223b[p=1,l=212,c=8192,r=211]={\x16<<<\x03\x01\x00\xCf\x01\x00\x00\xCb\x03\x03K\x8f\xD6\xA5\x9e~\x99...\x00\x08\x8a\x8a\x00\x1d\x00\x17\x00\x18\xAa\xAa\x00\x01\x00>>>\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00...\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
WARN   [08:42:25.288] [dw-26] o.e.j.h.HttpParser -  bad HTTP parsed: 400 Illegal character 0x16 for HttpChannelOverHttp@24809a38{r=0,c=false,a=IDLE,uri=null}
Any help would be greatly appreciated.
Thanks,
Kirk

Since posting this I have found this document - http://registry-project.readthedocs.io/en/latest/security.html?highlight=https
I have made changes to the registry.yaml file but the items are overwritten by Ambari.  Any suggestions on what should be added to Ambari  for these items below:
server:
applicationConnectors:
- type: https
port: 8443
keyStorePath: ./conf/keystore.jks
keyStorePassword: test12
validateCerts: false
validatePeers: false
adminConnectors:
- type: https
port: 8444
keyStorePath: ./conf/keystore.jks
keyStorePassword: test12
validateCerts: false
validatePeers: false


Implement DGAPI v2.1

Implementation involves:

[x] Changes to getDetails.

[x] Add introductory price cycles, type and icon url.
[x] Add tests.

[ ] Changes to getPurchases.

[ ] Remove everything except for item id and purchase token.
[ ] Ensure backwards compatibility.
[ ] Add tests.

[ ] Changes to getPurchaseHistory.

[ ] Add get purchase history.
[ ] Add tests.

[ ] Changes to acknowledge.

[ ] Remove acknowledge.
[ ] Add consume.
[ ] Ensure backwards compatibility.
[ ] Add tests.

getDetails changes were made in #350 .


Objectified the Wheel

Moved the game wheel into its own object. All functionality is as before.
Once everyone comments and adds their approval, the last person to approve should merge the PR and let the team know in Slack.

Not sure the checkWheel() call should be in the constructor. Maybe put it in main and make checkWheel public? I guess this depends on how we implement the progression of the game, if we have a Game object or something. Other than that, looks good.

I agree with Alex on the checkWheel() call just because we're still not sure on implementation down the line.  But otherwise I would say approve and we can mess with it next iteration.

I moved the call! Thanks for the comments.


Please allow me to add header to signin/signup page

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I will add header to the signin page this will make UI more interactive to users. And users will be able to navigste easily
Use Case
This allows users to navigate across website easily.
Benefits
No response
Add ScreenShots

No header in this
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Anishkagupta04 please assign me this issue under gssoc level2

@Anishkagupta04  please assign me this issue.
I am GSSOC Contributor.

@Anishkagupta04
hey, I'd like to contribute in this issue.
I have read the Contributing Guidelines.
I'm a GSSOC'24 contributor.
I have starred the repository.


Automatically update layers.json when releasing

We want npm run update to run in the release workflow (to update the layer versions before tagging a release).

Hi, can I work on this?

@Vinitvh sure, that would be most welcome!


An Extra Tutorial on acoustic wave modelling

This is a tutorial on acoustic wave modelling.

The major change is adding initialisation of src and rec using SourceLike Data object and explaining self.propagator.time_loop_stencils_a = src.add(m, u) + rec.read(u) and rephrasing the part about the seismic data initialisation.

Update the origin,and spacing from 2d to 3d in the example code to be consistent with the title of the tutorial, Acoustic Wave Modelling in 3D.


Using as argument of a factory class

Argument 1 passed to Illuminate\Database\Eloquent\Factory::{closure}() must be an instance of Ybazli\Faker\Faker, instance of Faker\Generator given
here is my Factory class
$factory->define(Buyer::class, function (YbazliFaker $fakoor) {
    return [
        'name' => $fakoor->firstName(),
        'family' => $fakoor->lastName(),
        'mobile' => $fakoor->mobile(),
        'remember_token' => Str::random(10),
        'reagent_self' => Str::random(7),
        'activation_sms' => rand(100, 999),
        'province_id' => 21,
        'city_id' => 296,
        'is_active' => 1,
    ];
});`

I tried diffrent ways of class name and it's varible but it does not help , and i also test
$fakoor

varible with
isset

but it doesn't help

I declare it with
Ybazli\Faker\Facades\Faker

and it was wrong , the correct way is with
Ybazli\Faker\Faker


Zone, isolates and Worker are poorly documented

What steps will reproduce the problem?

https://api.dartlang.org/apidocs/channels/stable/#dart-async.Zone
https://api.dartlang.org/apidocs/channels/stable/#dart-isolate
https://api.dartlang.org/apidocs/channels/stable/#dart-dom-html.Worker

Zone

The documentation is not detailed. The concepts are defined via uncommon terms. For example, Zone is defined via "dynamic extent", which is not a common term (only that it comes from Common Lisp :), sorry couldn't resist). Same goes for the concepts "bind" and "register". The docs use casual language (e.g. "gives the zone a chance to wrap the callback", or "asynchronous version of"), which is ok to get an intuitive sense of what they mean, but they should be backed by details using a stricter language. Some terms are defined recursively (e.g. registerCallback "registers the given callback"), which is not helpful.
isolates

It's safe to say this library is not documented at all. The link provided at the top is broken. It probably meant to link to https://www.dartlang.org/docs/dart-up-and-running/contents/ch02.html#isolates, but even there you won't find any details.
Worker

The docs are an excerpt from MDN, which document the JavaScript API. For instance, Dart doesn't have XMLHttpRequest. There is also no discussion about the differences between isolates and workers. In fact the docs for isolates overload the meaning of "worker" by describing isolates as "independent workers".

The article is gone, i will never be able to understand zone.

The article is gone, i will never be able to understand zone.

@PandaGeek1024 the article on zones is still available though archived.

What I find very undocumented is the interaction between Zones and Isolates.
I'm currently trying to understand why a test I'm trying to write using FakeAsync (which makes use of zones) doesn't seem to work with a stream linked to an isoloates SendPort and there seems to be no documentation at all about how Zones work (or don't) with Isolates.


gh-58 | feat:adding version endpoint

Relevant Issue
Things added as part of the PR.

added a version endpoint in /internal/mux/server.go
Implemented basic version subcommand for indexer, gateway, tracker.
Implemented a version endpoint in extractor

@mjpitz , The build seems to be failing due to go-groups.
I'm not familiar with this command and google seems to be returning nothing. Can you tell me what I need to do to fix this?

@pavan-kalyan : from the build output:
run make fmt and commit changes:
 internal/mux/server.go | 2 +-

Yes, I have tried that:
➜  depscloud git:(gh-58) make fmt
cd extractor && npm run lint

><EMAIL_ADDRESS>lint /home/pavan/dev/depscloud/depscloud/extractor
> eslint --fix src/**/*.ts

go-groups -w ./deps ./gateway ./indexer ./tracker ./internal
make: go-groups: No such file or directory
make: *** [Makefile:21: .fmt] Error 127
➜  depscloud git:(gh-58)

I have also tried the other commands
➜  depscloud git:(gh-58) gofmt -s -w internal/mux/server.go                                           <<<
➜  depscloud git:(gh-58) git status
On branch gh-58
Your branch is up to date with 'origin/gh-58'.

nothing to commit, working tree clean

So you need to download go-groups. make build-deps will download it. gofmt doesn't re-order / group imports.

Resolves gh-58

This looks good. One more set of changes (re-use objects where possible). I wasn't sure if we wanted c.Name or c.Command.Name.

According to the docs for urfave/cli. There doesn't seem to be a direct Name variable (if I'm reading this right).

Thank you @pavan-kalyan for your pull request!

If you're looking for a great next issue might I recommend https://github.com/depscloud/depscloud/issues/3 ?

Thanks for guiding me through this!
Let me take a look at #3


Use websockets for the wasm sides as well.

Idea:

Use websockets for cosmos chains to run from current height.
We can query for older txns as well using search txns api, when we have to restart from older height.

We already have exact implantation on centralized relayer.

IBC relayer seems to be quite stable for now, so we won't be making this change anytime soon. It'll just be on the icebox, and we'll revisit it if needed later.

#223


Support for knowledge base

Support for a private knowledge base. Like Azure cognitive search + OpenAI Service.

It's on our roadmap, stay tuned

so good

Hi, related to this, if I copied a bunch of website text into the character profile, would that work in terms of enabling a user to ask questions about the content and have the bot respond with the information in the character profile? So, basically, I'm wanting to create a Q&A bot that can provide specific information. Thanks!

@scooter7  yes. make a new character of your choice and add your data in the data folder. you might need to install some py libraries. for example for pdf pypdf and etc.

https://github.com/StanGirard/quivr

👍You guys are amazing! A knowledge base that supports uploading external files has been implemented.
But I also want to make a request to improve the product and users:
Can a knowledge base be built from data generated by the current system (for example, chat records)?
Or the website (for example, Twitter, Weibo). I saw quivr has this function, and @Shaunwei is a contributor, so it should be familiar.


Problems with the "Overseer" sidebar

Hi,
since the most recent focus.nvim changes, the Overseer sidebar isn't ignored anymore. Before, it worked out of the box, but now, even adding it to the disabling autocommand has no effect. As far as I can tell it has filetype OverseerList and buftype nofile. This is my lazy.nvim config for focus:
return {
	"nvim-focus/focus.nvim",
	lazy = false,
	config = function()
		require("focus").setup({
			ui = {
				relativenumber = true,
				absolutenumber_unfocussed = true,
				signcolumn = false,
			},
		})
		-- Disable focus autoresize for specific filetypes and buftypes
		local augroup = vim.api.nvim_create_augroup("FocusDisable", { clear = true })
		local ignore_buftypes = { "nofile", "prompt", "popup" }
		vim.api.nvim_create_autocmd("WinEnter", {
			group = augroup,
			callback = function(_)
				if vim.tbl_contains(ignore_buftypes, vim.bo.buftype) then
					vim.w.focus_disable = true
				else
					vim.w.focus_disable = false
				end
			end,
			desc = "Disable focus autoresize for BufType",
		})
		local ignore_filetypes = { "starter", "minifiles", "Navbuddy", "noice", "neo-tree", "OverseerList" }
		vim.api.nvim_create_autocmd("BufWinEnter", {
			group = augroup,
			callback = function(_)
				if vim.tbl_contains(ignore_filetypes, vim.bo.filetype) then
					vim.w.focus_disable = true
				else
					vim.w.focus_disable = false
				end
			end,
			desc = "Disable focus autoresize for FileType",
		})
	end,
}

@willothy ^^

Thanks for the ping! I'll look into this ASAP.
@yngwi mind sharing your overseer config or a minimal init?

Thank you, it works again as expected!


airwave: fix VST SDK and Qt plugins

Motivation for this change

VST SDK 3.6.8 (vstsdk368_08_11_2017_build_121.zip) has fallen off the Internet.
VST SDK 3.6.14 (vst-sdk_3.6.14_build-24_2019-11-29.zip) can be automatically downloaded from Steinberg's servers or from GitHub but does not contain the required VST2 SDK headers.

Things done

Made the package use VST SDK 3.6.6 (vstsdk366_27_06_2016_build_61).
Raised an issue on the Steinberg VST SDK GitHub.
Also added qt5.wrapQtAppsHook into nativeBuildInputs as per #65399 (qt5.mkDerivation is not an option because of multiStdenv.mkDerivation - but hey, now it builds and runs!)

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Also added qt5.wrapQtAppsHook into nativeBuildInputs as per #65399 (qt5.mkDerivation is not an option because of multiStdenv.mkDerivation - but hey, now it builds and runs!)

You can do mkDerivationWith multiStdenv.mkDerivation

Closing due to inactivity. Feel free to reopen the discussion.

Closing due to inactivity. Feel free to reopen the discussion.


Auto discovery of dashboards/alert rules/ other configurations by the dynatrace operator

Hi All,
Grafana dashboards are automatically discovered from the ConfigMaps in the deployed namespace. If a ConfigMap has been created with the grafana_dashboard label set to "1" , then the JSON encoded dashboard in the ConfigMap will be imported into Grafana.
Same way, if the dynatrace operator detects and auto imports automatically based on certain label, will ease our life for the automation.
Are there any plans to support this feature ?

Hi, this is currently not supported and also not planned. I will take that the responsible Project Manger to follow that idea up.


Add menu item to Tools menu to unlock the url so it will work without admin rights

Without admin rights is impossible.


corrupting disk image

ehh - hate to be the guy to cry: wolf!
but I've just spoiled my development.sqlite3 with 10MB of payload - which is not a big deal (but if my production with 50 times that will perform likewise ...)
couldn't help notice the mention on your gem in the plot and as this is my first corrupted DB file since MySQL changed their password strategy back in the day, I'm somewhat edgy 🥹
anything I can do to rule out enhancedsqlite3 being the culprit?
An error occurred when inspecting the object: #<ActiveRecord::StatementInvalid: SQLite3::CorruptException: database disk image is malformed>
An error occurred when running Kernel#inspect: #<ActiveRecord::StatementInvalid: SQLite3::CorruptException: database disk image is malformed>
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/sqlite3-2.0.1-arm64-darwin/lib/sqlite3/statement.rb:36:in `prepare'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/sqlite3-2.0.1-arm64-darwin/lib/sqlite3/statement.rb:36:in `initialize'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/sqlite3-2.0.1-arm64-darwin/lib/sqlite3/database.rb:166:in `new'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/sqlite3-2.0.1-arm64-darwin/lib/sqlite3/database.rb:166:in `prepare'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/sqlite3/database_statements.rb:36:in `block (2 levels) in internal_exec_query'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:997:in `block in with_raw_connection'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activesupport/lib/active_support/concurrency/null_lock.rb:9:in `synchronize'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:969:in `with_raw_connection'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/sqlite3/database_statements.rb:33:in `block in internal_exec_query'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activesupport/lib/active_support/notifications/instrumenter.rb:58:in `instrument'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:1112:in `log'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-enhancedsqlite3-adapter-0.7.0/lib/enhanced_sqlite3/adapter.rb:67:in `block in log'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activesupport/lib/active_support/tagged_logging.rb:139:in `block in tagged'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activesupport/lib/active_support/tagged_logging.rb:39:in `tagged'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activesupport/lib/active_support/tagged_logging.rb:139:in `tagged'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activesupport/lib/active_support/broadcast_logger.rb:240:in `method_missing'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/activerecord-enhancedsqlite3-adapter-0.7.0/lib/enhanced_sqlite3/adapter.rb:67:in `log'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/sqlite3/database_statements.rb:32:in `internal_exec_query'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:114:in `query'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:110:in `query_values'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/abstract/schema_statements.rb:35:in `data_sources'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/schema_cache.rb:430:in `block in tables_to_cache'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/abstract/connection_pool.rb:399:in `with_connection'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/schema_cache.rb:429:in `tables_to_cache'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/schema_cache.rb:313:in `data_source_exists?'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/schema_cache.rb:38:in `data_source_exists?'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/connection_adapters/schema_cache.rb:182:in `data_source_exists?'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/model_schema.rb:418:in `table_exists?'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/activerecord/lib/active_record/core.rb:358:in `inspect'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb/inspector.rb:101:in `inspect'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb/inspector.rb:101:in `bind_call'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb/inspector.rb:101:in `rescue in inspect_value'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb/inspector.rb:95:in `inspect_value'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb/context.rb:639:in `inspect_last_value'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb.rb:1387:in `output_value'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb.rb:1057:in `block (2 levels) in eval_input'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb.rb:1380:in `signal_status'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb.rb:1041:in `block in eval_input'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb.rb:1120:in `block in each_top_level_statement'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb.rb:1117:in `loop'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb.rb:1117:in `each_top_level_statement'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb.rb:1040:in `eval_input'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb.rb:1021:in `block in run'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb.rb:1020:in `catch'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/irb-1.13.1/lib/irb.rb:1020:in `run'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/railties/lib/rails/commands/console/irb_console.rb:106:in `start'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/railties/lib/rails/commands/console/console_command.rb:59:in `start'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/railties/lib/rails/commands/console/console_command.rb:8:in `start'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/railties/lib/rails/commands/console/console_command.rb:87:in `perform'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/thor-1.3.1/lib/thor/command.rb:28:in `run'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/thor-1.3.1/lib/thor/invocation.rb:127:in `invoke_command'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/railties/lib/rails/command/base.rb:178:in `invoke_command'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/thor-1.3.1/lib/thor.rb:527:in `dispatch'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/railties/lib/rails/command/base.rb:73:in `perform'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/railties/lib/rails/command.rb:71:in `block in invoke'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/railties/lib/rails/command.rb:149:in `with_argv'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/railties/lib/rails/command.rb:69:in `invoke'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/rails-e3867798a001/railties/lib/rails/commands.rb:18:in `<main>'
<internal:/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
<internal:/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
/Users/walther/.asdf/installs/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'

This is the first I've seen, so I don't have an immediate thought that the gem caused it. We will need to investigate what all you've been doing locally lately, as that stacktrace comes after the corruption occurred. Read thru this documentation page and let me know if anything jumps out as something that might have occurred in your case: https://www.sqlite.org/howtocorrupt.html

ok - so I see a number of mentions of 'multiple processes' which points me to 'reader' / 'writer' - and in my case I have the database.yml like this
development:
  writer:
    <<: *default
    pool: 1
    database: storage/development.sqlite3
  reader:
    <<: *default
    readonly: true
    database: storage/development.sqlite3

and the solid_queue reading like this:
# config/solid_queue.yml
dispatchers:
  - polling_interval: 1
    batch_size: 500
    recurring_tasks:
      background_job_scheduler:
        interval: 60
        class: BackgroundManagerJob
        queue: default
        schedule: every minute
        enabled: true

and the development configuration like
# config/environments/development.rb
  ...
  config.enhanced_sqlite3.isolate_connection_pools = true
  config.solid_queue.connects_to = { database: { writing: :writer, reading: :reader } }
  ...

This morning I started by loading the app in Chrome - clicking through 4-5 views and then started on my first issue (something time_zone related); finished that, committed the code and then on to #2 which was adding a better root_path => a dashboard. Which meant for me to rails g scaffold dashboard ... and my best guess is that once I started hitting the database after that (successful) migration, things started going south.
I recall rebooting my MBAir this morning after a system upgrade - but I did use the app successfully for at least 10-15min before all was lost.
I am in no way pointing any fingers at you nor others -- only reporting what I see, and hoping by doing so to perhaps keep others from getting "burnt"
cheers,
W

And I take no offense and didn't feel you were pointing fingers. I want to get a better sense of what corrupted your database as well, because we absolutely want to ensure that we don't walk people into corrupt databases. I appreciate the report.

great!
and - yes - I do use the same DB for both web instance and solid queue

risked deploying my changes for the day - and they seem to have had no off-setting effect this far.
One of the issues being labeled "SQLite Configuration Errors" is wrong usage of protection mechanisms but unless enhancedsqlite3 chances any of them I don't see it any other way than me having to chalk it up on bad hardware or macOS screwing with the file descriptors - but thanks again for listening and responding so fast!

You should almost certainly use a separate database for jobs.

What makes you say that?
imho:
I was taught ages ago that a 1-file database system is not a proper db - but if 37-signals dare experimenting with SQLite so do I
As for the distribution of work, I’m aware that there will be scalability paths to take once the product starts saturating the current VM

Den 27. maj 2024 kl. 23.40 skrev Stephen Margheim @.***>:
You should almost certainly use a separate database for jobs.
—
Reply to this email directly, view it on GitHub https://github.com/fractaledmind/activerecord-enhancedsqlite3-adapter/issues/18#issuecomment-2134071426, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABPFXOENQBR4GEN47QOVMLZEOR5FAVCNFSM6AAAAABIK3QVHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUGA3TCNBSGY.
You are receiving this because you modified the open/close state.


The "Overview Dashboard" terraform code isn't static

The "tf/dashboards/overview-.tf" file is constantly changing, each time I run "slogen . --apply --clean".
I believe this is because the map is unordered and the rows are being pulled out arbitrarily: https://github.com/SumoLogic-Labs/slogen/blob/main/libs/overview.go#L193
This means that my terraform code changes on each run, rather than being hermetic.
This is a low priority, but it would be nice to have these rows sorted.

Agreed, all the need loops in templates should be sorted by the resource name.
should be an easy change.

fixed in https://github.com/SumoLogic-Labs/slogen/pull/51/commits/9cc3f5932c277d26bbd5a5236263d4a638c2049d


Refresh access token after timeout

Once the 60 mins expire, we need to refresh the access token.  get this done

When I first did auth, it was via svelte functions coz I wanted somewhere easy to host endpoints (vercel).  Now that we have the api running on cloud run, moving auth end points in there.

Done today


Vickel: Blacklist gefluegelhof-harter.de

Vickel requests the blacklist of the website gefluegelhof-harter\.de. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

gefluegelhof-harter.de seems to have been hacked. (Gefluegelhof=chicken-farm in German) in google or ddg it shows a resume in Chinese characters which translates to a product catalog which has nothing to do with chicken (CHANEL 1990s Collection Catalog, etc. -. CHANEL 1990s), hence my blacklist request out of the box

Rejected by Jeff Schaller in Charcoal HQ. Reason: 'based on my interpretation of the Guidance, this doesn't yet qualify for blacklisting'


Using this theme causes Emacs to crash or to MacOS to close Emacs for no reason

Hello, the other day I was trying old terminal fonts in Emacs and saw this theme to simulate a good old console but Emacs was automatically closed with no reason, I assume it was the fonts so I remove them. But today trying this theme again I get the same behavior (no weird fonts this time), any idea what is causing this? I'm on Mac OS Mojave 10.14.5.

I have seen Emacs crash when changing themes repeatedly in one session - it's likely a bug in the theme system, not something specific to this theme. It happens to me every time I download a new package with many themes and try them all out.

That sounds weird, and perhaps is what is happening, but why only using this theme? it doesn't crash for you? (while using this theme?).

Sorry - it doesn't happen for me; I only experience theme related crashes when changing themes many times per session. The theme itself is nothing but data - it uses standard color names and a few hex constants, that's all.

OK, I take that back - I finally did reproduce that on one machine.

Mojave -- GNU Emacs 26.2 (build 1, x86_64-apple-darwin18.2.0, NS appkit-1671.20 Version 10.14.3 (Build 18D109)) of 2019-04-12

However,  as I said before, the theme is just data. There must be a bug in the theme system to cause a previously valid theme to cause stability problems.

@ZzAntares  I tried Emacs 26.1 for OS X on Mojave, and it doesn't crash. It seems to be a problem introduced in Emacs 26.2. You can download 26.1 from https://emacsformacosx.com/builds

Great!, let me see if I can downgrade from brew...


Screencast of using Opossums Hystrix Metrics stream inside of MSA

Once we have all the pieces of the Hystrix metrics inside opossum, we should create a screencast that we can share out that shows our progress.

Looking forward to this!

created: https://youtu.be/ElBVU8PYc5g


Approach

Learned the k8s fundamentals and the operator pattern
Created a new operator using the operator-sdk
Compared differences between the new operator and this current operator
Read the k8s docs about deprecations
Updated the Go version and other deps accordingly
Tested the updated operator against a local minikube cluster

Related PRs

https://github.com/wso2/k8s-wso2is-operator/pull/11

Test environment
This updated version of the operator has been tested and works with,

Minikube v1.29.0
k8s v1.26.1 on docker 20.10.23

Learning

Followed official k8s docs, operator-sdk docs
Followed tutorials including https://www.youtube.com/watch?v=ha3LjlD6g7g

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Theano implementation for enwik8

Nice to have the fix for stacking RHN layers! We implemented support for it, but haven't really tried to see how much it improves results. Did you run any experiments yet?

Hi, yeah, that indeed was missing in code before. I haven't run stacked RHN layers experiments.
With this second version of code I have ran on PTB to completion (reached the SOTA results), and am still running on enwik8. Attached are logs.
theano_rhn_ptb_933626850.log.txt
theano_rhn_enwik8_750738364.log.txt

Great, thanks! I'm merging this now, and you can submit another PR in case you have any problems with the enwik8 run.


How to identify a VM running pod?

Please add reliable way to identify pods that are actually running the VMs (i.e. virt-launcher-* pods).
Currently  AFAIK it can only be done by parsing container name or tag kubevirt.io/app=virt-launcher.
I general it would be nice to have a way to reliably recognize various parts of KubeVirt (virt-handler, virt-launcher, libvirt, ... pods) on API level for troubleshooting and UI purposes.

Roman mentioned today the kubevirt.io/domain tag that matches the VM name.

Ok. So @rmohr is kubevirt.io/domain tag stable enough to by used by other systems? If yes we can close this issue I guess.

@jniederm it is possible that we will rename it to kubevirt.io/vm, which I think makes more sense. Apart from that, there will always be such a label.

Thanks.
Just a recap: pod running a VM is identified by tag kubevirt.io/domain which is expected to be renamed to kubevirt.io/vm.


assertDefined getDocumentHighlights

From 3.1.3 (occurrences)
Error: Debug Failure.
    at Object.assertDefined (tsserver.js:1446:24)
    at tsserver.js:114911:92
    at Object.map (tsserver.js:442:29)
    at getDocumentHighlights (tsserver.js:114911:42)
    at Object.getOccurrencesAtPosition (tsserver.js:114899:31)
    at IOSession.Session.getOccurrences (tsserver.js:122233:64)
    at Session.handlers.ts.createMapFromTemplate._a.(anonymous function) (tsserver.js:121766:61)
    at tsserver.js:123086:88
    at IOSession.Session.executeWithRequestId (tsserver.js:123077:28)
    at IOSession.Session.executeCommand (tsserver.js:123086:33)
    at IOSession.Session.onMessage (tsserver.js:123106:35)
    at Interface.<anonymous> (tsserver.js:124369:27)
    at emitOne (events.js:116:13)
    at Interface.emit (events.js:211:7)
    at Interface._onLine (readline.js:282:10)
    at Interface._normalWrite (readline.js:424:12)
    at Socket.ondata (readline.js:141:10)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at addChunk (_stream_readable.js:263:12)
    at readableAddChunk (_stream_readable.js:250:11)
    at Socket.Readable.push (_stream_readable.js:208:10)
    at Pipe.onread (net.js:594:20)

This is failing at Debug.assertDefined(program.getSourceFile(f)) in getDocumentHighlights. This  indicates that there was a getOccurrencesAtPosition request for a file that was not in the program. It would help to know if there was previously an open request on that file.

Closing this so that we can reopen when there is stack with change #28242 to investigate this further.


Multiple Slacks support

Hi
Is there a canonical example of how to use this API to support multiple Slack workspaces, as more than one team installs the Bot?
Do I need to create multiple Slack Client or RTM objects ?

I would assume you need one client per workspace, instantiated using a token that is authorized for that org. what exactly is the use case?

That's how I ended up implementing it in the meantime.
The use case is a Slack app that multiple people can independently install.
As it stands right now I have to capture the bot access tokens the OAuth flow gives me upon install, add them to my config file and restart the binary.

are we talking about listing an app on the slack app directory so that other teams can download it?

Yes, I've made my app public and available to other Slacks, although not gone as far as publishing it on the Slack app directory

Yes, a client must be instantiated per workspace (token). and the users of this library are responsible for determining how those tokens are stored, managed, and used.


APIM Backend type Pool - mandatory field protocol is not supported

Bicep version
Bicep CLI version 0.25.3 (862708594a)
Describe the bug
I'm trying to create a backend type Pool in APIM. I'm using simple guide from here
Once I'm trying to deploy it I'm getting error:
az deployment group create --name demoRGDeployment --resource-group GPT --template-file backends.bicep

{"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/eba19cb8-af90-44c2-ac0b-f0a65149efa4/resourceGroups/GPT/providers/Microsoft.Resources/deployments/demoRGDeployment","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"protocol","message":"Protocol is not supported"}]}]}}

and once I comment out protocol line I'm getting error that protocol is mandatory:
az deployment group create --name demoRGDeployment --resource-group GPT --template-file backends.bicep                                        Warning BCP035: The specified "object" declaration is missing the following required properties: "protocol". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]

{"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/eba19cb8-af90-44c2-ac0b-f0a65149efa4/resourceGroups/GPT/providers/Microsoft.Resources/deployments/demoRGDeployment","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"protocol","message":"'protocol' should not be empty."}]}]}}

To Reproduce
Definition of object:
resource symbolicname 'Microsoft.ApiManagement/service/backends@2023-05-01-preview' = {
  name: 'hyp-test-openapi/myBackendPool'
  properties: {
    description: 'Load balancer for multiple backends'
    type: 'Pool'
    protocol: 'https'
    url: 'https://example.com'
    pool: {
      services: [
        {
          id: '/backends/hyptest'
        }
        {
          id: '/backends/westus'
        }
      ]
    }
  }
}

I am getting the same error. It seems like a bug. If bicep value of protocol is 'https' it fails with this error, if it is 'http' it passes.


Ability to run query on Azure MySQL ?

Issue Type: Feature Request
It would be nice to be able to run Azure MySQL from Azure Data Studio.
Azure Data Studio version: azuredatastudio 1.2.4 (1ebfd0235690ad044ed2874a02e65188f5fea01c, 2018-11-02T21:50:52.634Z)
OS version: Windows_NT x64 10.0.17134

@datauduong we're tracking the request to add additional relational databases with this issue https://github.com/Microsoft/azuredatastudio/issues/56.  I'll close this as a duplicate since we don't want to have a distinct issue for each possible DB.  Though we are certainly prioritizing databases hosted on Azure higher.


Simplify API with React Hooks/Optional Implicit Behaviour

Should be relatively painless (for consumers) as everything is already a render function. Defining what animations you want to happen could be tricky though. And the collector behaviour we have now probably would need to be re-written. Hmm.
Ignoring implementation details the API could be something like this?
import { useBaba, revealMove, circleExpand, wait } from 'yubaba';

const Component = () => {
  // Each animation is now a function, call it with or without args.
  const { ref, style, className } = useBaba('my-baba', [ // lmao this almost sounds like yubaba. i like it.
    revealMove({ duration: 400 }),
    wait(),
    circleExpand({ background: '#ccc' }),
  ], {}); // Third arg has optional props such as "in" prop in current Baba component.

  // alternatively we could have a indefinite args where the last one is dynamically the optional props. would have some perf overhead.
  useBaba('my-baba', revealMove(), wait(), circleExpand(), {});

  return
;
};

If we compare the above to todays world:
import Baba, { Wait, RevealMove, Expand } from 'yubaba';

<Baba name="my-baba">
  <RevealMove duration={400}>
    <Wait>
      <CircleExpand background="#ccc">
        {({ ref, style, className }) =>
}
      </CircleExpand>
    </Wait>
  </RevealMove>
</Baba>

Much simpler end result with the react elements, however the initial setup seems to be.. a more verbose API.

We'd also want a better API internally for animations.
Today it looks like:
class Animation extends React.Component {
  beforeAnimate = (data, onFinish, setChildProps) => {
  };

  animate = (data, onFinish, setChildProps) => {
  };

  render() {
    const { children } = this.props;

    return (
      <Collector
        data={{
          action: 'animation',
          payload: {
            beforeAnimate: this.beforeAnimate,
            animate: this.animate,
          },
        }}
      >
        {children}
      </Collector>
    );
  }
}

If we were to re-imagine using hooks, perhaps it wouldn't even need to be a component - just a function that returns callbacks. Making the entire collector implementation redundant...
const animation = () => ({
  action: 'animation',
  beforeAnimate: (data, onFinish, setChildProps) => {},
  animate: (data, onFinish, setChildProps) => {},
});

Simpler yes - but it also puts in the restriction of not allowing any instance state. Maybe that's actually a good thing though.

Including the baba manager component as well (thoughts: is baba manager considered a parent here of the baba?)
const manager = useBabaManager(/* optional name if multiple child babas */ 'my-baba');
const baba = useBaba('my-baba', revealMove(), wait(), circleExpand());

Next thought:
How could we compose animations with hooks?

Currently it's render props everywhere. I think the ideal state (considering we still need to use React Context to communicate between some components) is going to be a mix of hooks and components.
import { useMotion, useMove, useCircleExpand } from '@element-motion/core';

() => {
  // Creates a motion component dynamically.
  // Use a component so we can pass around context as needed.
  const Motion = useMotion([
    // Motion hooks so we can memoize over the react lifecycle
    useMove(),
    useCircleExpand(),
  ]);

  return (
    <Motion>
      /* Implicitly pass down className/styles */

hello world

    </Motion>
  );

  return (
    <Motion>
      /* Explicitly pass down className/styles */
      {motion =>
hello world
}
    </Motion>
  );
}


Improve 'Basic sample' document

[ ] The 'Basic sample' document has some typo/wording errors;
[ ] Example codes may have some typos also,
[ ] Some parts may be more accurate or helpful;

Getting back on this, i've only found a very few of typo to fix.
I'm closing this issue until some things are found again, they should be explicitly reported here so i can fix them.


Only publish sdist

Pull Request Test Coverage Report for Build 41

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 39:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


feat: rtk swapper queries

Description
Adds swapperApi with getUsdRate and getTradeQuote endpoints.

getUsdRate partially implemented
getTradeQuote not yet used due to current swapper architecture

Note, the getUsdRate lib method is still called a lot of times (so the network tab is only slightly better) as its currently being used as a hacky way to check for supported swapper pairs. It's gross, but PR does not intend to change that logic.
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A
Risk
Medium - touches swapper rate queries.
Testing
Use the trade widget and check rates when selecting sell asset, buy asset, and using a fiat amount.
Screenshots (if applicable)
N/A

Looks legit. We could probably further improve swapper performance by looking at caching optimizations within the swappers themselves but this is great

This is good to go once Cypress unrugs itself and CI goes green.


python311Packages.semver: 3.0.0 -> 3.0.1

Diff: https://github.com/python-semver/python-semver/compare/refs/tags/3.0.0...3.0.1
Changelog: https://github.com/python-semver/python-semver/releases/tag/3.0.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.


Github project is missing label static-site-generator

I think it makes sense that you add the label static-site-generator to this github project.

Makes sense, we have it in our npm keywords:
https://github.com/netlify/netlify-cms/blob/2787ad233830570334368f12d79caae6156959d1/packages/netlify-cms/package.json#L19


upgrade problem, 0.9.0 i encounter the problem

[+] Running 2/0
✔ Container node-090-execution-1  Cre...                                  0.0s
✔ Container node-090-node-1       Created                                 0.0s
Attaching to execution-1, node-1
execution-1  | INFO [06-26|07:20:39.002] Starting geth on an OP network...        network=base-mainnet
execution-1  | INFO [06-26|07:20:39.002] Bumping default cache on mainnet         provided=1024 updated=4096
execution-1  | INFO [06-26|07:20:39.002] Enabling metrics collection
execution-1  | INFO [06-26|07:20:39.002] Enabling stand-alone metrics HTTP endpoint address=<IP_ADDRESS>:6060
execution-1  | INFO [06-26|07:20:39.002] Starting metrics server                  addr=http://<IP_ADDRESS>:6060/debug/metrics
execution-1  | INFO [06-26|07:20:39.003] Maximum peer count                       ETH=100 total=100
execution-1  | INFO [06-26|07:20:39.005] Smartcard socket not found, disabling    err="stat /run/pcscd/pcscd.comm: no such file or directory"
execution-1  | Fatal: Failed to raise file descriptor allowance: operation not permitted
execution-1  | Fatal: Failed to raise file descriptor allowance: operation not permitted
execution-1 exited with code 1
node-1       | waiting for execution client to be ready
node-1       | waiting for execution client to be ready
node-1       | waiting for execution client to be ready
node-1       | waiting for execution client to be ready
node-1       | waiting for execution client to be ready

btw i already increase ulimit by myself...


0.8.0

Coverage remained the same at 100.0% when pulling 7c0dc2c2e75ca8b49ff5a89b62ecd4155699a7d5 on develop into 767057f68c8d9a1eb61c356099a143e69917afb2 on master.

Coverage remained the same at 100.0% when pulling 7c0dc2c2e75ca8b49ff5a89b62ecd4155699a7d5 on develop into 767057f68c8d9a1eb61c356099a143e69917afb2 on master.


split parameters and future proof depsOnly flag

ran local tests on this one. the previous all in one string was not working as intended.

Thanks for your PR, but I already included the (same) fix to the problem in https://github.com/Bedrock-OSS/regolith/pull/227. I just didn't merge it yet or open PR for that, but there is a draft with exactly the same fix.


[Feature]: make graph image for README.md with html

Package Scope

[ ] Add to an existing package
[ ] New package

Package name:
Overview

Describe the solution you'd like

Additional context

No plan


Cache classes.length

Makes loop faster. The effect of course won't be huge with small arrays, but if you care about performance than you might as well do it.

Codecov Report

Merging #6 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #6   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          13     13
  Branches        6      6
=====================================
  Hits           13     13

Impacted Files
Coverage Δ

src/index.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


New logo/icon proposal

Good day sir. I am a graphic designer and i am interested in designing a logo for your good project. I will be doing it as a gift for free. I just need your permission first before I begin my design. Hoping for your positive feedback. Thanks

Hello @mansya , thanks for the initiative! we appreciate your help, but we already have one and do not have a plan to update it as of now.


Support symbolic links in input files

This PR:

adds a step to model setup to resolve the input directory paths to absolute paths and resolve symlinks.
pass follow_symlink=True to copy commands when copying config files. However this is already a default value but I added in so it clear in the code that it's intentional.
more tests for the above

In 0daf9115b65468e05f1db4bd8285fdc9a896c923, I had just one test that would run payu setup once and test that inputs, configuration files and executables that were set up as expected. In 6d975159f4102ac184ab13544f1dbbb451e2225e, I split up the tests to try(?) make it simpler to read and have one test for one thing. My concern was that it would make running tests slower as were running a payu setup multiple times. It ended up only adding a couple seconds to the tests..
To check how current manifests are changed due to these changes, I ran payu setup for release-1deg_jra55_ryf branch in access-om2-configs(https://github.com/ACCESS-NRI/access-om2-configs/tree/release-1deg_jra55_ryf). One of the full path changes are in input.yaml manifest are:
 work/INPUT/JRA55_MOM1_conserve2nd.nc:
-  fullpath: /g/data/vk83/experiments/inputs/access-om2/remapping_weights/JRA55/global.1deg/2020.05.30/JRA55_MOM1_conserve2nd.nc
+  fullpath: /g/data/vk83/configurations/inputs/access-om2/remapping_weights/JRA55/global.1deg/2020.05.30/JRA55_MOM1_conserve2nd.nc
   hashes:
-    binhash: abe66e4b33cbb75d25c010ea5f96f053
+    binhash: 3ba86d1ae2c7641a29dce1179c55ad64
     md5: 00be8ec0f1126055b65dc68178ce4eb5

(as /g/data/vk83/experiments/ is a symlink for /g/data/vk83/configurations)
Closes #385
Closes #450

coverage: 56.131% (+0.2%) from 55.951%
when pulling 6d975159f4102ac184ab13544f1dbbb451e2225e on ACCESS-NRI:450-support-symbolic-links
into 68d8482e5307af62603431fe95f1426a28056948 on payu-org:master.


Skipped reloading System Manager Configuration

Describe the issue
When I install packages using pacman, it skips reloading the SystemManager Configuration. The reason being Current root is not booted. I can very easily ignore this because it has not caused any problems as of yet.
To Reproduce
I don't exactly know which packages cause this problem, but the packages that have something to do with the system cause this issue.
Expected behaviour
It should refresh the System Manager Configuration.
Enviroment:

Windows build number: 10.0.19042.450
Security Software: NA
WSL version 1/2: WSL 2
ArchWSL version <IP_ADDRESS>
ArchWSL Installer type zip clean
Launcher version 20040300

I moved to ArchWSL2 and this issue is not present there so I am closing this issue.

Could you link to ArchWSL2? I'm still on this one and haven't found a migration path.

I have same problem like you when I am installing package via pacman:
erven2016@DESKTOP-14AL006 ~ $ sudo pacman -S openssh
[sudo] password for erven2016:
warning: openssh-9.0p1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) openssh-9.0p1-1

Total Installed Size:  4.19 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation?
  Skipped: Current root is not booted.
(2/3) Creating temporary files...
/usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to resolve specifier: uninitialized /etc detected, skipping
All rules containing unresolvable specifiers will be skipped.
(3/3) Arming ConditionNeedsUpdate...


remove reference of namespace istio-system

What this PR does / why we need it:
User should be creating the rules in whatever namespace they would like... so that they can actually view them.  Else, if I don't have access to istio-system, I won't be able to view my rules.
I noticed later on in the actions section, we still have namespace reference in there.  Given default is the namespace we use in bookinfo, it makes sense start with that namespace.
I've tested this, and it works for me.
Release note:
NONE

Hmm, ok found one issue with being namespace default, after the mixer-rule-deny-serviceaccount.yaml  is deleted, I'm still not able to get to the details...

ok, working with @douglas-reid and discovered the details just came back after I deleted the rule about 20 mins ago.

@linsun: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-cluster_wide-auth.sh
9e291c3cbf94158ea9bcc961a9a028063d61d174
link
/test e2e-cluster_wide-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

istio-system is also noted in https://github.com/istio/istio/blob/master/samples/bookinfo/kube/mixer-rule-ratings-ratelimit.yaml#L5 and https://github.com/istio/istio/blob/master/samples/bookinfo/kube/mixer-rule-ratings-denial.yaml#L5-L5 . Should these be updated as well?

@jmuk PTAL

fwiw, writing rules in istio-system makes them (with the current configuration of mixer) universal. they will apply to all services regardless of namespacing. putting rules in a namespace limits their scope to that namespace. we should probably make that very explicit, so that the choice is understood.

good point, I think we should @douglas-reid!  I was very confused why our routing rule didn't specify namespace and suddenly when I move to mixer rules it is namespace in istio-system.

On 2nd thought, I think some of these policies doesn't make sense to be global, for example:  the ones that uses service account because service account is very specific to namespace:  mixer-rule-deny-serviceaccount.yaml

/lgtm
Agreed. I think some of the config node can be in istio-system -- like the global handler config can be bound by rules in individual namespaces. Having said that, I think this structure makes sense as our example.


Add support for placeholders to Feign spring-mvc RequestMapping annot…

Improvement to address: https://github.com/spring-cloud/spring-cloud-netflix/issues/894

Closed via 2b40952


Add Jenkins Getting Started Script for Java

What does the program do ?

Simple Jenkins pipeline in Java
In what programming language it is written?
Groovy

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


Replace fandom with minecraft.wiki

Replace fandom's minecraft wiki with the new wiki
I also removed "official" - The wiki, neither minecraft.wiki, nor the fandom one is owned by Microsoft/Mojang; it's community maintained, so it's not considered "official"

Thought I caught all the fandom references :sweat_smile:. Thanks.


Android project missing gradlew scripts

Project is missing the gradle wrapper scripts (the entrypoint to gradle usage).

@AnmAtAnm Thank you for opening this issue. 🙏
Please check out these other resources that might be applicable:

Support Console - If you have a support contract.
Discord - chat with other developers
StackOverflow - use the google-maps tag
Google Maps Platform issue trackers

This is an automated message, feel free to ignore.


[BUG] hash_aggregate_test.py::test_exact_percentile_groupby_partial_fallback_to_cpu failed mismatched cpu and gpu output with DATAGEN_SEED=1723492454

Describe the bug
rapids_integration-scala213-dev-github, run: 223
failed in spark 334 integrations tests,
AssertionError: GPU and CPU float values are different [0, 'percentile(val, 0.1)']

cpu = -2.6611656653555613e+151, gpu = -2.2241524877840376e+151
float_check = <function get_float_check.<locals>.<lambda> at 0x7fd4e5238c10>
path = [0, 'percentile(val, 0.1)']

[2024-08-12T22:06:45.648Z] FAILED ../../src/main/python/hash_aggregate_test.py::test_exact_percentile_groupby[[('key', RepeatSeq(Integer)), ('val', Double), ('freq', Long(not_null))]0][DATAGEN_SEED=1723492454, TZ=UTC, IGNORE_ORDER] - AssertionError: GPU and CPU float values are different [0, 'percentile(val, 0.1)']
[2024-08-12T22:06:45.648Z] FAILED ../../src/main/python/hash_aggregate_test.py::test_exact_percentile_groupby_partial_fallback_to_cpu[false-partial-[('key', RepeatSeq(Integer)), ('val', Double), ('freq', Long(not_null))]][DATAGEN_SEED=1723492454, TZ=UTC, IGNORE_ORDER, ALLOW_NON_GPU(ObjectHashAggregateExec,SortAggregateExec,ShuffleExchangeExec,HashPartitioning,AggregateExpression,Alias,Cast,Literal,ProjectExec,Percentile)] - AssertionError: GPU and CPU float values are different [0, 'percentile(val, 0.1)']
[2024-08-12T22:06:45.648Z] FAILED ../../src/main/python/hash_aggregate_test.py::test_exact_percentile_groupby_partial_fallback_to_cpu[false-final|complete-[('key', RepeatSeq(Integer)), ('val', Double), ('freq', Long(not_null))]][DATAGEN_SEED=1723492454, TZ=UTC, IGNORE_ORDER, ALLOW_NON_GPU(ObjectHashAggregateExec,SortAggregateExec,ShuffleExchangeExec,HashPartitioning,AggregateExpression,Alias,Cast,Literal,ProjectExec,Percentile)] - AssertionError: GPU and CPU float values are different [0, 'percentile(val, 0.1)']
[2024-08-12T22:06:45.648Z] FAILED ../../src/main/python/hash_aggregate_test.py::test_exact_percentile_groupby_partial_fallback_to_cpu[true-partial-[('key', RepeatSeq(Integer)), ('val', Double), ('freq', Long(not_null))]][DATAGEN_SEED=1723492454, TZ=UTC, IGNORE_ORDER, ALLOW_NON_GPU(ObjectHashAggregateExec,SortAggregateExec,ShuffleExchangeExec,HashPartitioning,AggregateExpression,Alias,Cast,Literal,ProjectExec,Percentile)] - AssertionError: GPU and CPU float values are different [0, 'percentile(val, 0.1)']
[2024-08-12T22:06:45.648Z] FAILED ../../src/main/python/hash_aggregate_test.py::test_exact_percentile_groupby_partial_fallback_to_cpu[true-final|complete-[('key', RepeatSeq(Integer)), ('val', Double), ('freq', Long(not_null))]][DATAGEN_SEED=1723492454, TZ=UTC, INJECT_OOM, IGNORE_ORDER, ALLOW_NON_GPU(ObjectHashAggregateExec,SortAggregateExec,ShuffleExchangeExec,HashPartitioning,AggregateExpression,Alias,Cast,Literal,ProjectExec,Percentile)] - AssertionError: GPU and CPU float values are different [0, 'percentile(val, 0.1)']

Steps/Code to reproduce bug
Please provide a list of steps or a code sample to reproduce the issue.
Avoid posting private or sensitive data.
Expected behavior
A clear and concise description of what you expected to happen.
Environment details (please complete the following information)

Environment location: Standalone
Spark configuration settings related to the issue

Additional context
Add any other context about the problem here.

This is caused by https://issues.apache.org/jira/browse/SPARK-45599 it was fixed in Spark 4.0.0 and Spark 3.5.2. I looked closer at the test results and I saw that there was a -0.0 and a regular 0.0 as one of the percentiles produced.
It is also a dupe of #10233 (I wish the github issue search was better)
I think we probably want to have the tests avoid outputting both -0.0 and 0.0 for versions that do not have the fix in it.

Dup of https://github.com/NVIDIA/spark-rapids/issues/10233


Mutliple-line support with ""

Add support for multiple-line commands using the "" characters.
Adding "" to the end of the line means that the next line should be processed as part of it.
E.g.
/execute @e[name=CityRunner,score_power_up_option=1,score_power_up_option_min=1] ~ ~ ~ \
	execute @e[name=cr_falling_powerup,score_power_ups=0] ~ ~0.6 ~ \
		setblock ~ ~ ~ minecraft:chest 2 replace {CustomName:- Power Up -,Items:[{Slot:13,id:ender_pearl,Count:3}]}

This would be processed as one command block line
!docommand ArgumentOne \
	ArgumentTwo \
	ArgumentThree

This would be processed as one bang command line.

#18 closed this.


Incompatibility of SMCABC log_prob with PyTorch 1.8

Hello!
I was toying around with SMABC via sbibm and came across an exception while trying to run:
import sbibm
from sbibm.algorithms import smc_abc
task = sbibm.get_task("two_moons")
posterior_samples, _, _ = smc_abc(
    task=task, num_samples=1_000, num_observation=1, num_simulations=10_000
)

which spits out the following (truncated to relevant bits):
~/.pyenv/versions/3.7.4/lib/python3.7/site-packages/sbi/inference/abc/smcabc.py in _sample_and_perturb
(self, particles, weights, num_samples)
    497             parms_perturbed = self.get_new_kernel(parms).sample()
    498
--> 499             is_within_prior = torch.isfinite(self.prior.log_prob(parms_perturbed))
    500             num_accepted += is_within_prior.sum().item()
    501

~/.pyenv/versions/3.7.4/lib/python3.7/site-packages/torch/distributions/independent.py in log_prob(sel
f, value)
     89
     90     def log_prob(self, value):
---> 91         log_prob = self.base_dist.log_prob(value)
     92         return _sum_rightmost(log_prob, self.reinterpreted_batch_ndims)
     93

~/.pyenv/versions/3.7.4/lib/python3.7/site-packages/torch/distributions/uniform.py in log_prob(self, v
alue)
     71     def log_prob(self, value):
     72         if self._validate_args:
---> 73             self._validate_sample(value)
     74         lb = self.low.le(value).type_as(self.low)
     75         ub = self.high.gt(value).type_as(self.low)

~/.pyenv/versions/3.7.4/lib/python3.7/site-packages/torch/distributions/distribution.py in _validate_s
ample(self, value)
    275         assert support is not None
    276         if not support.check(value).all():
--> 277             raise ValueError('The value argument must be within the support')
    278
    279     def _get_checked_instance(self, cls, _instance=None):

ValueError: The value argument must be within the support

I believe this comes down to a line in the SMCABC checking whether perturbed parameters are within the prior:
https://github.com/mackelab/sbi/blob/340424ecaacc5c375a4818927f8a3e2742ceb979/sbi/inference/abc/smcabc.py#L499
The problem is that PyTorch 1.8 validates against the support of the distribution before taking a log_prob.
This might be addressed by changing the above line to
is_within_prior = self.prior.support.check(parms_perturbed)

However, this presupposes that the support.check() method exists, which might not be the case for user-defined priors. So a more conservative change might be:

try:
    is_within_prior = self.prior.support.check(parms_perturbed)
except AttributeError:
    is_within_prior = torch.isfinite(self.prior.log_prob(parms_perturbed))

I'll go ahead and raise the last change in a PR for the sake of taking a next step, but obviously I'm happy to defer to what the maintainers think is best!

Hi there,
thanks for creating this issue! What is your version of sbi? If it is not the newest version, please upgrade both sbi and sbibm and see if the error persists.
Best
Michael

Thanks for the quick response!
Just upgraded to ensure that I'm on 0.16.0 for sbi and 1.0.6 for sbibm, which I believe are the latest versions, but the error still persists.

Hey! I think this is indeed a bug. The perturbation can move particles outside of the prior support, which cause the new PyTorch to raise a ValueError.
But I think the fix suggested in #505 will not work because of the same problem. I think we need to use within_support and I actually have the fix on a local branch - just forgot to push it.

Ah cool! Thanks for the quick fix. I'll close #505 then :)

Can be closed with release 0.16.1.

Seems to work now :) Thank you!


[CT-3330] [Bug] get_create_materialized_view_as_sql is missing from Postgres 1.7 runtime in Cloud

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
1.6 added Postgres support for materialized views. While 1.7 saw some ergonomic upgrades across the board, the previously working materialized views flow now can struggle to locate a default macro needed for this materalization.
The kicker is that this is a Cloud-only bug we're detecting. This bug is found only in Cloud, neither in CI/CD nor local tests in core.
Is this a caching problem? A macro space problem? Who's to say?
Expected Behavior
Materialized views build successfully (just as they do outside of core).
Steps To Reproduce

Set the dbt env to 1.7.latest
Open the IDE to a simple project in Cloud (e.g. one obtained from a dbt init)
In the my_second_dbt_model.sql, simple convert the materialization from table to materialized_view.
dbt run -s +my_second_dbt_model

Relevant log output
Compilation Error in model my_second_dbt_model (models/example/my_second_dbt_model.sql) `get_create_materialized_view_as_sql` has not been implemented for this adapter.
> in macro default__get_create_materialized_view_as_sql (macros/relations/materialized_view/create.sql)
> called by macro get_create_materialized_view_as_sql (macros/relations/materialized_view/create.sql)
> called by macro materialized_view_get_build_sql (macros/materializations/models/materialized_view.sql)
> called by macro materialization_materialized_view_default (macros/materializations/models/materialized_view.sql)
> called by model my_second_dbt_model (models/example/my_second_dbt_model.sql)

Environment
Cloud with dbt-core 1.7. Postgres Managed with SSH.

Which database adapter are you using with dbt?
postgres
Additional Context
I verified by hand materialized views are building just fine for other adapters, so this is a postgres-specific problem.
We also note that this works with postgres + 1.6 in Cloud.
One other piece of info is that the macro in question was moved (not altered, just moved). Whether this impacts the runtime or not is yet to be seen.

Update from @mikealfare

The issue is here: https://github.com/dbt-labs/dbt-core/blob/main/plugins/postgres/setup.py#L63-L70 (plus no MANIFEST.in file). We don't actually package up the macros recursively and I moved them one level deeper in 1.7. We don't catch it in CI because we pull the entire repo and so the macros come along with it. However, when we build we drop these files. dbt-postgres 1.7 is likely broken on PyPI, which then gets installed in the bundle.


add new abstraction for simple Lambda that does not need explicit initialization

motivation: make simple things simple
changes:

add new abstraction names SimpleLambdaHandler that has a default initializer
add test

we could / should consider doing this on LambdaHander instead of the new abstraction, also not in love with the "Simple" prefix.

We can drop context: from LambdaHandler’s initializer, then the SimpleLambdaHandler model will just fit (we can keep async and throws so users can still initialize some resources if they want).

@stevapple context is needed when users need to initialize resources, it provides thinks like the NIO EventLoop and Terminator, so we cannot drop it.

Is there any reason they cannot use async/await for asynchronous startup, and use throw in place of manual termination? I think that's the "simple" way and should work for most people.

termination is for resource cleanup when shutting down, there needs to be an entry point to that. also all NIO based clients (eg db client based on NIO) need access the the EventLoop for initialization to avoid thread hops

superseded by #273


OSError: [Errno 98] Address already in use

While I run this cmd: python3 aem_hacker.py -u https://site.com --host <IP_ADDRESS>
The error comes.
Traceback (most recent call last):
  File "aem_hacker.py", line 1676, in <module>
    main()
  File "aem_hacker.py", line 1648, in main
    httpd = run_detector(args.port)
  File "aem_hacker.py", line 1605, in run_detector
    httpd = HTTPServer(('', port), handler)
  File "/usr/lib/python3.8/socketserver.py", line 452, in __init__
    self.server_bind()
  File "/usr/lib/python3.8/http/server.py", line 138, in server_bind
    socketserver.TCPServer.server_bind(self)
  File "/usr/lib/python3.8/socketserver.py", line 466, in server_bind
    self.socket.bind(self.server_address)
OSError: [Errno 98] Address already in use

Solutions?
Thank you

I kill every service on Python, but still, an error comes.


Updated orbit download for faster performance

~5x faster performance. Repeated dates using same orbit where slow to verify. This skips verification and applies downloaded orbit to all products of the same date (different subswaths or frames).

It does not work as expected. As I remember, we cannot anticipate that only one orbit file is required for a date. This commit enhances downloading scanning orbits for just one subswath: 30213d9f8484a4f514930d993c98919c4d8622db


Attempting Deploy First Application returns mostly No help topic for [cmd]

Describe the bug
I'm trying to follow your tutorial and that seems not really fluent:
brew install kubevela   # <--- all good
[...]

❯ vela install --help
No help topic for 'install'

❯ vela install
No help topic for 'install'
vela install --api.addr=https://localhost:6443
No help topic for 'install'

# ... I finally chose the helm approach instead which worked without issue ...
$ vela addon enable velaux
No help topic for 'addon'

Expected behavior
I would at least expect a message more clear than "no help"
KubeVela Version
❯ vela --version
vela version v0.19.2

Cluster information
I'm using a local docker desktop k8s. My default kubeconfig is pointing to it.
Additional context
I will probably sort that by going further in your documentation but you may recognise it's not a great starting point with the KubeVela :-)
Thank you by advance.

This is 100% my side issue. Another tool named vela was present on my machine. Removing it and using the appropriate kubevela resulted in the expected behaviour.


feat(Keys_Viewing): Make AES available in noir

For the note encryption we need to have some encryption decryption available. As it looks atm, we will be using AES, so we need to have some AES implementation available.
BB already have an implementation so ideally we can simply expose that as a blackbox function, otherwise we need an implementation in pure noir.
We would very much want not do have the pure noir as it would be a pain to broadcast vs few calls to blackbox functions.

FWIW there was a community implementation in pure Noir: https://github.com/TaceoLabs/noir-aes
But I believe Mike mentioned it not being (sufficiently) performant.
If we already have a good implementation in barretenberg we certainly should blackbox it 👍


Hinted handoff and GET

Handoffs in Riak occur a result of partition_repair, ownership_transfer or hinted_handoff.
In the first two cases, the data being handed off is generally not present in the vnode receiving the handoff.
In the latter case, hinted handoff, this is not true.  As whilst the vnode was down, fallback vnodes are collecting GETs as well as PUTs.  As read_repair will by default operate on both primary and fallback, whilst a fallback is deputising for a primary it will receive external PUTs (i.e. updates and fresh PUTs via the API relevant to that partition), but also PUTs generated for GETs that occur during the failure (as read repair will detect that the object is not present in the fallback).
When the primary recovers, a hinted handoff is prompted.  This will include PUTs where no object is present (inserts which occurred during the outage), PUTs where an old object is present (updates which occurred during the outage) and PUTs where the current object is present (due to read repair of GETs which occurred during the outage).
When handling a handoff_data item the function riak_kv_vnode:do_diffobj_put/3 is called.  Note that this is a different path to the normal PUT of an object, and it always starts with riak_kv_vnode:do_get_object/4.
In the standard path of PUT there is an optimisation, so that normally only a HEAD request is required before a PUT.  However, that optimisation is not in the handoff_data path - do_get_object will always get the full object including body, not just the metadata.
If the handoff is an ownership transfer or a partition repair, all the objects are generally new (as the vnode starts empty), and so the riak_kv_vnode:do_get_object/4 returns {error, not_found} at very low cost.  However, for hinted handoff, this is not the case - and the riak_kv_vnode:do_get_object/4 requires a fetch of the whole object, which is commonly a much higher cost.
This means that hinted handoff is more expensive than a normal PUT (with the leveled backend), and much more expensive than handoffs for other reasons.  So if the transfer-limit and handoff_timeout is tuned for ownership transfers, hinted handoffs may unexpectedly fail due to timeouts.
This is especially exacerbated when running relatively slow disks and relying on page caches - as while metadata (required for HEAD responses) can generally be expected to be found in the page_cache, the object body may not.  This makes the read before the write potentially very expensive.

This issue can be partially mitigated by https://github.com/basho/riak_kv/pull/1844.  However, if the majority of PUT load while the node has been down are UPDATEs and not INSERTs, even with read repair to fallbacks disabled there could be an issue.

There are two potential optimisations here in addition to https://github.com/basho/riak_kv/pull/1844:

Change riak_kv_vnode:do_diffobj_put/3 so that it can use a HEAD request before a PUT rather than a GET request, as with the standard PUT path.
Force handoffs to backoff.  Currently the sync before then next batch is an implicit backoff.  Perhaps the backoff should be more sever and explicit if the sync time goes beyond a certain threshold.

Changing the riak_kv_vnode code to use HEAD optimisation for handoffs as well as PUTs, leads to significant improvements in throughput - and with no handoff errors.
Pre-change:

Post-change:

As a consequence, extremes of vnode_put times (which lead to issues with vnode_timeout causing handoff exits):

Test
median(vnode_put_fsm_time_100)
mean(vnode_put_fsm_time_100)
p99(vnode_put_fsm_time_100)

Pre-change
5.8 s
11.2 s
101.1 s

Post-change
0.001 s
0.004 s
0.02 s

Looking at stats per vnode of "fetches" for object bodies.
Pre-change:

Post-change:

Note that the count of fetches is non-zero post change.  This is probably because of "equal" vector clocks.  When a "repair" GET is handed off, the local vector clock will equal the handed off vector clock.  This currently prompts an unnecessary GET.  It is only when the inbound object dominates the local vector clock that the GET is avoided.

With regards to equal objects being handed off.
Unless the inbound object strictly dominates the locally stored object - https://github.com/basho/riak_kv/blob/riak_kv-3.0.12/src/riak_kv_vnode.erl#L2950-L2964 - a GET is required.
There is caution expressed in the dominates function itself:
https://github.com/basho/riak_core/blob/riak_kv-3.0.12/src/vclock.erl#L110-L128
If the two vector clocks are strictly equal, then there would be no need (probably?) to GET.  That is to say if A does not dominate B, that is not enough to say that A is not of interest in the merge.
There are challenges to changing this to consider optimising for equality of vector clock in handoff.  There would be risks of potential false reasoning that could have data loss repercussions.   This lack of optimisation can be addressed through not allowing read repair to fallbacks.
So, for now, leave as-is, and except the additional GET in this case.

Running the test with read_repair_primaryonly, the hinted handoffs now run at nearly twice the rate, and complete in nearyl half the time:


Fixes #451 inlay hint api change

Change the calls to inlay_hint.enable to arrange the parameters in the expected way.
Fixes #451
this is the error this PR addresses:
vim.lsp.inlay_hint.enable(bufnr:number, enable:boolean) is deprecated, use vim.lsp.inlay_hint.enable(enable:boolean, filter:table) instead. :help
 deprecated
Feature was removed in Nvim 0.10-dev

There is a failing unit test. It doesn't fail for me when I run the tests locally, and it doesn't appear to have anything to do with the code changes I made.


Pushing fix for #10 parameterise feed URLs

I have run the script, but I'm not sure if the format of the feed URLs has changed and broken things as it can't extract a cty.dat properly.

Hello ivernus,
Thank you for your suggestions!
The code in this repository is in the middle of a rewrite, and you've made some changes to the old code. You can preview the new code (in progress) in the branch 5c-excepts.
The old code is not very tolerant to modifications, and loading a custom CTY.DAT file only works in the new version. In the new version, the feed is customizable, but the download link is not (yet).

The new code is not yet documented enough, and currently lacks a command-line interface (also in the works).
I should be fairly trivial to use from within a python script, or the Python REPL.
Just instantiate the class BigCty from the package, and .load() the cty.dat file, and .dump()  to a json file.
You probably do not want to run setup.py though, as the new code is currently going through more changes.


Add a better demo and publish to GH pages

On second thought, I think I'll put the demo in a separate repository


[webserver] onCreate not called correctly

As reported by @thijsvdanker; it seems the onCreate is called without hostnames and therefor returns void. Once a hostname is added the website is touched and so onCreate should again be called from within onUpdate, but this is not (always) the case.
In order to solve this at least:

create a unit test that proves files are generated for nginx, apache etc (if enabled)
see what the process is during create, update
ensure files are generated

I experienced the same issue recently. This happens because the observer is checking the relation object, sometimes this relation has not been instantiated and thus will return null.. We can load the relation beforehand and do the check or use the website_id on domain to check and then load.

The problem seemed to be related to the observer events being called before the transaction was completed. This should now be fixed.