Trying onrender.com instead of Heroku

Following Heroku discontinuing its free tier, I have been look at moving my app to another free alternative, such as onrender.com.
I'm using the same repository and setting a secret EARTHENGINE_TOKEN properly. Unfortunately I am still encountering authentication problems and I can't work out what I'm missing.
RefreshError: ('invalid_grant: Bad Request', {'error': 'invalid_grant', 'error_description': 'Bad Request'})

The app is hosted at https://spen-farm.onrender.com/. (It used to be spen-farm.herokuapp.com).
I am posting here as the procedure is almost identical to the Heroku set-up, and I'm hoping there's a quick solution. Please let me know if there's any other places to host geemap apps for free (I'm having similar auth issues with streamlit).
Thanks

I have not tried out onrender yet. See https://github.com/giswqs/geemap-heroku/issues/17#issuecomment-1182703454 if it helps.

Unfortunately no success trying out #17.
It seems that I'm having problems authenticating any new geemap app on streamlit, onrender, etc. My issue does not seem to be specific to onrender so it might be something to do with my token in particular. Is there a limit to how many apps I can have for one refresh token?

There is no limit to how many apps you can have, but GEE only allow a few concurrent connections, so you can't use too many apps simultaneously. But should be able to deploy them.

That's good to know about there being no limits to how many apps you can have, thanks.
Yes I can run my app locally with no issues.

Hi,
Managed to fix this - it turned out to be a problem related to the kernel defined in the Jupyter notebook. The ee authentication messages that were throwing me off were likely due to the ee package and not the earthengine-api. After updating the notebook to use the correct environment, it deployed in a similar way to Heroku.
As for those looking for an alternative to heroku for free geemap app hosting - onrender.com does seem to be worth considering.
Thanks


🔥 Remove .gem files and start ignoring them

We don't want to have a bunch of .gem files as it doesn't bring much
value and will end up with a bunch of them as new versions are released.

Thank you for this 🔥


Use .Release.Namespace instead of .Release.Name as a prefix for cluster-scoped objects

Right now cf-operator.fullname prefixes the chart name with the release name and not the namespace:
https://github.com/cloudfoundry-incubator/quarks-operator/blob/master/deploy/helm/quarks/templates/_helpers.tpl#L14-L25
This is used to create names for e.g. cluster roles and cluster rolebindings. The problem is that with helm 3 the release name is no longer unique (and it wasn't with helm 2 either if you had more than one tiller instance).
So you can have a cf-operator release in both ns1 and ns2. Both will try to create a cluster role called cf-operator-quarks-cluster (among others for job, secret, and statefulset), creating a collision.
If you prefix with the namespace, the role and rolebinding will be ns1-quarks-cluster and ns2-quarks-cluster, which can be removed independently when their corresponding release is removed from ns1 or ns2.
Given that the namespace-scoped objects don't include the release name in their object names, it isn't supported to install multiple releases of the same quarks chart into the same namespace anyways, so dropping the release name from the objects should not be an issue.
The kubecf cluster-scoped objects have the same problem, but I thought I would raise it here first.

Makes perfectly sense, and this I think got mostly unnoticed since we added multi-ns support for a single operator install

I don't think we have any explicit tests for installing multiple operators in a single cluster. The e2e tests on the flintstone Concourse could have catched this, but they are red.
This shouldn't create any problems when updating the operator, right?

This shouldn't create any problems when updating the operator, right?

I don't think so; during update the roles and rolebindings with the old names should get deleted, and the new ones should get created. But I've obviously not actually tested it...

If we want to allow multipe operators per namespace, we could use 'monitoredID' to prefix all cluster resources. We'd also have to prefix all the release namespace resources, right now I think only webhook is missing.
However, if we decide not to support multiple per  namespace, we can drop the prefixes and just prefix cluster resources with the Release.Namespace as suggested.
In any case you should be able to use Values.fullnameOverride to work around the helm chart issue.
It's not a straight forward fix, since the operator update test relies on the default name and we probably have to do it for all helm charts.

If we want to allow multipe operators per namespace

Does this make sense? In general helm charts don't really support installing the same chart multiple times into the same namespace because things like services and statefulset have fixed names. Namespace are already the mechanism to avoid name collisions, so why invent another mechanism to create essentially nested namespaces?


Move Forwarder to TrackReceiver

moved Forwarder to TrackReceiver
separated EncodingSelector from Forwarder
moved handling selectEncoding  media event from SimulcastTee to WebRTC Endpoint
copied Testing.Sink and Testing.Source from membrane_core and extended them

Two tests are not passing but let me fix then in the next PR


Nearly all services assume coreutils is present / systemd-confinement doesn't

Describe the bug
I just tried to enable confinement for a service, and it broke because it had a bare ln line in ExecStartPre. systemd-confinement only looks at the closure of the Exec lines and does not include the service's path.
This could be solved in two ways, either systemd-confinement also takes the service's Path into account, or services are more explicit about relying on coreutils. When I had a look in the repo, I found a grand total of two services that call ${pkgs.coreutils}/bin/ln rather than just ln, and this is probably also extended to more binaries. However, confinement.fullUnit specifically exists so the default does not pull in coreutils.
To Reproduce
Steps to reproduce the behavior:

Pick any service that relies on coreutils being in the path, I started with Grafana
Enable hardening for it:

systemd.services.grafana = {
  confinement.enable = true;
  serviceConfig.BindPaths = ["/var/lib/grafana"];
};

Activate and discover Grafana will no longer start:

grafana-pre-start[6753]: /nix/store/65y806k0bs348cadw040qzga6jcd433c-unit-script-grafana-pre-start/bin/grafana-pre-start: line 2: ln: command not found

Add coreutils:

systemd.services.grafana = {
  confinement = {
    enable = true;
    packages = [ pkgs.coreutils ];
  };
  serviceConfig.BindPaths = ["/var/lib/grafana"];
};

See Grafana start fine

Expected behavior
Service starts without needing to add coreutils.
Additional context
I realise that coreutils has been a part of the default path for services for quite a long time and services are written with this in mind. I realise that actually changing this list is unlikely to happen, especially in the short term. I would however like to ask whether services should be written with this list in mind, or whether they should be explicit in their dependencies.
https://github.com/NixOS/nixpkgs/blob/df18d77f1ea455909d0799edfa2e425aa04faf14/nixos/modules/system/boot/systemd.nix#L255-L262
I guess my question boils down to this: Should users wanting to enable confinement themselves be expected to look at the unit file and add dependencies from the above list manually, risking breakage if a service is updated to use a listed dependency, should they when in doubt just enable fullUnit (contradicting the docs) or should services directly reference packages from this list so they'll be included in the Exec closures?
Notify maintainers
@aszlig

systemd.services.grafana = {
  confinement.enable = true;
  serviceConfig.BindPaths = ["/var/lib/grafana"];
};

Btw. you can also use StateDirectory:
systemd.services.grafana = {
  confinement.enable = true;
  serviceConfig.StateDirectory = "grafana";
};

I guess my question boils down to this: Should users wanting to enable confinement themselves be expected to look at the unit file and add dependencies from the above list manually, risking breakage if a service is updated to use a listed dependency, should they when in doubt just enable fullUnit (contradicting the docs) or should services directly reference packages from this list so they'll be included in the Exec closures?

This is something I pointed out in the initial pull request, which is why the documentation has the following note:

The store paths listed in path are not included in the closure as well as paths from other options except those listed above.

So yes, this is deliberate and the services either need to directly reference ${pkgs.coreutils} or have coreutils in confinement.packages.
In theory, we could also add path to confinement.packages by default, but it would only add to the options needed in order to have the most strict level of confinement. For example right now if you want it to be a strict as possible you need to set mode = "chroot-only" and binSh = null. Including path by default would add another mkForce on confinement.packages.
Of course, this is how I usually approach sandboxing services, which not only involves confinement but also other things such as SystemCallFilter, PrivateNetwork, etc... and I go from the most restrictive configuration to "just enough things allowed so the application works". I also tend to sometimes go through a few hoops to make sure the application in question uses the full store path rather than rely on PATH or ugly wrappers, but of course YMMV.
If people commonly expect that path is included in confinement.packages we could change the default, but given that it will be painful in terms of backwards-compatibility (eg. existing services using the module silently get new store paths in the chroot) I'd rather see very convincing arguments why this would be a good default.

If people commonly expect that path is included in confinement.packages we could change the default, but given that it will be painful in terms of backwards-compatibility (eg. existing services using the module silently get new store paths in the chroot) I'd rather see very convincing arguments why this would be a good default.

I agree. I'd expect the risk to be low, seeing as that list of default paths hasn't really changed in the past 9 years, but it's a valid point. I would really prefer it if services were explicit about their dependencies. That's… rather impactful though, which is why I wanted to create this issue.
I'm not entirely sure to what extent those hardcoded extra paths are actually necessary, except that now services of course depend on it and it's going to be difficult to change. I do think it would be a good idea if services listed their dependencies explicitly. Perhaps this should be an RFC instead? Not entirely up-to-date on the process any more...


diff-gaussian-rasterization error

Hello,
Thank you very much for sharing such excellent work. However, I find it very difficult to set up the environment. My CUDA version is 11.6, and I followed the instructions in the README for the rest of the setup. However, I encounter errors when installing the submodules using pip install .. The error message is as follows:
Processing /disk2/wh/code/SplaTAM_wh/diff-gaussian-rasterization-w-depth
Preparing metadata (setup.py) ... done
Building wheels for collected packages: diff-gaussian-rasterization
Building wheel for diff-gaussian-rasterization (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [70 lines of output]
/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/torch/cuda/init.py:83: UserWarning: CUDA initialization: Unexpected error from cudaGetDeviceCount(). Did you run some cuda functions before calling NumCudaDevices() that might have already set an error? Error 804: forward compatibility was attempted on non supported HW (Triggered internally at  /opt/conda/conda-bld/pytorch_1659484803030/work/c10/cuda/CUDAFunctions.cpp:109.)
return torch._C._cuda_getDeviceCount() > 0
No CUDA runtime is found, using CUDA_HOME='/disk2/wh/anaconda3/envs/splatam'
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-310
creating build/lib.linux-x86_64-cpython-310/diff_gaussian_rasterization
copying diff_gaussian_rasterization/init.py -> build/lib.linux-x86_64-cpython-310/diff_gaussian_rasterization
running build_ext
/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/torch/utils/cpp_extension.py:820: UserWarning: There are no /usr/bin/g++-10 version bounds defined for CUDA version 11.6
warnings.warn(f'There are no {compiler_name} version bounds defined for CUDA version {cuda_str_version}')
building 'diff_gaussian_rasterization._C' extension
creating /disk2/wh/code/SplaTAM_wh/diff-gaussian-rasterization-w-depth/build/temp.linux-x86_64-cpython-310
creating /disk2/wh/code/SplaTAM_wh/diff-gaussian-rasterization-w-depth/build/temp.linux-x86_64-cpython-310/cuda_rasterizer
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "/disk2/wh/code/SplaTAM_wh/diff-gaussian-rasterization-w-depth/setup.py", line 17, in
setup(
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/init.py", line 103, in setup
return distutils.core.setup(**attrs)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 185, in setup
return run_commands(dist)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
dist.run_commands()
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
self.run_command(cmd)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/dist.py", line 989, in run_command
super().run_command(command)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
cmd_obj.run()
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/wheel/bdist_wheel.py", line 368, in run
self.run_command("build")
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/dist.py", line 989, in run_command
super().run_command(command)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
cmd_obj.run()
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/command/build.py", line 131, in run
self.run_command(cmd_name)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
self.distribution.run_command(command)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/dist.py", line 989, in run_command
super().run_command(command)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
cmd_obj.run()
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 88, in run
_build_ext.run(self)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 345, in run
self.build_extensions()
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 765, in build_extensions
build_ext.build_extensions(self)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 467, in build_extensions
self._build_extensions_serial()
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 493, in _build_extensions_serial
self.build_extension(ext)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 249, in build_extension
_build_ext.build_extension(self, ext)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 548, in build_extension
objects = self.compiler.compile(
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 581, in unix_wrap_ninja_compile
cuda_post_cflags = unix_cuda_flags(cuda_post_cflags)
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 480, in unix_cuda_flags
cflags + _get_cuda_arch_flags(cflags))
File "/disk2/wh/anaconda3/envs/splatam/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 1694, in _get_cuda_arch_flags
arch_list[-1] += '+PTX'
IndexError: list index out of range
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for diff-gaussian-rasterization
Running setup.py clean for diff-gaussian-rasterization
Failed to build diff-gaussian-rasterization
ERROR: Could not build wheels for diff-gaussian-rasterization, which is required to install pyproject.toml-based projects

I think this is related to issue which has been solved.

thank you！ @JzHuai0108


Add Chef-server to Chef-automate UI

:nut_and_bolt: Description: What code changed, and why?
This will add chef-server on automate UI, after the deployment is completed.

We have added new module add_chef_server_to_a2_ui which will create an admin token and then will add chef-server to automate UI
:chains: Related Resources
:+1: Definition of Done
:athletic_shoe: How to Build and Test the Change
Build package automate-ha-deployment
build components/automate-backend-deployment
And use this package for deployment while using Chef-automate HA Deployment
:white_check_mark: Checklist
All PRs must tick these:

[x] I have read the CONTRIBUTING document.
[x] All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

[ ] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
[ ] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
[ ] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
[ ] Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
[ ] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

[x] Tests added/updated? (all new code needs new tests)
[x] Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.
:camera: Screenshots, if applicable

Is there a particular reason that each FE is getting added? They all point at the same database so are essentially we're just adding the same Chef Infra Server multiple times with different names. It would seem to make sense that you would only need to add a single entry for the FQDN or better yet if we knew the FQDN for the Chef Infra FE Loadbalancer. That way there is no additional work needed if you add or remove FE nodes down the road.


twister: cannot build samples/tests on Windows

Describe the bug
Twister cannot be used to run tests with --build-only flag on Windows OS.
To Reproduce
Steps to reproduce the behavior:

Clone Zephyr repository on Windows OS according to this tutorial:
https://docs.zephyrproject.org/latest/getting_started/index.html#
Run Twister to build hello_world sample by this command:

python scripts/twister -p nrf52840dk_nrf52840 -T samples/hello_world --ninja --build-only

Expected behavior
Sample should be built with no error.
Impact
Twister cannot be used on Windows for build any samples or tests
Logs and console output
>python scripts/twister -p nrf52840dk_nrf52840 -T samples/hello_world --ninja --build-only
ZEPHYR_BASE unset, using "C:\zephyr"
Traceback (most recent call last):
  File "C:\zephyr\scripts\twister", line 209, in <module>
    from twisterlib import HardwareMap, TestSuite, SizeCalculator, CoverageTool, ExecutionCounter
  File "C:\zephyr\scripts/pylib/twister\twisterlib.py", line 28, in <module>
    import pty
  File "C:\Python39\lib\pty.py", line 12, in <module>
    import tty
  File "C:\Python39\lib\tty.py", line 5, in <module>
    from termios import *
ModuleNotFoundError: No module named 'termios'

Environment:

OS: Windows 10
Toolchain Zephyr SDK
Commit SHA: e8f09b471e907d05772b8fc42e9e14a28101c0b8

Additional information
I already have proposition for fix this bug and I will create PR soon

@gopiotr  can you please send a PR?


check sample method vocab against sample preparation vocab

HI Vance and David
Please check the vocab assigned to the method field under Sample. It does not give us options that we expect to provide information on how the sample was collected (method). Instead, it appears to be information that will come under Observation about what the lab has done to the sample. We were expecting to be able to assign the type of method used to collect the sample (hand sample, jackhammer, sledgehammer,  scrapings, core section, grab sample, dredge, etc), but instead, the list is of lab processes (chelate, aggregate, dessicate, filter etc).

duplicate #216
closing and pasting comment there


[BUG] Memory leak, unable to remove object

window.web.form_view = new FormView({ el: $("#form"), });
window.web.form_view.remove()
window.web.form_view = new FormView({ el: $("#form"), });
It keeps all events of first instance & never remove it from memory.
Big memory leakage issue. Do not advice to move on IRC, instead fix it, let us know what exact todo, I will write code to manage this issue.

@tejastank I think this is expected behaviour:
https://github.com/jashkenas/backbone/blob/master/backbone.js#L1160-1166
The remove method of the view just removes the view element/DOM node from the DOM and stops listening to the events.

I had tried same things.
Even many different way, also with delete, but old events & memory object exists even we do .remove or other methods.

Try the mailing list or the IRC channel for questions. Github issues are for maintaining the framework only.


Deserializing unknown/new enum members

Taking a look at the field de-serializers in the generated models, (Example at https://github.com/microsoft/kiota-samples/blob/main/msgraph-mail/dotnet/Models/ItemBody.cs#L34) Enums are handled by calling the GetEnumValue function.
In the event the API evolves and adds a new member to the Enum model, the new member will fail to match, and the function will return a default value (null in C#). However, this information of the Enum will be lost as the match will have failed. To alleviate this, we should add the enum member to the additionalData bag as it is unknown and will still be accessible to a user in the event of a failed match.
This can be done by

Updating the generated model code to have something like this. Leads to slightly more generated code

{"contentType", n => { ContentType = n.GetEnumValue<BodyType>(); if(ContentType == null) AdditionalData.Add("contentType", n.GetStringValue()); } }

Possibly using the serialization abstractions to give a signal in the case of a failed match and set the value possibly by throw an exception to be handled and add to the additionalData.
Possibly using the serialization abstractions to use reflection to check if the property being updated is an Enum and has been successfully set.

Leaning towards option 1 as the other options will most likely lead to performance impacts in the hot paths of other generated properties.
Thoughts? cc @baywet

Hey @andrueastman,
Thanks for bringing this up. I'd like to take a step back here and understand the need before we think of solutions.
IMHO having the ability to access unrecognized values for enums is only valuable for logging/tracing scenarios.
For every other scenario, having a new enum value show up (because the service evolves) will require code changes to take advantage of it. And since people are already changing the code and a deployment, they can refresh their client (either through refreshing the self-serve generation or through pulling the latest version of the package).
Because older generation SDKs would not get refreshed weekly, it made sense to have this ability to cover the interval between a new value showing up on the API and that value being available in the SDK. But even outside of Kiota based SDKs, we've been consistently matching service refreshes on a weekly base for over 2 years now which highly decreases the value of "such a feature" IMHO.
Am I missing anything here?

But even outside of Kiota based SDKs, we've been consistently matching service refreshes on a weekly base for over 2 years now which highly decreases the value of "such a feature"

I definitely hear you on this point.
From a graph SDK view, I see is in these two scenarios, and being able to obtain the values creates a way out.

A service may return values that are not publicly described/documented in the metadata as they are only available (and intentionally hidden) as they are available for only a subset of special users/tenants.
A user does not wish to update the version due to other unrelated changes needed with upgrading the version.

I think that if an application wants to see the new value they need to update their client.

@andrueastman Do you have additional points? or are you ok with closing this issue?

Sorry I missed this. This one is good to close.


Migrate to a Flexible Image API

Search before asking

[X] I have searched the Autodistill issues and found no similar feature requests.

Description
Autodistill currently accepts file names in predict() calls. We want to enable users to provide:

File names
NumPy arrays from OpenCV
PIL Images
Base64 images

Inference has logic for this, but we may want to move it upstream into supervision, which will take time. This issue is a place to track that such a change is being planned.
We will likely implement a new load_file function in autodistill that base models can use to load a file from different means.
To build this change, all base models will need to be updated with the new API.
Use case
No response
Additional
No response
Are you willing to submit a PR?

[X] Yes I'd like to help by submitting a PR!

This is now complete as of autodistill==0.1.20.


Update README to add LoreSoft.Blazor.Controls

Typeahead, DateTimePicker, and ToggleSwitch

Thanks!
Released in  https://github.com/AdrienTorris/awesome-blazor/releases/tag/v2020.W38.


Node14: SyntaxError: Unexpected token '??='

Env: Local
Need Update Node.js to version 16+
https://github.com/gluon-framework/gluon/blob/main/src/api/v8Cache.js#L25
Or update code to
    urls ??= await getScriptUrls(includePreload);
    // urls = urls ?? await getScriptUrls(includePreload);

Gluon does/will not support Node <16, as stated in docs: https://gluonjs.org/docs/guide/quick-start/#requirements


[Bug]: Embedded browser not usable

Is there an existing issue for the same bug?

[X] I have checked the troubleshooting document at https://docs.all-hands.dev/modules/usage/troubleshooting
[X] I have checked the existing issues.

Describe the bug

The address cannot be edited.
Current OpenHands version
newest.

Installation and Configuration
docker from wsl

Model and Agent
No response
Operating System
No response
Reproduction Steps
No response
Logs, Errors, Screenshots, and Additional Context
No response

Hello there! I think currently that's as designed. They don't want it to be editable, it's just for OpenHands to use and it is in an experimental stage.
For example you can give it this prompt:
Go to the OpenHands github page at https://github.com/All-Hands-AI/OpenHands and tell me how many stars the github repo currently has
It will use the browser to perform the task.

Closing as designed.


iprep: Duplicate reputation check

Validate that duplicate reputation entries are handled properly and don't cause a memory leak.
Issue: 5748
Suricata PR: #8773

Tests pass only if you do not have the leak sanitizer, right Jeff ?

Merged in #1339, thanks!


Introduce Spring Boot Auto Configuration

Changes

introduces basic autoconfig for XsuaaServiceConfiguration
introduces autoconfig for JwtDecoder
XsuaaJwtDecoderBuilder can be configured with default validators
https://github.com/SAP/cloud-security-xsuaa-integration/blob/a31768d497d65de0551d35d0491ef1549b6f2134/spring-xsuaa/src/main/java/com/sap/cloud/security/xsuaa/token/authentication/XsuaaJwtDecoderBuilder.java#L81
uses default validators from spring-security Oauth2 https://github.com/SAP/cloud-security-xsuaa-integration/blob/a31768d497d65de0551d35d0491ef1549b6f2134/spring-xsuaa/src/main/java/com/sap/cloud/security/xsuaa/token/authentication/XsuaaJwtDecoderBuilder.java#L27

Open Todos / follow ups

[x] update documentation
[x] update integration tests and samples
[x] apply code formatting rules
[ ] enhance changelog and increase version
[x] some further tests with existing sample applications
[x] issue #86

@mwdb as requested. I've changes the target branch to version1.5
can you please review?


Update reacts.js

Another pro sponsor to get auto lunaping emote reactions on the message.

Closed because other changes made this PR behind master. These changes incorporated in that commit.


Issue importing Foundation 6 into Project

Getting this error in the browser.
When first trying to setup meteor with foundation6.
My project is located here:
https://github.com/dmc2015/meteoric-portfolio
Foundation 6 installation steps:
https://atmospherejs.com/zurb/foundation-sites
meteor add zurb:foundation-sites

Created main.scss in projectroot/client/scss/
Did not work.
Errors prevented startup:

While processing files with fourseven:scss (for target web.browser):
/client/scss/main.scss: Scss compiler error: File to import: {zurb:foundaiton-sites}/scss/foundation not found in file: /Users/don/dev/js/meteor-projects/portfolio/{}/client/scss/main.scss

Your application has errors. Waiting for file change.

Moved main.scss to projectroot/client/
Still did not work.
Errors prevented startup:

While processing files with fourseven:scss (for target web.browser):
/client/main.scss: Scss compiler error: File to import: {zurb:foundaiton-sites}/scss/foundation not found in file: /Users/don/dev/js/meteor-projects/portfolio/{}/client/main.scss

Your application has errors. Waiting for file change.

In main.scss
@import '{zurb:foundaiton-sites}/scss/foundation';

@include foundaiton-everything;

I needed to add '_' in front of the name.
Documentation could be updated here to put the right file name in, '_main.scss'.
https://atmospherejs.com/zurb/foundation-sites


s2n_recv: clear *more when connection is closed.

Discussed in Issue #165 .

Merged, thanks for the fixes!


Missing exports types in v5

I noticed that you are now only exporting the EChartsOptions and not the subtypes like BarSeriesOption, ChartDataset, etc. This will result in losing all of the typings in our code base. Could you please export those types as well?

The latest version of ECharts has exported the options of series and components.


Begin implementing EC balancing parallelization support.

What problem are we solving?
Make EC balancing logic topology-aware: https://github.com/seaweedfs/seaweedfs/discussions/6179 .
How are we solving the problem?
Begin the implementation of parallel EC re-balancing operations within shell.EcBalance().
This impacts both ec.encode and ec.balance.
How is the PR tested?
No algorithmic changes, other than running EC sub-tasks in parallel. Following changes will likely require at least unit testing.
Checks

[x] I have added unit tests if possible.
[x] I will add related wiki document changes and link to this PR after merging.

how to prevent one volume server running multiple EC encoding processes?

Right now there's no parallelization in place for the EC encoding phase - just the re-balancing happening after.
Was thinking about running encodings in parallel though :cry: Is this a problem? I assumed volume servers could handle multiple EC encoding requests without issues.

Later need to add a parallel limit on each volume server for the ec encoding/decoding.


Adding new folder for pdfs, plus pdfs with data necessary for stat analysis

These PDF files are from the functional specification documentation and contain the data necessary to complete our statistical analysis.
Of note:

The wolf reports retain their original names from download
"Deer Health - Disease" is a screenshot of a graph saved as a pdf and details the number of deer w/ chronic wasting disease. While there is a pdf deer report available at the county level, it does not appear to contain numerical CWD information.
"Deer seen per hunted hour" is a screenshot of a graph saved as a pdf. While there is a pdf deer report available at the county level, it does not appear to contain numerical deer seen information.
"Harvest Trends" is a screenshot of a graph saved as a pdf. While there is a pdf deer report available at the county level, it only contains information from the past 3 years.
"Post Deer Hunt Population Estimates" is a screenshot of a graph saved as a pdf. The county level pdf reports do contain this information, but it's displayed as a graph. Given it would have to be read and aggregated, I assumed it would be easier to read it only once.

I will be making table mockups later today detailing what information Logan and I need for the stats analysis.

Added csvs with data required to answer our proposed statistical questions and a document detailing where the information came from. The data is real and was manually entered

Added new csv file for proportion stats test and updated creation documentation accordingly.


Unregister devices

Whenever the user uninstall the app, is the plugin unregistering the device by default? Or would that be something we have to handle manually?

That cannot be handled by the app because the app has no way of knowing was uninstalled, but if reinstalled will definitely get a new token.

But if app uninstalled you won't get any notifications if that is your concern.

Thanks. So I guess I don't have to worry about that part then, assuming FCM will take care of cleaning up unused tokens on their end

Right on server side is were you will do this cleanup


az CLI resolves partial argument names  e.g. --resource is getting resolved to --resource-group

This is autogenerated. Please review and update as needed.
Describe the bug
CLI should not resolves partial argument to other arguments, it should be absolute. Could cause confusion for users , as there could be multiple argument names starting with the same root name (e.g. resource-group, resource-type etc). It could also break automation due to side effects
Command Name
``
Errors:

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
``

Expected Behavior
Environment Summary
Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-debian-buster-sid, Ubuntu 18.04.6 LTS
Python 3.7.9
Installer: PIP

azure-cli 2.36.0

Extensions:
ml Unknown
machinelearningservices Unknown

Dependencies:
msal 1.17.0
azure-mgmt-resource 20.0.0

Additional Context

@zhoxing for awareness

Hi, could you share debug log or steps to reproduce?


Cannot import name 'ELECTRICAL_VOLT_AMPERE' from 'homeassistant.const'

Updated to latest HA 2021.8.0 and Sunpower integration didn't start up
`Logger: homeassistant.setup
Source: setup.py:173
First occurred: 9:25:34 AM (1 occurrences)
Last logged: 9:25:34 AM
Setup failed for sunpower: Unable to import component: cannot import name 'ELECTRICAL_VOLT_AMPERE' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)`

Looks like the naming changed in the latest release. Here is the commit that broke it, https://github.com/home-assistant/core/commit/074d762664976d3414b8a33535e9b850d80a42fa

Testing some locally
"POWER_VOLT_AMPERE" changed to "POWER_VOLT_AMPERE"
"VOLT" changed to "ELECTRIC_POTENTIAL_VOLT"

Tested locally and worked, created a Pull request, https://github.com/krbaker/hass-sunpower/pull/7


Optimize function calls

__temp1 = size()
__longtemp2 = __temp1

should be
__longtemp2 = size()

It's like a constant propagation but it's not a constant.

https://github.com/dplassgit/d2lang/blob/trunk/src/com/plasstech/lang/d2/optimize/TempPropagationOptimizer.java would be the place


Strange operationId name

I ran into a situation where I ended up with the following operationId which seems a little odd.
"operationId":"ApiV{versionHelloWorldGet"
Now I've traced it back to the FriendlyId function but have yet to discover the actual cause of this odd behaviour.
I'm actively investigating this, and it might be caused by something else in my current project.

Duplicate of #244

IMHO this should be reopened and investigated for resolution. I do not believe this behavior is intended; therefore, it's a bug. The issue isn't specifically related to ASP.NET API Versioning, so it's not a duplicate either. There are other cases where this can happen.
The bug exists at: ApiDescriptionExtensions.cs (Line 43). This code assumes that any URL segment that contains a route parameter will have the form of {param name} and extracts the parameter name from within (ex: api/helloworld/{id});  however, that is incorrect. It's perfectly valid to have route parameters that include other literal characters in the URL segment. Given the assumption on the format, the code then presumes it can just trim off the leading { and trailing }, which would theoretically leave only the route parameter name.
Consider the path api/v{api-version}/helloworld/{id}. This is what a route might look like using API versioning via a URL segment (which isn't the only way). The current code processes the second segment such that:

api -> trim { and } -> api
v{api-version} -> trim { and } -> v{api-version
helloworld -> trim { and } -> helloworld
{id} -> trim { and } -> id
api + v{api-version + helloworld + By + id + GET -> to titlecase -> ApiV{versionHelloWorldGet

My suggestion would be to either not mangle the URL at all or come up with an alternate method that considers all the variations of route parameters and any associated route constraints. For example, consider: api/employees/{ssn:regex(^\\d{{3}}-\\d{{2}}-\\d{{4}}$)}. This would become something like ApiEmployeesBySsn:regex(^\d{{3}}-\d{{2}}-\d{{4}}$), which is hardly a friendly identifier IMO.

@commonsensesoftware coming up with a "friendly" identifier that works in all cases is near impossible. But, you've pointed out some cases where improvements can be made.
I would also point out that you can use an IOperationFilter (see readme) to implement your own strategy for generating operationIds. Alternatively, you can decorate actions with SwaggerOperationAttribute to explicitly set the operationId for any given one.

@domaindrivendev I agree - coming up with a universal friendly name isn't so easy.
Why not just use ActionDescriptor.DisplayName? It's not without flaws, but it does produce a friendly name. The format can be updated via extensions as well. It also seems that the ActionDescriptor passed around is usually a ControllerActionDescriptor, which allows building a friendly name from the type and method name - similar to the default behavior, but with more control. Some other alternatives could include using various combinations of ActionDescriptor.GroupName, ActionDescriptor.ControllerName, ActionDescriptor.ActionName, and/or ActionDescriptor.HttpMethod.
In the spirit of keeping things simple, perhaps ActionDescriptor.DisplayName or a close variation by default. Then you can use an albeit new XML Comment to override the friendly name. For example:
/// <summary>
/// Gets a single resource.
/// </summary>
/// <param name="id">The requested resource identifier.</param>
/// <returns>The requested resource.</returns>
/// <friendlyName>GetResourceById</friendlyName>
/// <response code="200">The resource was successfully retrieved.</response>
/// <response code="404">The resource does not exist.</response>
[HttpGet( "{id:int}", Name = "GetResourceById" )]
[ProducesResponseType( typeof( Resource ), 200 )]
[ProducesResponseType( 404 )]
public IActionResult Get( int id ) => Ok();

Pardon my ignorance, but I don't know whether the friendly names need to be unique and, if so, whether it's unique by API version or for everything. If the name must span everything, then mixing in the GroupName somehow should provide disambiguation.
There are many ways this problem could be solved or improved. May you find a few of these ideas useful or spark additional thoughts.

This functionality has gone through many iterations to try get a systematic generation of a "friendly id" correct and looks like there's still many issues. At this point, I'm tempted to go back to the original approach which just used the action name in the method signature. That puts the onus on developers to come up with meaningful and unique names. I understand that won't work for everyone, but folks can always override that strategy with their own implementation. It's just too trick for SB to come up with something that works for all cases.

@domaindrivendev I completely agree.  Personally, I think the simplest way to publish the operation name in one's spec is to simply name the operation the way one wants it published.
So, instead of a lazily naming a method Get, we should name it GetThingyById.  If we want to maintain an internal name vs an external operation name, then it make sense to use the SwaggerOperation.
If people are not happy with exposing an operationId at all, then there could be a c.DescribeOperationId(false) setting to control that.  BUT, since there is an available workaround to set the friendly name to blank, then I don't think a new setting is necessary.

@commonsensesoftware, @jboarman - see the above PR. It reverts to using the action name OR the route name. So, developers can choose to be more explicit with their method names OR they can provide an explicit OperationId through the HttpMethodAttribute:
[HttpGet]
public IActionResult GetProducts()
...

[HttpGet(Name = "GetProducts"]
public IActionResult Get()
...

// Both of the above will generate an operationId = "GetProducts"

Merged - will be generally available with the 4.0.0 release (coming soon). In the meantime you can try it out with the latest preview package on myget.org:
https://www.myget.org/feed/domaindrivendev/package/nuget/Swashbuckle.AspNetCore


restart browser with each describe

now we have the restart browser with each test , it costs so much times.
// If true, protractor will restart the browser between each test.
  // CAUTION: This will cause your tests to slow down drastically.
  restartBrowserBetweenTests: false,

can we restart browser with each describe or with each file
#1435

+1 please add this!

did you find any solution to the above issue? @shaoping

@nishakchaudhari   did not have useful solution for this， i  execute the describe with more config files

+1

+1 after each suite makes sense. This would assist our CI with no end

:+1: for each suite fresh start

+1

Have we achieved this?

I could make it work with Jasmine 2 framework. I emit an event when a describe finishes. Will make a pull request in the weekend

please achieve this , as the test increase biger, it's a big problem

+1, this would be quite nice.

+1
This would make sense because the related tests would be completed at a go before restarting the browser.

@angular why is this in the icebox if this is a really important feature for not having slow tests?

@ilanbiala Please feel free to submit a PR if it is something that you really need.

@NickTomlin do you disagree?

@ilanbiala I personally don't use milestones as a way of tracking features, so I don't have strong opinions on this being in the icebox or not. I do feel that there's no sense in moving it out unless someone wants to champion the feature.

So much noise, when the solution is so simple.  The original fix for #1435 should have made this general from the start.


Allow models in config

Where are the tests? Have you added tests? Have you updated the tests? Read the
comment above and the documentation referenced in it first. Write tests!
Seriously, read :help neural-dev and write tests.

Would you like to finish this one and bright it out of draft? It just needs some defaults configured, some tests, and documentation for the options.

I've implemented this now. See :help neural and the options for each source.


.gituprevision has no newline at EOF

Unless other tooling is incompatible with a newline at EOF I think it's beneficial to have it, in case users do e.g. cat .gituprevision.
Currently looks like:
00000000  73 74 61 62 6c 65 2f 31  32 3a 36 61 39 37 61 32  |stable/12:6a97a2|
00000010  33 37 61                                          |37a|

Base system newvers.sh parses .gituprevision with something like awk -F: '{print $2}' and works fine with the newline.

Done!


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/33391

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/33770

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/33837


fix: handle opensearch write_documents error handling

Fix error handling in opensearch write_documents
It seems only to be failing on haystack 2.0 🤔
Error:
packages/haystack_integrations/document_stores/opensearch/document_store.py\", line 171, in write_documents\n    error_type = e[\"create\"][\"error\"][\"type\"]\nKeyError: 'create'",

 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.

Hi @paualarco thanks for the contribution.
I'm looking into this right now,  a suggestion: always try to add a reproducible example. It helps the reviewers get into context quickly.

@paualarco I suspect this was already been fixed by this https://github.com/deepset-ai/haystack-core-integrations/issues/547 - we just need to make a new release
but still, can you provide me with a snippet of code that replicates the error you are having?

new release: https://pypi.org/project/opensearch-haystack/0.3.0/

@davidsbatista yes, apologies for not providing a snippet. This happened when trying to insert a string field in opensearch that was already indexed as an integer.
We reverted the haystack version to see the actual error stacktrace and found out.
I guess then we could close this issue?

thanks for the feedback @paualarco just confirm me that's everything is solved from your side with the new release and I will close it


Hyperlinks are not rendered nor the control going into onHyperlink.

Text containing hyperlinks is not rendered.

I just pushed a new release to npm containing the fix from issue #60. If that isn't your issue please provide a sample file demonstrating the issue.

It is still not fixed. Try rendering the attached file.
word pad pic link.zip

There was a bug in the latest version which prevented your sample from running at all (due to infinite recursion). I have published a bugfix for that. Afterwards I get the following result (left libreoffice, right our sample page):

This looks correct to me (apart from the table, which we don't support).

This is now fixed. Appreciate the efforts :+1:


SSLV3_Alert_Handshake_Failure

When attempting to run the check, I get the following error.
I believe we disabled SSLv3 after the following vulnerability was discovered: https://support.citrix.com/article/CTX200238
2020-01-14 11:52:19,659 WARNING Retrying (Retry(total=0, connect=None, read=None
, redirect=0, status=None)) after connection broken by 'SSLError(SSLError(1, '[S
SL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:1108)')
)': /vpn/../vpns/
2020-01-14 11:52:19,674 ERROR [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert h
andshake failure (_ssl.c:1108)

Thanks for the issue @BBurkhead!
An SSL handshake failure is indicative of an error on the server you're connecting to or, more likely, your local system.  Usually the culprit is something like a missing libssl installation.
If you can tell me about your local setup then I can try to help further, or if you can share the name of the host you are testing against then I could run against it and see if I get the same error.

Thank you for reaching out to check on my issue. I thought the same thing so I tried it on two different systems and received the same error. So now I believe it to be a server issue. To test further, I ran the script against virtuallab.pace.edu (mentioned in a previous issue) and it told me that virtuallab.pace.edu does not appear to be vulnerable. This reinforced my hunch that it was the server, so I ran “CVE-2019-19781.exe –log-level=debug” and received the following:
c:\Python\Scripts>cve-2019-19781 --log-level=debug connect.bankfirstamerican.com
2020-01-14 15:21:23,990 DEBUG Disabling insecure request warnings.
2020-01-14 15:21:23,990 DEBUG Disabling URL normalization.
2020-01-14 15:21:23,990 DEBUG Creating connection pool, retries=2, timeout=10s
2020-01-14 15:21:23,990 DEBUG Connecting to https://connect.bankfirstamerican.com/vpn/../vpns/
2020-01-14 15:21:23,990 DEBUG Converted retries value: 2 -> Retry(total=2, conne
ct=None, read=None, redirect=0, status=None)
2020-01-14 15:21:23,990 DEBUG Starting new HTTPS connection (1): connect.bankfirstamerican.com/:4
43
2020-01-14 15:21:24,052 DEBUG Incremented Retry for (url='/vpn/../vpns/'): Retry
(total=1, connect=None, read=None, redirect=0, status=None)
2020-01-14 15:21:24,052 WARNING Retrying (Retry(total=1, connect=None, read=None
, redirect=0, status=None)) after connection broken by 'ProtocolError('Connectio
n aborted.', ConnectionResetError(10054, 'An existing connection was forcibly cl
osed by the remote host', None, 10054, None))': /vpn/../vpns/
2020-01-14 15:21:24,052 DEBUG Starting new HTTPS connection (2): connect.bankfirstamerican.com/:4
43
2020-01-14 15:21:24,084 DEBUG Incremented Retry for (url='/vpn/../vpns/'): Retry
(total=0, connect=None, read=None, redirect=0, status=None)
2020-01-14 15:21:24,099 WARNING Retrying (Retry(total=0, connect=None, read=None
, redirect=0, status=None)) after connection broken by 'ProtocolError('Connectio
n aborted.', ConnectionResetError(10054, 'An existing connection was forcibly cl
osed by the remote host', None, 10054, None))': /vpn/../vpns/
2020-01-14 15:21:24,099 DEBUG Starting new HTTPS connection (3): connect.bankfirstamerican.com/:4
43
2020-01-14 15:21:24,115 ERROR ('Connection aborted.', ConnectionResetError(10054
, 'An existing connection was forcibly closed by the remote host', None, 10054,
None))
I wasn’t sure if this had anything to do with us implementing the workaround by Citrix (https://support.citrix.com/article/CTX267679), so I disabled that, reran the exe and got the same thing.
A little more info, I just went out to Python’s website, downloaded the Python3.8.1 exe, installed all features except documentation and py launcher, and installed the advanced features except the download debug binaries.
I also installed the library with pip
py -m pip install https://github.com/cisagov/check-cve-2019-19781/releases/download/v1.0.0/cve_2019_19781-1.0.0-py3-none-any.whl
I reinstalled with PIP just now and tried running the script again but still get the same error.


Support for defaultProps will be removed from function components in a future major release.

Feedback summary
Using React 18 I started to notice these warning messages for default props.
Warning: FormGroup: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
The console gets crowded with many of these messages, making it hard to check actual errors or any other important debug messages.
Improvements
Migrating default props to normal JS parameters.
CC: @adamstankiewicz

We'll want to move away from using propTypes as well https://react.dev/blog/2024/04/25/react-19-upgrade-guide#removed-proptypes-and-defaultprops

Thanks for flagging this, @ochavarria2u.
One important caveat we'll need to consider is how the Paragon docs site relies on propTypes and defaultProps to generate the props API sections for components (e.g., props API for Alert) as well.


don't raise an exception in NullCache.has

NullCache is supposed to be a drop-in debugging replacement for other caches, but currently its has function crashes the application.

Makes sense. Could you rebase this against the latest maintenance branch, add a changelog entry and perhaps a test? Thanks!


fix: contact's email field error message

Codecov Report

Merging #484 (60f707e) into main (fb134b7) will decrease coverage by 9.49%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #484      +/-   ##
==========================================
- Coverage   46.95%   37.46%   -9.50%
==========================================
  Files         233      151      -82
  Lines       11673     2389    -9284
  Branches      608      608
==========================================
- Hits         5481      895    -4586
+ Misses       5233     1319    -3914
+ Partials      959      175     -784

Impacted Files
Coverage Δ

...b.com/trisacrypto/directory/pkg/gds/emails/mock.go

...github.com/trisacrypto/directory/pkg/utils/gzip.go

...acrypto/directory/pkg/gds/store/index/container.go

...m/trisacrypto/directory/pkg/gds/store/trtl/mock.go

....com/trisacrypto/directory/pkg/trtl/interceptor.go

...github.com/trisacrypto/directory/pkg/trtl/peers.go

...ithub.com/trisacrypto/directory/pkg/trtl/backup.go

...risacrypto/directory/pkg/gds/store/index/search.go

...com/trisacrypto/directory/pkg/bff/config/config.go

...om/trisacrypto/directory/pkg/gds/client/profile.go

... and 72 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fb134b7...60f707e. Read the comment docs.


Should throw if compiling uniform blocks to GLSL <= 1.30

Following code can get out without any error being thrown and will eventually produce a shader compile error.
#version 130
layout(std140) uniform Matrices
{
    mat4 mvpMat;
    mat4 normalMat;
} ubo;
...

Uniform blocks were introduced with GLSL 1.40.

Currently, I think UBOs should become uniform structs in legacy targets, but GL 3.0 (GLSL 1.30) is probably an edge case here, it's not a legacy target, except it doesn't have UBOs.


Cadl, convenience method for pageable

depend: https://github.com/Azure/cadl-azure/issues/1839
epic: https://github.com/Azure/cadl-azure/issues/1943

https://github.com/Azure/autorest.java/issues/1741


Analyse OpenAlex concept trends

[ ] Bar chart of most frequent topics in last 2 years
[ ] Investigate increase and decrease in topic popularity by calculating absolute change in topic frequency and looking at highest positive and negative growth areas between last complete year and 5 years previous. Could also look at line chart plotting rise and fall of those topics.

Is this good to close @georgerichardson?


fix(parser): date parser failing for chinese in older w issues

:tada: This PR is included in version 3.24.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add color pass flags to Forward Clustered renderer

This PR removes a lot of enum values related to the color render pass in favor of a new flag-bases approach. This means instead of hard-coding all the possible option combinations into enums, we can write our logic by checking a bit-mask.
The changes in rendering_device_vulkan.cpp add support for unused attachments. That means RenderingDeviceVulkan::framebuffer_create() can take null RIDs in the attachments vector, which will result in VK_ATTACHMENT_UNUSED entries in the render pass.
This is used in this same PR to establish fixed locations for the color pass attachments (only color and separate specular so far, but TAA will add motion vectors as well). This way, the attachment locations in the shader can stay the same regardless of which attachments are actually used.
Right now all the combinations of flags are generated, but we will need to add a way to limit the amount of combinations in the future.
I still need to look into whether this makes sense in the mobile renderer, but I wanted to get the PR out to get some feedback.
@BastiaanOlij I had to rebase on top of your multiview PR. I'm pretty sure my changes result in the same pipelines and shader versions as the ones you added, but I'm not sure how to properly test multiview, so if you can give it a check that would be awesome.

This looks awesome! We should also apply these changes to the mobile renderer.
As for stereoscopic, it crashes, strangely enough even in the editor:
CrashHandlerException: Program crashed
Engine version: Godot Engine v4.0.alpha.custom_build (60ae040b56b87e4cb5894c84c57abc6a0749368f)
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[0] Map<unsigned int,RID,Comparator<unsigned int>,DefaultAllocator>::find (D:\Development\godot4-git\core\templates\map.h:585)
[1] Map<unsigned int,RID,Comparator<unsigned int>,DefaultAllocator>::has (D:\Development\godot4-git\core\templates\map.h:621)
[2] RendererSceneRenderImplementation::RenderForwardClustered::RenderBufferDataForwardClustered::get_color_pass_fb (D:\Development\godot4-git\servers\rendering\renderer_rd\forward_clustered\render_forward_clustered.cpp:243)
[3] RendererSceneRenderImplementation::RenderForwardClustered::_render_scene (D:\Development\godot4-git\servers\rendering\renderer_rd\forward_clustered\render_forward_clustered.cpp:1630)
[4] RendererSceneRenderRD::render_scene (D:\Development\godot4-git\servers\rendering\renderer_rd\renderer_scene_render_rd.cpp:5096)
[5] RendererSceneCull::_render_scene (D:\Development\godot4-git\servers\rendering\renderer_scene_cull.cpp:3223)
[6] RendererSceneCull::_render_reflection_probe_step (D:\Development\godot4-git\servers\rendering\renderer_scene_cull.cpp:3344)
[7] RendererSceneCull::render_probes (D:\Development\godot4-git\servers\rendering\renderer_scene_cull.cpp:3372)
[8] RenderingServerDefault::_draw (D:\Development\godot4-git\servers\rendering\rendering_server_default.cpp:91)
[9] RenderingServerDefault::draw (D:\Development\godot4-git\servers\rendering\rendering_server_default.cpp:383)
[10] Main::iteration (D:\Development\godot4-git\main\main.cpp:2682)
[11] OS_Windows::run (D:\Development\godot4-git\platform\windows\os_windows.cpp:667)
[12] widechar_main (D:\Development\godot4-git\platform\windows\godot_windows.cpp:169)
[13] _main (D:\Development\godot4-git\platform\windows\godot_windows.cpp:191)
[14] main (D:\Development\godot4-git\platform\windows\godot_windows.cpp:205)
[15] WinMain (D:\Development\godot4-git\platform\windows\godot_windows.cpp:219)
[16] __scrt_common_main_seh (d:\a01\_work\6\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288)
[17] BaseThreadInitThunk
-- END OF BACKTRACE --

Here is a simple test project that works without the need of XR equipment as it just outputs a side by side image:
https://github.com/BastiaanOlij/godot_test_multiview

@BastiaanOlij the crash was related to reflection probes, but your test project helped me fix that bug and other multiview related bugs. I force-pushed the updated version.
In your project, I'm still getting some weird issues that seem related to sky rendering, and I can reproduce them on current master too, so I think they are not related to my changes, but it's hard to tell if my PR breaks anything else until we are sure it works fine on master.

@BastiaanOlij I pushed a new version, everything should be working now.

@reduz I pushed a new version that allows for registering the valid flag combinations and only compiles those pipelines. The PR is ready for a final review and merge.

@BastiaanOlij I pushed a new version, everything should be working now.

Cool, what turned out to be the problem?

@BastiaanOlij I had accidentally removed a fix while getting rid of some debug prints :)

Seems good, pending fix on above comment to merge.

Rebased and updated, should be good to merge.

Thanks!


Blog Post Topic

Current politics (Example: "There is a politician in the news, what is going on, that's it.")

It may be possible to find trending newspaper articles and then analyze those trending newspaper articles. Consider doing this as an expansion of sorts.


Kaleido 1.0.0rc0 can't plot datetimes as axis label correctly when renderer=“png”

Environment

Python 3.12
Plotly 6.0.0rc0
Kaleido 1.0.0rc0
vscode 1.96.0

Problem
in kaleido 1.0.0rc0, when set renderer="png", Plotly plot datetime as int as axis label, when set renderer="plot_mimetype", Plotly plot datetime correctly as axis label.
in Kaleido 0.2.1, no matter renderer="png" or renderer="plot_mimetype", Plotly can both plot datetime correctly as axis label.
import plotly.graph_objects as go
import pandas as pd

periods = 10
x = pd.date_range("20241215T00:00:00", periods=periods, freq="h").to_numpy()
y = list(range(periods))
fig = go.Figure()
fig.add_trace(go.Scatter(x=x, y=y))
fig.show(renderer="png")

import plotly.graph_objects as go
import pandas as pd

periods = 10
x = pd.date_range("20241215T00:00:00", periods=periods, freq="h").to_numpy()
y = list(range(periods))
fig = go.Figure()
fig.add_trace(go.Scatter(x=x, y=y))
fig.show(renderer="plotly_mimetype")

Temporarily workaround
my temporarily workaround is casting datetime to str dtype.
import plotly.graph_objects as go
import pandas as pd

periods = 1000
x = pd.date_range("20241215T00:00:00", periods=periods, freq="h")
y = list(range(periods))
fig = go.Figure()
fig.add_trace(
    go.Scatter(
        x=x.astype(str),
        y=y,
    )
)
fig.show(renderer="png")

Hi! Thanks for this, I'm going to mark it active.
I think its solved in an unreleased but already-merged pr (which may come out tomorrow or the day after).


Replace LEDs and phototransistor on LSA with IR sensors.

The current design of LSA is very prone to ambient light and often cause inconvenience in line following.
Possible solution is to test TCRT-5000 for ambience interference.
If it proves to be better than current design, we can easily modify our LSA design to include it.

As discussed previously

[ ] Try different IR based Transmitter Receiver Pairs ( PTH and SMD ) from various LAMI vendors on a perfboard
[ ] Test on the current SRA Board and check readings on ADC lines for line-following with and without a buffer amplifier IC
[ ] If buffer amplifier is needed, find a dealer (online or offline) if HEX IC is available ( 5 -6 gates in one IC ) for the facility of more than 4 sensor pairs if desired
[ ] Redesign LSA PCB prototype for the best available combinations
[ ] Test PCB Prototype
[ ] Final Order

Hard deadline - 5th November
@marck3131 proceed with this issue and update ASAP

@marck3131 Please post the perfboard testing results here ASAP

ping @marck3131. Please post the results here as well.

5 IR sensors were tested on perfboard with resistors 4.7k E and 100 E , with gpio pin numbers 32, 34, 35, 36, 39
Tested Line following too with the same ...

@marck3131 Please put the images, sensor placement and line-following demo video with new config here as well for reference.

@dhairyashah1 we can close this issue as this has been implemented in the design.

@dhairyashah1 we can close this issue as this has been implemented in the design.

LGTM. Design PR #21 merged in master.

Feature PR #21 merged in master


Docs: Publish documentation to new domain

Summary
Have GitHub actions build and publish documentation to docs.byte-bot.app

This is 1/2 done
https://docs.byte-bot.app/ is live, but it points to the readme

This is done


As an NUS student, I want to know where I should be at certain times, so that I won’t be late or miss out anything.

We will not be implementing this as we are not using location services.


Active Screen Overlay on Fixed Header

Hello @lakshyatyagi24 , Can i work on this issue?

sure @Vineet955

I want to contribute to open source Projects .Can I work on this issue

Hey @lakshyatyagi24 can I try this. ?

yes sure @saumyasrivastava08 and @chinmaym07

is this issue still open i am working on it

Yes @saumyasrivastava08


 I think it has enough space for it. Instead of including your logo on the top, you should put it below the LED. Please consider this, I'm not the only one complaining about this.

I appreciate the concern and the idea, though I truly do not believe my design has the room to make this work. I believe there is a clearance issue between the hole, and the physically deeper USB Type C receptacle.
As it stands, I have no intention of implementing this change, as once the last few boards sell out on Tindie, I no longer intend to sell these.
At any rate, the project is fully open source, so you're free to fork the project and attempt to add the mounting hole yourself. You could even replace the USB C receptacle with a shallower version, provided you can find a suitable replacement online.


Investigate how DSP generated model details can be captured for supporting the Registered Model Call

Is your feature request related to a problem? Please describe.
When a user is on data science pipelines screen, and asks to register the model that came of the run from UI, to make API call the details about the model are required.
Describe the solution you'd like
We need details like a model name, s3 location, model type etc from the DSP itself so that these can be supplied to the RegisteredModel API call.
Additional context
talk to DSP team and I am hoping this data can be found the MLMD server if we check the details of the run. So, there may be API call that dashboard can call get that info, we need to figure that out

@tarilabs can you document your conclusions from the demo and see if this can be closed or we need to do more work on this?


[QUERY] Use of StorageTransferOptions is not very discoverable and "sensible" parameters are not obvious

Environment:

Azure.Storage.Blobs 12.7.0

I just discovered that BlockBlobClient.UploadAsync() is extraordinarily slow in its default configuration.  Transferring 24 MB from UK to US was taking 15-20 minutes.
The solutions is to pass in a BlobUploadOptions object containing a StorageTransferOptions object.  I used
   new StorageTransferOptions
   {
       MaximumConcurrency = 20,
       InitialTransferLength = 0x10000,
       MaximumTransferSize = 0x10000
   }

and reduced the upload time to well under a minute.
This leads to a couple of comments....

Whatever defaults that are used when the options are NOT explicitly specified lead to dreadful performance and it's not terribly discoverable that you need to hand-tune them to get to a decent baseline.  (I'm guessing DownloadToAsync will suffer from the same issue.)

It's not at all obvious what "sensible" values should be provided.  I appreciate that everyone's system is different and there's no "right" answer but perhaps some singletons such as StorageTransferOptions.TypicalDesktop or StorageTransferOptions.IIS would help.  Failing that, improving the documentation (https://azuresdkdocs.blob.core.windows.net/$web/dotnet/Azure.Storage.Common/12.4.1/api/Azure.Storage/Azure.Storage.StorageTransferOptions.html) to suggest some typical values would be useful.

Thank you for your feedback.  Tagging and routing to the team best able to assist.

@jaschrep-msft @kasobol-msft To help address better defaults for download/upload options and to see if maybe documentation is needed to help suggest certain values (obviously this would require the user to have a good grasp on their environment and we should have to put some kind of disclaimer that the defaults suggested can only help to an extent)

@jaschrep-msft, James can you coordinate with Tamra and get the doc updated to reflect the sensible defaults and then close this bug with the link to the doc?

@jaschrep-msft, James can you coordinate with Tamra and get the doc updated to reflect the sensible defaults and then close this bug with the link to the doc?

For those hitting this thread, there's some useful related info in this checklist (not addressing the specific point of optimal StorageTransferOptions settings; but closely related): https://docs.microsoft.com/en-us/azure/storage/blobs/storage-performance-checklist#checklist

Update: a guide to StorageTransferOptions is underway and going through our internal review and publishing process.

A blog post on this topic has been published to the Azure SDK dev blog.


SwapTwoNumbers

Why:
Closes #1713
What's being changed:
added a c file for SwapTwoNumbers.

Hey @Osher160
Please get auto-assigned to the linked issue by commenting !assign on #1713 to prevent any conflict 🤗


WIP: 113/skip turn

Solves #113
This pull request introduces new command. Users can skip there turn instead of moving or attacking
This is still work in progress because ui widget does not implemented. However, you can test this by executing game.process_skip_turn() from web console

Skip turn button has been added
However, there are some bugs:

selected unit does not stop pulsing
backend and frontend become out of sync when you skip turn after move without attack

Need to test it manually and kill all bugs

Skip turn button has been added
However, there are some bugs:

selected unit does not stop pulsing
backend and frontend become out of sync when you skip turn after move without attack

Need to test it manually and kill all bugs

Bug, mentioned here was fixed

Bug, mentioned here was fixed

Still struggling with tests


Caret icon in dropdown button does not represent the current state

Select one ...  (check one with "x")
[ ] bug
[ ] feature request
[x] enhancement

Expected behavior
The caret icon should point upwards when the dropdown is open.
Actual behavior
The caret icon is always pointing downwards regardless of the dropdown state.
Reproduction of behavior
N/A
Environment details

Angular version: 5.2.9

Clarity version: 0.11.10

OS and version: macOS 10.13.3

Browser: [Chrome 63]

@karmasakshi
There is a problem with this feature request when we consider that dropdown menus can show up on top, to the right, to the left, or on the bottom of the dropdown trigger. If there is a use case for your application that requires this behavior, it can easily be achieved with a few lines of CSS to augment the default styles. But it is not a feature we plan to implement in Clarity.
Thanks!


[CWS] Allow suppressing all non-drift rule-based events

What does this PR do?
This PR modify the auto-suppression behavior.
To be suppressed:

the matching rule has to have the allow_autosuppression=true tag.
the event type should be defined in runtime_security_config.security_profile.auto_suppression.event_types
the event should have an associated containerID
if the workload have an active dump: we should have the runtime_security_config.activity_dump.auto_suppression.enabled config set to true.
if the workload have an active security profile (either in learning, or in stable with the event already present): we should have the runtime_security_config.security_profile.auto_suppression.enabled config set to true.

And now if a workload has no active security profile, and neither an active activity dump (this happens when a new workload starts while we already reached the maximum of concurrent active dump), we can allow events to be suppressed if runtime_security_config.activity_dump.auto_suppression.enabled config is set to true.
Motivation
Events could be suppressed while an activity dump is running, most of the remaining noise comes from workloads that are in wait list to be dumped. This change should allow to remove most of the remaining noise.
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes

/merge


feat: add basic support for multi-cluster replication

This adds the bare minimum changes to enable multi-cluster replication, and adds some docs to explain concretely how to achieve it.

apologies for the delay, new version up now

Hi @arlyon !
e2e are all failing :)

Hey folks, is this going to land soon?
Multi-cluster replication would be huge for migrating to this operator and afaik it's the only way to change shard-count without killing the cluster!

I fixed the lint error now. It is slow going as I can't run the tests locally since they rely on kind, each iteration requires CI approval, and, most importantly, I am slow to update this :)
Hopefully we can get it landed soon.

Hey @alexandrevilain apologies for the back-and-forth. I got access to a machine that can run kind and have verified that the e2e tests work now.

Hey @alexandrevilain apologies for the back-and-forth. I got access to a machine that can run kind and have verified that the e2e tests work now.

Greeeat! I’ll review this as soon as possible! Thanks for your work! 👌

Hi @arlyon !
Do you need so help for the last few steps ? :)


Python 3 support

Pattern should start supporting Python 3. Looking at the amount of code, it is a non-trivial task and any help is much appreciated.

+1 for Python 3 support.
I realize the need to support a mature, powerful, and loyal community of legacy Python users, but Python 3 is only going to get more relevant with time, not less.
More importantly, Python 3 is just better.  Its standard library organization is much cleaner, its syntax is more readable, and in many common cases it performs significantly better than Python 2 (speed and/or memory footprint).
That said, it’s often tricker to port to Python 3 than it “feels” like it should be.  For a while, six has helped make this a little easier, but it only went so far.
To make the transition as painless as possible, I strongly recommend the Python-Future package. It is way more powerful than six; it has tools focused on automating as much of the transition as possible; and it has truly excellent documentation.
I believe it was mentioned earlier in this thread, but I just wanted to reiterate its awesomeness for anyone that might have missed it.  Seriously—just browsing its documentation can evoke the inspiration to transition to a 2-3 compatible codebase.

I haven’t used Pattern yet, but it also has excellent documentation (great job!).  Unfortunately, my current research is in Python 3.  That’s how I found my way to this page.  I hope Pattern gets to Python 3 soon!
Keep up the excellent work, and May The Source™ Be With You!

@Zearin I used future to do the majority of the heavy lifting in the python 3 port, see the pattern3 repo. Please do try it out.

How could you define the "state" of the project for porting Pattern into Python 3?
I used two years ago for Python 2.7 and it was awesome, now I'm going to work with Python 3 and I would love to use it (Pattern) again!
Thanks!

Greetings, we came across this from here, and I just noticed that while a lot of the build looks stable, support for Python 3.3 seems not to be working? At least that is how I would interpret the Travis CI page. Thanks.

I just quickly tested it on Python 3.4, by creating a conda virtual environment with python 3.4 (using conda create -n python3 python=3.4 anaconda) and running the following:
    git clone https://github.com/pattern3/pattern.git
    cd pattern
    python setup.py install

However, unfortunately, upon testing, text parsing functions at least for the web module do not seem to work... In the test folder I ran python test_web.py which is what we are using, and the following is a sample of what I got back...
======================================================================
FAIL: test_plaintext (__main__.TestPlaintext)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test_web.py", line 455, in test_plaintext
    u"link\n\n* item1 xxx\n* item2")
AssertionError: 'tags amp; things\n\ntitle1\n\ntitle2\n\nparagr[93 chars]tem2' != 'tags & things\n\ntitle1\n\ntitle2\n\nparagraph[76 chars]tem2'
- tags amp; things

======================================================================
FAIL: test_encode_utf8 (__main__.TestUnicode)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test_web.py", line 53, in test_encode_utf8
    self.assertTrue(isinstance(web.encode_utf8(s), str))
AssertionError: False is not true

----------------------------------------------------------------------
Ran 91 tests in 0.500s

FAILED (failures=4, errors=40, skipped=1)                                       357d  ⍉

(python3)

I used pattern with Python 2 before and I loved it, but now I switched to Python 3. What is the status of porting Pattern to Python 3?

It is astonishing to me that someone hasn't completed a full update to get Python 3 version of pattern working. I guess I will fork pattern3 and try to finish it myself.

never mind. too many recursion errors, encoding errors, etc. someone who knows the actual codebase should really update it.

@jamesacampbell it's not so far off https://github.com/pattern3/pattern/issues/5

@hayd yeah i was getting bogged down in all of the failures in test_web and test_db but did notice that the others were passing. commenting in that thread now. thanks

Tips to write Python 2-3 compatible code:
http://python-future.org/compatible_idioms.html
https://docs.python.org/3/howto/pyporting.html
This library is very good, and it can't stop in time...

Support for Python 3 is a long and ongoing discussion.
@hayd has done a lot of work on this -- see also https://github.com/pattern3/pattern
@hayd and I agreed that we should merge his work back into the main branch and take it step by step in a single branch, but I never get round to it due to time constraints. It's frustrating. Students at the university are now taught Python 3 and we can't offer Pattern to tell them about Natural Language Processing.
I will give it another go by submitting the task to Google Summer of Code.
But really Pattern needs more people that manage pull requests, that have push and admin rights, and that can take it into their own hands. Being the sole admin has worked well in the past to keep the source code clean and the focus tight, but we need to rethink this strategy.
Contact me at<EMAIL_ADDRESS>if you feel like stepping up.

@tom-de-smedt I would be interested in taking this on as a part of GSoC.

Possibly relevant in this discussion: http://www.python3statement.org/  , major scientific Python projects are phasing out 2.7 support. You might even want to consider dropping 2.7 entirely and switch to 3 at a next major version release, if that makes the transition easier.

Hello everyone, i've gone through the issues and it's very interesting. So many questions asked about pattern's compatibility with Python3. Currently working on a python3 project and i need pattern but i can't install due to compatibility issues.
@hayd i went through your pattern3 repo and noticed the Travis build was failing do you need help with that.

@andela-bolajide can't speak for @hayd but please if you have time fork it and get the travis builds passing and then do a merge request or I would use your fork as is in meantime if you get it fully working in Python 3. I don't have time myself to do it.

Okay @jamesacampbell, i'll get to work tomorrow and i'll be in touch. Cheers man

Hi guys, I found that textblob is using pattern library and they provide python 3 support. So if anyone is in a hurry, just to there and check the docs.

Hi ,
I using python 3, I cant install pattern with anaconda. I try 'pip install pattern',but it doesn't work .
this is the result:

Pattern isn't compatible with Python3 yet. @afsun

my friend installed it for python3. but she cant remember how did she do that !

@tom-de-smedt I would be interested in taking this on as a part of GSoC.

I did not take this project.

I will work on this issue as part of this year's GSoC, so there will definitely be some substantial progress over the summer. We will probably track most of the development in the preliminary pattern3 repository for now, since parts of the code are already ported. We'll see what the status quo is – what works and doesn't work – over the next weeks.
So if you want to be part of all that (which would be great!), bring in your ideas or thoughts on the process and make sure to follow the above mentioned repository.

@markus-beuckelmann very excited about this, thanks

Update: As part of Google Summer of Code 2017, Markus Beuckelmann (@markus-beuckelmann) will be working on the future of Pattern (porting it to Python 3 is first on our list). Markus is admin of the repo now and can handle pull requests and invite collaborators. Be sure to reach out to him and include him in discussions about the port. About the pattern3 fork: a lot of work was done here by Andy Hayden (@hayd). Andy & I agreed that a fork, which was my idea, was not the best idea. All work on porting the toolkit should happen here. So we will take what we can use from the pattern3 repo, put it in here, and continue here, eventually discarding the pattern3 fork. It is less confusing for everyone if we work on 1 repo instead of 2 forks. Hopefully we can make some progress over the summer.

Thanks @tom-de-smedt, I hope it's going to be a productive summer! Here is how I plan to proceed...

First steps will be...

to rip out the bundled dependencies (e.g. feedparser, json, BeautifulSoup, ... in pattern.web) from the code base and make them external dependencies. (Done!)
to make ideally all unit tests pass for Python 2.7.13. Only from this we can confidently start porting to Python 3 and immediately see if the introduced changes break Python 2 support.

Unfortunately, as of right now, not all unit tests pass for Python 2.7.13, e.g. a lot of tests in test_web.py fail because either APIs are discontinued or deprecated – we can just skip these for now and deal with it later. Others are more important, e.g. in test_en.py, test_text.py and it's not immediately clear (at least to me) why they fail now when they used to pass. I'll have to look into this...
I will setup Travis CI (continuous integration) to make the unit testing easier, especially to keep track of which tests pass/fail for different Python versions. (Done!)
I'll leave the master branch untouched for now and keep all the commits working towards a stable Python 2.7 version in the development branch. Forked from development we will have a python3 branch where we can work on porting to Python 3.
We will merge python3 back to development later down the line and eventually merge everything back into master. If the changes are significant enough, we should at some point consider releasing a new major release.
I will also try to create something like a todo list listing individual steps of the overall process (both related to porting to Python 3 and more general improvements) and maybe some milestones. Maybe this will make it easier for people to jump in and work on some issues.
Let's continue to use this issue here (#62) to talk about the general status quo and bigger picture of Python 3 support. However, I will open some issues in the next days where we can talk about the details of individual steps/problems.
One more thing: What are people's thoughts on dropping support for Python 2.6?

Finally, and I think I speak in the name of many Pattern users/developers, special thanks to @hayd for all the valuable work done in the pattern3 fork. We will make use of it wherever reasonable.

Just checked pattern3 and it seems it also uses sgmllib inside pattern/web, would be good someone is familiar how it works or what it does (maybe code for that lib?) as due to that one I can't even start running tests :) I think it can be changed to lxml. Every other test of pattern3 seems doesn't have such dependencies and can be worked out.

I realize I'm a bit behind on keeping people following this issue up to date with the latest progress! Google Summer of Code is over, since a couple weeks now already, and it has brought substantial progress (see full list of commits). We are now in a position where we have a version on the development branch that supports all modules except for pattern.server on both Python 2.7 and Python 3.5+. For people who want to find out more about the specifics and intermediate steps, go ahead and read my detailed GSoC reports on the Newsaudit blog (#1, #2, #3).
So now the plan is to smooth out the rough edges and release a new major version Pattern 3.0 within the next months. There is really only one known bug at the moment that is solely related to Python 3 and it only affects the information gain tree classifier IGTree in pattern.vector. Then there are a couple of issues like deprecated web APIs in pattern.web that should be addressed before the next release.
In the meantime, everybody feel free to check out the development branch and report any issues that may come along!

not sure how long this is gonna take. but as soon as the page is up again maybe you can add some info about that dev works with py3, what the restrictions are (what does not work yet) and how to install it. e.g.
go into your python3 environment!
git clone https://github.com/clips/pattern
cd pattern
git fetch
git checkout development
python setup.py install

might make a lot of people happy

Sure, I will update the README.md on the master branch with some more information in the next days.

@markus-beuckelmann Is there any update on this? Is the current advice to build the development branch if we need python 3 support?

@jpfairbanks, yes, if you need Python 3 support right now you can check out the development branch: git clone -b development https://github.com/clips/pattern

I have installed  pattern3 with pip in a conda virtual environment.  I am working in Windows 8.1  64-bit .When I try to execute
from pattern3.en import tag
I have the following errror:
Traceback (most recent call last):
  File "test_pattern.py", line 5, in <module>
    from pattern3.en import tag
  File "C:\Users\Rodolfo\Anaconda3\envs\flasky\lib\site-packages\pattern3\text\en\__init__.py", line 22, in <module>
    from pattern3.text import (
  File "C:\Users\Rodolfo\Anaconda3\envs\flasky\lib\site-packages\pattern3\text\__init__.py", line 28, in <module>
    from pattern3.text.tree import Tree, Text, Sentence, Slice, Chunk, PNPChunk, Chink, Word, table
  File "C:\Users\Rodolfo\Anaconda3\envs\flasky\lib\site-packages\pattern3\text\tree.py", line 37
    except:
         ^
IndentationError: expected an indented block

Any idea  or help will be appreciated :)

@masaguaro I have the same issue while trying to use gensim lemmatization. Maybe a recent push gone wrong by a mix of tabs and spaces?
I'll open a new issue about this.

Thank you @JanmajaySingh . I posted the same question on stackoverflow but I had no answer . It seems that there is not too much  Python 3 support. Perhaps you are right, and it's just a mix of tabs and spaces, which shouldn't be difficult to fix (using Sublime, for example). Right now, I am doing some work with NLPTK, but I will keep your idea for future use.

@masaguaro @JanmajaySingh (#217), you are using the deprecated pattern3 repository which contains a completely different code base that is not maintained anymore. There is a development branch here on clips/pattern with Python 3 support. You can clone it, git clone -b development https://github.com/clips/pattern and install with pip or conda. Let us know if there are any issues with the development branch...

@markus-beuckelmann Thanks! Issue #217 was closed.

Hello @markus-beuckelmann  @JanmajaySingh
I am working in Windows 8.1 64-bit, in a conda virtual environment.
I was trying to run pattern/examples/01-web/04-twitter.py and I had the following error:
Traceback (most recent call last):
  File "C:\Users\Desktop\pattern\examples\01-web\04-twitter.py", line 12, in <module>
    from pattern.db import Datasheet, pprint, pd
  File "C:\Users\Desktop\pattern\examples\01-web\..\..\pattern\db\__init__.py", line 1879, in <module>
    csvlib.field_size_limit(sys.maxsize)
OverflowError: Python int too large to convert to C long
[Finished in 1.5s]

Any idea ?  Thank you in advance.

Hey,
Is there any time frame on an official release of the python3 support? Or an idea of how close it is to being ready?
Thanks,
Ash

If enough people are interested, especially if it helps them working. Maybe we can consider putting a bounty on this task? It would be nice it such work would be paid :)
https://www.bountysource.com/issues/1685084-python-3-support

@zedrem @tuxayo Considering that the development branch was last updated 9 months ago, I guess the primary contributors have been busy.
The dev branch in its current form works without issues (at least for me). You can refer to @markus-beuckelmann 's comment (March 6).

@masaguaro I dunno if you could find a workaround to your issue, but I guess modifying the C source code to something like long long int might help. But it may break other modules in unexpected ways. I don't know any other details about your project though, you're better off asking on S/O.

Yea thanks, I've read the thread and understand that you can use the tool from the development branch. For what I needed, I was happy to even use the pattern3 side-project that was set up initially and then discontinued.
However, I really like patterns article extraction tool and want to incorporate it into another tool that I'm building. As far as i'm aware (?) there is no way to do that with pattern in its current condition. I'm guessing that you can't specify specific git branches in your requirements.txt for example?
If anyone is aware of any similar article extraction tools, please let me know (but I'm conscious that it is off topic for this thread).

@zedrem For me, I can install it by running this

sudo apt-get install mysql-server
sudo apt-get install libmysqlclient-dev
git clone -b development https://github.com/clips/pattern
cd pattern/
sudo python3 setup.py install

A lot of work was done by @markus-beuckelmann during last year's GSoC. During this year's GSoC, @Xsardas1000 (Maksim Filim) is doing great work (Markus & me are mentoring). Check Max' progress here: https://github.com/clips/pattern/tree/devmodified
We should be able to get out an "overall stable" official release by the end of the month, if everything goes well.
If you notice things that don't work yet, please report them here. Better yet, if you want to help out, please let us know, we can give you some editing privileges and author credits to move things forward more quickly.
As a side note, the documentation needs to move to a new location too (e.g., www.pattern3.net). Let us know if you'd want to contribute some web development skills to this end.
Thanks for your patience, we're nearing a stable release of Pattern 3.

Hy, I'm an undergrad student at Unicamp (Brazil) and got interested in helping this repo. I thought about starting with code coverage and found that there's some duplicated code at server/__init__.py, db/__init__.py and others, is this intentional?


Update Dockerfile to python3

update dockerfile to use python3 in latest version of cloud9
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Subsequent PR updated additional module files as well.


resolve #11 add custom log fn

May be better to only ask for one function and pass an additional argument into the function: stage="train"|"test"

Can you fix the missing CLA error below first? I'll review the PR after that.

@lerrytang done!

Thanks for the PR, can you give example code of supplying a tensorboard log function?
This code serves as both a test and is something mentioned in #11 .
You can modify one of the examples (e.g., mnist or cartpole).

Should I add some actual code or can it be documentation?
Some problems that arise around the example code:

does the user have tensorflow (or pytorch) installed? should we throw a warning or an error if tensorboard is not found?
the logging function needs to access the tensorboard Summary object
if using tensorflow's tensorboard implementation the logging function has to be inside a with statement:

with writer.as_default():
  def log_scores_fn():
       pass

   trainer.run()

pytorch's tensorboard implementation has different syntax (and doesn't require a with statement)

It might be better to describe this code in a documentation section rather than modify the example.
Or I could make a separate example .py file with strict requirements for tensorflow or pytorch installation.

I'd prefer some actual code that proves the PR works, on top of that, extra documentation is better.
As for the problems w.r.t the example code, it is the logging function provider's responsibility to address them.
If the logging function depends on something else, can we enclose it? Something like:
# Just an example, not tested.
def get_logging_fn(writer):
    def fn(fn_args):
        with writer.as_default():
            do_stuff()
    return fn
trainer = Trainer(logging_fn=get_logging_fn(tf_writer), ...)

I just discovered flax provides tensorboard too! It's already in evojax dependencies, probably we should use it?

hey @lerrytang, any update on this?

Hi, apologies for the delay.
I tested the PR but it has some problems:

With no additional packages installed, it gives a warning message Please install either tensorflow or pytorch to log the rewards to tensorboard. This is ok.
However, after installing pytorch, I still get this message.
After installing tensorboard, I get an error complaining about AttributeError: module 'distutils' has no attribute 'version'. This is due to distutils change and can be easily fixed, however, this adds an extra workload to the users.

I suggest the following modifications:

Change the warning message. It seems installing pytorch and tensorboard suffices.
In evojax.util, can you catch distutils error (AttributeError: module 'distutils' has no attribute 'version') and print out the fix for the users? (e.g., modify torch/utils/tensorboard/__init__.py: add from distutils.version import LooseVersion and comment out LooseVersion = distutils.version.LooseVersion)

Again, sorry for the delay and thank you for the contribution.

This is weird. Looks like you installed an old pytorch version. Looks like this bug has been fixed a year ago: https://github.com/pytorch/pytorch/pull/69904
what is your pytorch version?

Fixed the warning to mention the tensorboard package too.


How to inject variables into custom popovers?

I'm not able to find a way to inject variables into a custom popover. It seems like I should be able to use variables inside of the custom popover template, but that did not work. It does not seem to have access to the view model.

When doing custom popovers, the Popover element is actually part of your view, it has access to the ViewModel. You don't need to inject anything, you can just access any property or method in your view model.
How are you trying to use it?

I tried that but it doesn't seem to be working - in the Aurelia inspector there were no variables exposed. Basically I did something like this:

    ${item.title}

  ${item.id}

But item is not exposed inside of the popover.

That looks about right, it should work, I will take a look as soon I have a chance.

I did some testing, and it is working as expected, I was able to bind to properties in the View Model inside the Custom Popover.
Can you please provide the complete example, maybe we are just missing something.

                  test ${item.created_at}

${item.id}

${item.id}

This is the code. ${item.id} is defined correctly in the triggering div but is undefined in the popover. Any idea?

Oops, figured it out. It gets the variables from where it is defined, not from where it is called. I misunderstood. Thanks @tochoromero for checking on this!

I'm glad you figured it out :)


Simulator: power supply

Can we get a simulator for the dashboard for the power supply service?
The dashboard already shows an enabled toggle, but it would be good to have a slider between voltage_min and voltage_max if possible. There should probably be some default UI for all services that use the min_value max_value registers?

Fixed by https://github.com/microsoft/jacdac-docs/commit/ce90341465457808ac1fcb1f0c8254538aba236d


Agent's Information Set

The individuals know their values for U_1 and U_0 when making their decision. Please account for this when simulating the choice.

This seems done as part of eribon edits?


Use RWMutex for Cache Synchronization

We currently use a standard sync.Mutex for locking cache objects. This means that if multiple users are requesting the same cached object at the same time, they will be served in the waitlist sequence rather than concurrently. The desired behavior would be for global read access to a cache object unless a write is required, with an exclusive lock being required just for the duration of the write operation.

feature is completed in v1.1!