[BUG] Ob-async does not work.

the bug output
error in process sentinel: Cannot open load file: No such file or directory, org-version.el
see issues
if you clean uprm -rf  ~/.emacs.d/.local/straight/build/org-plus-contrib/*.elc.  it's working.
But, we got new problem, the emacs can not find org version.  similar like this  issues.

We have this hack in place to prevent this issue. I cannot reproduce it. Please include your M-x doom/info and steps to reproduce it.

Also, ob-async is already installed by Doom. You do not need to install or configure it yourself.

Also, ob-async is already installed by Doom. You do not need to install or configure it yourself.

We have this hack in place to prevent this issue. I cannot reproduce it. Please include your M-x doom/info and steps to reproduce it.

emacs   version    26.3
        features   NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS
        build      Sep 02, 2019
        buildopts  (--with-ns '--enable-locallisppath=/Library/Application Support/Emacs/${version}/site-lisp:/Library/Application Support/Emacs/site-lisp' --with-modules)
        windowsys  ns
        daemonp    server-running
doom    version    2.0.9
        build      HEAD -> develop, origin/develop, origin/HEAD 04a2cb94c 2019-11-02 23:34:34 -0800
system  type       darwin
        config     x86_64-apple-darwin18.2.0
        shell      /bin/zsh
        uname      Darwin 19.0.0 Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 x86_64
        path       (~/.poetry/bin/ /usr/local/opt/texinfo/bin/ /usr/local/opt/nss/bin/ ~/anaconda3/bin/ /usr/local/opt/imagemagick@6/bin/ ~/.cargo/bin/ /usr/local/bin/ /usr/local/opt/texinfo/bin/ /usr/bin/ /bin/ /usr/sbin/ /sbin/ /Applications/VMware Fusion.app/Contents/Public/ /Library/TeX/texbin/ /usr/local/MacGPG2/bin/ /opt/X11/bin/ /Applications/Wireshark.app/Contents/MacOS/ /usr/local/opt/ ~/go/bin/ /Applications/Emacs.app/Contents/MacOS/libexec/)
config  envfile    envvar-file
        elc-files  0
        modules    (:input chinese :completion company helm ivy :ui doom doom-dashboard doom-quit hl-todo modeline nav-flash ophints (popup +all +defaults) treemacs vc-gutter vi-tilde-fringe window-select workspaces :editor file-templates fold rotate-text snippets :emacs dired electric ibuffer vc :tools (eval +overlay) flycheck (lookup +docsets) lsp magit :lang cc common-lisp data emacs-lisp ess go (haskell +intero) julia latex markdown nix (org +dragndrop +hugo +ipython +pandoc +present) python sh :app (rss +org) :config (default +smartparens) :private spacemacs-default)
        packages   (n/a)
        elpa       (n/a)

that will help you easy test : Org-src:
#+BEGIN_SRC sh :async
sleep 4s && echo 'done'
#+END_SRC
#+RESULTS:
: done
if you get issue that not find org-version.el
try run this:
#+BEGIN_SRC sh
rm -rf  ~/.emacs.d/.local/straight/build/org-plus-contrib/*.elc
#+END_SRC

Ah, I can reproduce it. Try this and see if it resolves the issue:
(add-hook! 'ob-async-pre-execute-src-block-hook
           (load (expand-file-name "init.el" user-emacs-directory)))

thanks, it's solved the issue. but if the user place initialization logic in ob-async-pre-execute-src-block-hook, which runs before execution of every src block. such as Julia:
(add-hook 'ob-async-pre-execute-src-block-hook             '(lambda ()                (setq inferior-julia-program-name "/nix/store/qzpr1kwkhnz55mdlq8skc5sqrc6l2j2b-system-path/bin/julia")                ))
added your config
`ob-async.el.
Value ((lambda nil   (setq inferior-julia-program-name "/nix/store/qzpr1kwkhnz55mdlq8skc5sqrc6l2j2b-system-path/bin/julia"))  (lambda   (&rest _)   (load    (expand-file-name "init.el" user-emacs-directory))))
new issue.
error in process sentinel: async-handle-result: Cannot open load file: No such file or directory, ob-julia error in process sentinel: Cannot open load file: No such file or directory, ob-julia
So, how to write a config which can be load of both no error.

How about:
(defadvice! +org-init-doom-during-async-executation-a (orig-fn &rest args)
    :around #'ob-async-org-babel-execute-src-block
    (let ((ob-async-pre-execute-src-block-hook
           (cons (lambda () (load (expand-file-name "init.el" user-emacs-directory)))
                 ob-async-pre-execute-src-block-hook)))
      (apply orig-fn args)))

This should ensure that our hook is always first.

(defadvice! +org-init-doom-during-async-executation-a (orig-fn &rest args)
    :around #'ob-async-org-babel-execute-src-block
    (let ((ob-async-pre-execute-src-block-hook
           (cons (lambda () (load (expand-file-name "init.el" user-emacs-directory)))
                 ob-async-pre-execute-src-block-hook)))
      (apply orig-fn args)))

error in process sentinel: async-handle-result: Cannot open load file: No such file or directory, org error in process sentinel: Cannot open load file: No such file or directory, org
debug info :

Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" "org")
  signal(file-missing ("Cannot open load file" "No such file or directory" "org"))
  async-handle-result((lambda (result) (with-current-buffer # (let ((default-directory "/home/gtrun/project/my-code/my-julia/")) (save-excursion (cond ((member "none" ...) (message "result silenced")) ((member "silent" ...) (message ...)) (t (goto-char #) (let ... ... ... ...))) (run-hooks (quote org-babel-after-execute-hook)))))) (async-signal (file-missing "Cannot open load file" "No such file or directory" "org")) #)
  async-when-done(# "finished\n")

Those errors don't seem related, but try this:
(defadvice! +org-init-doom-during-async-executation-a (orig-fn &rest args)
    :around #'ob-async-org-babel-execute-src-block
    (let ((ob-async-pre-execute-src-block-hook
           ;; Ensure our hook is always first
           (cons `(lambda ()
                    (load ,doom-autoload-file)
                    (load ,doom-package-autoload-file))
                 ob-async-pre-execute-src-block-hook)))
      (apply orig-fn args)))

Those errors don't seem related, but try this:
(defadvice! +org-init-doom-during-async-executation-a (orig-fn &rest args)
    :around #'ob-async-org-babel-execute-src-block
    (let ((ob-async-pre-execute-src-block-hook
           ;; Ensure our hook is always first
           (cons `(lambda ()
                    (load ,doom-autoload-file)
                    (load ,doom-package-autoload-file))
                 ob-async-pre-execute-src-block-hook)))
      (apply orig-fn args)))

error in process sentinel: async-handle-result: Symbol’s function definition is void: after! error in process sentinel: Symbol’s function definition is void: after!

I cannot reproduce these new errors, but try this:
(defadvice! +org-init-doom-during-async-executation-a (orig-fn &rest args)
    :around #'ob-async-org-babel-execute-src-block
    (let ((ob-async-pre-execute-src-block-hook
           ;; Ensure our hook is always first
           (cons `(lambda ()
                    (load ,(expand-file-name "init.el" doom-emacs-dir)))
                 ob-async-pre-execute-src-block-hook)))
      (apply orig-fn args)))

If possible, can you hop on our discord? I don't want to spam here.

Is this issue solved? I have the latest version of doom as 11/19/2019 20:30 PDT. But I still have missing org-version.el file.

Is this issue solved? I have the latest version of doom as 11/19/2019 20:30 PDT. But I still have missing org-version.el file.

Sure, No any issue appears in my config with lastest doom-version.  You only need one config to your doom. for async
'(use-package! ob-async)'
tested on drawin and nixos

emacs   version    26.3
        features   NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS
        build      Sep 02, 2019
        buildopts  (--with-ns '--enable-locallisppath=/Library/Application Support/Emacs/${version}/site-lisp:/Library/Application Support/Emacs/site-lisp' --with-modules)
        windowsys  ns
        daemonp    server-running
doom    version    2.0.9
        build      HEAD -> develop, origin/develop, origin/HEAD ff179b080 2019-11-18 18:13:59 -0800
system  type       darwin
        config     x86_64-apple-darwin18.2.0
        shell      /bin/zsh
        uname      Darwin 19.0.0 Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 x86_64
        path       (~/.poetry/bin/ ~/.cargo/bin/ /usr/local/bin/ /usr/bin/ /bin/ /usr/sbin/ /sbin/ /Applications/VMware Fusion.app/Contents/Public/ /Library/TeX/texbin/ /usr/local/MacGPG2/bin/ /usr/local/share/dotnet/ /opt/X11/bin/ ~/.dotnet/tools/ /Applications/Wireshark.app/Contents/MacOS/ ~/.poetry/bin/ /usr/local/opt/texinfo/bin/ /usr/local/opt/nss/bin/ ~/anaconda3/bin/ /usr/local/opt/imagemagick@6/bin/ ~/.cargo/bin/ /usr/local/opt/ ~/go/bin/ /Applications/Emacs.app/Contents/MacOS/bin-x86_64-10_14/ /Applications/Emacs.app/Contents/MacOS/libexec-x86_64-10_14/ /Applications/Emacs.app/Contents/MacOS/libexec/)
config  envfile    envvar-file
        elc-files  0
        modules    (:input chinese :completion company helm ivy :ui doom doom-dashboard doom-quit hl-todo indent-guides modeline nav-flash ophints (popup +all +defaults) treemacs vc-gutter vi-tilde-fringe window-select workspaces :editor file-templates fold rotate-text snippets :emacs dired electric ibuffer vc :term eshell :tools (eval +overlay) flycheck (lookup +docsets) lsp magit pass upload :lang cc common-lisp data emacs-lisp ess go (haskell +intero) julia latex markdown nix (org +dragndrop +hugo +ipython +pandoc +present) python scheme sh :app (rss +org) :config (default +smartparens) :private spacemacs-default my-org my-code)
        packages   (n/a)
        elpa       (n/a)

I can no longer reproduce the issue. @ztlevi Try doom build.

(use-package! 'ob-async)

Don't do this. It is unnecessary and loads all of org.

I still get the error.
error in process sentinel: async-handle-result: Cannot open load file: No such file or directory, org-version.el
error in process sentinel: Cannot open load file: No such file or directory, org-version.el

I am using org-wild-notifier. Can you please try this package and enable it M-x org-wild-notifier-mode
(package! org-wild-notifier)
(use-package! org-wild-notifier
  :defer t
  :init
  (add-hook 'doom-post-init-hook #'org-wild-notifier-mode t)
  :config
  (setq org-wild-notifier-alert-time 15
        alert-default-style (if IS-MAC 'osx-notifier 'libnotify)))

@ztlevi

Added (package! org-wild-notifier) to ~/.doom.d/packages.el

Added your use-package! block to ~/.doom.d/config.el

doom refresh

Restart Emacs

Opened an org file and executed
#+BEGIN_SRC sh :async t
sleep 2
echo 25
#+END_SRC

Ran without issue. Ran it multiple times, even.
Currently on 24efd5b90 with Emacs 26.3.

Side-note: doom-post-init-hook doesn't exist anymore. It was replaced with doom-after-init-modules-hook some time ago, so org-wild-notifier isn't even loading.

What about you trigger it manually? Did you get the error?

Side-note: doom-post-init-hook doesn't exist anymore. It was replaced with doom-after-init-modules-hook some time ago, so org-wild-notifier isn't even loading.

this issue not about org-babel-async. I tried to download the org-wild-notifier. also got the same error report.

Agh. I see it. It's the way org-wild-notifier scrapes your org agenda files. It uses async much like ob-async does, except unlike ob-async, it doesn't provide us a way to inject Doom's state before it runs.
This is non-trivial to fix from Doom's side. I suggest using org-alert instead.

Emm, org-alert doesn't really work. While org-notify does pop notification but it repeats the notification every two minutes which is very annoying.
Is this possible to fix it from org-wild-notifier-mode? If so, I would like to open a issue

As of 30f72da I've employed a new solution to this and the ob-async problem, which should resolve your issue. Let me know if that isn't the case.

Nice! It works! 💯


6.0 Feedback:  App goes blank while choosing a different tip rack option during tip length calibration

Overview
https://user-images.githubusercontent.com/39049853/170590280-47b7a93d-9c8a-4238-aeda-b93da5cf05b9.mov
Current Behavior

There are no network errors
Expected Behavior
app should not white screen
Steps To Reproduce

Goto devices page
click on the robot
Goto robot settings
Goto Tip length calibrations -> click on the overflow menu
click on Recalibrate Tip length and Pipette Offset option
Click on "Use a different Tip Rack"

Operating system
No response
Robot setup or anything else?
No response

@reachojhaneha
Could you try this branch app_fix-different-tiprack-white-screen for #10490?

Verified fix


Updated store providers

Updates here are part of a larger PR and contains only functionality. The UI is on another PR. There is a demo page in #test route to test the new store.
the Demo page will be removed before merging this PR.

Page doesn't load at all if you have no wallet installed:

Uncaught Error: Wallet not installed or incompatible.

There is a missing condition in checking account state listener which should be fixed in https://github.com/DarkFlorist/lunaria/pull/95/commits/5e15f46f74d76b384fb89d52e9f38613e02a31ff


Question: Github release and tags

First I apologize if this is the wrong place to ask but I'm experiencing issue with the github release and tag for cakephp/cakephp. As you can see on github and on packagist, the project is now in 3.0.0-RC1 but the badge still show 3.0.0-dev3 from almost 6 month ago.
I'm using either https://img.shields.io/github/tag/cakephp/cakephp.svg or https://img.shields.io/github/release/cakephp/cakephp.svg but still get the same result.
It might not be an issue with your badge but I though you might have an idea of what might be the reason.
Thank's by advance

Hi!
This is absolutely the right place to ask.
It is a bit of a tricky situation. We rely on npm's semver library (the one actually used in npm) to guess the latest version. It doesn't try to guess the meaning of prerelease labels. It yields the following:
semver.maxSatisfying(['v3.0.0-dev3', 'v3.0.0-RC1'], '')
'v3.0.0-dev3'

I assume the reason for this is that:
'v3.0.0-dev3' > 'v3.0.0-RC1'
true

The data I receive from GitHub includes a published_at: '2015-01-02T19:09:28Z' field, but then v2.6.1 would be returned instead. There are even more critical cases in the wild, where old branches such as v1.0.0 which is superseded by v2.0.0, but a maintenance release v1.0.1 is published after v2.0.0. GitHub's release system is unfortunately fairly dumb, and since I don't rely on it much, I didn't anticipate the surprises it has brung.
What this needs is either a latest flag from GitHub, or a smarter algorithm, but I don't have it. In case you would like to try to find a solution, here's a snippet of the data we receive.
https://api.github.com/repos/cakephp/cakephp/releases
{ url: 'https://api.github.com/repos/cakephp/cakephp/releases/856971',
    assets_url: 'https://api.github.com/repos/cakephp/cakephp/releases/856971/assets',
    upload_url: 'https://uploads.github.com/repos/cakephp/cakephp/releases/856971/assets{?name}',
    html_url: 'https://github.com/cakephp/cakephp/releases/tag/2.6.1',
    id: 856971,
    tag_name: '2.6.1',
    target_commitish: 'master',
    name: 'CakePHP 2.6.1 Released',
    draft: false,
    author:
     { login: 'markstory',
       id: 24086,
       avatar_url: 'https://avatars.githubusercontent.com/u/24086?v=3',
       gravatar_id: '',
       url: 'https://api.github.com/users/markstory',
       html_url: 'https://github.com/markstory',
       followers_url: 'https://api.github.com/users/markstory/followers',
       following_url: 'https://api.github.com/users/markstory/following{/other_user}',
       gists_url: 'https://api.github.com/users/markstory/gists{/gist_id}',
       starred_url: 'https://api.github.com/users/markstory/starred{/owner}{/repo}',
       subscriptions_url: 'https://api.github.com/users/markstory/subscriptions',
       organizations_url: 'https://api.github.com/users/markstory/orgs',
       repos_url: 'https://api.github.com/users/markstory/repos',
       events_url: 'https://api.github.com/users/markstory/events{/privacy}',
       received_events_url: 'https://api.github.com/users/markstory/received_events',
       type: 'User',
       site_admin: false },
    prerelease: false,
    created_at: '2015-01-16T02:36:35Z',
    published_at: '2015-01-16T02:41:14Z',
    assets: [],
    tarball_url: 'https://api.github.com/repos/cakephp/cakephp/tarball/2.6.1',
    zipball_url: 'https://api.github.com/repos/cakephp/cakephp/zipball/2.6.1'
}

@espadrine OK I got it, thank's for the explanation, we might give it an other try when we hit stable but the maintenance release case you mentioned is quite likely to happen also...


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-source-version-target/pull/59 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-source-version-target.git

Docs Build status updates of commit 60ba6cd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

versioningArchiveSourceFolder/TOC.yml
:white_check_mark:Succeeded
View (sql-server-2014 || azuresqldb-current || azuresqldb-mi-current || azure-sqldw-latest || >= aps-pdw-2016 || >= sql-server-2016 || >= sql-server-linux-2017 || sql-server-previousversions || sqlallproducts-allversions)

versioningArchiveSourceFolder/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 60ba6cd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

versioningArchiveSourceFolder/TOC.yml
:white_check_mark:Succeeded
View (sql-server-2014 || azuresqldb-current || azuresqldb-mi-current || azure-sqldw-latest || >= aps-pdw-2016 || >= sql-server-2016 || >= sql-server-linux-2017 || sql-server-previousversions || sqlallproducts-allversions)

versioningArchiveSourceFolder/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Paperwork for RocksDB fix

Scope & Purpose
This just finishes some paperwork for a change which was already
done in another PR. Namely, CHANGELOG and a note in
3rdParty/README_maintainers.md
Original PR: https://github.com/arangodb/arangodb/pull/21273

[*] :hankey: Bugfix (paperwork)

Checklist

[*] :book: CHANGELOG entry made

This is comments only and does not touch any executable or compiled file. I am merging this without a CircleCi run.


Fix for editing Moves on Other-type actors - [merged]

In GitLab by @mclemente on Feb 22, 2024, 13:55
Merges beta -> master
Related to #107.

In GitLab by @Asacolips on Feb 22, 2024, 13:58
approved this merge request

In GitLab by @Asacolips on Feb 22, 2024, 13:59
mentioned in commit 81211b47d7533c299a62717d7b9d37ad482b868c


Spelling Correction from Dawson's Spelling Bee

Automated corrections from https://github.com/dawsonbotsford/spellingBee . If the correction is correct, star the repo, if it is wrong, report an issue!

Ignore. Testing in progress!


mismatch of coordinate systems and such.

code for PhysicsComponent.update
if not self.weightless:     self.kick(dv=Vector(0, -self.gravity), restrict_velocity=False)
in display systems the topleft corner is (0, 0)
to the right is +x
downward is +y
but the way i have it a downward accelleration is a decrease in dy/dt
so in this situation when altering your angle to point to the right
setting PhysicsComponent.dir = 0
and the graphics keyframe to 15
accellerating causes you to move left for some reason.
strange because the above issue with gravity would make you think that you would float upward and that that would be the issue.

fixed by offsets and stuff. related to #9

the above comment was supposed to also close this issue


Update CSS token per new design system theming capability

Alaska Airlines Pull Request
Fixes: #44
Summary:

Update the design tokens to reflect the new theming conventions regarding tokens from the AuroDesignTokens and JetstreamDesignTokens repo.

Type of change:
Please delete options that are not relevant.

[x] Revision of an existing capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Pico Display Issue, Backlight unable to set.

I am trying to use multiple addon board and when I call the RTC function from Waveshare(https://thepihut.com/products/precision-rtc-module-for-raspberry-pi-pico-ds3231), It makes the backlight 100%.
I'm trying to figure out if it's a pin conflict or something deeper.
Currently I'm using a Waveshare RTC + UPS.
They are stacked - Pico, UPS, RTC, Display.
I've set the backlight right at the beginning (like in the example code)
I've used the buttons example code as my base, The below code is called when I press my Y button.
 bus = I2C(0,scl=Pin(21),sda=Pin(20))
address = 0x68
start_reg = 0x00
w  = ["Sunday","Monday","Tuesday","Wednesday","Thursday","Friday","Saturday"]
t = bus.readfrom_mem(int(address),int(start_reg),7)
a = t[0]&0x7F  #second
b = t[1]&0x7F  #minute
c = t[2]&0x3F  #hour
d = t[3]&0x07  #week
e = t[4]&0x3F  #day
f = t[5]&0x1F  #month
display.text("%02x/%02x/20%x %02x:%02x:%02x %s" %(t[4],t[5],t[6],t[2],t[1],t[0],w[t[3]-1]),10,0,240,4)``

I think your pin definitions are the issue:
bus = I2C(0,scl=Pin(21),sda=Pin(20))
According to the schematics of the Waveshare RTC board, you should be using different pins (6 for SCA, and 7 for SCL). GP20 is pin26 of the Pico, which is used for the BL_EN signal on the Display Pack, so you're pumping your I2C data into the backlight control line!

I think your pin definitions are the issue:
bus = I2C(0,scl=Pin(21),sda=Pin(20))
According to the schematics of the Waveshare RTC board, you should be using different pins (6 for SCA, and 7 for SCL). GP20 is pin26 of the Pico, which is used for the BL_EN signal on the Display Pack, so you're pumping your I2C data into the backlight control line!

Those are for the old version of the board.

So it's a pin conflict as suspected, Shall buy a different screen, Cheers!


stop using deprecated part of the terraform sdk API

Blocked by #100 and #103. I'm not keen to merge this until we have basic acceptance tests in place to detect regressions.
While working on #106 I noticed that v2 of the terraform sdk has deprecated the Create/Read/Update/Delete properties of the schema.Resource struct in favour of new properties that support passing context.
I thought I'd bite the bullet and just make the change everywhere so all current resources are a good model for adding new resources in the future.
Note that we only updated to v2 of the sdk in #89 ~3 weeks ago, so this deprecation only appeared for us recently.
I haven't made an effort to use the new context instances to improve the way timeouts are handled when we query the graphql API. That could be worth exploring in the future.

Cool. I'll merge once #100 and #103 land :sparkles:

:eyes:

I've rebased onto main and force pushed


How to install an addin?

I'm trying to install the addin I'm writing and the command tools/install doesn't install the addin in monodevelop.
How am I supposed to do it?

Run xbuild yourproject.csproj /t:CreatePackage and the MSBuild targets will create an mpack file. You can install this using the "install from file" button in the Addin Manager.

Xamarin Studio (v5.9.8) doesn't seem to recognize .mpack files (doesn't even show up under all files from Install From File browser.
When trying to install by InstallAddIn target mdtool results in
FATAL ERROR [2015-11-01 21:32:32Z]: ICSharpCode.SharpZipLib.Zip.ZipException: Version required to extract this entry not supported (45)

Is there some other build format that Xamarin accepts or if there is temporary support missing?


Minor changes needed for OpenVMS

Define util sleep functions on VMS.
If PRIO_PROCESS is not defined then do not attempt to use it in the definition of SET_HIGH_PRIORITY.

All good !


A problem occured when github action was running

What happened?

Minimal Mistakes version: 4.24.0
Ruby gem or remote theme version: 3.3.7
Jekyll version: 4.3.1
Git repository URL: https://github.com/S-N-O-R-L-A-X/S-N-O-R-L-A-X.github.io
Hosted on GitHub Pages (if yes provide URL to site): https://s-n-o-r-l-a-x.github.io/
Operating system:

Expected behavior
The deployment job shoud run well. But now it ran well in local but raised an error when github action was running, which said "Warning:  github-pages can't satisfy your Gemfile's dependencies.
/usr/local/bundle/gems/jekyll-3.9.3/lib/jekyll/theme.rb:84:in `rescue in gemspec': The minimal-mistakes-jekyll theme could not be found. (Jekyll::Errors::MissingDependencyException)"
Steps to reproduce the behavior

Run jekyll new  to create a blog.
Use git remote to relate github and blog.
Install theme using Gem-based method.
Push the code to remote.

Other
No response

I found that adding the faraday-retry gem to the gemfile fixed this issue:
gem 'faraday-retry', '~> 2.2'

I've been able to fix the similar issue with this documentation https://github.com/mmistakes/minimal-mistakes#remote-theme-method 😉


Open Source Documentation for docs.github.com

Summary
The open-source community loves to innovate. Open-sourcing docs.github.com will welcome new ideas from a huge and diverse group of people.
This Autumn, we'll be moving to an open-source contribution model for GitHub Docs.
Intended Outcome
We build a community around docs.github.com of people who are passionate about developer documentation. This community will help us keep docs up to date, recommend & improve examples, and maybe even contribute complete articles, guides or tutorials.
How will it work?
At a high level, we'll accept internal and community contributions. Internal contributions are restricted to hubbers only, primarily on the Docs team. The reason for this is because we need docs access that is restricted from public consumption for confidential releases.
For community contributions, we envision three pathways:

Contributors making small bug fixes via PRs
Contributors working closely with GitHub, via issues and PRs, to make medium-sized contributions, like new articles or overhauls to existing articles
Contributors creating indexed content that utilizes platform content components

https://github.blog/changelog/2020-10-07-github-docs-are-now-open-source/


Lighthouse report is not displayed in the Netlify UI

Describe the bug
The same GitHub mono repo is linked to multiple Netlify sites, including staging, production, testing-env1, and testing-env2. The netlify.toml file is configured with the Netlify Lighthouse plugin. The goal is to generate a Lighthouse report only when changes occur in a specific app and only on the staging Netlify site. However, this feature is not available by default. To address this, a custom wrapper plugin was developed to check if the site is staging, verify if there are any changes in the specific app, and generate the Lighthouse report. The plugin runs successfully, and Lighthouse scores are visible, but the report cannot be viewed as shown in the screenshot.
Expected behavior
The report should show even when the plugin is called via the wrapper plugin
Screenshots
The screenshot provided appears when the @netlify/plugin-lighthouse is run via netlify.toml file. However, this same screenshot is not generated when the plugin is called via the wrapper plugin.

Additional context
Attaching the sample code
index.js
export const onPostBuild = async ({ constants, utils }) => {

  if (!isEnvironmentAllowedToRunPlugin()) {
    return;
  }

  if (hasChangesInApp1(utils)) {
    const inputs = {
      settings: {
        preset: 'desktop'
      },
      audits: [{
        path: 'app1',
        output_path: 'reports/app1.html',
        thresholds: {
          performance: 0.9,
          accessibility: 0.9,
          'best-practices': 0.9,
          seo: 0.9,
        }
      }],
    };

    await lighthouse.onPostBuild({constants, utils, inputs});
  }

manifest.yml
name: netlify-plugin-lighthouse

package.json
{
  "name": "netlify-plugin-lighthouse",
  "version": "1.0.0",
  "description": "netlify plugin that runs @netlify/plugin-lighthouse based on the condition",
  "main": "index.js",
  "type": "module",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
}

netlify.toml
[[plugins]]
  package = "/plugins/netlify-plugin-lighthouse"

The plugin runs successfully, and Lighthouse scores are visible, but the report cannot be viewed as shown in the screenshot.

Am I understanding correctly that you're seeing Lighthouse scores in the deploy logs, but not the UI above the log? Are you able to share any of the output? Do you see any errors or warnings?
I see a call to await lighthouse.onPostBuild({constants, utils, inputs}); in your wrapper - can I ask how are you importing lighthouse here?

The plugin runs successfully, and Lighthouse scores are visible, but the report cannot be viewed as shown in the screenshot.

Am I understanding correctly that you're seeing Lighthouse scores in the deploy logs, but not the UI above the log? Are you able to share any of the output? Do you see any errors or warnings?
I see a call to await lighthouse.onPostBuild({constants, utils, inputs}); in your wrapper - can I ask how are you importing lighthouse here?

Yes. The Lighthouse scores are visible in the deploy logs but not the UI above the log. I've attached the logs.
I'm importing lighthouse plugin as
import * as lighthouse from '@netlify/plugin-lighthouse';

await lighthouse.onPostBuild({constants, utils, inputs});

8:58:19 PM: Mon, 27 Mar 2023 15:28:19 GMT LH:ChromeLauncher Waiting for browser.
8:58:19 PM: Mon, 27 Mar 2023 15:28:19 GMT LH:ChromeLauncher Waiting for browser...
8:58:19 PM: Mon, 27 Mar 2023 15:28:19 GMT LH:ChromeLauncher Waiting for browser.....
8:58:19 PM: Mon, 27 Mar 2023 15:28:19 GMT LH:ChromeLauncher Waiting for browser.....✓
8:58:20 PM: Mon, 27 Mar 2023 15:28:20 GMT LH:config:warn IFrameElements gatherer requested, however no audit requires it.
8:58:20 PM: Mon, 27 Mar 2023 15:28:20 GMT LH:config:warn Inputs gatherer requested, however no audit requires it.
8:58:20 PM: Mon, 27 Mar 2023 15:28:20 GMT LH:status Connecting to browser
8:58:20 PM: Mon, 27 Mar 2023 15:28:20 GMT LH:status Resetting state with about:blank
8:58:20 PM: Mon, 27 Mar 2023 15:28:20 GMT LH:status Navigating to about:blank
8:58:20 PM: Mon, 27 Mar 2023 15:28:20 GMT LH:status Benchmarking machine
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Initializing…
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Preparing target for navigation mode
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Running defaultPass pass CSSUsage, JsUsage, ViewportDimensions, ConsoleMessages, AnchorElements, ImageElements, LinkElements, MetaElements, ScriptElements, IFrameElements, Inputs, MainDocumentContent, GlobalListeners, Doctype, DOMStats, OptimizedImages, PasswordInputsWithPreventedPaste, ResponseCompression, TagsBlockingFirstPaint, FontSize, EmbeddedContent, RobotsTxt, TapTargets, Accessibility, TraceElements, InspectorIssues, SourceMaps, FullPageScreenshot
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Resetting state with about:blank
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Navigating to about:blank
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Preparing target for navigation
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Cleaning origin data
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Cleaning browser cache
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Preparing network conditions
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Beginning devtoolsLog and trace
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Loading page & waiting for onload
8:58:21 PM: Mon, 27 Mar 2023 15:28:21 GMT LH:status Navigating to http://localhost:5100/app/accounts
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:Navigation:error Provided URL did not match initial navigation URL
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: CSSUsage
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: JsUsage
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: ViewportDimensions
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: ConsoleMessages
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: AnchorElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: ImageElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: LinkElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: MetaElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: ScriptElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: IFrameElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: Inputs
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: MainDocumentContent
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: GlobalListeners
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: Doctype
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: DOMStats
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: OptimizedImages
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: PasswordInputsWithPreventedPaste
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: ResponseCompression
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: TagsBlockingFirstPaint
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: FontSize
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: EmbeddedContent
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: RobotsTxt
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: TapTargets
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: Accessibility
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: TraceElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: InspectorIssues
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: SourceMaps
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering in-page: FullPageScreenshot
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering trace
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering devtoolsLog & network records
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: CSSUsage
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: JsUsage
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: ViewportDimensions
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: ConsoleMessages
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: AnchorElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: ImageElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: LinkElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: MetaElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: ScriptElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: IFrameElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: Inputs
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: MainDocumentContent
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: GlobalListeners
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: Doctype
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: DOMStats
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: OptimizedImages
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: PasswordInputsWithPreventedPaste
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: ResponseCompression
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: TagsBlockingFirstPaint
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: FontSize
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: EmbeddedContent
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: RobotsTxt
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: TapTargets
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: Accessibility
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: TraceElements
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: InspectorIssues
8:58:24 PM: Mon, 27 Mar 2023 15:28:24 GMT LH:status Gathering: SourceMaps
8:58:25 PM: Mon, 27 Mar 2023 15:28:25 GMT LH:status Gathering: FullPageScreenshot
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Populate base artifacts
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Get webapp manifest
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Get webapp installability errors
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Collect stacks
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Running offlinePass pass ServiceWorker
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Resetting state with about:blank
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Navigating to about:blank
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Preparing target for navigation
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Preparing network conditions
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Beginning devtoolsLog and trace
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Loading page & waiting for onload
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Navigating to http://localhost:5100/app/accounts
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:Navigation:error Provided URL did not match initial navigation URL
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Gathering in-page: ServiceWorker
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Gathering devtoolsLog & network records
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Gathering: ServiceWorker
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Disconnecting from browser...
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Cleaning origin data
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Analyzing and running audits...
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Uses HTTPS
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Registers a service worker that controls page and `start_url`
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Has a `<meta name="viewport">` tag with `width` or `initial-scale`
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: First Contentful Paint
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Largest Contentful Paint
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: First Meaningful Paint
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Speed Index
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Screenshot Thumbnails
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Final Screenshot
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Total Blocking Time
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Max Potential First Input Delay
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Cumulative Layout Shift
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: No browser errors logged to the console
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Initial server response time was short
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Time to Interactive
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: User Timing marks and measures
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Avoid chaining critical requests
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Avoid multiple page redirects
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Web app manifest and service worker meet the installability requirements
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Provides a valid `apple-touch-icon`
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Configured for a custom splash screen
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Sets a theme color for the address bar.
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Manifest has a maskable icon
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Content is sized correctly for the viewport
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Displays images with correct aspect ratio
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Serves images with appropriate resolution
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Fonts with `font-display: optional` are preloaded
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Avoids deprecated APIs
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Minimizes main-thread work
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: JavaScript execution time
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Preload key requests
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Preconnect to required origins
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: All text remains visible during webfont loads
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Diagnostics
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Network Requests
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Network Round Trip Times
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Server Backend Latencies
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Tasks
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Metrics
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Performance budget
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Timing budget
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Keep request counts low and transfer sizes small
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Minimize third-party usage
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Lazy load third-party resources with facades
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Largest Contentful Paint element
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Largest Contentful Paint image was not lazily loaded
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Avoid large layout shifts
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Avoid long main-thread tasks
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Avoids `unload` event listeners
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Avoid non-composited animations
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Image elements have explicit `width` and `height`
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Page has valid source maps
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Preload Largest Contentful Paint image
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Ensure CSP is effective against XSS attacks
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Full-page screenshot
8:58:30 PM: Mon, 27 Mar 2023 15:28:30 GMT LH:status Auditing: Script Treemap Data
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Site works cross-browser
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Page transitions don't feel like they block on the network
Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Each page has a URL
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[accesskey]` values are unique
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[aria-*]` attributes match their roles
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `button`, `link`, and `menuitem` elements have accessible names
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[aria-hidden="true"]` is not present on the document `<body>`
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[aria-hidden="true"]` elements do not contain focusable descendents
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: ARIA input fields have accessible names
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: ARIA `meter` elements have accessible names
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: ARIA `progressbar` elements have accessible names
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[role]`s have all required `[aria-*]` attributes
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[role]`s are contained by their required parent element
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[role]` values are valid
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: ARIA toggle fields have accessible names
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: ARIA `tooltip` elements have accessible names
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: ARIA `treeitem` elements have accessible names
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[aria-*]` attributes have valid values
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[aria-*]` attributes are valid and not misspelled
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Buttons have an accessible name
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: The page contains a heading, skip link, or landmark region
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Background and foreground colors have a sufficient contrast ratio
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Definition list items are wrapped in `<dl>` elements
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Document has a `<title>` element
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[id]` attributes on active, focusable elements are unique
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: ARIA IDs are unique
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: No form fields have multiple labels
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `<frame>` or `<iframe>` elements have a title
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Heading elements appear in a sequentially-descending order
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `<html>` element has a `[lang]` attribute
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `<html>` element has a valid value for its `[lang]` attribute
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Image elements have `[alt]` attributes
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `<input type="image">` elements have `[alt]` text
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Form elements have associated labels
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Links have a discernible name
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: The document does not use `<meta http-equiv="refresh">`
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `<object>` elements have alternate text
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: No element has a `[tabindex]` value greater than 0
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `[lang]` attributes have a valid value
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: `<video>` elements contain a `<track>` element with `[kind="captions"]`
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Custom controls have associated labels
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Custom controls have ARIA roles
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: User focus is not accidentally trapped in a region
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Interactive controls are keyboard focusable
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Interactive elements indicate their purpose and state
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: The page has a logical tab order
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: The user's focus is directed to new content added to the page
Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Offscreen content is hidden from assistive technology
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: HTML5 landmark elements are used to improve navigation
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Visual order on the page follows DOM order
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Uses efficient cache policy on static assets
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Avoids enormous network payloads
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Defer offscreen images
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Eliminate render-blocking resources
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Minify CSS
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Minify JavaScript
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Reduce unused CSS
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Reduce unused JavaScript
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Serve images in next-gen formats
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Efficiently encode images
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Enable text compression
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Properly size images
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Use video formats for animated content
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Remove duplicate modules in JavaScript bundles
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Avoid serving legacy JavaScript to modern browsers
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Page has the HTML doctype
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Properly defines charset
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Avoids an excessive DOM size
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Avoids requesting the geolocation permission on page load
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: No issues in the `Issues` panel in Chrome Devtools
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Avoids `document.write()`
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Avoids front-end JavaScript libraries with known security vulnerabilities
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Detected JavaScript libraries
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Avoids requesting the notification permission on page load
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Allows users to paste into password fields
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Use HTTP/2
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Uses passive listeners to improve scrolling performance
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Document has a meta description
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Page has successful HTTP status code
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Document uses legible font sizes
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Links have descriptive text
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Links are crawlable
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Page isn’t blocked from indexing
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: robots.txt is valid
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Tap targets are sized appropriately
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Document has a valid `hreflang`
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Document avoids plugins
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Document has a valid `rel=canonical`
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Auditing: Structured data is valid
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:status Generating results...
8:58:31 PM: Mon, 27 Mar 2023 15:28:31 GMT LH:ChromeLauncher Killing Chrome instance 6142
8:58:32 PM: {
8:58:32 PM:   results: [
8:58:32 PM:     {
8:58:32 PM:       title: 'Performance',
8:58:38 PM: Starting post processing
8:58:32 PM:       score: 0.99,
8:58:32 PM:       id: 'performance',
8:58:32 PM:       threshold: 0.85
8:58:32 PM:     },
8:58:38 PM: Post processing - HTML
8:58:32 PM:     {
8:58:32 PM:       title: 'Accessibility',
8:58:32 PM:       score: 0.97,
8:58:32 PM:       id: 'accessibility',
8:58:32 PM:       threshold: 0.9
8:58:32 PM:     },
8:58:32 PM:     {
8:58:32 PM:       title: 'Best Practices',
8:58:32 PM:       score: 0.92,
8:58:32 PM:       id: 'best-practices',
8:58:32 PM:       threshold: 0.9
8:58:32 PM:     },
8:58:32 PM:     { title: 'SEO', score: 0.9, id: 'seo', threshold: 0.9 },
8:58:32 PM:     { title: 'PWA', score: 0.22, id: 'pwa' }
8:58:32 PM:   ]
8:58:32 PM: }
8:58:32 PM: Report collected: audited_uri: 'public/app1', html_report_size: 461.51 KiB

Thank you for the further details! I've taken some time to investigate/reproduce, and the root of the problem is that our systems only expect to show the report UI for the @netlify/plugin-lighthouse specifically. The wrapper plugin you've created is a different plugin (despite encasing the same behaviour), so we don't persist the results/display in the UI in the same manner.
As a workaround, the report can still be persisted to an output path and viewed, as I believe you've already done with your wrapper. Aside from that, I believe the path forward would be the feature request to support the behaviour you're seeking in the Netlify plugin directly.
With that in mind, I'm going to close this issue and create a new one that details the feature request.


Seed Phrase Generate Issue

@ajamaica I am using this library for Android Solana wallet and generating the Seed phrase for create the account, but getting 48 words of seed phrase while generate the phrase. Where In the iOS Solana and Web generated 24 words of seed phrase. So not able to Restore Existing Wallet in the Solana. Can you please guide us where need to change?

There was no Mnemonic bip39 generation. That PR will add this functionality.


Where were the themes in the previous version？

Please check the existing issues to make sure you're not duplicating a report.
For bug reports, please provide the following information:
In a terminal, run zimfw info and paste the output below:
zimfw version: 1.1.1 (previous commit is 6129062)
ZIM_HOME:      /home/lxc/.zim
Zsh version:   5.8
System info:   Linux lxc-PC 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

gist of .zimrc:
gist of .zshrc:
Description

I used the liquidprompt theme for a long time.
Today I reinstall the latest zimfw in the  ~/.zim directory by running
curl -fsSL https://raw.githubusercontent.com/zimfw/install/master/install.zsh | zsh.
I use prompt -l to check the available themes list, however, I don't see the themes in the wiki like eriner in the result, either.
I just want the python virtual environment name and computer name are in the same line.
Steps to reproduce
Images or other information

Hi @daxinnan. Please read the Changelog.
The prompt module now only contains the Zsh default prompts, which are the ones you see listed. Other prompts need to be initialized separately using zmodule. For liquidprompt, it's zmodule nojhan/liquidprompt, as that repository does not belong to the zimfw organization and its not maintened by us.

Thanks, I find the restore theme great too. :smile:


Incase of triggers renaming, new triggers getting created but original triggers not getting deleted with selective deployment of Azure Data Factory

Describe the bug
We are using selective deployment of objects using include exclude rules in file. Observed that if we rename the existing trigger in JSON file and try to publish to ADF then its creating renamed trigger which is expected but still keeping the original trigger in stopped state instead of deleting it (which is not expected). But if we rename pipelines, its deleting old ones and creating with new name which is expected. Seems like this issue observed with only triggers.
To Reproduce
Your script here:
./.github/scripts/deploy.ps1 -SubscriptionName "SubName1" -ResourceGroupName "Test-RG1" -DataFactoryName "Test-DF1" -Location "eastus2" -RootFolder ""/home/runner/work/adf-dev/adf-dev"" -Stage "dev" -DeleteNotInSource:$true -IncludeExcludeFile "./.github/publish-includeexclude-objects.txt"
deploy.ps1 script:
param
(
[parameter(Mandatory = $true)] [String] $SubscriptionName,
[parameter(Mandatory = $true)] [String] $ResourceGroupName,
[parameter(Mandatory = $true)] [String] $DataFactoryName,
[parameter(Mandatory = $true)] [String] $Location,
[parameter(Mandatory = $true)] [String] $RootFolder,
[switch] $DeleteNotInSource = $false,
[String] $Stage = "dev",
[parameter(Mandatory = $true)] [String] $IncludeExcludeFilePath
)
#Install-Module -Name Az.DataFactory -Scope CurrentUser -Force # required by azure.datafactory.tools
Install-Module -Name azure.datafactory.tools -Scope CurrentUser -Force
Import-Module -Name azure.datafactory.tools
#Run TestAdfCode function to validate JSON
Test-AdfCode -RootFolder "$RootFolder"
#Set deploy parameters
$opt = New-AdfPublishOption -FilterFilePath $IncludeExcludeFilePath
$opt.DeleteNotInSource = $DeleteNotInSource
$opt.StopStartTriggers = $true
$opt.DeployGlobalParams = $false
$opt.CreateNewInstance = $false
#Deploy to Data Factory
Publish-AdfV2FromJson -RootFolder "$RootFolder" -ResourceGroupName "$ResourceGroupName" -DataFactoryName "$DataFactoryName" -Location "$Location" -Stage $Stage -Option $opt
Objects publish-includeexclude-objects.txt file:
+pipeline.test_selectivemigration_pipeline1
+trigger.test_selectivemigration_trigger1
Expected behaviour
If triggers are renamed then it should create new trigger as per renaming and should delete the one with old name instead of keeping it in stopped state.
Screenshots
If applicable, add screenshots to help explain your problem.
Version of PowerShell module of:
azure/powershell@v1
Importing module > 1.10.0
Provide all files to reproduce the issue

Attach at least log file (you can wipe out any potentially sensitive info)
Attach files of objects which are involved in the process

Detailed Deployment Log:
STEP: Reading Azure Data Factory from JSON files...
IntegrationRuntimes: 1 object(s) loaded.
LinkedServices: 10 object(s) loaded.
Pipelines: 79 object(s) loaded.
DataSets: 27 object(s) loaded.
DataFlows: 0 object(s) loaded.
Triggers: 14 object(s) loaded.
Managed VNet: 0 object(s) loaded.
Managed Private Endpoints: 0 object(s) loaded.
Factories: 1 object(s) loaded.
Number of objects marked as to be deployed: 1/132

[trigger].[test_selectivemigration_trigger3]

STEP: Stopping triggers...
Getting triggers...
The number of triggers to stop: 12 (out of 17)
Stopping deployed triggers:

Disabling trigger: TEST1 trigger
Disabling trigger: TEST3 trigger
Disabling trigger: TEST4 trigger
Disabling trigger: TEST5 trigger
Disabling trigger: TEST6 trigger
Disabling trigger: TEST2 trigger
Disabling trigger: TEST7 trigger
Disabling trigger: TEST8 trigger
Disabling trigger: TEST9 trigger
Disabling trigger: TEST10 trigger
Disabling trigger: TEST11 trigger
Disabling trigger: TEST12 trigger
Complete stopping deployed triggers

STEP: Deployment of all ADF objects...
Deployment of Global Parameters will be skipped as publish option 'DeployGlobalParams' = false
Start deploying object: [trigger].[test_selectivemigration_trigger3] (1 dependency/ies)
Finished deploying object: [trigger].[test_selectivemigration_trigger3]
STEP: Deleting objects not in source ...
Azure Data Factory (instance) loaded.
DataSets: 27 object(s) loaded.
IntegrationRuntimes: 1 object(s) loaded.
LinkedServices: 10 object(s) loaded.
Pipelines: 79 object(s) loaded.
DataFlows: 0 object(s) loaded.
Triggers: 18 object(s) loaded.
STEP: Starting all triggers...
The number of triggers to start: 12

Enabling trigger: TEST1 trigger
Enabling trigger: TEST3 trigger
Enabling trigger: TEST4 trigger
Enabling trigger: TEST5 trigger
Enabling trigger: TEST6 trigger
Enabling trigger: TEST7 trigger
Enabling trigger: TEST8 trigger
Enabling trigger: TEST9 trigger
Enabling trigger: TEST10 trigger
Enabling trigger: TEST11 trigger
Enabling trigger: TEST2 trigger
Enabling trigger: TEST12 trigger

Hi @NowinskiK, Can you please let me know if you have any update on this issue.

Not really. This case requires preparation of whole PS script to be able to test it.
If you can prepare such script and attach all required files to prove this is really happens and it is repeatable - that can help me to investigate that over reduce amount of time required.

I have uploaded requested files, please rename them as mentioned below.
Rename "deploy powershell script.txt" to "deploy.ps1"
Rename "test_selectivemigration_pipeline1 JSON.txt" to "test_selectivemigration_pipeline1.json"
Rename "test_selectivemigration_trigger1 JSON.txt" to "test_selectivemigration_trigger1.json"
Command to Run:
./.github/scripts/deploy.ps1 -SubscriptionName "SubName1" -ResourceGroupName "Test-RG1" -DataFactoryName "Test-DF1" -Location "eastus2" -RootFolder ""/home/runner/work/adf-dev/adf-dev"" -Stage "dev" -DeleteNotInSource:$true -IncludeExcludeFile "./.github/publish-includeexclude-objects.txt"
Uploaded below files.
publish-includeexclude-objects.txt
deploy powershell script.txt
publish-includeexclude-objects.txt
test_selectivemigration_pipeline1 JSON.txt
test_selectivemigration_trigger1 JSON.txt

Hi @NowinskiK, As requested I have uploaded the PS script. Could you please let me know if you have any update.

Thanks for attaching the files, including the script.
Unfortunately, I can't see how that can help to reproduce the issue.
The script contains only one execution of Publish-AdfV2FromJson, do it will create 1 trigger and 1 pipeline; that's it.
Of course, after the first run I can rename the trigger and rerun the script again - I just need to be sure that you tested the feature in exactly that way?

@NowinskiK  Yes we tested with only one pipeline and trigger only, if we rename any trigger then ADF not deleting the original trigger and we end up having 2 triggers. Please let me know if you have any more questions.

I prepared appropriate and full test script, it is in the repo now:
https://github.com/SQLPlayer/azure.datafactory.tools/tree/develop/adhoc/issue-223
Additionally, I recorded quick video to show you, that the scenario you described, works:
https://youtu.be/B_IgLfAdLgg

Probably I know what scenario you're referring to.
Yes, it will omit deleting renamed trigger if it's excluded from the deployment.
In such case you must set the option DoNotDeleteExcludedObjects = false, which means it will delete excluded objects.
Doc reference:
Step: Deleting objects not in source


delaylock: delay lock 5 sec after backlight off

New bootloader app for delaying the locking of the touchscreen to 5 seconds after the backlight turns off. Giving you the chance to interact with the watch without having to press the hardware button again.
Inspired by the conversation between @gfwilliams and user156427 linked here: https://forum.espruino.com/conversations/392219/
Can be installed from my app loader: https://thyttan.github.io/BangleApps/?id=delaylock

LGTM, thanks!


"Receive" option in navbar and standalone page

Acceptance Criteria

[ ] "Receive Tokens" option in the navbar
[ ] User scans QR code and is redirected to /send-money/<accountID>
[ ] Mobile ok
[ ] Tested

Assets
Description and mockup

@Patrick1904 @kcole16 let's also add QR scanner in "Send" as most people (in US at least) don't know how to scan QR code.
https://github.com/nimiq/qr-scanner looks good in terms of code size impact. Also most likely https://parceljs.org/code_splitting.html#using-dynamic-imports can be used to reduce impact when it's not needed.


Make it easy to generate roles for the dr-cluster and hub flavor of the operator

Currently, we run the make manifests target to generate the crds, roles, webhooks for the code we have in our repo.
This generates the config/rbac/role.yaml file for the roles. Then the developer has to copy the updated/generated lines over to the right file config/hub/rbac/role.yaml or config/dr-cluster/rbac/role.yaml depending on where the +kubebuilder:rbac: lines were updated.
This is

manual
error-prone
not documented

We should make this process easier.
More details:

output one shows where we have the +kubebuilder:rbac marker lines in our code.
output two shows the current splits between dr-cluster and hub roles.

$ grep -nri "+kubebuilder:rbac:" ./* | grep -v "Binary file" | cut -d":" -f1 | sort | uniq
./internal/controller/drcluster_controller.go
./internal/controller/drclusterconfig_controller.go
./internal/controller/drplacementcontrol_controller.go
./internal/controller/drpolicy_controller.go
./internal/controller/kubeobjects/velero/requests.go
./internal/controller/protectedvolumereplicationgrouplist_controller.go
./internal/controller/replicationgroupdestination_controller.go
./internal/controller/replicationgroupsource_controller.go
./internal/controller/volumereplicationgroup_controller.go

$ wc -l config/rbac/role.yaml config/dr-cluster/rbac/role.yaml config/hub/rbac/role.yaml
     434 config/rbac/role.yaml
     275 config/dr-cluster/rbac/role.yaml
     220 config/hub/rbac/role.yaml
     929 total

Let's start by documenting the process of adding new rbac rules. I'm sure that if you ask current developers how to do this most will fail to describe the right process.


Origin line renders incorrectly in Compatibility rendering method on Mali GPU

Tested versions

Reproducible 4.2.1 [Stable], and versions from the end of last year, I don't know what version is, but, it happens on a old version too

System information
Android 14 Godot 4.2.1 Stable Mali GPU
Issue description
On the editor happens this, just when using compatibility renderer

Steps to reproduce
Open the Godot on Compatibility renderer with a Samsung Galaxy A13 (Europe version)
Minimal reproduction project (MRP)
ShinobiWarSim.zip

Most likely a regression from https://github.com/godotengine/godot/pull/83895

@Lufims Did the issue go away with the latest update?

@Lufims Did the issue go away with the latest update?

Yes, but now the world grid is doing the same thing, or before it was too, but I didn't see, anyway, now I can make games without being annoyed by a glitch, thanks


GCP Datastore provider

Looks great, thanks. Can you please test both concurrency modes? (I am not familiar with the Datastore, so I am not sure it will work, or if it makes sense)

According to the reading The default concurrency mode on newly provisioned Datastore instance is PESSIMISTIC (running firestore in datastore mode) and based on the documentation of the emulator there doesn't seem a way to set the concurrency mode on the emulator itself.
To make matters worse, there isn't a mechanism to introspect the concurrency mode from the client that I'm aware of so as to fail fast upon finding on an unsupported concurrency mode. I have yet to test it on other concurrency mode as I am limited on privilege to do so.
The option that I can see is to have this documented in the usage guide. What do you think?

It's OK by me. Can you please do the small changes from the comments? Then we can merge it and release it. Thanks again


Fix for Issue #22

Initial fix for Issue #22.
@vkuznet While working on this, I have a few questions:

Does datasets GET API require dataset_access_type parameter for each request? Only way to make dataset GET tests work is by including dataset_access_type for each of the tests:
https://github.com/d-ylee/dbs2go/blob/4e37beb2f4e73c4283ee218607d3c226fb3a9008/test/int_datasets.go#L220
Problems when using parent_dataset as a parameter: I get a SQL malformed error when trying to use parent_dataset as a parameter around the WHILE clause: https://github.com/d-ylee/dbs2go/blob/4e37beb2f4e73c4283ee218607d3c226fb3a9008/dbs/datasets.go#L99

@d-ylee to answer your questions:

no, there is no mandatory parameters for datasets API, it should work with and without dataset_access_type parameter. In this case the datasets API will return all datasets regardless of their status
we should fix datasets.sql template to account for parent_dataset lookup like this

...
{{else}}
        D.DATASET
{{end}}
{{if .ParentDataset}}
        ,PDS.DATASET PARENT_DATASET
{{end}}

i.e. put parent dataset at the end of select clause and then remove PARENT_DATASET from conds statement like this:
conds, args = AddParam("parent_dataset", "PDS.DATASET", a.Params, conds, args)

Please make these adjustments and test the code.

@vkuznet
In my integration tests, I have been using PRODUCTION as the dataset_acces_type. https://github.com/dmwm/dbs2go/blob/50f05b9495b098adae976e52c91777996b99c6ac/test/data/integration/integration_data.json#L8
Does this logic have dataset_access_type default to only finding rows that have it set to VALID and not show rows that have it set to other values, such as PRODUCTION, DELETED, DEPRECATED, or INVALID, as listed when accessing https://cmsweb.cern.ch/dbs/prod/global/DBSReader/datasetaccesstypes
https://github.com/dmwm/dbs2go/blob/50f05b9495b098adae976e52c91777996b99c6ac/dbs/datasets.go#L78-L98

yes, by default this API should only list VALID datasets, and I suggest that you check this in a test with and w/o dataset_access_type varaible


Bump istanbul to 0.4.5

Coverage decreased (-6.3%) to 85.551% when pulling 0c5f48ca647ed861f4dc432542c44b5586b9b1a2 on SAP:istanbul into 18dbe79a852a95a952e28e25851718ca0a756d41 on cloudfoundry-incubator:master.


🚨 WIP: Update theme docs 🚨

Nothing in this doc should be considered final until it is merged!

Thanks all for catching all my typos ❤

Pushed a few tiny changes and then fixed the conflict with main.  Things look fine to me - but you certainly know the status of theme stuff more than I do 🤣

Awesome gunna merge it! Thanks for contributing everyone.


Free-floating visualization responses with failures

As per log entry
[org.enso.languageserver.runtime.RuntimeConnector] No sender has been found associated with request id [e715b5da-a7bc-4261-8b43-156eae6bd86c], the response [org.enso.polyglot.runtime.Runtime.Api$.VisualizationExpressionFailed] will be dropped.

No other indication of the failure, the request id does not appear to exist anywhere else.

It kinda feels plausible because we send the reply in (1) and (2), thus removing them from the senders' list https://github.com/enso-org/enso/blob/develop/engine/language-server/src/main/scala/org/enso/languageserver/runtime/RuntimeConnector.scala#L128.

This has changed (regressed?) in https://github.com/enso-org/enso/commit/e529f7bb3b0fbc98a39c9a460cfda439d4458549

Closing - will add a new one if we see in GUI2.


Failed to minify the code from this file: #create-react-app

Creating an optimized production build...
Failed to compile.
Failed to minify the code from this file:
    ./node_modules/react-form/dist/index.es.js:168:22

Read more here: http://bit.ly/2tRViJ9

System info
macOs M1 (MBP)
node: v16.2.0
npm: 7.13.0

Hey all, I'm closing this issue as it appears to be related to a version of the old non-current @tanstack/react-form and friend APIs. We're looking to 1.x soon enough, and I want to more easily filter down to more recent issues.
Thanks for being early adopters of our tooling! We know that it can lead to issues like this being unresolved sometimes, but we're working hard on the new iteration of Form.
Maybe take a look and let us know what you think?
https://tanstack.com/form
Best,

Corbin


Fetch recently updated packages to sync

https://www.npmjs.com/browse/updated

page 1: https://www.npmjs.com/browse/updated?offset=0
page 2: https://www.npmjs.com/browse/updated?offset=36
page 3: https://www.npmjs.com/browse/updated?offset=72
page 4: https://www.npmjs.com/browse/updated?offset=108
page 5: https://www.npmjs.com/browse/updated?offset=144

Read from window.__context__.context.packages

window.context = {"context":{"title":"recently updated packages","packages":[{"name":"@htmlbricks/bootstraplayout-component","description":"Svelte Bootstrap 5 WebComponent","maintainers":["dariocaruso"],"dist-tags":{"latest":"0.1.31"},"lastPublish":{"maintainer":"dariocaruso","time":"2021-12-18T14:01:46.030Z"},"types":{},"publisher":


Replication service enhancement.

Remote cert verification to target level. P0
Permission adjustment (project admin can handle) - P0
Wildcard list for tag in replication rule to control tags.  - P0 for backend.  todo: refine.
Replicate/deletion only in replication rule - P1
System level replication policy: filter, target.  (schedule) Project policy will overwrite system policy. - P1
Batch pull image into Harbor (manual, per namespace). - P1
Multiple targets for a policy - P1
Scheduling for replication job, certain time - P2
Not all of the work will be done before pks-1.0, but need to make sure there's feature hole or inconsistency for that release.

Draft estimation:
core 4w
filter 1w
replicator 1w
UI 2w
test&fix 1w


Port not being parsed to an int

Sorry we can't quite pinpoint what broke it, but some combination of updated packages started throwing the following error:
host and port must be specified

from connection_pool.js:8
So we did a quick fix by making connect-mongo.js:43 be this:
options.port = parseInt(db_url.port);

to handle the case of a url being passed into the MongoStore constructor, because url.parse leaves port as a string.

are you using node >= 0.5.0 ?

No. I believe it's 0.4.11
And maybe it's something else with our setup.
Thanks,
-Jed
On Nov 12, 2011, at 10:07 AM, Tomas<EMAIL_ADDRESS>wrote:

are you using node >= 0.5.0 ?

Reply to this email directly or view it on GitHub:
https://github.com/kcbanner/connect-mongo/issues/15#issuecomment-2718025

I tested with 0.4.12 and there url.parse() also returns the port as a string. So I think the tests have been failing for a long time and nobody noticed.

Interesting. Maybe most people are using the parameter signature instead of a URL string.
Thanks for following up.
-Jed
On Nov 12, 2011, at 10:32 AM, Tomas<EMAIL_ADDRESS>wrote:

I tested with 0.4.12 and there url.parse() also returns the port as a string. So I think the tests have been failing for a long time and nobody noticed.

Reply to this email directly or view it on GitHub:
https://github.com/kcbanner/connect-mongo/issues/15#issuecomment-2718145

same issue here with node 0.4.12

Same issue here with node 0.6.2, and the parseInt trick fixed it.

New version pushed to npm. Sorry I was so slow on this guys, school makes you a bad maintainer!

Haha no problems!  Thanks for connect-mongo and let me know if you need any co-maintainers.

kcbanner: I see npm has connect-mongo updated to 0.1.7, but package.json is still 0.1.6 here on github. did you forget to push?


What do  Webhook Token and ID means?

any idea about webhook' token and ID?

Turns out you can just copy your self-made webhook from your server, both the IDs and the TOKEN is on the copied url


Discord link doesn't work properly

clicking on the discord link requires a refresh to apply properly
solution: open in new tab?

Fixed in 7bab229070dec06447650069c783c381cf9eceaf


Create solution2.py

Description of Change

References

Checklist

[x] Added detailed description of changes.
[ ] Relevant documentation/comments is changed or added.
[x] Added file name matches File name guidelines.
[ ] PR title follows semantic commit guidelines.

Notes:

Added python solution


ConnectionPool Chunked

Just too many .ts pieces that the threads ocuupied all, then the Connection get chunked..
Hoping for improving
testUrl = "https://v02.qooqlevideo.com/t/1500240326/aO5KJx322k_zigBjSO1icw/2617/hd/stream.m3u8"

@Yodamt ,sorry,can not open the url.


npm audit security report for shipit-deploy

Low             Prototype Pollution
Package         lodash
Patched in      >=4.17.5
Dependency of   shipit-deploy [dev]
Path            shipit-deploy > shipit-utils > lodash
More info       https://nodesecurity.io/advisories/577
See https://github.com/shipitjs/shipit-utils/issues/6

I created a pull request, see https://github.com/shipitjs/shipit-utils/pull/7


Fix date shown when editing a field slip

coverage: 93.414% (+0.001%) from 93.413%
when pulling 46e460b55bd9f0c31382c469d3428eae81ff5f38 on njw-fs-edit-date
into 0b90fdf45d8e94ce02b05b98abebe0947a83bc58 on main.


BUG IN SETAVATAR

Please tick all applicable boxes.

[x] I am using Python 3.5 or higher (run python --version on the command line)
[x] I have followed the official guides to install the bot for my system
[x] I have updated my dependencies to the latest version using the appropriate update script

Which version are you using?

[ ] The latest master version (1.9.7)
[x] The latest review version

What type of issue are you creating?

[x] Bug
[ ] Feature request
[ ] Question

Description of issue
a bug in the setavatar command
there was someone who's case was not reproducible
in particular module 'aiohttp' has no attribute 'Timeout'
in the setavatar command changing
this
        try:
            with aiohttp.Timeout(10):
                async with self.aiosession.get(thing) as res:
                    await self.user.edit(avatar=await res.read())

to this
        try:
            with async_timeout.timeout(10):
                async with self.aiosession.get(thing) as res:
                    await self.user.edit(avatar=await res.read())

will fix the problem
however it might not be a long term solution however it does make the link uploading work at the very least
Steps to reproduce

attempting to change the avatar from a link
note: uploading images as an avatar doesn't work because of this bug

Log file
Please attach your MusicBot log file (located at logs/musicbot.log) to this issue. You can do so by dragging and dropping the file here. If you do not include your log file, you WILL be asked to provide one.
musicbot.log

I didn't test your solution, however 5 seconds in the aiohttp documentation, I found this, and made
        try:             timeout = aiohttp.ClientTimeout(total=10)             async with aiohttp.ClientSession(timeout=timeout):                 async with self.aiosession.get(thing) as res:                     await self.user.edit(avatar=await res.read())
Although this works, it led to
168118999337402368/Aleana#2643: !setavatar [ERROR:bot] Exception in on_message Traceback (most recent call last):   File "/mnt/secondary/aleana/test/MusicBot/musicbot/bot.py", line 2726, in on_message     response = await handler(**handler_kwargs)   File "/mnt/secondary/aleana/test/MusicBot/musicbot/bot.py", line 137, in wrapper     return await func(self, *args, **kwargs)   File "/mnt/secondary/aleana/test/MusicBot/musicbot/bot.py", line 2445, in cmd_setavatar     thing = message.attachments[0]['url'] TypeError: 'Attachment' object is not subscriptable
Once I work out the kinks with set avatar here, I'll make a PR to solve this issue.

See the above PR @OzoneHelix

@AutumnClove thank you

what I discover was a partial fix it fixed links but not uploading an image

I tested your solution and got this result in VSC before even starting the bot
Undefined variable 'async_timeout'

its odd because when I tried your solution it was looking in init.py for it which makes no sense

darn github's formatting

Error given when trying my solution?

Unable to change avatar: module 'aiohttp' has no attribute 'ClientTimeout'

its really weird

I should probably say I'm using Pycham and not VSC

If you update your dependencies for review, you'll most likely solve that error. The current requirements.txt for d.py rewrite requires aiohttp>=3.3.0,<3.4.0 which has ClientTimeout

wait correction I have python 3.5.2 installed

ok after installing python 3.6.6 your solution works completely my solution half worked so this is much better

I removed python 3.5.2 and now using python 3.6.6 the setavatar command works completely

travis also seemed to have failed when trying to use python3.5

That's a known issue.

well lets hope it will be resolved in the future


mrpt2: 2.13.5-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository mrpt2 to 2.13.5-1:

upstream repository: https://github.com/MRPT/mrpt.git
release repository: https://github.com/ros2-gbp/mrpt2-release.git
distro file: humble/distribution.yaml
bloom version: 0.12.0
previous version for package: 2.13.4-1

This pull request has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/preparing-for-humble-sync-and-patch-release-2024-08-06/38909/2

@audrow What do you think about merging this one to fix the regression @jlblancoc mentioned?


Implement Quick Sort Algorithm in JavaScript

This issue is about Quick Sort Algorithm

✅  I searched or browsed the repo’s other issues to ensure this is not a duplicate

✅ Issue Title is Quick Sort Algorithm in Javascript

✅ I will send my PR only after I'm assigned to this issue by any maintainer

✅ Assign this issue to me

✅ I ensure that I am not already assigned to 2 or more issues

@Claribell I've assgined this issue to you!

@sobhanbera please assign this issue to me, i want to close it asap. I'm really interested.


docs-bug(Button): Alignemt of buttons is broken in the "Basic buttons" of buttons docs

Documentation Feedback
Alignemt of buttons is broken in the "Basic buttons" section of the docs page.
See the below screenshots for more details (Disabled Icon button is under Accent Flat button and many other cases).
V15 (broken):

V14 (Ok):

Affected documentation page
https://v15.material.angular.io/components/button/overview
Browser
Google Chrome 108.0.5359.125

This is being set by MDC here: https://github.com/material-components/material-components-web/blob/master/packages/mdc-button/_button-shared-theme.scss#L45.
It follows the button material spec, where buttons without any borders have a padding of 8px versus 16px if they do.


Fix: Backport #5275 to release-1.6

Description of your changes

Update pkg dependency, refer to https://github.com/kubevela/pkg/pull/28 https://github.com/kubevela/kubevela/pull/5275
Fixes #5556
I have:

[ ] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

@wonderflow @chivalryq  There will be some conflicts in unit tests. Is it okay to resolve these conflicts?Will it affect its original function？

@suwliang3 Good job. You can try to solve the conflicts. I guess most of them won't affect the function. They are just API incompatibility caused by version bumping.

Check-diff job failed because the controller-gen version in CI is bumped. Please run make reviewable to include the differences. @suwliang3

why there're so many changes while #5275 only changes 6 lines.

It should be the reason for the package version dependency. @chivalryq

ping @wonderflow


added Ubuntu dependency list to readme

Thanks for your PR. This is much appreciated! We just made a new release with some changes to the README on the release branch. Unfortunately that means that this change doesn't apply anymore. We removed the build instructions from the README and have them only in our documentation to avoid having to keep the two in sync.
Would you mind rebasing onto master (I've just merged the release branch into master) and adding a section over here instead? You could more or less copy the Arch Linux instructions and replace it with the Ubuntu commands.


Fix test

Hi, thanks for the work on this project, it really makes benchmarking with different distributions very easy!
I fixed a test and added how to create graphs from the benchmarking data.
The older version of bokeh is needed, because figure() does not accept a field named plot_height in the latest release.
The older one still has it as a compatibility layer.

Thanks for the kind words, I'm glad to hear it can easily be used. This started out as a personal research project and most of the features were developed to make my life easier. It's also grown into a bunch of different things. Might make sense to separate them out more clearly in the future.


Cretbot sslwith cloudflare as dns

I followed your tutorial https://github.com/antonputra/tutorials/tree/main/lessons/078
Great one, but I used cloudflare as my DNS and came to an issue which caused a redirection loop
This one got resolved by enabling full strict on ssl/tsl>overview>full strict
Can I create a pull request to make this tutorial page better and address the issue since cloud flare is widely used dns.
Here is a reference for you https://serverfault.com/questions/1109368/cretbot-ssl-certificate-not-working-properly/1109370#1109370

Thanks, merged


I am having trouble accessing code study groups in my area.

Hi I sent you an email already however i am not receiving a response i would highly appreciate it if you responded and potentialy provide a phone number that i can contact someone with, thank you. And i also tried the link in google chrome on windows and logged in.

//and the link failed sorry for misconception.
// lol i am commenting in code.


RTL support

GitBook editor is missing an RTL (right-to-left) writing support.
Ace Editor is known to support it though.

I've found this project from the mentioned bug backlinks and it is fantastic... CodeMirror supports RTL well and after that a little style hacking would be needed of course.

If it is still relevant ACE might be good now from RTL point of view - please check ajaxorg/ace#1429


updated rails to 5.1.5 and fixed docker error

I rule and have completed some work on Case Manager that's ready for review!
(brief, plain english overview of your changes here)
This pull request makes the following changes:

updates rails to 5.1.5
fixes a docker bug identified and fixed by @colinxfleming for starting up virtual box

Codecov Report

Merging #1384 into master will increase coverage by 0.72%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #1384      +/-   ##
=========================================
+ Coverage   93.47%   94.2%   +0.72%
=========================================
  Files          61      61
  Lines        1380    1380
=========================================
+ Hits         1290    1300      +10
+ Misses         90      80      -10

Impacted Files
Coverage Δ

app/models/concerns/user_searchable.rb
92.85% <0%> (+3.57%)
:arrow_up:

app/models/event.rb
96.66% <0%> (+6.66%)
:arrow_up:

app/models/concerns/attribute_displayable.rb
85.71% <0%> (+7.14%)
:arrow_up:

app/helpers/events_helper.rb
100% <0%> (+66.66%)
: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 e648950...c62868f. Read the comment docs.


add annotatin declaration support

fixes: #648

Can you post an apiview with this fix applied?

https://apiview.dev/Assemblies/Review/8520e97afd3045e2942f5d9b7a6a77b3#com.azure.search.documents.indexes.FieldIgnore

You missed a version update in the c# code

how about now?

// cc @pakrym for a new release of APIView when time allows. Thanks.

I'm out tomorrow but @mssfang and @praveenkuttappan have access to deployment approval for the site.


old sketch continues to be served on port 3000

I can't full explain or pinpoint the steps to reproduce this (will follow up when I can), but I'm experiencing a problem where a sketch a ran when first working with the editor today continues to run even if I quit the editor, make a new project, etc.

The only way I can get something to run is to leave the above sketch open and run a new one (which is served on 3001).

I wonder if this is the same situation, or related to #68?

Ah, after some poking around I believe this is the same bug.  Will close and can re-open if I notice something more/new after #68 is resolved.


GitHub Pages not reflecting the change

The recent changes to the package updates made by @chestrada do not reflect the change on the public page.  Investigate and provide a fix.

Issue is all but fixed! Ran the npm update and changes are on master. 'security-updates' is ready for removal.


mstdn.exe toot failed because -i option's value type remained int64 yet.

$ mstdn toot hogehoge
bad request: 404 Not Found: Record not found
exit status 1

-i option's default should be empty-string, but it was 0 as int64.
I tried to fix it. Would you merge if there are no problems ?

Coverage decreased (-0.1%) to 85.674% when pulling aaeb9f1de2219bfa992afbd862cb1e6b59f309d0 on zetamatta:fix-mstdnexe-toot-iflag into d38a3e6dfcc25e799eaecd9fc4e7bbe5b6262ea3 on mattn:master.

Thank you


[SPARK-48196][SQL] Turn QueryExecution lazy val plans into LazyTry

What changes were proposed in this pull request?
Currently, when evaluation of lazy val of some of the plans fails in QueryExecution, this lazy val remains not initialized, and another attempt will be made to initialize it the next time it's referenced. This leads to planning being performed multiple times, resulting in inefficiencies, and potential duplication of side effects, for example from ConvertToLocalRelation that can pull in UDFs with side effects.
Why are the changes needed?
Current behaviour leads to inefficiencies and subtle problems in accidental situations, for example when plans are accessed for logging purposes.
Does this PR introduce any user-facing change?
Yes.
This change would bring slight behaviour changes:
Examples:
val df = a.join(b)
spark.conf.set(“spark.sql.crossJoin.enabled”, “false”)
try { df.collect() } catch { case _ => }
spark.conf.set(“spark.sql.crossJoin.enabled”, “true”)
df.collect()

This used to succeed, because the first time around the plan will not be initialized because it threw an error because of the cartprod, and the second time around it will try to initialize it again and pick up the new config. This will now fail, because the second execution will retrieve the error from the first time around instead of retrying.
The old semantics is if plan evaluation fails, try again next time it's accessed and if plan evaluation ever succeeded, keep that plan. The new semantics is that if plan evaluation fails, it keeps that error and rethrows it next time the plan is accessed. A new QueryExecution object / new Dataset is needed to reset it.
Spark 4.0 may be a good candidate for a slight change in this, to make sure that we don't re-execute the optimizer, and potential side effects of it.
Note: These behaviour changes have already happened in Spark Connect mode, where the Dataset object is not reused across execution. This change makes Spark Classic and Spark Connect behave the same again.
How was this patch tested?
Existing tests shows no issues, except for the tests that exhibit the behaviour change described above.
Was this patch authored or co-authored using generative AI tooling?
Trivial code completion suggestions.
Generated-by: Github Copilot

@cloud-fan @JoshRosen
Given the change, do you think it would make sense to add a copy() API to Dataset, sth like
/**
 * Create a copy of this Dataset with a fresh execution.
 *
 * While a Dataset object caches its query plan, this will create a new Dataset that will
 * start from scratch from the parsed logical plan.
 */
def copy(): Dataset[T] = {
  new Dataset[T](this.sparkSession, this.queryExecution.logical, this.encoder)
}

so that users can re-run all stages that are otherwise lazy cached?
It was relevant also before this change, because I don't think there was a no-op way to get a "fresh" Dataset object? I suppose the closest to noop would have been .as[T] with T being the existing encoder, but one would need to know the encoder of the Dataset to pass it.

Same issue with Pytorch dataloader:
Starting test(python3.11): pyspark.ml.tests.connect.test_parity_torch_data_loader (temp output: /__w/apache-spark/apache-spark/python/target/48a24a54-af73-4bf1-8b17-c2962e25b85c/python3.11__pyspark.ml.tests.connect.test_parity_torch_data_loader__t8i37nvz.log)
Error: The operation was canceled.

🤷

thanks, merging to master!


Registration at apps.dev.microsoft.com portal is deprecated

sample recommend to register at https://apps.dev.microsoft.com portal which is deprecated.  Please update instruction

Hi bachong, its not deprecated for b2c tenants yet.


added = and ; to satisfy jshint

One error is still thrown ("Don't make functions within a loop") which probably cannot be resolved that easily. The comment /* jshint loopfunc:true */ might be helpful

I have added another major improvement (sorry if this wasn't the right way, new to GitHub, forking and pull requests). The draw method has been broken for redrawing - this can be seen in the Spring example when you hit the redraw button. It will effectively kick some nodes off the screen. Why? Because the translation has been applied twice. I removed the unnecessary code (which should also improve performance)


fix: discord 아이콘의 색상을 github 아이콘 색상과 통일합니다

Overview
ASIS.

TOBE.

아이콘 색상을 통일합니다.
PR Checklist

[X] I read and included theses actions below

I have read the Contributing Guide
I have written documents and tests, if needed.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.53%. Comparing base (64ff16e) to head (4ea8046).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #291   +/-   ##
=======================================
  Coverage   99.53%   99.53%
=======================================
  Files          38       38
  Lines         642      642
  Branches      156      156
=======================================
  Hits          639      639
  Misses          3        3

----
🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles


"来園者" needs to be replaced with "ゲスト"

Strongly recommend to replace "来園者" with "ゲスト" , I can see "来園者" is used as a localized Japanese word of "guest" in English, however, it should be "ゲスト" which stands for guest user of Microsoft Teams.
https://docs.microsoft.com/ja-jp/microsoftteams/microsoft-teams-online-call-flows#feedback

ドキュメントの詳細
⚠ このセクションを編集しないでください。 docs.microsoft.com で必須です ➟ GitHub の問題のリンク。

ID: 43c84773-337e-9df7-7fbd-fc9d94280711
Version Independent ID: 223a78a0-67fd-8b96-be3f-153bb400101b
Content: Microsoft Teams 通話のフロー
Content Source: Teams/microsoft-teams-online-call-flows.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

@hyoshioka0128 - Thank you for submitting this feedback.
I will get this over to for investigation. Thank you for reporting and making the docs better. Much appreciated.

@officedocsbot assign @scanum

@OfficeGlobal

@OfficeGlobal following up on this issue? Could you please update status? Thanks

@hyoshioka0128 , @scanum string was updated and published live. The issue is fixed

@hyoshioka0128 Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

@officedocsbot close