[WFCORE-5086] Embedded mode sets jboss.server.content.dir incorrectly

JIRA: https://issues.redhat.com/browse/WFCORE-5086

@jamezp could you review when you have a chance please?

@spyrkob This has a checkstyle problem. The change seems fine.

Sorry, should be fixed now

Core - Full Integration Build 9882 outcome was FAILURE using a merge of 109ce1dd33ce180b5f85175a041a7fbcd4cfc218
Summary: Execution timeout (new); tests passed: 6429, ignored: 101 Build time: 05:01:22

Core - Full Integration Build 9884 outcome was FAILURE using a merge of 109ce1dd33ce180b5f85175a041a7fbcd4cfc218
Summary: Execution timeout; tests passed: 6448, ignored: 102 Build time: 05:01:12


Enable downloading a particular insider commit.

Useful when the latest insiders is broken, and you can't test against stable.
If you are ok with this feature, I will add docs and tests

Ok now this should be ready to go. It was working for downloadAndUnzipVSCode but not runTests. Also, I added a test but I think that documenting it in readme could just confuse people- this is not what we want to encourage people to typically use.


Office League - Add players during league creation

After discussion with tsi:

If defined as admin in create league -> player
In invitation: Allow only email or existing player
Noticed bugs
Do not allow duplicate


[WIP] Exploring the possibility to have an FLP sandbox without /test-resources

Feature: #1631
Tested

[x] generates an html and cdm file that works with a simple single app preview
[ ] multiple apps
[x] adaptation project preview
[x] adaptation project editing

@Klaus-Keller, I am closing this one. It seems not be required anymore.


Safety switch circuit braker doesn't work if RC signal is not present when booting

Minor issue, haven't investigated it yet

Behaviour changed now, seems to be fine.


Fix issue with description of modes

The defaults PR (#99) moved multiple as the mode to the top as it is the default, but failed to swap the description of single vs. multiple. This corrects that.

@ehsandeep


abort trap 6 mac os

When i launch Quest-Discord-Precense-Client i get this error
at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter)
at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
at System.IO.FileStream.OpenHandle(FileMode mode, FileShare share, FileOptions options)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at System.IO.StreamReader.ValidateArgsAndOpenPath(String path, Encoding encoding, Int32 bufferSize)
at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks)
at System.IO.File.InternalReadAllText(String path, Encoding encoding)
at System.IO.File.ReadAllText(String path)
at Quest_Discord_Presence_Client.Client.LoadConfig() in /home/runner/work/Quest-Discord-Presence-Client/Quest-Discord-Presence-Client/src/Client.cs:line 105
at Quest_Discord_Presence_Client.Client..ctor(String[] args) in /home/runner/work/Quest-Discord-Presence-Client/Quest-Discord-Presence-Client/src/Client.cs:line 34
at Quest_Discord_Presence_Client.Client.Main(String[] args) in /home/runner/work/Quest-Discord-Presence-Client/Quest-Discord-Presence-Client/src/Client.cs:line 44
Abort trap: 6
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]

There are some issues with the client and MacOS currently.
It works for some, but not for others.
In the meanwhile, I'd recommend you use the client by MagMagic instead: https://github.com/madmagic007/Oculus-Quest-Presence

There are some issues with the client and MacOS currently.
It works for some, but not for others.
In the meanwhile, I'd recommend you use the client by MagMagic instead: https://github.com/madmagic007/Oculus-Quest-Presence


🐛 FromFactory doesn't honor the Range attribute

Describe the Bug
It's not really a bug, more like an unfilled expectation.
I expected the System.ComponentModel.Annotations.RangeAttribute to be honored by the FromFactory method but this is not the case.
Scenario
I'm adding a customization to create a System.Version and I wanted to constraint the numbers used for generating the version.
fixture.Customize<Version>(o => o.FromFactory(([Range(0, 2)] int major, [Range(0, 10)] int minor, [Range(0, 100)] int patch) => new Version(major, minor, patch)));

Expected Behavior
The components of the constructed Version should be within the specified ranges.

@Kralizek to me it sounds more like a feature request then a bug

I was uncertain it if was supposed to work or not :)
Is the Range attribute (and the other data annotations) considered only when decorating properties?

@Kralizek it is supposed to work for properties, fields, and method parameters but not for that lambda in the .FromFactory since it doesn't pass through the same deconstruction pipeline as the other code

@Kralizek this feature touches the weird object graph thing aka NodeComposer, which I am a bit afraid of. 😅
I think Mark might have been the only one to truly understand it.
I will try to figure it out but it might take me a while.
I'll open another feature request to replace this bug report.

I appreciate that :)


python310Packages.pytorch-lightning: 2.0.2 -> 2.0.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pytorch-lightning is: Lightweight PyTorch wrapper for machine learning researchers
meta.homepage for python310Packages.pytorch-lightning is: https://pytorch-lightning.readthedocs.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.3 with grep in /nix/store/fgpkl2z0plnymfakjml9sg57xn3amdx6-python3.10-pytorch-lightning-2.0.3
found 2.0.3 in filename of file in /nix/store/fgpkl2z0plnymfakjml9sg57xn3amdx6-python3.10-pytorch-lightning-2.0.3

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
larynx-train
python310Packages.larynx-train
python310Packages.pytorch-lightning

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fgpkl2z0plnymfakjml9sg57xn3amdx6-python3.10-pytorch-lightning-2.0.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.pytorch-lightning https://github.com/r-ryantm/nixpkgs/archive/5029637bbd3d27e44c524953ed65f98d4eee4ef9.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/fgpkl2z0plnymfakjml9sg57xn3amdx6-python3.10-pytorch-lightning-2.0.3
ls -la /nix/store/fgpkl2z0plnymfakjml9sg57xn3amdx6-python3.10-pytorch-lightning-2.0.3/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

2 packages built:

larynx-train (python310Packages.larynx-train)
python310Packages.pytorch-lightning

Maintainer pings
cc @tbenst for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pytorch-lightning is: Lightweight PyTorch wrapper for machine learning researchers
meta.homepage for python310Packages.pytorch-lightning is: https://pytorch-lightning.readthedocs.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.0.4 with grep in /nix/store/j41dx0h1yiaqdf5khlqliw1bhk032gl7-python3.10-pytorch-lightning-2.0.4
found 2.0.4 in filename of file in /nix/store/j41dx0h1yiaqdf5khlqliw1bhk032gl7-python3.10-pytorch-lightning-2.0.4

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
piper-train
python310Packages.piper-train
python310Packages.pytorch-lightning

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j41dx0h1yiaqdf5khlqliw1bhk032gl7-python3.10-pytorch-lightning-2.0.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.pytorch-lightning https://github.com/r-ryantm/nixpkgs/archive/4c85d73eeaa9a5f80316c8d3e4cd7f0f4be48478.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/j41dx0h1yiaqdf5khlqliw1bhk032gl7-python3.10-pytorch-lightning-2.0.4
ls -la /nix/store/j41dx0h1yiaqdf5khlqliw1bhk032gl7-python3.10-pytorch-lightning-2.0.4/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

2 packages built:

piper-train (python310Packages.piper-train)
python310Packages.pytorch-lightning

Maintainer pings
cc @tbenst for testing.


Error "Lib doesn't have a run script" should be thrown for dev-version.

Error about "Library does not have a run script" doesn't throw when version is dev.
~ > haxelib list flixel
flixel: [3.3.12]
~ > haxelib run flixel
Library flixel version 3.3.12 does not have a run script
~ > haxelib list heaps
heaps: git [dev:/Users/ak/Developer/Haxe/libs/heaps/git]
~ > haxelib run heaps
~ > # nothing

I'm not sure, is this planned behaviour?

Doesn't happen anymore, and the code for run doesn't seem to ignore missing run.n for dev version.

Well, this exact case reproduces, but that's because heaps actually HAS a run.n file. If I delete it, it complains, so I'm closing this issue.


Add contour-gateway

This adds the Contour gateway CRDs.
https://projectcontour.io/docs/main/config/gateway-api/
Since Contour 1.28+ it supports the Gateway API v1.0.0.

Hey!
Thanks for the contribution and sorry for the late reply;
Can you please run a make ci to generate the workflows/auto-setup for the new library?

Sure. I ran make .github/workflows/main.yml as make ci doesn't exist in the current Makefile.


chore: Migrate angular RELEASE

awesome work!

Thanks!

fyi noticed that the angular-sdk app triggers a 400/401 requests after login
but this reproduces also in the previous repo, so I'll open separate issue

👍

lets add environment.development.ts to gitignore and merge 👍

Done


Metrics created from a cloud_run_revision have resource type generic_node

Metrics uploaded to Cloud Monitoring from a Cloud Run service
(despite initializing otel with the GCP resource detector), have "Resouce Type: generic_node
If this could be fixed in a coming release it would be amazing. Thanks.

Thanks @dgnemo!  This is on our radar, and we will try to have this done soon.
We are tracking it in https://github.com/GoogleCloudPlatform/opentelemetry-operations-go/issues/735, so i'll close this if thats alright.


Support ?raw query params on ONNX models

/kind feature
Describe the solution you'd like
The ONNX predictor extension check does not allow for query parameters such as ?raw=true to be appended to the storage URI:
 "error": "admission webhook \"inferenceservice.kserve-webhook-server.validator\" denied the request: Expected storageUri file extension: '.onnx' but got '.onnx?raw=true'"

https://github.com/kserve/kserve/blob/v0.7.0/pkg/apis/serving/v1beta1/predictor_onnxruntime.go#L48-L57
It would be useful for this validator to allow for query params such that models from the onnx model zoo could be used natively.

Fixed in kserve 0.11.o

#3014


Route config such as "foo/:id" or "foo/x" didn't work

It seems failed somewhere, but I didn't see any error in server console
Even though I have development=1, it tried to load bundle resources, and saw error in browser console:
Uncaught Error: Script error for: app/bundles/app.js
If I change foo/x to foo_x, then it works.

Found the error, which is not related to route config. So close the issue.


status indicator for single-point queries

We have a spinner now, and it's fast enough I don't think we need anything more.


Provision the Client VM with Less Resource

The client vm is now resourced the same as the server: n1-standard-2 (2 vCPUs, 7.5 GB memory)
This can probably be lower to save some $$$.

Per Andrew: The smallest non-mirco instance should be good
Micro doesn't have enough ram

However, Joe's benchmarkings show that smaller VM takes longer time to spin up, due to longer time to install dependencies (basically, all of Foseti).  So, these need to be stripped down to only install what the client VM needs.


Error when using nested BaseSettings classes

Checks

[x] I added a descriptive title to this issue
[x] I have searched (google, github) for similar issues and couldn't find anything
[x] I have read and followed the docs and still think this is a bug

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.8.2
            pydantic compiled: True
                 install path: C:\Users\ricardoch\VirtualEnv\fastapi\Lib\site-packages\pydantic
               python version: 3.6.8 (tags/v3.6.8:3c6b436a57, Dec 24 2018, 00:16:47) [MSC v.1916 64 bit (AMD64)]
                     platform: Windows-10-10.0.19041-SP0
     optional deps. installed: ['dotenv', 'email-validator', 'typing-extensions']

import pydantic
from pydantic import BaseSettings

class PostgresSettings(BaseSettings):
    USER: str
    PASSWORD: str
    HOST: str
    PORT: int
    DB: str

    class Config:
        env_prefix = "POSTGRES_"

class Settings(BaseSettings):
    POSTGRES: PostgresSettings
    PROJECT_NAME: str
    FASTAPI_ENV: str
    TESTING: bool = False

    class Config:
        case_sensitive = True

settings = Settings(_env_file='settings.env')
print(settings)

produces following error
Traceback (most recent call last):
  File "...", line 42, in <module>
    settings = Settings(_env_file='settings.env')
  File "pydantic\env_settings.py", line 36, in pydantic.env_settings.BaseSettings.__init__
  File "pydantic\main.py", line 406, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for Settings
POSTGRES
  field required (type=value_error.missing)

It seems that the sub-class PostgresSettings(...) does not read the '.env' file.
It works however if I define it like this
class Settings(BaseSettings):
    POSTGRES: PostgresSettings = PostgresSettings(_env_file='settings.env')
    PROJECT_NAME: str
    FASTAPI_ENV: str
    TESTING: bool = False

    class Config:
        case_sensitive = True

Here is my 'settings.env' sample
POSTGRES_USER=qwe
POSTGRES_PASSWORD=asd
POSTGRES_HOST=zxc
POSTGRES_PORT=000
POSTGRES_DB=iupo

PROJECT_NAME=hello
FASTAPI_ENV=there
TESTING=true

Your .env file I think should be modified:
POSTGRES='{"USER": "", "PASSWORD": "", "HOST": "", "DB": "", "PORT": 5432}'
PROJECT_NAME =A
FASTAPI_ENV =B
TESTING=False

You can check the docs: https://pydantic-docs.helpmanual.io/usage/settings/#parsing-environment-variable-values

Or use a double underscore when defining nested variables.
https://pydantic-docs.helpmanual.io/usage/settings/#parsing-environment-variable-values


is it possible to access aws redshift ? currently im using node-redshift npm.

but its written that its not stable...and this git much more reliable..

I have never heard of aws redshift before, so don't know off-hand. This module will work with any service that uses the MySQL wire protocol, if it uses that.

is it possible to add aws driver to this lib?

I'm not familiar with aws red
shift. This module will work with any service that uses the MySQL wire protocol, if it uses that.

Redshift has its own custom protocol, for which Amazon provides ODBC and JDBC drivers for use by BI and data warehouse tools.  I believe behind the scenes it's really a flavor of Postgres, not MySQL.  Take a look at https://www.npmjs.com/package/node-redshift, which uses the pg module to connect.

Thanks, @femto113 . Then yea, it wouldn't be added to this module, since this module is to provide the MySQL protocol.

@femto113 thanks, I finally use node-redshift...it seem to be much less reliable than odbc..but easier for me, maybe when delivery is done and time to breath will come :), i will deep dive into it.


Split command argument for training path.

Split original argument --train into --train-laughs and --train-non-laughs.
It prevents shell from expanding prefixes as a list of files.
Also update README accordingly.
Solves #2

So that is a good start, but right now if the shell expands a wildcard to the path names, that won't be handled correctly by the Python code.  So two changes need to happen, one to inform argparse that you might have multiple values for each of those parameters, and two to detect if we just got a single input, in which case run glob() or if we got a list of individual files, in which case skip the glob().
For example, given:
#example1.py
import argparse
parser = argparse.ArgumentParser()
parser.add_argument('--param')
print(parser.parse_args())

Results in:
$ python example1.py --param file1 file2 file3
usage: example1.py [-h] [--param PARAM]
example1.py: error: unrecognized arguments: file2 file3

What you want is probably the nargs argument with "+", like so:
#example2.py
import argparse
parser = argparse.ArgumentParser()
parser.add_argument('--param', nargs='+')
print(parser.parse_args())

Results in:
$python example2.py --param file1 file2 file3
Namespace(param=['file1', 'file2', 'file3'])

So then you can add a check like if len(laughs) == 1: laughs = glob(laughs[0]) or similar in the appropriate place.

OK, I had a different behavior in mind. I thought that one would only pass the path to the directories containing files, having one directory per type of audio sample.
For example :

/my/path/to/laugh/files is a directory containing your f*.wav
/my/path/to/nonlaugh/files is a directory containing your d*.wav
calling python laughr.py --model model.h5 --train-laughs /my/path/to/laugh/files --train /my/path/to/nonlaugh/files would do the job

Do you prefer being able to pass a wildcard to the filenames as a parameter ?

Oh, I see what you're going for.  That would change how the data files are laid out, but probably for the better I think.
Can you remove the /files reference (for clarity) leaving it just the directory portion of the paths, so /my/path/to/laughs and then I think it looks good to merge!

:fireworks:


Docs for install cuda 11.0 and cudnn 8

Now that tensorflow 2.4.0 is almost out with cuda 11.0 and cudnn 8 support, it would be nice to have the instructions updated for GPU installation.

Hi, I'm willing to work on this issue. However, there are many issues at the moment with RTX cards running on CUDA 11.0. Some suggest that 11.1 works while 11.0 doesn't. Personally, I was facing issues even while using the TF docker container until I was facing issues even while using the TF docker container. I stumbled across an article by lambda stack which allowed me to use TF 2.3 on my new RTX 3080.
So I suggest waiting on this issue for a little while longer until the issues have been sorted out. In the meantime, I'll start up a pull request since I think we should refactor the GPU support page.

Some suggest that 11.1 works while 11.0 doesn't.

@nluehr Is this true?  This could be a reason to move to 11.1 or 11.2 sooner rather than later.
CC @pkanwar23

FYI. GPU instructions have been updated. There might be minor omissions, which I'll fix soon.

I was trying to reproduce the instruction here I was doing it in version20.04.
I started by running ubuntu-drivers devices to find the recommended drivers for my version. The recommended version is nvidia-driver-455 - third-party free recommended.
Using the instructions here.
I replaced 1804 with 2004 as shown in the lines below.
wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/cuda-ubuntu2004.pin
sudo mv cuda-ubuntu1804.pin /etc/apt/preferences.d/cuda-repository-pin-600
sudo apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/7fa2af80.pub
sudo add-apt-repository "deb https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/ /"
sudo apt-get update
wget http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu2004/x86_64/nvidia-machine-learning-repo-ubuntu2004_1.0.0-1_amd64.deb
sudo apt install ./nvidia-machine-learning-repo-ubuntu2004_1.0.0-1_amd64.deb
sudo apt-get update
# Install NVIDIA driver
sudo apt-get install --no-install-recommends nvidia-driver-455
sudo reboot
Reboot. Check that GPUs are visible using the command: nvidia-smi
However, I was stuck when I tried to replace the following line because ubuntu 2004 has no libnvinfer7_7.1.3-1+cuda11.0_amd64.deb counterpart that is available in 18004.
check here.
So my question is, is their a package i need to install in version 2004 that will replace the libnvinfer7_7.1.3-1+cuda11.0_amd64.deb` version in ubuntu 18?

I was trying to reproduce the instruction here I was doing it in version20.04.
I started by running ubuntu-drivers devices to find the recommended drivers for my version. The recommended version is nvidia-driver-455 - third-party free recommended.
Using the instructions here.
I replaced 1804 with 2004 as shown in the lines below.
wget https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/cuda-ubuntu2004.pin
sudo mv cuda-ubuntu1804.pin /etc/apt/preferences.d/cuda-repository-pin-600
sudo apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/7fa2af80.pub
sudo add-apt-repository "deb https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/ /"
sudo apt-get update
wget http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu2004/x86_64/nvidia-machine-learning-repo-ubuntu2004_1.0.0-1_amd64.deb
sudo apt install ./nvidia-machine-learning-repo-ubuntu2004_1.0.0-1_amd64.deb
sudo apt-get update
# Install NVIDIA driver
sudo apt-get install --no-install-recommends nvidia-driver-455
sudo reboot
Reboot. Check that GPUs are visible using the command: nvidia-smi
However, I was stuck when I tried to replace the following line because ubuntu 2004 has no libnvinfer7_7.1.3-1+cuda11.0_amd64.deb counterpart that is available in 18004.
check here.
So my question is, is their a package i need to install in version 2004 that will replace the libnvinfer7_7.1.3-1+cuda11.0_amd64.deb` version in ubuntu 18?

Is this still an issue.

this has been fixed, please refer to link, moving this to closed status.


how to set marker's initial position at bottom of the MapScreen

Is this a bug report?
No
Have you read the Installation Instructions?
Yes
Environment
react-native:0.55.4
react: 16.3.1
react-native-maps: ^0.21.0

Actual Behavior
Initially marker is showing at the center of the Map Screen
But as per my requirement it should at the bottom of the Map Screen

Expected Behavior
Marker should be at bottom of the Map Screen

I have the same problem... Any ideas?


Fix missing yaml module

Short Description: Fix missing yaml module
Fixes:

Fix missing yaml module

Last commit has spelling mistake

@solderzzc Sorry, I fixed it. The correct package name is pyyaml not pyaml

thanks :)


[Feature Request] Add per-package pacman argument

I would imagine this working by adding an 'Edit' action where you can add common arguments by check boxes, and a text box for adding custom arguments. Would also help solve #64 as you could specify a pgp key.
A few useful pacman argument:

--skippgpcheck (when pgp keys don't exist)
--noconfirm (for package conflicts)

Hey, thats a good idea.
--noconfirm is already added to every build. See the current command here: https://github.com/Lukas-Heiligenbrunner/AURCache/blob/master/backend/src/builder/build.rs#L255

Hmm. I still get this error when trying to build obs-studio-tytan652
:: There are 2 providers available for jack:
:: Repository extra:
    1) jack2  2) pipewire-jack
Enter a number (default=1):

:: There are 3 providers available for opengl-driver:
:: Repository extra:
    1) mesa  2) mesa-amber  3) nvidia-utils
Enter a number (default=1):
:: Calculating conflicts...
:: Calculating inner conflicts...

:: Inner conflicts found:
    ffmpeg: ffmpeg-obs (ffmpeg)

:: Conflicting packages will have to be confirmed manually
error: can not install conflicting packages with --noconfirm
No files found in build directory

Log attached
22d1e9294cfd91d71493e992e2d7903460955986b97f2af3fda4fde1694a7d84-json.log

fixed in #74


Can't use latest Alamofire and RxSwift with Moya 8.0.1

I have the following podfile:
pod 'Alamofire', '~> 4.3'
pod 'RxSwift', '~> 3.2'
pod 'RxCocoa', '~> 3.2'
pod 'Moya/RxSwift', '8.0.1'
When I run pod update I get:
[!] Unable to satisfy the following requirements:

Alamofire (~> 4.3) required by Podfile
Alamofire (~> 4.2.0) required by Moya/Core (8.0.1)
RxSwift (~> 3.2) required by Podfile
RxSwift (~> 3.2) required by Podfile
RxSwift (~> 3.1) required by RxCocoa (3.2.0)
RxSwift (~> 3.1.0) required by Moya/RxSwift (8.0.1)

Seems like a problem with these lines in Podspec:
ss.dependency "RxSwift", "~> 3.1.0"
ss.dependency "Alamofire", "~> 4.2.0"

change to "~> 3.0" && "~> 4.0" could fix the problem, but there might be a reason why we have it this way (I'm out of the loop lately). Because of this we should discuss the fix with @Moya/contributors first. We could just higher up the versions of pods as well.

Let's see if we can update our dependencies.

It would actually be really nice to have some sort of dependency update check somewhere to keep us up to date. What do you think, @Moya/contributors? Should I create a separate issue?

Or we should do what @sunshinejr suggested, using just ~> 3.0 and ~> 4.0 respectively. Not sure what is the best option here.

I would go with @sunshinejr's suggestion for the time being.

@andreyfel Moya 8.0.2 was release and should fix your problem. Can you please update and let us know if you still have issues? :wink:

Thank you guys for the quick reaction! It resolved issue with Moya, but I still have the same issue with Moya-ObjectMapper. Opened an issue there https://github.com/ivanbruel/Moya-ObjectMapper/issues/45


Question about control_primitives and control_primitives_context

There seem to be functions of the same name under the two folders, one folder is used for skill manager agent while the other is used for action agent, I'm wondering what is the reason two function implementations of the same name is needed? Could anyone help me understand?

Hi, thanks for your interest in this project! This is a trick we use to shorten the context:
The control_primitives refer to the actual functions that are executed on the JavaScript side. To provide the bot with environmental feedback, we incorporate multiple safeguards and chat messages.
On the other hand, the control_primitives_context contains functions that are displayed within GPT's context. They serve as examples for GPT on how to utilize the Mineflayer API and our control primitives. We don't want GPT to see those if...else safeguards.

You're awesome! @xieleo5 Thanks!


Fix vision samples

adds region tags, static images, and updates authentication

@tmatsuo we are waiting for a fix on the Speech API that should go out next week. I don't really want to update our samples to fix it. I agree it'd be pretty slick to only run select samples for tests!
I added logic to write a bounding box for vision samples. LMK what you think.


correct #143 ARIMA forecast errors if p and q are both zero

when p and q are both zero it ignores a step

Just curious if this is going to get merged in. I ran in to the same issue

My fault... I gave up of the project where I was trying to use spark-ts.
But come on, I can add the space. Sorry about the delay.

You are the best, thanks!
-JD

On Nov 23, 2016, at 4:50 PM, Tiago Dinis da Fonseca<EMAIL_ADDRESS>wrote:
My fault... I gave up of the project where I was trying to use spark-ts.
But come on, I can add the space. Sorry about the delay.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/sryza/spark-timeseries/pull/171#issuecomment-262664887, or mute the thread https://github.com/notifications/unsubscribe-auth/AA6dsJa5rzCUfF_lgTFnPgc-pFJSKWfkks5rBN9kgaJpZM4KWBYo.

LGTM! Merging this.


Switch to using declarations

Similar to file-scoped namespaces, let's get rid of some more nesting?
There's one instance where it wasn't switched, there's more interaction with the modified stream in the same test case there so I thought it's acceptable to keep like that.

Turns out there was one more block-scoped namespace, not sure how VS missed that the first time.

@Regenhardt can you check again with the latest main if its merge able? If it still fits, please merge your changes. ❤

Rebased, found another using statement, everything works :)


Remove non-actionable config validation warning

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
When setting Helm value apiRateLimit or otherwise providing the api-rate-limit config value in Cilium's ConfigMap, then Cilium Agent produces non-actionable log messages with level warning, like the one below:
level=warning msg="Unable to validate option api-rate-limit value of type stringToString" subsys=config

There is nothing one can do about it, the api-rate-limit setting is actually valid and everything works as expected. However, the log message is misleading as it suggest that something is wrong and that one might have to fix the api-rate-limit config.
Those log messages are generated by https://github.com/cilium/cilium/blob/v1.15.6/pkg/option/config.go#L4190, because the config validation logic does not know how to validate the api-rate-limit (which does not mean that the config is wrong). I suggest we either

(A) completely remove that log message, as it is not actionable at all
(B) or at least change the log level from warning to info and adapt the wording to make it more clear that there is nothing wrong with the config.
(C) or implement proper validation for the stringToString type and only log if that validation fails

Cilium Version
1.15.6
Kernel Version
6.1.90
Kubernetes Version
1.29.4
Regression
No response
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Cilium Users Document

[ ] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

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

(A) completely remove that log message, as it is not actionable at all

I worry that this is generic code that could protect users who misconfigure other flags. Not sure if this is the right path.

(B) or at least change the log level from warning to info and adapt the wording to make it more clear that there is nothing wrong with the config.

Related to above: If there is an error but for a different flag, then setting it to info could lead the user to think that the error isn't a problem when it actually is a problem.

(C) or implement proper validation for the stringToString type and only log if that validation fails

I think this proposal makes the most sense, add a new case to the switch for stringToString and validate that format.

@alex-berger would you like to implement (C)?

@aanm implemented (C) in https://github.com/cilium/cilium/pull/33779.

https://github.com/cilium/cilium/pull/33779 caused a regression and was reverted in https://github.com/cilium/cilium/pull/34277.
@joestringer @aanm Can we please reopen this issue.


committed branch showing error

Does this occur consistently?
Repro steps:

Action: appService.Deploy
Error type: Error
Error Message: fatal: your current branch 'main' does not have any commits yet
Version: 0.24.9
OS: win32
OS Release: 10.0.22623
Product: Visual Studio Code
Product Version: 1.79.2
Language: en

Call Stack
extension.bundle.js:2:2208177extension.bundle.js:2:2208177
rejected extension.bundle.js:2:2206767

Looks like you haven't committed any changes to your repository yet.  Please reopen if it doesn't help.


style(all): Improve coding style (using rust-clippy)

Coverage remained the same at 89.354% when pulling 0f71490c61c4e607904a9b5454da22f6b9da3fb8 on amousset:style-improvement into 6fe2ef679b61e3058e511f348ade8c45c1baab99 on lettre:master.


Unable to produce relative file paths for attachments in file: field when exporting

[x] I have verified that I am on the latest release of BBT (https://github.com/retorquere/zotero-better-bibtex/releases/latest) and Zotero
[x] I am posting a single question, bug or feature request
[x] I have included a descriptive subject of the problem
[x] I am available for follow-up questions and testing

My data directory is set to ~/zotero (with the storage folder internally that symlinks to another location so I can sync it across computers) in the Zotero preferences and my pdfs are exported via Zotfile to ~/literature. I saw an explanation for the current scheme of generating relative vs. absolute paths for the file: field in #654, but I am still unable to produce relative paths regardless of my selected export location. The ~/zotero/storage folder contains mostly html content from snapshots because I relocate the pdfs with Zotfile.
I have exported my .bib file to ~/zotero, ~, and ~/literature, but every time it produces an absolute path in the file: field. This applies for both the html content in ~/zotero/storage and the pdf content in ~/literature. Given the current implementation I don't really expect the pdf files to be defined relative paths under any case, but I am surprised the html content was not defined as a relative path.

If you export to ~/literature where your attachments live, the path should automatically be relative. I will have a look.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>55 ("fixes #935 (I think)").

@retorquere This build is working for me. Many thanks.

A new release (.194) will be out soon, but it's just what you have now with a formal label on it. You will be upgraded autommatically, or you can force-update in the addons panel in 10 minutes or so when the tests have ran.


Adding Gradle org.jlleitschuh.gradle.ktlint-idea plugin.

Still having trouble having IntelliJ format the Kotlin code with the same style as the ktlint plugin.
This commit also adds the  org.jlleitschuh.gradle.ktlint-idea, in addition I ran the the ktlintApplyToIdea task.

What are the issues/diferences you're running into?

I'm not having a problem perse, just an unmet expectation. My expectation is that if I run the ktlintFormat Gradle task and see no files changed; therefore I should no see any formatting change if I open any Kotlin file and apply formatting changes via IntelliJ.  Right now this is not the case, for example the DgsGraphQLCollatedMetricsTagsProvider.kt file. If I run the task I see no change but If I apply the format via IntelliJ I do.
This PR doesn't fix things, or at least yet.


Parse and infer dom.generated.d.ts

Codecov Report
Attention: Patch coverage is 93.10345% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 82.84%. Comparing base (d7288b9) to head (5efe336).

Files
Patch %
Lines

src/Escalier.Interop/Parser.fs
94.54%
3 Missing :warning:

src/Escalier.TypeChecker/Visitor.fs
33.33%
2 Missing :warning:

src/Escalier.Interop/Infer.fs
95.65%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #182      +/-   ##
==========================================
+ Coverage   82.18%   82.84%   +0.66%
==========================================
  Files          21       21
  Lines        7717     7787      +70
  Branches     1144     1150       +6
==========================================
+ Hits         6342     6451     +109
+ Misses       1375     1336      -39

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


Creating a function from another function

Wraps a function to throw an exception when running for a long time.
To control the execution time, it is required to call a function inside
some other function - the call function.
The example shows a simple demonstration of working with a function with no
arguments. But what if you want to wrap a function and pass arguments to it
through the wrapper function.
The call function in the example is used to call a function with no arguments.
The callv2 function is used to call a function, passing arguments to it. Now
for this you need to use Function.apply. This leads to inconvenience when
passing arguments, to disabling the static check of a function call.
It is proposed to implement the ability to define types for a function
based on the types of another function. See callv3, callv4, ... for possible
syntax examples.
The implementation of the feature will make it possible to write wrappers for
functions while maintaining static control and ease of specifying the types
of parameters, the type of result.
Maybe the task can be solved somehow with the help of annotations, code
generators. I don’t know, I haven’t tried it yet, but I want to get the
simplest way to solve it.
The syntax can be anything, just a few examples are listed. The main thing is
that the problem can be solved.
class TimeoutFunction<T extends Function> {
  final T _func;
  final Duration timeout;

  TimeoutFunction(this._func, this.timeout);

  Future<dynamic> call() async {
    var completer = Completer();

    var timer = Timer(timeout, () {
      assert(!completer.isCompleted);
      completer.completeError('timeout');
    });

    Future.value(_func()).then((result) {
      if (!completer.isCompleted) {
        timer.cancel();
        completer.complete(result);
      }
    });

    return completer.future;
  }

  Future<dynamic> callv2({
    Map<Symbol, dynamic> namedArgs = const {},
    List<dynamic> posArgs = const [],
  }) async {
    var completer = Completer();

    var timer = Timer(timeout, () {
      assert(!completer.isCompleted);
      completer.completeError('timeout');
    });

    Future.value(Function.apply(
      _func,
      posArgs,
      namedArgs,
    )).then((result) {
      if (!completer.isCompleted) {
        timer.cancel();
        completer.complete(result);
      }
    });

    return completer.future;
  }

  // The "@" character emphasizes that the task is solved at the compilation level.
  @AboutType<T>.returnType
<EMAIL_ADDRESS>async {
    //...
  }

  @AboutType<_func>.returnType
<EMAIL_ADDRESS>async {
    //...
  }

  @MakeFunction<T, callv5> {
    // .....
  }
}

I don't want to enable reflection on function types, where you can dynamically create a function of any type that you can think up  in the program.
I also don't want to enable reflection over argument lists (converting them into lists and maps, and reifying them back).
That's not the correct level of abstraction.
It does mean that we have no way to abstract over function signatures. If you don't know the parameter list statically, there is no way you can create a function with that parameter list at runtime.
(Which is good for code-size, bad for flexibility.)
A more suitable solution could be something like:
/// Returns a function with the same type as [function].
///
/// When the returned function is invoked, the [around] function is called first.
/// It can then call its `original` function argument when it wants to transfer control to
/// the wrapped [function], which is then invoked with all arguments provided
/// to the returned function.
/// The `original` function never returns. Calling it effectively works like returning from
/// the [around] function at the call-point (or like it threw an uncatchable exception).
/// The [around] function can intercept the return using `try`/`finally`, but it must
/// eventually throw or let the returning from calling `original` complete.
/// If the returning completes, the call to the returned function completes with the
/// same result. If [around] ends by throwing, the call to the returned function
/// throws the same error and stack trace.
F wrap<F extends Function>(F function, Never Function(Never Function() original) around);

The obvious short-coming is async functions. If function returns a future, do we want to await it before returning from around? Maybe, probably, but not certainly. So maybe we need two different functions.
Another approach, more promising, but also demanding more changes to the language, is to actually allow abstracting over parameter lists. Maybe using record, so Function is defined as
class Function<out R, in P extends Record> {
  static R invoke<out R, in P extends Record>(Function<R, P> function, P arguments) => function(...arguments);
}

Obvious short-coming is that a record doesn't have optional fields, so an int Function(int, [int]) would be a subtype of both Function<int, (int,)> and a Function<int, (int, int)> (aka. int Function(int) and int Function(int, int)), but won't have a Function<R, P> representation itself.
Still better than nothing, and with a proper argument-list record spread operator, it's pretty usable.
Even just being able to abstract over return type is useful. Then Function.apply would be
  external static R apply<R>(Function<R, Never>, List<Object?> positional, [Map<Symbol, Object?>? named]);

and would keep the proper return type.

This is not about dynamic function wrappers. @AboutType.returnType will be replaced by the compiler with a static type that matches the return type of the template function. This is about developing a template engine for creating wrapper functions.

And @AboutType.parameter will be replaced by the compiler with a list of parameters. Some analogue of define from c/c++.

Fine. As a dart expert, what would be your advice for writing a function that wraps another function and controls how long it takes to execute. This function should be part of a library that allows you to set the maximum execution time for a function. Practical use? For example, there is a certain system of real time. The task must be completed within a certain time.

Limiting execution time only applies to asynchronous functions to begin with. There is no way to preempt a running synchronous computation without its cooperation. At least not inside the same isolate, and all isolate communication is asynchronous too.
We can't abstract over function signatures, so I'd limit myself to nullary functions and expect you to provide the parameters inside that function.
That means that instead of doing someFunction = addTimeout(duration, someFunction); and having it work for every type of function, you need to know the parameter type at the point where you wrap and do:
someFunction = (int arg1, int arg2) => someFunction(arg1, arg2).timeout(duration);

or, for a synchronous function, I'd spawn an isolate running it, like Isolate.run does, but keep the isolate around so I can kill it when a local timer times out. Still asynchronous in the local isolate.
The example using @AboutType suggests a macro based solution instead. I don't know whether the currently designed macros can handle that, but maybe they can.
Just be careful that you actually know the types at the point where the macro must be expanded.

Thanks for the advice.
By the way, the proposed mechanism could be used not only for timeouts. Another example, functions with caching. There is even a package like this https://pub.dev/packages/cached. In this package, the developer applies annotations with code generation. With the support of the described mechanism in some form, it would be easier for him to do this.
The described mechanism will probably not be needed often, and in certain cases it can be changed to code generators, but if something like this were at least in an experimental form, then the solution of some problems could be simplified.

If code generation is the way to go, then I'd recommend looking at the macros/metaprogramming proposal; https://github.com/dart-lang/language/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3Astatic-metaprogramming
Generally, this will likely require language changes, so an more specific issue in the language repository will be more actionable.


Intermittent #FileInfo errors when parsing cue

v0.4.0

Does this issue reproduce with the latest release?
Yes
What did you do?
	cfg := &load.Config{
		Dir:        "/",
		ModuleRoot: "/",
		Overlay:    map[string]load.Source{},
	}
	cfg.Stdin = strings.NewReader(input)
	instances := load.Instances([]string{"-"}, cfg)

	if len(instances) != 1 {
		return nil, errors.Errorf("unsupported number of instances: %d", len(instances))
	}

	runtime := cuecontext.New()
	inst := runtime.BuildInstance(instances[0])
	if err := inst.Err(); err != nil {
		buf := &bytes.Buffer{}
		cueerrors.Print(buf, err, nil)
		return nil, errors.Wrap(ErrInvalidConfig, buf.String())
	}

Every 1 in ~8 times, Cue will error when validating it's own cue files:
#FileInfo.definitions: could not parse arguments: cannot convert non-concrete value bool:
    types.cue:26:2
#FileInfo.optional: could not parse arguments: cannot convert non-concrete value bool:
    types.cue:27:2
#FileInfo.const
raints: could not parse arguments: cannot convert non-concrete value bool:
    types.cue:28:2
#FileInfo.keepDefaults: could not parse arguments: cannot convert non-concrete value bool:
    types.cue:29:2
#FileInfo.incomplete: could not parse arguments: cannot convert
non-concrete value bool:
    types.cue:30:2
#FileInfo.imports: could not parse arguments: cannot convert non-concrete value bool:
    types.cue:31:2

What did you expect to see?
No errors, as the cue input is valid.
What did you see instead?
Errors parsing cue's own internal definitions.

This is fixable if I update the BuildFile generated within an instance as follows, prior to building the instance:
	instances[0].BuildFiles[0].Encoding = build.CUE
	instances[0].BuildFiles[0].Form = build.Schema
	instances[0].BuildFiles[0].Interpretation = ""

This is because Cue short circuits here: https://github.com/cuelang/cue/blob/master/internal/filetypes/filetypes.go#L77-L80
However, by default, Form is an empty string and so evaluating does not short circuit.
This isn't so much a fix - the race condition/bug exists somewhere when parsing cue's builtin, using gob encoding.

That was a lie - if I include packages, this transient error still exists as the build type is not schema.
Instead, I had to reimplement dependency resolution and file parsing to generate instances for each file (and their depencency).

This issue has been migrated to https://github.com/cue-lang/cue/issues/1043.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


useFetch doesn't convert Date to string

Environment

Operating System: Linux
Node Version:     v18.20.3
Nuxt Version:     3.13.0
CLI Version:      3.12.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      compatibilityDate, devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-kayd36?file=utils%2Fget.ts
Describe the bug
If you return a Date from a api route the type doesn't get converted to string
Additional context
No response
Logs
No response

This is likely a Nitro issue with:
https://github.com/unjs/nitro/blob/d20ffcbd16fc4003b774445e1a01e698c2bb078a/src/types/fetch/_serialize.ts#L28-L47
Would you see if you can reproduce this in pure Nitro (reproduction sandbox), and if so, raise there? 🙏

I can't. Auto Imports and Typescript not working inside stackblitz


dom-reporter input focus

Hello again :)
It appears the dom reporter is looking for data-felte-validation-message.
The issue I'm having with this now it took two days of my life component is that, even I can inject the attribute data-felte-validation-message into it, it becomes out of sync, so when the dom-reporter is doing the querySelect on the form, it can't find it at that time.
I tested the theory with importing tick().then(() => { ...focus }) into the dom-reporter, it was partially sucessful. setTimeout was the most successful.
I'm just asking so I learn, what do you think about having the dom-reporter accept an onSubmitError callback in the options and if it is not provided then execute the standard logic?

I'm struggling to understand what's happening here. Are you trying to use the reporter-dom package with a custom field? (not an input, textarea, etc). Do you have an example of what you're trying to achieve? (a Code Sandbox or Svelte REPL example would be nice, just note that if you're using yup, it won't work on the Svelte REPL).

helloo :) yes it is with the custom components and not just this one I was working on but also I tested with carbon too. I will get you a repository as soon as I can. That would be the easiest, should had done that to begin with.

With Felte v1 there's a new and better way to handle custom form controls where user's don't interact directly with native HTML controls. This shouldn't be an issue from now. Here's the example from the docs:
<script>
  import { createField } from 'felte';

  export let name;

  const { field, onInput, onBlur } = createField(name);

  function handleInput(e) {
    onInput(e.currentTarget.innerText);
  }
</script>

<div
  use:field
  on:input={handleInput}
  on:blur={onBlur}
  aria-labelledby={labelId}
  role="textbox"
  contenteditable="true"
  tabindex="0"
  />

Note that the element where you use the action has to be focusable. I'm also hoping to improve a bit the way Felte finds invalid inputs, but this works pretty well now!


Company service için prototip mesajlar ve servis düzenlemesi

conflict giderilmeli
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts


Add support for creating, getting, and resolving predictions

Resolves #178

This doesn't have all the fields of the prediction data structure, but just wanting to check myself before I go any further.  Works with my test client to create, get and resolve predictions.

Thanks for the pr, just a couple things that need changing

Okay this one is ready for another look!  I had some trouble with the date time stuff because apparently twitch is giving me dates of the format: 2021-09-07T01:21:27.725465223Z which python did not like.  Seems like different parts of the API all have different time stamp formats though.

The api is very inconsistent. I'm pretty sure they try to be as inconsistent as possible tbh. I'll review this again in a few hours, thanks


fix: Check if program cancelReader is is nil before invoking

This PR fixes an issue where a user may provide a nil input via tea.WithInput(nil).  This option method does not check if the input is nil and sets the withCustomInput attribute with a nil input. This logic is sound since a Tea program may not necessarily want to handle any inputs from users (such as those in non-TTY environments).
However, a nil pointer exception is thrown during tea.Run because the cancelReader is always invoked after the main renderer.  Its instantiation is variable and dependent on whether an input is provided. To mitigate against this, this PR checks if cancelReader is non-nil.

Hi @meowgorithm, @muesli, any updates on this? :)

Looks good to me. @muesli, whatcha think?

Looks good to me! Thank you @nderjung!

Thanks!


feat(azure): add support for Azure Application Insights

Issue #830

@tim775, this is ready for review :)


Perhaps another reason to look at for AttributeError

See https://twitter.com/raymondh/status/1296865073747513344
#Python wish: With effort, we could make error reporting much smarter and more helpful.

>>> predict(unknown_flower, iris_measurements. iris_labels)
AttributeError: 'list' object has no attribute 'iris_labels'
Hint: A period followed by a space is unusual, did you intend a comma?

Also on that thread, https://twitter.com/westurner/status/1296952288909627392
"[Python-ideas] Better error messages [was: (no subject)]"
https://groups.google.com/g/python-ideas/c/TbhXqKNzpCI/m/j-IPMY0DBwAJ?pli=1
- sys.excepthook
- didyoumean-python (NameError, AttributeError, etc) https://github.com/SylvainDe/DidYouMean-Python
- didyoumean (AttributeError) https://github.com/dutc/didyoumean

See: https://github.com/SylvainDe/DidYouMean-Python

Done.


Service Worker registration failed: TypeError

Bug report
Packages affected

[ ] sandpack-client
[x] sandpack-react

Description of the problem

What were you doing when the problem occurred?
Opening the browser with a Sandpack instance in the viewport view causes the error in my console (see screenshot above).
What steps can we take to reproduce the problem?
I implement two types of sandpack instances in my project: 1. Quickstart Presets, 2. Fully cusomized editor.
Both are implemented by following the official documentation.

Link to sandbox: link (optional)
Your Environment

Software
Name/Version

Sandpack-client version

Sandpack-react version
^2.12.1

Browser
Firefox, Chrome, Safari

Operating System
macOS: Sonoma 14.3.1

It has been fixed in the latest version. Sorry for the long wait!

Awesome! Thanks!


Clio Ricmotech Cup not on Road series list

The renamed Clio Cup is not available on the Road page. It was previously known as the iRacing Clio Cup but has changed name to Clio Ricmotech Cup - Fixed - 2023 Season 3 Fixed. Has a season ID of season=4358

I've realised the name of the Clio series across a few different parts of the game are not consistent. I'm checking with iRacing what it should be and hopefully they'll update it correctly.
As an aside, I know in the below we need to update the ID value (its now 519), but I can't remember what the number (4220W6) on the first line is for.
4220W6 iRacing Clio Cup - Fixed : Road 	LICENSE D 	ID 518
@bfiete Can you let me know what this is?


Request for number_format_insert to support number that already have thousands separators (commas) and decimal point

Example:

This works...
1555715
then apply using a stroke the translation {:number_format_insert:$nnn,nnn,nnn,nnN}, I get:
$1,555,715

This doesn't work...
1,555,715 (phoenix stroke for this would be  WUPB/PHL/TPAOEUFB/H-PB/STKPWOEUFB/TH/SAEFB/H-PB/STKPWAEPB)
then apply using a stroke the translation {:number_format_insert:$nnn,nnn,nnn,nnN}, I get:
$1,5,55,,715

Not urgent, but certainly would make this perfect for someone who already learned to stroke numbers "as they hear the speaker say them" as taught in the Phoenix courses.

fixed by IQubic


[24.05] python3Packages.{mautrix,matrix-nio}: add withOlm flags

Description of changes
Manual backport of https://github.com/NixOS/nixpkgs/pull/336901.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Tests are broken. Will probably have to backport version bumps.


my email isn't recogizied

Subject: my email isn't recogizied
Description:
I tried to log in
Results:
I received a message that my email is not recognized.
Backend version: develop-0023fa73
Frontend version:
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/login
User:

not enough info


[BUG] 5 tests fail when enabling GPU serde for the normal Shuffle.

Describe the bug
GPU serde for the normal Shuffle is introduced in PR https://github.com/NVIDIA/spark-rapids/pull/10818. But the following 5 tests fail when GPU serde is on. Luckily the errors are probably related to some internal difference in GPU nodes and the plan tree, nothing to do with the final output data.
- skewed inner join optimization *** FAILED ***
  ArrayBuffer(GpuShuffledSymmetricHashJoin Inner, [key1#55153L], [key2#55159L], false,<PHONE_NUMBER>, false
  :- GpuCoalesceBatches targetsize(1073741824)
  :  +- GpuCustomShuffleReader coalesced
  :     +- ShuffleQueryStage 0
  :        +- GpuColumnarExchange gpuhashpartitioning(key1#55153L, 100), ENSURE_REQUIREMENTS, [id=#158817]
  :           +- GpuProject [CASE WHEN (id#55151L < 250) THEN 249 WHEN (id#55151L >= 750) THEN 1000 ELSE id#55151L END AS key1#55153L, id#55151L AS value1#55154L]
  :              +- GpuRange (0, 1000, step=1, splits=10)
  +- GpuCoalesceBatches targetsize(1073741824)
     +- GpuCustomShuffleReader coalesced
        +- ShuffleQueryStage 1
           +- GpuColumnarExchange gpuhashpartitioning(key2#55159L, 100), ENSURE_REQUIREMENTS, [id=#158839]
              +- GpuProject [CASE WHEN (id#55157L < 500) THEN 249 ELSE id#55157L END AS key2#55159L, id#55157L AS value2#55160L]
                 +- GpuRange (0, 1000, step=1, splits=10)
  ) had size 1, but joins.head.isSkewJoin was false (AdaptiveQueryExecSuite.scala:688)
- skewed left outer join optimization *** FAILED ***
  ArrayBuffer(GpuShuffledHashJoin [key1#55174L], [key2#55180L], LeftOuter, GpuBuildRight, false
  :- GpuCoalesceBatches targetsize(1073741824)
  :  +- GpuCustomShuffleReader coalesced
  :     +- ShuffleQueryStage 0
  :        +- GpuColumnarExchange gpuhashpartitioning(key1#55174L, 100), ENSURE_REQUIREMENTS, [id=#159076]
  :           +- GpuProject [CASE WHEN (id#55172L < 250) THEN 249 WHEN (id#55172L >= 750) THEN 1000 ELSE id#55172L END AS key1#55174L, id#55172L AS value1#55175L]
  :              +- GpuRange (0, 1000, step=1, splits=10)
  +- GpuCoalesceBatches targetsize(1073741824)
     +- GpuCustomShuffleReader coalesced
        +- ShuffleQueryStage 1
           +- GpuColumnarExchange gpuhashpartitioning(key2#55180L, 100), ENSURE_REQUIREMENTS, [id=#159098]
              +- GpuProject [CASE WHEN (id#55178L < 500) THEN 249 ELSE id#55178L END AS key2#55180L, id#55178L AS value2#55181L]
                 +- GpuRange (0, 1000, step=1, splits=10)
  ) had size 1, but joins.head.isSkewJoin was false (AdaptiveQueryExecSuite.scala:688)
- skewed right outer join optimization *** FAILED ***
  ArrayBuffer(GpuShuffledHashJoin [key1#55195L], [key2#55201L], RightOuter, GpuBuildLeft, false
  :- GpuCoalesceBatches targetsize(1073741824)
  :  +- GpuCustomShuffleReader coalesced
  :     +- ShuffleQueryStage 0
  :        +- GpuColumnarExchange gpuhashpartitioning(key1#55195L, 100), ENSURE_REQUIREMENTS, [id=#159343]
  :           +- GpuProject [CASE WHEN (id#55193L < 250) THEN 249 WHEN (id#55193L >= 750) THEN 1000 ELSE id#55193L END AS key1#55195L, id#55193L AS value1#55196L]
  :              +- GpuRange (0, 1000, step=1, splits=10)
  +- GpuCoalesceBatches targetsize(1073741824)
     +- GpuCustomShuffleReader coalesced
        +- ShuffleQueryStage 1
           +- GpuColumnarExchange gpuhashpartitioning(key2#55201L, 100), ENSURE_REQUIREMENTS, [id=#159365]
              +- GpuProject [CASE WHEN (id#55199L < 500) THEN 249 ELSE id#55199L END AS key2#55201L, id#55199L AS value2#55202L]
                 +- GpuRange (0, 1000, step=1, splits=10)
  ) had size 1, but joins.head.isSkewJoin was false (AdaptiveQueryExecSuite.scala:688)

- Change merge join to broadcast join without local shuffle reader *** FAILED ***
  ArrayBuffer() had size 0 instead of expected size 1 (AdaptiveQueryExecSuite.scala:520)
- Verify the reader is LocalShuffleReaderExec *** FAILED ***
  ArrayBuffer() had size 0 instead of expected size 1 (AdaptiveQueryExecSuite.scala:549)

Looked further into this and found all the failures are due to the plan after AQE changed when GPU Serde is on, different from the expectation. For example
# GPU Serde on
==> Got GpuColumnarToRow false
+- GpuShuffledSymmetricHashJoin Inner, [a#290], [a#307], false,<PHONE_NUMBER>, false
   :- GpuShuffledSymmetricHashJoin Inner, [n#324], [a#290], false,<PHONE_NUMBER>, false
   :  :- GpuCoalesceBatches targetsize(1073741824)
   :  :  +- GpuCustomShuffleReader coalesced
   :  :     +- ShuffleQueryStage 0
   :  :        +- GpuColumnarExchange gpuhashpartitioning(n#324, 200), ENSURE_REQUIREMENTS, [id=#4258]
   :  :           +- GpuCoalesceBatches targetsize(1073741824)
   :  :              +- GpuFilter ((gpuisnotnull(l#325) AND (cast(l#325 as int) = 1)) AND gpuisnotnull(n#324))
   :  :                 +- GpuFileGpuScan parquet [n#324,l#325] Batched: true, DataFilters: [isnotnull(l#325), (cast(l#325 as int) = 1), isnotnull(n#324)], Format: Parquet, Location: InMemoryFileIndex[..., PartitionFilters: [], PushedFilters: [IsNotNull(l), IsNotNull(n)], ReadSchema: struct<n:int,l:string>
   :  +- GpuCoalesceBatches targetsize(1073741824)
   :     +- GpuCustomShuffleReader coalesced
   :        +- ShuffleQueryStage 1
   :           +- GpuColumnarExchange gpuhashpartitioning(a#290, 200), ENSURE_REQUIREMENTS, [id=#4288]
   :              +- GpuCoalesceBatches targetsize(1073741824)
   :                 +- GpuFilter gpuisnotnull(a#290)
   :                    +- GpuFileGpuScan parquet [a#290,b#291] Batched: true, DataFilters: [isnotnull(a#290)], Format: Parquet, Location: InMemoryFileIndex[.., PartitionFilters: [], PushedFilters: [IsNotNull(a)], ReadSchema: struct<a:int,b:int>
   +- GpuCoalesceBatches targetsize(1073741824)
      +- GpuCustomShuffleReader coalesced
         +- ShuffleQueryStage 2
            +- GpuColumnarExchange gpuhashpartitioning(a#307, 200), ENSURE_REQUIREMENTS, [id=#4319]
               +- GpuCoalesceBatches targetsize(1073741824)
                  +- GpuFilter gpuisnotnull(a#307)
                     +- GpuFileGpuScan parquet [a#307,b#308] Batched: true, DataFilters: [isnotnull(a#307)], Format: Parquet, Location: InMemoryFileIndex[f.., PartitionFilters: [], PushedFilters: [IsNotNull(a)], ReadSchema: struct<a:int,b:int>

# GPU Serde off
==> Got GpuColumnarToRow false
+- GpuShuffledSymmetricHashJoin Inner, [a#290], [a#307], false,<PHONE_NUMBER>, false
   :- GpuBroadcastHashJoin [n#324], [a#290], Inner, GpuBuildLeft
   :  :- BroadcastQueryStage 3
   :  :  +- GpuBroadcastExchange HashedRelationBroadcastMode(List(cast(input[0, int, false] as bigint)),false), [id=#4391]
   :  :     +- GpuShuffleCoalesce<PHONE_NUMBER>
   :  :        +- GpuCustomShuffleReader local
   :  :           +- ShuffleQueryStage 0
   :  :              +- GpuColumnarExchange gpuhashpartitioning(n#324, 200), ENSURE_REQUIREMENTS, [id=#4258]
   :  :                 +- GpuCoalesceBatches targetsize(1073741824)
   :  :                    +- GpuFilter ((gpuisnotnull(l#325) AND (cast(l#325 as int) = 1)) AND gpuisnotnull(n#324))
   :  :                       +- GpuFileGpuScan parquet [n#324,l#325] Batched: true, DataFilters: [isnotnull(l#325), (cast(l#325 as int) = 1), isnotnull(n#324)], Format: Parquet, Location: InMemoryFileIndex[, PartitionFilters: [], PushedFilters: [IsNotNull(l), IsNotNull(n)], ReadSchema: struct<n:int,l:string>
   :  +- GpuShuffleCoalesce<PHONE_NUMBER>
   :     +- GpuCustomShuffleReader coalesced
   :        +- ShuffleQueryStage 1
   :           +- GpuColumnarExchange gpuhashpartitioning(a#290, 200), ENSURE_REQUIREMENTS, [id=#4288]
   :              +- GpuCoalesceBatches targetsize(1073741824)
   :                 +- GpuFilter gpuisnotnull(a#290)
   :                    +- GpuFileGpuScan parquet [a#290,b#291] Batched: true, DataFilters: [isnotnull(a#290)], Format: Parquet, Location: InMemoryFileIndex[., PartitionFilters: [], PushedFilters: [IsNotNull(a)], ReadSchema: struct<a:int,b:int>
   +- GpuCustomShuffleReader coalesced
      +- ShuffleQueryStage 2
         +- GpuColumnarExchange gpuhashpartitioning(a#307, 200), ENSURE_REQUIREMENTS, [id=#4319]
            +- GpuCoalesceBatches targetsize(1073741824)
               +- GpuFilter gpuisnotnull(a#307)
                  +- GpuFileGpuScan parquet [a#307,b#308] Batched: true, DataFilters: [isnotnull(a#307)], Format: Parquet, Location: InMemoryFileIndex[,PartitionFilters: [], PushedFilters: [IsNotNull(a)], ReadSchema: struct<a:int,b:int>

Steps/Code to reproduce bug
Enable the GPU serde by changing the test code line as
.set(RapidsConf.SHUFFLE_GPU_SERDE_ENABLED.key, "true"),
and run the tests by the command
mvn package -DwildcardSuites=com.nvidia.spark.rapids.AdaptiveQueryExecSuite

We need to understand more details for why these are failing.

We need to understand more details for why these are failing.

Added what I have found so far in the description.


Block nets, such as NPS, are not displaying label correctly in xlsx file

ExcelPainter is not writing the calc name when calc_only is True... the view name is written instead.

Resolved by #169.


Add simple averaging to monitor output to increase readability.

My power usage is very sporadic - this makes it so that the information on the monitor is difficult to read since it changes so quickly. It would significantly increase readability if these values were averaged over a second or so - so that I could get a better idea of the total requirements of my power system.

Great suggestion! I'll roll something out for this.


Works Station doesn't drop items when closing gui and shift-right-click is not working correctly

...

fixed in 1.8.4 release 6662daddaafddec9dd983df6e026f654ee3c0699


SystemV struct arguments

According to the SystemV abi, struct arguments must be passed at a fixed stack offset. Cranelift didn't have any way to implement this before. This is necessary to compile proc-macros using cg_clif: https://github.com/bjorn3/rustc_codegen_cranelift/issues/905#issuecomment-616173297
Fixes #1108
TODO

[x] Don't misuse INVALID, but introduce a proper type.
[x] Implement this correctly for WindowsFastcall or give an error.

Ready for review. There are two hacks that can be removed once the old style backends are removed: The __sarg type and the __sarg_dummy instruction.

r? @fitzgen

All tests pass.

Are the TODOs in the original comment taken care of?

Are the TODOs in the original comment taken care of?

Thanks for reminding me.

Don't misuse INVALID, but introduce a proper type.

I have introduced the SARG__ type.

Implement this correctly for WindowsFastcall or give an error.

I will add an error for now.

I have turned it into a panic, as there is no way to report an error in the function signature legalization.

Should I squash?

That would be helpful, yes.

Splat

CI passed

Thanks for rebasing @bjorn3.
I took a look at the code, but I don't feel familiar enough with many of the bits that it is touching to be the official reviewer, determine if this is the proper approach to solving the problem, etc. I think @bnjbvr or @sunfishcode would be better reviewers.

Also, to be clear, like others above I'd also be more comfortable if someone who's worked more on the old backend could review as well.

@bnjbvr , would you mind sanity-checking this? LGTM from code-quality perspective, just want to make sure I'm not missing anything w.r.t. interactions with the old ABI mechanisms.

macOS doesn't have any logs for the failure.

It passed this time.

Thanks!


Internationalization & Hungarian translation

I created a localized version using i18next that covers the Calculator and the About page. There are a few glitches here & there, but its usable. I've included a Hungarian translation as well.
I know it's a major patch which makes ongoing maintenance and all subsequent improvements more difficult. At this moment it is optimized to be minimally obtrusive to the main branch and potentially be maintained as a fork long-term: the keys for the translations are the English labels themselves. Let me know your thoughts on merging this to the master. If you'd like to do that and you agree that it's the best choice, I'd be happy to extract the English labels into separate language files, which is probably easier to maintain in the long term if all languages are upstream. If you don't want to take on that burden, that's fine as well, I'll just try to maintain the fork myself and publish it separately.

So, what do you folks think? Would you entertain the idea or should I go ahead and prepare for maintaining & publishing the fork for the long term?
It's not a problem either way, I just want to avoid duplicate work.
/cc @catherio @dominic @beshaya as the most active contributors

Sounds good! I'll get to it and let you know when it's ready to be merged. Will probably take about a week or so, depending on how much free time I'll have, we'll see.

OK, I think I'm done with what needed to be done at this stage. The only big chunk that's left over is the localization of the country/location selector, but that'd need touching too many parts of the code, so I did not dare to go there -- and it might not even be worth doing. Let me know what you think, @beshaya

Hi Gyp, sorry I've been hammered with work this week + out for the weekend. I'll take a look early next week.
Thanks again for this!

@gyp  - Thanks for all you're doing here. I've been tracking this thread along with @beshaya and the rest of the team.
One question I/we are looking at is how to bring these changes in alongside the very large project happening over on the ux-redesign branch. We may request your help in merging your work with the numerous updates happening over there. I hate to create more work for you. Once these two branches are both merged into main, things should be pretty easy moving forward.
@beshaya / others - curious your thoughts which one we should merge first. Or if @gyp should potentially start working against ux-redesign now and tracking it as we go?

Sure, I'm happy to help, let me know which way would you like me to proceed.
I might need some help here & there though, I am by no means proficient in React, Typescript and the last time I worked on anything frontend-heavy as a coder was a decade ago. But I'll try and will ask for help if I'm stuck :)

@gyp Thanks again for all your work. We want you to know how much we appreciate it! We've been hard at work with a big upgrade. We hope to have it out in the next week.
Whenever you're ready, you might start doing your work against the ux-redesign branch. There will be a ton of merge conflicts with the work you already did that will need to be resolved because there is so much new text on the calculator page. As soon as we merge ux-redesign into main, I'm in favor of supporting you to get your i18n branch in next. (I haven't talked with @beshaya or others directly about a plan, this is just my two cents.)
So yeah. If you merge in ux-redesign, that's where to begin, I think!

OK, I started working on it. It's indeed a huge merge with tons of conflicts, but I'll work through those one-by-one. I'll let you know when it's done. (I dig the new design, BTW :))

Glad you like the new design. And thanks! I was thinking of you every time I made a commit and I was like "this is making a lot of work for him!" I appreciate your diligence! Once we get your branch merged in, it'll be easier for all of us to keep it up to date.

OK, the big-bang merge is now done, it wasn't that horrible after all.
But there are tons of small things yet to be done, I'll let you know when it will make sense to look at it again.

I think it's now ready to be merged.
The ux-design branch as of afde36383707a2dee5941605739f5e3ae501d4c0 is now merged and the localization is fairly complete. There are still a few rough edges here & there but I think it's acceptable.
Please do check the functionality and all the labels, especially around the changes you made recently as there were a few brutal conflicts and I could easily have messed up the merges.
/cc @blanchardjeremy

@beshaya @gyp - I think we need to recreate this pull request with a request to merge into ux-redesign. Is that right?
Right now it includes all the commits from ux-redesign which makes the code review very difficult. 7

I did a review of the calculator page and here are my notes:

"Step 2 - Person Risk" (purple header) should be "Step 2: Describe the activity"
"Duration:How long is the activity, in minutes?" is missing a space before "How"
Under the small help text underneath "Their Mask" it looks like you changed it to If they're eating or drinking, select “no mask” ... It should be If you're
the points display should show: "90% of your weekly risk budget" (the word "your" is missing)
"We believe with roughly 90% confidence that th actual risk falls " (type. should be "the")
" If you do this activity many times with the same people each week, enter it as "household member" to see what the maximum transmission rate is per week." doesn't match what I see on the ux-redesign branch. Check it out.
Typo: "Hight Caution Budget"

I changed  the pull request to reflect that I want to merge it into ux-redesign. Most of the conversation here was generic, so it would not make sense to start a completely new pull request just because of that.
Thanks for the review! Those exactly the kind of problems I thought I'd leave in it.

"Step 2 - Person Risk" (purple header) should be "Step 2: Describe the activity"
"Duration:How long is the activity, in minutes?" is missing a space before "How"
the points display should show: "90% of your weekly risk budget" (the word "your" is missing)
"We believe with roughly 90% confidence that th actual risk falls " (type. should be "the")
Typo: "Hight Caution Budget"

All fixed by d70c173294d6152675470b191205afc67843168e

Under the small help text underneath "Their Mask" it looks like you changed it to If they're eating or drinking, select “no mask” ... It should be If you're

Oh yeah, I wanted to commit that one separately as that was not a mere localization rather a substantive change, I just forgot by the time I got there. Sorry about that. Let me know if you'd like me to extract it to a separate patch or simply revert it.
But please double check it first though, as I think the original version was incorrect and my change makes sense. Why should my eating nullify their mask use? It nullifies my own mask use all right, but that's already taken care of by setting my mask usage to 'no mask'. If they're eating, it cancels out their mask usage, but if they're wearing their mask, that protects me, even if I took mine off while I'm eating.

" If you do this activity many times with the same people each week, enter it as "household member" to see what the maximum transmission rate is per week." doesn't match what I see on the ux-redesign branch. Check it out.

That was a deliberate simplification. The ux-redesign branch there does this strange thing where it gives the suggestion either as 'household member' or 'partner/spouse' based in whether a distance is chosen in the selector:
https://github.com/microcovid/microcovid/blob/1202d71baa182513521d1116bac96b25bc2feb8d/src/components/calculator/ExplanationCard/ExplanationCard.tsx#L173-L180 I don't understand the logic behind it (why would the lack of selecting a distance suggest household member and selecting any kind of distance a partner?), and I don't think such a level of precision or brevity is required for a note hidden pretty far down in the page structure. On the other hand, the code and the translation would be much more complex if one had to accommodate for this branching, so I thought just adjusting the verbiage slightly and removing this logic is the better choice here.

I just merged in the latest changes from ux-redesign and noticed that the budget selector is broken, and it seems to be broken on ux-redesign as well: changing the budget does not update the risk results and the thermometer. I tried to figure out what's going on but my React skills are way too limited to troubleshoot this, I just thought you'd like to know, as this pretty much breaks the budget setting functionality.

It's great to see the redesigned merged onto the mainline. Thanks for the housekeeping, @beshaya.
I merged in the changes to this branch again, as of this moment, it merges clean onto main, too.
I kept the changes mentioned in https://github.com/microcovid/microcovid/pull/284#issuecomment-719903795 (change in the note about the effect of others mask wearing during eating and a simplification around the note on the ExplanationCard), let me know what you think about those.

@gyp  Thanks for the questions/suggestions on those two points above.
For this PR, I think it's important that we match whatever is in the current app exactly (even if there are spots for improvement, as you suggest). For any suggestions/bugs you find, please open them as separate issues and just "leave them there" for now so this pull request can be as simple as possible.
You can just copy-paste the comments from above into two separate issues and we can all look at them together.
And yeah, feel free to just make a new commit "reverting" those changes. (and you can keep them around for separate PRs.

@blanchardjeremy there you go, they're reverted, a separate issue was filed under #457
Note that I made the required follow-ups in the PointsDisplay functional tests as well, even though they did not break yet, but they would, should any changes be made in the labels in the default locale. It made that code quite hard to read, which is not ideal, but, not being a React developer, I've got no idea what would be the right strategy around that.

@gyp FYI - we're looking at getting this merged in today or in the next day or so. From then on out, each pull request should be a small "bite-sized" piece of code that can be easily reviewed.

That's awesome, thanks.
Do you have any plans to add new translations? I'll try to recruit people to help out, but I want to avoid double work.


[ristretto] Derive ops for easy group definitions (PoC)

This is a PoC for PR #232 which demonstrates two things:

how to derive a variety of arithmetic operators when the operands are NewTypes which inner types support those operations. Included are :

core::ops::{Add, AddAssign, Mul, MulAssign, Neg, Sub, SubAssign};
std::iter::Sum;

as implemented on both references and owned instances.
2. how to define a trait using those operations. In particular, we show the "convenience trait" pattern, (here GroupOps, GroupOpsOwned, ScalarMul, ScalarMulOwned) and their use in the final trait definition.
(see discussion at https://github.com/MystenLabs/fastcrypto/pull/232#discussion_r1030563246)

This has served its purpose. See the results in the discussion & evolution of #232


Feature Request: automattically adding a dependency for the Winget Installer Package.

Or a requirement for a complete Winget installation.

#23

+1 I have now created a win32 that updates winget and deploy it the devices. All other applications are deployed to user for a smoth autopilot enrollment


How to prevent page refresh while tab changes ?

How to prevent page refresh while tab changes ? Thanks.

can you show a plunker that shows that behaviour please? I am not quite sure what you mean by refresh, if you mean full page refresh then that should not be happening.
which versions are you using etc?

@pziegler
Take this example: I have two tabs: tabA and tabB, both contain some text input and datatable component. First fill some data in tabA and then press tabA's search button, tabA's datatable will present data sent from server. Then switch to tabB and return to tabA. The data in text input and datatable disappeared as the tabA's controller reinitialized.
I tried some methods , such as
$state.transitionTo(tab.route, tab.params, { reload: false, inherit: false, notify: true });
but still not resolved.
BTW, I am using AngularJS 1.3.9, UI-Router 0.2.18
Thanks

should merge this question with #82
it's about keeping the content and stateful transitions as well.
would be better to keep discussion in one thread.
found this in ui-router
https://github.com/angular-ui/ui-router/issues/2096
I would look on stackexchange or the ui-router project as this isnt really related to the tabs project itself

@pziegler
I think it's issue of ui-router project,  should I close current issue ?

yes, I think that would be preferable . You can always link to this issue when you create a new issue there (or if you search you might find..) I think you want something like sticky states or so

@pziegler
Thanks, I am closing this issue

@fireworkstudio: Seems like that behavior has been fixed in the latest update of ui-router, but that is still not yet released...

@MikiSoft
That's cool, looking forward to it

I forgot to ask, have you tried it on v0.3.1 to see if it works with it?

I used another open source solution which depends on tabs.
sx-tabs


Adding environment variable for server path

…g.json path

Hey, thank you for the PR! Can you help me understand the circumstances under which this is necessary? How are is your project set up such that the app can't be found?

I build my docker containers with the node_modules in /dist, and a symlink of /dist/node_modules to the current directory.
For development, we run this docker container and map the current directory into /home/strong-pm, with a symlink of node_modules -> /dist/node_modules
For production, we add the current directory to that base image and cut a docker image with the release code.
For whatever reason, the fact that node_modules isn't in the current directory causes divineLoopbackServerPath to fail.  I thought about debugging this condition, but though that having a way to override/fix it would be needed even if this situation were resolved.

I see. This module depends on https://github.com/inxilpro/node-app-root-path to determine project root. app-root-path already has a means to override its decisions using an env-var, APP_ROOT_PATH. Can you try setting APP_ROOT_PATH to your project root (wherever package.json exists) and see if it solves your problem?

You are right -- APP_ROOT_PATH solves the same problem.
Can you update the README to include this?  APP_ROOT_PATH=/home/strong-pm solved my problem

Added to README! Thanks for your feedback.