clarify meaning of default if minOccurs>1

Suppose an Element has minOccurs=2 and a default value. Should this be allowed?
Either:

the EBML Reader should insert enough copies of the Element to satisfy the minOccurs with default values as needed. Or.
We could say that 'default' values are only valid when minOccurs equals 1.

I prefer 2.

I also prefer 2.

Currently we don't have a case of minOccurs > 1, and it hadn't been our intention to allow that in the first place. Remember, minOccurs=1 was originally the mandatory flag.
I don't see a case where minOccurs > 1 makes sense, but then again, we allowed it…
Oh well. I'm either for disallowing minOccurs > 1 or for your option 2.

minOccurs comes from the analogy with XML. But XML has no default value like we do. Maybe we should bring back the mandatory flag and explain it's similar to minOccurs = 0|1 in XML ?

XML does have default values like EBML, but they are only for attributes which may only occur once within an element. It seems a bit controversial since the XML Document is not semantically understood alone but needs the XML Schema to be interpreted.
Although we have no minOccurs>1 use case, I don't suppose we should force other EBML adopters to have this limit. There is some writing about the zero-one-infinity rule that explains design exceptions. If someone makes an EBML Document Type to describe triangles a minOccurs=3 may make sense.
I think saying 'default' values are only valid when minOccurs=1 is the solution most analogous to XML since XML only uses defaults for attributes which infer that more than one occurrence is not possible.

I don't really see a good case for minOccurs=2 or more. Is it ever used in
XML? Maybe if we could think of some cases (not Matroska related) we would
know if a default value makes sense or not. I don't think forcing a
restriction just because we can is a good reason to add this limitation.
Maybe saving a matrix in a linear way could be a good example of minOccurs
= maxOccurs = 9. A default value of 0 would make sense too. The problem is
when you don't write an element because it's default, is it at the
beginning or the end?
Another ensemble of X elements not ordered could be stored linearly too. If
you write only Y elements that means the other X-Y are the default values.
That could save a lot of space in scientific samples.
Le 18 sept. 2016 16:13, "Dave Rice"<EMAIL_ADDRESS>a écrit :

XML does have default values like EBML, but they are only for attributes
which may only occur once within an element. It seems a bit controversial
since the XML Document is not semantically understood alone but needs the
XML Schema to be interpreted.
Although we have no minOccurs>1 use case, I don't suppose we should force
other EBML adopters to have this limit. There is some writing about the
zero-one-infinity rule that explains design exceptions. If someone makes an
EBML Document Type to describe triangles a minOccurs=3 may make sense.
I think saying 'default' values are only valid when minOccurs=1 is the
solution most analogous to XML since XML only uses defaults for attributes
which infer that more than one occurrence is not possible.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Matroska-Org/ebml-specification/issues/95#issuecomment-247850023,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAoJNaoItJ8SHySO90G0oixZ-8-FL-dYks5qrUcHgaJpZM4J6JDY
.

Yes, you may have minOccurs=2 in a valid XML.
The default value [in XML] for both minOccurs and maxOccurs is 1.


Error when describing multiple array method names like #[] and #[]?

Hello,
Spec2 seems to mangle "#[]" and "#[]?" into the same module name  Spec2___Root::Spec2__Array::Spec2___.
This results in the error  already initialized constant Spec2___Root::Spec2__Array::Spec2___::SPEC2_FULL_CONTEXT
Platform Crystal 0.19.4 (2016-10-07) on Linux, Spec2 at eef5144d86f3aadf95811ffc0450be389db36fed
Code snippet
require "spec2"

Spec2.describe Array do
  describe "#[]?" do # Each on their own is fine
    it "returns nil" do
      expect(([ 3, 4 ])[2]?).to be_nil
    end
  end

  describe "#[]" do
    it "raises IndexError" do
      expect{ ([ 3, 4 ])[2] }.to raise_error IndexError
    end
  end
end

Note: This also happens with #[]=
Thanks

I guess, we ought to transform special symbols into some meaningful words. For example #[]= will become: __sharp____openbrace____closebrace____equals__. Are you up for making a pull request?
Also, it can be worked around in your code with specifying some sort of conceptual description in your describe after the name of the method:
describe "#[] - index accessing operator" do
  # ..
end

I guess, we ought to transform special symbols into some meaningful words. For example #[]= will become: __sharp____openbrace____closebrace____equals__. Are you up for making a pull request?
Also, it can be worked around in your code with specifying some sort of conceptual description in your describe after the name of the method:
describe "#[] - index accessing operator" do
  # ..
end


install itself is failing

pip install lightgbm
Exception: Please install CMake and all required dependencies first
python 3.9
macOS

Thanks for using LightGBM. This is not enough information for us to help you.
Based only on what you've provided, I'm guessing that you tried running
pip install lightgbm

And got this error.

Please install CMake and all required dependencies first

Try the following.
brew install cmake
pip install lightgbm

If that doesn't work, we need more information.

exactly what commands you ran to install lightgbm
output of cmake --version
output of conda info if using conda

poetry add cmake
->
`
The following packages are already present in the pyproject.toml and will be skipped:
• cmake
`
poetry add lightgbm
->
`Exception: Please install CMake and all required dependencies first
The full version of error log was saved into /Users/user_name/LightGBM_compilation.log
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for lightgbm

Failed to build lightgbm
ERROR: Could not build wheels for lightgbm, which is required to install pyproject.toml-based projects
`
cmake version 3.24.2
`
Poetry
Version: 1.2.2
Python:  3.9.6
Platform:   darwin
OS:         posix
`

The full version of error log was saved into /Users/user_name/LightGBM_compilation.log

Did you check that file? It should contain more information about why the wheel can't be built.

  Could NOT find OpenMP_C (missing: OpenMP_C_FLAGS OpenMP_C_LIB_NAMES)

could the cmake error not be displayed while I am installing lightgbm, the bottleneck of having to go to another directory is inconvenient.
plus it is showing me all the old errors, I would only want to see the installation errors of the current pip install

Based on the information you've provided, it looks like after following the other error messages you've resolved missing OpenMP and are now facing exactly the same issue as https://github.com/microsoft/LightGBM/issues/5269#issuecomment-1283164740.
Because no free continuous integration (CI) services support M1 Mac (ARM) machines and because none of this project's active maintainers have free access to an M1 Mac machine, it's very difficult for LightGBM to test support for compiling on that architecture. You can try the other possibilities mentioned in #5269, such as installing lightgbm from conda-forge as suggested by https://github.com/microsoft/LightGBM/issues/5269#issuecomment-1259295645.
We understand that this is frustrating for M1 Mac users but it's unlikely to change unless:

a free CI service allows frequent testing on M1 Mac machines
one or more contributors with access to M1s submit patches that add support for compiling LightGBM on the arm64 Macs

could the cmake error be displayed while I am installing lightgbm. the bottleneck of having to go to another directory is inconvenient

It is an intentional choice that all stderr / stdout from compilation isn't pulled back into the output stream of pip install lightgbm.
If you feel strongly that lightgbm should support that, please open a separate feature request issue explaining why you believe that behavior would be preferable to the current state where logs are dumped to a file.

plus could you do a gcc check, I had to find the gcc version manually, could this directly be suggested while installation
...
could do it for more steps also

lightgbm's Python package is very unlikely to support an interactive installation mode like that.

many installations of the Python package are non-interactive (e.g. in container builds or automated processes running on remote servers)

an interactive installation guide like that wouldn't be desirable in those settings

this project supports a wide range of compilers and operating systems, making support for such an interface likely very expensive in terms of development time and maintainers' attention
lightgbm would prefer not to be opinionated about how users install build toolchain tools, except in situations where absolutely necessary

for example, you may want to use pip to install cmake but others will prefer conda, brew (macOS), asdf, directly downloading cmake official releases, and other options

If you feel very strongly that such an interactive installation mode would be worth the effort, please open a separate feature request issue explaining why you think it would be valuable and, in as much detail as possible, how you'd like it to work.

currently this works,
pip install lightgbm --install-option=--nomp

I will create the required issues


[Bug]: computeRMS fails to calculate stderr when masked arrays are given.

FAQ check

[X] Yes, I checked the FAQ and my question has not been addressed.

Contact Details
No response
Instrument
Light curve fitting (Stages 4-6)
What happened?
After masking outliers in S4, computeRMS in S5 will return an invalid result from np.ma.std(data). This means the stderr returned from computeRMS will also be a masked array of invalid values, and will cause the Allan plot made in S5 to be blank. @taylorbell57 suggests this only happens when all values are masked for a certain bin, but I've only been working with single-bin lightcurves and not all the values have been masked (I did a 10-sigma clipping step in S4, and there was good data there).
Here's a look at a bad Allan plot:

And here's a look at a working Allan plot:

The only difference is whether I ran the sigma clipping step in S4.
Error traceback output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

What simulated dataset is this for, and what branch is your code up-to-date with?

This was the full NIRSpec dataset, and my code is up to date with main as of this morning.

Can you send me your S4's Meta_Save.dat file and S5's .ecf and .epf files by email so I can reproduce the error locally?

Yep. I'll send those when I get out of some meetings.

I encountered a related problem in S5 when flagging outliers in S4. I managed to fix it, but I think we'll continue to see problems like this unless we take the more drastic step of moving away from masked arrays in S5. It should be simple to, at the start of S5, copy all good data points into a new array. At that point, there's no point to keeping the masked data.


gnome.hitori: 3.38.1 -> 3.38.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for gnome.hitori is: "GTK application to generate and let you play games of Hitori"
meta.homepage for gnome.hitori is: "https://wiki.gnome.org/Apps/Hitori"
meta.changelog for gnome.hitori is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

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

Warning: no invocation of /nix/store/3ds2w39cj3kipkz099ksqn2nv6vgjs2l-hitori-3.38.2/bin/hitori had a zero exit code or showed the expected version

Warning: no invocation of /nix/store/3ds2w39cj3kipkz099ksqn2nv6vgjs2l-hitori-3.38.2/bin/.hitori-wrapped had a zero exit code or showed the expected version

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

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

found 3.38.2 with grep in /nix/store/3ds2w39cj3kipkz099ksqn2nv6vgjs2l-hitori-3.38.2

found 3.38.2 in filename of file in /nix/store/3ds2w39cj3kipkz099ksqn2nv6vgjs2l-hitori-3.38.2

directory tree listing: https://gist.github.com/e25845deb04a0216301a9f37c65e8fb1

du listing: https://gist.github.com/8f365e56947c833e5abfe99022207e02

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

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
gnome.hitori

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3ds2w39cj3kipkz099ksqn2nv6vgjs2l-hitori-3.38.2 \
  --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 gnome.hitori https://github.com/r-ryantm/nixpkgs/archive/c9624410211b192ea67c243ed58e0b43e8ea8758.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/3ds2w39cj3kipkz099ksqn2nv6vgjs2l-hitori-3.38.2
ls -la /nix/store/3ds2w39cj3kipkz099ksqn2nv6vgjs2l-hitori-3.38.2/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

1 package built:

gnome.hitori

Maintainer pings
cc @hedning @jtojnar @dasj19 @maxeaubrey for testing.

Result of nixpkgs-review pr 124532 at c9624410 run on x86_64-linux 1

1 package built successfully:

gnome.hitori

1 suggestion:

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/desktops/gnome/games/hitori/default.nix:63:5:
   |
63 |     license = licenses.gpl2;
   |     ^


ERROR [internal] load metadata for mcr.microsoft.com/windows/servercore:ltsc2019

Steps to reproduce:
docker build -t mediapipe_unity:windows . -f docker/windows/x86_64/Dockerfile
Any idea what the reason of this issue might be ?

Maybe same as #278


governance: public list of roles on sktime

based on some discussions, it's not easy to find out who does what on sktime - for instance, CC membership is on the CC repo, CoC membership is in the CoC, and core contributors are listed nowhere in particular (which makes that information not findable).
This PR remedies the problem of findability by adding a ROLES.md to the repository root, as a single source of truth.
I've filled it in to the best of my current knowledge.

@fkiraly I think it also makes sense to list current Summer program participants (and eventually have a past Summer program participants section). What do you think?
Markus and I had also been thinking it would be good to add this as a sub-file in the "About" section in our online docs. One benefit in the short-run is during events like a code or the upcoming docsprint we can let people know about that section of the documentation so they can look up relevant people to ask questions.

Markus and I had also been thinking it would be good to add this as a sub-file in the "About" section in our online docs. One benefit in the short-run is during events like a code or the upcoming docsprint we can let people know about that section of the documentation so they can look up relevant people to ask questions.

Yes, sure! You can easily embed md there, so would be fine with this - I'm not familiar enough with the new webpage back-end though to do that in this PR.

@fkiraly I think it also makes sense to list current Summer program participants (and eventually have a past Summer program participants section). What do you think?

That would make sense, my problem is that I don't have the full list of mentees. Someone else could add it?

I'd prefer to declutter the root directory and instead add this to the website as describe by @RNKuhns above, see https://github.com/alan-turing-institute/sktime/issues/1204 and https://github.com/alan-turing-institute/sktime/issues/1159.
For the website, rst is preferred, md doesn't support cross-references.

For the website, rst is preferred, md doesn't support cross-references.

I don't mind either way, I just prefer having it above not having it in any form.
We should also think about findability - it should be a one-click user journey from the landing page rather than having to click through through the docs.
What would the location and "click distance" be for your proposed location?

Closed in favour of #1328


Update Set-SFTPFolder.md

Example says -localFile and not -localFolder.

Example says -localFile and not -localFolder.


Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub

Downloading the binary file without Docker & running gives an error
❯ slashbase
Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub

mostly because the release binaries has an indirect dependency on go-sqlite3 which in turn needs to be built with CGO
Steps to reproduce

download slashbase binary from release page (linux_amd64.zip)
add slashbase to path or move to ~/.local/bin
run slashbase & see the error

Possible fix
Add 'CGO_ENABLED=1' to go build release command

Updated the binary release file for linux_amd64. The new file should work.
Thanks for pointing the issue @navicstein


Clarification EC2 instances must be set to the private DNS hostname of the instance (will typically end in .internal)

File: ee/ucp/kubernetes/configure-aws-storage.md
I dont understand this sentence
"EC2 instances must be set to the private DNS hostname of the instance (will typically end in .internal)"
What must be set in the EC2 instances ?  A property ? What  property ?

It should say hostname of the EC2 instances

@bermudezmt You can set the EC2 hostname using the following docs from AWS: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/set-hostname.html

@martencassel - This looks like it's been fixed - PTAL at the current version of the file and see if additional updates are needed - thank you!


Package spec in build plan and metadata?

Describe the problem you are trying to solve
I'd like to selectively prebuild some or all of the dependencies of my crate.
I can do this with cargo build --package log which is super awesome.
If I have two version of log, I need to specify which one with a package spec. Cargo gives me the ability to do cargo metadata and cargo build --build-plan, it also gives me the option to get an ID with cargo pkgid (https://doc.rust-lang.org/cargo/reference/pkgid-spec.html)
Unfortunately, I can't make them play together. metadata and --build-plan don't provide package specs, so I end up forced to do manual parsing if I want to hope to make all these tools interact.
Describe the solution you'd like
Include a package spec in the output of cargo metadata and/or cargo build --build-plan
Notes
Related to #2644 since that was essentially what I was trying to do.

If #7289 isn't a duplicate, then its closely related.

Hmm, it appears package specs are ambiguous and we'd need to solve that first.
While working to improve the design of package id specs, we should include resolving #7725.


Support using java.time instead of ThreeTenBp in generated code

In Android, using core library desugaring is now favored over the use of ThreeTenBp to make java.time classes available in the project.  However, swagger-gradle-codegen generates codes that imports from org.threeten.bp.  It would be great if we could configure swagger-gradle-codegen to use java.time instead

I've just realized that we already support this. It has been merged in #138.
It's available on master or on the upcoming version of the plugin


Fix details tag replacement

The issue was that there is bug in js which didnt matched replace in linebreaks.
I have used regexp now.
Now it is also tested in e2e tests

Thanks @pantharshit00 !


EstimateFee

Add function EstimateFee to wallet.
This pr corresponds to the one to btcd here.

I think this should go into chain.go instead, since it isn't a wallet-specific command.

Tested it, works fine.  Can we just merge this, and move it later? It's just a cut and paste


add tunable crop scale and aspect ratio in RandomSizedCrop

Current configuration in RandomResizedCrop is fixed between 0.08 and 1.0, which is too much for compact convolutional neural networks such as MobileNet and ShuffleNet. So I make the crop scale and the aspect ratio tunable in RandomSizedCrop to make more flexible augmentation.

Thanks!


Add multi-gpu mining option in advanced settings

Add multi-gpu mining option in advanced settings. User can select 1-6 GPU to mine.

Multi-gpu mining has now been made available by default. In future updates, users will have the option to disable particular GPUs within advanced settings.


import fix candidate a: removal of dex cert

Fix #2041
Chart PR https://github.com/epinio/helm-charts/pull/341

Codecov Report
Base: 60.05% // Head: 51.24% // Decreases project coverage by -8.81% :warning:

Coverage data is based on head (7d25fe0) compared to base (655e401).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2042      +/-   ##
==========================================
- Coverage   60.05%   51.24%   -8.81%
==========================================
  Files         179      179
  Lines       14543    14543
==========================================
- Hits         8734     7453    -1281
- Misses       4713     6102    +1389
+ Partials     1096      988     -108

Flag
Coverage Δ

acceptance-api
33.84% <ø> (-11.79%)
:arrow_down:

acceptance-apps
36.46% <ø> (+0.19%)
:arrow_up:

acceptance-cli
39.06% <ø> (-16.46%)
:arrow_down:

unittests
8.26% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Notification when DWELL

How can it be implemented that the notification is only sent when "GeofenceStatus.DWELL" is activated? Thanks!

Since this plugin does not yet have a filtering function implemented, you can use a conditional statement in the _onGeofenceStatusChanged function.
Future<void> _onGeofenceStatusChanged(
    Geofence geofence,
    GeofenceRadius geofenceRadius,
    GeofenceStatus geofenceStatus,
    Location location) async {
  // If not in DWELL status, the service will not perform the code below.
  if (geofenceStatus != GeofenceStatus.DWELL) return;

  // some code
}

Thx!


Need to update the product data in seed.json to MongoDB Atlas.

Successfully seeded MongoDB Atlas, the product lists can be viewed at https://peak-everest-furniture.herokuapp.com/api/products, closing issue now.


Set ocaml version of ocamlformat to 4.11

Fixes #8

Is the purpose of this to stop ocamlformat from inserting incompatible let-punning?

Ah yes, this is related to #10

Is the purpose of this to stop ocamlformat from inserting backward incompatible let-punning available in later versions of OCaml?

Exactly, sorry, I forgot to reference my own issue. 🤦♂


Can’t pull requests

Bug Report Dump (Auto-generated)

Version 1.28.0<PHONE_NUMBER>)
Device: iPhone 6s Plus (iOS 11.3)
TestFlight: true

Hey @TeamSoldierNub2, I'm not sure what you mean — can you elaborate?

Hey @TeamSoldierNub2, I'm not sure what you mean — can you elaborate? Creating pull requests from within GitHawk is not supported as of yet.

@BasThomas ah, sorry. I thought it was possible before. Should this be a feature soon? You could pull some code to allow this. Like create issue but instead it pulls a request. Do those two work the same way?
Sent with GitHawk

Closing this in favour of #1796 #2496


Doesn't work with gradle 8.x

When gradle 8.x is used then following error appears:
Cannot locate tasks that match '::dependencies'. The path should not include an empty segment (try ':dependencies' instead).

Thanks for the report 🙏 I added a simple workaround, which I hope will address your setup. For some reason I expected people to pass empty string as the input when referencing the root project (intead of : which is a well-known convention)

That was really quick - thanks a lot :)


repl error for lambda expression with modal pattern argument of user defined type

After loading a file like this
------- so this is non-linear untyped lambda calculus ??
data Exp where
  Abs : (Exp [] -> Exp []) -> Exp;
  App : Exp [] -> Exp [] -> Exp

unAbs : Exp -> (Exp [] -> Exp [])
unAbs (Abs f) = f

eval : Exp -> Exp
eval (Abs f) = (Abs f);
eval (App [e1] [e2]) = let [v] = unAbs(eval e1) [e2]
                        in v

I tried some lambda expression and it an internal error
Granule> \([x] : Nat[]) -> x
\([x] : Nat [0..∞]) -> x
Granule> \([x] : Exp[]) -> x
grin: Internal checker error, tried to look up nonexistent type (Id "Exp" "Exp") in context.
CallStack (from HasCallStack):
  error, called at src/Language/Granule/Checker/Patterns.hs:46:20 in granule-frontend-<IP_ADDRESS>-Jm0NhEo217c3iIJhsg9juR:Language.Granule.Checker.Patterns

Hi @kyagrd, thanks for submitting this bug report. It got fixed some time ago, although when we get our exhaustivity checker working unAbs will be an issue.


f

Codecov Report

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

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage        ?   88.91%
=======================================
  Files           ?       47
  Lines           ?     2454
  Branches        ?        0
=======================================
  Hits            ?     2182
  Misses          ?      272
  Partials        ?        0

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


Fix failed to parse source map error (#42)

Fix #42 as proposed by @mcmire

Hey @maui-r, sorry I haven't looked at this yet. I need to double-check this against create-react-app to verify that the issue reported is indeed resolved. I'll make time for this today.

I'm working on creating a new release which includes this fix. I need to get https://github.com/MetaMask/detect-provider/pull/47 merged but then I will get a new release issued after that.


Bug: Claudie doesn't support multiple Provider configurations for the same cloud provider

Current Behaviour

Using multiple Provider (at least two) configurations for the same cloud provider results in the following error in terraformer
Error: Duplicate provider configuration
jakub-blog-test-z7ep12d │
jakub-blog-test-z7ep12d │   on jakub-blog-test-z7ep12d-azure-2-provider.tf line 1:
jakub-blog-test-z7ep12d │    1: provider "azurerm" {
jakub-blog-test-z7ep12d │
jakub-blog-test-z7ep12d │ A provider configuration for "azurerm" with alias "nodepool" was already
jakub-blog-test-z7ep12d │ given at jakub-blog-test-z7ep12d-azure-1-provider.tf:1,1-19. Each
jakub-blog-test-z7ep12d │ configuration for the same provider must have a distinct alias.

Expected Behaviour

Claudie builds an infrastructure for the same cloud provider using multiple Provider configurations.
Steps To Reproduce

Create at least two secrets for Providers configuration. I created one secret with credentials for our sponsorship subscription and the other one with our pay-as-you-go subscription credentials.
Apply an InputManifest that provisions at least two node pools, each with a different Provider configuration. I've used the following one

apiVersion: claudie.io/v1beta1
kind: InputManifest
metadata:
  name: jakub-blog-test
  labels:
    app.kubernetes.io/part-of: claudie
spec:
  providers:
    - name: cloudflare-1
      providerType: cloudflare
      secretRef:
        name: cloudflare-secret
        namespace: default
    - name: azure-1
      providerType: azure
      secretRef:
        name: berops-azure-secret
        namespace: default
    - name: azure-2
      providerType: azure
      secretRef:
        name: sponsor-azure-secret
        namespace: default

  nodePools:
    dynamic:
      - name: control-azure-1
        providerSpec:
          name: azure-1
          region: westeurope
          zone: "1"
        count: 1
        serverType: Standard_B2s
        image: Canonical:0001-com-ubuntu-minimal-jammy:minimal-22_04-lts:22.04.202212120

      - name: compute-azure-1
        providerSpec:
          name: azure-1
          region: westeurope
          zone: "2"
        count: 1
        serverType: Standard_B2s
        image: Canonical:0001-com-ubuntu-minimal-jammy:minimal-22_04-lts:22.04.202212120
        storageDiskSize: 50

      - name: compute-azure-2
        providerSpec:
          name: azure-1
          region: northeurope
          zone: "3"
        count: 1
        serverType: Standard_B2s
        image: Canonical:0001-com-ubuntu-minimal-jammy:minimal-22_04-lts:22.04.202212120
        storageDiskSize: 50

      - name: loadbalancer-1
        providerSpec:
          name: azure-1
          region: northeurope
          zone: "1"
        count: 1
        serverType: Standard_B2s
        image: Canonical:0001-com-ubuntu-minimal-jammy:minimal-22_04-lts:22.04.202212120
        storageDiskSize: 50

  kubernetes:
    clusters:
      - name: jakub-blog-test
        version: "v1.26.0"
        network: <IP_ADDRESS>/24
        pools:
          control:
            - control-azure-1
          compute:
            - compute-azure-1
            - compute-azure-2
  loadBalancers:
    roles:
      - name: apiserver
        protocol: tcp
        port: 6443
        targetPort: 6443
        targetPools:
          - control-azure-1
    clusters:
      - name: apiserver-lb-claudie
        roles:
          - apiserver
        dns:
          dnsZone: claudie.dev
          provider: cloudflare-1
        targetedK8s: jakub-blog-test
        pools:
          - loadbalancer-1

It should also work without a loadbalancer.
Anything else to note
This issue first occurred in this blog.

This should be fairly easily supported with provider aliases.

Hey guys, looks like here's the culprit for azure:
https://github.com/berops/claudie/blob/master/services/terraformer/templates/azure/provider.tpl#L7C22-L7C30
It seems you're doing it right for other providers, though to me it seems better to base these on provider.name rather than provider.region:
https://github.com/berops/claudie/blob/master/services/terraformer/templates/aws/provider.tpl

@MarioUhrik is right about the azure bug.
Regarding the provider.name, I think that does not work as a single provider can be used for more nodepools, which can be spread in different regions.

Indeed, and given the fact, that in Claudie the design allows the usage of two different AWS provider configs in the same region (e.g. for billing or reporting purposes), the current code imposes a limitation.

At first, we have to check whether changing the TF provider name triggers a resource recreation. We need to check the provider alias for all the cloud providers.


AccessViolationException

Hi!
When I try recreate Chakra Runtime, create Chakra Context and acquire Context Scope several times I got the following exception when trying to call a function. Here is additional message:

"Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

I am using the latest Chakra version with release build (x64).

Ok, I managed to resolve the problem. It seems when you are passing arguments to the function you have to call AddRef() on each JavaScriptValue, otherwise they could be collected before the function is actually called. After execution you can release them. I think it is quite important and it should be added to the documentation.
Here you have sample code snippets:
private static JavaScriptValue[] PrepareJavaScriptFunctionArguments(JavaScriptValue javaScriptThisArgument, object[] arguments)
{
    JavaScriptValue[] javaScriptFunctionArguments = new JavaScriptValue[arguments.Length + 1];

    javaScriptFunctionArguments[0] = javaScriptThisArgument;

    for (int i = 0; i < arguments.Length; i++)
    {
        javaScriptFunctionArguments[i + 1] = JavaScriptConverter.FromObject(arguments[i]);
        javaScriptFunctionArguments[i + 1].AddRef();

    }
    return javaScriptFunctionArguments;
}

private static object CallFunction(JavaScriptValue javaScriptFunction, JavaScriptValue[] javaScriptFunctionArguments)
{
    try
    {
        var result = javaScriptFunction.CallFunction(javaScriptFunctionArguments);
        var objectResult = JavaScriptConverter.ToObject(result);
        foreach (var argument in javaScriptFunctionArguments)
        {
            argument.Release();
        }
        return objectResult;
    }
    catch (JavaScriptScriptException exception)
    {
        throw new ChakraException(exception.Error);
    }
}

Thanks for the suggestion @Havret . You're pretty much right - you need to pin down JavaScriptValues with JsAddRef if these values are no longer on the stack. It's also important to release these objects after you're done so that GC can actually collect them, as you've shown in the second snippet. I'll look into adding documentation at a proper location and will post link here when I'm done.

Actually we already had it documented here. Closing the issue.

Hi,
I know this issue has been closed, but I am having some concerns regarding the solution suggested by @Havret. Don't you still have a race condition with the garbage collector between the two following lines?
  javaScriptFunctionArguments[i + 1] = JavaScriptConverter.FromObject(arguments[i]);
  // garbage collection can happen here, collecting the newly created object
  javaScriptFunctionArguments[i + 1].AddRef();

Am I missing something here?
Thanks in advance,
Morten

@mortenab You still have a native stack reference to the JavaScriptValue s.t. GC won't collect the object.

@liminzhu thanks for the reply.
So I guess the .NET stack is seen as part of the native stack?
If I for example implemented the function call in this way:
JavaScriptValue jsStr = JavaScriptValue.FromString("testArg");
var result = javaScriptFunction.CallFunction(new JavaScriptValue[] { JavaScriptValue.Null, jsStr });

I would not need to call AddRef on the jsStr, since it is on the stack?
Thanks,
Morten

No you're fine as long as the object is still on the C# stack.

@liminzhu thanks for the clarification. I have created another issue in the samples repo: https://github.com/Microsoft/Chakra-Samples/issues/49
You are welcome to close that issue.

@liminzhu sorry I have a couple more questions on this... I'm not sure I understand how C# call stack can prevent an object from being collected by JavaScript GC? I had an impression the two GCs are not really aware of each other?
Also does JavaScript GC always run continuously on a separate thread? Or does it pause while a host callback function is being executed?

The C# GC and the ChakraCore GC are not aware of each other, but the ChakraCore GC can walk the native stack and find pointers to things in the ChakraCore recycler and use those as roots. As long as the translation of various Js* handles into C# treats them as opaque and keeps the handle on the stack, then the ChakraCore recycler won't collect them.
The ChakraCore recycler doesn't run continuously (unless it has to due to app behavior), but it does do as much as possible away from the main thread. Most of the "marking" will happen on background threads, then the main thread will be stopped momentarily for a final pass to make sure that there is a consistent state of the world. At this point we also handle some cleanup synchronously, like invoking finalizers. Once that is done, most of the "sweep" of actually returning memory to the recycler to be used later happens on a background thread again.

Thanks, @MSLaguana. That clarifies it a bit, however after more digging I found this discussion from which it sounds like it might not always be safe to rely on the compiler to actually keep values on the stack, and the recommendation seems to be to still call JsAddRef/JsRelease: https://github.com/microsoft/ChakraCore/issues/2836
Also I'm not sure if running a .NET host complicates matters even further compared to a native C host... I couldn't find much documentation on how .NET runtime interacts with the native stack and if it does any additional optimizations, but wanted to do more research on this.
Should I be worried about this at all? Or is it something that can happen in theory, but shouldn't really happen in practice?

I see, that makes a lot of sense now. As always, thank you for your super promt response, detailed answers and patience while answering my questions :)


Missing Flutter.h when building for iOS

When building for iOS my application throws an error that flutter.h is missing. It's not pointing to a plugin. It seems like my code's the issue.
I tried to fix the error using everything mentioned here: https://stackoverflow.com/questions/64973346/error-flutter-flutter-h-file-not-found-when-flutter-run-on-ios/65577277 and here: https://github.com/flutter/flutter/issues/70895.
Flutter doctor -v shows no errors:
[✓] Flutter (Channel stable, 2.5.3, on macOS 12.0.1 21A559 darwin-x64, locale de)
    • Flutter version 2.5.3 at /usr/local/Caskroom/flutter/2.0.6/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (5 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0-rc3)
    • Android SDK at /Users/dev/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0-rc3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 13.1, Build version 13A1030d
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)

[✓] VS Code (version 1.62.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.28.0

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 95.0.4638.69

Complete output of the building-process:
Building net.dev.app for device (ios-release)...
Automatically signing iOS for device deployment using specified development team in Xcode project: XXXXXXXX
Running pod install...                                           2.284ms
Running Xcode build...
Xcode build done.                                           31,4s
Failed to build iOS app
Error output from Xcode build:
↳
    --- xcodebuild: WARNING: Using the first of multiple matching destinations:
    { platform:iOS, id:xxx-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
    { platform:iOS, id:xxx-xxx, name:devIOS }
    { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
    { platform:iOS Simulator, id:8BDC26D1-F182-421C-93A0-627ED20CCC9D, OS:15.0, name:iPhone 8 }
    { platform:iOS Simulator, id:DBAE56B6-2798-4A34-A1D5-39D44D897C17, OS:15.0, name:iPhone 8 Plus }
    { platform:iOS Simulator, id:41FA36A9-111D-41FF-B024-522DD1A718DB, OS:15.0, name:iPhone 11 }
    { platform:iOS Simulator, id:CD35A794-9531-4A22-BCEA-B9A388921954, OS:15.0, name:iPhone 11 Pro }
    { platform:iOS Simulator, id:E2481BF1-08B5-4F3F-84E5-47CCCAB656A2, OS:15.0, name:iPhone 11 Pro Max }
    { platform:iOS Simulator, id:E04EEF9B-CECC-4507-9A32-CFDCF818C41E, OS:15.0, name:iPhone 12 }
    { platform:iOS Simulator, id:CB5267E5-637C-4643-A2A2-C1D6220D5179, OS:15.0, name:iPhone 12 Pro }
    { platform:iOS Simulator, id:E93F1DF7-5563-45FC-ADD8-8ED623B30D3B, OS:15.0, name:iPhone 12 Pro Max }
    { platform:iOS Simulator, id:C9A349E0-DDD3-434D-A6CB-749D059B0EDE, OS:15.0, name:iPhone 12 mini }
    { platform:iOS Simulator, id:853FC893-E495-4B60-B3A3-6BD67C73591A, OS:15.0, name:iPhone 13 }
    { platform:iOS Simulator, id:647CFF71-976B-4D76-B929-E69083897D30, OS:15.0, name:iPhone 13 Pro }
    { platform:iOS Simulator, id:803FBB8A-14D5-4F6F-83F0-E2A7129FFD67, OS:15.0, name:iPhone 13 Pro Max }
    { platform:iOS Simulator, id:8D5FA35F-0976-45C8-85AC-C73E16424011, OS:15.0, name:iPhone 13 mini }
    { platform:iOS Simulator, id:32AAB0C5-E614-415A-A9E4-3E51C18039D1, OS:15.0, name:iPhone SE (2nd generation) }
    { platform:iOS Simulator, id:F28F0B01-1C66-421D-84ED-141C3960F646, OS:15.0, name:iPod touch (7th generation) }
    { platform:iOS Simulator, id:2F821532-1CBD-4905-A093-FC463BA32FD3, OS:15.0, name:iPad (9th generation) }
    { platform:iOS Simulator, id:A1446CB2-27F6-4743-94B3-EAE653D42A2E, OS:15.0, name:iPad Air (4th generation) }
    { platform:iOS Simulator, id:28615608-3235-423E-A2D2-07F1B054C775, OS:15.0, name:iPad Pro (9.7-inch) }
    { platform:iOS Simulator, id:33D99E54-3851-4216-B9AD-34D2D19B5D3D, OS:15.0, name:iPad Pro (11-inch) (3rd generation) }
    { platform:iOS Simulator, id:7A8234C0-B686-4E3B-B04E-C32DCAF445C1, OS:15.0, name:iPad Pro (12.9-inch) (5th generation) }
    { platform:iOS Simulator, id:7E440BB4-4ADD-4D17-AA69-C44632404F50, OS:15.0, name:iPad mini (6th generation) }
    ** BUILD FAILED **

Xcode's output:
↳
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/sensors_plus-1.2.1/ios/Classes/FLTSensorsPlusPlugin.m:45:24: warning: this old-style function definition is
    not preceded by a prototype [-Wstrict-prototypes]
    void _initMotionManager() {
                           ^
    1 warning generated.
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-5.3.2/ios/Classes/InAppBrowser/InAppBrowserWebViewController.swift:557:13: warning:
    setter for 'statusBarStyle' was deprecated in iOS 9.0: Use -[UIViewController preferredStatusBarStyle]
                UIApplication.shared.statusBarStyle = UIStatusBarStyle(rawValue: previousStatusBarStyle)!
                ^
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-5.3.2/ios/Classes/Types/URLCredential.swift:14:25: warning: comparing non-optional
    value of type '[Any]' to 'nil' always returns true
            if certificates != nil {
               ~~~~~~~~~~~~ ^  ~~~
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-5.3.2/ios/Classes/Util.swift:86:25: warning: 'spotlightSuggestion' was deprecated in
    iOS 10.0: renamed to 'WKDataDetectorTypes.lookupSuggestion'
                    return .spotlightSuggestion
                            ^
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-5.3.2/ios/Classes/Util.swift:86:25: note: use 'WKDataDetectorTypes.lookupSuggestion'
    instead
                    return .spotlightSuggestion
                            ^~~~~~~~~~~~~~~~~~~
                            WKDataDetectorTypes.lookupSuggestion
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-5.3.2/ios/Classes/Util.swift:121:31: warning: 'spotlightSuggestion' was deprecated in
    iOS 10.0: renamed to 'WKDataDetectorTypes.lookupSuggestion'
                if type.contains(.spotlightSuggestion) {
                                  ^
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-5.3.2/ios/Classes/Util.swift:121:31: note: use 'WKDataDetectorTypes.lookupSuggestion'
    instead
                if type.contains(.spotlightSuggestion) {
                                  ^~~~~~~~~~~~~~~~~~~
                                  WKDataDetectorTypes.lookupSuggestion
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-5.3.2/ios/Classes/Util.swift:216:21: warning: immutable value 'j' was never used;
    consider replacing with '_' or removing it
                    for j in ipv6.count...8 {
                        ^
                        _
    remark: Incremental compilation has been disabled: it is not compatible with whole module optimization
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/barcode_scan-3.0.1/ios/Classes/BarcodeScannerViewController.swift:47:38: warning: 'flashMode' was
    deprecated in iOS 10.0: Use AVCapturePhotoSettings.flashMode instead.
        return device != nil && (device?.flashMode == AVCaptureDevice.FlashMode.on || device?.torchMode == .on)
                                         ^
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/barcode_scan-3.0.1/ios/Classes/BarcodeScannerViewController.swift:200:14: warning: 'flashMode' was
    deprecated in iOS 10.0: Use AVCapturePhotoSettings.flashMode instead.
          device.flashMode = on ? .on : .off
                 ^
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/barcode_scan-3.0.1/ios/Classes/SwiftBarcodeScanPlugin.swift:24:36: warning: 'devices(for:)' was deprecated
    in iOS 10.0: Use AVCaptureDeviceDiscoverySession instead.
                result(AVCaptureDevice.devices(for: .video).count)
                                       ^
    /* com.apple.ibtool.document.warnings */
    /Users/dev/.pub-cache/hosted/pub.dartlang.org/flutter_inappwebview-5.3.2/ios/Storyboards/WebView.storyboard:global: warning: This file is set to build
    for a version older than the deployment target. Functionality may be limited. [9]
    /Users/dev/GitHub/my_app/ios/Runner/Runner-Bridging-Header.h:1:9: note: in file included from
    /Users/dev/GitHub/my_app/ios/Runner/Runner-Bridging-Header.h:1:
    #import "GeneratedPluginRegistrant.h"
            ^
    /Users/dev/GitHub/my_app/ios/Runner/GeneratedPluginRegistrant.h:10:9: error: 'Flutter/Flutter.h' file not found
    #import <Flutter/Flutter.h>
            ^
    1 error generated.
    <unknown>:0: error: failed to emit precompiled header
    '/Users/dev/Library/Developer/Xcode/DerivedData/Runner-cbgrqxmjjcojaagoxzouleayuoqx/Build/Intermediates.noindex/PrecompiledHeaders/Runner-Bridging-Header
    -swift_2V9F1QDZBMZA0-clang_QF9IPAUWC82R.pch' for bridging header '/Users/dev/GitHub/my_app/ios/Runner/Runner-Bridging-Header.h'
    /Users/dev/GitHub/my_app/ios/Runner/Runner-Bridging-Header.h:1:9: note: in file included from
    /Users/dev/GitHub/my_app/ios/Runner/Runner-Bridging-Header.h:1:
    #import "GeneratedPluginRegistrant.h"
            ^
    2 errors generated.
    remark: Incremental compilation has been disabled: it is not compatible with whole module optimization
    error: generate-pch command failed with exit code 1 (use -v to see invocation)
    note: Using new build system
    note: Planning
    note: Build preparation complete
    note: Building targets in parallel
    /Users/dev/GitHub/my_app/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of
    supported deployment target versions is 9.0 to 15.0.99. (in target 'MTBBarcodeScanner' from project 'Pods')
    /Users/dev/GitHub/my_app/ios/Pods/Pods.xcodeproj: warning: The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of
    supported deployment target versions is 9.0 to 15.0.99. (in target 'OrderedSet' from project 'Pods')

It has somehow solved itself.


Update asdk-register.md

just a typo

@balagev : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@balagev : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@balagev - thank you!

@balagev - thank you!


Fix fatal error on stage.

Refs #5910

Looks good! Except, I still don't see the $node parameter being used anywhere in the dosomething_campaign_get_hot_time_left() function. Does the cron get called somewhere in this functions?

@sbsmith86 yeah it's passed in in the cron, we might need to update that later today

yeah cron errors, I'll make an issue for that :wink:


monit-slapd  slapd_service_file path changed to sysv in jessie

it is missing a case for default: undef


Add stubs for the ensure functions

Added function stubs to ensure the resources which are required to run and instance of AWSLoadBalancerController. Also added RBAC permissions to the controller through kubebuilder annotations.

/lgtm

/lgtm


Write setup guide for readme

This is mostly done, but I need to write Capistrano setup instructions.

This gets real weird and unclear at the end — I think I committed before I was done a few weeks back. Going to do one more pass over it.


auto-close = "outsideClick" do not work with new uib-dropdown directive

Just switched to 0.14.2,  the new directive uib-dropdown ignores the auto-close="outsideClick".  It works if I keeps the old dropdown directive, but don't if I update as per the warning message in the console.
Console warnings:
dropdown-toggle is now deprecated. Use uib-dropdown-toggle instead.
dropdown-menu is now deprecated. Use uib-dropdown-menu instead.
thanks,
eddie

Can you please quickly create a plunker that demonstrates this?  Thanks.

http://plnkr.co/edit/f6NV20pHZE7lcBBwTCcS?p=preview

Thanks for the reproduction - this is actually a usage issue, as one can see it working here. What was missing was the uib-dropdown-menu attribute (or class, if one wants) on the element with the dropdown menu.

thanks that works.  Looks like the documentation on the web site only mentioned:  dropdown-menu , not uib-dropdown-menu.

I know this is about 2 years too late, as the library is deprecated, but this only works with the attribute uib-dropdown-menu. It doesn't work with the element uib-dropdown-menu or dropdown-menu, nor with the class dropdown-menu.


Update dp-renderer to 1.8.0 and make dp-design-system the priority over sixteens

What
Updated dp-renderer to 1.8.0 and updated mapper functions to use SixteensVersion where pertinent
How to review

Sense check code
Check pages handled by the dataset controller locally to ensure that they are loading in either Sixteens or dp-design-system. If it is a CMD or legacy dataset page, then that should be loading in Sixteens. If it's the Census dataset landing page, then dp-design-system should be loaded in

Who can review
Anyone

Not solely related to this service but there are a number of console.errors which I believe are related to code in the dp-design-system  I would sumize that this method needs a closer look

As discussed, this was a bug in the ONS DS that has been fixed by bumping the npm module version. I will update this PR with the new commit hash once dp-design-system is updated


Support Async Observations

Similar to async computes, we need some way of creating Observations that can set their values asynchronously.
This would allow us to replace uses of compute.async with Observations and fully support https://github.com/canjs/can-define/issues/149.

This might be the same as https://github.com/canjs/can-observation/issues/84.
cc @christopherjbaker @justinbmeyer

The are definitely related. The deferred observables was one way to make an
asynchronous observable (and was implemented in RVM, which is what these
were for), though I think one that supports async functions would be much
nicer.
The specific need for these was RVM, and it was solved in the repo, do
these can be closed if the functionality is not otherwise desired.


⚠ Bofrost.at has degraded performance

In 0308dca, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1169 ms

Resolved: Bofrost.at performance has improved in 0aa8ebd after 10 minutes.


[WIP] [Feature] T4 app tools

I've implemented the previous vscode extension from CUA inside the project. Currently before running it you have to manually compile it with yarn compile in the apps/vscode folder. To run it simply use the vscode "Run and Debug" menu.
I've not added yarn compile as a required task before running because currently throws a bunch of errors regarding other packages (that I've already tried to exclude in the tsconfig). I would appreciate if you had a solution, here they are:
../../node_modules/react-native/types/modules/LaunchScreen.d.ts:17:16 - error TS2451: Cannot redeclare block-scoped variable 'ReloadInstructions'.

17   export const ReloadInstructions: any;
                  ~~~~~~~~~~~~~~~~~~

  ../../node_modules/@types/react-native/modules/LaunchScreen.d.ts:8:16
    8   export const ReloadInstructions: any;
                     ~~~~~~~~~~~~~~~~~~
    'ReloadInstructions' was also declared here.

Found 244 errors in 18 files.

Errors  Files
     4  node_modules/@types/node/globals.d.ts:47
     4  node_modules/@types/node/url.d.ts:826
     5  ../../node_modules/@types/react-native/index.d.ts:194
     3  ../../node_modules/@types/react-native/modules/BatchedBridge.d.ts:8
     1  ../../node_modules/@types/react-native/modules/Codegen.d.ts:1
     1  ../../node_modules/@types/react-native/modules/Devtools.d.ts:2
    15  ../../node_modules/@types/react-native/modules/globals.d.ts:10
     5  ../../node_modules/@types/react-native/modules/LaunchScreen.d.ts:4
   177  ../../node_modules/@types/react-native/node_modules/@types/react/ts5.0/index.d.ts:3168
     5  ../../node_modules/@types/react-native/public/DeprecatedPropertiesAlias.d.ts:20
     1  ../../node_modules/@types/react/ts5.0/global.d.ts:152
     1  ../../node_modules/@types/react/ts5.0/index.d.ts:3199
     5  ../../node_modules/react-native/types/index.d.ts:200
     3  ../../node_modules/react-native/types/modules/BatchedBridge.d.ts:17
     1  ../../node_modules/react-native/types/modules/Codegen.d.ts:10
     1  ../../node_modules/react-native/types/modules/Devtools.d.ts:11
     7  ../../node_modules/react-native/types/modules/globals.d.ts:19
     5  ../../node_modules/react-native/types/modules/LaunchScreen.d.ts:13

The extension then works fine in the dev environment.

The issues are fixed!!
Now the only thing that you have to do to debug the vscode extension is uncommenting a line in .vscode/settings.json, only if you normally have a non default terminal profile.
I've also fixed the github workflow and it should be good now.


Account for read/cancel rights locked in dispute period and cancel resolutions

reproduce scenarios where delayed execution of request can be exploitet to get extra rights
account for pending read/cancel rights locked in dispute_period and cancel resolutions

logs from reproduced test cases
running 3 tests
test tests::consider_awaiting_cancel_resolutions_and_cancel_disputes_when_assigning_initial_read_rights_to_sequencer ... FAILED
test tests::consider_awaiting_cancel_resolutions_and_cancel_disputes_when_assigning_initial_cancel_rights_to_sequencer ... FAILED
test tests::consider_awaiting_l1_READ_update_in_dispute_period_when_assigning_initial_read_rights_to_sequencer ... FAILED

failures:

---- tests::consider_awaiting_cancel_resolutions_and_cancel_disputes_when_assigning_initial_read_rights_to_sequencer stdout ----
thread 'tests::consider_awaiting_cancel_resolutions_and_cancel_disputes_when_assigning_initial_read_rights_to_sequencer' panicked at 'assertion failed: `(left == right)`
  left: `SequencerRights { read_rights: 2, cancel_rights: 2 }`,
 right: `SequencerRights { read_rights: 1, cancel_rights: 2 }`', pallets/rolldown/src/tests.rs:2061:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- tests::consider_awaiting_cancel_resolutions_and_cancel_disputes_when_assigning_initial_cancel_rights_to_sequencer stdout ----
thread 'tests::consider_awaiting_cancel_resolutions_and_cancel_disputes_when_assigning_initial_cancel_rights_to_sequencer' panicked at 'assertion failed: `(left == right)`
  left: `SequencerRights { read_rights: 1, cancel_rights: 4 }`,
 right: `SequencerRights { read_rights: 1, cancel_rights: 2 }`', pallets/rolldown/src/tests.rs:1906:13

---- tests::consider_awaiting_l1_READ_update_in_dispute_period_when_assigning_initial_read_rights_to_sequencer stdout ----
thread 'tests::consider_awaiting_l1_READ_update_in_dispute_period_when_assigning_initial_read_rights_to_sequencer' panicked at 'assertion failed: `(left == right)`
  left: `SequencerRights { read_rights: 2, cancel_rights: 2 }`,
 right: `SequencerRights { read_rights: 1, cancel_rights: 2 }`', pallets/rolldown/src/tests.rs:1980:13

failures:
    tests::consider_awaiting_cancel_resolutions_and_cancel_disputes_when_assigning_initial_cancel_rights_to_sequencer
    tests::consider_awaiting_cancel_resolutions_and_cancel_disputes_when_assigning_initial_read_rights_to_sequencer
    tests::consider_awaiting_l1_READ_update_in_dispute_period_when_assigning_initial_read_rights_to_sequencer

test result: FAILED. 0 passed; 3 failed; 0 ignored; 0 measured; 45 filtered out; finished in 0.04s

:kissing:


feat: add billing endpoints

#60  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @RajatPawar and the rest of your teammates on  Graphite


Objects should be deleted as the user scrolls down

I want to delete objects as the user scrolls down. Does ngInfiniteScroll provide a way to do it ?

@jchgautier I think virtual repeat does this https://material.angularjs.org/latest/demo/virtualRepeat

@jchgautier There is a bunch of potential problems in doing a virtual repeat/garbage collection. It would most definitely be something that would enhance this lib a lot. The main issue is that a virtual repeat works completely different from a basic infinite scrolling since it is in a simple implementation bound to a fixed height of elements.

For performance issue, ngInfiniteScroll should work load more content, and also remove those previous generated content at the same time.
virtualRepeat is not really same idea of removing previous generated content.


demo does not run in Google colab

When running the demo code in Colab using the provided link, I encounter the following error in the first code block:
--> 328         return list(public_symbols)
    329
    330     # Pytest testing

AttributeError: module 'numpy' has no attribute 'typing'

This suggests a potential issue with the Numpy version installed in this environment. numpy.typing was introduced in Numpy version 1.20. The demo code runs well locally with numpy 1.24. on my machine.

Thanks for letting me know Jacob! The issue was the importing of np.typing. The numpy versions are ensured to be  >=1.22 .
I made some changes and hopefully the issue is now fixed. Although, I do see some installation issues that depend on some colab version. Although, running the first cell twice does the job. Feel free to try it out again.


First character overwritten in headers and variables tabs

When you start typing headers or variables, the first character you type is replaced by a {.

Fixed in the latest version. Please let us know if you still have that issue, then we reopen it!


Handle incomplete releases

For some releases (pre-releases?), Tidal's API does not return all tracks:

https://listen.tidal.com/album/365033100 (Cached)
https://listen.tidal.com/album/355013613 (Cached)

The missing tracks are not shown on tidal.com/browse/album pages at all, on listen.tidal.com pages they are displayed greyed out.
Since the API returns at least the correct track count we could try to fill the tracklist (for single medium releases) with [unknown] tracks to allow for these releases being combined with other sources which have the track titles and lengths.

It is not only Tidal. Here are different tracklists (and reported release date) from the various services as of today:
Tidal (https://tidal.com/browse/album/365033100):
2024-06-07

The Bounce

Spotify (https://open.spotify.com/intl-de/album/50D6UCzWeKbFron5Q3l7NC)
2024-06-07

The Bounce

Apple (https://music.apple.com/gb/album/the-bounce-single/1747775711)
2024-06-21

The Bounce

But the API did not return a tracklist.
Beatport (https://www.beatport.com/release/-/4585106)
2024-06-07

The Bounce (Extended Mix)
The Bounce (Lampe Remix)

Deezer (https://www.deezer.com/en/album/591275592)
2024-06-07

The Bounce (Extended Mix)
The Bounce
The Bounce (Lampe Remix)

Only track 2 and 3 are already playable, track 1 is displayed grayed out.
My best bet on the situation is that 2024-06-21 will be the actual date of release and that this will eventually end up with a 3 track tracklist as right now only reported by Deezer. That Tidal gives the only track the number "2" strongly hints at that.
2024-06-07 is likely the date they added this to the various services, and only iTunes reports a future release date.

Related Tidal-specific issue: #65


Request CTO validation is not working

Describe the bug
It is possible to send an invalid request (with respect to the CTO model) and have the Ergo execute.
To Reproduce

Download the attached template
Using the request and state within the archive
cicero execute --request monthlysales-invalid.json --state state.json
Note that execution succeeds, when it should fail

Expected behavior
The execution should fail because sales[0].price.doubleValue is a string.
Version
Cicero 0.13.5

Concerto is generally quite lose with validation. Bug or feature?
bash-3.2$ cat models/model.cto
namespace org.accordproject.promissorynote

import org.accordproject.money.MonetaryAmount from https://models.accordproject.org/money.cto

transaction Payment extends Request {
  o MonetaryAmount amountPaid
  o Boolean isValid
	o Integer someNumber
}
bash-3.2$ cat request.json
{
  "$class": "org.accordproject.promissorynote.Payment",
  "amountPaid": {
    "doubleValue": 1.0,
    "currencyCode": "USD"
  },
  "isValid" : "something",
  "someNumber" : "something else"
}
bash-3.2$ concerto validate --ctoFiles models/*.cto --sample request.json
8:45:45 AM - info:
{
  "$class": "org.accordproject.promissorynote.Payment",
  "amountPaid": {
    "$class": "org.accordproject.money.MonetaryAmount",
    "doubleValue": 1,
    "currencyCode": "USD"
  },
  "isValid": false,
  "someNumber": null,
  "transactionId": "7a521051-6af6-4aca-8a26-199f66b09753",
  "timestamp": "2019-12-06T13:45:45.698Z"
}

A proposed resolution is to change the validation semantics to be strict. This means atomic values in the JSON will have to be proper instances of the corresponding atomic type.
Before
Boolean
true validate Boolean -> true
false validate Boolean -> false
"true" validate Boolean -> true
3.14 validate Boolean -> false
null validate Boolean -> false
undefined validate Boolean -> false
{} validate Boolean -> false
[] validate Boolean -> false

After
Boolean
true validate Boolean -> true
false validate Boolean -> false
"true" validate Boolean -> ERROR
3.14 validate Boolean -> ERROR
null validate Boolean -> ERROR
undefined validate Boolean -> ERROR
{} validate Boolean -> ERROR

Initial PR implementing the proposal is in #161

Initial PR implementing the proposal is in #161

The change in this PR is great at identifying potential issues in test. E.g., in Ergo:
https://github.com/accordproject/ergo/pull/724

Fixed based on proposal in #161 in the 1.0 branch


Support for Compose for PostgreSQL service

when will this be available on bluemix? The current buildpack on bluemix "buildpack_liberty-for-java_v3.5-20161114-1152.zip" does not work for auto-configuration for postgresql


hw5 Jialun Weng

I don't know if this is the correct way to do it.
From Jialun Weng

should be merging into ProbeDemo branch.


Problems with DataGrid filtering if DataGrid is in Dialog component.

When you place DataGrid in Dialog component filter options are not showing.

[X] The issue is present in the latest release.
[X] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Dialog has z-index  set to 1300 and div that filter is placed in has no z-index, so it is invisible. In console or CSS file I can manually set z-index of that div to 1400 and then I can see the filters, but I cannot type anything in input field anyway. (The same applies to XGrid)
Expected Behavior 🤔
DataGrid placed in Dialog should work correctly with filters available.
Steps to Reproduce 🕹
Steps:

Create Dialog and DataGrid or XGrid inside
Open the dialog
Click on 3 dots column menu - nothing happens
Click  filter icon or Density icon in Toolbar - nothing happens
Add to CSS div[role="tooltip"] { z-index: 1400;}
Now you can see filter and density options when you click on icons
Open filters and try to type any value - doesn't work

Your Environment 🌎

`npx @material-ui/envinfo`
System:
OS: Windows 10 10.0.19042
Binaries:
Node: 12.16.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 87.0.4280.141
Edge: Spartan (44.19041.423.0), Chromium (87.0.664.75)
npmPackages:
@material-ui/core: 4.11.1 => 4.11.1
@material-ui/data-grid: ^4.0.0-alpha.15 => 4.0.0-alpha.15
@material-ui/icons: 4.11.2 => 4.11.2
@material-ui/lab: 4.0.0-alpha.57 => 4.0.0-alpha.57
@material-ui/pickers: 3.2.10 => 3.2.10
@material-ui/styles:  4.11.2
@material-ui/system:  4.11.2
@material-ui/types:  5.1.0
@material-ui/utils:  4.11.2
@material-ui/x-grid: ^4.0.0-alpha.15 => 4.0.0-alpha.15
@material-ui/x-grid-data-generator: ^4.0.0-alpha.15 => 4.0.0-alpha.15
@material-ui/x-license:  4.0.0-alpha.15
@types/react:  17.0.0
react: ^16.13.1 => 16.14.0
react-dom: 16.13.1 => 16.13.1
styled-components:  4.4.1
typescript:  3.9.7

A code example would be nice.

A code example would be nice.

https://github.com/Grzegorzsa/mui-datagrid-bug

https://github.com/Grzegorzsa/mui-datagrid-bug


Experiment with Organization of existing Data

I'm curious about maintaining historical comparisons. How best do we represent that?

Dan raises an interesting point about multi-repo organization in #31


Fix(switch): set default value (checked)

Overview
https://codesandbox.io/s/switch-default-value-nwg2g?file=/src/App.js
now:

after:
checked: undefined -> false to control the value of input:checkbox.

Screenshots (if applicable)
Testing

[ ] Updated Typescript types and/or component PropTypes
[x] Added / modified component docs
[ ] Added / modified Storybook stories

Will be cutting a new release today with this in it


Poihana 92%

Based on Poihana.cpp from Project Template. Thanks to Headpenguin for fixing an instruction swap.

My only issue is that init() does not specify why it's commented out / nonmatching, and the use of brackets {} on single lines is inconsistent. Please use {} on every block.

lgtm


Themes get reset and broken on reload (related to SSR)

Description
Clearly and concisely explain the problem.
You can mention unclear or missing information, typos, grammatical mistakes, etc.
Any contributions and suggestions are welcome!

Go to any page that supports dark mode. Let's use the main docs page.

Select dark or light mode.
Confirm the mode is successfully changed.
Refresh the page.
The UI gets displayed in brand mode, but the state is not(check the theme picker).
If the theme you've picked was the light mode, then some other weird stuff happens. This might indicate that some of the components use a class depending on the mode, some of them might be using another strategy.

The source of the problem is probably this(because we are using SSR):
https://github.com/dreamonkey/quasar/blob/3c4dea8f30833318d25d45f56d8a4804797a8cd6/docs/src/components/landing-page/use-theme.js#L4
Website Section URL
Website live preview, paste the page URL or section name (eg. Docs, if it happens on all docs page) below.
Everywhere that supports dark mode, https://quasar.beget.it/docs

I think this is due to SSR pollution as you said, will find a way to make it work

This should be fixed


Cannot attack mobs / entities with mod installed

minecraft version 1.18.2
forge version 40.0.17
Narrowed down issue to the Controllable mod, without it installed I can damage mobs/entities but cannot do so using a controller and this mod. I would love if this bug is fixed as I cannot play with a keyboard/mouse due to medical reasons!
I suspect the update to 1.18.2 broke the mod in some form.

Fixed in https://github.com/MrCrayfish/Controllable/commit/fe25bba23c15905cca2afe38999f724e255a5500


fix: add Slack Team ID custom claim

What kind of change does this PR introduce?
This change adds Slack's https://slack.com/team_id as a custom claim.
What is the current behavior?
Right now, it is difficult to use Supabase for apps that use Slack workspace membership as an authorization mechanism.
What is the new behavior?
With this change, a user's Slack team ID is included in the identity_data column.
Additional context
Slack API response documentation

awesome! thanks for pointing this out and adding it, just curious - what would you use the slack team_id for in your current use case?


Question re: max

When display type is 'dot', the highest dot gets cut in half by the top of the graph (Just like dot series in http://n3-charts.github.io/line-chart/#/examples) which I do not want to happen.
The only way round that which I have found is to manually set the "max" to a few ticks more than the highest value in the data set, like so:
var highestValue = determineHighestValue(dataSet);
$scope.myOptions.axes.y.max = highestValue + 3;

Is there a smarter way of doing this?
If not, how about we allow passing a function like function(lowestValue, highestValue) to min and max?
The max and min aren't actually documented on http://n3-charts.github.io/line-chart/#/docs - should I raise a separate issue for that or even raise a PR?

Thanks :-)

Duplicate of #474

Hi @andyhasit
yeah your workaround is the only solution for now. Sure, feel free to submit a PR for the docs.
You can pass the function to min and max options, however i think we wont support one single option for both because this would be redundant.
Best,
Christoph

This has been fixed in #476, please see the issue for the solution


"How to write a new Score implementation?" doc

We need to have a dedicated "How to write a new Score implementation?" doc entry.
Here is rough idea/draft:
---
title: "Score Implementation Guidelines"
linkTitle: "Score Implementation Guidelines"
weight: 10
description: >
  Guidelines for how a Score implementation should operate.
---

## Score Implementation Guidelines

A "Score implementation" is a process or system that can be used to transform an input Score definition that follows the Score schema into a real set of resources or workloads in a target runtime.

Examples:

- `score-compose` converts workloads into a Docker Compose project.
- `score-helm` injects workloads into a Helm chart to insert Kubernetes manifests into a target cluster.
- Humanitec's Platform Orchestrator can convert Score workloads into deployed modules and provides extensive support for resource types and classes.
- Future implementations may target other platforms like cloud container runtimes, serverless functions, or other workload implementations.

## CLI implementations

### SHOULD support an `init` subcommand

The init command should be run in a directory in order to initialize local state needed for a Score project.

- Validate that the system state will support the Score implementation. Throw an error if required binaries or configuration is not available or not valid.
- Create a skeleton `score.yaml` file if one does not already exist.
- Create a `.score-<impl>` directory in the current directory if one does not exist yet. This may be skipped if the Score implementation never stores project-local state. This may also be a symlink to a directory elsewhere on the system.

The `init` command can support other optional flags as needed.

### MUST support a `generate` subcommand

The `generate` command should be run after `init` and should transform the Score workloads into a format that can be deployed in an implementation specific way.

For example, `score-compose` generates Docker compose manifests; `score-helm` generates a Helm values file to combine with a chart; other Score implementations may generate terraform, cloud formation, or other infrastructure manifests for deployment.

#### `generate` SHOULD support multiple score files

When technically possible, the implementation should support multiple score files. For example: `generate (options..) some-score.yaml score*.yaml`.

The workloads and resources from multiple files should be combined so that workloads from different score files remain independed but resources and references may be shared between them.

#### `generate` MUST NOT deploy workloads

The `generate` command generates the final manifests that can be deployed in an implementation specific way. It must not actually perform the deployment.

#### `generate` MAY prepare or provision resources if not supported at deploy time

While the `generate` command should not deploy the workloads, it may take steps to prepare, validate, or event provision resources required by the workloads.

This should only be done if the deployment step cannot provision the resources.

For example, `score-compose` may use the generate command to generate initial configuration files, secrets, volumes, or other configuration required by the services generated.

#### `generate` SHOULD use the local directory created by `init` for storage

The local project directory (`.score-<impl>`) should be used for project specific storage. This may be used for preparing manifests, tracking resource state, or creating mount points for files and volumes used by either resources or workloads used in the deployment.

#### `generate` SHOULD support override flags to override elements of the provided Score files

It's common that a specific score implementation may not support a feature or requirement used by the given Score file. This can usually be fixed by allowing users to provide some overrides that are merged into the Score files before manifests are generated. This allows values to be changed or overridden.

For example, `generate -f score.yaml -o score.compose-overrides.yaml` might be used to remove or modify unsupported resources.

### SHOULD deprecate the `run` command

Implementations that currently support a `run` command, should mark it deprecated and direct users towards the `init` + `generate` flow.

`run` was deprecated becaue it's meaning is not clear, and it's implementation had wildly different affects in different Score implementations. It may be kept for backwards compatibility, but documentation and tutorials should point users towards the generate flow.

## Validation

### MUST validate against the Score specification

Implementations MUST strictly validate the input Score definition against the schema and throw errors for any unexpected fields, structure, or incorrect typing.

### MUST reject Score definitions that depend on unsupported features

Not all Score implementations can realisticaly support all features of the Score specification. In some cases, these features will change the functionality of the workload negatively and should be rejected.

For example, if a Score implementation doesn't support mounted files, but the workload depends on a mounted file for runtime configuration, it cannot ignore this and should throw an error.

### SHOULD warn on Score definitions that use unsupported features

Related to the previous point, many aspects of the Score definition are not strictly required for the workload to function.

For example, a workload may not be affected if an implementation does not support liveness or readiness probes. Or an implementation may not support cpu reservations and may convert these into limits or ignore them completely.

These warnings should be presented to the user at generate or deploy time through log messages or other appropriate warnings in the user interface.

### MUST reject Score definitions that use unsupported resource types or classes

If a resource type is used that the Score implementation does not support, it cannot be ignored and must be rejected with an appropriate error.

Similarly with classes or more complex resource provisioning implementations, the resource must be rejected if the resource cannot be provisioned.

## Core features

### MUST support container image, command, args, and environment variables

These are the core features of the container element. The command and args should be interpreted like the `Entrypoint` and `Cmd` properties of the OCI specification respectively: `command` indicates the default argv to execute while `args` provides additional arguments that are appended to `command` or the default `Entrypoint` of the container.

Environment variables must be supported.

### MUST support multiple containers per Workload

The implementation must support provisioning multiple containers for the workload. This is a common part of the Score specification that users expect to be transferable between implementations.

### SHOULD place containers of the same Workload in the same network namespace or host if possible

When possible, the containers of a Workload should be placed in the same network namespace so that they can access network sockets over the local loopback interface and cannot listen on the same ports.

If this is not possible, a warning should be thrown, and users should be guided towards alternative network connectivity options if they require inter-container connectivity.

For similar reasons, if containers depend on shared volumes or files that will not be backed by the same storage, warnings should be thrown.

### MUST support service ports

If the definition includes one or more Services, these should be used to expose ports from the network of the Workloads or any replicas of the same Workloads.

Service ports on the same Workload may not overlap, but may overlap with other Workloads (for example, each Workload might have a port 80 service). If this not supported, warnings should be raised.

Workloads may reference and connect to service ports of other Workloads.

The score-implementation-sample repo is up, this should be referenced from this doc too: https://github.com/score-spec/score-implementation-sample.


Support arrow functions without a block statement

#393 supports arrow functions, but will fail when using arrow functions without block statements, like the one mentioned by @julien-c in #389:
function: !!js/function >
  () => 'Wow! JS-YAML Rocks!';

Like @kivlor pointed out already, there's no constructor for ArrowFunction, so this is a bit of a workaround. Personally, I'd rather see this resolved with a safe-eval.

LGTM.
Kick me in a couple of days, i'll merge & publish if no more objections.

@puzrin Ping 😃

Sorry for silence. Published new version with your fixes. Thanks for efforts and patience!

Converting ({ foo, bar}) => "baz" eats argument. Please consider to support the case. TIA


Admin privileges required?

When enabling the extension I get the message:

Run VS Code with admin privileges so the changes can be applied.

Is this required? When using vscode in workplace environments it's not always possible to use admin privileges.

The extension modifies core files, so yes, administrator privileges are required. This extension is extremely alpha, WIP, or whatever you want to call it, and it is basically the bare minimum required to be functional. Please bear with me as I make this extension more stable and better at what it's supposed to do.
Simply running VS Code with admin privileges once should be enough. Just right click the icon and "Run as Administrator". Run the command to enable it, and you should be set from there on. This will need to be applied again after each VS Code update.


Spec converters

Convert non-RDF specifications to the JSON-LD format. The following types of data are supported:

CEDS (in the CSV format),
ZIP archives containing JSON Schema files,
XML Schema.

@richard0000 I rebased this against the develop branch and changed the PR's base.


Last Seen (Last Area) Sensor

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I recently created my own sensor to save the last "valid" result from "sensor.phoneBLE_area". It was harder than I thought it would be.
My "problem" is that my phone will sleep from time to time (seems common). That said, it seems impossible to actually pick it up and move it somewhere WITHOUT "it" knowing. (It always wakes up).
I have a sensor that will show the last "valid" (not unknown/unavailable) location. I find it useful. I think it would be useful if it was built in.
Thank you for making such a useful integration/application!

Hi 6of6, thanks for your suggestion and well done setting up your own template for this.
It is something that has been requested previously and I have decided that I will implement it when I get the time to address it. The feature request is being tracked in issue #202 so I will close this one as a duplicate, and invite you to hop over to #202 and click the "Subscribe" button on that issue so you can stay up to date on progress, and contribute any of your findings or questions there.
Cheers!

Duplicate of #202


Allow for generic excludes of file extensions

"Vanilla (neo)vim" has the option wildignore to allow ignoring some file patterns. This list is neither respected nor is there any other way to enable ignoring specific file patterns.

I posted a patch here


ls: use libc::{major, minor} to calculate device number

At the time of #2145, major and minor have not been added to libc, so we have to manually calculate the device number.
And those functions have been added (rust-lang/libc#2937) so that we can employ them.
BTW, I called cargo fmt on this file, but I didn't see rustfmt.toml in this project, so if you guys don't like it, feel free to ask to to discard the format changes.
Ref: #2140

I love simplifications :)

Test Android builds (28, default, x86) failed on a cp test, which seems unrelated to this PR:
failures:

---- test_cp::test_cp_parents_2_dirs stdout ----
current_directory_resolved:
mkdir_all: /data/data/com.termux/files/usr/tmp/.tmp1DCT2X/a/b/c
mkdir: /data/data/com.termux/files/usr/tmp/.tmp1DCT2X/d
run: /data/data/com.termux/files/home/coreutils/target/debug/coreutils cp -a --parents a/b/c d
thread 'test_cp::test_cp_parents_2_dirs' panicked at 'Command was expected to succeed.
stdout =
 stderr = cp: Permission denied (os error 13)
', tests/common/util.rs:176:9

failures:
    test_cp::test_cp_parents_2_dirs

test result: FAILED. 2325 passed; 1 failed; 31 ignored; 0 measured; 0 filtered out; finished in 215.43s

error: test failed, to rerun pass `--test tests`
error: 1 target failed:
    `--test tests`
Error: The process '/bin/sh' failed with exit code 101

And sadly I have no idea about the failure in Run GNU tests...

both of them aren't your fault ... noise :(


How can we access one service function in another service class

Hi Joe,
Greetings of the day...!!!
We have created some generic service and we would like call the another service class function in this service.
and all services are registered under loaded under scoped.
When we are trying to loadthe service in the constructor function and using the same in our function getting below error.
→  TypeError: Cannot read property 'apply' of undefined
→      at memberInvoker (D:\UI\Projects\koa-abs\node_modules\awilix-koa\src\invokers.ts:93:38)
→      at dispatch (D:\UI\Projects\koa-abs\node_modules\koa-router\node_modules\koa-compose\index.js:44:32)
→      at next (D:\UI\Projects\koa-abs\node_modules\koa-router\node_modules\koa-compose\index.js:45:18)
→      at D:\UI\Projects\koa-abs\node_modules\koa-router\lib\router.js:346:16
→      at dispatch (D:\UI\Projects\koa-abs\node_modules\koa-router\node_modules\koa-compose\index.js:44:32)
→      at D:\UI\Projects\koa-abs\node_modules\koa-router\node_modules\koa-compose\index.js:36:12
→      at dispatch (D:\UI\Projects\koa-abs\node_modules\koa-router\lib\router.js:351:31)
→      at dispatch (D:\UI\Projects\koa-abs\node_modules\koa-compose\index.js:42:32)
→      at D:\UI\Projects\koa-abs\node_modules\koa-compose\index.js:34:12
→      at dispatch (D:\UI\Projects\koa-abs\node_modules\koa-compose\index.js:42:32)
→      at scopePerRequestMiddleware (D:\UI\Projects\koa-abs\node_modules\awilix-koa\src\scope-per-request.ts:13:12)
→      at dispatch (D:\UI\Projects\koa-abs\node_modules\koa-compose\index.js:42:32)
→      at bodyParser (D:\UI\Projects\koa-abs\node_modules\koa-bodyparser\index.js:86:11)
→      at
→      at process._tickDomainCallback (internal/process/next_tick.js:228:7)
Could you please provide any help in this regard.

My name is Jeff. ;)
Please show me the code for the route file.

Sorry for the wrong mention for your name. :)
and here the code we are using in routes
import { createController } from 'awilix-koa'
const api = genericService => ({
previewData: async ctx =>
ctx.ok(await genericService.previewData(ctx))
})
export default createController(api)
.prefix('/generic')
.post('/previewData', 'previewData')

The error occurs because it is attempting to call a function that does not exist. But according to your code above it should work fine. Are you sure this is the route you are hitting that produces the error?

Thank you for the update Jeff... :)
In Router file we can include multiple services and we can can call any service function.
Just for request:
is there any way that i can use the one service(services/a-service.js) in another service like (services/b-service.js).
will we use a-service function available in b-service.js
Thanks,
Surendra.

Yes you can, simply declare it in service-b constructor. 😄
Is this issue resolved? 😄


"Pseudoasynchronous" connect

As a stepping stone towards #15 that could potentially be done without a ton of disruption, allowing the interface to be in place without disrupting all the code, something like:

split the mitogen.service thread pool out so it is separate from the service dispatcher. There are already desires elsewhere to reuse this pool, but I've forgotten what they are.  [one at least is a desire to further blur the lines between 'service' and regular function call, the child function call dispatcher can begin running async functions with a new flag]
teach latches (finally) to be waitable using mitogen.select, so the pool can be triggered either by a latch in the local process or by an incoming message
make Router.connect() immediately return a Context, and defer the actual connection to the pool

Nothing else changes. That leaves just getting the interface and error handling right, which is probably the hardest part.

Rather than making the Ansible parallel setup code more generic, it could start to go away
Connection methods can then be migrated one at a time to fully async, without a "flag day" beyond the interface change (add it as a new router method?)
Planned new connection methods like libssh which absolutely need a thread during the agent auth phase already have a pool in place to run on

superseded: #419 introduced the majority of async connect in a single pass. the remaining stuff can be done on an as-needed basis


[Feature] Add clear button in Number System Calculator

Description
The clear / reset button will clear the input number from the input field and also add an option like "Select one option " in both dropdown menu.
Screenshots

Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Pls assign me this issue #758

Go ahead @ManasiDhotkar


Crash when viewing data for a specific object

When trying to detailed data for specific object, I get this crash:
Incorrect resolution sequence for Java constructor public constructor i() defined in m6.i[c@49bb83a] (x3.j: class m6.i)
Device Info: Samsung A10, android 10, One UI 2
App ver: 1.1.2-fdroid
Detailed Explanation:
When I zoom in on an area, I get a series of boxes showimg imformation about the objects in view.
When I click on one of these boxex, more info is shown however after few seconds, the app crashes.

Ok just saw that its duplicate of #23


fix: add ports for docker compose

This is WIP, but adding ports here at least allows for ingress for RPC commands.

Thanks Adam. Closing as stale.


[Bug] "Key path value '<0;1>' is not a valid uint32" - exported output descriptor is invalid and not recognized by Bitcoin Core

Preconditions:

Sparrow 1.7.1 portable, Windows 11.
Testnet.

Steps:

File -> Export Wallet -> Output Descriptor Export File -> Save.
Copy content of the saved file to Clipboard.
Open Bitcoin Core 24.0.1 (bitcoin-qt.exe -testnet) console.
Run the command:  importdescriptors '[{"desc": "wpkh([3f97f7d5/84h/1h/0h]tpubDCo3Gc8f31Hdz2cC8uUbHc1Hz96jpQaKWdkz4PE2ctFSKKQwG5MQ24Mm5nWDALMgRXrMgtStPfwNa4MvpDYXEmF2iWj4dyg1Z4j8gmSvyAr/<0;1>/*)#89q6exj7", "timestamp": "now"}]'

Actual result:
The descriptor is not accepted by Bitcoin Core:
[
{
"success": false,
"error": {
"code": -5,
"message": "wpkh(): Key path value '<0;1>' is not a valid uint32"
}
}
]
Expected result:
Sparrow creates an Output Descriptor that is accepted by Bitcoin Core and import is finished  successfully.
Logs (TRACE level)
sparrow.log

Multipath descriptors are specified in the proposed BIP 389, and support has already been added to several libraries: https://github.com/bitcoin/bips/pull/1354
Specifying multiple descriptors in a single descriptor string will be supported by Bitcoin Core when https://github.com/bitcoin/bitcoin/pull/22838 is merged. I believe this is an important improvement, as it makes output descriptors much more usable. I find a single, compact descriptor for a wallet is important when copying out as a backup, particularly onto durable media. More so when it is a multisig wallet that ideally requires a backup of all the xpubs.

I think that there is the misleading message that needs correction in Sparrow:

Apparently, the exported "output descriptor" is not compatible with Bitcoin Core.

To be fair it's compatible with minor edits. I think it goes too far to say it's misleading, which suggests I am intentionally trying to mislead users.
As application developers, we don't have the luxury of changing anything after release, and many users choose not to upgrade. The PR linked above could be merged tomorrow, which would the message true. If that happened, would you then consider your proposed "not compatible" suggested text misleading?

Yes, as a user, I would consider the text inaccurate even if Bitcoin Core merges the PR tomorrow. An example of a more accurate statement: "The output (...) description of the wallet will be compatible with Bitcoin Core version 25". Alternatively, there could "minor edits" communicated.
I don't want to suggest that the message was made in order to mislead users intentionally. I understand that things may be imperfect. As a matter of fact, I want to contribute and give suggestions to improve Sparrow. Also, I appreciate your time, skills and effort.

The output descriptor export has been changed in b15d6308 to have both multipath and single descriptors, with comments to guide the user:
# Receive and change descriptor (BIP389):
wpkh([959957d8/84h/0h/0h]xpub...uue/<0;1>/*)#u35nht4r

# Receive descriptor (Bitcoin Core):
wpkh([959957d8/84h/0h/0h]xpub...uue/0/*)#2ez7nqrd

# Change descriptor (Bitcoin Core):
wpkh([959957d8/84h/0h/0h]xpub...uue/1/*)#md8lw4n4


aquatone won't  run without ip address

I use the follow command to run aquatone:
cat test.txt | aquatone
when test.txt contains ip, which is
www.ksyun.com <IP_ADDRESS>

It run normally, but if I remove the ip, no results will show.
Is this normal ? Cause the doc show I can feed it with hostnames.
Thanks

I fixed this by building the latest source code, rather than using the release v1.4.3


Custom Date Filters not getting reset

Package
filament/filament
Package Version
v2.12.7
Laravel Version
v9.2
Livewire Version
v2.6
PHP Version
php 8.1
Bug description
i used the example here to create date filters
https://filamentphp.com/docs/2.x/tables/filters#custom-filter-forms
everything works but when i click "reset filters" dates are not reset
i checked filament admin panel demo and you have a date filter in "orders" page.
https://demo.filamentphp.com/shop/orders
there the reset button works, and dates have a muted default value which prompted me to check what happens if i add a default, and it worked. the only problem is i don't want them to have defaults.
so i added ->default(null) and now they reset, but this feels like a dirty fix.
also why do the default date on "orders" page have a muted color? are they normal defaults?
Steps to reproduce

create custom date filters for a table just copy pasting the docs example
try to reset dates after setting them

Relevant log output
No response

Please upgrade to v2.12.9

worked thanks


An empty project

An empty project, with just a readme, getting so many stars, is truly unbelievable.

A lot of people (including me) just use stars to keep track of projects by putting them on a list. Makes it easier to organize them and check back later when (hopefully) the code and weights are released.


[SAMZA-2772] Manage Jekyll dependencies with Gradle

Summary
This change moves Jekyll dependency management into Gradle. Contributors will no longer be required to install ruby & Jekyll by hand.
Changes

Gemfiles no longer manage dependencies.  This is done with the jruby-gradle-plugin Gradle plugin.

rubygems.org is still the source of Ruby libraries

The locally install MRI Ruby interpreter is replaced with JRuby.

This allows the Ruby interpreter to be a part of the Samza project.

Jekyll plugin changes

Rouge replaces pygments.rb. Rouge is native Ruby and does not have a python requirement.
Kramdown replaces Redcarpet because Redcarpet does not work with JRuby.
Both Kramdown & Rouge can run inside the JRuby JVM.

buildscript.gradle

jcenter.bintray.com is no longer active.
plugins.gradle.org has the required plugins

Testing
Testing was done with JDK 1.8 and on Linux.  I visually confirmed that content generated with JRuby looks like content generated by MRI Ruby by running two Jekyll instances at the same time.  Both Jekyll instances threw the same errors for missing content at /learn/documentation/latest.   I'm open to suggestions for improving confidence relating to the Jekyll plugin changes.
I also ran ./gradlew test which built successfully.

I'm not sure why the last commit (ccb932d) failed testing when the previous one (651a1bc) worked.  You can see the diff by clicking the ccb932d link above.
Is the samza-kafka_2.12:test task stable? I ran ./gradlew clean build test locally and the build was successful.  Let me know if I need to trigger another build with an empty commit or if it's something else.  Thanks

I'm open to suggestions for improving confidence relating to the Jekyll plugin changes.

One thing I thought of was to list & compare the generated file names in _site.  I found some of the javadoc files were missing with the jruby generated site.  I think I need to revisit the Jekyll plugin changes.

I found the following differences after generating documents with Jekyll using both MRI Ruby & Jruby.  Input was generated by running find on the _site directory and saving the output to a sorted text file.
$ sdiff -Ws -w 220 ~/mri_ruby_docs ~/jruby_docs
./Gemfile                                                                                <
./Gemfile.lock                                                                                <
./index.md.bak                                                                                <
./meetups/aug-2016.md                                                                          <

The missing Gemfile, Gemfile.lock, & index.md.bak files I'm not concerned with as they were removed as part of this change.  The meetups/aug-2016.md file was a surprise.  FWIW: it's not referenced in the MRI Ruby build or at https://samza.apache.org/meetups so I'm not concerned about it right now.

FYI: Removing the Jekyll incremental build flag resolved the file name differences I found in the previous comment.

Good catch.  I updated publish-site.sh and tested the best that I could as I don't have SVN write access.  Let me know if it doesn't work correctly.  Thanks


Fixed version # in POM

Coverage increased (+0.006%) to 52.103% when pulling 6827608b31c1e3e08ae371d27c38716810fb8012 on dcy2003:pom-fix into f7ea3e2f07e86cc199d6b9ae25c0480fef87379c on ngageoint:master.