Agda: Fix haskell version 2.6.1

In the future, it would be good to maintain multiple agdaPackages sets along side different versions, like how coq-packages is set up. To do this we would need access to different versions of Agda. As a start I have tried to fix version 2.6.1 of Agda so that the current package set can be fixed to this version and won't break when another version comes out.
My understanding is that this will make an Agda package which follows the latest version, and an Agda_2_6_1 package which is fixed on 2.6.1. Apologies if what I have done in this PR does not do this or if there is a better way to achieve this.

This works, although it is possible that Agda-2.6.1 will stop building due to updates to its dependent Haskell packages.  You'll have to keep an eye on this in the future.
Also, Agda-2.6.1 is building for me, so I will merge this in.
However, it appears that cabal2nix can't figure out the license for Agda, so Hydra is not building Agda.  This will be quite inconvenient for anyone who actually wants to use Agda from nixpkgs.  (If you look at the output of cabal2nix cabal://Agda-2.6.1, you can see that hydraPlatforms is set to [].  My guess is that this is because the license is set to unknown.)
I imagine you probably want to fix this, so I'd suggest sending a PR to the cabal2nix repo sorting out this licensing issue.  I'm not sure whether you need upstream to specify the license correctly in the cabal file, or you need to teach cabal2nix about the nixpkgs license, or you need to add an additional license here in nixpkgs.  If you can't figure out which of these is necessary.

cabal2nix cabal://Agda also has hydraPlatforms = stdenv.lib.platforms.none; so I expect this is set somewhere in nixpkgs. I'll have a look

I expect this is set somewhere in nixpkgs. I'll have a look

It is set in nixpkgs, because hackage2nix is used to generate the hackage-packages.nix (or whatever the name is) file, which internally uses cabal2nix.
I imagine you'll have to send a PR to cabal2nix to fix this.  (Or maybe make sure a known license is used in the upstream Agda.cabal file?)

I had a look, it seems to use a custom license and has OtherLicense in its cabal file

I'm not sure I understand, if Agda has hydraPlatforms = [] then surely that isn't being fixed in cabal2nix.

I'm not sure I understand, if Agda has hydraPlatforms = [] then surely that isn't being fixed in cabal2nix.

I believe that cabal2nix is the codebase that has the logic that sets hydraPlatforms to [] if the license is OtherLicense.

I had a look, it seems to use a custom license and has OtherLicense in its cabal file

I believe the correct solution here is to add the license to the list of known licenses here in nixpkgs, and then send a PR to cabal2nix that adds a special case to to the Agda package to use that license.

I'm not sure I'm being clear:

Agda-2.6.1 has hydraPlatforms = []
Agda (as currently in nixpkgs) also has hydraPlatforms = [] set by cabal2nix
Agda is build by hydra
Why does something special need to be done for Agda-2.6.1?

Huh, sorry, it looks like I was wrong about this.
I was under the impression that having hydraPlatforms = [] would cause Hydra to not build your package.
However, you're completely right that Agda is being built by Hydra.
$ git clone ...nixpkgs...
$ cd nixpkgs
$ nix-store --query --outputs $(nix-instantiate -A haskellPackages.Agda)
/nix/store/hhmwwvhv6cc2wg6kcbcqnrqns8211vl9-Agda-2.6.1-data
/nix/store/5dxg14cbr1y56mplp2vw9yz3357hipsn-Agda-2.6.1-doc
/nix/store/hjzx97m5l9l3ba80335k0iycvm6d6hzs-Agda-2.6.1
$ nix path-info --json --store https://cache.nixos.org/ /nix/store/hjzx97m5l9l3ba80335k0iycvm6d6hzs-Agda-2.6.1 | jq
[
  {
    "path": "/nix/store/hjzx97m5l9l3ba80335k0iycvm6d6hzs-Agda-2.6.1",
    "narHash": "sha256:1rz0yzj7y3znwhm0p9dy6v98fqlc608lr2jgrh7fvm9fp918fqgq",
    "narSize":<PHONE_NUMBER>,
    "references": [
      "/nix/store/06655sar8phm0i83j2j9yl9xidxhiiv7-regex-base-<IP_ADDRESS>",
      "/nix/store/0w4lcn6i0wn6i8c5gi80xl3gr6c24qz7-hashtables-<IP_ADDRESS>",
      ...
      "/nix/store/vrddk9p422y272i7k772ig8npii49h3l-STMonadTrans-0.4.4",
      "/nix/store/y18bhdg3snpwcwbxaah57sygpj4pj1hw-aeson-<IP_ADDRESS>"
    ],
    "deriver": "/nix/store/8ynwb2s0c8320syn26r203hanqwvq2y7-Agda-2.6.1.drv",
    "signatures": [
      "cache.nixos.org-1:wgy4gA463XRRX/SDlR1cSOTcUO5OF19/T2u9m1jxVbm+s6PXx5uUwM6tH4bVgfJsdjfIg6lPUMV1hh0uwt6ZAA=="
    ],
    "url": "nar/151w2jdmkq7jhg36xdrxkfnm6qaylbfs4xb4q1934166xbf4lg3l.nar.xz",
    "downloadHash": "sha256:151w2jdmkq7jhg36xdrxkfnm6qaylbfs4xb4q1934166xbf4lg3l",
    "downloadSize": 85050812
  }
]

So haskellPackages.Agda is definitely being built by Hydra.
However, it definitely has hydraPlatforms = [].  The following is taken from hackage-packages.nix:
  "Agda" = callPackage
    ({ mkDerivation, aeson, alex, array, async, base, binary
     , blaze-html, boxes, bytestring, Cabal, containers, data-hash
     , deepseq, directory, edit-distance, emacs, equivalence, exceptions
     , filepath, geniplate-mirror, ghc-compact, gitrev, happy, hashable
     , hashtables, haskeline, ieee754, mtl, murmur-hash, pretty, process
     , regex-tdfa, split, stm, strict, template-haskell, text, time
     , transformers, unordered-containers, uri-encode, zlib
     }:
     mkDerivation {
       pname = "Agda";
       version = "2.6.1";
       sha256 = "0af1nyyscdc4gr4l0k3ayq3rn8qxqkx1b7rh4mw023gkz1m433v7";
       isLibrary = true;
       isExecutable = true;
       enableSeparateDataOutput = true;
       setupHaskellDepends = [ base Cabal directory filepath process ];
       libraryHaskellDepends = [
         aeson array async base binary blaze-html boxes bytestring
         containers data-hash deepseq directory edit-distance equivalence
         exceptions filepath geniplate-mirror ghc-compact gitrev hashable
         hashtables haskeline ieee754 mtl murmur-hash pretty process
         regex-tdfa split stm strict template-haskell text time transformers
         unordered-containers uri-encode zlib
       ];
       libraryToolDepends = [ alex happy ];
       executableHaskellDepends = [ base directory filepath process ];
       executableToolDepends = [ emacs ];
       postInstall = ''
         files=("$data/share/ghc-"*"/"*"-ghc-"*"/Agda-"*"/lib/prim/Agda/"{Primitive.agda,Builtin"/"*.agda})
         for f in "''${files[@]}" ; do
           $out/bin/agda $f
         done
         for f in "''${files[@]}" ; do
           $out/bin/agda -c --no-main $f
         done
         $out/bin/agda-mode compile
       '';
       description = "A dependently typed functional programming language and proof assistant";
       license = "unknown";
       hydraPlatforms = stdenv.lib.platforms.none;
       maintainers = with stdenv.lib.maintainers; [ abbradar ];
     }) {inherit (pkgs) emacs;};

@peti do you know why this would be happening?  I was pretty sure that when hydraPlatforms = stdenv.lib.platforms.none, the package wouldn't built by Hydra.

It seems like the vast majority of haskell packages have hydraPlatforms = []

@alexarice In general, all packages that are marked broken will have hydraPlatforms = [].  Packages that are not marked broken will have hydraPlatforms not specified (unless they can only be built on darwin or linux or something).
As far as I know, a package that is not marked broken, but does have hydraPlatforms = [] should not be built by Hydra.
I'm not surprised that Agda has hydraPlatforms = [], since its license is "unknown", but I am surprised that it is being built by Hydra.
I was wondering if @peti would have some idea why this is happening.

To add to the confusion, I believe Agda isn't cached on arm.

@cdepillabout, I believe Agda is being built on Hydra because pkgs/top-level/release.nix lists it explicitly:

agdaPackages = packagePlatforms pkgs.agdaPackages;

@peti, oh good find, I had no idea that that adgaPackages existed, or that it would force Hydra to build Agda.

agdaPackages is quite new, though Agda was definitely build by hydra before it's introduction

Sorry to resurrect this thread but I'm not sure where the best place to ask is. My understanding is that that this change would introduce a new Agda_2_6_1 attribute, though this doesn't seem to have happened. Is this because the current version is 2.6.1 so it doesn't make a duplicate? In any case, is there any way to get an alias for 2.6.1 which won't break when 2.6.2 comes out?

Is this because the current version is 2.6.1 so it doesn't make a duplicate?

I think this is what is happening.  If you don't think this should be the case, then you can open an issue on the cabal2nix repo, which contains the program hackage2nix, which is responsible for this.

In any case, is there any way to get an alias for 2.6.1 which won't break when 2.6.2 comes out?

I'm not sure there is a good way to do this.
I guess you could always do something like haskellPackages.Agda_2_6_1 or haskellPackages.Agda.


Disable list of commands from playground repositories

Description
DiceDB Playground is an interactive platform that allows users to experiment with DiceDB commands in a live environment, similar to the Go Playground. Users will be able to submit and execute commands directly through a web interface. The initial implementation will focus on enabling users to search for and trigger commands.
For more details about DiceDB playground you can check here.
To enhance the security of our application, we need to implement a blacklist for certain  commands that could potentially lead to data loss or unauthorized access. This blacklist should be enforced in both the backend and frontend components of our application.
Add following commands for blacklisting:

FLUSHALL
FLUSHDB
DUMP
ABORT
AUTH
CONFIG
SAVE
BGSAVE
BGREWRITEAOF
RESTORE
MULTI
EXEC
DISCARD
QWATCH
QUNWATCH
LATENCY
CLIENT
SLEEP
PERSIST

Note: Implementation will be part of both DiceDB playground frontend repo and backend repo.
Tasks

Backend Implementation:

Update service to restrict the blacklisted commands.
Implement middleware or a service layer to intercept and reject requests for blacklisted commands.
Ensure appropriate error responses are returned when blacklisted commands are attempted.

Frontend Implementation:

Block blacklisted commands in frontend, with error message as below:
- (error) ERR unknown command '<COMMAND_NAME>'

Test the implementation to ensure that blacklisted commands are correctly rejected with appropriate error messages.
Document the changes made in the README or relevant documentation files.
Add sufficient unit and integration test for the same

hey can you assign this to me?

Thanks for assigning, So i have to open pull requests in those repos right?

Thanks for assigning, So i have to open pull requests in those repos right?

Yes

@lucifercr07  I would like to work on this  issue could you please assign it to me

Frontend changes merged as part of https://github.com/DiceDB/playground-web/pull/19

I have also added blacklisted commands in the backend repo - https://github.com/DiceDB/playground-mono/pull/23

Closing, merged as part of https://github.com/DiceDB/playground-mono/pull/23


Update external dependencies (jars from maven)

What's up with the test failure?

I'm looking into it. It's related to updating byte-buddy.

PTAL - I removed mockito and byte-buddy for now.

What could go wrong :shrug:


[Bug]: build failure on macos

What happened?
the build action on macOS always fail recently
Steps To Reproduce
Information and Steps to reproduce the behavior.
Relevant log output
No response

including boringssl is conflicted with the system installed openssl


Is there a way to run rustic-cargo-run interactively

so that I can enter input to a command line application I'm building.
I think https://emacs.stackexchange.com/questions/51156/cargo-process-does-not-accept-user-input is about the same question.
Using cargo.el seems a bit redundant because rustic seems to provide a lot of that already.

Changing the suggestion from the SO answer to
(with-eval-after-load 'rust-mode
  (define-key rust-mode-map (kbd "C-r") 'my-cargo-run))
(defun my-cargo-run ()
  "Build and run Rust code."
  (interactive)
;;  (cargo-process-run)
   (rustic-cargo-run)
  (let (
      (orig-win (selected-window))
      (run-win (display-buffer (get-buffer "*Cargo Run*") nil 'visible))
    )
    (select-window run-win)
    (comint-mode)
    (read-only-mode 0)
    (select-window orig-win)
  )
)

seemed to be enough.
Perhaps still worth considering adding something like this to rustic.

Is this ok for you #126 ?

Yes, that would do.
I there a reason not to make it a comint buffer? (just curious)

Why would you want the compilation buffer be in comint-mode ? It's just about sending some input to the process right ? There will also be issues if you want it to work correctly after you entered your input.

With the code above it's like running like in a shell which is convenient for developing interactive command line apps.
I don't know much about Emacs yet. How would it not run correctly this way?

Example:
If you want to use compilation-next-error in comint-mode this won't work because you have a check in the function that will complain about it:

(defun compilation-next-error (n &optional different-file pt)
  "Move point to the next error in the compilation buffer.
This function does NOT find the source line like \\[next-error].
Prefix arg N says how many error messages to move forwards (or
backwards, if negative).
Optional arg DIFFERENT-FILE, if non-nil, means find next error for a
file that is different from the current one.
Optional arg PT, if non-nil, specifies the value of point to start
looking for the next message."
  (interactive "p")
  (or (compilation-buffer-p (current-buffer))
      (error "Not in a compilation buffer"))

But if it's that important for you it would be possible to make a mode that's only being used by cargo-run ?

"Important" is a strong word. I'm at the beginning of the process in figuring out a good workflow for Emacs with Rust, with little to no knowledge in both.
I'll just experiment with above hack and your recent change and see how it works.
Thanks a lot for your support <3

Hi, I'm a beginner in Rust and I'm following the guessing game tutorial in the book.
In the tutorial, users would enter a number on each guess. With rustic-compile-send-input, I have to run the function on each guess, which is not so convenient for an interactive program.
IMHO, cargo run should focus on running the program rather than finding errors from compilation, which is taken care of in cargo check or cargo build. So it makes sense to let rustic-cargo-run use a separate buffer.

Can you please open a ned issue.


Check if Objective must be always improved when finding adaptable Objectives

Check if Objective must be always improved when finding adaptable Objectives.
Solve the following issue first https://github.com/meta-control/mc_mdl_tomasys/issues/11

Done at 8687ae7bffd488308c63713c667d86a2d9c39185


Version bump for 2.14.0 release

includes:

add TESTING.md ( Issue: #356 )
add support for HDP <IP_ADDRESS> ( Issues: #358 #359 )
add helper to fetch HDP build number from public repository ( Issues: #360 )

Although there should be no change in default behavior, I thought #360 is a big enough change to warrant the minor version bump.  We can say 2.14 potentially supports future HDP releases where 2.13 will not

failures due to https://github.com/sous-chefs/java/issues/463, fixing it here as its trivial


Fix Tests on New CI

Overview

Fix CI container configuration

Add ODBC library headers
Add timezone info
Fix pinned version of virtualenv
Add run option for host gateway, allowing port bindings to remain a way of have "multiple instances" for DB tests.

Swap libcurl test runners to pure python.
Configure git to fetch tags properly in CI.
Revert disable of Py27 tests, and gearman instrumentation.
Genericize gearman settings for CI vs local.
Fix coverage paths for containers.

Testing

Last test run before reverting container to latest tag that's unupdated: https://github.com/newrelic/newrelic-python-agent/actions/runs/5358678225

Codecov Report

Merging #843 (6e4c496) into main (658f818) will decrease coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #843      +/-   ##
==========================================
- Coverage   74.75%   74.65%   -0.11%
==========================================
  Files         198      198
  Lines       19324    19327       +3
  Branches     3307     3307
==========================================
- Hits        14446    14428      -18
- Misses       3999     4041      +42
+ Partials      879      858      -21

Impacted Files
Coverage Δ

newrelic/config.py
55.43% <100.00%> (+0.52%)
:arrow_up:

... and 47 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Mod Idea

Add Oil Pumps and Water Pumps to do the same as the miners

Like to place pumps everywhere?

Like to place pumps everywhere?

Yeah. For oil.

Yeah. For oil.

yes please!


Fix miscount in attestation rerequest banner

Description
The banner informing the user of how many text messages were being resent was based on the count of non-completed attestations, which can be greater than the number of attestations required to confirm a phone number.
Other changes
Time of lastRevealAttempt was being updated even when no new attestations were being revealed. This resulted in the user having to wait 1 min to re-request a text message if even none were on the way.
Tested
Manually
How others should test

Ensure the banner shows the right number of text messages requested
If the confirmation process is started (i.e., the user reaches the VerificationCodeInputScreen), then the user leaves the flow and resumes the confirmation process, ensure that the user is not forced to wait 1 min before requesting more attestations

Related issues

Fixes #458

Backwards compatibility
Yes

https://valora.testquality.com requirement R36. Do not remove or edit.

https://valora.testquality.com requirement R62.

https://valora.testquality.com requirement R63.

https://valora.testquality.com requirement R64.


Added machine learning compute from private repo.

Adding this in before Ignite. The feature flag has been removed on our RP so this is ready to be public. See the following PRs on the private repo for commit history. Initial, move to current branch, added an error provisioning property, removed an unneeded class. I'd like to get this PR in ASAP so that I can merge the .NET SDK into the public repo as well.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@shutchings,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

No modification for AutorestCI/azure-sdk-for-python

No modification for AutorestCI/azure-sdk-for-node

No modification for AutorestCI/azure-sdk-for-ruby


Apple clang v 15.0.0 cannot build registry

Bug description
On a Mac using the default c compiler clang from Apple, the following error occurs while building the registry (dev branch at commit a98f8bce6):

Compiler specifics:
Apple clang version 15.0.0 (clang-15<IP_ADDRESS>)
Target: x86_64-apple-darwin23.4.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

The alternative is to use the gcc compiler. However, we are likely to get questions on this if we don't address it.

The openfast_registry CMakeLists.txt file has the wrong version for the C++ standard. std::quoted is part of the C++14 standard, whereas the current version is listed as C++11. Most compilers in use should support C++14 so I'll summit a PR to change the required C++ standard version.

Fixed with 2210


Handling vips warnings

Is there a way to handel vips warnings? Or can I check if the image is ok before I use it?
here is a part of my supervisor log.
vips warning: VipsJpeg: read gave 3 warnings
vips warning:
vips warning: VipsJpeg: read gave 1 warnings
vips warning:
vips warning: VipsJpeg: read gave 2 warnings
vips warning:
vips warning: VipsJpeg: read gave 1 warnings
vips warning: VipsJpeg: Corrupt JPEG data: 490153 extraneous bytes before marker 0xd9
VipsJpeg: JPEG datastream contains no image

vips warning: VipsJpeg: read gave 2 warnings
vips warning:
vips warning: VipsJpeg: read gave 2 warnings
vips warning:
vips warning: VipsJpeg: read gave 6543 warnings
vips warning: VipsJpeg: Premature end of JPEG file
VipsJpeg: JPEG datastream contains no image

vips warning: VipsJpeg: read gave 6543 warnings
vips warning: VipsJpeg: Premature end of JPEG file
VipsJpeg: JPEG datastream contains no image

vips warning: VipsJpeg: read gave 2 warnings
vips warning:
vips warning: VipsJpeg: read gave 2 warnings
vips warning:
vips warning: VipsJpeg: read gave 2 warnings
vips warning:

You can set the VIPS_WARNING environment variable to silence ignorable warning messages. The command to run the functional tests uses this.
If an unrecoverable situation is reached when toFile or toBuffer are called, processing will stop and the error will be passed as the first parameter to the callback function.

What I like to do is find out witch image that gave that warning so I can replace the broken file. So how do I capture the warning and print it like this instead?
vips warning: VipsJpeg: read gave 1 warnings on /home/user/images/img1024_2.jpg

If you've not already seen it, #113 is related to this question. You'll probably need to add support for what you need to libvips itself.

Ah okej not mutch I can do about it then.


Add 2D covariant form using P4estMesh

This PR contains a preliminary implementation of a two-dimensional DG solver for PDEs on surfaces in covariant form, starting here with the variable-coefficient linear advection equation on the sphere.
I defined a new P4estElementContainerCovariant type to carry the specific geometric information needed for the covariant form. Since only the scalar advection equation is supported so far, I didn't add Christoffel symbols as part of this PR.
Trixi.jl's rhs!, weak_form_kernel!, flux_differencing_kernel!, compute_coefficients!, calc_interface_flux!, max_dt, and calc_error_norms functions are specialized in dg_2d_manifold_in_3d_covariant.jl so as to dispatch on the new type AbstractCovariantEquations{NDIMS, NVARS}. The physical and numerical fluxes called by those functions take in the cache as well as the node and element indices, so that all the geometric information can be accessed by these fluxes. This way, we do not need to store the spatially varying geometric quantities that the contravariant fluxes depend upon as auxiliary solution variables as I did in an earlier implementation of my spherical shallow water solver.
The initial condition is prescribed with zonal and meridional velocity or momentum components, which then get transformed in compute_coefficients! to get the local contravariant components. An additional elixir elixir_spherical_advection_covariant.jl has been added as an example of this, using a smooth Gaussian bell test case adapted from the standard Cosine bell case (Case 1 from the Williamson et al. test suite). Standard values of geophysical parameters are provided as constants in src/equations/reference_data.jl.
This PR also includes tests for the new weak-form and flux-differencing solvers, which give the same results when the arithmetic mean is used for the two-point volume flux. As discussed in #43, Trixi.jl versions below 0.9 are no longer supported.

After the discussion in #46, I wonder if this should be modified to not pass the cache around, or if it's best to merge it first and then look into cleaner alternatives.

Superseded by #47.


More general ITensorNetwork constructors

ITensorNetwork constructors that accept custom element types and undef.
Also add tests for orthogonalize, dijkstra_shortest_paths, and GraphsFlows.mincut that are currently broken but will be fixed by:
https://github.com/ITensor/ITensors.jl/pull/1039
https://github.com/mtfishman/NamedGraphs.jl/pull/27
https://github.com/mtfishman/DataGraphs.jl/pull/14
@JoeyT1994 @LinjianMa

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@414d008). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #41   +/-   ##
=======================================
  Coverage        ?   75.87%
=======================================
  Files           ?       29
  Lines           ?     1140
  Branches        ?        0
=======================================
  Hits            ?      865
  Misses          ?      275
  Partials        ?        0

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[WIP] support database metrics

Codecov Report
Attention: Patch coverage is 78.94737% with 12 lines in your changes missing coverage. Please review.

Project coverage is 79.96%. Comparing base (753a609) to head (1cc9df6).

Files with missing lines
Patch %
Lines

pkg/inst-api-semconv/instrumenter/db/db_metrics.go
78.94%
8 Missing and 4 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #272      +/-   ##
==========================================
- Coverage   80.02%   79.96%   -0.06%
==========================================
  Files          23       24       +1
  Lines         976     1033      +57
==========================================
+ Hits          781      826      +45
- Misses        156      164       +8
- Partials       39       43       +4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Indicator margin/padding?

In horizontal mode, it would be useful if there were a property which allows for the customization of space between the indicators and the bottom edge of the control. I would love to increase the distance of the indicators from the bottom as we have a design where there is an element which overlaps the bottom of the control and it almost overlaps the indicators.
The above property could control the distance of the indicators from the right most edge of the control in horizontal mode as well.
Is there any chance of implementing such a property? I cannot seem to find a different way to do this.

Yes it could be done, but in your case, why an element overlaps the carousel?

I think a picture better explains the scenario.

Whats that bump for?

It's just part of the design that is being implemented for the app being built. The bump overlays the carousel and the images scroll underneath it. It would be great if the carousel indicators can be moved up.

As i said, it can be done but it doesn't make sense just because of your design, you got my point? A functionality needs to be something the whole community needs.

There's a lot of things to change just to add that property.

Yeah I understand. I saw that it might be a lot of work, so if I am the first person requesting this, then the work involved may not justify the end result. But if it has been requested before, then perhaps it would make sense. The alternative for me is to hide your carousel indicators, still use your carousel view and implement the indicators on my own, positioning them where appropriate.

This control soon will be officially included in Xamarin.Forms core.

That is great news, because this control is better than the Xamarin.Forms.CarouselView control which is still in beta. One of the reasons for opting to use this control is because the carousel indicators are built in.
I understand that you would not want to necessarily implement the positioning of the indicators just because one person asked for it. It makes sense for this to be a larger community requirement before it is considered to be implemented. So if it is the case that such a feature would not widely be used, then I will implement the indicators myself which will overlap the control at the correct position.

Let me give it a try first.

Sorry, doing this is way complicated :(

If my work is helping you, please help me back: https://xamarinhq.wufoo.com/forms/nominate-a-xamarin-mvp/
This is what i have done that is community visible:

Alex has been pretty active sharing his knowledge and answering questions in StackOverflow, GitHub and Xamarin Forums.
Alex has been open sourcing Xamarin components and plugin with the community, with more of 10 repositories being maintained on GitHub.
One of Alex's Xamarin.Forms plugin, the CarouselView, is currently being pulled into the Xamarin.Forms core (https://github.com/xamarin/Xamarin.Forms/pull/853). As an stable widget, this control has become the standard for Xamarin.Forms carousel screens with more that 16K downloads in NuGet and more than 100 solved and not open issues.
Another Alex's plugin, the SegmentedControl (https://github.com/alexrainman/SegmentedControl), is a big candidate to be also pulled into Xamarin.Forms core.
Plus Xamarin.Forms UI related plugins, Alex shares plugins to set app icon Badge, Google Analytics and KeyChain access.
Alex shares his knowledge about cutting edge technologies like Couchbase NoSQL and MobileIron integration with Xamarin Apps.

I know this is closed, but it would also be great if the positioning of the Inidicators could be made a bit more flexibel, e.g. at a specified height of the control itself

What I actually did to achieve this was to margin the topside of the indicator to a negative value.


Enable FPU for RP235X Core1

Fix #3353

We should do like cortex-m-rt for consistency: enable the FPU only when building for -eabihf targets.
(I think there are reasons to not enable the FPU if you don't need it? like lower power consumption?)
https://github.com/rust-embedded/cortex-m/blob/master/cortex-m-rt/build.rs#L69-L71
https://github.com/rust-embedded/cortex-m/blob/master/cortex-m-rt/src/lib.rs#L597


API Permanently Removed or Not

          Not just swagger. The whole API is down. I'm getting this error when I tried to send request via post man to https://countriesnow.space/api/v0.1/countries/states

<!DOCTYPE html>
<html>

<head>
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <meta charset="utf-8">
    <title>Heroku | Application Error</title>
    <style media="screen">
        html,
        body,
        iframe {
            margin: 0;
            padding: 0;
        }

        html,
        body {
            height: 100%;
            overflow: hidden;
        }

        iframe {
            width: 100%;
            height: 100%;
            border: 0;
        }
    </style>
</head>

<body>
    <iframe src="//www.herokucdn.com/error-pages/no-such-app.html"></iframe>
</body>

</html>

Originally posted by @everestster in https://github.com/MartinsOnuoha/countriesNowAPI/issues/201#issuecomment-2558716270

Hello, apologies for the downtime, we are back online 🚀
we were late on our service payment.

Here's a link if you'd like to support. ❤


Morning session code review on desktop

Please kindly reduce the use of ids as seen in the list items for <li> tags, consider using classes

😉Well done, I couldn't found any issue in the pull request #4

Nice code, I do not see any issue. Nice coding.


tests don't run in release mode

I got this compilation failure when running the tests with
swift test --sanitize=address -c release -Xswiftc -enable-testing

which we do as part of the SwiftNIO compatibility/test suite before releases.
Compile Swift Module 'AWSSDKSwiftCore' (29 sources)
Compile Swift Module 'AWSSDKSwiftCoreTests' (9 sources)
/private/tmp/.nio-release-tools_z0dmMg/aws-sdk-swift-core/Tests/AWSSDKSwiftCoreTests/AWSClientTests.swift:39:34: error: value of type 'AWSClient' has no member 'debugCreateAWSRequest'
            let awsRequest = try sesClient.debugCreateAWSRequest(
                                 ^~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
/private/tmp/.nio-release-tools_z0dmMg/aws-sdk-swift-core/Tests/AWSSDKSwiftCoreTests/AWSClientTests.swift:66:34: error: value of type 'AWSClient' has no member 'debugCreateAWSRequest'
            let awsRequest = try kinesisClient.debugCreateAWSRequest(
                                 ^~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~
error: terminated(1): /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-build-tool -f /private/tmp/.nio-release-tools_z0dmMg/aws-sdk-swift-core/.build/release.yaml test output:

@weissi hmm... yeah this is to maintain the fileprivate status of createAWSRequest method in release mode. The public debug method is added as an extension when the Debug directive is set
-Xswiftc -DDEBUG
is this an option for you to add?

@jonnymacs sure, that's fine. Just out of interest, why don't you make it internal ?

@weissi it's a good question.  I didn't define the original access control for createAWSRequest, that was @noppoMan, so he may provide a better answer. But I imagine it's because internal still allows for exposing the method through an extension in another part of the code and we want to restrict all access to this method to just this file.
Using the DEBUG directive to add an internal debug method that is exposed with @testable seemed like a nice workaround to preserve the fileprivate access control while still adding some tests. (note - i misspoke in my prev comment, debugCreateAWSRequest is not public)

I don't think we've needed this, so sent out https://github.com/swift-aws/aws-sdk-swift-core/pull/134

fixed

thank you! I will change the nio release tools to run aws core with release mode too :)


[proposal/question] Shouldn't the event endpoint be used for visit events?

Why is a separate visit endpoint needed, can't we just use /event?
e.g.
fetch('/event', {method: "POST", body: JSON.stringify({
  name: "visit",
  website: location.host,
  page: location.pathname,
  referrer: document.referrer
})})

Relevant: https://github.com/Litlyx/litlyx/blob/main/producer/src/index.ts#L31

For code design reasons, we have decided to keep them separate, as we handle visits and events in our database independently.


Desync - Save/Discard changes

I ran into synchronization issues after trying to save a file/discard changes.
If you run into this issue, please follow the instructions here to capture diagnostic information that will help us figure out the cause.

Closing as stale.


Consider replacing browser state behavior with scoped style tags for pseudo-selectors.

We need to implement scoped style tags (#18) anyway. Maybe once those are done, we drop the current state handling behavior and instead output :hover, :focus, and :active into a scoped style tag. This would make them work on the initial server-side render too, before the client hydrates the app.

Captured better in #53


Should support user-defined joints in libsdformat

Came up in: https://github.com/RobotLocomotion/drake/issues/12404
For things that are nominally enumerated, add a USER_DEFINED enum, with the ability to access the raw XML... but only when it's a namespaced type? e.g. //joint/@type="drake:bushing"
From Asana, 2019-11-07

Per f2f with @scpeters, @azeey, and @sammy-tri:

No concrete use case yet for libsdformat to have a custom joint type
If/when needed, still need to decide between <joint type="custom:drake:bushing"/> or <drake:joint type="bushing"/>

Decision should be motivated by simplicity, e.g. to ensure frame graph can be parsed, libsdformat should know how to get pose + frame name from joint for implicit frame. (Easy if <joint/> is used, needs custom reg if <drake:joint/> is used)
Failure mode: Some cases don't care if the joint can't be parsed (e.g. Rviz, you just want frames + visuals), while others should really fail fast (e.g. Gazebo simulation, Drake kinematics, etc.)

There now seems to be a use case for Drake: planar joints
https://github.com/RobotLocomotion/drake/pull/13747
FYI @seancurtis-tri

Rescoped to just joints.
Relates #138

From meeting via VC:

SC: Schema validation
* Enumerating joint types for accept //joint/@type
* Alternative: //joint/@type="custom"

<joint type="custom">
<drake:joint_type>planar</drake:joint_type>
</joint>

<joint type="custom" drake:type="planar">
...
</joint>

<drake:joint name="my_joint" ...>
<pose relative_to="..."/>
</drake>

<link>
<pose relative_to="my_joint"/>
</link>

* How can custom schemas can be validated?

This should be scribed into a proposal

From conversation in osrf/sdf_tutorials#45, I believe we've reinforced that the ultimate solution should be //joint/@type="custom". It should be either like Option (1) or Option (2), which is up to the downstream library.
I'm going to take Option (3) out of the running.
FYI @seancurtis-tri @joemasterjohn


Log missing for new boxes?

I just added a fresh Vagrantfile and ran the Vagrant up command in VSCode. This is for a box that I have yet to download. Nothing happens. The output is empty. Although it appears to be doing something because it created a .vagrant directory.
Does it just not show any sort of log when you are creating a new box?

Also at the end of the operation it looks like it worked. An info box comes up saying Vagrant process succeeded or something like that.
Looks like the log just isn't working for this extension. Any vagrant operation I do, there is nothing in the Output panel (using the Vagrant dropdown).

Ah I just noticed another issue that is probably related. Whenever I run a new vagrant command it creates a new Vagrant dropdown in the Output panel. And it appears that you can only select the last one created. That's why it's not working.

You should make it just append to existing output panel instead of creating a new one for each operation.

i have this same problem

+1 on windows 7


Node version update from 16.* to 18.*

Node version update from 16.* to 18.*

@gichinna-fadv this issue was fixed on #8 and available on v1.2.1. Additionally, please check out the archival notice as it will no longer be maintained. Thank you for your support and understanding!


test: there is a test failed when running "make check"

Version: v1.x
Platform: Ubuntu 18.04.2 LTS x86_64
gcc version: gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0

not ok 117 - getaddrinfo_fail
# timeout
# Output from process `getaddrinfo_fail`: (no output)

Thanks for the report. That test makes a DNS query for xyzzy.xyzzy.xyzzy. (not expected to resolve to anything) which seems to time out on some people's networks.
Suggestions on how to improve that welcome. Otherwise we should probably just close this out.


Update api_keys.md

Added information pertaining to the following:

Generating new keys - without invalidating the old ones
Replace old API keys with new keys
Testing API Keys
"Inactivate an API key" is there in the same section, so it seems it would be redundant to reiterate.

@ksigler7

fixes #2985

Hello @NexWeb,Thanks again for the PR! It's HACKTOBERFEST! We want to show our appreciation by sending                                              you some special Hacktoberfest swag. If you have not already, could you please fill out                                              this form so we can send it to you? Thanks!                                             Team SendGrid DX


[BUG] Quickstart sidebars are broken

Describe the bug
https://docs.fastht.ml/tutorials/quickstart_for_web_devs.html

Expected behavior
I've replicated this locally with the latest commit of nbdev.
Environment Information
Please provide the following version information:

fastlite version: n/a
fastcore version: n/a
fasthtml version: n/a

Confirmation
Please confirm the following:

[x] I have read the FAQ (https://docs.fastht.ml/explains/faq.html)
[x] I have provided a minimal reproducible example
[x] I have included the versions of fastlite, fastcore, and fasthtml
[x] I understand that this is a volunteer open source project with no commercial support.

Fixed in #554


Test issue

The test is being in progess.
Steps to reproduse:

Test1
Test2
Test3 @DimitarEfremov Test this

Test was succesfull.


Fail on eslint on the react app

The build and deploy job (GitHub Actions) fails with the error below. I have tried to change lots of settings, but always gets the same error.

react-scripts build

Creating an optimized production build...
Failed to compile.
Failed to load plugin 'import' declared in '.eslintrc.json': Cannot find module 'eslint'
Require stack:

/github/workspace/react-app/node_modules/eslint-plugin-import/lib/ExportMap.js
/github/workspace/react-app/node_modules/eslint-plugin-import/lib/rules/named.js
/github/workspace/react-app/node_modules/eslint-plugin-import/lib/index.js
<EMAIL_ADDRESS>Referenced from: /github/workspace/react-app/.eslintrc.json

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: react-scripts build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /github/home/.npm/_logs/2022-02-28T17_14_26_001Z-debug.log

Thanks for this feedback.


Add Request Position When GPS Connected

Hello Anton,
Can you add feature request position when gps connected for GPS teltonika?
Regards
J.P

Do you mean like a button to request position from device? It will require to finish #7 first.

Little difference, i want when gps connected to the server, server force device to give latest position, currently i have problem with Teltonika FM100, some device always send old data... not currently so so i need to force gps to send last position...
TQ

Do you have any documentation on how to send location request to Teltonika devices?


Welcome screen Is always showing

I cannot disable the Welcome Screen package as well as "Show On Startup" is not saved.
I am using Mac OS Catalina 10.5.2.

Hey @spedy. Thank you for opening the issue.
I cannot reproduce the bug on the latest version of atom. Can you confirm if the bug still occurs.
macOS Catalina 10.15.6
apm  2.5.0
npm  6.14.5
node 10.20.1 x64
atom 1.50.0
python 2.7.16
git 2.24.3

I can confirm that this does happen and has been happening for over a year, It just got to the point that it annoyed me enough I was going to raise an issue, then I found this one, so I won't raise a new one.
Just to be clear this is the screen Welcome Screen I get every time I open Atom:

What's most annoying about it is that if you have multiple Atom windows then these welcome pages and extra frame are applied to every window, I usually have 4-5 windows depending on what projects i'm working on so having to close the "Welcome Guide" page, then the extra pane that the "Welcome Guide" page was in and then the "Welcome" page on every window.
As a result I rarely close Atom and put off taking the upgrades because it means dealing with closing all these welcome pages. I Just upgraded to 1.53.0 and this issue continues.
I would like to suggest that the welcome pages should only display on windows with no open files, this alone would go a long way to resolving this issue for me.

macOS Catalina  10.15.7 (19H2)

Additional screen shot from 1.54.0, showing confirmation that all windows are impacted

Additional screen shot from 1.54.0, showing confirmation that all windows are impacted

Just to make sure, does editing the config.cson (and adding it to “disabled packages”) work?

Just to make sure, does editing the config.cson (and adding it to “disabled packages”) work?

I will give it a try, but can you give me a link to how to do that?

I will give it a try, but can you give me a link to how to do that?

I will give it a try, but can you give me a link to how to do that?
@damies13
https://flight-manual.atom.io/using-atom/sections/basic-customization/#global-configuration-settings

I will give it a try, but can you give me a link to how to do that?
@damies13
https://flight-manual.atom.io/using-atom/sections/basic-customization/#global-configuration-settings

Actually unchecking the option Show On Startup
https://stackoverflow.com/questions/41342121/how-to-get-rid-of-atoms-welcome-screen
Seems to have fixed it for me, but that is really not an obvious place to look to disable it. That checkbox should really be on the core page of the atom settings or at worst the editor page, I would have never found that setting if I had not googled "Atom disabled packages Welcome Guide", and I would not have googled that if not for @ThatXliner 's comment about disabled packages.
I still consider the facet that this is checked by default to be a bug, the default setting should be to only show the first time a user opens atom, or worst case on atom version upgrades, but not every time unless someone turns that option on. I should not have to go hunting this deep into the settings to disable a welcome screen

Actually unchecking the option Show On Startup
https://stackoverflow.com/questions/41342121/how-to-get-rid-of-atoms-welcome-screen
Seems to have fixed it for me, but that is really not an obvious place to look to disable it. That checkbox should really be on the core page of the atom settings or at worst the editor page, I would have never found that setting if I had not googled "Atom disabled packages Welcome Guide", and I would not have googled that if not for @ThatXliner 's comment about disabled packages.
I still consider the facet that this is checked by default to be a bug, the default setting should be to only show the first time a user opens atom, or worst case on atom version upgrades, but not every time unless someone turns that option on. I should not have to go hunting this deep into the settings to disable a welcome screen

The checkbox is right on the bottom, though. I think they should do a step in the welcome guide on how to disable the package.

The checkbox is right on the bottom, though. I think they should do a step in the welcome guide on how to disable the package.

I still consider the facet that this is checked by default to be a bug, the default setting should be to only show the first time a user opens atom, or worst case on atom version upgrades, but not every time unless someone turns that option on. I should not have to go hunting this deep into the settings to disable a welcome screen

Well, if it was off by default, we'll need a way to activate it on the initial, first, startup

I still consider the facet that this is checked by default to be a bug, the default setting should be to only show the first time a user opens atom, or worst case on atom version upgrades, but not every time unless someone turns that option on. I should not have to go hunting this deep into the settings to disable a welcome screen

Well, if it was off by default, we'll need a way to activate it on the initial, first, startup

@damies13 Does the checkbox in your first screenshot not work?

@damies13 Does the checkbox in your first screenshot not work?

@Aerijo Fair call, I totally didn't see that, how embarrassing.

@Aerijo Fair call, I totally didn't see that, how embarrassing.


DocsArchive-<IP_ADDRESS>Auto archive content

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

Docs Build status updates of commit d4c023e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-08-05-02-21-26 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Linux (Kali) Android: have tried manually android# ./gradlew --rerun-tasks installDebug

even changed greeting text in index.android.js and mv it to  index.js and changed it in MainActivity.java
.setJSMainModuleName("index"), http://localhost:8081/index.js shows changed index.js  BUT
nothing changed in emulator (Genymotion) app-debug.apk - (com.firstproekt) shows initial first-time :
" Welcome to React Native! " as it was when first time

react-native run-android
adb shell pm uninstall  com.firstproekt

does not help. It seems ./gradlew again and again copies from somewhere firstly-made app-debug.apk with "Welcome to React Native" to android/app/build/outputs/apk
/android# ./gradlew --rerun-tasks installDebug
:app:preBuild UP-TO-DATE
:app:preDebugBuild UP-TO-DATE
:app:checkDebugManifest
:app:preReleaseBuild UP-TO-DATE
:app:prepareComAndroidSupportAppcompatV72301Library
:app:prepareComAndroidSupportSupportV42301Library
:app:prepareComFacebookFrescoDrawee061Library
:app:prepareComFacebookFrescoFbcore061Library
:app:prepareComFacebookFrescoFresco061Library
:app:prepareComFacebookFrescoImagepipeline061Library
:app:prepareComFacebookFrescoImagepipelineOkhttp061Library
:app:prepareComFacebookReactReactNative0120Library
:app:prepareOrgWebkitAndroidJscR174650Library
:app:prepareDebugDependencies
:app:compileDebugAidl
:app:compileDebugRenderscript
:app:generateDebugBuildConfig
:app:generateDebugAssets UP-TO-DATE
:app:mergeDebugAssets
:app:generateDebugResValues
:app:generateDebugResources
:app:mergeDebugResources
:app:processDebugManifest
:app:processDebugResources
:app:generateDebugSources
:app:processDebugJavaRes UP-TO-DATE
:app:compileDebugJavaWithJavac
:app:compileDebugNdk UP-TO-DATE
:app:compileDebugSources
:app:preDexDebug
:app:dexDebug
:app:validateDebugSigning
:app:packageDebug
:app:zipalignDebug
:app:assembleDebug
:app:installDebug
Installing APK 'app-debug.apk' on 'Google Nexus 5 - 5.0.0 - API 21 - 1080x1920 - 5.0'
Installed on 1 device.
BUILD SUCCESSFUL
Total time: 3 mins 37.504 secs

Can you try pressing the Menu button and then Reload JS?
In general, can you please use Stack Overflow to ask questions and tag them with react-native? http://stackoverflow.com/questions/tagged/react-native
Many people from the community hang out on Stack Overflow and will be able to see your question. Using Stack Overflow for questions also helps us use Github issues to keep track of bugs that need to be fixed.


Drag to reorder

See https://developer.mozilla.org/en-US/docs/Web/API/HTML_Drag_and_Drop_API/Drag_operations


Documentation for Using Checkboxes with Simple Tables?

Hello!
I am trying to utilize checkboxes within a simple table and cannot seem to find anything in the documentation about it? On this demo page here I can find great source code for simple tables and for enhanced tables that use checkboxes, but nothing for checkboxes within simple tables. Is this functionality available, and if so, could anyone provide a quick example for how to incorporate them?
Thank you in advanced for the help!

@mackpenn I don't understand, what's wrong with this demo? https://material-ui.com/demos/tables/#sorting-amp-selecting

@oliviertassinari nothing is wrong with it, I apologize if my initial question came off the wrong way. A better way to phrase the question would probably be, is there functionality for checkboxes within simple tables, like the demo above that one, or or can checkboxes only be incorporated into EnhancedTables? I'm trying to migrate from material-ui 0.20 to 1.2 without losing the checkbox functionality that was originally there.

@mackpenn You should be able to pick the checkbox demo we have, and to simplify the logic. It's the strategy I would use.


add scram-sha-256 support

Hi,
Since pg 14, scram-sha-256 is the default encryption method. I've change the postgresql_password for support the new encoding methods and change in postgresql::server::role for use this function. The default methods of the function still md5, but that create a breaking (encode doesn't have default value on my code)
I've set the username as salt chain per default.
I've test and validate on postgresql14
This PR include https://github.com/puppetlabs/puppetlabs-postgresql/pull/1132
Regards,

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@fe80: Good job!
Linked to:

https://github.com/scram-sasl/info/issues/1


”Ceuașu de Câmpie”, ”Bozed”, ”Câmpenița”, ”Culpiu” are listed in the drop-down menu

Description:
When user writes ”Ceuașu de Câmpie”, ”Bozed”, ”Câmpenița”, ”Culpiu” the locations appear in the drop-down menu next to the comune and the county which is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Ceuașu de Câmpie"

Expected results
The location appears in the drop-down menu as "Sat Ceuașu de Câmpie, MUREȘ (Ceuașu de Câmpie)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Bozed"

Expected results
The location appears in the drop-down menu as "Sat Bozed, MUREȘ (Ceuașu de Câmpie)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Câmpenița"

Expected results
The location appears in the drop-down menu as "Sat Câmpenița, MUREȘ (Ceuașu de Câmpie)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Write in the search bar "Culpiu"

Expected results
The location appears in the drop-down menu as "Sat Culpiu, MUREȘ (Ceuașu de Câmpie)".


Proof verification

This feature covers proof verification when it is necessary such as

checking proof hash anytime wanted
checking proof hash when state updates
supporting shards

Scope:

build a proof verification function that is able to check proof hash in any tree node.

This is the same issue as #259 Closing it now.


Update fedora.md

Added Fedora 26, which is served from https://download.docker.com/linux/fedora/26/ .

Proposed changes
Added Fedora 26 to list of supported versions.  It is available for download.

Unreleased project version (optional)

Related issues (optional)

Looks good, thanks @javabrett, cc @mistyhacks


Service list/online status not updated after authenticator delete

When an enrolled identity's authenticator is deleted (via a re-enroll) the desktop client does not refresh the identity's online status or service list.
Steps to reproduce:
create an identity and give it access to one or more service
enroll the identity via the desktop client
verify the service details show up in the desktop client
re-enroll the authenticator to delete the current authenticator and generate a new enrollment
At this point, the desktop client will continue to show the services for the identity and continue to show it as enrolled until the user either manually restarts the desktop client or something else triggers a refresh.

This functionality refers to legacy authentication (i.e. non-OIDC). OpenZiti is moving to a new authentication model where this issue is handled differently (through revocations) that can be issued.
Closing due to end-of-life support for legacy authentication.


Don't overwrite data in copy from req.params to res.locals

Now, we are ensuring that req.params.user not overwrite res.locals.user in usermiddleware. But probably this middleware is not the correct place to do it.
Also, we are not checking if others properties are being overwritten

do you like? @dgaubert ;)


Clean up logging

Note type of error - fatal, unexpected, retry
Log parent event

Merging per Steve


python312Packages.courlan: 1.2.0 -> 1.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.courlan is: Clean, filter and sample URLs to optimize data collection
meta.homepage for python312Packages.courlan is: https://github.com/adbar/courlan
meta.changelog for python312Packages.courlan is: https://github.com/adbar/courlan/blob/v1.3.0/HISTORY.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.0 with grep in /nix/store/1zirs193dfl9bzl2nh1c34wv2fb3jh7l-python3.12-courlan-1.3.0
found 1.3.0 in filename of file in /nix/store/1zirs193dfl9bzl2nh1c34wv2fb3jh7l-python3.12-courlan-1.3.0

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.courlan
python311Packages.trafilatura
python312Packages.courlan
python312Packages.trafilatura

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1zirs193dfl9bzl2nh1c34wv2fb3jh7l-python3.12-courlan-1.3.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 python312Packages.courlan https://github.com/r-ryantm/nixpkgs/archive/906c1b3a7c2529f3402c816810485cf838edf385.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/906c1b3a7c2529f3402c816810485cf838edf385#python312Packages.courlan

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1zirs193dfl9bzl2nh1c34wv2fb3jh7l-python3.12-courlan-1.3.0
ls -la /nix/store/1zirs193dfl9bzl2nh1c34wv2fb3jh7l-python3.12-courlan-1.3.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

4 packages failed to build:

python311Packages.trafilatura
python311Packages.trafilatura.dist
python312Packages.trafilatura
python312Packages.trafilatura.dist

4 packages built:

python311Packages.courlan
python311Packages.courlan.dist
python312Packages.courlan
python312Packages.courlan.dist

Maintainer pings
cc @jokatzke for testing.

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

8 packages built:

python311Packages.courlan
python311Packages.courlan.dist
python311Packages.trafilatura
python311Packages.trafilatura.dist
python312Packages.courlan
python312Packages.courlan.dist
python312Packages.trafilatura
python312Packages.trafilatura.dist


Deleting orphan image ?

Django does not remove image files related to model objetcs since a long time (1.2) and so we can have some orphan media files when their related object has been deleted, even more since we have mass upload feature.
Since plugins keep a hided previous version object (for published/unpublished state), we can't directly remove these files from delete object/form method, so the last way is to have a commandline to delete orphan media files that only remove files that does not belong into any model objects (published or not).

Since we use sorl-thumbnail in admin thumb and templates, we will need also to check about sorl cache store.

Fixed in v1.0.0 (yet to be released).
Worth to notice that now image fields are manage with django-smart-media, currently it clean original uploaded file but has still to see for the sorl cache, it has an issue for this.


Does this really work on an Arduino?

Hello,
This appears to be EXACTLY what we have been looking for ... but I'm a little confused by the naming and examples.
Will this run on a Arduino?  Is there a sample for the Arduino?
I see examples for other platforms ... but not the Arduino ... or am I missing something?

Hi Scott,
Please contact us me at<EMAIL_ADDRESS>Thanks
Jin
On Sat, Sep 12, 2015 at 8:28 PM, Scott C. Lemon<EMAIL_ADDRESS>wrote:

Hello,
This appears to be EXACTLY what we have been looking for ... but I'm a
little confused by the naming and examples.
Will this run on a Arduino? Is there a sample for the Arduino?
I see examples for other platforms ... but not the Arduino ... or am I
missing something?
—
Reply to this email directly or view it on GitHub
https://github.com/awslabs/aws-sdk-arduino/issues/3.

--
Keep smiling,
Jin

Could you give a public response? Thanks

I'm integrating this to Teensy 3.5 with SIM800 and initial build gives me these errors
AmazonDynamoDBClient.cpp: In member function bool AttributeValue::jsonDeserialize(MinimalString)

AmazonDynamoDBClient.cpp: 595:14: error: 'SS' was not declared in this scope
   if (!SS.jsonDeserialize(serializedSS)) {
AmazonDynamoDBClient.cpp: In member function MinimalString AttributeValue::jsonSerialize() const

AmazonDynamoDBClient.cpp: 672:35: error: 'SS' was not declared in this scope
   MinimalString pairValue = SS.jsonSerialize()
AmazonDynamoDBClient.cpp: In member function MinimalList<MinimalString> AttributeValue::getSS() const

AmazonDynamoDBClient.cpp: 738:12: error: 'SS' was not declared in this scope
   return SS
AWSClient2.cpp: In member function void AWSClient2::initSignedHeaders()

AWSClient2.cpp: 117:35: error: 'AWS_DATE_LEN2' was not declared in this scope
   len = X_AMZ_DATE_HEADER_LEN + AWS_DATE_LEN2 + AWS_TIME_LEN2

AWSClient2.cpp: 117:51: error: 'AWS_TIME_LEN2' was not declared in this scope
   len = X_AMZ_DATE_HEADER_LEN + AWS_DATE_LEN2 + AWS_TIME_LEN2
AWSClient2.cpp: In member function char* AWSClient2::createStringToSign()

AWSClient2.cpp: 133:46: error: 'HASH_HEX_LEN2' was not declared in this scope
   canonicalFormLen += SIGNED_HEADERS_LEN + HASH_HEX_LEN2 + 2

AWSClient2.cpp: 160:48: error: 'AWS_DATE_LEN2' was not declared in this scope
   int toSignLen = TO_SIGN_TEMPLATE_LEN + 2 * AWS_DATE_LEN2 + AWS_TIME_LEN2

AWSClient2.cpp: 160:64: error: 'AWS_TIME_LEN2' was not declared in this scope
   int toSignLen = TO_SIGN_TEMPLATE_LEN + 2 * AWS_DATE_LEN2 + AWS_TIME_LEN2
AWSClient2.cpp: In member function char* AWSClient2::createSignature(const char*)

AWSClient2.cpp: 174:32: error: 'HASH_HEX_LEN2' was not declared in this scope
   char* signature = new char[HASH_HEX_LEN2 + 1]()
AWSClient2.cpp: In member function void AWSClient2::initUnsignedHeaders(const char*)

AWSClient2.cpp: 207:61: error: 'AWS_DATE_LEN2' was not declared in this scope
   int len = AUTHORIZATION_HEADER_LEN + strlen(awsKeyID) + AWS_DATE_LEN2

AWSClient2.cpp: 209:15: error: 'HASH_HEX_LEN2' was not declared in this scope
   + HASH_HEX_LEN2
AWSClient2.cpp: At global scope
AWSClient2.cpp: 32:20: warning: 'CONNECTION_HEADER' defined but not used [-Wunused-variable]
   close"
Error compiling libraries


feat: Add schedule scaling possibility

Description
Additionally, it would be nice to use schedule scaling for ddb tables. (https://docs.aws.amazon.com/autoscaling/application/userguide/get-started-exercise.html)
If you want to save cost with PROVISIONED but have for example an import job that needs a lot of capacity it's the only option to not run into scaling issues.
Motivation and Context
If you want to save cost with PROVISIONED but have for example an import job that needs a lot of capacity it's the only option to not run into scaling issues.
Breaking Changes
No, as it is only an additional option.
Draft
This is just a draft of how It could be implemented. I'm open to superior solutions as I know its kinda bad practice.
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

@antonbabenko Do you maybe have time to share your opinions on that, please?

@antonbabenko Can you maybe have another look at it, please? Please let me know what you think 🙂

@antonbabenko Just a friendly reminder that I'm still looking for another review :)


[BUG] v5-dev: Segmentation violation bootstrapping cluster with LB disabled

What did you do

How was the cluster created?

k3d cluster create --config k3d-config.yml

k3d-config.yml
---
apiVersion: k3d.io/v1alpha2
kind: Simple
image: rancher/k3s:v1.20.7-k3s1
options:
  k3d:
    disableLoadbalancer: true

What did you expect to happen
Cluster bootstrapped successfully. This used to work when the latest tag was based on a 4.x release.
Screenshots or terminal output
bash-5.1# k3d cluster create --config k3d-config.yml
INFO[0000] Using config file k3d-config.yml (k3d.io/v1alpha2#simple)
WARN[0000] Default config apiVersion is 'k3d.io/v1alpha3', but you're using 'k3d.io/v1alpha2': consider migrating.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0xc87659]

goroutine 1 [running]:
github.com/rancher/k3d/v4/pkg/config.TransformSimpleToClusterConfig(0xfbb098, 0xc0000b0000, 0xfcc4e8, 0x152ce28, 0xc0004
ef318, 0x6, 0xe7eaad, 0xf, 0xe7c137, 0xb, ...)
        /app/pkg/config/transform.go:145 +0x699
github.com/rancher/k3d/v4/cmd/cluster.NewCmdClusterCreate.func2(0xc000103400, 0xc00007a6c0, 0x0, 0x2)
        /app/cmd/cluster/clusterCreate.go:188 +0x71b
github.com/spf13/cobra.(*Command).execute(0xc000103400, 0xc00007a6a0, 0x2, 0x2, 0xc000103400, 0xc00007a6a0)
        /app/vendor/github.com/spf13/cobra/command.go:860 +0x2c2
github.com/spf13/cobra.(*Command).ExecuteC(0xc000102c80, 0xc0000300b0, 0x4, 0x4)
        /app/vendor/github.com/spf13/cobra/command.go:974 +0x375
github.com/spf13/cobra.(*Command).Execute(...)
        /app/vendor/github.com/spf13/cobra/command.go:902
github.com/rancher/k3d/v4/cmd.Execute()
        /app/cmd/root.go:146 +0x65
main.main()
        /app/main.go:27 +0x25

Which OS & Architecture

docker run -it --entrypoint /bin/bash rancher/k3d:latest-dind

Which version of k3d
bash-5.1# k3d --version
k3d version v5.0.0-dev.2
k3s version v1.21.3-k3s1 (default)

Which version of docker
D:~ $ docker version
Client: Docker Engine - Community
 Version:           19.03.3
 API version:       1.40
 Go version:        go1.12.10
 Git commit:        a872fc2f86
 Built:             Tue Oct  8 01:00:44 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          20.10.7
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       b0f5bc3
  Built:            Wed Jun  2 11:54:58 2021
  OS/Arch:          linux/amd64
  Experimental:     true
 containerd:
  Version:          1.4.6
  GitCommit:        d71fcd7d8303cbf684402823e425e9dd2e99285d
 runc:
  Version:          1.0.0-rc95
  GitCommit:        b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
D:~ $ docker info
Client:
 Debug Mode: false

Server:
 Containers: 6
  Running: 1
  Paused: 0
  Stopped: 5
 Images: 51
 Server Version: 20.10.7
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runtime.v1.linux runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d71fcd7d8303cbf684402823e425e9dd2e99285d
 runc version: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.4.72-microsoft-standard-WSL2
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 24.91GiB
 Name: docker-desktop
 ID: HCCN:VYEV:3LHM:WZCQ:PUW3:23UB:GZND:LFEE:RZOR:6DGL:XCO7:5BQK
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 56
  Goroutines: 61
  System Time: 2021-07-30T10:45:06.2295384Z
  EventsListeners: 4
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: true
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
D:~ $

Hi @erikgb , thanks for opening this issue!
This is caused by a bug where the function tries to access the loadbalancer that is disabled in your config (unrelated to running in dind).
Fixed by ac527e7 just now which will be released in the next v5 dev release :+1:

Hi, I am getting this in version:
k3d version v5.4.6
k3s version v1.24.4-k3s1 (default)
Here is the output:
`
INFO[0027] Updating loadbalancer config to include new server node(s)
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xa30205]
goroutine 35 [running]:
github.com/k3d-io/k3d/v5/pkg/runtimes/docker.Docker.ReadFromNode({}, {0xf49520, 0xc00042a540}, {0xdded0a, 0x16}, 0x0)
/home/runner/work/k3d/k3d/pkg/runtimes/docker/util.go:160 +0xc5
github.com/k3d-io/k3d/v5/pkg/client.GetLoadbalancerConfig({0xf49520, 0xc00042a540}, {0xf57d68?, 0x1528898?}, 0xc0000b4100)
/home/runner/work/k3d/k3d/pkg/client/loadbalancer.go:132 +0x336
github.com/k3d-io/k3d/v5/pkg/client.UpdateLoadbalancerConfig({0xf49520, 0xc00042a540}, {0xf57d68?, 0x1528898?}, 0x1?)
/home/runner/work/k3d/k3d/pkg/client/loadbalancer.go:61 +0x17f
github.com/k3d-io/k3d/v5/pkg/client.NodeAddToCluster({0xf49520, 0xc00042a540}, {0xf57d68?, 0x1528898?}, 0xc000107ba0, 0xc0000b4100?, {0x1, 0x0, {0xc000046480, 0x2, ...}, ...})
/home/runner/work/k3d/k3d/pkg/client/node.go:261 +0x17bb
github.com/k3d-io/k3d/v5/pkg/client.NodeAddToClusterMulti.func1()
/home/runner/work/k3d/k3d/pkg/client/node.go:316 +0x57
golang.org/x/sync/errgroup.(*Group).Go.func1()
/home/runner/go/pkg/mod/golang.org/x/sync@v0.0.0-20220513210516-0976fa681c29/errgroup/errgroup.go:74 +0x64
created by golang.org/x/sync/errgroup.(*Group).Go
/home/runner/go/pkg/mod/golang.org/x/sync@v0.0.0-20220513210516-0976fa681c29/errgroup/errgroup.go:71 +0xa5
`


element-web: 1.7.31 -> 1.7.32

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/vector-im/element-web/releases.
meta.description for element-web is: "A glossy Matrix collaboration client for the web"
meta.homepage for element-web is: "https://element.io/"
meta.changelog for element-web is: "https://github.com/vector-im/element-web/blob/v1.7.32/CHANGELOG.md"
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

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

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

found 1.7.32 with grep in /nix/store/zhnalkrc93yaxyjw1af4nhk99955wy56-element-web-1.7.32

found 1.7.32 in filename of file in /nix/store/zhnalkrc93yaxyjw1af4nhk99955wy56-element-web-1.7.32

directory tree listing: https://gist.github.com/3ca7c6426037290e5ebbf9db69860e2b

du listing: https://gist.github.com/f5ff755699a9846d916d4e4163f9032e

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

671 total rebuild path(s)

242 package rebuild(s)

242 x86_64-linux rebuild(s)
211 i686-linux rebuild(s)
51 x86_64-darwin rebuild(s)
167 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
element-desktop
gitaly
gitlab
gitlab-ee
gitlab-workhorse
glasgow
home-assistant
inkcut
inkscape-extensions.inkcut
lima
linuxPackages_lqx.acpi_call
linuxPackages_lqx.akvcam
linuxPackages_lqx.amdgpu-pro
linuxPackages_lqx.anbox
linuxPackages_lqx.apfs
linuxPackages_lqx.asus-wmi-sensors
linuxPackages_lqx.batman_adv
linuxPackages_lqx.bbswitch
linuxPackages_lqx.bcc
linuxPackages_lqx.bpftrace
linuxPackages_lqx.broadcom_sta
linuxPackages_lqx.can-isotp
linuxPackages_lqx.chipsec
linuxPackages_lqx.cpupower
linuxPackages_lqx.cryptodev
linuxPackages_lqx.ddcci-driver
linuxPackages_lqx.digimend
linuxPackages_lqx.dpdk-kmods
linuxPackages_lqx.ena
linuxPackages_lqx.evdi
linuxPackages_lqx.facetimehd
linuxPackages_lqx.fwts-efi-runtime
linuxPackages_lqx.gcadapter-oc-kmod
linuxPackages_lqx.hid-nintendo
linuxPackages_lqx.hyperv-daemons
linuxPackages_lqx.intel-speed-select
linuxPackages_lqx.isgx
linuxPackages_lqx.it87
linuxPackages_lqx.ixgbevf
linuxPackages_lqx.jool
linuxPackages_lqx.kernel
linuxPackages_lqx.lttng-modules
linuxPackages_lqx.mba6x_bl
linuxPackages_lqx.mbp2018-bridge-drv
linuxPackages_lqx.mwprocapture
linuxPackages_lqx.mxu11x0
linuxPackages_lqx.ndiswrapper
linuxPackages_lqx.netatop
linuxPackages_lqx.nvidia_x11
linuxPackages_lqx.nvidia_x11_beta

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zhnalkrc93yaxyjw1af4nhk99955wy56-element-web-1.7.32 \
  --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 element-web https://github.com/r-ryantm/nixpkgs/archive/3cfd0dc63d4a7d5015125c08a3ec2350347a3a54.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/zhnalkrc93yaxyjw1af4nhk99955wy56-element-web-1.7.32
ls -la /nix/store/zhnalkrc93yaxyjw1af4nhk99955wy56-element-web-1.7.32/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @ma27 @fadenb @mguentner @ekleog @ralith @mjlbach @dali99 for testing.

https://matrix.to/#/!bijaLdadorKgNGtHdA:matrix.org/$1NYar9Nx0fxF0HEIwCJN5DJ_3IG1N8BGZuZOTIw5cMg?via=matrix.org&via=mozilla.org&via=privacytools.io:

If non-element official build channel take slightly longer to update, don't be too alarmed: there's a minor change to the build process.

Broken at run-time.


Support item expanding and collapsing

Issue #33
Describe your changes
This is a WIP of an implementation to support nested items (i.e. nested CellViewModels), enabled by NSDiffableDataSourceSectionSnapshots.
What's been done so far

As discussed in the issue, CellViewModel now includes a children property, which allows us to provide an array of AnyCellViewModels. Each of those can have children, and so on.
Created DiffableSectionSnapshot, which is a typealias for NSDiffableDataSourceSectionSnapshot. The ability to append items to other items is only supported through section snapshots. The logic to do so is recursive - appending the items for each top level cell, then for each of those going into all of their children, and so on.
Inside DiffableDataSource, I added a check to see if we have at least one section with at least one cell that has non-empty children. If that's the case, we split off into creating section snapshots. Otherwise, we proceed with the existing standard snapshot approach.

I believe we'll want the same completion logic, so I tried to separate that into a method so as to not repeat all of the comments in there.

The final commit is purely for demo purposes, which implements a rough version of some things described below that are still needed + in order to be able to show a quick demo in the example app.

https://github.com/user-attachments/assets/e4fb5fb1-0546-4861-bc5e-cb2f9538ab2c

What still needs to be done

We need to figure out an approach for reconfiguring items for the section snapshots. Section snapshots don't have the same reconfigure APIs as standard snapshots, so my thinking is we'll need to apply all of the section snapshots, then at the end grab the current full snapshot via self.snapshot(), then reconfigure from there.
We'll need additional recursive logic in CollectionViewModel to ensure that we're referencing the snapshot's visibleItems when we're grabbing a CellViewModel for a given index path. The index paths all change when you expand/collapse an item, so we have to account for that.
Example app work - not sure if want that in this PR or a separate one.
Perhaps some additional/updated comments
Tests

One other note - this warning appears whenever collapsing or expanding an item, and then any time the collection view updates after that. Only way I've been able to "fix" it is by disabling diffing on a background queue, but not sure why.

Related to the above, found this super interesting response from Apple:

Currently, you do need to apply snapshots on the main queue when using certain features (such as outline disclosure expand/collapse support, or interactive item reordering) where the user is directly manipulating the collection view and an immediate UI update is expected in response.

Also goes on to say that "applying snapshots from a background queue is almost always unnecessary in general."
https://forums.developer.apple.com/forums/thread/757270


workspaceContains activation event does not fire when debugging the extension host

Testing #27483

VSCode Version: Code - Insiders 1.13.0-insider (afe47dc84467b487ce0079ff72f55e7ef4f7ebca, 2017-05-30T09:59:32.734Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author
Version

vetur
octref
0.6.10

java
redhat
0.4.0

todotasks
sandy081
0.4.0

kustovscode
seanmcbreen
0.0.4

code-spell-checker
streetsidesoftware
1.1.0

I could not get this to work.  I did a very simple test of changing the boiler plate hello world package.json to:
    "activationEvents": [
        "onCommand:extension.sayHello",
        "workspaceContains:**/*.md"
    ],

I also tried
    "activationEvents": [
        "onCommand:extension.sayHello",
        "workspaceContains:**/*.kusto"
    ],

I then ran this in a folder that had both .md and a .kusto files.  I did not manage to activate the extension via the presence of these files and as a result did not get the Hello World info message.
My code compiled and I could get to the message via the command.  I could also get this to work with e traditional activation event:
    "activationEvents": [
        "onCommand:extension.sayHello",
        "workspaceContains:README.md"
    ],

@seanmcbreen I'm sorry I don't know what could be wrong with your setup. Perhaps share the extension as a zip and I can take a look. Here is what I have just tried and works for me:

I create C:\Users\Alex\.vscode-insiders\extensions\test\package.json:

{
    "publisher": "alex",
    "name": "test",
    "version": "0.0.0",
    "engines":{
        "vscode": "^1.0.0"
    },
    "activationEvents": [
        "onCommand:extension.sayHello",
        "workspaceContains:**/*.md"
    ],
    "main": "./main.js"
}

I create C:\Users\Alex\.vscode-insiders\extensions\test\main.js:

exports.activate = function() {
    console.log('Hello world, I am activated');
};

I then open with the Insiders a folder that contains a subfolder called test and a file called test.md and the extension activates for me.
Can you perhaps share your entire extension, perhaps there is something else to it?

Is it possible you are debugging your extension and that is the root cause?

Yes I was debugging - that said I can get it to work now... YAY

@seanmcbreen Thanks for your reply!
We need to figure out why debugging the extension host makes the glob search process not work, since many other extension authors might run into it.

The root cause is:

we launch the extension host with execArgv: --debug-brk=XXX
out-of-the box, nodejs will inherit process.execArgv when forking a process
so the search process that looks for glob files would also launch with --debug-brk=XXX
the search process would not error, but would also not complete, resulting in the activation event not being generated

The fix is to start the search process with fresh execArgv such that it doesn't start in debug-brk mode when the extension host is started in debug-brk mode

Verified, but the extension isn't activated in this case:

package.json has "workspaceContains:**/*.md"
Open a workspace that doesn't have a .md file
Add a .md file

Is it expected to be?

@roblourens Your use case makes sense, but please create a separate feature request. The workspaceContains always had the semantics of what is in the folder when the folder is opened.


Creating data controller for the November release using kubectl

Creating a data controller using native kubernetes tools (kubectl).  Using the guidelines from the docs site Create Data Controller. I fail  when setting up the webhook part.
Bug
When creating the webhook job for the November release the job is targeting a script that does not exist and changing this yaml to the correct one "/opt/webhook/create-and-deploy-webhook.sh" with required arguments namespace and name will produce another error about permissions for the services account.
Log information
| INFO | Checking for existing webhook...
| ERROR | An error occurred when checking for an existing webhook...
| ERROR | Debug Info:
{ "kind": "Status", "apiVersion": "v1", "metadata": { }, "status": "Failure", "message": "mutatingwebhookconfigurations.admissionregistration.k8s.io "arcdata.microsoft.com-webhook-arc" is forbidden: User "system:serviceaccount:arc:sa-arc-webhook-job" cannot get resource "mutatingwebhookconfigurations" in API group "admissionregistration.k8s.io" at the cluster scope", "reason": "Forbidden", "details": { "name": "arcdata.microsoft.com-webhook-arc", "group": "admissionregistration.k8s.io", "kind": "mutatingwebhookconfigurations" }, "code": 403 }

I've added the following to Role : role-arc-webhook-job

apiGroups: ["*"]
resources: ["secrets"]
resourceNames: ["arc-webhook-secret"]
verbs: ["get"]

It currently has delete, not sure if it is needed or not
This solved my issue together with the change of the script path.

@aheden can you please verify the new release? @twright-msft pushed the changes

Hi,
The there were some issues with the clusterrole: cr-arc-webhook-job
From:
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: cr-arc-webhook-job
rules:

apiGroups: ["admissionregistration.k8s.io"]
resources: ["mutatingwebhookconfigurations"]
resourceNames: ["arcdata.microsoft.com-{{namespace}}"]
verbs: ["delete"]
apiGroups: ["admissionregistration.k8s.io"]
resources: ["mutatingwebhookconfigurations"]
verbs: ["create"]

To
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: cr-arc-webhook-job
rules:

apiGroups: ["admissionregistration.k8s.io"]
resources: ["mutatingwebhookconfigurations"]
resourceNames: ["arcdata.microsoft.com-webhook-{{namespace}}"]
verbs: ["delete", "get"]
apiGroups: ["admissionregistration.k8s.io"]
resources: ["mutatingwebhookconfigurations"]
verbs: ["create"]
- apiGroups: ["*"]
resources: ["namespaces"]
resourceNames: ["{{namespace}}"]
verbs: ["patch"]

Hey @aheden, we now have a merged December release. Do you mind re-deploy and reporting back?

I've submitted a PR to update to what @aheden commented and tested end:end.  Should be good to go now.


cmd/go2go: newtype of constraint causes endless recursion

What version of Go are you using (go version)?

$ go version
go version devel +34f76220c3 Sat Jul 4 04:55:49 2020 +0000 windows/amd64

Does this issue reproduce with the latest release?
n/a
What operating system and processor architecture are you using (go env)?

Go2go playground
windows/amd64

What did you do?
https://go2goplay.golang.org/p/mSgtHY8Dv7v
What did you expect to see?
Successful compilation or error like
prog.go2:3:6: illegal cycle in declaration of K
prog.go2:3:6: 	K refers to
prog.go2:3:6: 	K

What did you see instead?
Partial stack trace:
goroutine 1 [running]:
go/types.(*subster).func_(0xc020161780, 0xc0000411d0, 0x0)
	G:/workspace/exprm/go/src/go/types/subst.go:489 +0x165 fp=0xc020161370 sp=0xc020161368 pc=0xe6d265
go/types.(*subster).funcList(0xc020161780, 0xc000006048, 0x1, 0x1, 0x0, 0x0, 0x0, 0x0)
	G:/workspace/exprm/go/src/go/types/subst.go:503 +0xa5 fp=0xc0201613e0 sp=0xc020161370 pc=0xe6d325
go/types.(*subster).typ(0xc020161780, 0xff10c0, 0xc00010a080, 0x0, 0x0)
	G:/workspace/exprm/go/src/go/types/subst.go:302 +0x177e fp=0xc020161758 sp=0xc0201613e0 pc=0xe6bede
go/types.(*Checker).subst(0xc0001045a0, 0x4a, 0xff10c0, 0xc00010a080, 0xc0078aa520, 0x1, 0xc0078aa520)
	G:/workspace/exprm/go/src/go/types/subst.go:230 +0x12b fp=0xc0201617b0 sp=0xc020161758 pc=0xe6a6cb
go/types.(*Checker).instantiate(0xc0001045a0, 0x45, 0xff1200, 0xc00007e240, 0xc0000325e0, 0x1, 0x1, 0xc00000a520, 0x1, 0x1, ...)
	G:/workspace/exprm/go/src/go/types/subst.go:139 +0x2aa fp=0xc0201619a8 sp=0xc0201617b0 pc=0xe6974a
go/types.(*instance).expand(0xc00003e480, 0x0, 0x0)
	G:/workspace/exprm/go/src/go/types/type.go:938 +0xb1 fp=0xc020161a18 sp=0xc0201619a8 pc=0xe70611
go/types.(*instance).Named(0xc00003e480, 0x8)
	G:/workspace/exprm/go/src/go/types/type.go:929 +0x32 fp=0xc020161a40 sp=0xc020161a18 pc=0xe70492
go/types.(*Named).Under(0xc00007e2d0, 0x0, 0x0)
	G:/workspace/exprm/go/src/go/types/decl.go:498 +0x6e fp=0xc020161c10 sp=0xc020161a40 pc=0xe3b28e
go/types.(*Named).TypeParam(0xc00007e2d0, 0x0)
	G:/workspace/exprm/go/src/go/types/type.go:791 +0x32 fp=0xc020161c38 sp=0xc020161c10 pc=0xe6f5d2
go/types.(*Checker).instantiate(0xc0001045a0, 0x45, 0xff1200, 0xc00007e240, 0xc0000325e0, 0x1, 0x1, 0xc00000a520, 0x1, 0x1, ...)
	G:/workspace/exprm/go/src/go/types/subst.go:150 +0x84f fp=0xc020161e30 sp=0xc020161c38 pc=0xe69cef
go/types.(*instance).expand(0xc00003e480, 0x0, 0x0)
	G:/workspace/exprm/go/src/go/types/type.go:938 +0xb1 fp=0xc020161ea0 sp=0xc020161e30 pc=0xe70611
go/types.(*instance).Named(0xc00003e480, 0x8)
	G:/workspace/exprm/go/src/go/types/type.go:929 +0x32 fp=0xc020161ec8 sp=0xc020161ea0 pc=0xe70492
go/types.(*Named).Under(0xc00007e2d0, 0x0, 0x0)
	G:/workspace/exprm/go/src/go/types/decl.go:498 +0x6e fp=0xc020162098 sp=0xc020161ec8 pc=0xe3b28e
go/types.(*Named).TypeParam(0xc00007e2d0, 0x0)
	G:/workspace/exprm/go/src/go/types/type.go:791 +0x32 fp=0xc0201620c0 sp=0xc020162098 pc=0xe6f5d2
go/types.(*Checker).instantiate(0xc0001045a0, 0x45, 0xff1200, 0xc00007e240, 0xc0000325e0, 0x1, 0x1, 0xc00000a520, 0x1, 0x1, ...)
	G:/workspace/exprm/go/src/go/types/subst.go:150 +0x84f fp=0xc0201622b8 sp=0xc0201620c0 pc=0xe69cef
go/types.(*instance).expand(0xc00003e480, 0x0, 0x0)
...

Hi @tdakkota, thanks for filing this.  There is some chance what you found is similar to Crash 22 in https://github.com/golang/go/issues/39634#issuecomment-647167060.
Crash 22 there also seemed to be endless recursion, and comparing the partial trace you posted here with the call stack there, they both seem to follow a similar pattern of:
go/types.(*instance).expand-> instantiate -> TypeParam -> Under -> Named -> expand -> instantiate -> ...
That said, I'm not sure if they are the same underlying problem, and I think you are more likely to have a better guess than me whether or not they are the same.  ;-)
cc @griesemer

I have a question, what this declaration does mean?
type comp(type T comparable) T

type K comp(K)

Is it similar to
type NewK comp(OldK) // OldK is comparable

or to
type K comparable

?
Thanks.

This was fixed in the type checkers with the above CL.
For
package p

type comp[T comparable] T
type K comp[K] // becomes 'type K K', where K is comparable

the reported error is now:
$ go tool compile -G=3 x.go2
x.go2:4:6: invalid recursive type K
	x.go2:4:6: K refers to
	x.go2:4:8: comp refers to
	x.go2:4:6: K


Mandd/ensemble functionsfixes

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
Closes #206
Closes #198
What are the significant changes in functionality due to this change request?

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code. ok
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts). ok
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details. ok
[x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass. they do
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True. test added
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync. n/a
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done. #206 #198
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added? n/a

Check list passed...
PR can be accepted...


Return git common dir to address worktree issues

[x] All tests passed. If this feature is not already covered by the tests, I added new tests.
[x] All static analysis checks passed.
[x] This pull request is on the dev branch.
[x] I used gofmt for formatting the code before submitting the pull request.

Fixes jfrog/jfrog-cli#1531

cc: @Robert-Morgowicz @ schmidtl25


Markup cells invisibile when reopening files

Issue Type: Bug

Open my endgame notebook
Scroll to bottom
Close the editor
Open through quick pick again

VS Code version: Code - Insiders 1.65.0-insider (Universal) (32456dc9e7d3194a94dd3ee0322ccf47e461d09c, 2022-02-23T05:27:54.628Z)
OS version: Darwin x64 21.3.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 3

Memory (System)
32.00GB (0.09GB free)

Process Argv
--enable-proposed-api ms-vscode.vscode-notebook-history --enable-proposed-api vscode.notebook-editing --enable-proposed-api vscode.vscode-test-resolver --enable-proposed-api donjayamanne.kusto --enable-proposed-api donjayamanne.jupyterpowertools --enable-proposed-api rebornix.better-jupyter-errors --enable-proposed-api rchiodo.jupyter-tools --crash-reporter-id 1a907bbd-fa02-4595-81e0-63e1648afb31

Screen Reader
no

VM
0%

These items are not actually hidden but have the wrong top offset in this case

This seems to be caused by createMarkupPreview being invoked when the hidden cell is scrolled into view:
https://github.com/microsoft/vscode/blob/1d618b2df1cf08f0e3ab706353f0a8f6f1424795/src/vs/workbench/contrib/notebook/browser/notebookEditorWidget.ts#L2522
For some reason, this._list.getAbsoluteTopOfElement returns a wrong cell offset. In the case here, it returns a offset of something like 2600 while the actual offset is closer to 6600

I think this code has always been computing the wrong offset. We just don't always see it as showMarkupPreview skips sending an update if the cell was already visible:
https://github.com/microsoft/vscode/blob/6db11fbf331e16eb59a7d81ec5905705331ab433/src/vs/workbench/contrib/notebook/browser/view/renderers/backLayerWebView.ts#L1035
@rebornix I pushed a potential fix copied from some other code. Can you please take a quick look and let me know if this looks ok? I think we should try consolidating this logic instead of having it copied in multiple places but I don't know enough about this area of the code  to say how to do this


Refactoring #3, #4, and #7.

[x]  refactor html and css

[x]  use static assets for hobby images

[x]  change our root path to render "main.jinja"

I also made our headings have a rainbow animation, so it won't look too plain for right now.

Closes #13.

Looks great to me! I tried it out and love the rainbow animations.

I just discovered that the way I was referencing my images were not the best practice. I will update it when I get home later today.

Looks Great!


Client doesn't verify GitHub proof

Steps to reproduce

Edit keybase.md signature or payload
Verify proof from client
Proof still shows as valid

Details
I tried tampering with my keybase.md gist because I wanted to see how the client reports that a signature is invalid.
At first I only changed a few characters in the payload. Proof still shows as valid.
I tried using keybase id -s mbloms to make sure that the proof wasn't cached. Still valid.
Then I tried changing the signature. Still valid.
I tried squashing the history so that the original valid signature is not even in the git history. Still valid.
Now I removed the payload entierly and replaced the signature with null.
Still keybase says it's valid. It doesn't matter if I use my phone or my computer.
Is this a bug or why does it still think the proof is valid?
$ keybase id -s mbloms
- INFO Identifying mbloms
OK public key fingerprint: C708 0729 DBD7 5119 A53D 18AC 7F64 B7A3 F7F6 819E
BTC  bitcoin 1M5ZRjyqJDjVen3Yb3joZp24j2o5Qai84R
XLM  Stellar GDDUEQJUIHVJQDZZDK7WAXMJW4ZOFUVE7TQXG7LFWTQCHL5JNEKLLWP5 (mbloms*keyb
ase.io)
OK "chawlindel" on reddit: https://www.reddit.com/r/KeybaseProofs/comments/dcr0zb/
my_keybase_proof_redditchawlindel_keybasembloms/
OK "mbloms" on github: https://gist.github.com/6e96c7f6e448513bc15fa64947af2868
OK "mbloms" on twitter: https://twitter.com/mbloms/status/1176623629813071873

$ keybase id mbloms
- INFO Identifying mbloms
OK public key fingerprint: C708 0729 DBD7 5119 A53D 18AC 7F64 B7A3 F7F6 819E
BTC  bitcoin 1M5ZRjyqJDjVen3Yb3joZp24j2o5Qai84R
XLM  Stellar GDDUEQJUIHVJQDZZDK7WAXMJW4ZOFUVE7TQXG7LFWTQCHL5JNEKLLWP5 (mbloms*keyb
ase.io)
OK "mbloms" on github: https://gist.github.com/6e96c7f6e448513bc15fa64947af2868 [c
ached 2019-12-08 17:46:36 CET]
OK "chawlindel" on reddit: https://www.reddit.com/r/KeybaseProofs/comments/dcr0zb/
my_keybase_proof_redditchawlindel_keybasembloms/ [cached 2019-12-08 17:46:36 CET]
OK "mbloms" on twitter: https://twitter.com/mbloms/status/1176623629813071873 [cac
hed 2019-12-08 17:46:36 CET]

I stumbled upon this and was curious as well, so I MITM'd the keybase id traffic. Apparantly it's pulling down https://gist.githubusercontent.com/mbloms/6e96c7f6e448513bc15fa64947af2868/raw/ed3adc55398e85e425f03c9c38bfe81f6cdb5eb6/keybase.md which is your old revision that does have the signature in it. That's probably the underlying reason why keybase handles the changed gist, because under the hood it's using whichever revision the file is at when you first made the proof.

Interesting. That explains why it didn't break when I force pushed over my gist. Weird that GitHub doesn't delete the original blob after I force push over it