Compilation error for custom reverse rule

In the code sample below, a custom reverse rule is defined for a Matrix -> Float64 function (for the sake of a minimal example, this just extracts a value from the Matrix).
Depending on how exactly this rule is used, it works or results in an unspecific compilation error (see the code comments). Three cases are shown in the code: In particular, the last case differs from the first only by a slight re-ordering of the arithmetic in g2 compared to g1.
I'm new to Enzyme, so maybe I'm simply doing something wrong here and you could provide a hint at what's going on? If not, does this hint at a bug?
This is on Julia 1.9.2 with Enzyme#main.
Thanks a lot!
MWE
using Logging
using Enzyme
using Enzyme: EnzymeRules
import .EnzymeRules: forward, reverse, augmented_primal, ConfigWidth, needs_primal, AugmentedReturn

debuglogger = ConsoleLogger(stderr, Logging.Debug)
global_logger(debuglogger)
Enzyme.API.printall!(true)

function f(C)
    C[1, 1]
end

function forward(func::Const{typeof(f)}, RT::Type{Duplicated}, C::Duplicated)
    Duplicated(C.val[1, 1], C.dval[1, 1])
end

function augmented_primal(config::ConfigWidth{1}, ::Const{typeof(f)}, RT::Type{<:Active}, C::Duplicated)
    primal = needs_primal(config) ? C.val[1, 1] : nothing
    AugmentedReturn(primal, nothing, nothing)
end

function reverse(config::ConfigWidth{1}, ::Const{typeof(f)}, dret, tape, C::Duplicated)
    C.dval[1, 1] += dret.val
    (nothing, )
end

C = rand(Float64, 10, 10)

# Works
dC = zero(C)
g1(C) = C[2, 2] + f(C)
res = autodiff(Reverse, g1, Active, Duplicated(C, dC))

# Works (difference to before: use ReverseWithPrimal, change evaluation order in g2 compared to g1)
dC = zero(C)
g2(C) = f(C) + C[2, 2]
res = autodiff(ReverseWithPrimal, g2, Active, Duplicated(C, dC))

# Compilation error (difference to before: back to Reverse)
dC = zero(C)
res = autodiff(Reverse, g2, Active, Duplicated(C, dC))

Full output
See https://gist.github.com/wisp3rwind/f27477fad8068b546a8f202d057cce16

Should now be fixed on main, please reopen if it persists.

Works now, thanks!


Add support for NumPy 2.0

Fixes https://github.com/data-apis/array-api-compat/issues/77

OK, it looks like this is working. This is ready for review. Then I can double check the cupy tests and cut a release.

Two CI failures:

It looks like  array-api-tests-numpy-dev / tests (3.8) needs skipping, since Python 3.8 is too old - that job only picks up numpy 1.24.
The other failure is a one-off failure for a __ne__ test due to hypothesis non-reproducibility (could be ignored)

I guess the nightly builds are lagged. Going to just merge this now to avoid further delay.


Use electron instead of phantomjs

This change is

I'm closing this one as we are getting rid of klassified.

you'd better archive the project instead of closing unaddressed issues, so that anyone willing to fork would have a clearer view

See https://github.com/foretagsplatsen/klassified/pull/58.


p7zip: 17.03 -> 17.04

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/szcnick/p7zip/releases.
meta.description for p7zip is: "A new p7zip fork with additional codecs and improvements (forked from https://sourceforge.net/projects/p7zip/)"
meta.homepage for p7zip is: "https://github.com/szcnick/p7zip"
meta.changelog for p7zip is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/6wz8pcfj0rymwnrjyqm3x9g3fdb02lw0-p7zip-17.04/bin/7za passed the binary check.

/nix/store/6wz8pcfj0rymwnrjyqm3x9g3fdb02lw0-p7zip-17.04/bin/7zr passed the binary check.

/nix/store/6wz8pcfj0rymwnrjyqm3x9g3fdb02lw0-p7zip-17.04/bin/7z passed the binary check.

3 of 3 passed binary check by having a zero exit code.

3 of 3 passed binary check by having the new version present in output.

found 17.04 with grep in /nix/store/6wz8pcfj0rymwnrjyqm3x9g3fdb02lw0-p7zip-17.04

found 17.04 in filename of file in /nix/store/6wz8pcfj0rymwnrjyqm3x9g3fdb02lw0-p7zip-17.04

directory tree listing: https://gist.github.com/75ac350f00db0233c1b23d9a29cdd96f

du listing: https://gist.github.com/45a5566cbeafde5e87ace3a19dc51228

Rebuild report (if merged into master) (click to expand)

173 total rebuild path(s)

72 package rebuild(s)

71 x86_64-linux rebuild(s)
46 i686-linux rebuild(s)
19 x86_64-darwin rebuild(s)
37 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
dtrx
far2l
fuse-7z-ng
hostsblock
kcc
libsForQt5.ark
libsForQt512.ark
libsForQt514.ark
libsForQt515.ark
lightburn
linuxPackages-libre.ply
linuxPackages.ply
linuxPackages_4_14.ply
linuxPackages_4_14.prl-tools
linuxPackages_4_19.ply
linuxPackages_4_4.ply
linuxPackages_4_4.prl-tools
linuxPackages_4_9.ply
linuxPackages_4_9.prl-tools
linuxPackages_5_10.ply
linuxPackages_5_11.ply
linuxPackages_5_4.ply
linuxPackages_hardened.ply
linuxPackages_hardkernel_4_14.ply
linuxPackages_hardkernel_4_14.prl-tools
linuxPackages_hardkernel_latest.ply
linuxPackages_hardkernel_latest.prl-tools
linuxPackages_latest-libre.ply
linuxPackages_latest.ply
linuxPackages_latest_hardened.ply
linuxPackages_latest_xen_dom0.ply
linuxPackages_latest_xen_dom0_hardened.ply
linuxPackages_lqx.ply
linuxPackages_testing_bcachefs.ply
linuxPackages_xen_dom0.ply
linuxPackages_xen_dom0_hardened.ply
linuxPackages_zen.ply
lutris
lutris-free
lutris-unwrapped
mas
mcomix3
multibootusb
p7zip
patool
plasma5Packages.ark
playonlinux
portmod
protontricks
python38Packages.binwalk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6wz8pcfj0rymwnrjyqm3x9g3fdb02lw0-p7zip-17.04 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A p7zip https://github.com/r-ryantm/nixpkgs/archive/2c58740b87a8da41338f1bca754c1f31e38b935e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6wz8pcfj0rymwnrjyqm3x9g3fdb02lw0-p7zip-17.04
ls -la /nix/store/6wz8pcfj0rymwnrjyqm3x9g3fdb02lw0-p7zip-17.04/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @7c6f434c for testing.

Result of nixpkgs-review pr 118532 at 2c58740b run on aarch64-linux 1

5 packages marked as broken and skipped:

libsForQt512.ark
multibootusb
spring
springLobby
unetbootin

4 packages failed to build:

sweethome3d.furniture-editor
sweethome3d.textures-editor
win-spice
zdoom

25 packages built successfully:

dtrx
far2l
fuse-7z-ng
hostsblock
kcc
libsForQt5.ark (libsForQt515.ark ,plasma5Packages.ark)
libsForQt514.ark
mcomix3
p7zip
patool (python38Packages.patool)
portmod
python38Packages.binwalk
python38Packages.binwalk-full
python39Packages.binwalk
python39Packages.binwalk-full
python39Packages.patool
r2mod_cli
rarcrack
sabnzbd
sweethome3d.application
win-qemu
win-signed-gplpv-drivers
win-virtio
woeusb
xarchiver

1 suggestion:

warning: unused-argument
Unused argument: fetchpatch.
Near pkgs/tools/archivers/p7zip/default.nix:1:28:
  |
1 | { stdenv, fetchFromGitHub, fetchpatch, lib, enableUnfree ? false }:
  |                            ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.

Result of nixpkgs-review pr 118532 run on x86_64-darwin 1

7 packages marked as broken and skipped:

dtrx
far2l
multibootusb
patool
portmod
python38Packages.patool
python39Packages.patool

12 packages built:

hostsblock
kcc
mas
mcomix3
p7zip
python38Packages.binwalk
python38Packages.binwalk-full
python39Packages.binwalk
python39Packages.binwalk-full
r2mod_cli
rarcrack
xarchiver

Result of nixpkgs-review pr 118532 run on x86_64-linux 1

1 package built:

p7zip


Text overlay in generated PDF for field "Spezifikationskennung"

Hello,
I generate a PDF from this UBL XRechnung XML file https://github.com/itplr-kosit/xrechnung-testsuite/blob/master/src/test/business-cases/standard/01.01a-INVOICE_ubl.xml
It's working fine except there is a text overlay at the end on the "Spezifikationskennung" field
See screen capture and full XML generated bellow.
This test is based on master branch code.

01.01a-INVOICE_ubl.xml.pdf
Best regards

After some research in the code base, this overlay is caused by the presence of both CustomizationID and ProfileID in the XML:
    <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>
    <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>

This section layout in PDF is 2 column but the URN used as ID are too long for that display.
I will provide a pull request to switch this section on single column layout.

thank you, merged, I hope it is non destructive :-)


fix: set api host on embedded configs

Review Type Requested (choose one):

[x] Glance - superficial check (from domain experts)
[ ] Logic - thorough check (from everybody doing review)

Summary
These changes make it so that there is a new embedded config in the services category for the api host, this is required for the services to be able to send data to the apiand it is simpler to add this to the embed instead of asking all RPs to add an env file and source it when they run the service.
Task/Issue reference
Closes: https://github.com/Lilypad-Tech/internal/issues/147
Details (optional)
I added the config in the services category, I could be swayed into adding it elsewhere (most prob a new category which I'd call somewhere in line with services so it made sense to add there). I did have to add the services flags/options to the solver which will only use 1 out of 3, I do feel this is good enough for now, unless you (the reviewer) have strong reasons why this should be on a different flag/options category.
I went with the route of Initing the logger services instead of instancing them because it felt too much to have to keep the instance around in the services using the loggers.
Reference to the discussion about this task.
How to test this code? (optional)

Spin up a network (get ahold of a GPU RP)
Spin up an api server
Spin up a cron server
Verify you get node info and connect events when you run the resource provider service
Trigger a cli job and verify you get the deal and job events
Trigger a pow round and verify you get the hashrates events

I know it's merged already but just thought I'd pick out this point:
Verify you get node info and connect events when you run the resource provider service
These events are come to the api from the solver not from the resource provider, so that doesn't actually test the RP knows the API_HOST

These events are come to the api from the solver not from the resource provider, so that doesn't actually test the RP knows the API_HOST

You are correct, let me further clarify: the way to trigger those events is by executing the resource provider and then you see those events in the solver's console


Crawl different data based on the config

We should have the config file which specify the data you want to crawl.
Some heavy operations like getting all likers, all comments can be specified in the config.

https://github.com/huaying/instagram-crawler/pull/44


flutter update-packages --force-upgrade fails to un-pin flutter sdk deps

Steps to reproduce

Create the following pubspec.yaml file in a clean directory (henceforth referred to a $DIR):
name: bug_report
dependencies:
  flutter:
    sdk: flutter
  meta: any

Update your $FLUTTER_ROOT/packages/flutter/pubspec.yaml file to specify a pinned version of meta: 1.1.6 (which is what it's currently pinned to)

Run the following commands:
$ cd $DIR
$ FLUTTER_ROOT=/path/to/flutter_root \
    PUB_ENVIRONMENT=flutter_cli \
    pub upgrade

Observed results
Because your pubspec.yaml depends on the Flutter SDK, it's pinned to the same version of meta that Flutter is pinned to.  This is working as intended.
However, the previous steps are exactly what flutter update-packages --force-upgrade does, with the exception of putting the Flutter SDK dependency in its synthetic pubspec.yaml file.  Unfortunately, some of Flutter's transitive deps require the Flutter SDK and thus are triggering this behavior.  The net result is that any non-dev dependency listed in the Flutter framework's pubspec is pinned and never upgraded.

Thanks for getting to the bottom of this! This seems serious as it will leave developers stranded on stale deps. I'm going to tag this 'customer: product' to signal my believed importance.

@mit-mit tagging it as "customer: critical" will get it seen in the weekly triage (https://github.com/flutter/flutter/wiki/Issue-hygiene).  Would you say this is critical?

flutter update-packages is for development on flutter itself, and force-upgrade is only for creating PRs to flutter, it should never be run by a developer using flutter.

@jonahwilliams, the issue is that it doesn't upgrade our dependencies properly.


Add proxy support

My ssh server is behind a firewall, so connections require a proxy. Using OpenSSH, this is possible with a ~/.ssh/config setup like this:
Host server.com
  ProxyCommand ssh -q -W %h:%p<EMAIL_ADDRESS>  # Alternatives:
  #ProxyCommand ssh<EMAIL_ADDRESS>exec nc %h %p 2> /dev/null
  #ProxyCommand ssh<EMAIL_ADDRESS>'exec 3<>/dev/tcp/server.com/22; cat <&3 & cat >&3;kill $!'

Such capability appears to be available within ssh2, so please add support. I think it would be best if the proxy command were configurable.

+1
I simply use "ProxyJump myservername" in Remote-SSH config and it works really transparently.
I would love to be able to use this with remote-fs.


performance-based list ordering?

A comment in #54 said --

What is the performance? (quite brave to put yourself before Mark Logic)

This is the first suggestion I've seen that the list ordering is based on anything other than randomness.
As you now seem to say that "performance" (a rather opaque and variably defined word) is supposed to guide the order of these listings, it seems reasonable that some notes should be added to the page -- minimally including what benchmark(s) are being used to determine this comparison, and how new entrants may produce verifiable results to guide their own placement on the list.  Minimal information required would include:

what hardware (or cloud VM setup) should be used?
what network or other tuning should be applied?
what dataset should be used (if not specified within the benchmark)?

LDBC and TPC benchmarks are reasonably well specified along those lines, though it is entirely possible to run any benchmark against a poorly configured instance and get terrible results, where a properly configured instance would deliver great results.
I would especially like to know these answers so that Virtuoso can be put in its proper positions in all sections where it is (or should be) listed.

Hi Ted,
the list is not ordered by performance benchmarks.
In fact it is not really ordered. Perhaps a little by popularity.
If you feel something should be rearranged, please tell me so.
best
sed

I would suggest some ordering, by something a bit less ephemeral and subjective than "popularity".
The most common (dare I say, "default") ordering for such lists is alphabetical by product or, less often, vendor name.  Such ordering is typically visually obvious, letting visitors easily locate and/or appropriately add items of interest.  I would be happy to produce a PR for such, if you would apply it.

Hi Ted,

thanks for your Energy. But I do not want to make it alphabetically. In this case some weird DBs might appear above which I do not like.

I am not fully lucky with the way OpenLink Virtuoso been presented now:

The format is different. There are many CR/LineFeeds in there. No database description has this.
One database should be in there only once. E.g. Arango DB is in several categories, but mostly with a link to multimodel. It should be like this too for OpenLink.
In the feedback section I speak about a 500 char limit. Every vendor somehow likes to break it ;-)

If you do not sent a PR I would change it for your product.
Best
Stefan Edlich


Readme for coaps update

Please review updates to the coaps start command.

@Vyrastas @abtink - made the requested change, thanks.


Intellisense tip "Process keyword" was not localized

VSCode Version: 1.44.2
OS Version: Windows x64 10.0.18363
Language: Non-English

Steps to Reproduce:

Open a workspace which contains a .cpp file
Open a cpp file
Type "#include" in the cpp file

Expected:
The intellisense tip "Process keyword"  was localized
Actual:
"Process keyword" was not localized

Does this issue occur when all extensions are disabled?: Yes

This only happens when you have the C++ extension installed.


WinGet Support for the preview version

What feature or improvement do you think would benefit Files?
Add support for standalone WinGet packages for the Files (Preview) versions, because the self-updater of the preview version sometimes takes a little longer or cannot be used in the event of a start-up crash.
Since I download files from the Microsoft Store anyway, the Store version is sufficient for me personally, but the Preview version unfortunately has no external updater.
Requirements

publish files under FilesCommunity.Files
publish files preview under FilesCommunity.Files.Preview

Files Version
2.4.40
Windows Version
Windows 11 Pro
Comments
No response

The preview version updates automatically, opening the app will automatically check for updates and display a notice on the toolbar when one is available.

Yes, but I have the problem (issue is about to be uploaded) that the preview version doesn't even start.
So even if you patch it, I would have to go to the website and download it from there instead of winget upgrade --all

We already have a WinGet version for the stable app, would you like to open a PR on the WinGet repo adding the preview version?

One issue with it is the version number has to be updated for a new version or Winget will not update as a newer version already installed.

@xIUPITERx are you willing to maintain the WinGet package for the preview version?

How complicated would it be?

You'd have to submit an updated package to the WinGet repo about once a week to keep it up to date.

Properly you would just have to change the version number in the manifest files on the WinGet repo witch can be done from GitHub file edit feature

I'll have a look at it, but it might take a while because it's a bit stressful IRL.

Closing for now but happy to help if you have any questions.

https://github.com/files-community/Files/issues/11380#issuecomment-1437132690

I've filed https://github.com/microsoft/winget-pkgs/issues/166364#issue-2450869495.


HaLVMs in Amazon's Cloud

What is the status of this? What things need to be added to HaLVM to make this work?

It should work, but has never been tested.

It doesn't look like there is a HaLVM AMI available. it needs to work with AKI, like mirageOS does.
Would this script get me 90% of the way there?
https://github.com/mirage/mirage/blob/master/scripts/ec2.sh
I rather not build HaLVM on bare metal, can I run the fedora build host via HVM on AWS?

My plan was to use that script as a base, yes.
And yes, you should be able to build the build host on AWS, you just won't be able to run HaLVMs on it.

OK, update: I was able to get an upload and boot (I think) a HaLVM on EC2 ... it doesn't work well. After some investigation, it looks like EC2 uses an old version of Xen that the HaLVM doesn't presently support. It's possible that the problem stems from that. So the next step is to figure out a way to build Xen 3.4.3 for a platform I can mess around with, and make sure that all those issues are accounted for.

Wow. Okay, good to know. I built a build host on EC2 using ubuntu 14.04 it took around 4 hours so I didn't get a chance to actually build any of the same projects yet, thanks for the update.

my Docker host is running in a t2.micro instance which has this version of Xen:
[    0.000000] DMI: Xen HVM domU, BIOS 4.2.amazon 06/02/2014
[    0.000000] Hypervisor detected: Xen HVM
[    0.000000] Xen version 4.2.
[    0.000000] Xen Platform PCI: I/O protocol version 1
I am going to continue building HaLVM.

Hmmm. Looks like t2.micro instances are HVM-based, whereas the HaLVM is paravirt-based. It's also not clear if they support PV-GRUB or a similar system or not.

Right, that was just the build host; I wasn't trying to run HaLVM on that machine, just build it on that machine.
Amazon does support PV-GRUB, just not on that instance type. I am now realizing that Xen version has nothing to do with the Xen version they run on their PV instances... sorry!
http://www.brendangregg.com/blog/2014-05-09/xen-feature-detection.html

I was able to use a modified version of the ec2.sh to boot the GetId sample program on a m3.medium instance. Do you have another unikernel I should be testing with? I will try some more advanced examples today.

If you could get the WebServer to start, that would be amazing!
https://github.com/GaloisInc/HaLVM/wiki/HaLVM-Web-Server-Quick-Start

Building network-hans-0.2...
Preprocessing library network-hans-0.2...
[1 of 7] Compiling Hans.Socket.Handle ( src/Hans/Socket/Handle.hs, dist/build/Hans/Socket/Handle.o )
[2 of 7] Compiling Network.Socket.Internal ( src/Network/Socket/Internal.hs, dist/build/Network/Socket/Internal.o )
[3 of 7] Compiling Network.Socket.ByteString.Lazy ( src/Network/Socket/ByteString/Lazy.hs, dist/build/Network/Socket/ByteString/Lazy.o )
[4 of 7] Compiling Network.Socket.ByteString ( src/Network/Socket/ByteString.hs, dist/build/Network/Socket/ByteString.o )
[5 of 7] Compiling Network.BSD.ServiceDB ( src/Network/BSD/ServiceDB.hs, dist/build/Network/BSD/ServiceDB.o )
my system runs of memory here. it has 2gb, how much do you recommend?

You could also add swap space
On Feb 23, 2015 3:14 PM, "A. F. Dudley"<EMAIL_ADDRESS>wrote:

Building network-hans-0.2...
Preprocessing library network-hans-0.2...
[1 of 7] Compiling Hans.Socket.Handle ( src/Hans/Socket/Handle.hs,
dist/build/Hans/Socket/Handle.o )
[2 of 7] Compiling Network.Socket.Internal (
src/Network/Socket/Internal.hs, dist/build/Network/Socket/Internal.o )
[3 of 7] Compiling Network.Socket.ByteString.Lazy (
src/Network/Socket/ByteString/Lazy.hs,
dist/build/Network/Socket/ByteString/Lazy.o )
[4 of 7] Compiling Network.Socket.ByteString (
src/Network/Socket/ByteString.hs, dist/build/Network/Socket/ByteString.o )
[5 of 7] Compiling Network.BSD.ServiceDB ( src/Network/BSD/ServiceDB.hs,
dist/build/Network/BSD/ServiceDB.o )
my system runs of memory here. it has 2gb, how much do you recommend?
—
Reply to this email directly or view it on GitHub
https://github.com/GaloisInc/HaLVM/issues/17#issuecomment-75622260.

Adding Swap is a good idea, still don't know how much to add.

I'm not sure. You might try adding "--disable-split-objs" to see if that helps decrease your memory requirements (at the cost of a larger binary).

Error from WebServer:
Xen Minimal OS!
start_info: 0x112e000(VA)
nr_pages: 0xf0000

shared_inf: 0x7db69000(MA)
 pt_base: 0x1131000(VA)

nr_pt_frames: 0xd
mfn_list: 0x9ae000(VA)

mod_start: 0x0(VA)
 mod_len: 0

   flags: 0x0

cmd_line: root=/dev/sda1 ro 4

stack:      0x96d840-0x98d840
MM: Init
  _text: 0x0(VA)

 _etext: 0x7dc7d(VA)

_erodata: 0x9a000(VA)
 _edata: 0x9fce0(VA)

stack start: 0x96d840(VA)
   _end: 0x9ade40(VA)

start_pfn: 1141
max_pfn: f0000

Mapping memory range 0x1400000 - 0xf0000000
setting 0x0-0x9a000 readonly
skipped 0x1000
MM: Initialise page allocator for 18ba000(18ba000)-f0000000(f0000000)
MM: done
Demand map pfns at f0001000-20f0001000.
Heap resides at 20f0002000-40f0002000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0xf0001000.
Initialising scheduler
Thread "Idle": pointer: 0x20f0002050, stack: 0x2070000
Thread "xenstore": pointer: 0x20f0002800, stack: 0x2080000
xenbus initialised on irq 1 mfn 0x1ba6fb1
Thread "shutdown": pointer: 0x20f0002fb0, stack: 0x2090000
Dummy main: start_info=0x98d940
Thread "main": pointer: 0x20f0003760, stack: 0x20a0000
"main" "root=/dev/sda1" "ro" "4"
vbd 2049 is hd0
******************* BLKFRONT for device/vbd/2049 **********
backend at /local/domain/0/backend/vbd/1397/2049
10240 sectors of 512 bytes

vbd 2064 is hd1
******************* BLKFRONT for device/vbd/2064 **********
backend at /local/domain/0/backend/vbd/1397/2064
8377344 sectors of 512 bytes

GNU GRUB  version 0.97  (3932160K lower / 0K upper memory)

+-------------------------------------------------------------------------+||||||||||||||||||||||||+-------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.

Press enter to boot the selected OS, 'e' to edit the

commands before booting, or 'c' for a command-line.  Mirage                                                                                The highlighted entry will be booted automatically in 1 seconds.     Booting 'Mirage'

root (hd0)
Filesystem type is ext2fs, using whole disk
kernel /boot/halvm.gz
block error -1 for op 0
============= Init TPM Front ================
Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront initialization! error = ENOENT
Tpmfront:Info Shutting down tpmfront
xc: error: panic: xc_dom_core.c:621: xc_dom_find_loader: no loader found: Invalid kernel
xc_dom_parse_image returned -1
close(3)
Error 9: Unknown boot failure
Press any key to continue...
I can provide access to the AMIs or anything else that might help with this issue.

GetId works just fine without debugging in xen turned on, is this also the case for WebServer or would that cause it to break?

I don't think debugging would matter.
Yes, can you open up the AMI? And how did you get that console output?

Here is the ami-ID I have made it public, let me know if you need something more:
ami-00e6b568
from the web ui:
actions -> instance settings -> Get system log (at the very bottom)
If you are using something like boto, you can pull it that way as well. I avoid the CLI tools, so I don't know how to do it from there.

Oh! Excellent on both fronts. I was despairing how I was going to debug these.
I'm seeing the same error as you in my instance, which is good, I suppose. :)

It boots now and sees a NIC:
root (hd0)
Filesystem type is ext2fs, using whole disk
kernel /boot/halvm.gz
============= Init TPM Front ================
Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront initialization! error = ENOENT
Tpmfront:Info Shutting down tpmfront
close blk: backend=/local/domain/0/backend/vbd/1122/2049 node=device/vbd/2049
close blk: backend=/local/domain/0/backend/vbd/1122/2064 node=device/vbd/2064
Found 1 NIC
22:00:0B:7F:CF:94

OK. As you might think, this suggests that it found an Ethernet card, but then either failed initializing it or failed to complete a DHCP handshake.
If this is an older version of Xen, then this could just be a matter of back-porting support for older NIC backends.

[    0.000000] DMI: Xen HVM domU, BIOS 4.2.amazon 06/02/2014
[    0.000000] Hypervisor detected: Xen HVM
[    0.000000] Xen version 4.2.
[    0.000000] Xen Platform PCI: I/O protocol version 1
[    0.000000] Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs.
[    0.000000] Blkfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated disks.
[    0.000000] ACPI: RSDP<PHONE_NUMBER>0ea020 000024 (v02    Xen)
[    0.000000] ACPI: XSDT 00000000fc00f710 00005C (v01    Xen      HVM 00000000 HVML 00000000)
[    0.000000] ACPI: FACP 00000000fc00f260 0000F4 (v04    Xen      HVM 00000000 HVML 00000000)
[    0.000000] ACPI: DSDT 00000000fc0035e0 00BBF6 (v02    Xen      HVM 00000000 INTL 20090123)
[    0.000000] ACPI: APIC 00000000fc00f360 0000D8 (v02    Xen      HVM 00000000 HVML 00000000)
[    0.000000] ACPI: SRAT 00000000fc00f4b0 000170 (v01    Xen      HVM 00000000 HVML 00000000)
[    0.000000] ACPI: HPET 00000000fc00f620 000038 (v01    Xen      HVM 00000000 HVML 00000000)
[    0.000000] ACPI: WAET 00000000fc00f660 000028 (v01    Xen      HVM 00000000 HVML 00000000)
[    0.000000] ACPI: SSDT 00000000fc00f690 000031 (v02    Xen      HVM 00000000 INTL 20090123)
[    0.000000] ACPI: SSDT 00000000fc00f6d0 000031 (v02    Xen      HVM 00000000 INTL 20090123)
[    0.000000] Booting paravirtualized kernel on Xen HVM
[    0.000000] xen: PV spinlocks enabled
[    0.000000] xen:events: Xen HVM callback vector for event delivery is enabled
[    0.264007] Xen: using vcpuop timer interface
[    0.264014] installing Xen timer for CPU 0
[    0.560094] xen:balloon: Initialising balloon driver
[    0.564038] xen_balloon: Initialising balloon driver
[    0.568079] xen:balloon: Cannot add additional memory (-17)
[    0.610123] Switched to clocksource xen
[    0.638675] xen: --> pirq=16 -> irq=8 (gsi=8)
[    0.638717] xen: --> pirq=17 -> irq=12 (gsi=12)
[    0.638741] xen: --> pirq=18 -> irq=1 (gsi=1)
[    0.638769] xen: --> pirq=19 -> irq=6 (gsi=6)
[    0.638799] xen: --> pirq=20 -> irq=4 (gsi=4)
[    1.061693] xen: --> pirq=21 -> irq=28 (gsi=28)
[    1.061765] xen:grant_table: Grant tables using version 1 layout
[    1.209680] xen_netfront: Initialising Xen virtual ethernet driver
[    1.358828] xenbus_probe_frontend: Device with no driver: device/vfb/0
I am running in a m3.medium. Which uses Xen PVHVM

:+1: on documenting this and getting it on the readme/front page. Would greatly facilitate experimentation and tickle the right buzzwords (Unikernel, EC2, AWS, etc.)

Is this still an issue?

Nope, it's done ... until someone finds a bug.


Set up puppeteer tests with Firefox.

#16240
Testing plan:
Tested locally.
GIFs or screenshots:
Here is the screenshot of "Not Secure Warning" hiding the Get API Key button.
Refer this commit

@chdinesh1089 @priyank-p can you do a review on this?

I have rebased the PR!
cc: @chdinesh1089 @priyank-p

Looks good to me. Added two comments which wouldn't require any code changes.

@chdinesh1089 Updated the PR!

Posted one comment; otherwise this lgtm.  I tried running it locally and got a hang, so we can open a follow-up issue to investigate that, as long as it still works in Chrome.  The eventual goal is to be able to run it in CI; before we do that, we'll want to do the trick of running it in Firefox mode 100x in CI to see if it fails nondeterminstically?  That in turn can determine whether we want to enable running this mode in CI.
@priyank-p @chdinesh1089 can help with how to do that?  I'm not sure if it's in our "working on puppeteer tests" documentation, but if not we should add it.

@timabbott I have rebased the PR and updated the changes required.

Posted one comment; otherwise this lgtm. I tried running it locally and got a hang, so we can open a follow-up issue to investigate that, as long as it still works in Chrome. The eventual goal is to be able to run it in CI; before we do that, we'll want to do the trick of running it in Firefox mode 100x in CI to see if it fails nondeterminstically? That in turn can determine whether we want to enable running this mode in CI.

Should I create one issue that will combine/point to all the issues or should I create separate issues?
BTW Where did it fail when you ran it?

I'd do a single master issue.
Can you rebase this PR for the merge conflicts?

Rebased the PR @timabbott!

I merged about half the commits with some textual tweaks as the series ending with d12257e2c1a76877dd1ae33b18d528e8fdfb456d, and pushed the rest back here.  It's worth your reading the commit messages and comments I adjusted, as it may help you improve your technical writing style.

I merged about half the commits with some textual tweaks as the series ending with d12257e, and pushed the rest back here. It's worth your reading the commit messages and comments I adjusted, as it may help you improve your technical writing style.

Ok, Tim. I'll work on it and try to improve it.

I think I know why it failed.
This is because the overlay was not completely closed.
I knew that because I ran the 07-navigation.ts 100 times in Firefox mode.
This fixes it 5d10e6fa (Please avoid the commit message).
It ran successfully for 100 times in CircleCI and Github Actions.
Should I also add this commit?

I didn't merge the rest mostly because I only had a moment and wanted to have a bit more time to think about some of the others.
@Riken-Shah yeah, definitely add additional bug fix commits to this PR.

OK posted a batch of comments on the rest of this PR.  I'm excited about this!

@timabbott  a gentle reminder - This PR is ready for another review.

Posted a couple small comments, otherwise lgtm!

@timabbott I have updated a PR!

Merged, thanks @Riken-Shah!


Archive command fails when model contains versioned imports.

Bug Report 🐛
The cicero archive command fails if the model.cto contains versioned imports or specifies a versioned namespace.
Current Behavior

Take the current<EMAIL_ADDRESS>archive and modify its package.json file to use cicero 0.24.0.

    "accordproject": {
        "template": "clause",
        "cicero": "^0.24.0",
        "runtime": "ergo"
    },

Confirm the namespace at the top of the model.cto looks like this...

namespace org.accordproject.helloworld

Execute the command cicero archive and the following output is displayed

% cicero archive
10:53:07 am - INFO: Using current directory as template folder
10:53:09 am - INFO: Creating archive<EMAIL_ADDRESS>

Now modify the namespace at the top of the model.cto to look like this...

namespace<EMAIL_ADDRESS>

Execute the command cicero archive and the following output is displayed

% cicero archive
10:53:41 am - INFO: Using current directory as template folder
10:53:41 am - ERROR: Expected identifier but "0" found. File /Users/martin/helloworld/model/model.cto line 1 column 40

Expected Behavior
As we "cannot use an unversioned import org.accordproject.contract when 'strict' option on Model Manager is set" then the cicero archive command should accept versioned namespaces and imports.

I would love to solve this issue . Can I know a little more about the issue and the location of the file?


Rewrite of Docker installation process

Sorry for the very large PR.
Rewrote most of the Docker installation workflow to simplify it and create abstractions away from specific Python versions and execution environments. These changes include adding optimized defaults, a multi-stage Docker build, support for modern OCI container standards, podman support, and general workflow optimizations.
These changes will allow for automation in building of image artifacts, unit testing, and creation of pinned releases in the future.

Yah, I can do that. I'll rebase it with latest and resolve any merge conflicts that come up. There shouldn't be any IMO.

We can do different requirements.txt for different Python versions within 3.9+ but most of the packages should be left floating to latest or on major version release (ie- "pandas==2.* "). Unless there's a backward compatibility, regression bug, or version pinning argument, there isn't an need to pin it IMO. When such an issue is discovered, you can add into requirements.txt as the minimum supported version across ALL Python 3.9+ versions. Based on my quick review of the code, I didn't see any Python 3.10+ specific syntax used so we should be good there.
Also a lot of core libraries also have constant security and bug updates so you don't want have to read a dozens of changelogs to discover this. Luckily Github will search for and alert you to these issues sometimes.


Unknown source dispatching touch events for GearVR controller

Same issue as #1245. Touch/Motion events are being generated by button presses, yet they aren't originating from the GearCursorController. I'm currently working on setting motion events for the GearCursorController, but these aforementioned touch events often interrupt any touch events I generate. To reproduce this error, you can use the code in the previous issue:
@Override
public boolean onTouchEvent(MotionEvent event) {
    Log.d("MyActivity", "onTouchEvent: " + event);
    ...do something...
    return super.onTouchEvent(event);
}

Notice that pressing any of the buttons besides home or back on the GearVR Controller will dispatch a motion event of the form
 MotionEvent { action=ACTION_MOVE, actionButton=0, id[0]=0, x[0]=1480.0, y[0]=720.0, toolType[0]=TOOL_TYPE_UNKNOWN ... }
The coordinates will always be (1480, 720), meaning there will always be a touch dispatched at that location.
I appreciate any help anyone can offer.

This is done by the platform by design. Confirmed also by https://developer.oculus.com/blog/developing-for-the-gear-vr-controller/.
What you could is filter out the touch events based on some criteria. Like tool type of value TOOL_TYPE_UNKNOWN and few other MotionEvent fields that probably identify the events uniquely.

Great, thanks for looking into this for me. I'll look into possible ways of ignoring the touch events.


Put pre-commit hooks into a GitHub sub-module

README of each repository needs to state that you have to run tools/setup.cmd. Other actions and checks can be made by the setup script itself - e.g., get the sub-module.

Initial proposal:

create a new github repository, possible name: ontokit
move the ./tools and ./validation directories from this repo, to same directories in ontokit
use git submodules to have ontokit show up as the ./ontokit directory in this repo
move the setup.cmd script to the base directory of ontokit
modify the setup.cmd and pre-commit scripts to work in this configuration and automate details of submodules as much as possible

If we implement the versioning ontology in gist as in #979, we could also put the versioning queries in ontokit. If people want to modify the queries they could still create their own versions.
Could everything that's now in gist tools also reside in ontokit?

Could everything that's now in gist tools also reside in ontokit?

Yes, that is my expectation.

We should also put the versioning queries into this repository.

Repository: ontology-developer-kit

Make sure everything from ./tools and ./validation has been copied over.

Note: Validations are currently gist specific.

Make sure everything from ./tools and ./validation has been copied over.

If validations are gist-specific in the sense of referring to gist, they should not be in the sub-module. If they are gist-specific only in the sense that they use the gist style guide, then we can include them since they enforce our conventions. Anyone who doesn't want to apply those conventions doesn't have to use them.


Add: Support for the LinkAccount card type

I would rather add a type option to #card, but I don't want to add a fourth parameter. Users will have to be careful to not call #card after calling #linkAccount.
On the bright side, I guess this protects us if Amazon ever changes the means by which one invokes the account linking process.

app.intent('MyAuthenticatedIntent', function(request, response) {
  const accessToken = request.data.session.user.accessToken;

  if (!accessToken) {
    response.linkAccount();
  } else {
    response.say('Welcome back, ' + lookupUser(accessToken).firstName);
  }
});


Add more info to the RCOS Main Page

I think the RCOS Main page can go over the history of RCOS and note some significant student projects (YACS/Submitty). Additionally, it could cover more of the process behind RCOS - how the first weeks you can find a project to work on then submit an Undergraduate Research Proposal(and link to this form) to do it for credit or do it for experience under the details tab. I think it should be easy for people who are interested in RCOS to get a better sense of what it is about and how to join.  Potential text to add is -  "Anyone can show up to the friday meetings and listen to the tech talks/project presentations given. If you want to work on an existing project you can talk to the people working on it or if you want to start your own project you can make pitch slides and work on that. Projects can cover fields such as Machine Learning, Web Development, Software Engineering, Hardware etc..  as long as they meet the criteria of being open source. Additionally, you can contribute to any existing open source project."

I'm going to mark this as closed - the rework of Observatory's front-end code (in observatory-client) is already tackling this issue.


Copyright

Copyright headers in the project say Copyright <year>, Yahoo! Inc. that is not correct, because I didn't sign any CLA with Yahoo.
It's suggested to change all headers to Copyright <year> Memory contributors and add a NOTICE file that lists copyright holders: Yahoo Inc. and Metamarkets Group Inc.

@leventov
I will have to check with our legal folks on this.
I should point out that it is an objective of mine to move this Memory functionality (along with DataSketches) to Apache Foundation (incubator), which at that point this should become moot.  To achieve this goal I would need Metamarkets to also support this move by declaring to AF that they need and use this technology and agree to continue to support it and contribute to it.  I think I need at least 3 companies to do that.  Being able to demonstrate heavy use within Druid would also help.

@leventov
Your contributions are licensed to this project under the terms of the Apache license. This project was published by Yahoo. You (or your company) still maintain copyright on your code, you did not assign your copyrights to Yahoo, and Yahoo did not ask you to assign your copyrights. Thus, the copyright declaration is correct, at it applies to the project as a whole.
There are a few ways in which open source projects manage their copyright declaration. Recently Google published a helpful analysis here https://opensource.google.com/docs/casebook/authorship/ addressing the underlying legal issues. The method we use in this project is the one we find most common. There are projects that use either joint copyright declaration or they create a virtual entity "Authors of FOO project" to act as joint owners. Many legal experts point to issues that joint copyright raises, although there are those who suggest it's not as bad of an idea as most people suggest. https://chesteklegal.com/wp-content/uploads/2017/08/Joint-Authorship-final-unbranded.pdf That said, the Patrick McHardy case and other cases point to the problems you face when you try to deal with conflicts in open source. We're looking to avoid those problems by operating our projects in a very standard and well-understood manner -- like most open source projects do.
Moreover, and probably most importantly, we believe this project will be ideal to contribute to ASF and incubate it alongside Druid etc. At that point I'll be asked by ASF to assign our copyrights to the foundation. I'm in the position to do that -- but I would not be able to do so if we assigned the copyrights to a virtual entity.  For the reasons above, we don't think it is in the best interest of the long term objective to change the copyright assignment to virtual joint entity when we prefer to steer this project toward the direction Druid.io is going.


Update supported platforms

🗣 Description
This pull request updates the platforms supported by this Ansible role in addition to ensuring that the cyhy-feeds package is installed with pip2.
⚠ Note
This pull request is reliant on the merge of the following PRs:

cisagov/ansible-role-cyhy-feeds#8
cisagov/ansible-role-pip#50
cisagov/ansible-role-python#46

💭 Motivation and context
We are in the process of updating the instances in cisagov/cyhy_amis to use Debian Buster for instances running Python 2 code. With the above mentioned PRs for Python/pip installation we can expand the supported platforms.
🧪 Testing
Automated tests pass.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] Tests have been added and/or modified to cover the changes in this PR.
[x] All new and existing tests pass.

✅ Pre-merge checklist

[x] Revert dependencies to default branches.

@jsf9k Would you look the changes over and see if you have any contention? This is just to get this PR through on Python 2 until we're ready to merge the instance this runs on bumping to Debian Buster (which will allow changing this project to Python 3 completely).


Strain data bugs

https://eric.dictybase.dev/stockcenter/strains/DBS0238556

[ ] Need to check for non-empty DOI string before attempting to fetch publication data
[ ] Add red color for error fetching publications
[ ] Convert γ in systematic name
[ ] Convert γ in names
[ ] Sort characteristics alphabetically
[ ] Sort phenotypes alphabetically

an example of a strain with HTML embedded in string


mass version command and latest version check

adds  a version subcommand to:

print the current version info
check if there are any newer releases of the CLI and print a warning if so.
print the git SHA it was built from (sometimes useful incase for whatever reason we push to a mutable tag and are confused)

modifies our releasing workflow to dynamically inject version and git SHA into our binary.
adds a -version flag (some gophers might expect this to be here and it's easy to give them that behavior w/ cobra)

fixes https://github.com/massdriver-cloud/massdriver/issues/1190
Notes for reviewer

if you're not familiar ldflags is a way to set dynamic values at compile time often used for versioning when running go build
I adjusted the make commands such that they'd set version and git SHA to indicate that this was built locally.

Question for anyone who knows

I'd love to do a "test run" of the release flow with the new LD flags before making it official could we do that with a pre-release in github?

truly honored, and humbled to have grand pleasure of being PR #69 on this repo ;)

I’m not positive about the pre-release stuff either. This all looks great like the use of LDflags.
I’m curious if we need the extra -version. It’s extra code, more output in help, and a second way to do something.

I’m curious if we need the extra -version. It’s extra code, more output in help, and a second way to do something.

I don't have a strong opinion and am happy to remove.
FWIW Cobra does all the implementation so it's just a one line of setting an extra struct field so maintenance burden is minimal. I take your point on multiple ways to do things / help duplication.
My original thought was that it might save someone the churn of -version flag unrecognized -> read help string -> ok i'll remove the dash.
I've definitely more than once been like and wished it just was behind all of those:
$ python version # no dice
can't open file 'version': [Errno 2] No such file or directory
$ python -version # grrrr
Unknown option: -e
$ python --version # FINALLY
3.9.13


Problem with psnr and ssim

Hi @bennyguo，thank you for your excellent work. During the experiment, I found that the psnr and ssim is very low, even lower than nues, and then I found that the perspective of the rendered image and the original image are different, and the two images are not aligned.

Hi! Did you use the camera parameters provided by BlendedMVS or you estimated them by COLMAP?

thanks for your reply! I used camera parameters estimated by colmap

This is probably because the estimated poses are different from those provided by BlendedMVS, causing the misalignment. You could try implementing a new DataModule utilizing the BlendedMVS data, or wait for my implementation :) If you are interested in implementing it on your own, you may refer to datasets/colmap.py for an example. All you have to do is to provide self.directions, self.all_c2w, self.all_images, and self.all_fg_masks in the dataset.

@lidemina Hi! I just found a bug in the COLMAP dataset. The camera parameters are inconsistent in the training and validation datasets due to the randomness of RANSAC used to estimate the ground plane, which leads to low PSNR as you described. I'll push a fix later today.

@lidemina Hi! I just found a bug in the COLMAP dataset. The camera parameters are inconsistent in the training and validation datasets due to the randomness of RANSAC used to estimate the ground plane, which leads to low PSNR as you described. I'll push a fix later today.

great to hear that, thanks for your reply!


10.0.0-beta.2

This is missing a changelog entry for https://github.com/realm/realm-object-store/pull/1032, which it pulled in.


TestNG 7.6.0 with gradle doesn't work with Java 8

TestNG Version

Note: only the latest version is supported
TestNG 7.6.0

Expected behavior
TestNG should work with JDK 8
Actual behavior
Execution failed for task ':testing:compileJava'.
> Could not resolve all files for configuration ':testing:compileClasspath'.
   > Could not resolve org.testng:testng:7.6.0.
     Required by:
         project :testing
      > No matching variant of org.testng:testng:7.6.0 was found. The consumer was configured to find an API of a library compatible with Java 8, preferably in the form of class files, preferably optimized for standard JVMs, and its dependencies declared externally but:
          - Variant 'antApiElements' capability org.testng:testng-ant:7.6.0 declares an API of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'antRuntimeElements' capability org.testng:testng-ant:7.6.0 declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'apiElements' capability org.testng:testng:7.6.0 declares an API of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'guiceApiElements' capability org.testng:testng-guice:7.6.0 declares an API of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'guiceRuntimeElements' capability org.testng:testng-guice:7.6.0 declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'javadocElements' capability org.testng:testng:7.6.0 declares a runtime of a component, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
                  - Doesn't say anything about its target Java version (required compatibility with Java 8)
                  - Doesn't say anything about its elements (required them preferably in the form of class files)
          - Variant 'junitApiElements' capability org.testng:testng-junit:7.6.0 declares an API of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'junitRuntimeElements' capability org.testng:testng-junit:7.6.0 declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'runtimeElements' capability org.testng:testng:7.6.0 declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'sourcesElements' capability org.testng:testng:7.6.0 declares a runtime of a component, and its dependencies declared externally:
              - Incompatible because this component declares documentation and the consumer needed a library
              - Other compatible attributes:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
                  - Doesn't say anything about its target Java version (required compatibility with Java 8)
                  - Doesn't say anything about its elements (required them preferably in the form of class files)
          - Variant 'yamlApiElements' capability org.testng:testng-yaml:7.6.0 declares an API of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)
          - Variant 'yamlRuntimeElements' capability org.testng:testng-yaml:7.6.0 declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
              - Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
              - Other compatible attribute:
                  - Doesn't say anything about its target Java environment (preferred optimized for standard JVMs)

Is the issue reproducible on runner?

[ ] Shell
[ ] Maven
[X] Gradle
[ ] Ant
[ ] Eclipse
[ ] IntelliJ
[ ] NetBeans

Test case sample

Please, share the test case (as small as possible) which shows the issue

Contribution guidelines
Incase you plan to raise a pull request to fix this issue, please make sure you refer our Contributing section for detailed set of steps.

The release notes had called out that 7.6.0 would require JDK11.
The release notes for 7.5 had also explicitly mentioned that 7.5 would be the last of the releases that would work on JDK8.
please either upgrade to JDK11 and use 7.6.0 or please stick to 7.5.


RUSTUP_UPDATE_ROOT not set by default

The rust install script (https://sh.rustup.rs) when executed fails with the error:
sh: 18: RUSTUP_UPDATE_ROOT: parameter not set
(23) Failed writing body

I tried it on two different ubuntu setup by executing curl https://sh.rustup.rs -sSf | sh. When I set the value manually it worked but as far as I understand it this variable should have been set with a default with a default value.

It looks like the script was just updated to fix this.

problem introduced in https://github.com/rust-lang/rustup.rs/pull/1495
The script now contains a potential contradiction if the user has not set a RUSTUP_UPDATE_ROOT.  The set makes use of unbound variables an error, and then there is a check for if the variables are empty.  This would be fine if the user had set RUSTUP_UPDATE_ROOT to an empty value, but breaks if they haven't set it at all.  I have to believe that is quite common.
`
set -u
if [ -z "$RUSTUP_UPDATE_ROOT" ]; then
RUSTUP_UPDATE_ROOT="https://static.rust-lang.org/rustup"
fi
`

See #1683

All I'll say is that it was nearing midnight when I tested 1.17.0's installer, and I clearly tested 1.16.0's instead because I'm super-clever like that.  Mea culpa.

I'll bankroll the use of a brand-new version number.  No stress.

We have a fix live which is fine for now, so unless other issues are spotted with 1.17.0 which we weren't aware of, I figure we'll leave this be.  @Delet0r are you okay for this issue to be closed?

Shure :D, thanks alot.


[DEVOPS-38] Hide minimized CMD window

The batch script shortcut target introduced in CSLA-62 causes a
minimized CMD window to spawn when opening the Daedalus shortcut.
This approach for suppressing it has been tested manually on Windows
Server 2012 r2.

Approach manually verified on Windows 10 as well.

cc @jagajaga

If a fix has been merged into rc, should I merge the same branch into master, or merge rc into master? cc @darko-mijic

@neongreen master must be >= RC or release branch


Be consistent with social link generation

Love the theme.
I noticed that the way Twitter links are constructed in default.html was different than Github, Dribbble and Instagram links:
default.html expects site.twitter to contain only your Twitter handle, where site.github, site.dribbble and site.instagram are expected to be complete URL strings.
This pull changes this so that the template only requires a handle.

All 3 sites, Dribbble, GitHub, and Instagram, are served over HTTPS. Can you change the links to https:? It saves the user a redirect from http -> https when they click the link.
And while you're there, would you change the Twitter link as well to https?

Good point. Incoming ...

@ssorallen All set with https:.

Great, thanks for the changes. :+1:


pcsxr: init at 1.9.94

Motivation for this change
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

I'm not sure if all those patches from debian are needed. At least 4 (so it uses the new plugins after a update and not cached) and 8 (so the build doesn't depend on date) are.

LGTM, but I think adding so many patches to the nixpkgs repo is not a good idea.
You can use fetchpatch and just fetch them from https://anonscm.debian.org/cgit/pkg-games/pcsxr.git/tree/debian/patches?h=debian/1.9.94-2, e.g. https://anonscm.debian.org/cgit/pkg-games/pcsxr.git/plain/debian/patches/01_fix-i386-exec-stack.patch?h=debian/1.9.94-2.

Ok, removed the patches from the tree and into fetchpatch.


python310Packages.azure-mgmt-containerservice: 20.5.0 -> 20.6.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.azure-mgmt-containerservice is: "This is the Microsoft Azure Container Service Management Client Library"
meta.homepage for python310Packages.azure-mgmt-containerservice is: "https://github.com/Azure/azure-sdk-for-python"
meta.changelog for python310Packages.azure-mgmt-containerservice is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20.6.0 with grep in /nix/store/sjsnp1jmsp565jkmn2gxkva4kl0ffmaj-python3.10-azure-mgmt-containerservice-20.6.0
found 20.6.0 in filename of file in /nix/store/sjsnp1jmsp565jkmn2gxkva4kl0ffmaj-python3.10-azure-mgmt-containerservice-20.6.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
azure-cli
python310Packages.azure-mgmt-containerservice
python39Packages.azure-mgmt-containerservice

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/sjsnp1jmsp565jkmn2gxkva4kl0ffmaj-python3.10-azure-mgmt-containerservice-20.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.azure-mgmt-containerservice https://github.com/r-ryantm/nixpkgs/archive/867941decf630135e7581b106a05446e11e908a3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/sjsnp1jmsp565jkmn2gxkva4kl0ffmaj-python3.10-azure-mgmt-containerservice-20.6.0
ls -la /nix/store/sjsnp1jmsp565jkmn2gxkva4kl0ffmaj-python3.10-azure-mgmt-containerservice-20.6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

azure-cli
python310Packages.azure-mgmt-containerservice
python39Packages.azure-mgmt-containerservice

Maintainer pings
cc @mwilsoncoding for testing.

Result of nixpkgs-review pr 198136 run on x86_64-linux 1

3 packages built:

azure-cli
python310Packages.azure-mgmt-containerservice
python39Packages.azure-mgmt-containerservice


[QUESTION] responsive design

hi,
It is one of the projects I use as a basis for developing applications. However, I couldn't find the slightest thing about responsive approach. Font size, icon size etc. are not based on the screen size in any way, they are used by giving a static size. In many projects, I see that they are customized according to the screen size
What is the right approach here? Why is this not the preferred approach in this application?

@mary-ext why did you dislike, if you have a comment I would like to hear it?


Validate that description is single line

@FFY00 what is the rationale here?
This breaks all our project installs via pdm-backend (which was updated yesterday to 0.8.0rc1).
Since when are multiline descriptions illegal?

The spec says they are one line:
https://packaging.python.org/en/latest/specifications/core-metadata/#summary
And putting multiple lines originally broke the format:
https://github.com/mesonbuild/meson-python/issues/67#issuecomment-1140458563
But it looks like we were joining the newlines correctly since 0.6 in https://github.com/pypa/pyproject-metadata/commit/c74f4c58b06931edf1477d6236026237db8c4b41.

@henryiii you are linking to the Summary field, not the Description field, which is causing these issues.

You are correct regarding the single line summary/description field
However due to the previous behavior it is effectively a breaking change

@frostming can decide here (also @dnicolodi or @rgommers for meson-python). If it should be warning for a release, then error, or have an opt-in/out by backends, etc, happy to leave it to them. If I were deciding, I'd look at the numbers on PyPI of multiline project.descriptions. (I'll likely do that at some point anyway).

I've just created a milestone for 0.8.0 - it'd be useful to start tagging issues/PRs with a milestone, makes it easier to investigate potential issues later.

even with a pre-release

This is vendored into pdm-backend, so it's actually a normal release of pdm-backend that found this, not a pre-release. Scikit-build-core will be vendoring in the next release too: https://github.com/scikit-build/scikit-build-core/pull/703 - partially because we guarantee reproducible SDists, and those can be affected by changes in pyproject-metadata. Also I want to ship METADATA 2.2 soon, and don't want to wait for all distros to update.

I'm not sure I follow. Is this about how the field is serialized in the METADATA file or is it about how it is specified in pyproject.toml? Clearly the former is possible as the format used for the METADATA file allows for splitting value into multiple lines (it just needs to be done properly, and it is actually required for very long field values). For the latter, the only thing that the specification says, is that description needs to be a string, thus, technically, newlines are allowed. However (unfortunately as most of the Python packaging specifications) the specification is very loose and lacking details on how the field is supposed to be used. I think that concatenating multiple lines into a single line is the correct thing to do. I'm not sure whether the multi-line support currently in pyproject-metadata is correct.

It's also interesting that only the core-metadata summary field is specified to be single-line, not the TOML description field - it is only specified to be a TOML string. TOML strings are generally allowed to be multiline.
Personally I also find this documentation way too obscure for something that is user-facing -- how is the average pyproject.toml user supposed to find a core-metadata specification documentation snippet (which is not even clear to be associated with the pyproject.toml description field to the uninitiated).

I think normalizing the description field in a way similar to
description = '\n'.join(description.splitlines())

is the best way forward. The multi-line value support currently in pyproject-metadata (linked by @henryiii a few comments above) does not seem right according to the metadata specification (summary should be a single line).
Is description the only field affected by this? Can other field contain newline characters?

I think normalizing the description field in a way similar to

I think you meant:
description = ' '.join(description.splitlines())

Technically, new lines are allowed in strings in toml. So you could put them in all the fields. IMO, that should be validated and error out, but it could be done. Many of them (like name) can't have spaces, so that rules out new lines too. license is free-form, so it probably can have newlines.

@henryiii When reading the core metadata specification, it is very hard for me to distinguish which ones are format requirements and which ones are validation requirements. The specification says that the format is RFC822-like. And RFC822 does not preserve newlines in any field (except the message body). Thus it is very weird to say that Summary is not allowed to contain newlines: the serialization format does not allow it. Therefore, I get that this is not a content validation requirement, but a serialization format requirement (a restriction of what RFC822 would otherwise allow). This is where my conclusion that the current pyproject-metadata behavior is not correct. But obviously there is quite a lot of speculation regarding interpretation of the specification.

I think you meant:
description = ' '.join(description.splitlines())

Ops. Yes, indeed. Too much multitasking...

I agree that the main issue here is the relatively late introduction of the new validation.
Poetry's [tool.poetry.description] does not complain about multiline descriptions. The serialized metadata summary is single line.

IMO, this is a standardization question. The guidelines should either be updated to describe what to do with multiline descriptions or to require a single line. If the latter, validate-pyproject and schemstore could validate that these are a single line, that might be a good first step.

If I understand the email-format correctly (which I probably don't), new lines are not possible without workarounds like the seven spaces + pipe one, which is only implemented for Description?

It's a decade since I've concerned myself with this kind of details, but my understanding is the same. Newlines are not preserved in email messages headers.

I would not introduce a warning at this point. Normalizing newlines to spaces seems natural enough to make it happen without warning, unless newlines are explicitly forbidden. Either replacing newlines with spaces or preserving newlines in the serialization format as in the current code (knowing that they would be substituted with spaces when the METADATA file is read) are fine for me. The latter may be a violation of the specification, but it seems that nothing breaks on this violation, thus it is inconsequential.

In my view, the current specifications are clear. Summary must be a single line, and description must be a string that maps to Summary. There is no mapping rule that says newlines in description get special treatment, so doing so would be a non-portable implementation detail. Changing any of this would require a spec change, and probably a PEP (as the evidence here is that the issue is not uncontroversial…)
As to whether this project should validate the field, or whether it should deprecate multi-line values, with or without a warning, that is a project decision. Projects specifying a multi-line description are technically in violation of the standards, and tools could fail as a result, but in practical terms the violation seems to do little harm. So I’m not sure that I personally see the benefit of being strict here.
I agree that there should be better user facing documentation describing how to write your pyproject.toml. Information is scattered over too many places, and at the same time too many tools don’t document things “because they are covered elsewhere”. Blaming the user for not finding the right detail in the spec isn’t helpful here. But nor is it fair to claim the standard can be ignored because it’s not obvious where to find it.

@pfmoore As indicated in previous comments, the format used for core metadata does not allow to encode a value containing a newline characters. Newlines must be followed by indentation and are treated as a continuation of the previous line. This kind of encoding is used when the value to be recorded becomes too long (I haven't checked where python.email.Message puts the limit when using the compat32 policy).
If the core metadata specification refers to the value before serialization, specifying that it should not contain newlines seems superfluous as newlines cannot be encoded, thus must be rejected a priori. If it refers to the encoded value, should it also be interpreted as an implicit limit on the length of the value?

The core metadata spec refers to the (abstract) value of the metadata, independent of serialisation. Specifying that Summary must be a single line is not superfluous, because the spec doesn't refer to any particular serialisation method. Indeed, PEP 566 originally included a specification for a JSON format serialisation of the core metadata. While that format was never standardised, disallowing newlines in that context definitely isn't redundant.
The email serialisation format is regrettably somewhat under-specified, as noted in the spec itself, precisely because the email format was never intended for this use and therefore doesn't cover all the nuances we need. That's regrettable, but simply a fact of life taht we have to deal with. The formats the standards are based on were defined in simpler times, when nobody felt the need for this level of precision.

IMO, if implementations are allowed to reject multiline description, then everyone should reject multiline descriptions, otherwise the point of PEP 621, having a single definition all tools can share, is somewhat invalidated. I'd assume tools that read PEP 621 that are not the backend generally don't strictly validate multiple lines, so in practice it's mostly okay, but it's still not at all ideal.
The problem with allowing multiple line descriptions is that then there is no assistance at all in keeping this short, and you end up with things like this (selecting the three longest project.description fields in all pyprojects.tomls on PyPI):
https://github.com/Abdel-RahmanSaied/mediaSecure/blob/caabcf86622a519a55a99f604d8dad60a27f94bc/pyproject.toml#L11-L47
https://github.com/ultrafunkamsterdam/nodriver/blob/9943eb8b4426e8153936da6346d77f7112b6bb2e/pyproject.toml#L4-L32
https://gitlab.tel.uva.es/juagar/qoptcraft/-/blob/89644a9ed0321bae314fedb59db3c5af22614541/pyproject.toml#L17-24
These projects obviously confused the project.description with the project.readme.text field. If this was enforced as a single line in pyproject.toml, then these projects would  Also, very interestingly, on PyPI these are showing the first line only, not the merging of all lines. Does setuptools just ignore the following lines?

On PyPI a couple of weeks ago, here's a count of the new lines:
-1: 97599
0: 39283
1: 39
2: 22
3: 12
4: 6
5: 4
6: 2
7: 1
8: 1
27: 1
35: 1

(-1 means the description is empty)
That means 0.2% of all projects use newlines in the description field.

Out of curiosity, here's a randomly selected one new line project:
https://github.com/TrueLearnAI/truelearn/blob/dc159e2418a8beafab8e96b665d96ed14c23fb4f/pyproject.toml#L19-L20
And the PyPI description is cut in half, as expected for setuptools: https://pypi.org/project/truelearn

That example suggests that the newline is somewhat incidental, included purely to wrap the text somewhere convenient. So for that case, replacing <spaces>newline<spaces> with a single space would probably be acceptable.
But of course, that may not always be true, and "in the face of ambiguity, refuse the temptation to guess"...
With regard to "if one project rejects newlines, all should otherwise interoperability suffers" - yes, in theory. In practice, though, changing backends is never simply changing the build-system value (otherwise why bother having multiple backends) so fixing the description isn't going to be a major problem. Practicality beats purity and all that - in this case, not breaking existing users of a backend is more important than making the transition marginally easier for people changing backends (IMO).

I’m not referring to changing backends, but tools that can read the pyproject.toml as well. A lot of work went into making sure that arbitrary tools can read this, and it has enabled some great things (like front ends allowing any backend, GitHub dependency graphs, Ruff and UV pull information here, validate-pyproject, etc. Tools like that cannot know what a multiline description will do; error, join (current behavior here), or truncate (setuptools). It may not be all that common for them to care about the description, but the fact remains that they can’t tell exactly what it will be.
I think that pyproject-metadata should not be opinionated, unless the specs are opinionated. Personally, I will check this field and throw a clear error inside scikit-build-core if it’s multi line, as that will help users understand this field.

OK. I think we're talking past each othere here - my apologies.
As far as standards are concerned, a project with a newline in the description value is invalid. Beyond that, the standards have nothing to say. In particular, the standards don't require tools to raise an error when they encounter invalid projects.
Tools have to make their own decisions as to how they handle invalid projects. Most are likely to take the stance that they will reject them, simply because that's easier. However, some tools might prefer (for backward compatibility reasons, or otherwise) to handle invalid projects. Yes, that means that if your project (or a project you're using) is invalid, some tools will fail. That's what happens once you stray outside of the standards.
As far as pyproject-metadata is concerned, I'm not sufficiently familiar with the project to have an opinion[^1]. It really depends on what tools use the library, and how they want to handle invalid data. Presumably most of those tools are build backends, of one form or another? That may affect what features they want from pyproject-metadata.
[^1]: Not that that's ever stopped me before! 🙂

Three build backends that I know of use pyproject-metadata: scikit-build-core, meson-python, and pdm-backend. I think that’s our major users. Others might use it directly for building utilities of some sort, but I think it’s mostly used through those build backends.
I’m happy to go with whatever the other backend maintainers like: no warning, warning, or error. I’ll make it an error for scikit-build-core regardless.
The current standards don’t say much about this field at all, could that be updated to say it’s a single line summary?

The current standards don’t say much about this field at all, could that at least be updated to say it’s a single line summary?

They say it's mapped to Summary, which is defined to be a single line. Saying that description should therefore be a single line as well feels like a simple clarification to me.

The core metadata spec refers to the (abstract) value of the metadata, independent of serialisation

the specification document opens with a description of the serialization format, thus I was under the impression that the specification covers both the data specification and the serialization format, thus the data does not exist in isolation from the serialization format.

Major thanks for the user-friendly fix in 0.8!


Minimum interval

Minimum interval is complex and causes problems. Always forget to change it. Doesn't guarantee work gets done.
Perhaps this will be resolved with Mo's scheduling.
Perhaps minimum interval should be calculated internally.
Perhaps minimum interval should just be a regulatory thing, but true scheduling is independent.

One way to possibly do this (pending scheduling) would be to have a "time between surveys" variable that would likely be a number of days or months... is this too easy/good to be true! @AkaMrmuffin @tbarchyn @KeeganShaw-GIS

I think we should keep "time between surveys." It actually represents a general scheduling time when there is no specific scheduling. One option to solve this issue is when scheduling is enabled, especially when specific survey time is required, such as "only fly aircraft at the July," then the "time between surveys" will be overwritten to 0 for each facility. Otherwise, use the "time between surveys".

What's the status on this @AkaMrmuffin and @KeeganShaw-GIS ? Is min_int only used if scheduling isn't used? Or is it used either way? My gut is to get rid of it and just calculate it automatically internally because I can't imagine a situation in which a technology with e.g., quarterly surveys would want to do them all in a month (it's just a bad idea). Should we get rid of this to simplify things - and allow people to schedule any way they want? Please discuss.

It is used either way. If the exact survey time interval is specified (e.g., only June 2018), they should be 0 for all facilities since min_int will stop technologies from visiting facilities. We can get rid of it, but when scheduling is not activated, the crew may visit some facilities too many times than other facilities since there is no enough rule to regulate their visiting order except the generated emission rate from the facility. I think this is part of the question: "how to represent the work practices when there are not enough data to define the real work practice." I am actually leaning to keep the min_int. We should discuss it this Friday.

@KeeganShaw-GIS  Can you please add this to the agenda for next week?

This is solved last week


Change Azure SKU to Standard_D32ads_v5 and move to West US 3

Also updates a bunch of tools.
This change is trying to fix the same timeout https://github.com/microsoft/vcpkg/pull/36485 was trying to fix; we are seeing the build die after 2 days despite that change.

/azp run

Failures are identical to https://dev.azure.com/vcpkg/public/_build/results?buildId=99450&view=logs&j=878666d5-db33-5b27-9e7d-b0c7ee352005&t=dc897974-8f7e-5107-e5db-0a01be8e9d4f


Excel application co-authoring

Office 365 monthly channel already support Excel client application co-authoring for SharePoint Online/OneDrive Online files.
Does it also apply for SharePoint 2016/2019 server? if yes, do we need OOS support?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3b626929-198d-3be9-d202-df1c80699327
Version Independent ID: 7bed15b6-1a2d-fff5-c62e-3c07308882c6
Content: Overview of co-authoring in SharePoint Server
Content Source: SharePoint/SharePointServer/governance/co-authoring-overview.md
Product: sharepoint-server-itpro
GitHub Login: @tomresing
Microsoft Alias: toresing

It does not apply. There is a note in this document covering that case

The Excel client application does not support co-authoring workbooks in SharePoint Server. The Excel client application uses the Shared Workbook feature to support non-real-time co-authoring workbooks that are stored locally or on network (UNC) paths. Co-authoring workbooks in SharePoint is supported by using the Excel Web App.


PHP7 Strict rule for each php file

I think we should add this to each php file.
<?php  declare( strict_types = 1 );
Yes, that implement that we map our source to php 7.

:+1:


Heap Sort

Add a file code file written in C++ of heap sort

Hi I would like to work on this issue as part of Octoberfest. Plz assign this to me.
Thanks.

can you assign this to me please? @amritansh22

@kratikaatgithub @khushi2912 Anyone of you can do it. Just read the contribution guide and open a PR once done

how can we add local file to git repo?

@amritansh22 Please let me contribute during event.

@Priyanshu2802 You can contribute anytime you feel. You can also open your own issues.

@KalyanKumar-4 I suppose you are using Github Web. After forking this repository, there is an option on top to add file

Click on it you can see the option to upload file.

@khushi2912 I have assigned this issue to you. Open a PR once done

Yes sure! @amritansh22


[WIP] Axes 3.0.0. Fixes #215 #223 #233 #236

Hi everyone.
I just did a bunch of changes to use the Django auth signals, so I suppose a lot of things may have changed.
It is possible to be some broken tests but I already tested on a Django 1.11 project and works pretty fine.
Please feel free to add comments or suggestions, and help me out fixing or improving tests. I won't have much time to work on them in the next couple weeks, but I would like this to be merged soon.
any help is very much appreciated.

It seems override_settings is not working on the tests. Can anybody please take a look?

This is due to everything using axes.settings directly. Basically, all the settings are set at import time, and ignore the fact that django settings are dynamic.
Take a look at django-appconf. I've never used it before, but it should be a quick fix for you

@camilonova Still need to check the tests? I can help :)

@jorlugaqui please do, any help is very much appreciated.

Coverage decreased (-62.5%) to 29.305% when pulling 4b319dc51e2bd477b71ae7d6acadd87a728c0692 on django-1.11 into 85ece7254157ca1b9be21b84687ac940cf424fab on master.

Coverage decreased (-51.09%) to 40.725% when pulling 36a0d28deba5d49ad1c5d7c105b010804955dfa8 on django-1.11 into 85ece7254157ca1b9be21b84687ac940cf424fab on master.

Coverage decreased (-23.7%) to 68.148% when pulling 04501cad373af7a13d9e88577f477efb4f0f1a98 on django-1.11 into 85ece7254157ca1b9be21b84687ac940cf424fab on master.

@cybojenix It was not that "quick" but it worked. Thanks.

@jazzband/members I need help checking AXES_COOLOFF_TIME seems is not working as before.

@camilonova
Please be more careful about pinging (currently) 278 people, most of them not being involved in this particular project.

@blueyed sure.

@jorlugaqui can you help me checking?

@camilonova, yes, will try to test it this week.

@camilonova tested manually in Django==1.11.4, AXES_COOLOFF_TIME seems to be working, but the tests are complaining because of incorrect status code from admin checking. I'm still investigating it.

Sorry for jangling your nerves.., but any news on this issue? Thx!

@camilonova I tried manually with a different version of Django, this time with 1.11.3 and again seems to be working (using Django app admin).
What I noticed is that probably the test test_failure_limit_once is not working properly: This test tries to block the user using admin app, the issue is that after the third chance you don't get blocked, it just gives you the error user/logging message, and then because of that others tests fail in cascade, or at least most of them, since other tests use test_failure_limit_once
If I repeat the process manually in admin app then I got the 403 blocked (expected behavior), so I guess something in test configuration is missed. I tried to figure it out yesterday but I did not succed, I will keep trying.
PWD: Any ideas?

@jorlugaqui I think this has been reported as an actual issue somewhere. Looking through the issue history could be fruitful, though I'm not 100% sure I remember correctly :)

Any help in here is very appreciated. I do not have much time to work on this right now.

@JosephKiranBabu Done. Thank you.

@camilonova when you guys are planning to release new version with django 1.11 support ?

@edicopratik as soon as we make the tests run in this branch. If you want/can help please go ahead.

I think I'm moving on removing the failed tests so we can merge this branch and later on we can improve the test suite.

This will only support python3 and django 1.11 and later


Integrated Terminal: add "Clear Console" button

VSCode Version: 1.14.0-insider

Currently, the buttons in the integrated terminal panel are just add(+) and kill(trash can).
The only two way to clear terminal output is using the shortcut or using the context menu.
(Using 'clear' command in terminals seems like "cleared", but when we scroll to top later after some outputs, the previous output reveals again. -> it may seem to another bug I think)
However, I can see "Clear Console" (clearRepl in i18n resource id) buttons in vscode's problems, output and debug console.
Why don't we have "Clear Console" button in vscode's integrated terminal?
Would it be a PR-welcomed feature?

Since the user can't customize the actions the fear of adding this is causing bloat. Right now there terminal has 4 buttons and a dropdown which is the most UI along with output. I think we should revisit this when the terminal UI gets redone for tabs https://github.com/Microsoft/vscode/issues/10546 and/or the panel gets tweaked to work vertically https://github.com/Microsoft/vscode/issues/2806
Also there are other ways of doing a clear in the terminal which you might prefer:

cmd+k on macOS

via command palette: ctrl+shift+p, "tclear"

via custom keybinding:
{ "key": "ctrl+k", "command": "workbench.action.terminal.clear",
                    "when": "terminalFocus" }


IMPROVEMENT: Ensure program exits with appropriate error codes and messages

Description
This enhancement adds proper exit codes to ensure the program exits with 0 when no errors occur, and a non-zero code when an error is encountered. The program currently handles errors appropriately with try/catch blocks, but the exit codes need to be explicitly set to signal success or failure to the operating system.
Implementation
Modify the program to check for errors before exiting. If an error is detected, output the error message to stderr and exit with a non-zero status code. If no errors are present, the program should exit cleanly with a 0 status code.
An example of how this could be implemented in JavaScript:
try {
  // ... other code

  process.exit(0);  // Exit with 0 if no errors
} catch (error) {
  console.error(`Error: ${error.message}`);
  process.exit(1);  // Exit with 1 for errors
}

Closed by https://github.com/cleobnvntra/genereadme/commit/1f7222d14a60d6b0b659dcf936a4debc7060a674


Release/1.6.2

Coverage remained the same at 96.992% when pulling 058afec738e02e765709ada02e56c4a448e12b03 on release/1.6.2 into<PHONE_NUMBER>5389b5298e99256626b37e2abbace6 on develop.


Some other things we may want to remove/clean up

src/scene.jl (testing file?)
src/utilities/quaternions.jl (not used anymore?)
GLMakie/src/experiments (testing?)
src/jl_rasterizer (WIP?)

See also #1511

Thank you for the quick merge request! It has to be merged quickly and released because Makie is now broken after an env update.
Is there a way to automatically find redundant imports?

I just looked for import and using with grep.
I also don't think these duplicates are really the reason you got an error. Many of them have been around for a long time. Did you try restarting your Julia session and importing Makie again? Or restarting, building and them importing?


[Fonts] Icon request: water_drop

pls

The water_drop icons already exist in flutter 2.10.3. See screenshot below. Closing as the icon already exists.


Server needs to support CORS

When UI is done as a separate server the requests are treated as Cross-origin and current API rejects the OPTIONS requests fired by browser (works with CLI for GET/POST). The below link details the problem and possible workarounds.
https://nabil6391.medium.com/avoid-cors-requests-for-a-react-app-2988e0061c1a

Closed due to inactivity


Buggy maps view with time range

Tested on rerun-sdk 0.20.0a3. See video (nuscenes example)
https://github.com/user-attachments/assets/6a58b8be-6fc0-4e52-9bb8-1407515c8224

There are several things at play there:

The "jumping to default" position (aka Rerun HQ) whenever no data is in the view. That's very annoying and I'm going to fix it asap. (Note: with this example, there are two ways to have no data: move the cursor all the way to the left; and set an empty-interval time range.)
The "set zoom level on double click" behaviour.

To expend on the latter, double click does two things:

engage "follow" mode (aka auto-scroll to track the object or mean position of all objects)
set the zoom level to fit the data (that's one-shot, not continuously updated like the scrolling)

There are technical reasons for why things are that way. There are certainly ways to improve on that behaviour, but that requires more work than can fit for 0.20.

Related:

https://github.com/rerun-io/rerun/issues/7884

Can this be closed or is there more to do? (Cursory testing seems to indicate working as intended now.)


📃: Add Cybersecurity Pdf resources

:red_circle: Title :
Add Cybersecurity PDF Resources
:red_circle: Aim :
To curate and provide access to valuable PDF resources related to cybersecurity for learners and professionals in the field.
:red_circle: Brief Explanation :
This contribution aims to compile a collection of high-quality PDF resources covering various aspects of cybersecurity. The resources will include topics such as network security, ethical hacking, penetration testing, cryptography, and incident response. Each resource will be accompanied by a brief description to help users understand its relevance and content.
PDF Resources 📄

The Basics of Hacking and Penetration Testing
A comprehensive guide covering the fundamentals of hacking and penetration testing techniques.

Cybersecurity Essentials
An introduction to key concepts and practices in cybersecurity, aimed at beginners.

Network Security: A Beginner's Guide
A practical guide to understanding network security principles and techniques.

Ethical Hacking: A Hands-on Approach
This resource provides a hands-on approach to ethical hacking practices and tools.

Cryptography and Network Security
An in-depth look at cryptographic techniques and their application in securing networks.

Screenshots 📷

N/A

:white_check_mark: To be Mentioned while taking the issue :

Full name : Charul Chim
What is your participant role? (Mention the Open Source Program name. Eg. GSOC, GSSOC, SSOC, JWOC, etc.)
GSSOC

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

add label and level gssoc-ext level


Other buttons not enclosed in a Submit in the Form component will also cause the form to submit.

<Form.Root onSubmit={(evt) => {
    console.log('submit...')
    evt.preventDefault()
}}>
    <Flex direction="column" gap="3">
        <FormField name={"name"}
                   label={"名称"}>
            <Form.Control asChild>
                <TextField.Input
                    value={name}
                    onChange={(evt) => setName(evt.target.value)}
                />
            </Form.Control>
        </FormField>
    </Flex>
    <Flex gap="3" mt="4" justify="end">
        <Button variant="soft" color="gray">Cancel</Button>
        <Form.Submit asChild>
            <Button>Create</Button>
        </Form.Submit>
    </Flex>
</Form.Root>

Is there something wrong with my implementation?

I'm very sorry, this seems to be a very basic front-end issue, but I am a novice and just found the cause of the problem. Under the form, all buttons will trigger submission by default. If this behavior is not needed, the type of the button needs to be set to button.
<Button variant="soft" color="gray" type="button">Cancel</Button>


Shutdown menuitem only escapes to pico8 shell

Currently selecting the shutdown menu item will kick you onto the pico8 shell, whereas in reality it should terminate the entire picolauncher process.

resolved


[BUG] #804 search/median_search.cpp FIXED

[BUG] Incorrect results #804
File: search/median_search.cpp
Example:
A=[25,21,98,100,76,22,43,60,89,87]
43 is the 4th smallest number of A.
https://github.com/TheAlgorithms/C-Plus-Plus/issues/804

Please fix clang-tidy warnings.

fixed clang-tidy warnings. Please have a look.


CDS-94692-CD 1.31.x RN

Release Notes item from the following lists are documented:
https://harness.atlassian.net/wiki/spaces/PIPE/pages/21717024769/Change+List+for+Pipeline+Service+Build+1.68
https://harness.atlassian.net/wiki/spaces/PD/pages/21719646209/NG+Release+SAAS+March+26th+2024+for+1.31.x-+Build

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://660673cf54c2bcb72a598e13--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://660a5845e50ac460ed0f06bf--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://660ad3b0b604847c72712935--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://660b9e32137caf7fb611a73f--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://660bbf99137caf9a1411aac8--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://660cfa2872121995002cc52b--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://660cfa8e72121995fd2cc53d--harness-developer.netlify.app


[APPM-741] Wrong task description for application subscription workflow

Application subscription workflow task description is stated as an API subscriptino to the 'Default Application' in the admin dashboard and on BPS Approve API [ yahoo - 1.0.0 ] subscription creation request from subscriber - testuser4 for the application - DefaultApplicationReference: https://wso2.org/jira/browse/APPM-741

Not related to IoT server, hence closing


Confirmation is unreadable. Pink on Pink

Describe the bug
Text is unreadable. Background and text color are same.
To Reproduce
Steps to reproduce the behavior:

On a table, check a row.
Goto "with selected" and hit "delete"
Notice, confirmation is pink on pink

Expected behavior
text is readable.
Screenshots

Additional context

Operating system: win 11
Browser: ff
phpMyAdmin version: 5.2.1
BooDark version: 1.0.1

Add any other context about the bug here.

nvm, i see it is fixed in newest release