A/B testing on scan pause command

@tacaswell and I are having a disagreement on what hitting ctrl+c should do.
@tacaswell wants this behavior:
...scan is running
[user input] ctrl+c captured
...behind the scenes there is a 0.5 second timeout that is waiting for another
   ctrl+c. If this other ctrl+c is captured, the scan will end with an Abort state
...if no additional ctrl+c is received within 0.5 seconds, the user is dropped
   back to the IPython REPL

@ericdill wants this behavior:
...scan is running
[user input] ctrl+c captured

You pressed ctrl+c. Do you want to:
(r) resume the scan
(a) abort the scan (bad exit state)
(s) stop the scan (good exit state)
(p) pause the scan (and return to the REPL)

Note that an additional ctrl+c will (a)bort the scan.
input -->

...indefinitely wait for user input.

It seems like the right approach here is to do some A/B testing!  Build both and see which one users like!
cc @danielballan

Sure, as long as we pick a winner in the near future.
I implemented something like the second way on a branch awhile back, except
that the pause happens immediately and the user only gets to choose what
happens next.
I came around to the first way yesterday in conversation with Claudio,
Stuart, and Andy.
I'll show them both and see what they like.
On Tue, Aug 4, 2015 at 11:11 PM Eric Dill<EMAIL_ADDRESS>wrote:

@tacaswell https://github.com/tacaswell and I are having a disagreement
on what hitting ctrl+c should do.
@tacaswell https://github.com/tacaswell wants this behavior:
...scan is running
[user input] ctrl+c captured
...behind the scenes there is a 0.5 second timeout that is waiting for another ctrl+c. If this other
ctrl+c is captured, the scan will end with an Abort state
...if no additional ctrl+c is received within 0.5 seconds, the user is dropped back to the IPython REPL
@ericdill https://github.com/ericdill wants this behavior:
...scan is running
[user input] ctrl+c captured
You pressed ctrl+c. Do you want to:
(r) resume the scan
(a) abort the scan (bad exit state)
(s) stop the scan (good exit state)
(p) pause the scan (and return to the REPL)
Note that an additional ctrl+c will (a)bort the scan.
input -->
...indefinitely wait for user input.
It seems like the right approach here is to do some A/B testing! Build
both and see which one users like!
cc @danielballan https://github.com/danielballan
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/bluesky/issues/152.

My real concern with the first option above is that the user will be returned to the REPL with no clear indication of what to do next.  That concern is the entire motivation with the (perhaps unecessarily) complicated input prompt I proposed.
How about this. I am fully on-board with @tacaswell 's option above (which might actually be @danielballan 's suggestions, I'm not sure how the credit falls out here!), but print out a few lines that is (roughly) like this and then return the user to the REPL with the run engine in a paused state. Unless two ctrl+c's are intercepted which should (abort or stop?) the scan.
Your RunEngine is now in a paused state. These are your options for changing
the state of the RunEngine:

resume()  --> will resume the scan
 abort()  --> will kill the scan with an 'aborted' state to indicate
              the scan was interrupted
  stop()  --> will kill the scan with a 'finished' state to indicate
              the scan stopped normally

I think you are onto something. Let me spell it out in tedious detail to
make sure we are on the same page.

The RunEngine catches a Ctrl+C signal.
The RunEngine starts listening for a second Ctrl+C signal.
The RunEngine requests a pause.
If a pause is not possible, the RunEngine aborts, becomes idle, and
returns the REPL. A message is printed, the same as it is now, and we are
done.
If a pause is possible, the RunEngine enters a paused state and
withholds the REPL for half a second, enough time for a second Ctrl+C to
register. If a Ctrl+C is caught, the RunEngine aborts, as in (4).
Otherwise, the RunEngine prints a message like the one you suggested
above.

I like the half-second pause because it removes any doubt about whether the
RunEngine is blocking Ctrl+C or not: if the user has the REPL, the user
owns Ctrl+C. If not, the RunEngine owns it.
Dan
On Wed, Aug 5, 2015 at 3:26 PM Eric Dill<EMAIL_ADDRESS>wrote:

My real concern with the first option above is that the user will be
returned to the REPL with no clear indication of what to do next. That
concern is the entire motivation with the (perhaps unecessarily)
complicated input prompt I proposed.
How about this. I am fully on-board with @tacaswell
https://github.com/tacaswell 's option above (which might actually be
@danielballan https://github.com/danielballan 's suggestions, I'm not
sure how the credit falls out here!), but print out a few lines that is
(roughly) like this and then return the user to the REPL with the run
engine in a paused state. Unless two ctrl+c's are intercepted which
should (abort or stop?) the scan.
Your RunEngine is now in a paused state. These are your options for changing
the state of the RunEngine:
resume()  --> will resume the scan
abort()  --> will kill the scan with an 'aborted' state to indicate
the scan was interrupted
stop()  --> will kill the scan with a 'finished' state to indicate
the scan stopped normally
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/bluesky/issues/152#issuecomment-128119497.

Other than your step two being out of order (step two is really part of step five), yes we are in agreement. Thanks for spelling this out explicitly!

You might be right.
My thought was this: Assuming that aborting takes some time though, and
assuming that the user might mash Ctrl+C twice out of habit, it might
correct to catch and ignore a second Ctrl+C, if it occurs before we are
ready to return the REPL.
I'm not sure that makes sense, though. We'll see how the implementation
shakes out.
Note that, no matter what, if the user hits Ctrl+C *three *times, we won't
be getting in the way at that point. So it's still possible to kill
stubborn scans by mashing Ctrl+C frantically -- an important feature!
On Wed, Aug 5, 2015 at 5:11 PM Eric Dill<EMAIL_ADDRESS>wrote:

Other than your step two being out of order (step two is really part of
step five), yes we are in agreement. Thanks for spelling this out
explicitly!
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/bluesky/issues/152#issuecomment-128150439.

Closed by #154


Beta plan

measuring sucsess
what we have learned from alpha that justifies beta
funding for beta
team for beta
high level plan for beta/what we want to learn


WindowsDriver - Alternative for DesiredCapabilities

Now that DesiredCapabilities are deprecated, what is the best alternative to use with a WindowsDriver?
I appreciate that although using DesiredCapabilities will still work, but I would prefer to future proof my tests.
I'm coding in C# with Visual Studio.
Thanks
E.G.
DesiredCapabilities appCapabilities = new DesiredCapabilities();
appCapabilities.SetCapability("app", @"C:\Windows\System32\notepad.exe");
NotepadSession = new WindowsDriver(new Uri("http://<IP_ADDRESS>:4723"), appCapabilities);

@jamiel44 for the time being its AppiumOptions, which is available in the beta versions. Future releases may proceed with this or provide an alternative.

@akinsolb  - Should this still be open?
AppiumOptions has been released and just works
Example 1:
AppiumOptions options = new AppiumOptions();

options.AddAdditionalCapability("app", @"C:\Windows\System32\notepad.exe");
return new WindowsDriver<IWebElement>(new Uri("http://<IP_ADDRESS>:4723"), options);

Example 2:
AppiumOptions options = new AppiumOptions();

options.AddAdditionalCapability("app", "Microsoft.WindowsCalculator_8wekyb3d8bbwe!App");
return new WindowsDriver<IWebElement>(new Uri("http://<IP_ADDRESS>:4723"), options);

@TroyWalshProf No, There should be another task to develop AppiumOptions further, but this should be closed.


Browser exec doesn't work

Installed chrome extension, logged in to tiktok, checked that the lives are visible on browser but still it doesn't work.
Tried multiple lives.
ttlr.py -mode auto -ffmpeg -combine -user ************ -browser_exec "C:\Program Files\Google\Chrome\Application\chrome.exe"
2024-02-02 03:45:23,263 - INFO - Tiktok Live Recorder v4.2
2024-02-02 03:45:24,299 - INFO - Username: ***********
2024-02-02 03:45:24,300 - INFO - Room ID: ************
2024-02-02 03:45:25,337 - INFO - *********** is live
2024-02-02 03:45:25,337 - INFO - Getting live url for room ID ****************
2024-02-02 03:45:25,903 - ERROR - Exception caught in main:
2024-02-02 03:45:25,904 - ERROR - Account is age restricted
Traceback (most recent call last):
File "C:\tiktok-live-recorder-4.2\ttlr.py", line 97, in main
bot.run()
File "C:\tiktok-live-recorder-4.2\tiktok_bot.py", line 69, in run
live_url = self.get_live_url()
^^^^^^^^^^^^^^^^^^^
File "C:\tiktok-live-recorder-4.2\tiktok_bot.py", line 261, in get_live_url
except errors.AgeRestricted as e: raise e
^^^^^^^
File "C:\tiktok-live-recorder-4.2\tiktok_bot.py", line 249, in get_live_url
if bot_utils.login_required(json):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\tiktok-live-recorder-4.2\bot_utils.py", line 71, in login_required
raise errors.AgeRestricted('Account is age restricted')
errors.AgeRestricted: Account is age restricted

Any update for this, not sure if I'm using the browser exec correctly or if it doesn't work on windows.

Installed chrome extension, logged in to tiktok, checked that the lives are visible on browser but still it doesn't work. Tried multiple lives.
ttlr.py -mode auto -ffmpeg -combine -user ************ -browser_exec "C:\Program Files\Google\Chrome\Application\chrome.exe" 2024-02-02 03:45:23,263 - INFO - Tiktok Live Recorder v4.2 2024-02-02 03:45:24,299 - INFO - Username: *********** 2024-02-02 03:45:24,300 - INFO - Room ID: ************ 2024-02-02 03:45:25,337 - INFO - *********** is live 2024-02-02 03:45:25,337 - INFO - Getting live url for room ID **************** 2024-02-02 03:45:25,903 - ERROR - Exception caught in main: 2024-02-02 03:45:25,904 - ERROR - Account is age restricted
Traceback (most recent call last): File "C:\tiktok-live-recorder-4.2\ttlr.py", line 97, in main bot.run() File "C:\tiktok-live-recorder-4.2\tiktok_bot.py", line 69, in run live_url = self.get_live_url() ^^^^^^^^^^^^^^^^^^^ File "C:\tiktok-live-recorder-4.2\tiktok_bot.py", line 261, in get_live_url except errors.AgeRestricted as e: raise e ^^^^^^^ File "C:\tiktok-live-recorder-4.2\tiktok_bot.py", line 249, in get_live_url if bot_utils.login_required(json): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\tiktok-live-recorder-4.2\bot_utils.py", line 71, in login_required raise errors.AgeRestricted('Account is age restricted') errors.AgeRestricted: Account is age restricted

i think that a private live is different to a age restricted live, a private live needs a permission of the host to acess and the age restricted live needs a account logged to see, to solve this error i think that we need to implement a new function to read cookies, if i was wrong please correct me (not sure if the extension take the cookies)


utm: 4.0.8 -> 4.1.5

Description of changes

Update UTM to the latest version 4.1.5.
Changelog: https://github.com/utmapp/UTM/releases/tag/v4.1.5
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.


How can I use toFile pseudo-synchronusly?

I'm trying to resize a few images and then create .ico files from them. I'm using sharp to resize my files and save them as a different file temporarily. I need to keep executing after the file is actualy present in the fs to be able to convert them, but using async doesn't seem to do much.
Is there any way to only keep execution once the file is done writing like with fs.write
here's mock code of what I'm doing:
//all paths are global (wiht drive letter), not relative (not starting with ".")
async function execution(globalLocation) {
	let allDir = getAllDirs(globalLocation);
	for (dir of allDir) {
		let pngFile = getPNGfile(dir); //returns path of file string
		let image = await sharp(pngFile)
			.resize(256, 256, {
				kernel: sharp.kernel.nearest,
				fit: 'contain',
				background: { r: 255, g: 255, b: 255, alpha: 0.0 },
			})
			.toFile(`${dir}\\tmp.png`, (err) => {
				if (err) {
					throw err;
				}
			});
		console.log(JSON.stringify(getAllFiles(dir))); //file is not in file system yet
		convertToICO(`${dir}\\tmp.png`)// throw error file doesn't exists
	}
}

Hi, did you see https://sharp.pixelplumbing.com/api-output#tofile ?

A Promise is returned when callback is not provided.

Conversely, a Promise is not returned when a callback is provided.

Perhaps the docs, in this case written in a era when the use of callbacks were more common than Promises, be clearer in this regard? Happy for a PR to update the JSDocs in the code, if you're able.


After full screen out Video not showing only audio show - Flutter Web

Unable to see video after minimize

duplicate of https://github.com/zezo357/flutter_meedu_videoplayer/issues/51


docs(aurora): DOC-472 aurora stage instructions

Resolves Jira: DOC-472

Stephen provided feedback in Slack.


Unexpected behavior of animatedList

Hi, it seems to me that I have encountered incorrect behavior of the animated list.
Watch the video, this is the official example from the link https://api.flutter.dev/flutter/widgets/AnimatedList-class.html
https://user-images.githubusercontent.com/44409006/122125414-1f636f00-ce39-11eb-847e-0a9601a344d5.mov
The bottom line is the following, when the animation of the object is deleted, its display is incorrect, the color and serial number are not correct

I see the same behavior using the linked code sample. Labeling accordingly.

@gspencergoog - another example of why samples need tests


[Feature request] Support for alpha when using JPEG compression

Is your feature request related to a problem? Please describe.
The current compression options that support alpha channel also requires very high bandwidth.
Describe the solution you'd like
An additional compression option that sends two JPEG streams in parallel; one for RGB, and a monochrome stream for the alpha.
The sender would need to make two separate encodes from the same source image and the receiver would make two separate decodes and combine the result back into a final RGBA image.
Additional context
The suggestion was originally made for the Teleport project at https://github.com/fzwoch/obs-teleport/issues/100.
I'm not familiar with the libjpeg-turbo library, but with some luck both the dual encoding and decoding can be accomplished by reading from/writing to the same raw image buffer and adjusting the strides for the passes, rather than doing additional copy operation.

The OBS part of this could be tricky, a source can be YUV or RGBA, but one over the other can have bigger performance implications in OBS than one would expect, to the point where a smooth YUV feed can be turned into being unusable when converted to RGBA on the receiving end - I have learned that during past tests with various format conversions.
DistroAV aka OBS-NDI seems to utilize a standard filter integrated into OBS instead, probably for that very reason, so I guess I will rather look into implementing a similar solution if possible (it might not be, since they use a a sync source, while Beam uses an async source, which also changes things about the color formats, will have to see).


[feature request] create a note and link  it inline in the  current note

As in the title of the issue, it would be really convenient to create a note and  link  it inline in the  current note.
(or maybe such option existst but I didnt learnt about it)

i agree that it’d be convenient. it’s currently not possible, but i can add it as a slash command in the next release

@danieltomasz just wanted to follow up - if the above isn't what you meant, can you provide an example/workflow of what this feature would look like?

I am making note in one paper, then some reference ideas came out, this is a fragment  of my notes
- [[Aperiodic offset]] is correlate with neuronal population spiking and blood-oxygen-level-dependent signal from function MRI
	- [[Berezutskaya et al. (2022) Open multimodal iEEG-fMRI dataset from naturalistic stimulation with a short audiovisual film]] could be used to check the relationship between the [[Aperiodic offset]] and [[fMRI signal]]
	- #reference to [[Winawer et al. 2013 Asynchronous Broadband Signals Are the Principal Source of the BOLD Response in Human Visual Cortex]]  and [[Hermes et al. 2017 Neuronal synchrony and the relation between the blood-oxygen-level dependent response and the local field potential]] #followup

Indeed this is possible using slash command; sorry I didnt reacted to your comment
It could be augmented with creating hotkey for inline adding Zotero item (currently the window open only  after 5 keystrokes /log + enter
Maybe this is not necessary because of slash workaround and you have other priorities but having a separate command with hotkey is quite common, for example many obsidian plugins have it, and the new Citations in Logseq have separate command too


(chore) Fixing Windows Build

Changed package name in package.json to contain valid characters only.
Calling the right make dist target

Results are here: https://ci.appveyor.com/project/Opentrons/opentrons

Follow-up ticket: https://trello.com/c/GBvv5Wrh/108-windows-build-chores


Get rid of most @rpath nonsense on Darwin

This requires some small changes in the stdenv, then working around the weird choice LLVM made to hardcode @rpath in its install name, and then lets us remove a ton of annoying workaround hacks in many of our Go packages. With any luck this will mean less hackery going forward.
Motivation for this change
I got sick of seeing people getting weird rpath-related errors when packaging Go programs.
Fixes #18131
@acowley this should fix the Go issue you encountered earlier today
Things left to do

[x] Test some other stuff that depends on LLVM (e.g., rustc) to make sure it still runs now that I took out the rpath install name in libLLVM. I expect it to but it might have an extraneous rpath load command or two in it.
 I forgot to work off staging and was too lazy to switch over and wait another couple of hours for everything to build again
[ ] Make sure I didn't break anything on Linux (but I'm pretty sure I didn't)

Things done

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

[ ] NixOS
[x] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Do you know why the problem of rpaths causing cyclic references between Go outputs does not exist on Linux?

Because of the patchelf --shrink-rpath stdenv does.

Yeah, we could have replicated that, but given that the rpaths are almost entirely unnecessary on macOS, I'd rather just scrap them altogether than replicate the more complicated solution on a platform that doesn't need it.

How does dynamic library linkage work on darwin in general? (Just asking, I'm curious.) Do the binaries contain absolute paths to the .dylib files? If so, why does the concept of RPATH exist in the file format in the first place?

Do the binaries contain absolute paths to the .dylib files?

Yes, and the libraries contain absolute paths to themselves, so that when programs (and other libraries) are linked to a library, they refer to it by its builtin absolute path.
Linux ld loader also supports loading libraries by an absolute path (this is documented in ld.so(8)), but AFAIK ld linker can't write them.

What @orivej said, but to answer your "why" question, it's to support relocateable libraries. We often distribute .app "files" that are basically bundles of dependencies in a folder, and in those cases you don't want your dependencies to expect to be in any particular place.
So basically, you can add @rpath as a special element to a library's self-reported path (which ends up the thing that anyone depending on that library refers to) and then the loader will search any relevant rpath entries in the executable being loaded for that lib. There's also a couple of other special cases like @executable_path and @loader_path, which refer to the top-level binary being loaded and the specific binary making the reference, respectively.

@Ericson2314 if you want it on Linux, is there a ticket for that? I'd be curious to hear some discussion of what's involved and see what the community thinks of it

There's https://github.com/NixOS/nixpkgs/issues/24844

Thanks!

I'm going to pick this into release (via staging-17.09) to ease the porting of Go packages to release-17.09. (Otherwise some of them encounter the "cycle detected" error.)

Released in cfc55fecddcfe2eede1f14313abd65ffd93fbf57.

Cool, thanks @orivej


--build-system not always available

In rez-build's finding on what build-system plugin to use, it only defines the --build-system flag if two or more build systems are detected.  This is problematic because there is no way to force the build system if you have build infrastructure that is building codebases that may find a single build system and others find multiple.  You can't configure the build infrastructure to always pass a --build-system flag because that will fail for codebases where only a single build system is defined.  And you can't leave out that flag because then you'll get errors for multi-build system codebases.
Some options:

Always define the --build-system flag, even for single build system codebases.  Raise an error if the value of --build-system doesn't match the build system found.
Have a default build system configuration value that rez-build will use in codebases with when multiple build systems are found and a --build-system flag is not provided.
Be able to specify the default build system in the package.py file.

I'm going to include (1) and (3) in a fix shortly. I'm also going to remove the predetermined 'choices' list for --build-system... this isn't really necessary, and it causes an extra package.py evaluation. Typically this doesn't matter much, but I'm starting to think about packages with more expensive evaluations (ie early-bound functions). For eg, consider a smart installer package that retrieves info from a website.

So I've stumbled on an unfortunate problem. The cmake build system has its own --build-system option. This has never conflicted before, because the cmake args are only added to the argparser if there's one valid build system... in which case, the standard --build-system option isn't added.
There is no fix for this other than removing or changing the cmake --build-system arg, so it's a rare case where I have to break backwards compatibility. I will change it to --cmake-build-system... hopefully, if anyone is using this, they're using the --bs short form.

https://github.com/nerdvegas/rez/releases/tag/2.26.0


models.py:143-146: Document terms Product, Position and...

The puzzle 257-457f55e0 from #257 has to be resolved:
https://github.com/fidals/refarm-site/blob/b00cfe6c36ef72ffd23f5a6ac54d2d7b23e2dd44/catalog/models.py#L143-L146
The puzzle was created by duker33 on 11-Feb-19.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@0pdd the puzzle #318 is still not solved.

@0pdd the only puzzle #318 is solved here.


SSL Support

[ ] nginx config
[ ] Expose 8443 to host
[ ] Document mounting ssl_certificate, ssl_certificate_key

Though I would put a update here I have forked this project and added in the ssl support but also made some larger changes that would mean it could not be merged into this project. The main change is that my project removes the mysql from this container so it will now use a separate mysql container that is linked to the koken one.
If you are interested it is here https://github.com/robrotheram/docker-koken-lemp/tree/SSL-Support


Doesn't work with Parallels provider

I tried using this with the Parallels provider and got the following message
==> default: Running provisioner: windows_reboot...
==> default: Issuing command: shutdown -t 0 -r -f
==> default: Launching remount_synced_folders action...
Vagrant attempted to call the action 'remount_synced_folders' on the provider
'Parallels (02b826ce-ecb8-4525-b64b-d3a7ac8de565)', but this provider doesn't support this action. This
is probably a bug in either the provider or the plugin calling this
action, and should be reported.

You should use https://github.com/aidanns/vagrant-reload instead. It should work, and is a better approach than this one.


[Bug report] Invalid value used as weak map key

Bug report
Description
When I use  in docs/README.md, it gets wrong.
Steps to reproduce

Reproduction link / repo: https://github.com/gtn1024/vuepress-next-bug

Expected behavior

Screenshots

Environment info

Browser: Chrome
Output of vuepress info:

➜  vuepress-next-bug git:(main) ✗ npx vuepress info

  System:
    OS: macOS 11.4
    CPU: (8) arm64 Apple M1
    Memory: 107.02 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.17.0 - ~/.nvm/versions/node/v14.17.0/bin/node
    Yarn: 1.22.10 - /opt/homebrew/bin/yarn
    npm: 6.14.13 - ~/.nvm/versions/node/v14.17.0/bin/npm
  Utilities:
    Git: 2.30.1 - /usr/bin/git
  Browsers:
    Chrome: 91.0.4472.106
    Edge: 91.0.864.53
    Firefox: 89.0.1
    Safari: 14.1.1
  npmPackages:
    @vuepress/bundler-vite: Not Found
    @vuepress/bundler-webpack:  2.0.0-beta.18
    @vuepress/cli:  2.0.0-beta.18
    @vuepress/client:  2.0.0-beta.18
    @vuepress/core:  2.0.0-beta.18
    @vuepress/markdown:  2.0.0-beta.18
    @vuepress/plugin-active-header-links:  2.0.0-beta.18
    @vuepress/plugin-back-to-top:  2.0.0-beta.18
    @vuepress/plugin-container:  2.0.0-beta.18
    @vuepress/plugin-debug: Not Found
    @vuepress/plugin-docsearch: Not Found
    @vuepress/plugin-git:  2.0.0-beta.18
    @vuepress/plugin-google-analytics: Not Found
    @vuepress/plugin-medium-zoom:  2.0.0-beta.18
    @vuepress/plugin-nprogress:  2.0.0-beta.18
    @vuepress/plugin-palette:  2.0.0-beta.18
    @vuepress/plugin-prismjs:  2.0.0-beta.18
    @vuepress/plugin-pwa: Not Found
    @vuepress/plugin-pwa-popup: Not Found
    @vuepress/plugin-register-components: Not Found
    @vuepress/plugin-search: Not Found
    @vuepress/plugin-shiki: Not Found
    @vuepress/plugin-theme-data:  2.0.0-beta.18
    @vuepress/plugin-toc: Not Found
    @vuepress/shared:  2.0.0-beta.18
    @vuepress/theme-default:  2.0.0-beta.18
    @vuepress/theme-vue: Not Found
    @vuepress/utils:  2.0.0-beta.18
    vue:  3.1.1
    vue-loader:  16.2.0
    vue-router:  4.0.9
    vuepress: ^2.0.0-beta.18 => 2.0.0-beta.18
    vuepress-vite: Not Found

Duplicate of #201.
In short, avoid using deprecated html tags, or set compilerOptions.isCustomElement

I think it's duplicated of #186, #201
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/center

@meteorlxy I think it should be written to the VuePress Document to highlight this feature as many people may ignore it.

Sure. We'll update the docs later


unrecognised option '--Mapper.ba_global_function_tolerance=0.000001'.

Try newer version of COLMAP > 3.6

do you manage to solve this problem?

@prakashknaikade what version of COLMAP are you using.
Working with version > 3.6 solved the issue for me.


Integrate cert management for Shoot clusters

What this PR does / why we need it:
This PR integrates the components Cert-Manager and Cert-Broker which handle certificate management for Shoot clusters. While the Cert-Manager is deployed once per Seed in the Garden namespace, the Cert-Broker is part of every Shoot cluster's control plane.
This feature can be enabled by setting the CertificateManagement: true in the featureGates section of ControllerManagementConfiguration. If enabled, the following information must be provided:

Access information for domains which certificates should be issued for.
Optional: Access Information for Let's Encrypt account to be used.

Which issue(s) this PR fixes:
Fixes #449
Release note:

Gardener can now handle certificate requests for managed domains of `Ingress` resources labeled with `garden.sapcloud.io/purpose: "managed-cert"`.

Gardener can now handle `Ingress` resources which request a certificate for Gardener managed domains. This can be enabled by setting the `CertificateManagement: true` in the `featureGates` section of `ControllerManagementConfiguration`. Please make sure that the required configuration is placed in the `Garden` namespace of the `Garden` cluster.

Thanks for your review @Adracus , @rfranzke. I've addressed your comments, PTAL.

@rfranzke, I've addressed your comments, PTAL.

Please rebase once again.


[v1.x] Backport #17689 and #17884 to v1.x branch

Description
As title.
@ciyongch @pengzhao-intel @TaoLv
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Adding this PR to v1.7.0 roadmap https://github.com/apache/incubator-mxnet/issues/16864

@mxnet-bot run ci [all]

@ElaineBao I merged the code changes of mkldnn_pooling.cc in PR#18067, could you please help double check for this part?

@ElaineBao I merged the code changes of mkldnn_pooling.cc in PR#18067, could you please help double check for this part? Thanks.


Check for issues in current maven build

The first error I see is:
[ERROR]   The project de.metanome:backend:1.2-SNAPSHOT (C:\Users\vmaharajh\code\Metanome\backend\pom.xml) has 1 error
[ERROR]     'dependencies.dependency.version' for com.sap.cloud.db.jdbc:ngdbc:jar is missing. @ line 242, column 21

To get past this error, I added the following into the com.sap.cloud.db.jdbc group of /backend/pom.xml:
<version>2.4.62</version>

However that then leads to another error
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar (default) on project test_helper: MavenReportException: Error while generating Javadoc:
[ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules but the packages defined in http://docs.oracle.com/javase/8/docs/api/ are in the unnamed module.

Hey Maharajh,
thanks for bringing up this issue! The defect was behind the defined scope of the dependency in the root pom file. I just updated it to master so at least the first error should disappear. The second point is mentioned in our readme under dependencies, but I'll update it to make the needed version more clear since it can indeed be misunderstood :)
Sorry for the inconvenience!
Cheers

Thanks for fixing it! Yeah, I saw the directions in the README. Since it said "Java JDK 1.8 or later", I figured 13 would work.

When you download a java version of your choice, there's a difference between the jdk1.x and the jdkx version. So "Java JDK 1.8 or later" actually refers to versions like jdk1.9, jdk1.10 and so on. The jdkxx versions are OpenJDKS. Maybe this link will bring some insights :) https://stackoverflow.com/questions/22358071/differences-between-oracle-jdk-and-openjdk

Ah. Thanks for the explanation, that makes sense. I'm new to java, and trying to understand one of the metanome algorithms.


"Death gasp" for a moth

About the PR
added "death gasp" sound for moths
Why / Balance
https://github.com/space-wizards/space-station-14/pull/27736
Media
https://github.com/space-wizards/space-station-14/assets/164364533/11195d09-039d-49f2-8fe7-5542c16630e3
https://github.com/space-wizards/space-station-14/assets/164364533/4e312fb7-019f-4893-83e3-5ccac42b859a

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl: RenQ

add: The moths now have their own "death grasp"

Are you sure about that license? Looks like other stuff from tgstation is licensed under CC-BY-SA-3.0

Are you sure about that license? Looks like other stuff from tgstation is licensed under CC-BY-SA-3.0

I don't know. in this case, can CC-BY-SA-3.0 be used?

if you use the original from freesound it can be CC0-1.0 otherwise CC-BY-SA-3.0 with tgs modified version

thanks


readme: fix incorrect demo configuration

Resolves https://github.com/nix-community/nixvim/issues/1934 There is an incorrect example, that might have worked previously, but is no longer the case.

@mergifyio queue


fixed layout breaking on sub-pixel width of container

in case the parent container width was not an integer, the free-form
layout broke the columns into two separate rows because the width was
set too large.

fixes this issue: https://www.concrete5.org/community/forums/usage/free-style-lay-out-column-widths/

Thanks!


chore(website): update START-HERE.md

I noticed there was a new Taiko testnet status page that wasn't included in the testnet docs. I figured it would be helpful to include.

Actually my PR will already include this change, so I think we won't need this. See: https://github.com/taikoxyz/taiko-mono/pull/12947


fix #25

I replaced thumb's attribute 'style' with directive 'ng-style'
Works fine on IE 11, Google Chrome, Mozilla Firefox.

@TheLegion merged and version incremented. If you test it, let me know here.

I've test it, works good. Thank you :)

@TheLegion If is it possible for you, take a look at https://github.com/thatisuday/ng-image-gallery/issues/28 where ng-style is also needed.

Ok, I'll fix #28.
The angular dependency in bower.json has version ^1.5.7 while the angular-animate has version 1.5.7. Is it right?

@TheLegion Yes. Feel free to change it to 1.5.8 if you want


Fix Session Benchmarks

On Polkadot, the Session Benchmarks are failing because the validator we create in the benchmark isn't selected in the validator set.
This problem is caused because the Session benchmarking uses the create_validator_with_nominators function from Staking, but does not first clean up the existing list of validators from storage.
This PR simply moves the Validator cleanup logic into the create_validator_with_nominators function so anyone that uses it gets the expected outcome.
Confirmed this fix locally.

And could we get a test? :D

Docs and tests added!

bot merge


Prompt user to configure unit tests when not already configured

This was originally reported by @qubitron (I thought I added an issue for this, couldn't find it, if we do, then we'll need to close this in favor that).

Open a folder with unit tests in VS Code
Enable Unit Tests in settings.json, but do not configure it.
VS Code will not throw errors about unit tests not having been configured.

Note: This applies to Unit Test test framework in Python.

When tests are not configured, they may not be discovered (if they don't follow the default config for the selected framework). When this happens, adding a button as proposed in #1983 would allow users to easily configure them, so we can wait & discuss better about prompting users when tests are left half configured.

Closing in favour of #4318


Fix JSON doc + set doc examples as golang

Pull Request Test Coverage Report for Build 471

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

Totals

Change from base Build 469:
0.0%

Covered Lines:
5139

Relevant Lines:
5154

💛  - Coveralls


Example Code in Readme

The sample code in the Readme is not working:
Graph graph = hopper.getGraph();
LocationIndexMatch locationIndex = new LocationIndexMatch(graph, new RAMDirectory());
locationIndex.prepareIndex();
MapMatching mapMatching = new MapMatching(graph, locationIndex, encoder);

I get the following error:
The constructor LocationIndexMatch(Graph, RAMDirectory) is undefined	Routing.java	line 145	Java Problem

That is because LocationIndexMatch expects a GraphStorage and not a Graph.
But if I change the code to, like it is done in the test files:
GraphStorage graph = hopper.getGraph();
LocationIndexMatch locationIndex = new LocationIndexMatch(graph, (LocationIndexTree) hopper.getLocationIndex());
MapMatching mapMatching = new MapMatching(graph, locationIndex, encoder);

I get the following exception:
05-07 11:26:24.235: E/AndroidRuntime(18902): Caused by: java.lang.IllegalArgumentException: Call LevelGraph.getBaseGraph() instead of using the LevelGraph itself

Thanks! This is indeed wrong - I've updated it to your code.
And you seem to try to use the map matching with hopper.setCHEnabled(true) where you would need to call graph.getBaseGraph before passing to the constructors. Currently a graph with enabled CH is not 'officially' supported and therefor not recommended.

I have the same problem and it is not resolved.
When I use:
GraphStorage graph = hopper.getGraph();
        //LocationIndexMatch locationIndex = new LocationIndexMatch(graph, new LocationIndexTree(hopper.getGraph(), new RAMDirectory()));
        LocationIndexMatch locationIndex = new LocationIndexMatch(graph, new RAMDirectory());
        locationIndex.prepareIndex();
        MapMatching mapMatching = new MapMatching(graph, locationIndex, encoder);

I get compilation error:
Exception in thread "main" java.lang.Error: Unresolved compilation problem:
	The constructor LocationIndexMatch(GraphStorage, RAMDirectory) is undefined

When I tried with:
LocationIndexMatch locationIndex = new LocationIndexMatch(graph, new LocationIndexTree(hopper.getGraph(), new RAMDirectory()));

I get this error:
Exception in thread "main" java.lang.IllegalThreadStateException: already created
	at com.graphhopper.storage.RAMDataAccess.create(RAMDataAccess.java:86)
	at com.graphhopper.storage.RAMDataAccess.create(RAMDataAccess.java:33)
	at com.graphhopper.storage.index.LocationIndexTree.prepareIndex(LocationIndexTree.java:319)
....

This is my full code block copied form README.md
    private void start( String[] args )
    {
        GraphHopper hopper = new GraphHopper().
//                disableCHShortcuts().
                setEncodingManager(new EncodingManager("CAR")).
                setGraphHopperLocation("graphhopper-out-folder2/").
                setOSMFile("/Users/karim/Documents/workspace-other/mapmatching/src/main/java/com/eta/resources/india-latest.osm");
        CarFlagEncoder encoder = new CarFlagEncoder();
        hopper.setCHEnable(false);
        hopper.importOrLoad();

     // create MapMatching object, can and should be shared accross threads
        GraphStorage graph = hopper.getGraph();
        LocationIndexMatch locationIndex = new LocationIndexMatch(graph, new LocationIndexTree(hopper.getGraph(), new RAMDirectory()));
        //LocationIndexMatch locationIndex = new LocationIndexMatch(graph, new RAMDirectory());
        locationIndex.prepareIndex();
        MapMatching mapMatching = new MapMatching(graph, locationIndex, encoder);

        // do the actual matching, get the GPX entries from a file or via stream
        List<GPXEntry> inputGPXEntries = getList();
        MatchResult mr = mapMatching.doWork(inputGPXEntries);

        // return GraphHopper edges with all associated GPX entries
        List<EdgeMatch> matches = mr.getEdgeMatches();
        // now do something with the edges like storing the edgeIds or doing fetchWayGeometry etc
        for (Iterator iterator = matches.iterator(); iterator.hasNext();) {
			EdgeMatch edgeMatch = (EdgeMatch) iterator.next();
			System.out.println(edgeMatch.getEdgeState());

		}
}

The readme is updated to reflect this change. For future reference look also into the unit tests.

Thanks a lot :)


backport 2.7:Add tests for mbedtls_cipher_crypt API

Description
Backport of #1099 to mbedtls-2.7
Status
READY

This is waiting on the original PR #1099 to be rebased before being merged, so it can be merged at the same time.

The original PR this is a backport of, #1099, has conflicts and needs rebasing, therefore demoting, and removing the 'ready for merge' label.

The original PR this is a backport of, #1099, still has conflicts and needs rebasing, therefore demoting, and removing the 'ready for merge' label.


[Support] Fix create-user.sh to work with bash 4

What
This script has set -u at the top, and was therefore erroring with:
./scripts/create-user.sh: line 181: uaa_uuid: unbound variable

For some reason this wasn't causing an issue with bash 3 (as included in
OS X). I presume bash 3 is not complaining because this variable is
declared as 'local' at the top of this function.
How to review
Test creating a new user in a dev environment using both bash 3 and bash 4 (the --no-email flag is useful when testing against dev).
Bash 4 is available in homebrew, but the #! line in the script will need to be updated to point to it while testing.
Who can review
Not me.

Code reviewed only, LGTM.


Correction for raw affiliation Director of Research,CNRS/Ecole normale supérieure de<EMAIL_ADDRESS>

Correction needed for raw affiliation Director of Research,CNRS/Ecole normale supérieure de<EMAIL_ADDRESS>raw_affiliation_name: Director of Research,CNRS/Ecole normale supérieure de<EMAIL_ADDRESS>new_rors: 02feahw73;04zmssz18
previous_rors: 05a0dhs15;02feahw73
works_examples: W2106319012
contact: db91bbceaaf4cfe96cf77c7f21380593:4975e4508910e9d202f96a839b35 @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


[spark] Memory allocation error during Spark test suite execution

The test suite of xgboost-spark triggers a memory allocation error in the native library. mvn output and the error log are here: https://gist.github.com/ssimeonov/f28ec11c185d73bd238e22b8600f6e42
The exact location of the reported error is https://gist.github.com/ssimeonov/f28ec11c185d73bd238e22b8600f6e42#file-0-mvn_output-txt-L678
Environment info
Operating System: OSX Yosemite
Compiler: gcc/g++-6 with OpenMP support
If installing from source, please provide

The commit hash (git rev-parse HEAD):<PHONE_NUMBER>d54fc97f8ac4b530c611d339a5f4c3
Logs will be helpful (If logs are large, please upload as attachment): provided in gist above

Steps to reproduce

Build xgboost following https://www.ibm.com/developerworks/community/blogs/jfp/entry/Installing_XGBoost_on_Mac_OSX?lang=en with caveat that I needed make clean_all && make -j4 per https://github.com/dmlc/xgboost/issues/1839
cd jvm-packages
mvn -Dspark.version=2.1.0 package

What have you tried?

I have tried using different Spark 2.x versions; it makes not difference

I do not think it is related to jvm-packages, maybe your gcc-6? @tqchen?

➜  jvm-packages git:(master) ✗ gcc-6 --version
gcc-6 (Homebrew GCC 6.3.0_1 --without-multilib) 6.3.0

config.mk is
# choice of compiler, by default use system preference.
export CC = gcc-6
export CXX = g++-6
# export MPICXX = mpicxx

# the additional link flags you want to add
ADD_LDFLAGS =

# the additional compile flags you want to add
ADD_CFLAGS =

# Whether enable openmp support, needed for multi-threading.
USE_OPENMP = 1

# whether use HDFS support during compile
USE_HDFS = 0

# whether use AWS S3 support during compile
USE_S3 = 0

# whether use Azure blob support during compile
USE_AZURE = 0

# Rabit library version,
# - librabit.a Normal distributed version.
# - librabit_empty.a Non distributed mock version,
LIB_RABIT = librabit.a

# path to libjvm.so
LIBJVM=$(JAVA_HOME)/jre/lib/amd64/server

# whether to test with coverage measurement or not. (only used for `make cover`)
# measured with gcov and html report generated with lcov if it is installed.
# this disables optimization to ensure coverage information is correct
TEST_COVER = 0

# path to gtest library (only used when $BUILD_TEST=1)
# there should be an include path in $GTEST_PATH/include and library in $GTEST_PATH/lib
GTEST_PATH =

# List of additional plugins, checkout plugin folder.
# uncomment the following lines to include these plugins
# you can also add your own plugin like this
#
# XGB_PLUGINS += plugin/example/plugin.mk

Same issue here?
Environment info
Operating System: macOS 10.12.4
Compiler: gcc/g++-6 with OpenMP support
$ gcc --version
gcc-6 (Homebrew GCC 6.2.0_1 --without-multilib) 6.2.0
$ g++ --version
g++-6 (Homebrew GCC 6.2.0_1 --without-multilib) 6.2.0

Package used (python/R/jvm/C++): jvm
xgboost version used: https://github.com/dmlc/xgboost/commit/e62be19c70b8ca62132393c3ab5c08dc292b4258
Console output from mvn package and error log here: https://gist.github.com/mcelvg/d8ea536fe29805951e786d973c22dbf8
Exact location of the reported error:
https://gist.github.com/mcelvg/d8ea536fe29805951e786d973c22dbf8#file-0-mvn_output-txt-L1023
Steps to reproduce
git clone --recursive https://github.com/dmlc/xgboost
cd xgboost; cp make/config.mk ./config.mk
export CC=gcc-6; export CXX=g++-6
make -j4

The above compiles without obvious error. JAVA_HOME is set correctly.
$ echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home

Set dis_omp=0  at create_jni.sh#L15
cd jvm-packages
mvn package

What have you tried?

Setting dis_omp=0 or dis_omp=1 at create_jni.sh#L15 produces the same type of error.
The following:
git clone --recursive https://github.com/dmlc/xgboost
cd xgboost/jvm-packages
export CC=gcc-6; export CXX=g++-6
mvn package

results in:
- test DF use nested groupData
Tracker started, with env={DMLC_NUM_SERVER=0, DMLC_TRACKER_URI=<IP_ADDRESS>, DMLC_TRACKER_PORT=9097, DMLC_NUM_WORKER=8}
- params of estimator and produced model are coordinated correctly
java(16461,0x70000a8a3000) malloc: *** error for object 0x9000000000000000: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
java(16461,0x70000acaf000) malloc: *** error for object 0x9000000000000000: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
[thread 44291 also had an error]#

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGILL (0x4) at pc=0x00007fffab3334db, pid=16461, tid=46339
#
# JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.45-b02 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# C  [libsystem_c.dylib+0x5f4db]  __abort+0xac
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/UXXXXXXX/src/github/xgboost/jvm-packages/xgboost4j-spark/hs_err_pid16461.log
XGBoostSparkPipelinePersistence:
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

[error occurred during error reporting , id 0x4]

Successfully built a previous version of xgboost (https://github.com/dmlc/xgboost/commit/ce84af79234be37c568a59976ae5ab0549dc9bc3)
The exact following steps result in a successful build on the same system with same compiler.
git clone --recursive https://github.com/dmlc/xgboost
cd xgboost
git reset --hard ce84af79234be37c568a59976ae5ab0549dc9bc3
cd dmlc-core
git reset --hard 78b78be34ac27d30f2193f3d51848c62887669c4
cd ../rabit
git reset --hard a9a2a69dc1144180a43f7d2d1097264482be7817
cd ../
export CC=gcc-6; export CXX=g++-6
cp make/config.mk ./config.mk; make -j4
cd jvm-packages
mvn package

At the end of the xgboost4j-spark 0.7 build:
Run completed in 19 seconds, 185 milliseconds.
Total number of tests run: 21
Suites: completed 5, aborted 0
Tests: succeeded 21, failed 0, canceled 0, ignored 0, pending 0
All tests passed.

Last few lines of output:
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ xgboost4j-example ---
[INFO] Building jar: /Users/UXXXXXXX/src/github/xgboost/jvm-packages/xgboost4j-example/target/xgboost4j-example-0.7.jar
[INFO]
[INFO] --- maven-assembly-plugin:2.6:single (make-assembly) @ xgboost4j-example ---
[INFO] Building jar: /Users/UXXXXXXX/src/github/xgboost/jvm-packages/xgboost4j-example/target/xgboost4j-example-0.7-jar-with-dependencies.jar
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] xgboost-jvm ........................................ SUCCESS [  2.515 s]
[INFO] xgboost4j .......................................... SUCCESS [ 19.914 s]
[INFO] xgboost4j-spark .................................... SUCCESS [ 41.103 s]
[INFO] xgboost4j-flink .................................... SUCCESS [ 13.665 s]
[INFO] xgboost4j-example .................................. SUCCESS [ 14.816 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:32 min
[INFO] Finished at: 2017-05-12T18:39:21-05:00
[INFO] Final Memory: 435M/2341M
[INFO] ------------------------------------------------------------------------

Perhaps not the same issue. Reinstalling the compiler (at version 6.3.0) appears to have resolved it for me.
brew uninstall gcc@6
brew install gcc@6 --without-multilib
export CC=gcc-6; export CXX=g++-6
git clone --recursive https://github.com/dmlc/xgboost
cd xgboost; cp make/config.mk ./config.mk; make -j4
cd jvm-packages
mvn package

Last couple lines of output:
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] xgboost-jvm ........................................ SUCCESS [ 10.433 s]
[INFO] xgboost4j .......................................... SUCCESS [ 35.953 s]
[INFO] xgboost4j-spark .................................... SUCCESS [01:17 min]
[INFO] xgboost4j-flink .................................... SUCCESS [ 27.391 s]
[INFO] xgboost4j-example .................................. SUCCESS [ 22.740 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:54 min
[INFO] Finished at: 2017-05-12T21:30:24-05:00
[INFO] Final Memory: 442M/1928M
[INFO] ------------------------------------------------------------------------


Drop php-cs-fixer/php-cs-fixer in favor of nikic/php-parser

Hi,
I would like to apologize for the recent experience you had to go through due to the act of sabotage and manipulation towards this project, caused by such unethical actions.
This patch combats https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/pull/7343, via the following changes:

Replace PHP CS Fixer with PHP-Parser
RemoveFinalKeyword Implementation
RemoveReadOnlyKeyword Implementation
Add @final DocBlock via --mark-final
Add @readonly DocBlock via --mark-readonly

It's important to note that these actions were deemed necessary due to the unethical nature and (in my opinion oppressive behavior) their violation of the spirit of open-source.
I've enabled Allow edits by maintainers; feel free to review the changes, provide any feedback, or make changes directly.
Thank you for your attention.

I think you forgot something to add to the composer.json 😉
"conflict": {
    "friendsofphp/php-cs-fixer": "*"
},

You go low, I go lower.

Also, readme contains a reference to PHP CS Fixer

Thanks @ghostwriter, I really appreciate that you brought this PR up to me, but also re-wrote the implementation with a fix! Not a small feat ❤
Luckily though, there was a PR that reverted the original change, so this ultimately won't be necessary:
https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/pull/7348
Thanks again for the time you've spent on this. If the original change to PHP CS Fixer would have stayed, or is reversed again, I will merge this PR 👍

@stevebauman personally I encourage you to merge this PR anyway. It drops Fixer as a dependency which in effect:

solves the issue with it being used "against our will": we don't like the purpose of this package and would prefer to not involve Fixer in it, but we can only rely on your good will (or conflict 😆)
produces smaller executable file, since Fixer has its own dependencies, while nikic/php-parser requires only few PHP extensions

I believe it's a great solution for both sides - you have smaller releases, almost independent code, while we don't grind our teeth 😉.
Of course it needs review and some tweaks, because nikic/php-parser should go to require-dev while require section should contain all extensions required by that lib (to work properly after PHAR is built).

solves the issue with it being used "against our will": we don't like the purpose of this package and would prefer to not involve Fixer in it

Yes you've made your vendetta clear against this package.

but we can only rely on your good will (or conflict 😆)

Only because your PR was reverted.

I believe it's a great solution for both sides - you have smaller releases, almost independent code, while we don't grind our teeth

No. This is what you want, not me. I will not rewrite my project because you personally disagree with it ideologically.
You have to understand that there are those who will disagree with you and use PHP CS Fixer in ways you don't intend, or want them to. To attempt to police that is truly bizarre and unhealthy, to say the least. Let it go.

I provided valid arguments in favour of this PR (not only ideological), but you decided to focus your answer on nonsense made out of thin air - OK, your choice. Goodnight!


Fix formatting issues in DG

Codecov Report

Merging #127 (f5e71be) into master (8f312cb) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #127   +/-   ##
=========================================
  Coverage     76.37%   76.37%
  Complexity      655      655
=========================================
  Files            92       92
  Lines          1989     1989
  Branches        238      238
=========================================
  Hits           1519     1519
  Misses          392      392
  Partials         78       78

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


Shape Mismatch Error When Loading EfficientNetB4 Weights

I've downloaded the weights for EfficientNetB4, but I'm encountering a shape mismatch in some layers. Here’s the error message I received:
RuntimeError: Error(s) in loading state_dict for EfficientNetEncoder:
        size mismatch for _conv_stem.weight: copying a param with shape torch.Size([48, 3, 3, 3]) from checkpoint, the shape in current model is torch.Size([48, 1, 3, 3]).

I have in_channels=1. Are there any available weights compatible with this configuration?

No, there are no weight configurations for that.
You have two options:

Convert the input image to RGB. I always do that with my SEM and grayscale microscopy images and it works just fine.
Change the dimensions of the pretrained weights. I've never done this myself, but you could either drop two of the channels or average the channel weights. I'm not sure what is best.

Overall my recommendation is to go with option 1. Let me know if there is some reason why you don't want to convert to RGB.


need info on authorization

The web-client for functions clearly shows the access token in the URL. How do I configure this with a CI/Github deployed function? is it host.json? Please document this somewhere. I downloaded the publish settings file but unsure what I need to add to my repository.

We have detailed documentation on this here: https://azure.microsoft.com/en-us/documentation/articles/functions-create-a-web-hook-or-api-function/

The location and format of the secrets files used for WebHook/Http functions is documented in the "Api keys" section here: https://azure.microsoft.com/en-us/documentation/articles/functions-bindings-http-webhook/. Is this what you're looking for?

thanks. nowhere there does it say you have to CMD into in d:/home/data/Functions/Secret and do a more on the hosts json file... why make that so arcane (and slow with the web CMD), why not display it in a convenient location on a wedge? And, so is the function key then always the ?code= parameter for the function?

What is a "wedge"?
Anyhow, you're really not supposed to have to mess with these files. Our Portal UI is supposed to manage setting them up properly, etc. as functions are created. That's why the doc is rough for this. Also, these file formats will likely undergo changes before we GA the service.
To set up a function "Foo", you create a Foo.json file containing the "key" secret. That will then be the required ?code= parameter value.

*blade=wedge. The docs are great for the blade managed functions, but does not cover the CI versions adequately.  I do not know how to connect to my Github hosted function.  Where do i get the code param for my function URL? It's right there in the web version, no idea where to get this for the Git version. https://MY_APP.azurewebsites.net/api/HttpTriggerNodeJS1?code=XXXX

i"If the secrets folder contains a JSON file with the same name as a function" - it doesn't.

I don't understand your last comment. Regarding secrets file layout, you can take a look at this example: here is a functions folder with some sample functions, and here is the corresponding secrets folder.
Anyhow, yes as you might expect, we've focused most of our limited doc resources on the primary Portal scenarios, so we're lacking in CI doc. I'll share that feedback with our doc team.

It's just not clear. Am I retrieving these values from the filesystem with CMD prompt, adding a host.json to my function directory in www/ or are these values all self-defined? Like, should I be spelunking around in CMD for these values? Do I then have to make a new file in the www/ folder to specify the key again?
To quote:
If the secrets folder contains a JSON file with the same name as a function, the key property in that file can also be used to trigger the function, and this key will only work with the function it refers to. For example, the API key for a function named HttpTrigger is specified in HttpTrigger.json in the secrets folder. Here is an example:
{
  "key":"0t04nmo37hmoir2rwk16skyb9xsug32pdo75oce9r4kg9zfrn93wn4cx0sxo4af0kdcz69a4i"
}

I don't see this in the secrets folder via CMD...

You can configure a function to require the master key by setting the authLevel property to "admin".

How do you do this? Easy for web made function (it's a tab). How to does one specify authLevel for a CI function? Is this what's required to even generate the FunctionName.json --> key file code?

My problem with the templates may be totally off-base: I don't see my function as a read-only function in the list on the left of the home Functions App screen.... something's wrong/not configured correctly with my template?

This is a usability issue on secrets management, which is going to be tracked here: https://github.com/projectkudu/AzureFunctionsPortal/issues/360
Closing this issue since the linked issue will help address this.


[Settings][AdvPaste]Check clibboard history gpo

Summary of the Pull Request
Don't allow enabling/disabling the Clipboard History in Settings if the user has it disabled by GPO.

PR Checklist

[x] Closes: #32945
[x] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Validation Steps Performed
Tested the behavior with the GPO enabled/disabled/not configured.
Message only shows on disabled, as expected.

Updated to below the setting:

/azp run


python: mypy: filter Success message

Using the following minimal vimrc:
let $DOTVIM = expand('$HOME/.config/nvim')

set runtimepath+=$DOTVIM/bundle/repos/github.com/petobens/neomake
filetype plugin indent on

let g:neomake_open_list = 2
let g:neomake_python_enabled_makers = ['flake8', 'mypy']

and running :Neomake on a foo.py file like:
x=1

I get:
|| Success: no issues found in 1 source file
foo.py|1 col 2 warning| E225 missing whitespace around operator

This pr suppresses the first line.

Thanks, makes sense.
We could also suppress the summary line on failures maybe - but that might be good (informational) in general.  What do you think?

Good point. Don't have a strong opinion on it though (they might be informative but also distracting).

Actually I believe it makes sense to also suppress them and added the change to do so

Thanks!
Will test this later, and likely also add a test probably.

Thank you!


[5.5] Propagate method async-ness during test discovery

Nominating the changes from https://github.com/apple/swift-tools-support-core/pull/258 to be pulled back for a 5.5.x dot release

Note that these changes will not be effective without several additional supporting changes in other repos also being pulled back to release/5.5, including:
https://github.com/apple/swift/pull/39870
https://github.com/apple/llvm-project/pull/3452

@swift-ci please test

This change is safe to land decoupled from the various other PRs involved in the effort, so I'm proceeding to merge.


minor remarks on occurrenceID

@albenson-usgs I'm assigning this to you. This PR proposes the addition of the following sentence to the comment of the occurrenceID

It is preferred to use the fields that are least likely to change in the future for this.

I think it's a fine addition, FWIW.

Thanks Mathew! The reason I suggested this is we had data provider who had their dataset reviewed (by a certain journal) which requested them to change the scientificName to accepted name. This led to unintentional change of the identifiers as aphiaID was used to construct occurrenceID that way.
We want to make sure that the occurrenceID is as stable as possible because we want people to be able to trace it. They may unintentionally change it if they use the fields that are likely to change. I guess that's one of the downside of composite identifiers. I hope this makes sense! Btw, thank you very much for preparing the training materials!


Add inverted toggle to Camera Offset Borders.

Adds an inverted toggle to camera offset borders which makes it so, when checked, the border disables itself when the associated flag is active, rather than enable itself when the associated flag is active.

Will release that shortly, thanks :+1:


[resolves #1437] Add support for component google-calendar

@ppalaga If you can resolve the conflicts, we can get this merged ASAP.
All of the Google API credentials are already configured on Jenkins, right?

000d240 resolves the conflicts.

All of the Google API credentials are already configured on Jenkins, right?

Yes.

dea5c32 resolves the conflicts again

ok to test


[fix] update omniauth gems to fix oauth login failure with facebook

Coverage decreased (-0.01%) to 83.47% when pulling de57fdbc96fbb1df4383fa873f18f8bf9a79ec2b on sunny4381:fixes/facebook-oauth-login into 00db95d3f5fe722997958c3bff119875d4fce986 on shirasagi:master.


[Bug]: DragonflyDB Loses Public Port Configuration After Restart

Error Message and Logs
Issue: When restarting a DragonflyDB instance in Coolify, the public port setting is not retained. The instance loses its public port configuration, unlike PostgreSQL, which correctly restores the public port after a restart.
Logs: No specific error logs, but the issue can be observed when checking the network settings of the DragonflyDB container after a restart. Port mappings are missing or not marked as public.
Steps to Reproduce

Deploy a DragonflyDB instance in Coolify and make the port public.
Confirm that the port is accessible publicly (e.g., using curl or a browser).
Restart the DragonflyDB instance from the Coolify dashboard or CLI.
Check the network configuration of the DragonflyDB instance after the restart.
Observe that the public port setting is not retained, and the instance is no longer accessible publicly.

Example Repository URL
Not applicable. This issue can be reproduced using a default DragonflyDB instance setup in Coolify.
Coolify Version
v4.0.0-beta.367
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Ubuntu 24.04
Additional Information
The issue does not occur with PostgreSQL instances, where the public port is restored correctly after a restart. The bug seems specific to DragonflyDB. Attempts to resolve it by adding a save() call in the StartDragonfly.php script did not fix the problem. This suggests that the is_public and public_port attributes may not be set or persisted correctly before the StartDatabaseProxy call.

Bump, same happens to me on "v4.0.0-beta.373" with mongodb. It's working in another coolify server currently at version "v4.0.0-beta.360", although the mongodb there was created on an older coolify version.


Allow selecting the schemas when bootstrapping the mapping

At the moment, the bootstrappers autogenerates a mapping for all the tables in all the non-system schemas. For a large database (e.g. Snowflake), this is problematic, as one would like to focus on a few schemas.

[ ] Add a parameter to the boostrapper CLI to select a few schemas

In the case of Snowflake, a role can assigned to the JDBC connection to limit the scope. If no role is assigned, Snowflake uses the default role. That's the standard mechanism in SF to limit the scope.

Just relying on the SF role is not enough, as the current ones may be too wide and creating new ones cannot be motivated for just bootstrapping purposes.
Using the active database/schema could become an alternative option, but this is likely to require extending the DB metadata providers of all the dialects, so I recommend implementing it after the first approach.


Please add a license file and a screen shot

I'd like to add this to awesome-zsh-plugins, but I prefer to add themes with screen shots in the readme so that users can see what they look like without having to install them.
Also, please add a license file, some people won't use any code that doesn't have an open source license. If you don't have one in mind, https://choosealicense.com is a good resource to help you select an appropriate one.
Thanks!

Hello @unixorn .
Sorry for the delay in contacting you.
I am very happy to add my theme to awesome-zsh-pulgins
We have added the MIT license and placed the image in the README, please check it.
Thanks.


Chart "CPU Usage" fails with misleading message because mpstat is not installed

On CentOS 7.
Also fails if locale is not English, because the chart expects "Average" to be written in the output.

Perhaps we can add LC_ALL=C before the command.


net: sockets: add shutdown() support in vtable and implement it for native and tls sockets

So far shutdown() implementation was a noop and just resulted in warning
logs. Add shutdown() method into socket vtable. Call it if provided and
fallback into returning -ENOTSUP if not.
Add basic shutdown() implementation for net_context sockets, which
handles only SHUT_RD as 'how' parameter and returns -ENOTSUP for SHUT_WR
and SHUT_RDWR. The main use case to cover is to allow race-free wakeup
of threads calling recv() on the same socket.
Add basic shutdown() implementation of TLS sockets, which basically
calls shutdown() on underlying wrapped sockets.
Fix internal http_client timeout implementation by using shutdown(..., SHUT_RD)
instead of close().
Fixes: #37730

@mniestroj buildkite complaining that SHUT_RD, etc aren't declared

@mniestroj: I'm all for implementing missing socket features, and thanks for going for that. But it's also fair to say that you implement a peculiar, adhoc feature, and that particular feature kept me perplexed for a while when reviewing this patch. The matter, I'm not familiar with usage of shutdown(SHUT_RD), in my list "the only useful" (from us/remote-peer communication perspective) was shutdown(SHUT_WR), which allows to signal to peer EOF, while still keeping receive data from it.
So, that would be first comment. Something like:

The main use case to cover is to allow race-free wakeup of threads calling recv() on the same socket.

doesn't provide enough information about the usecase. Please consider elaborating the description. It could be something along the lines of (please extend further):

The main usecase is to allow side-effect free wakeup of threads blocked in recv(), by calling shutdown(SHUT_RD) in another thread (e.g. a callback). Previously, close() was used for that, but that has side effect of also closing file descriptor. This led to cases when a file descriptor was closed in some circumstances, but not other, which was confusing to users. Moreover closed file descriptor could be reused in the meantime, leading to hard to debug races.

But now about the actual behavior of shutdown(SHUT_RD). I played with it on Linux (using Python) and indeed, it can be used in a way you use it. But faithfulness of your implementation is questionable. Here's a transcript:
Python 3.8.10 (default, Jun  2 2021, 10:49:15)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import socket
>>> s=socket.socket()
>>> s.connect(("localhost", 8082))
>>> s.recv(1)
^CTraceback (most recent call last):
  File "<stdin>", line 1, in <module>
KeyboardInterrupt
>>> socket.SHUT_RD
0
>>> s.shutdown(0)
>>> s.recv(1)
b''
>>> s.send(b"GET / HTTP/1.0\r\n\r\n")
18
>>> s.recv(1)
b'H'
>>> s.recv(1)
b'T'
>>> s.recv(1)
b'T'
>>> s.recv(1)
b'P'
>>> s.recv(1)
b'/'
>>> s.recv(20)
b'1.0 200 NA\r\nContent-'
>>> s.shutdown(0)
>>> s.recv(20)
b'Type: text/html\r\n\r\n<'
>>> s.shutdown(0)
>>>

As you can see, it "shuts down for read" only so much. After you called s.shutdown(SHUT_RD), you can still call send(), and the socket will be automagically un-shutdown for read. More important, the above shows that read shutdown doesn't affect any pending data on socket, it should be still readable. While in your implementation, as far as I can tell, you just flush it.
And then final point: We now have much better way to handle socket timeouts - by using setsockopt(SOCK_RCVTIMEO), instead of fiddling with all those multi-threading races of accessing a single I/O object (which should be avoided in the first place).
So, that's what we have: this doesn't really implement shutdown(), just one option of it, and of that option, a very partial, peculiar behavior piece. Bottom line: great work! ;-) Tests are there, etc. But as suggested above, please elaborate the description of this very peculiar behavior and usecase behind it. Thanks.

It looks like at least some of the failing tests are due to a simple compilation error, so ensure that the correct header is included for SHUT_RD.
/workdir/zephyr/subsys/net/lib/sockets/sockets.c:410:13: error: 'SHUT_RD' undeclared (first use in this function)

@mniestroj ping

Another ping @mniestroj


chore(docs): use Docker Toolbox, not boot2docker

Issue #4266 notes how boot2docker is now deprecated. This commit
changes documentation and Makefile notices to recommend using
Docker Toolbox and Docker Machine instead.

Code LGTM.

Followed the new instructions, but make push for any component produces something like the following now:
[kent@mbp logger]$ make push
docker tag -f deis/logger:git-f50c730 <IP_ADDRESS>:5000/deis/logger:git-f50c730
docker push <IP_ADDRESS>:5000/deis/logger:git-f50c730
The push refers to a repository [<IP_ADDRESS>:5000/deis/logger] (len: 1)
unable to ping registry endpoint https://<IP_ADDRESS>:5000/v0/
v2 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v2/: EOF
 v1 ping attempt failed with error: Get https://<IP_ADDRESS>:5000/v1/_ping: EOF
make: *** [push] Error 1

I'm not sure how or why, but it seems https is being used despite this being an insecure registry.

LGTM now.

Kicked off another run: https://ci.deis.io/job/test-ec2/2841/


Upgrade our issue templates to use GitHub issue forms ✍

Introduction
GitHub has recently rolled out a public beta for their issue forms feature. This would allow you to create interactive issue templates and validate them 🤯.
Appwrite currently uses the older issue template format. Your task is to create GitHub issue forms for this repository. Please use Appwrite's issue templates as a reference for this PR.
Tasks summary:

[ ] Fork & clone this repository
[ ] Prepare bug report issue form in .github/ISSUE_TEMPLATE/bug.yaml
[ ] Prepare documentation issue form in .github/ISSUE_TEMPLATE/documentation.yaml
[ ] Prepare feature request issue form in .github/ISSUE_TEMPLATE/feature.yaml
[ ] Push changes to master and test issue forms on your fork
[ ] Submit pull request

If you need any help, reach out to us on our Discord server.
Are you ready to work on this issue? 🤔 Let us know, and we will assign it to you 😊
Happy Appwriting!

Hello, I would like to work on this issue. Please assign me the same.

@Obnoxious-coder We will start assigning as soon as we kick off Hacktoberfest at 12 am EST 👍🏻
@aniketh-varma Please do not try to claim too many issues for yourself. We want everyone to have the chance to contribute to our projects.

Oh shoot, I only saw the first part of this request (above) and did not refresh the page to see that there were folks requesting to be assigned. I also still see it is unassigned. @Meldiron, does this cause any issue?

@Obnoxious-coder All the best :rocket:

@Christian-Oleson  We would love you to check out some of our other open issues and join us on Discord if you need help finding some.

@Christian-Oleson We would love you to check out some of our other open issues and join us on Discord if you need help finding some.

I get an error when trying to join your discord:
"Unable to accept invite"

@Christian-Oleson  it does work. I can share the link again https://appwrite.io/discord

@Christian-Oleson it does work. I can share the link again https://appwrite.io/discord

It's just me then, sadly. No worries.


Fix README typo in code for Rate Limit

The sample code in the README showed retryOnCacheLimit, when it should be retryOnRateLimit
Changes
Simple README typo fix.
Status

[✓] These changes have been tested and documented properly.
[ ] This pull request introduces some breaking changes.

Oh yes. Thanks for noticing the typo in the documentation.


Event Fee Error

The required and gte=0 tags conflict with each other at 0.0
Required ensures that a value is present and not non zero while gte=0 ensures that the value is greater than or equal to 0.

Removed required and made the fee optional.
If no fee is supplied, it will default to 0.


Refactor front end to comply with SSR under the app/ directory

Refactor the front end to follow the structure of the new app/ directory to have SSR.

LGTM


Why is Spyder using libraries from base environment instead of virtual environment

I created and activated a virtual environment with virtualenv:
virtualenv venv
source venv/bin/activate

Then I installed spyder kernels and other libraries in the virtual environment:
pip install spyder-kernels==0.*
pip install numba==0.50

Then I launched Spyder in the virtual environment:
spyder

And I changed the python interpreter in Spyder to the correct path using: > Python > Preferences > Python interpreter > Use the following Python interpreter
My Python interpreter in my virtual environment is
/Users/myname/venv/bin/python

However, when I import libraries in Spyder, rather than the libraries installed in the virtual environment, Spyder uses the libraries from the base Anaconda environment.
import numba
print(numba.__version__)
0.38.0
print(numba.__file__)
/anaconda3/lib/python3.6/site-packages/numba/__init__.py

This is causing all kinds of errors in my code.
What can I do to force Spyder to only use libraries installed in my virtual environment?

Hi @jafetgado, thanks for opening this issue. From your description, it seems that you did not restart the console kernels/Spyder to apply the interpreter switch. Also, it is not clear if you installed Spyder in the virtualenv. Please try to restart the console kernels or Spyder and see if that fixes your issue

Yes, I restarted the console several times, but it did not resolve the issue. Spyder was installed with Anaconda, but I installed the Spyder-kernels in the virtual environment.

pip install spyder-kernels==0.*

What's your Spyder version? I mention it because that version of spyder-kernels doesn't work with Spyder 4.

My spyder version is 3.2.8.

That's very old. Please update at least to 3.3.6 and try again.

I upgraded Anaconda Navigator to the most recent version, which came with Spyder 4.0.1 and Python 3.7.6. That alone solved the problem for me. Thank you.

Glad to know! That version has a lot of bugs though, so I'd recommend to update again to 4.1.3.


e2e: Specify RestartPolicy=Never in empty_dir test

This should fix #8745, at least the surface issue.  This does not fix the deeper issue (how this ever passed)

I too am surprised this ever work. I wrote this test originally so this was
an oversight on my part.
On Sun, May 24, 2015 at 12:53 AM Justin Santa Barbara <
<EMAIL_ADDRESS>wrote:

This should fix #8745
https://github.com/GoogleCloudPlatform/kubernetes/issues/8745, at least
the surface issue. This does not fix the deeper issue (how this ever passed)
You can view, comment on, or merge this pull request online at:
https://github.com/GoogleCloudPlatform/kubernetes/pull/8746
Commit Summary

e2e: Specify RestartPolicy=Never in empty_dir test

File Changes

M test/e2e/empty_dir.go
https://github.com/GoogleCloudPlatform/kubernetes/pull/8746/files#diff-0
(1)

Patch Links:

https://github.com/GoogleCloudPlatform/kubernetes/pull/8746.patch
https://github.com/GoogleCloudPlatform/kubernetes/pull/8746.diff

—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/8746.

Added the same thing on host_path test.

Is checking the pod status as mentioned in the issue important? Or should we just merge this. It LGTM.

We should merge this.
On Sun, May 24, 2015 at 5:36 PM Daniel Smith<EMAIL_ADDRESS>wrote:

Is checking the pod status as mentioned in the issue important? Or should
we just merge this. It LGTM.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/8746#issuecomment-105063805
.

Will do another review and tag.
On Sun, May 24, 2015 at 5:36 PM Paul Morie<EMAIL_ADDRESS>wrote:

We should merge this.
On Sun, May 24, 2015 at 5:36 PM Daniel Smith<EMAIL_ADDRESS>wrote:

Is checking the pod status as mentioned in the issue important? Or should
we just merge this. It LGTM.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/8746#issuecomment-105063805
.

Are we OK to merge?   I think this makes e2e tests a little faster, if you need a carrot :-)

My bad @justinsb.


ignore DMA map/unmap if device isn't using DMA controller

I've also tentatively introduced the cmocka unit test framework. I'd like to start doing better unit testing, ideally we should check that internal functions were (or weren't) with the correct arguments. I had tried to do this a year ago but got stuck (https://gcc.gnu.org/legacy-ml/gcc-help/2019-11/msg00015.html). In that email if we call __wrap_foo in bar then it works correctly, however it doesn't work at all in libmuser.


Support JSX children for Table component

According to this example, we need to insert the content as a string which prevents us from using jsx manipulation and much more.
The following currently throw Uncaught TypeError: Cannot read properties of undefined (reading 'content'):
export const customTable = createCustomBlock({
   ...
  render: ({ data, idx, mode, context, dataSource }) => {
    return (

        <Column>

                Title

        </Column>

    )
  },
}

Possible workaround:
  render: ({ data, idx, mode, context, dataSource }) => {
    const headers = data.data.value.headers
      .split(',')
      .map((h, i) => ({h.trim()}	))

    const headersHtml = ReactDOMServer.renderToStaticMarkup(headers)

    return (

        <Column>

            {`

                ${headersHtml}

            `}

        </Column>

    )
  },

I think this is still complicated for users. You can customize your custom table as you do.

@m-Ryan sorry, but I don't fully understand what you mean, can you elaborate please? Thanks!

Write your CustomTable  ...

I'm sorry to bother you, but I'm still don't understand.
If I understand it correctly, Table must not have children. It can contain only string.

JSX is just a syntax that is eventually converted into an html string.

          {ReactDOMServer.renderToStaticMarkup{
            <>

                    {content1}

                    {content2}

            </>
      }}

Oh I see. Thanks!


ItemSnapshotList data type support

How can I use ItemSnapshotList data type of shared part of kmp in swiftUI

Hi! Could you share some more details about the shared Kotlin code you are trying to use from SwiftUI?


BUG: Edit path for not exist

Fixes: #88  Edit the path which is not exist in website now it will shown its own error page instead of random page and it also have home button to get back to home page.
https://github.com/user-attachments/assets/4899c8ca-a3b6-43dd-b162-01e913b58628
@harshit1142 Please review it and merge accordingly:)

??


disallow_indexing & the blog_public override

It would be useful to be able to disable the disallow_indexing feature in staging environments. This could easily be achieved by adding an additional environment variable. The current behaviour prevents plugins such as https://wordpress.org/plugins/restricted-site-access from functioning

We could potentially add a filter for it. But why not just delete the file? You could also add another action to override ours with higher priority.

The problem with deleting the file is we would need to remember to do it whenever we re-install bedrock.
I've worked round the issue adding the following to one of our plugins
     if ( WP_ENV === 'staging' && has_filter( 'pre_option_blog_public', '__return_zero' ) ) {
         remove_filter( 'pre_option_blog_public', '__return_zero' );
    }

well, the idea is that you keep that file in there throughout development, and then during staging. then remove when you push to production. could even make removal part of your deployment routine.

Closing this since it's non-standard and the solution that @ocasta posted is fine.


error: expression has mode proof, expected mode exec when using pervasive::map

Hi Verus developers,
Thanks for building verus and I am currently using it to verify some programs I wrote before. But I encountered some confusing errors and need some help from you.
I was running verus (./tools/rust-verify.sh rust_verify/example/myexample.rs) on the following program:
#[allow(unused_imports)]
mod pervasive;
use pervasive::map::*;

#[exec]
pub enum Myenum {
    S1,
    S2,
}

#[exec]
pub fn myfun(map: Map<i32, i32>) -> Myenum {
    if map.dom().contains(10) {
        return Myenum::S1;
    } else {
        return Myenum::S2;
    }
}

#[exec]
fn main() { }

and verus reports the error
error: expression has mode proof, expected mode exec
  --> rust_verify/example/mini.rs:14:16
   |
14 |         return Myenum::S1;
   |                ^^^^^^^^^^

error: aborting due to previous error

If I remove the usage of Map, the error will disappear. I am confused about why this error can happen as I have annotated every function and every enum with exec as shown in the code, and why it is related to the pervasive::map. I have read this doc: https://github.com/secure-foundations/verus/blob/main/source/docs/design/modes.md but still do not know what is the root cause of the error. Could you please let me know what is the best way to address this error?
Thank you

Thanks for your interest in the project!  The issue is that map is only intended for specifications.  In your example, you're using dom, which is defined via fndecl: https://github.com/secure-foundations/verus/blob/fdb8c37d1e409e5eb51fcb7ca5533c4cfa729d69/source/pervasive/map.rs#L29 which declares dom() to be [#spec]: https://github.com/secure-foundations/verus/blob/fdb8c37d1e409e5eb51fcb7ca5533c4cfa729d69/source/builtin_macros/src/fndecl.rs#L7  Similarly, the Set that dom returns has contains declared as spec.
Eventually, we should have an exec map (e.g., wrapping HashMap) which would be specified in terms of map, in a similar way to how the exec vec is defined in terms of the spec seq.  Verus is still very much a work in progress!

Hi @parno , thanks for your reply!
I tried to find some workaround and interestingly verus does not report any error if I change myfun to the following:
#[exec]
pub fn myfun(map: Map<i32, i32>) -> Myenum {
    let mut b = false;
    if map.dom().contains(10) {
        b = true;
    }
    if b {
        return Myenum::S1;
    }
    else {
        return Myenum::S2;
    }
}

Is this a valid workaround that allows us to return different values according to map, or it is actually a bug?

Good catch -- that's a bug.  This should fix it: https://github.com/secure-foundations/verus/commit/ef62f0d599064ac1eb3318a9dc6d8daa9de714c4

Should we also make it an error to use Map as an exec variable in the first place?

Ultimately, the error for something like fn myfun(map: Map<i32, i32>) will be that you can't actually allocate an exec mode Map<i32, i32> value, so you can't call myfun.  We might also try to flag map: Map<i32, i32> as an error directly, as an additional sanity check.  It may be hard to be complete with this check, though, since you can declare something like fn myfun<A>(map: A) and then instantiate A with Map<i32, i32>.  Catching the instantiation of A = Map<i32, i32>, and similar instantiations, might require more elaborate traits.  Maybe a warning would be good enough, in cases where a parameter or datatype field clearly can never be instantiated?

I didn't think about the generics, but I think error/warning in this situation will always be helpful and result in a more relevant span. I've frequently found it surprising when these errors wouldn't caught and I would end up getting an error while trying to call a function that had a parameter accidentally marked as exec.
For the generics, I think we could catch it when it's instantiated, like when we instantiate myfun::<Map<i32, i32>> we see that this is a function that takes an exec argument of proof type. (Or we could just rely on the fact that the user just won't be able to call that function without another mode error somewhere else).

I've made a discussion to track the possible warning feature, https://github.com/secure-foundations/verus/discussions/170
I'm going to close this as resolved otherwise; feel free to reopen if you have follow-up questions.


Read assembly file in memory first so it won't be locked.

Reading assembly file into memory first so file won't be locked, allowing hot reloading of .dlls.

 Nice one =).

Thank you =).


Running it in a Github Action

Hi. Pretty cool extension! I'm wondering how does it work on the context of a github action.
The following steps
      - name: Install Poetry Environment
        run: |
          curl -sSL https://install.python-poetry.org | python3 -
          poetry config repositories.statsbomb https://statsbomb-368836370510.d.codeartifact.eu-west-2.amazonaws.com/pypi/statsbomb/simple/
          poetry config http-basic.statsbomb aws $(aws codeartifact get-authorization-token  --domain statsbomb --domain-owner<PHONE_NUMBER>10 | jq -r .authorizationToken)
          poetry self add poetry-plugin-lambda-build
          poetry install

      - name: Package Lambda function
        run: |
          poetry build-lambda

return
Run poetry build-lambda
  poetry build-lambda
  shell: /usr/bin/bash -e {0}
  env:
     ***
     ***

'artifact_path'
Error: Process completed with exit code 1.

I did set up the artifact_path on pyproject.toml, and the building works fine locally:
[tool.poetry-plugin-lambda-build]
artifact_path = "package.zip"

Hi, I appreciate your feedback!
I would check the following things...
I would run a plugin with the following option to have more logs on what exactly is happening.
poetry build-lambda -vvv

My rough guess is that you somehow are running an old version of the package that had this issue you can check the version with the following.
pip list | grep poetry

The artifact_path parameter was replaced by package_artifact_path a couple of versions ago. I will add some more descriptive error handling to prevent such errors.


Can't Disarm

Hello
I can have my alarm state and arm my alarm with home assistant, but i can't disarm it.
I in france, i try with the <IP_ADDRESS> release.
Best Regards

I’m in France too and I can do both actions with the lastest version.

I try this:
1/ delete integration
2/ uninstall plugin in HACS
3/ reboot
4/ install plugin in HACS
5/ reboot
6/ configure integration
i can select my phone but... when give the code backto the app i got an error.
try this with <IP_ADDRESS> and <IP_ADDRESS>
an idea of what i m missing ?

Hello
I delete the plugins, then withe  he last update of HA,
i have auto detection of my alarm, i configure it and everything was Ok now.
SO there no more any problem for me :)
thanks for your help.


[wrt] Update suite.json for securitymanu

Impacted TCs num(approved): New 0, Update 22, Delete 0
Unit test Platform: Android Crosswalk Canary 17.45.429.0
Android test result summary: Pass 22, Fail 0, Block 0
BUG=https://crosswalk-project.org/jira/browse/XWALK-5609
BUG=https://crosswalk-project.org/jira/browse/XWALK-5610
BUG=https://crosswalk-project.org/jira/browse/XWALK-5613

LGTM


Change to build to use dotnet

At a minimum, you have to upgrade a few scripts and project.json files just like here: aspnet/Configuration@9cfd22f

Fixed in https://github.com/aspnet/Routing/commit/672d596248126a54ed32dd8b8d0d56559fbbf429


Dev Documentation of PowerToys Run

Summary of the Pull Request
What is this about?
This PR adds the dev documents related to PT Run.
PR Checklist

[x] Applies to #7157
[x] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
The following files have been added in this PR . Click on each of the links to see the rendered view of the markdown files.

Architecture
Debugging
Project Structure
Telemetry
Plugins

Overview
Calculator
Folder
Indexer
Program
Shell
Uri
Window Walker

Validation Steps Performed
How does someone test & validate?

/azp run


question about d435 measurement accuracy

| Camera Model                       | { D435 } |
| Operating System & Version |   Ubuntu 16  |
| Kernel Version (Linux Only)    |  16.04  |
| Platform                                 | NVIDIA Jetson TX2 |
Issue Description
Hi,guys.Rencently I want to calculate the camera's current yaw angle from two points on a horizontal line, but I found that the error is large at a distance and the calculated yaw angle fluctuates greatly.
So I hope to reduce the error by least squares, but I find that the fluctuations become bigger. When I output these points, I found an interesting phenomenon. The depth value of each point is incremented by 5mm.

I know the accuracy of this camera is millimeter, but I have never heard of this phenomenon. I doubt if this is related to the filtering inside the camera.
I also use the function rs2_deproject_pixel_to_point(),but the continuity in the x direction illustrates its correctness.
In addition, this phenomenon has nothing to do with the angle of the camera, that is, the depth step of each adjacent point is never near 5mm.

@Cavendish-Koo
There are two aspects to your question as I see it:

Why is the step size at 1.8m about 5mm and not 1mm?  The reason for this is that we calculate depth to resolution of 1/32 of a disparity . So we have 32 subpixels in the calculation. There is an inverse relationship between depth and disparity. For the D435 at 848x480, the subpixel steps-ize becomes ~5mm.   At 1m the fundamental resolution limit of a single point is 1.5mm, and at 20cm it is 60um.
For the D415 this is 2.6x better at 1280x720.

Why is the curve not exactly linear? This is a different phenomenon and actually something we are working on. We may have a fix for this soon, and it will be released as a FW upgrade.

Thank you for your answer. I will wait for your good news to fix this problem.
I will close this question, thank you again.


Use IntersectionObserver when available

Although we haven't yet hit any perf bottlenecks in our own usage of react-inview-monitor, going forward we should replace the window scroll listeners with the Intersection Observer API:
https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API
NOTE: It's currently not yet supported in safari, so would need to keep current logic as fallback.

Fixed by #2