Update attribute table to include special-cases

Update attribute table to include special-cases/attributes where an attribute is used together with a geometry

Small doc change so merging myself


Navigation is not as snappy when installed as PWA.

Why is the navigation not as responsive when the app is installed as pwa. Is this because of the serviceworker or is it because of nextjs? I tested it on a iPhone.
btw cool project. I learned a lot.


Enh/parachute

Pull request type
Please check the type of change your PR introduces:

[X] Code base additions (bugfix, features)
[ ] Code maintenance (refactoring, formatting, renaming, tests)
[ ] ReadMe, Docs and GitHub maintenance
[ ] Other (please describe):

Pull request checklist
Please check if your PR fulfills the following requirements, depending on the type of PR:

ReadMe, Docs and GitHub maintenance:

[ ] Spelling has been verified
[ ] Code docs are working correctly

Code base maintenance (refactoring, formatting, renaming):

[ ] Docs have been reviewed and added / updated if needed
[ ] Lint (black rocketpy) has passed locally and any fixes were made
[ ] All tests (pytest --runslow) have passed locally

Code base additions (for bug fixes / features):

[ ] Tests for the changes have been added
[ ] Docs have been reviewed and added / updated if needed
[X] Lint (black rocketpy) has passed locally and any fixes were made
[X] All tests (pytest --runslow) have passed locally

What is the current behavior?

Currently there is no place to keep functions that are useful but do not belong to any of the 5 core classes in Rocketpy.
One of these functions is the compute_cds_from_drop_test, that calculates the CdS of a parachute from a drop test.
What is the new behavior?

With the module utilities.py, it is possible to save functions like the compute_cds_from_drop_test.
Does this introduce a breaking change?

[ ] Yes
[X] No

Other information

Enter text here...

@FranzYuri, I would suggest you run black to reformat your code:

Install black running pip install black
Run black rocketpy when in the repository folder

The second thing is that it may be necessary to add something like from .utilities import * or from .utilities import compute_cds_from_drop_test to the __init__.py file, so the import process can be achieved using from rocketpy import *.

Currently there is no place to keep functions that are useful but do not belong to any of the 5 core classes in Rocketpy. One of these functions is the compute_cds_from_drop_test, that calculates the CdS of a parachute from a drop test.

Can you guys please indicate other functions with that same behavior in the code?

@Gui-FernandesBR for now I haven't personally identified any function that applies. But I imagine we could use this file in the future to gather functions to help design Rockets/Parachutes/Motors etc. For example functions related to rocket parameter optimizations (ideal mass for a certain motor or something similar). I think the suggestion to create utilities.py came from @giovaniceotto and @FranzYuri, maybe they had different ideas.

Tks for explaning that, @Lucas-KB . If I'm understamdimg this correctly, I have some candidates to be included at utilities.py, let's see:

Environment:
def decimalDegressToArcSeconds(self, angle):
Flight:
def calculateFinFlutterAnalysis(self, finThickness, shearModulus):
def exportPressures(self, fileName, timeStep):

Those could help to give more "body" to this new .py file, and they could be moved in another PR I guess. Please let me know if these suggestions are good or not.
Also, I would recommend creating a simple example usage for these functions. At least for me, it is not easy to visualize how I could use the new capabilities.

Excellent suggestions @Gui-FernandesBR! I hope you are ok with me creating a new issue regarding your ideas so that we can come back to them in a future PR. The issue is here #111.

Don't need my permission @giovaniceotto ... Thanks for opening the 111, I appreciate it

@giovaniceotto I think it is alright now, can you take a look?

@FranzYuri, my bad, I had reviewed your changes but forgot to approve it!
Looks perfect now. Would you do the honors of merging the pull request?


Generate deltas + update lcsh terms

closes https://github.com/galterlibrary/Prism/issues/650
rearchitect to support LCSH deltas
release: v0.4.0
This is a big one, but the idea is straightforward: I've pulled up common code outside of the original MeSH contrib folder and I've added an injection point to pass scheme-specific functionality in otherwise identical algorithms.

Addressed comments. I will leave this around some more for further doublechecks and merge later in the day.


Move stream_params into viz_config?

Not sure if there are other yamls floating around in this repo, but this file only has
flow:
  - '00060'
stage:
  - '00065'

Move these into the config and remove this file?

Yeah i think that makes sense. Or just make it an object in 1_fetch.yml?


Damn makes a deck appear B (or W) when it is not

These decks are mono W. We could just exempt Damn specifically where we exempt mdfcs, split cards and traps?

I specialcased Damn


Autoscaling with multiple metrics does not work

/kind bug
What steps did you take and what happened:
Tried the following

Tried creating memory based autoscaling using knative annotations as below. A CPU based HPA was created instead with averageUtilization set to 80.

autoscaling.knative.dev/class: "hpa.autoscaling.knative.dev"
autoscaling.knative.dev/metric: "memory"
autoscaling.knative.dev/target: "75"

Tried creating memory based autoscaling using kserve annotations as below. A CPU based HPA was created instead with averageUtilization set to 80.

serving.kserve.io/autoscalerClass: hpa
serving.kserve.io/deploymentMode: RawDeployment
serving.kserve.io/metric: memory
serving.kserve.io/targetUtilizationPercentage: "70"

Tried creating memory based autoscaling by setting predictor.scaleMetric to memory and a memory based HPA was created. Yaay!

In scenario 1 and 2 HPAs are created as expected if the metric is set as cpu.
Now, I want my HPA to be controlled by both memory and CPU. I tried setting predictor.scaleMetric to memory and a corresponding scaleTarget. Also set CPU thresholds using serving.kserve.io/metric: cpu. But only predictor.scaleMetric is respected.
What did you expect to happen:
I want HPA to have both memory and CPU based triggers.
What's the InferenceService yaml:
apiVersion: serving.kserve.io/v1beta1
kind: InferenceService
metadata:
  annotations:
    serving.kserve.io/autoscalerClass: hpa
    serving.kserve.io/deploymentMode: RawDeployment
    serving.kserve.io/metric: cpu
    serving.kserve.io/targetUtilizationPercentage: "70"
  name: custom-model
  namespace: dev-xyz-multimodal-ner
spec:
  predictor:
    containers:
    - env:
      - name: AWS_BUCKET
        value: xyz-xyz-xyz-xyz-xyz-xyz
      image: <custom image>
      name: kserve-container
      resources:
        limits:
          cpu: "4"
          memory: 6Gi
        requests:
          cpu: "1"
          memory: 2Gi
    maxReplicas: 4
    nodeSelector:
      nodetype: modelserving
    scaleMetric: memory
    scaleTarget: 75
    tolerations:
    - effect: NoSchedule
      key: dedicated
      operator: Equal
      value: modelserving

Anything else you would like to add:
The HPA YAML inferenceservice generates
apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  annotations:
    serving.kserve.io/autoscalerClass: hpa
    serving.kserve.io/deploymentMode: RawDeployment
    serving.kserve.io/metric: cpu
    serving.kserve.io/targetUtilizationPercentage: "80"
  name: custom-model-predictor-default
  namespace: dev-xyz-multimodal-ner
  ownerReferences:
  - apiVersion: serving.kserve.io/v1beta1
    blockOwnerDeletion: true
    controller: true
    kind: InferenceService
    name: custom-model
spec:
  behavior:
    scaleDown:
      policies:
      - periodSeconds: 15
        type: Percent
        value: 100
      selectPolicy: Max
    scaleUp:
      policies:
      - periodSeconds: 15
        type: Pods
        value: 4
      - periodSeconds: 15
        type: Percent
        value: 100
      selectPolicy: Max
      stabilizationWindowSeconds: 0
  maxReplicas: 4
  metrics:
  - resource:
      name: memory
      target:
        averageUtilization: 75
        type: Utilization
    type: Resource
  minReplicas: 1
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: custom-model-predictor-default

Environment:

Istio Version: N/A (Using nginx)
Knative Version: N/A (Using Kubernetes deployment)
KServe Version: 0.11.0
Kubeflow version:
Cloud Environment:[AWS EKS]
Minikube/Kind version:
Kubernetes version: v1.28.7-eks-b9c9ed7
OS (e.g. from /etc/os-release): Amazon Linux 2

@shazinahmed Scaling based on multiple metrics is not supported, can you elaborate how you want to scale with both of these metrics?

@yuzisun I want to have two HPAs created like we can have it in a normal Kubernetes deployment, so that I can scale based both CPU and memory depending on what is over utilized.

Based on the options 1 and 2: it seems that the annotations are not used when the metrics are created, it defaults to CPU and 80% if predictor.scaleMetric | target are not set:
https://github.com/kserve/kserve/blob/master/pkg/controller/v1beta1/inferenceservice/reconcilers/hpa/hpa_reconciler.go#L60
Didn't find a doc link to HPA as well, we might be missing this part.
On the other hand, it seems k8s API supports it:
https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#scaling-on-multiple-metrics
Maybe we could evaluate to bring this functionality to KServer when HPA is enabled.
wdyt?


Acceptance Criteria

[ ] Integration tests have reasonable coverage.

What is reasonable?
Is that for the new actions?
Is that enough so we can close it?


Missing license and copyright information

I am unable to find any licensing and copyright information for this package.
Are you able to provide this?

Bump. @zodern  any chance you could make this happen?

It now has a license.


Setup branch protection rules for main branch

What would you like node-schedule to be able to do?

We should protect the main branch properly by requiring the current tests to pass before you can squash-merge/rebase merge a PR.
I think it's also a good time to prevent force pushes to the main branch, as I'm ready to accept contributions from the Renovate team on things I'm not qualified to change. 😄
Did you already have any implementation ideas?

I'd say just copy/paste what we have from renovatebot/renovate into here so that we keep the conventions/behavior the same between repositories in the org. 😄
I don't have enough rights to setup the branch protection rules, so somebody else will need to set that up. 😉 😉

@rarkins, I like the overall setup, nearly good to go:
GitHub changed the way you specify the "required tests" recently, you need to write a part of the test name before you can select it under "Require status checks to pass before merging". I don't see Jest or Lint status checks in the list of required tests right now.

I couldn't find any without 14.x

That's OK, you see the 14.x in the name because I use a test matrix like this:
https://github.com/renovatebot/node-schedule/blob/eccdccdaf7f6532cc9b17dd4d84d1d92a2b2371a/.github/workflows/jest.yml#L13-L15
I think it's possible to change the name by dropping the matrix. But I'd need to read the GitHub docs on Action syntax a bit more to be sure... 😄 I really only use the basic boilerplate setups. 😄


Laravel 5.0 support

I am upgrading my application from Laravel 4.2 to Laravel 5.0. But "laravelbook/ardent": "3." is throwing errors while running composer update command. I was using "laravelbook/ardent": "2." in Laravel 4.2.

@subhra44 How about closing this issue? It's very old and I doubt it is relevant any longer.


document replicate.models.predictions.create method

Followup to https://github.com/replicate/replicate-python/pull/207

@zeke  can i work on the above one

Thanks for the offer @pavansai26. I'm actually not sure about the state of this method in the Python API client. @mattt what do you think?

replicate.models.predictions.create has been deprecated in favor of an overload to replicate.predictions.create that accepts a model kwarg. This is documented in the README in this section: https://github.com/replicate/replicate-python?tab=readme-ov-file#run-a-model-and-stream-its-output


In announcements.html, content overlaps on resizing

In anouncements.html page, text in the upcoming events section overlaps. also, the padding in the upcoming event section is not proper.
To Reproduce the bug

Go to announcements.html
resize the window to mobile size
I would like to work on this issue. @smaranjitghose please assign me this issue.

Please check, its already fixed


rasterio error when writing raster

If I set up a fresh conda environment:
conda create -n ctx_test -c conda-forge python=3.5 contextily ipython

which installs:
(ctx_test) dh073065:~ dani$ conda list
# packages in environment at /Users/dani/anaconda/envs/ctx_test:
#
affine                    2.1.0                    py35_0    conda-forge
appnope                   0.1.0                    py35_0    conda-forge
asn1crypto                0.22.0                   py35_0    conda-forge
attrs                     17.2.0                   py35_0    conda-forge
boost                     1.64.0                   py35_4    conda-forge
boost-cpp                 1.64.0                        1    conda-forge
boto3                     1.4.7                    py35_0    conda-forge
botocore                  1.5.92                   py35_0    conda-forge
bzip2                     1.0.6                         1    conda-forge
ca-certificates           2<IP_ADDRESS>                   0    conda-forge
cairo                     1.14.6                        4    conda-forge
cartopy                   0.15.1                   py35_4    conda-forge
certifi                   2<IP_ADDRESS>              py35_0    conda-forge
cffi                      1.10.0                   py35_0    conda-forge
chardet                   3.0.4                    py35_0    conda-forge
click                     6.7                      py35_0    conda-forge
click-plugins             1.0.3                    py35_0    conda-forge
cligj                     0.4.0                    py35_0    conda-forge
contextily                0.9.2                    py35_0    conda-forge
cryptography              2.0.3                    py35_0    conda-forge
curl                      7.54.1                        0    conda-forge
cycler                    0.10.0                   py35_0    conda-forge
decorator                 4.1.2                    py35_0    conda-forge
docutils                  0.14                     py35_0    conda-forge
expat                     2.1.0                         3    conda-forge
fontconfig                2.12.1                        4    conda-forge
freetype                  2.7                           1    conda-forge
freexl                    1.0.2                         2    conda-forge
geos                      3.5.1                         1    conda-forge
gettext                   <IP_ADDRESS>                      0    conda-forge
giflib                    5.1.4                         0    conda-forge
glib                      2.51.4                        0    conda-forge
hdf4                      4.2.12                        0    conda-forge
hdf5                      1.8.18                        1    conda-forge
hypothesis                3.23.0                   py35_0    conda-forge
icu                       58.1                          1    conda-forge
idna                      2.5                      py35_0    conda-forge
ipython                   6.1.0                    py35_0    conda-forge
ipython_genutils          0.2.0                    py35_0    conda-forge
jedi                      0.10.2                   py35_0    conda-forge
jmespath                  0.9.3                    py35_0    conda-forge
jpeg                      9b                            0    conda-forge
json-c                    0.12.1                        0    conda-forge
kealib                    1.4.7                         2    conda-forge
krb5                      1.14.2                        0    conda-forge
libdap4                   3.18.3                        2    conda-forge
libffi                    3.2.1                         3    conda-forge
libgdal                   2.1.4                         2    conda-forge
libgfortran               3.0.0                         0    conda-forge
libiconv                  1.14                          4    conda-forge
libkml                    1.3.0                         1    conda-forge
libnetcdf                 <IP_ADDRESS>                       6    conda-forge
libpng                    1.6.28                        1    conda-forge
libpq                     9.6.3                         0    conda-forge
libspatialite             4.3.0a                       15    conda-forge
libssh2                   1.8.0                         1    conda-forge
libtiff                   4.0.6                         7    conda-forge
libxml2                   2.9.4                         4    conda-forge
libxslt                   1.1.29                        5    conda-forge
lxml                      3.8.0                    py35_0    conda-forge
matplotlib                2.0.2                    py35_2    conda-forge
mercantile                0.9.0                    py35_0    conda-forge
mkl                       2017.0.3                      0
ncurses                   5.9                          10    conda-forge
numpy                     1.13.1                   py35_0
olefile                   0.44                     py35_0    conda-forge
openjpeg                  2.1.2                         2    conda-forge
openssl                   1.0.2l                        0    conda-forge
owslib                    0.14.0                   py35_1    conda-forge
pandas                    0.20.3                   py35_1    conda-forge
pcre                      8.39                          0    conda-forge
pexpect                   4.2.1                    py35_0    conda-forge
pickleshare               0.7.4                    py35_0    conda-forge
pillow                    4.2.1                    py35_1    conda-forge
pip                       9.0.1                    py35_0    conda-forge
pixman                    0.34.0                        0    conda-forge
poppler                   0.52.0                        2    conda-forge
poppler-data              0.4.7                         0    conda-forge
proj4                     4.9.3                         4    conda-forge
prompt_toolkit            1.0.15                   py35_0    conda-forge
ptyprocess                0.5.2                    py35_0    conda-forge
pycparser                 2.18                     py35_0    conda-forge
pyepsg                    0.3.2                    py35_0    conda-forge
pygments                  2.2.0                    py35_0    conda-forge
pympler                   0.5                      py35_0    conda-forge
pyopenssl                 17.2.0                   py35_0    conda-forge
pyparsing                 2.2.0                    py35_0    conda-forge
pyproj                    <IP_ADDRESS>                  py35_0    conda-forge
pyshp                     1.2.12                     py_0    conda-forge
pysocks                   1.6.7                    py35_0    conda-forge
python                    3.5.4                         0    conda-forge
python-dateutil           2.6.1                    py35_0    conda-forge
pytz                      2017.2                   py35_0    conda-forge
rasterio                  0.36.0                   py35_0    conda-forge
readline                  6.2                           0    conda-forge
requests                  2.18.4                   py35_1    conda-forge
s3transfer                0.1.11                   py35_0    conda-forge
scipy                     0.19.1              np113py35_0
setuptools                36.3.0                   py35_0    conda-forge
shapely                   1.6.1                    py35_1    conda-forge
simplegeneric             0.8.1                    py35_0    conda-forge
six                       1.10.0                   py35_1    conda-forge
snuggs                    1.4.1                    py35_0    conda-forge
sqlite                    3.13.0                        1    conda-forge
tk                        8.5.19                        2    conda-forge
tornado                   4.5.2                    py35_0    conda-forge
traitlets                 4.3.2                    py35_0    conda-forge
urllib3                   1.22                     py35_0    conda-forge
wcwidth                   0.1.7                    py35_0    conda-forge
wheel                     0.29.0                   py35_0    conda-forge
xerces-c                  3.1.4                         3    conda-forge
xz                        5.2.3                         0    conda-forge
zlib                      1.2.8                         3    conda-forge
zope                      1.0                      py35_0
zope.interface            4.4.2                    py35_0
(ctx_test) dh073065:~ dani$

Then I try (example taken from here):
In [1]: import contextily as ctx

In [2]: w, s, e, n = (-106.6495132446289, 25.845197677612305, -93.50721740722656, 36.49387741088867)

In [3]: _ = ctx.bounds2raster(w, s, e, n, 6, 'tx.tif', ll=True)

It returns the following error:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-3-7db2ced4b25c> in <module>()
----> 1 _ = ctx.bounds2raster(w, s, e, n, 6, 'tx.tif', ll=True)

~/anaconda/envs/ctx_test/lib/python3.5/site-packages/contextily/__init__.py in bounds2raster(w, s, e, n, zoom, path, url, ll)
     77                       driver='GTiff', height=h, width=w,
     78                       count=b, dtype=Z.dtype,
---> 79                       crs='epsg:3857', transform=transform)
     80     for band in range(b):
     81         raster.write(Z[:, :, band], band+1)

~/anaconda/envs/ctx_test/lib/python3.5/site-packages/rasterio/__init__.py in open(path, mode, driver, width, height, count, crs, transform, dtype, nodata, **kwargs)
    156         raise TypeError("invalid driver: {0!r}".format(driver))
    157     if dtype and not check_dtype(dtype):
--> 158         raise TypeError("invalid dtype: {0!r}".format(dtype))
    159     if transform:
    160         transform = guard_transform(transform)

TypeError: invalid dtype: dtype('uint8')

In [4]:

It is strange, because with a similar set up, the CI seems to pass OK and it involves a call to bounds2raster.
@ocefpaf, @sgillies or @perrygeo, any ideas or suggestions? I'd really appreciate any sort of insight.

Just to add further info, CI running on Linux does not report back any issue, but Windows/macOS do.

For the record, I've been able to replicate the same problem on simpler setup:
conda create -n ctx_test -c conda-forge python=3.5 contextily ipython

With the example being:
import numpy as np
import rasterio as rio

a = np.random.random_integers(0, 256, size=(766, 766, 3)).astype('uint8')
w, h, b = a.shape
raster = rio.open('test.tif', 'w',
                 driver='GTiff', height=h, width=w,
                 count=b, dtype=a.dtype)

The error returned is:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-14-fce620e58065> in <module>()
     13                   driver='GTiff', height=h, width=w,
     14                   count=b, dtype=Z.dtype,
---> 15                   crs='epsg:3857', transform=transform)
     16 for band in range(b):
     17     raster.write(Z[:, :, band], band+1)

~/anaconda/envs/ctx_test/lib/python3.5/site-packages/rasterio/__init__.py in open(path, mode, driver, width, height, count, crs, transform, dtype, nodata, **kwargs)
    156         raise TypeError("invalid driver: {0!r}".format(driver))
    157     if dtype and not check_dtype(dtype):
--> 158         raise TypeError("invalid dtype: {0!r}".format(dtype))
    159     if transform:
    160         transform = guard_transform(transform)

TypeError: invalid dtype: dtype('uint8')

On this, I've noticed simply changing dtype=a.dtype for dtype=str(a.dtype) solves the issue. @sgillies, @perrygeo or any other one from the rasterio team, is this something expected? It used to work OK on earlier versions.

@darribas rasterio 0.36 is incompatible with numpy 1.13. you must either downgrade numpy to 1.11 or upgrade rasterio to the latest and greatest pre-release 1.0a9.

I wonder if this is related to the issue we have in #9 @darribas ...maybe a fix is just upgrading rasterio versions :-)

Possibly... We could have a quick try at that (installing bleeding edge rasterio). A longer-term question I had, maybe @sgillies can chip in is whether the fix proposed (str(dtype)) is a hack that's likely to bring trouble down the line or it's something that'll make it more robust? If the latter, I'd go ahead and merge; if the former, I think simply moving forward to the next rasterio version should work.

@darribas @choldgraf str(dtype) works with older numpy as far as I can tell.
Don't be misled by the 'a' in 1.0a9. 0.36 was a pre-release, too, and the new pre-releases are more stable than 0.36 was. I recommend switching if you can.

Don't be misled by the 'a' in 1.0a9. 0.36 was a pre-release, too, and the new pre-releases are more stable than 0.36 was. I recommend switching if you can.

Sorry be hijack this issue but now that you mentioned it we are having big problems by providing the 1.0 series in a dev channel due to that name while everybody is actually using it as the latest stable. Maybe a non-alpha release would help us to consolidate that release as THE rasterio we should use.

Thanks very much for the contributions @sgillies and @ocefpaf. Maybe the way forward then is to merge the str(dtype) patch and bump the rasterio version to 1.x. In that sense, it'd be great if it could be moved into stable conda-forge but, if for whatever reason it cannot happen soon, we can point to 1.0a9 for the time being.

I'm not recommending that 1.0a9 go in the conda-forge stable! I just wanted to point out that 0.36 never was stable in the way that 1.0.0 will be.

I'm not recommending that 1.0a9 go in the conda-forge stable!

BTW, it was in the main channel ("stable"), I had to remove only b/c of "rules."

I just wanted to point out that 0.36 never was stable in the way that 1.0.0 will be.

That is exactly why most people are asking to put it back on stable. Hopefully the 1.0.0 will be released soon :smile:

Just a quick note that I've tested contextily on 1.0a9 and still fails with the dtype('uint8'). However, applying the str(dtype) patch gets it to pass the test suite.


Links between nodes disappear after upgrade to 3.0 under Safari

Current Behavior
All links between nodes are gone after upgrade. In Chromium everything is working fine, errors only in Safari
[Log] JQMIGRATE: Migrate is installed, version 3.3.0 (vendor.js, line 4)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (purify.min.js.map, line 0)
[Log] Node-RED: 3.0.0 (red.min.js, line 16)
[Log] Versions (red.min.js, line 16)
[Log] jQuery – "3.5.1" (red.min.js, line 16)
[Log] jQuery UI – "1.12.1" (red.min.js, line 16)
[Log] ACE – "1.4.12" (red.min.js, line 16)
[Log] MONACO – "0.33.0" (red.min.js, line 16)
[Log] D3 – "3.0.3" (red.min.js, line 16)
[Log] Projects disabled (red.min.js, line 16)
[Error] TypeError: Object.hasOwn is not a function. (In 'Object.hasOwn(RED.runtime,"started")', 'Object.hasOwn' is undefined)
	(anonimowa funkcja) (red.min.js:18:367295)
	(anonimowa funkcja) (vendor.js:37:9365)
	Tn (vendor.js:35:8232)
	(anonimowa funkcja) (vendor.js:37:9337)
	Gt (red.min.js:18:360913)

Expected Behavior
No response
Steps To Reproduce
Upgrade node-red to 3.0 and use Safari
Example flow
paste your flow here

Environment

Node-RED version: 3.0
Node.js version: docker image
npm version: docker image
Platform/OS: Linux/docker
Browser: Safari/macosx

What version of safari are you using? This error suggests you're using using an old unsupported version.

It is 15.3

Others on the forum have also noted this & updated Safari to 15.5 solves the issue.
However, thanks for reporting this - it seems Safari 15.3 doesn't support hasOwn which we may look at ways around it.


Make particles with DISABLE_Z active respect ALIGN_Y. Fixes #12865

This fixes bug #12865, I essentially just copied the code that handles FLAG_ALIGN_Y from the else-branch of FLAG_DISABLE_Z and adjusted it to leave the z coordinate untouched.

Thank you for contributing! Changes LGTM. Could you please squash commits together? (PR workflow)

Done! Thanks for handling this so swiftly!


Merging master back to develop

Merging master back to develop after someon must have merged directly to master...

not needed


feat: Trend Micro Cloud One - Conformity Quick start: Due by SEPT 10

New Relic’s integration with Trend Micro Cloud One - Conformity
Summary
New Relic’s integration with Trend Micro Cloud One - Conformity ingests cloud security posture management (CSPM)
data from Trend Micro Cloud One - Conformity into New Relic in real-time. The integration deploys a Amazon Web Services (AWS) CloudFormation stack in your AWS account.
Using this integration, our AWS, Microsoft Azure and Google Cloud Platform (GCP) customers can bring in their Conformity generated CSPM data into New Relic One where it's contextualized and correlated with workload telemetry data delivering AI powered visualizations and quick insights.
Screenshots

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

adding @jaesius as a reviewer...

There a few questions that we need to answer before merging this in, but overall this mostly checks out. I made some comments on the PR

I've responded to one of your comments regarding "-" in the name.

I will take a look today and push up any language changes needed.

The  checks are failing after merging in the suggested changes, it looks like the YML got a little messed up, will take a look at this.

closing for this PR which resolves all the problems in the yml
https://github.com/newrelic/newrelic-observability-packs/pull/222


Setup golang env for the build_docs job

While running the build_docs job in circle ci for #451 it complains about syntax errors in makefile
#!/bin/bash -eo pipefail
make build_docs

Makefile:130: *** target pattern contains no '%'.  Stop.
Exited with code 2

This is because there's no golang env setup in that machine and go env commands are not working.

This is fixed by #451


TS project wide doesn't work on safari

use safari
open https://insiders.vscode.dev/github/microsoft/vscode-markdown-languageservice?vscode-coi=
open index.ts
🐛 TS initialises forever, console shows the error below

[Error] Unhandled Promise Rejection: TypeError: undefined is not an object (evaluating 'f')
	(anonymous function) (tsserver.web.js:1:3637082)
	asyncFunctionResume
	dispatchEvent
	(anonymous function) (11a837e0-9d6d-4655-927a-465d3a6a4e5c:1:270)

After #176294, this now woks fine in Safari tech preview. I suspect there's an issue with our nested worker polyfil but am still looking into this

I've tried debugging what is going on here but can't figure it out (and safari's dev tools are certainly not helping)
What I suspect is that our nested worker polyfill causes a message to be dropped somewhere, possibly because a message port is started early or never started
Given that everything works in safari tech preview though and given that don't plan on shipping project wide intellisense until cross origin isolation is enabled, this is a lower priority. Un-assigning from this month

I believe this all works in Safari 16.4 which added nested worker support. Not sure what the issue was with our nested worker polyfill (note that #183482 needs to be merged too to see this working end to end)


[Bug]: Battery Present Ampers is in mA but data is in A

The problem
I think you have the calculations for mA and A the wrong way around.
I know I have 2.4A coming in. If I change the unit to mA I get 2.4, but if I change it to A it shows 0.00248.

(Also, the spelling of Ampers should be Amperes or Amps)
What version of Home Assistant?
core-2024.12.3
What version of Renogy?
1.0.0-b9
Diagnostics information
renogy.json
Anything in the logs that might be useful for us?
No response
Additional information
No response

No problem.
If you need anymore help/testing, I'm willing.

I would be great if they added the unit to their API output, perhaps emailing them would get them to add it.

email<EMAIL_ADDRESS>he's heading the API development and very will respond next day.

@craigusus looks like a backend change was done at Renogy. Did this change your issue? try reloading the integration.

looks like a backend change was done at Renogy

What do you mean?

for consistent units

So they changed it to mA for all the ampere readings?

thats what im trying to determine. Mine has not changed.

No mine are still in mA.
I did email cc.chang and ask if they could add something like the below:
    "data": {
        "communicationMethod": null,
        "presentCapacity": null,
        "error": null,
        "remainingTime": null,
        "heatingModeStatus": null,
        "temperature": "15",

        "temperatureUnit": "°C",

        "presentVolts": "12.80",
        "cellVolts": null,
        "maximumCapacity": "99.83",

        "maximumCapacityUnits": "%",

        "totalMaximumCapacity": "99.83",
        "firmwareVersion": "0026",
        "sku": null,
        "batteryLevel": "11.92",

        "batteryLevelUnits": "V",

        "presentAmps": "-0.15",

        "presentAmpsUnits": "A"
    }

But this is Renogy, they can't even quality control their own apps.

No mine are still in mA.

So it's still reporting as 0.00251 A ?

No mine are still in mA.

So it's still reporting as 0.00251 A ?

That's correct.


Test

Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 764cb464 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
223,044
868,028
3,449,708

l1_rollup_execution_gas
842,131
3,595,136
22,205,370

l2_block_processing_time_in_ms
1,390 (+5%)
5,293
21,037

note_successful_decrypting_time_in_ms
340
1,049 (-1%)
3,786

note_trial_decrypting_time_in_ms
52.8 (-1%)
38.1 (-8%)
135 (-1%)

l2_block_building_time_in_ms
13,631 (-1%)
53,723
217,019

l2_block_rollup_simulation_time_in_ms
10,077 (-1%)
39,719
160,844

l2_block_public_tx_process_time_in_ms
3,530
13,951
56,002

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,457 (-1%)
29,190

note_history_successful_decrypting_time_in_ms
2,448
4,762 (-4%)

note_history_trial_decrypting_time_in_ms
76.1 (-1%)
177 (+7%)

node_database_size_in_bytes
3,779,802
4,079,163

pxe_database_size_in_bytes
29,940
59,499

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
200
43,109
20,441

private-kernel-ordering
115
25,833
9,689

base-rollup
2,062
244,144
881

root-rollup
84.9 (+3%)
4,088
889

private-kernel-inner
261
64,516
20,441

public-kernel-private-input
172
25,203
20,441

public-kernel-non-first-iteration
171
25,245
20,441

merge-rollup
9.71
2,608
881

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
10,331
26,317


Cannot deploy contract with a header file.

I am unable to deploy a contract which has an added header file in this.
An example of this is depoying the eosio.token contract whose .cpp file requires a .hpp file (#include <eosio.token/eosio.token.hpp>)
Any way around this?

Hey; glad you used the tool. I assume you have resolved the issue by yourself or that you have closed this issue with help from someone else. However, in case you want extra clarification on this particular issue (or for others who are experiencing similar confusion), there is a way to deploy contracts requiring other .cpp or .hpp files.
Using the guide as a reference point, it is possible to bundle dependencies for your main .cpp file by organizing the folder accordingly. In the screenshot on that page, you can see that the .cpp file has the line #include "helpers/Characters.hpp, pointing to the ./helpers/Characters.hpp file in the Root Folder Path (so, the helpers folder has to be a sub-directory in the root folder path).
If you want to use #include <eosio.token/eosio.token.hpp> as an example, you would have to rewrite it as #include "eosio.token/eosio.token.hpp" and ensure that the eosio.token folder is a sub-directory of your working project folder.
I hope this is clearer for you and helps you to understand how to develop more complex smart contracts using the tool.

Thanks, what you have explained is what I did to make it run.
By changing the location of the header file to

and changing the #include of the cpp file to

I was able to point to the cpp file to the /src folder and was able to compile and upload the smart contract
:+1:


Weird formatting in details about validator

Problem
See screenshot

Expected Behavior
Not having these visual issues
Steps to reproduce

Open wallet with an account
Go to staking
Select specific pool with longer name - https://wallet.near.org/staking/buildlinks.poolv1.near

@corwinharrell do you have any ideas how we should format the account ID in these situations? I don't really see how we'd get around it.

@Patrick1904 a couple easy wins to start:

I don't think it needs to be so big. In the original design for the delegation flow, this type is 24px. On prod it's currently 28. That would give us a bit more breathing room. Once we have figured out a sensical way to concatenate long addresses, I think this is our best bet.

I know we removed the @ for usernames. Is there a reason that persists here?

@Patrick1904 a couple easy wins to start:

I don't think it needs to be so big. In the original design for the delegation flow, this type is 24px. On prod it's currently 28. That would give us a bit more breathing room. Once we have figured out a sensical way to concatenate long addresses, I think this is our best bet.
I know we removed the @ for usernames. Is there a reason that persists here?

Thank you! It's an H1 so font size is dynamic like all other H1's. I adjusted so that 24px is the min vs 28px.


yasnippet 0.11.0

Created with brew bump-formula-pr.

Looks like ERT wasn't added to Emacs until 24.1, so the dependency needs to be bumped.


Feat: Merge DetectErrors and PlotErrors and add a similar FinalCheck task

Description
The DetectErrors and PlotErrors are merged into one task to make it simpler. This new task is also called at the end of the Repair workflow in order to check which errors were fixed or created during the curation process.
Checklist

This pull request is:

[ ] A documentation / typographical error fix

Good to go, no issue or tests are needed

[ ] A short code fix

[ ] Please include: Fixes: #<issue number> in the description if it solves an existing issue
(which must include a complete example of the issue).
[ ] Please include tests that fail with the main branch and pass with the provided fix.

[x] A new feature implementation or update an existing feature

[ ] Please include: Fixes: #<issue number> in the description if it solves an existing issue
(which must include a complete example of the feature).
[x] Please include tests that cover every lines of the new/updated feature.
[ ] Please update the documentation to describe the new/updated feature.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 83.99%. Comparing base (e23e232) to head (3312745).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #148      +/-   ##
==========================================
+ Coverage   83.95%   83.99%   +0.04%
==========================================
  Files          15       15
  Lines        1901     1906       +5
  Branches      303      304       +1
==========================================
+ Hits         1596     1601       +5
  Misses        209      209
  Partials       96       96

Flag
Coverage Δ

pytest
83.94% <100.00%> (+0.04%)
:arrow_up:

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

Files
Coverage Δ

src/morphology_workflows/curation.py
82.26% <100.00%> (+0.15%)
:arrow_up:

src/morphology_workflows/tasks/curation.py
100.00% <ø> (ø)

src/morphology_workflows/tasks/repair.py
100.00% <100.00%> (ø)

src/morphology_workflows/tasks/workflows.py
96.59% <100.00%> (ø)


ENH: Update to 1.4.0

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Cycle to get circleci to run.


Remove deprecated Docker Content Trust ENV passphrase variables

Since 1.9, Docker Content Trust Offline key has been renamed to Root key and the Tagging key has been renamed to Repository key.
The corresponding environment variables
DOCKER_CONTENT_TRUST_OFFLINE_PASSPHRASE
DOCKER_CONTENT_TRUST_TAGGING_PASSPHRASE
have also been deprecated and renamed to
DOCKER_CONTENT_TRUST_ROOT_PASSPHRASE
DOCKER_CONTENT_TRUST_REPOSITORY_PASSPHRASE
This fix removed the deprecated ENV passphrase variables for 1.12 and updated the docs.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

LGTM
ping @endophage @cyli @riyazdf ptal

LGTM

Yep, LGTM.

LGTM
@cyli would you mind to open docs PR for your suggest?

@LK4D4 Done:  https://github.com/docker/docker/pull/22609


[Home Assistant Git Exporter] Make branch configurable

Which addon?
Home Assistant Git Exporter
Is your feature request related to a problem? Please describe.
Many developers are switching from master being the default to main due to the connotations of main being more neutral than the former.
See https://github.com/github/renaming - https://sfconservancy.org/news/2020/jun/23/gitbranchname/
Unfortunately it appears that the master branch is hard coded at the following points:
https://github.com/Poeschl/Hassio-Addons/blob/91e740ad27e140e1450eea1acbce8ef18a52d3f8/git-exporter/root/run.sh#L48
https://github.com/Poeschl/Hassio-Addons/blob/91e740ad27e140e1450eea1acbce8ef18a52d3f8/git-exporter/root/run.sh#L190
This prevents the add-on from working with repositories that do not use the legacy naming scheme 😢
Describe the solution you'd like
It would be awesome if we could configure the branch name under repository.branch. (I'm happy to produce a PR if the issue is accepted 👌🏻)
Describe alternatives you've considered
Renaming to master or running both branches side by side would allow the add-on to function but this would be a messy workaround IMO.
Additional context
None to add.

I would go for a configurable branch name where the addon is pushing and pulling. 😉
Like you suggested a setting could specify the branch. The default for it should be main then.
A PR is more than welcome.

@notorious-gay How is it going? I see you made already a branch ;)


functional: clean up obsolete commands that are commented out

Just a cleanup for removing obsolete commands that have been already commented out.
Suggested by @jonboulle

lgtm, thanks!


TypeError: Cannot read property '239' of undefined

TypeScript Version:  2.5.2 / nightly (2.5.0-dev.201xxxxx)
Code
I'm upgrading my 2.3 project to 2.5 and I'm getting this really cryptic error:
❯❯❯ ./node_modules/.bin/tsc --noEmit
/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:56136
                throw e;
                ^

TypeError: Cannot read property '239' of undefined
    at getDeclarationSpaces (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:33091:52)
    at checkExportsOnMergedDeclarations (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:33037:41)
    at checkInterfaceDeclaration (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:34730:17)
    at checkSourceElement (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:35469:28)
    at Object.forEach (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:275:30)
    at checkSourceFileWorker (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:35536:20)
    at checkSourceFile (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:35521:13)
    at getDiagnosticsWorker (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:35574:17)
    at Object.getDiagnostics (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:35563:24)
    at /Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:56151:85
    at runWithCancellationToken (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:56129:24)
    at getSemanticDiagnosticsForFileNoCache (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:56143:20)
    at getAndCacheDiagnostics (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:56351:26)
    at getSemanticDiagnosticsForFile (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:56140:20)
    at /Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:56097:24
    at Object.flatMap (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:507:25)
    at getDiagnosticsHelper (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:56093:56)
    at Object.getSemanticDiagnostics (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:56104:20)
    at compileProgram (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:59094:43)
    at compile (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:59051:26)
    at performCompilation (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:58940:33)
    at Object.executeCommandLine (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:58883:9)
    at Object.<anonymous> (/Users/chet/Code/notion-next/node_modules/typescript/lib/tsc.js:59241:4)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/chet/Code/notion-next/node_modules/typescript/bin/tsc:2:1)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:427:7)
    at startup (bootstrap_node.js:151:9)
    at bootstrap_node.js:542:3

Expected behavior:
I would expect an error that tells me something about how I can fix this...
Actual behavior:

Hmm. Just found this issue which could be useful: https://github.com/Microsoft/TypeScript/issues/17982

This helped! I had the debugger stop on uncaught exception and found that the error was defining a type with the same name as an import.
❯❯❯ node --inspect --debug-brk node_modules/.bin/tsc -p .

It would be nice if this was reported to the user.

@ccorcos can you share a simple repro with the issue?

Hmm. I spent a solid 30 minutes this morning and I'm unable to come up with something minimal :/
In my circumstance, it had to do with an import and an interface having a name collision. There was a lot of JSX in that file and the name collision was for a component. But I'm unable to reproduce it in a minimal example... I guess we'll just hope someone else runs into this and finds this issue.

@ccorcos Don't worry my man, I have a repro for you:
// @filename: b.ts
export const zzz = 123;
export default zzz;

// @filename: a.ts
export interface zzz {
    x: string;
}

import zzz from "./b";

const x: zzz = { x: "" };
zzz;

export default zzz;

// @filename: index.ts
import zzz from "./a";

const x: zzz = { x: "" };
zzz;

import originalZZZ from "./b";
originalZZZ;

const y: originalZZZ = x;

And a fix forthcoming.


Use OSSRH snapshot repository to host snapshot releases.

Closes #4346.
Changes proposed in this pull request:

integrate snapshot uploading into the Maven build process (for the standard deploy goal)
remove scripts to upload to GitHub releases

This might need merging before it can be tested.

Merging to try it out.


Fetcher should extract by default, if not defined.

cc @turb

@brndnmtthws since it is Mesos default, I agree we should follow it.
cf. Mesos fetcher documentation


Add GELU to activations.py

Summary
Add GELU activation functions. Here are the fast and slow implementations.
Related Issues
This issue
PR Overview
Adds two GELU implementations : one fast and one slow to activations.py.

[n] This PR requires new unit tests [y/n] (make sure tests are included)
[y] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[y] This PR is backwards compatible [y/n]
[n] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

Please stop opening new PRs when making commits. I'll close and let your newest open.
I don't think this should be merged into Keras.
Not widely used
Not published yet
Please submit your PR at keras-contrib.


Is 1080p 30fps really supported?

Hi,
You wrote:
"

But where bandwidth is not a concern, experiences can be optimized for quality, including up to 1080p video resolution, up to 30fps for video and 15fps for content, and high-fidelity audio

"
Correct me if I'm wrong, but I have not heard yet that Teams supports Full HD (1080p) on video meetings, except on screen/application sharing.

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

ID: 8e8b2651-40bb-0d26-6126-d88689047f23
Version Independent ID: 5be83c7d-ef7f-5582-4a6c-f0709fb2ec7b
Content: Prepare your network for Microsoft Teams - Microsoft Teams
Content Source: Teams/upgrade-prepare-environment-prepare-network.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@Petri-X  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @Petri-X, thank you for your feedback.
I understand it's supported. There are more articles which mention 1080p:
https://docs.microsoft.com/microsoftteams/prepare-network#bandwidth-requirements
https://docs.microsoft.com/microsoftteams/platform/bots/calls-and-meetings/real-time-media-concepts#video-format

@Petri-X Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


DSP Dark Fog Items: Missing extra products spray, only speedup available

Describe the bug
No new items for the dark fog appear to be able to procude extra products and only allow you to select speedup for the proflieration sprays.
To Reproduce
Select any new item from the dark fog update  and ensure you have a spray selected. Any new items In the recipe chain will also not have the extra products, even when they should.
Expected behavior
E.g on missile sets, you should be able to select extra products as well. I have tested in game and yes extra products option is available for all missiles and their requirements.
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
Windows 10, Chrome Version 120.0.6099.129 (Official Build) (64-bit)
Smartphone (please complete the following information):
Additional context

Ah yeah, I forgot to update that
Will update and push in a few mins

@DanTheManOg
Can you check if you are seeing the expected behaviour?
If you are satisfied, you can close the issue


Paste from clipboard not working

Using OSX 10.9.5 and Java version 1.8.0_60, paste from clipboard functionality does not respond when clicked. I have confirmed that the data was in the clipboard by pasting into both a text editor and Excel.

@jthevos, thanks again for reporting. If you have time, steps/data to reproduce are really the only way I can debug this.

Closed because @jthevos never provided steps to reproduce.


Updated demo link.

Updated demo link to include password-field.

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


gpt4all: Request failed: HTTP 404 Not Found (type=value_error)

Hi, whenever I try to load a gpt4all model, I get an error, e.g., with an example from https://github.com/h2oai/h2ogpt/blob/main/docs/README_CPU.md
$ python generate.py --base_model=gpt4all_llama --model_name_gpt4all_llama=ggml-wizardLM-7B.q4_2.bin --score_model=None --langchain_mode='UserData' --user_path=user_path
soundfile, librosa, and wavio not installed, disabling STT
soundfile, librosa, and wavio not installed, disabling TTS
Using Model gpt4all_llama
load INSTRUCTOR_Transformer
max_seq_length  512
Must install DocTR and LangChain installed if enabled DocTR, disabling
0it [00:00, ?it/s]huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
        - Avoid using `tokenizers` before the fork if possible
        - Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 18/18 [00:02<00:00,  7.11it/s]
Loaded 18 new files as sources to add to UserData
Existing db, potentially adding 2878 sources from user_path=user_path
Found 0 new sources (0 have no hash in original source, so have to reprocess for migration to sources with hash)
Removing 0 duplicate files from db because ingesting those as new documents
Existing db, added 0 new sources from user_path=user_path
Starting get_model: gpt4all_llama
Starting get_model: gpt4all_llama
Starting get_model: gpt4all_llama
Starting get_model: gpt4all_llama
Traceback (most recent call last):
  File "/home/alex/Documents/doc_search_kb/h2ogpt/generate.py", line 16, in <module>
    entrypoint_main()
  File "/home/alex/Documents/doc_search_kb/h2ogpt/generate.py", line 12, in entrypoint_main
    H2O_Fire(main)
  File "/home/alex/Documents/doc_search_kb/h2ogpt/src/utils.py", line 65, in H2O_Fire
    fire.Fire(component=component, command=args)
  File "/home/alex/Documents/doc_search_kb/venv/lib/python3.11/site-packages/fire/core.py", line 141, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/alex/Documents/doc_search_kb/venv/lib/python3.11/site-packages/fire/core.py", line 475, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
                                ^^^^^^^^^^^^^^^^^^^^
  File "/home/alex/Documents/doc_search_kb/venv/lib/python3.11/site-packages/fire/core.py", line 691, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
                ^^^^^^^^^^^^^^^^^^^^^^
  File "/home/alex/Documents/doc_search_kb/h2ogpt/src/gen.py", line 1977, in main
    model0, tokenizer0, device = get_model_retry(reward_type=False,
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/alex/Documents/doc_search_kb/h2ogpt/src/gen.py", line 2305, in get_model_retry
    model1, tokenizer1, device1 = get_model(**kwargs)
                                  ^^^^^^^^^^^^^^^^^^^
  File "/home/alex/Documents/doc_search_kb/h2ogpt/src/gen.py", line 2717, in get_model
    model, tokenizer, device = get_model_tokenizer_gpt4all(base_model,
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/alex/Documents/doc_search_kb/h2ogpt/src/gpt4all_llm.py", line 30, in get_model_tokenizer_gpt4all
    model, tokenizer, redo, max_seq_len = get_llm_gpt4all(**llama_kwargs)
                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/alex/Documents/doc_search_kb/h2ogpt/src/gpt4all_llm.py", line 217, in get_llm_gpt4all
    llm = cls(**model_kwargs)
          ^^^^^^^^^^^^^^^^^^^
  File "/home/alex/Documents/doc_search_kb/venv/lib/python3.11/site-packages/langchain_core/load/serializable.py", line 107, in __init__
    super().__init__(**kwargs)
  File "/home/alex/Documents/doc_search_kb/venv/lib/python3.11/site-packages/pydantic/v1/main.py", line 341, in __init__
    raise validation_error
pydantic.v1.error_wrappers.ValidationError: 1 validation error for H2OGPT4All
__root__
  Request failed: HTTP 404 Not Found (type=value_error)

Even if I download the model manually from https://gpt4all.io/models/ggml-wizardLM-7B.q4_2.bin
$ ls -lh llamacpp_path/ggml-wizardLM-7B.q4_2.bin
-rw-r--r-- 1 alex alex 4.0G Feb  7 16:16 llamacpp_path/ggml-wizardLM-7B.q4_2.bin

Thanks

I don't recommend gpt4all models, I haven't tried to maintain them and I think they typically don't work on GPU and are CPU only.  In any case I recommend llama.cpp models, i.e. GGUF.
I didn't design h2oGPT to accept urls for gpt4all models.  The version I use automatically downloads models by name as described in the h2oGPT docs. https://github.com/h2oai/h2ogpt/blob/main/docs/FAQ.md#gpt4all
However, I can run your exactly command fine.  Just takes a while since runs on CPU.
python generate.py --base_model=gpt4all_llama --model_name_gpt4all_llama=ggml-wizardLM-7B.q4_2.bin --score_model=None --langchain_mode='UserData' --user_path=user_path

Basic case:

Uploaded doc and then asked question, but it takes WAY too long to be useful.

Note that gpt4all models do not go to llamacpp_path, that's only for llama.cpp models.  gpt4all models to to their own ~
/.cache location automatically.
However, I think you can provide the full absolute path and it'll work.

It's also possible they changed what models are available.  In any case, I don't plan to maintain the gpt4all models, but happy if someone helps you or provides any solutions.

@pseudotensor Thank you for your reply! I don't know why the command doesn't work for me, but I'll stick to GGUF then :smiley:


[BUG] Failed test diagnostics don't get shown immediately, but only after saving the file. (Due to inconsistent path slash usage -> \ and /)

Hey 👋, thanks again for this great plugin.
On my machine, when a test fails, the diagnostics for it do not get shown immediately. But only after I do some action, for example, saving the file. I looked through the source code and I think I found the issue. It seems to be in here:
https://github.com/nvim-neotest/neotest/blob/604dd922ad461f08048010505b7056f613b4d478/lua/neotest/consumers/diagnostic.lua#L191-L214
At these lines, the buffer paths get saved:
https://github.com/nvim-neotest/neotest/blob/604dd922ad461f08048010505b7056f613b4d478/lua/neotest/consumers/diagnostic.lua#L200-L203
And here they get checked:
https://github.com/nvim-neotest/neotest/blob/604dd922ad461f08048010505b7056f613b4d478/lua/neotest/consumers/diagnostic.lua#L207-L209
The issue is that valid_bufs and node:data().path have different ways of storing slashes. Example of printing these variables on my machine:
valid_bufs:
{
  ["C:\\Users\\X/MyStuff/Programming/Business/X/frontend/src/app/sign-up-form/login-form.component.spec.ts"] = true,
}

node:data().path:
C:\\Users\\X\\MyStuff\\Programming\\Business\\X\\frontend\\src\\app\\sign-up-form\\login-form.component.spec.ts

Because of that, the if check does not succeed, and the buffer does not get redrawn with the symbols. I would be nice to fix this.
Also, I think it is worth it to see if the same thing is also done in other parts of the code, maybe there is the same issue at other places.
Thank you for your help! :)

Thanks for the report, could you please try the latest commit? Don't have windows so can't confirm but think this should be fixed

It seems to work perfectly! Thanks :)


Daemon ecr release publish

Issue #, if available:
Description of changes:

Added workflow that can be triggered manually (at the time of the release) to publish daemon image to docker hub and ECR.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Change the registry_alias (bold in below Hint) in build and push step (tags) after creating public ECR repo for production account.
Hint: public.ecr.aws/u5g3z6k3/amazon/aws-xray-daemon:alpha


Does it support java properties format?

monaco-editor version: 0.X.Y
Browser:
OS:
Steps or JS usage snippet reproducing the issue:

Not at this time.


Adding a way to specify out of core from the command line

What do these changes do?
Creates a way to use larger than memory dataframes in Modin without having to initialize Ray first.

Related issue number

[x] passes git diff upstream/master -u -- "*.py" | flake8 --diff
[x] passes black --check modin/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/62/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/124/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/125/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/63/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/64/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/126/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-Performance-PRB/65/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Modin-PRB/127/
Test PASSed.

Merged build finished. Test PASSed.

This will be blocked on https://github.com/ray-project/ray/issues/3450


add 鉅亨財經新聞 showcase

By analyzing the blame information on this pull request, we identified @brentvatne and @manonthemat to be potential reviewers.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

@blackbing Please sign the CLA, once you do I can merge this. 👍

Done, thanks.

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


[Feature Request] A way to disable dismiss swipe

Is your feature request related to a problem? Please describe.
I use modals that I need the user to interact with. It is very interesting to me that the user cannot ignore it with swipe.
Describe the solution you'd like
Boolean "isSwipeable" to enable/disable swipe.
Describe alternatives you've considered
Place a gesture handler over the entire component to inhibit user gestures. But it affects the buttons.

Fact: "swipeDirection: undefined" inhibits Swipe, but if the user still has access to the transparent black overlay on the back, clicking it dismisses the modal.

    magicModal.show(ExampleModal, {       swipeDirection: undefined,       onBackdropPress: () => null,     });
Solve the problem. Sorry, I really need sleep lol. Anyway, I'll leave this FR grip, I think it might be something interesting.

That's really it! The config params will accept most properties from the original react-native-modal.
I'll keep the issue open untill I add more examples for those use-cases.


Add a --proxy parameter to kotatsu serve

A full featured development experience requires both:

kotatsu start src/server.js
kotatsu serve src/public.js

Unless I missed something, a load balancer is required to expose both on a single port.
Adding a --proxy parameter would ease development workflow (for instance using concurrently):
concurrent --kill-others \
  "kotatsu start src/server.js --port 1338" \
  "kotatsu serve src/public.js --port 1337 --proxy http://localhost:1338"

By the way I would suggest using webpack-dev-server instead of custom server, and forward devServer key from configuration in the webpack configuration.

Hello @themouette. Is this a problem to serve on two different ports? Also, you are using the --port option with the start command and this does nothing. The start command doesn't need a port. I guess the server.js scripts spawns an express app and you will set the port by using app.listen(1338).
Concerning webpack-dev-server I use webpack-dev-middleware which has quite the same effect. I can use this middleware along with webpack-hot-middleware etc. to better customize the server offered by the tool if needed.

Apart from that, let me check if I can quickly add a --proxy option.

Hello @Yomguithereal,
thanks for the (very) quick answer. Indeed, start and --port 1338 was a mistake, I tough it made the example easier to follow though.
Using a single port makes it more production like by providing a single entrypoint, but I get your point, CORS and configuration can do the trick.
I understand the flexibility of webpack-dev-middleware and webpack-hot-middleware and that's fine. The suggestion was based on the following thoughts:

webpack-dev-middleware never access webpack config, so it makes it impossible to provide a custom configuration for it outside of cli options;
webpack-dev-server seems to provide standard features;
webpack-dev-server is widely used by the community.

Yes I tend to use CORS generally so I unintentionally discarded other options, which is bad. So I'll try to add a --proxy option.
I thought that the webpack team deprecated the webpack-dev-server. I may be wrong. Let me check whether it return an express app before switching to it (plus you are right it has a proxy option which could come in handy in your case).

I am reading the code of webpack-dev-server and I am not very fond of what it offers more than the middleware. However, I see that (apart from the proxy option, but I will fix that :) ), the middleware takes the same options as the server. So what I will do is make sure the devServer options of the config are passed to the middleware.

So what I will do is make sure the devServer options of the config are passed to the middleware.

Looks good to me. thanks a lot.

@themouette, here is what I propose:
--proxy [namespace] [target]
# example
--proxy / http://localhost:8000
--proxy /api http://localhost:8000

You rock !

Just published 0.8.0 on npm. Tell me if this suits your needs :smile:.

that's perfect.


Relese job time out: setup command should be called before executing release job

Orb version:
2.3.0
What happened:
The release job will time out waiting for an interactive prompt.
gh config set prompt disabled

should be called before.
Expected behavior:

Call the setup command before using the cli.

This could be a solution:
https://github.com/CircleCI-Public/github-cli-orb/pull/49

Or calling the gh config set prompt disabled method in the install scipt

Any updates on this? Release job is still non-functional...

#49 was merged an released, if that fixed the problem please close the issue, otherwise provide more details.


Create two-level hierarchy

[x] Develop a general hierarchy API
Determine what it should be templated on. Right now, Mesh, Operator and MultiVector. However, it is unclear how Operator and Mesh should be separated. Should it be templated on the device too, or is it a part of Operator?
[x] Write a Level specialization for dealii host
[x] Write a Level specialization for dealii device

Done in #27 and #60.


Updates for Scala 2.13

Moved from: https://github.com/sangria-graphql/sangria-argonaut/pull/2
No errors from:
sbt ++2.11.12 mimaReportBinaryIssues
sbt ++2.12.10 mimaReportBinaryIssues

Note that 1.0.0 depended on Argonaut 6.2-RC2, and this release bumps that to 6.2.3. 6.2-RC2 was the last release candidate for RC2, and at a glance over git diff v6.2-RC2..v6.2 in an Argonaut checkout I think we're okay there, so I've only done a patch version bump. If anyone has concerns about this we can do a major bump.

The CI failure was because of Scoverage on 2.13.1. I've changed back to 2.13.0 for now.


chore(deps): Update uuid and @types/uuid

Proposed Changes

Bump uuid from 9.0.0 to 9.0.1
Bump @types/uuid from 9.0.0 to 9.0.8

Test Plan
My intent is that this will pass in CI and fix the statusboard entry for this repo.
It looks like the "Merge Me" workflow doesn't have a required permission though.
https://github.com/webdriverio-community/wdio-rerun-service/actions/runs/8137452602

Thanks for this - not sure how strict @christian-bromann wants to be as far as the eslint warnings that have appeared. I want to wrap up #68 and then I will do a general dependency bump and release with this included.

We can close this if it is easier for you. I hoped an easy PR would fix the build and get us back to green on https://webdriverio.github.io/statusboard/. It turns out the Merge Me workflow is missing a permission. I'd say we delete that here and in the Angular webdriverio-schematic repo too for now.


mfc465cn[lpr,cupswrapper]: init at 1.0.1-1

Description of changes
This package consists of the driver as well as the cupswrapper for the MFC-465CN printer by brother: https://support.brother.com/g/b/downloadlist.aspx?c=us&lang=en&prod=mfc5460cn_all&os=128
Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Hey, welcome to nixpkgs!
We need references to those two packages in pkgs/top-level/all-packages.nix, then others can nix-build -A <attribute> to build them.
We also require individual commits per attribute you are touching, so that would be one for adding yourself as a maintainer, then one for each package.
Thanks!

Hey, welcome to nixpkgs!
We need references to those two packages in pkgs/top-level/all-packages.nix, then others can nix-build -A <attribute> to build them.
We also require individual commits per attribute you are touching, so that would be one for adding yourself as a maintainer, then one for each package.
Thanks!

Thanks for the heads-up. I did as told :)

Sorry for the mess, it should be fine now.

The commits adding the files to pkgs/top-level/all-packages.nix will have to be squashed into the commits for adding the files. In the end, there should be one commit for each package, with each commit adding the new file for the package and adding the line in all-packages.nix.

The commits adding the files to pkgs/top-level/all-packages.nix will have to be squashed into the commits for adding the files. In the end, there should be one commit for each package, with each commit adding the new file for the package and adding the line in all-packages.nix.

Ahh thanks.

Hey, welcome to nixpkgs!
We need references to those two packages in pkgs/top-level/all-packages.nix, then others can nix-build -A <attribute> to build them.
We also require individual commits per attribute you are touching, so that would be one for adding yourself as a maintainer, then one for each package.
Thanks!

Then I did not understand this correctly, I thought I need a commit for each file that has changed.
Nevertheless it should be correct now.


Thank you very much and keep up the good work! :)

Sure.  Closed because #7 replaces it.


Animations stop working after animated sprite destroyed

On /beta, after you destroy a sprite with animation attached, future animations appear to not work.
Here is a simple repro: https://makecode.com/_5caCughHWdqW. Pressing A will replace the bobbing Taco with a bobbing Donut.
On regular Arcade (what that share link points to), this code works fine. But in /beta, the Donut does not bob.

Seems like a duplicate of https://github.com/microsoft/pxt-arcade/issues/2033.


add a1 legacy token integration test

Adding the test now since I've just been messing with this for acceptance testing.

[x] see test pass correctly (the logs have a permission granted line, so the 400 is the ingestion handler)
[x] move into nightlies 🌃

@stevendanna absolutely! thanks for the hint

I'll move it once I'm satisfied with the test script.

@chef/automate-deployment-team What do think about https://github.com/chef/automate/pull/3600/commits/5bcd4125d3785180f82a35a94654c165401bcc51? I can drop it, it just seemed like it belonged there.


How to query in Advanced find?

How to perform test automation for querying advanced find?
Such as openAdvancedFInd() and then look for contacts entity and selected a field. something like that using easyRepro.

Not sure if that's something on the road map (currently called out as not supported) - but I was wondering what scenario you were testing that relied on this? Since advanced find is something that can't really be changed it seems like you could probably make your test case a little more terse by skipping over this.

@jlattimer I am looking for similar thing because we want to run a workflow on a view in advanced find. Is there a different way to achieve this?
For Example: I should be running a workflow to change a value on My Accounts View from advanced find


Disable Chat Panel when task is finished

What problem or use case are you trying to solve?
When a task is finished, the chat panel is still active and allows inputs, even though it won't do anything:

Note: to reproduce this, you need to use an agent other than CodeAct*Agent which never finishes (before #2673 is merged).
Describe the UX of the solution you'd like
Disable the chat textbox when agent has finished the task.
Do you have thoughts on the technical implementation?
Describe alternatives you've considered
Additional context

Can you elaborate what exactly you'd like to disable? The user's textarea for input?

Can you elaborate what exactly you'd like to disable? The user's textarea for input?

Yep

Can you elaborate what exactly you'd like to disable? The user's textarea for input?

Yep

Ok, so if a task is "finished", why shouldn't the user be able to continue the chat session?

Ok, so if a task is "finished", why shouldn't the user be able to continue the chat session?

I thought simply disabling textarea is a simple and quick fix - likely one-liner.
Allowing the user to be able to continue the chat session sounds like a plan - we need backend changes though. We may also need to keep in mind that it could have other implications. For example, even though the user's intention is to start a new task, they might very likely continue using the same chat session and hit out-of-budget or max_iterations error pretty soon.

I'm a bit confused right now what the disabling is trying to fix?
It is the "normal" user UI operation that I give smaller or bigger tasks.
Sometimes the LLM marks them as finished, but that doesn't mean that I as a user am finished.
Any other web UI has continouus chat, I don't see why we would suddenly limit it to an arbitrary "one task" use? 🤔

Sometimes the LLM marks them as finished, but that doesn't mean that I as a user am finished.

Did you try continue the chat even if LLM marks them as finished? Per my testing (see the screenshots in the first post) it won't do anything.

I did more testing and realized it might just be an issue with certain agents: BrowsingAgent, DelegatorAgent, and probably more.

I haven't had an issue with CodeActAgent stopping on me with being finished.
If your screenshot is coming from delegation (browser agent?), and it gets stuck on finish, sure, that needs backend fixes.
But till then disabling user input is not the right way.

Note: to reproduce this, you need to use an agent other than CodeAct*Agent which never finishes (before https://github.com/OpenDevin/OpenDevin/pull/2673 is merged).

CodeActAgent never "stops" so you won't have an issue 😉

So glad about that! 🤣
Kidding aside, should we just re-check that all agents can react appropriately send and/or parse the "finish" tag and act accordingly?

should we just re-check that all agents

Totally. I rewrote the description and removed "good first issue" label. This is harder than just disabling textarea. Even if we want to do it (because some agents are hard to take further input or by design they cannot), we shall do it only for certain agents.

For example, even though the user's intention is to start a new task, they might very likely continue using the same chat session and hit out-of-budget or max_iterations error pretty soon.

I wonder how much good do these limits for interactive sessions. For non-interactive sessions, sure.


[DO NOT MERGE YET] GH-672: Fix SpEL parsing for @RabbitListener

Fixes spring-projects/spring-amqp#672
The StandardBeanExpressionResolver is based on the
TemplateAwareExpressionParser which can parse any string to the
LiteralExpression or to the CompositeStringExpression if
template tokens (#{ & }) are present in the source expression.
This way we don't need to deal with literal concatenations within
templated expression.
The expression like #{'foo.' + myBean.bar} can be replaced
with the foo.#{myBean.bar}

Do not merge yet: need team agreement.


TLSProxy requires ossltest engine

The TLSProxy tests currently require the use of the ossltest engine, that turns encryption largely into no-ops, produces constant strings as digest output, etc., so that the wire-format TLS messages can be inspected and modified by the perl layer.
However, ENGINE is slated for deprecation, so eventually ossltest will need to become a provider.  It is not entirely clear when the best time to effectuate that conversion will be, though.

That can IMO wait post 3.0.0.

That can IMO wait post 3.0.0.


[Feature Request]: Specify database role while initializing Spanner client

What would you like to happen?
Cloud spanner is introducing a new attribute in SpannerConfig to support role-based access control. The database role should be specified while initializing the Spanner database client.
Issue Priority
Priority: 2
Issue Component
Component: io-java-gcp

.take-issue


论文LightNER所说的附录没找到

Describe the question

A clear and concise description of what the question is.

LightNER: A Lightweight Generative Framework with Prompt-guided Attention for Low-resource NER论文中在5 Experiments开头说的Our experiments are evaluated in an exact match scenario and implementation details are presented in the appendix.“”，其中这个 appendix我在最后一节7 Conclusion and Future Work后没找到。
Environment (please complete the following information):

OS: [e.g. mac / window]
Python Version [e.g. 3.6]

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

https://arxiv.org/pdf/2109.00720.pdf 附录在第12页

收到


Add new commands repo_package_add and repo_package_delete

This introduces repo_package_add and repo_package_delete, which can be used to add (existing) packages to repositories and delete packages from repositories.

Coverage remained the same at 100.0% when pulling 44c7c2813627beee345280dfdd07476c6d793e0b on SHyx0rmZ:add-repo_package_add-and-repo_package_delete into 617e59967f3503d2945e50cd0abd78b512b138cb on sepulworld:master.

This is awesome!  Thank you for adding 👍 and the tests! Ill check it out asap

Maybe checkout out the Hound lint responses if you have a sec? Just to keep things uniform

Yes, will do. I had most of the formatting right, but apparently the git stash and my IDE messed it up and I am too tired to notice.

Coverage remained the same at 100.0% when pulling 9663b8d6b2f328f2cdb7bb5de0f96f9cced429a2 on SHyx0rmZ:add-repo_package_add-and-repo_package_delete into 617e59967f3503d2945e50cd0abd78b512b138cb on sepulworld:master.

Coverage remained the same at 100.0% when pulling cc7248b53b0bbc4944135ba8a78ca9b7c65d8f9e on SHyx0rmZ:add-repo_package_add-and-repo_package_delete into 617e59967f3503d2945e50cd0abd78b512b138cb on sepulworld:master.

If it's okay with you I'll leave the long lines unchanged.

Coverage remained the same at 100.0% when pulling b1d452ca58c88b78866bbae92dea03a6ecb56465 on SHyx0rmZ:add-repo_package_add-and-repo_package_delete into 617e59967f3503d2945e50cd0abd78b512b138cb on sepulworld:master.

Good looking out, no worries on long lines. Ok give me a chance to test these new options out. :)


Hilla project depends on Platform

As Hilla depends on Platform, when a new major/minor version is created, the build doesn't work due to circular dependency: Hilla cannot test itself due to missing corresponding Platform packages.
A solution could be to use Platform dependencies directly instead of depending on Platform

i made a PR here https://github.com/vaadin/hilla/pull/570 and tried to use snapshot versions of flow, flow-components instead of platform.  the build is failed at the moment as there is a missing dependency in WC, which failed when using with vite 3.1.0.
we can try if this one works or not, after the next WC release.
i also saw there are versions used in package.json, I am not sure what we can do with those, are they hardcoded?


PSA: Exceptions in Future are hidden

    Future {
      throw new Exception
    }

This code does nothing at all, the app doesn't force close, and the error isn't even logged. As a workaround, you can do this:
    Future {
      throw new Exception
    }.onFailure { case e =>
      Log.w(Tag, "Error in future", e)
    }

I don't know if this can by fixed by the gradle plugin, but if not, you should probably use the workaround in your code.

I think you can use a custom ExecutionContext with an overridden reportFailure method, like so: https://github.com/macroid/macroid/blob/master/macroid-core/src/main/scala/macroid/UiThreading.scala#L9

@stanch According to doc: Failed tasks should call reportFailure to let the ExecutionContext log the problem or whatever is appropriate for the implementation.
And as I've tested with the code below, method reportFailure was not called.
Future(throw new Exception("Test"))(customExecutionContext)


Update link to linear algebra content

Updates the link to the linear algebra content from the notebooks/ch-states/introduction.ipynb notebook ... current link results in a 404

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


IdeaAudio - does it have java wrapper?

Hi :)
I watched the stackoverflow issue http://stackoverflow.com/a/17993976/6312069 which describes how to get io devices list; But I couldn't get it... does the IdeaAudio have java wrapper?
Thanks

Duplicate of #1


MainApp: bump SociaLite version number to v1.3.2

We forgot to do this for the past releases, and we should also do this before the v1.4 release as well.

Actually should we just change it to v1.4 first?

Yeah, will just change to v1.4 now.


When grpc generates a controller, replace - with _

1. What version of Go and system type/arch are you using?

2. What version of GoFrame are you using?

3. Can this issue be re-produced with the latest release?
4. What did you do?

中文：gf的项目名称带了-关键字，在 gprc 生成 controller 的时候，controller 的包名也是带 - 的，这个是不符合 go 的包名规范的，而对于项目来说，很多人会以 - 来命名项目，应该将项目名称中带 - 的，替换为 _ 下划线，这样就符合规范了
英文：The project name of gf has the - keyword. When gprc generates controller, the package name of controller also contains -. This does not conform to the package name specification of go. For the project For example, many people will name projects with -, you should replace - in the project name with _ underscore, so that it conforms to the specification
5. What did you expect to see?
6. What did you see instead?

fix pull request: #2630

merge


404 on cri-containerd 1.2.8

1.2.8 was released but https://storage.googleapis.com/cri-containerd-release/cri-containerd-1.2.8.linux-amd64.tar.gz is not found.

Done

Looks good. Thank you!


Extension - Update content on unstake screen for some earning options

Describe the task

[x] Update content when ustake liquid staking on Bifrost

Link feedback : https://discord.com/channels/447263980252037141/959293613269995530/1293912035410841600
Link content: https://www.notion.so/subwallet/Chu-n-ho-content-khi-unstake-Bifrost-Liquid-staking-55dbf7cc35104a7dad990c1649cc7f7e?pvs=4#5a4752a8b5af49b498aa1a7806488115

[x] Update content when unstake Bittensor
https://www.notion.so/subwallet/Chu-n-ho-content-khi-unstake-Bifrost-Liquid-staking-55dbf7cc35104a7dad990c1649cc7f7e?pvs=4#1e4c163ee12d4983bb89a1530d7f09cb

Version test : http://<IP_ADDRESS>:8900/s/xLCDizFyqifeGQr

[ ] Update content when unstake Bittensor

[ ] Update content when ustake liquid staking on Bifrost

Expect : https://www.notion.so/subwallet/Chu-n-ho-content-khi-unstake-Bifrost-Liquid-staking-55dbf7cc35104a7dad990c1649cc7f7e?pvs=4#9875983c4aef4752a8f5a953838a7854

Version test: http://<IP_ADDRESS>:8900/s/SSjjqbCPTJ5K3EY
Validation passed in case :

Install/update version

Update content when unstake liquid staking on Bifrost

vDOT

vMANTA

Re-check content when unstake liquid staking on Acala

Re-check content when unstake on some networks
Update content when unstake Bittensor


fancy new design! part one - huge! :hugs: (issue #91)

initial version of new design implementation based on @caseyyee + @HudsonPowell/@benjaminleonard's designs (see https://github.com/WebVRRocks/webvrrocks/issues/91#issuecomment-263904157)

heh, just FYI: I had made so many changes to styles/index.styl, that the diff doesn't render by default in the PR unless you click on it to open it.

merging so we can get back up to speed 🚤


Video is not shown on client side using nodejs app

Failed to load '' as a plugin, because the frame into which the plugin is loading is sandboxed.

INFO: Requested access to local media
erizo.js (line 175)
DEBUG: Object { video=true,  audio=true,  fake=undefined,  more...}
erizo.js (line 175)
ERROR: Failed to get access to local media. Error code was undefined.
erizo.js (line 175)
DEBUG: Event: access-denied

SyntaxError: JSON.parse: unexpected end of data at line 1 column 1 of the JSON data
...("Room already connected");a.state=1;c(JSON.parse(e),function(c){var e=0,d=[],f,...

Can you give more info please? Browser, version, etc.

Hi,
I am also getting the same issue on firefox 50.1.0 and chrome Version 55.0.2883.87 (64-bit)
Browser logs:------------------------------------------
INFO:  Requested access to local media  erizo.js:177:478
DEBUG:  Object { video: Object, audio: true, fake: undefined, screen: "", extensionId: undefined }  erizo.js:177:478
No Erizo Controller found  connection_test.js:32:5
INFO:  Requested access to local media  erizo.js:177:478
DEBUG:  Object { video: Object, audio: true, fake: undefined, screen: undefined, extensionId: undefined }  erizo.js:177:478
INFO:  User has granted access to local media.  erizo.js:177:478
DEBUG:  Event: access-accepted  erizo.js:177:478
ERROR:  Failed to get access to local media. Error code was undefined.  erizo.js:177:478
DEBUG:  Event: access-denied
Erijo Logs in terminal:------------------------------------------------------------
{ username: 'user', role: 'presenter', room: 'basicExampleRoom' }
POST /createToken/ - - ms - -
GET /connection_test.html 304 1.128 ms - -
GET /erizo.js 304 0.389 ms - -
GET /connection_test.js 304 1.053 ms - -
{ username: 'user', role: 'presenter' }
404 ErrorNo Erizo Controller found
404 ErrorNo Erizo Controller found
POST /createToken/ 401 11015.960 ms - 25
Licode logs:---------------------------------------------------------------------------
2017-01-06 11:49:25.882  - ERROR: CloudHandler - No erizoController is available.
2017-01-06 11:49:35.212  - ERROR: CloudHandler - No erizoController is available.
2017-01-06 11:49:36.891  - ERROR: TokensResource - message: createToken error, errorMgs: No Erizo Controller available
2017-01-06 11:49:46.223  - ERROR: TokensResource - message: createToken error, errorMgs: No Erizo Controller available
It looks like create token request is not responding and I just executed all the scripts successfully and launched http://localhost:3001
Is there any more configuration needed to test the videoconference demo in local env using licode ?
ty

I have solved the problem but enabling proper CORS from my application. It was not working in nodejs application where I used JADE as a template engine for view page. Using plain html and providing sandbox permission I have solved the problem

Hi @codebazz  i m also facing the same error i.e  Failed to get access to local media ,access denied
can u help me to get of this.

@codebazz i'm having the same issue.
https://discourse.lynckia.com/t/failed-to-get-access-to-local-media-error-code-was-undefined/769
can you define how you fixed it?


Support for server side pre-rendering

I've been working on an Angular 2 app with an ASP.NET Core backend that uses server side pre-rendering. Unfortunately I found out that using these pipes breaks the server side rendering.
This mostly seems to be because they use window.setTimeout and window.clearTimeout, but window isn't available during the server side rendering for obvious reasons. Is there something we can do here to make this play nice with server side pre-rendering? Perhaps checking if window is defined would be enough?

This makes sense. Can you please send a PR for that?
Also, please see #74

I started working on this, but I'm having a hard time trying it out. I've tried to npm link it, but then the server side pre-rendering fails entirely with the same error message that is mentioned in #68. Any thoughts on that?

How did you import the module?
Please see my last comment on #81

I've tried both:
import { MomentModule } from 'angular2-moment/module';

and:
import { MomentModule } from 'angular2-moment/module';

But I'm getting the same error in both cases?

Can you please check with the latest beta, 1.0.0-beta.3?

I merged my forks master with your master and then tried to npm link again, but I'm still getting the same error message.
I noticed that both the TimeAgoPip and CalendarPipe now use ngZone.runOutsideAngular(), but it looks like that is still being executed during server side pre-rendering so it doesn't fix this issue. I guess we'll have to check for the existence of window explicitly. Want to try that out locally first though.

I ended up just modifying the copy of this module inside the node_modules folder in order to verify if it works as expected.


Update contributing workflow

Renamed HelloWorldLog to HelloLog to match web framework naming convention.
Also thinned down the contributing steps a bit. I don't want potential contributors to lose interest while reading through Goal 1.
We can replace all of Goal 2 with a helper script.

LGTM!