[BUG] - Timeout waiting for module.kubernetes-keycloak-helm.helm_release.keycloak

OS system and architecture in which you are running QHub
macOS Catalina 10.15.7
Expected behavior
Successful deployment of stage 05-kubernetes-keycloak
Actual behavior
Upon repeat deployments, I am getting this error:
[terraform]: │ Error: timed out waiting for the condition
[terraform]: │
[terraform]: │   with module.kubernetes-keycloak-helm.helm_release.keycloak,
[terraform]: │   on modules/kubernetes/keycloak-helm/main.tf line 1, in resource "helm_release" "keycloak":
[terraform]: │    1: resource "helm_release" "keycloak" {

from this change:
[terraform]:   # module.kubernetes-keycloak-helm.helm_release.keycloak will be updated in-place
[terraform]:   ~ resource "helm_release" "keycloak" {
[terraform]:         id                         = "keycloak"
[terraform]:         name                       = "keycloak"
[terraform]:       ~ status                     = "failed" -> "deployed"
[terraform]:         # (26 unchanged attributes hidden)
[terraform]:
[terraform]:         set {
[terraform]:           # At least one attribute in this block is (or was) sensitive,
[terraform]:           # so its contents will not be displayed.
[terraform]:         }
[terraform]:     }
[terraform]:
[terraform]: Plan: 0 to add, 1 to change, 0 to destroy.

How to Reproduce the problem?
This is my config:
project_name: aimee-qhub
provider: aws
domain: eo-analytics.delta-backend.com
certificate:
  type: lets-encrypt
  acme_email<EMAIL_ADDRESS>  acme_server: https://acme-v02.api.letsencrypt.org/directory
security:
  authentication:
    type: GitHub
    config:
      client_id: XXX
      client_secret: XXX
  keycloak:
    initial_root_password: XXX
default_images:
  jupyterhub: quansight/qhub-jupyterhub:v0.4.3
  jupyterlab: quansight/qhub-jupyterlab:v0.4.3
  dask_worker: quansight/qhub-dask-worker:v0.4.3
storage:
  conda_store: 200Gi
  shared_filesystem: 200Gi
theme:
  jupyterhub:
    hub_title: VEDA QHub
    hub_subtitle: NASA VEDA
    welcome: Welcome to the VEDA Analytics QHub.
    logo: https://cdn.cdnlogo.com/logos/n/66/nasa.png
    primary_color: '#5d7fb9'
    secondary_color: '#000000'
    accent_color: '#32C574'
    text_color: '#5d7fb9'
    h1_color: '#5d7fb9'
    h2_color: '#5d7fb9'
    version: v0.4.3
helm_extensions: []
monitoring:
  enabled: true
argo_workflows:
  enabled: true
kbatch:
  enabled: true
cdsdashboards:
  enabled: true
  cds_hide_user_named_servers: true
  cds_hide_user_dashboard_servers: false
ci_cd:
  type: github-actions
  branch: main
  commit_render: true
terraform_state:
  type: remote
namespace: dev
qhub_version: 0.4.3
amazon_web_services:
  region: us-west-2
  kubernetes_version: '1.23'
  node_groups:
    general:
      instance: m5.2xlarge
      min_nodes: 1
      max_nodes: 1
    user:
      instance: m5.xlarge
      min_nodes: 1
      max_nodes: 5
    worker:
      instance: m5.xlarge
      min_nodes: 1
      max_nodes: 5
jupyterhub:
  overrides:
    singleuser:
      lifecycleHooks:
        postStart:
          exec:
            command:
              [
                "gitpuller",
                "https://github.com/NASA-IMPACT/veda-documentation",
                "master",
                "docs",
             ]
profiles:
  jupyterlab:
  - display_name: Small Instance
    description: Stable environment with 2 cpu / 8 GB ram
    default: true
    kubespawner_override:
      cpu_limit: 2
      cpu_guarantee: 1.5
      mem_limit: 8G
      mem_guarantee: 5G
  - display_name: Medium Instance
    description: Stable environment with 4 cpu / 16 GB ram
    kubespawner_override:
      cpu_limit: 4
      cpu_guarantee: 3
      mem_limit: 16G
      mem_guarantee: 10G
  dask_worker:
    Small Worker:
      worker_cores_limit: 2
      worker_cores: 1.5
      worker_memory_limit: 8G
      worker_memory: 5G
      worker_threads: 2
    Medium Worker:
      worker_cores_limit: 4
      worker_cores: 3
      worker_memory_limit: 16G
      worker_memory: 10G
      worker_threads: 4
environments:
  environment-dask.yaml:
    name: dask
    channels:
    - conda-forge
    dependencies:
    - nbgitpuller
    - python
    - ipykernel
    - ipywidgets
    - qhub-dask ==0.4.3
    - python-graphviz
    - numpy
    - numba
    - pandas
    - pip:
      - kbatch
  environment-dashboard.yaml:
    name: dashboard
    channels:
    - conda-forge
    dependencies:
    - nbgitpuller
    - python==3.9.7
    - ipykernel==6.4.1
    - ipywidgets==7.6.5
    - qhub-dask==0.4.3
    - param==1.11.1
    - python-graphviz==0.17
    - matplotlib==3.4.3
    - panel==0.12.7
    - voila==0.3.5
    - streamlit==1.0.0
    - dash==2.0.0
    - cdsdashboards-singleuser==0.6.1

so with GITHUB_TOKEN, AWS_ creds set, I run the qhub deploy -c aimee-config.yaml
Command output
No response
Versions and dependencies used.
$ conda --version
conda 4.13.0

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"darwin/amd64"}

$ qhub --version
0.4.3

Others that might be relevant:

terrafrom 1.2.9
hashicorp/kubernetes v2.7.1
hashicorp/random v3.4.3
hashicorp/aws v4.34.0
hashicorp/helm v2.1.2

Compute environment
AWS
Integrations
Keycloak
Anything else?
No response

@abarciauskas-bgse if you have kubectl installed could you ran the following:

kubectl get pods --namespace=dev keycloak-0, this will tell if Keycloak is running
kubectl describe pod -n dev keycloak-0 , will show the pod's events
kubectl logs -n dev keycloak-0 --tail 100 will give us some logs

also, have you tried running the deploy command after a few minutes passed since the first timeout error?

Hi @abarciauskas-bgse, we released v0.4.5 Friday. This latest release should resolve the issues you're experiencing above. Thank you for your interest in QHub and let us if your deployment was successful :)

Adding @tracetechnical to this thread - he has been troubleshooting our deployment and found and fixed the issue with EBS CSI drivers and the updated kubernetes version, so we do believe the 0.4.5 upgrade should fix this problem. Thanks @iameskild


[pylint] Pin lazy-object-proxy dependency to latest working

What does this PR do?
Pins lazy-object-proxy dependency to latest working (1.6.0)
Motivation
1.7.0 broken for python2 (https://github.com/ionelmc/python-lazy-object-proxy/issues/61)
Describe how to test/QA your changes
No QA needed
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] The appropriate team/.. label has been applied, if known.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

Merging, pylint2 build step passes on all platforms


Set supertype on ruletypes even without fields or actions

Fixes https://github.com/langium/langium/issues/152

We discussed that with @spoenemann already. As far as I remember in case of AST generation such types should be generated. And as a designer of the Grammar and/or developer of a Code-Generator based on the AST I would expect to have such type inference.

since this exhibits a lot of unexpected behavior.

@msujew: What exactly wouldn't be expected?

How I understand, @msujew supposes different behavior when the rule X is alternatives and when it's a just "call", so 'X: Y' doesn't generate a type X, but X: Y | Z generates. Is it true?

Ah, ok. Thanks for the hint, @Pluralia .
But even then as a designer of the grammar I would expect such type hierarchy. I mean, it is the decision or responsibility of the one who designs the grammar, or?


Enhancing The Update Framework (Python - TUF) README

Description of the changes being introduced by the pull request:

Table of Contents: Added a Table of Contents to improve navigation and accessibility within the README.

Logo Color: Changed the logo color from black to white to enhance visibility and improve the overall aesthetic of the document.

Additional Badges: Included additional badges to highlight key aspects such as version, license, tech-stack, and community support, providing users with quick access to essential information.

Back to Top Button: Added a "Back to Top" button at the bottom of the README to facilitate easy navigation within the document.

Installation Section: Added an Installation section to provide users with clear guidance on how to install the software.

Contact Section Enhancement: Separated the Mailing List and CNCF Slack links for better readability and organization within the Contact section.

CNCF Logo Addition: Added the CNCF logo at the bottom of the README to acknowledge the project's affiliation with the Cloud Native Computing Foundation.

Before:

After:

Fixes #2654
Reviewers:
@trishankatdatadog @JustinCappos

@trishankatdatadog please review this PR for the issue #2654

2. Logo Color: Changed the logo color from black to white to enhance visibility and improve the overall aesthetic of the document.

This change makes the logo invisible with default GitHub Settings (You are using dark theme on GitHub so see the opposite effect).

Logo Color: Changed the logo color from black to white to enhance visibility and improve the overall aesthetic of the document.

This change makes the logo invisible with default GitHub settings (You are using dark theme on GitHub so see the opposite effect).

To ensure the logo is visible in both light and dark themes, a solution that automatically switches the logo based on the user's selected theme preference can be implemented. This strategy involves utilizing two different logo versions (one for light theme and one for a dark theme) and utilizing HTML and CSS to manage the theme-based switching.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.805%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1554

Relevant Lines:
1591

💛  - Coveralls

@jku it works for both light and dark theme now. please have a look

@trishankatdatadog @JustinCappos please review this PR for the issue #2654

Sorry, I'm running out of B/W... please try someone else? @jku has been massively helpful here, thanks!

@jku already left a thorough review here. From what I see, the key improvement of this PR is to use the correct markup for the section headers. @shubhusion, do you plan to address the review comments?

@jku already left a thorough review here. From what I see, the key improvement of this PR is to use the correct markup for the section headers. @shubhusion, do you plan to address the review comments?

@lukpueh yeah I will make changes as specified

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.805%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
1554

Relevant Lines:
1591

💛  - Coveralls

I'm closing this since no action in 2 months.
Please reopen if you get to it at a later date


Update screenshots containing sqrts and fix issue with document fragments inside sqrts

@kevinbarabash Thanks for fixing my error in declaring inner.


Add link to example repo using react-testing-library to test a Relay …

…Modern app.
I've made a rather extensive example of how to test a Relay Modern GraphQL app, and I've used react-testing-library for all tests. I figured it might be interesting for people to see how you can test a Relay Modern app with react-testing-library, mocking queries, and so on.
Would this be a good link to add to the readme? What do you think?

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


React flow stops responding after pressing shift+command+4 on macOS chrome

Hello,
As described in the title, you can easily reproduce this by opening https://reactflow.dev/examples/ on chrome in macOS and press shift+command+4.
After taking a screenshot, react flow stops responding.
The bug is not present on Firefox browser in macOS.

Duplicate of #824


Indeterminate progress bar doesn’t work in Edge

The colors are not applied, using custom properties and var(), for the valo-progress-slide keyframes.

Regression from 8aec886c5210a935a8372e67fb3eeb9f9731f0a7


Publish To AppSource fails with "unable to locate apps"

I'm using the latest microsoft/AL-Go-AppSource preview version.  When I run the "Publish To AppSource" action, I receive the following error in the Deliver step:
Using Azure.Storage version 2.1.0
Attempting authentication to https://api.businesscentral.dynamics.com/.default using clientCredentials...
Authenticated as app ***
AppSource MainAppFolder .\OfficeProducts
Error: Deliver action failed. Error: Internal error - unable to locate apps Stacktrace: at <ScriptBlock>, D:\a\_actions\microsoft\AL-Go-Actions\preview\Deliver\Deliver.ps1: line 430 at <ScriptBlock>, D:\a\_actions\microsoft\AL-Go-Actions\preview\Deliver\Deliver.ps1: line 99 at <ScriptBlock>, D:\a\_temp\0d7350a8-556b-49bf-9c5b-f06944c1e9e4.ps1: line 2 at <ScriptBlock>, <No file>: line 1
AL-Go action ran: Deliver Telemetry Correlation Id: 2d4b109a-f51e-4726-b175-9151ff7e31c4
Removing BcContainerHelper
Error: Process completed with exit code 1.

Freddy, you have been invited to this repo previously and should have permissions, so the repo URL is https://github.com/BMI-Software/OfficeProducts-AppSource/
If you need further information, I'll try to answer quickly.  I will be traveling on business tomorrow through early next week, and I'll keep an eye out for any responses here.
Thanks!

Thanks, will have a look tomorrow morning.

Tried to Update the AL-Go System files to a debug version of AL-Go.
Then I didn't get the same error.
I have now switched back to microsoft/AL-Go-AppSource@preview - and I also do not get the same error.
I now get this error:

Which is caused by the AuthContext for AppSource is made with the wrong scope.
When you fix that it should work.
One question - in this dialog:

Do you change any values when running?

I only changed the last value "Promote Appsource App" to Y.

We had the same issue and fixed it by adding
"scopes":"https://api.partner.microsoft.com/.default"
to the APSOURCECONTEXT Secret JSON.
Maybe that helps.

Use workflow from:  really just means where should you run the code from.
If you select a release branch or like in the drop down. you will be running an older version and you don't really want that.
On the error - it looks like you have specified the appId from app.json as your appSourceProductId.
That is wrong, you should follow these guidelines: https://github.com/microsoft/AL-Go/blob/main/Scenarios/settings.md#appsource-specific-basic-settings


installed but not working on splunk cloud.

04-05-2024 14:05:54.432 INFO  SearchPhaseGenerator [3580172 searchOrchestrator] -  Executing two phase fallback for the search=|makeresults 1| eval prompt="what can you say about splunk?" | obopenai prompt=prompt mode="nadav"
04-05-2024 14:05:54.432 INFO  SearchParser [3580172 searchOrchestrator] - PARSING: |makeresults 1| eval prompt="what can you say about splunk?" | obopenai prompt=prompt mode="nadav"
04-05-2024 14:05:54.433 INFO  ServerConfig [3580172 searchOrchestrator] - Will add app jailing prefix /opt/splunk/bin/nsjail-wrapper for TA-ob-openai-chatgpt
04-05-2024 14:05:54.433 INFO  ChunkedExternProcessor [3580172 searchOrchestrator] - Running process: /opt/splunk/bin/nsjail-wrapper /opt/splunk/bin/python2.7 /opt/splunk/etc/apps/TA-ob-openai-chatgpt/bin/obopenai.py
04-05-2024 14:05:54.526 ERROR ChunkedExternProcessor [3580188 ChunkedExternProcessorStderrLogger] - stderr: Traceback (most recent call last):
04-05-2024 14:05:54.526 ERROR ChunkedExternProcessor [3580188 ChunkedExternProcessorStderrLogger] - stderr:   File "/opt/splunk/etc/apps/TA-ob-openai-chatgpt/bin/obopenai.py", line 10, in
04-05-2024 14:05:54.526 ERROR ChunkedExternProcessor [3580188 ChunkedExternProcessorStderrLogger] - stderr:     from urllib.parse import urlparse
04-05-2024 14:05:54.526 ERROR ChunkedExternProcessor [3580188 ChunkedExternProcessorStderrLogger] - stderr: ImportError: No module named parse
04-05-2024 14:05:54.531 ERROR ChunkedExternProcessor [3580172 searchOrchestrator] - EOF while attempting to read transport header read_size=0
04-05-2024 14:05:54.531 ERROR ChunkedExternProcessor [3580172 searchOrchestrator] - Error in 'obopenai' command: External search command exited unexpectedly with non-zero error code 1.
04-05-2024 14:05:54.532 ERROR SearchPhaseGenerator [3580172 searchOrchestrator] - Fallback to two phase failed with SearchProcessorException: Error in 'obopenai' command: External search command exited unexpectedly with non-zero error code 1.
04-05-2024 14:05:54.532 WARN  SearchPhaseGenerator [3580172 searchOrchestrator] - Failed to create search phases: exception=31SearchProcessorMessageException, error=Error in 'obopenai' command: External search command exited unexpectedly with non-zero error code 1.
04-05-2024 14:05:54.537 INFO  SearchStatusEnforcer [3580172 searchOrchestrator] - sid=1712325954.992175, newState=BAD_INPUT_CANCEL, message=Error in 'obopenai' command: External search command exited unexpectedly with non-zero error code 1.
04-05-2024 14:05:54.537 ERROR SearchStatusEnforcer [3580172 searchOrchestrator] - SearchMessage orig_component=ChunkedExternProcessor sid=1712325954.992175 message_key=CHUNKED:NON_ZERO_EXIT__%d message=Error in 'obopenai' command: External search command exited unexpectedly with non-zero error code 1.
04-05-2024 14:05:54.537 INFO  SearchStatusEnforcer [3580172 searchOrchestrator] - State changed to BAD_INPUT_CANCEL: Error in 'obopenai' command: External search command exited unexpectedly with non-zero error code 1.
04-05-2024 14:05:54.550 INFO  SearchStatusEnforcer [3580172 searchOrchestrator] - Enforcing disk quota =<PHONE_NUMBER>0
04-05-2024 14:05:54.563 INFO  DispatchManager [3580172 searchOrchestrator] - DispatchManager::dispatchHasFinished(id='1712325954.992175', username='kundeng')
04-05-2024 14:05:54.563 INFO  UserManager [3580172 searchOrchestrator] - Unwound user context: kundeng -> NULL
04-05-2024 14:05:54.563 INFO  SearchOrchestrator [3580169 RunDispatch] - SearchOrchestrator is destructed.  sid=1712325954.992175, eval_only=0
04-05-2024 14:05:54.563 INFO  SearchStatusEnforcer [3580169 RunDispatch] - SearchStatusEnforcer is already terminated
04-05-2024 14:05:54.563 INFO  UserManager [3580169 RunDispatch] - Unwound user context: kundeng -> NULL
04-05-2024 14:05:54.563 INFO  LookupDataProvider [3580169 RunDispatch] - Clearing out lookup shared provider map
04-05-2024 14:05:54.564 INFO  dispatchRunner [162941 MainThread] - RunDispatch is done: sid=1712325954.992175, exit=0

Do you need to put python.version=3 in commands.conf?

04-05-2024 16:29:59.014 INFO ChunkedExternProcessor [3373950 searchOrchestrator] - Running process: /opt/splunk/bin/nsjail-wrapper /opt/splunk/bin/python2.7 /opt/splunk/etc/apps/TA-ob-openai-chatgpt/bin/obopenai.py 04-05-2024 16:29:59.159 ERROR ChunkedExternProcessor [3373974 ChunkedExternProcessorStderrLogger] - stderr: Traceback (most recent call last): 04-05-2024 16:29:59.159 ERROR ChunkedExternProcessor [3373974 ChunkedExternProcessorStderrLogger] - stderr: File "/opt/splunk/etc/apps/TA-ob-openai-chatgpt/bin/obopenai.py", line 19, in 04-05-2024 16:29:59.159 ERROR ChunkedExternProcessor [3373974 ChunkedExternProcessorStderrLogger] - stderr: import openai 04-05-2024 16:29:59.159 ERROR ChunkedExternProcessor [3373974 ChunkedExternProcessorStderrLogger] - stderr: File "/opt/splunk/etc/apps/TA-ob-openai-chatgpt/bin/../lib/openai/init.py", line 46 04-05-2024 16:29:59.159 ERROR ChunkedExternProcessor [3373974 ChunkedExternProcessorStderrLogger] - stderr: api_key_path: Optional[str] = os.environ.get("OPENAI_API_KEY_PATH") 04-05-2024 16:29:59.159 ERROR ChunkedExternProcessor [3373974 ChunkedExternProcessorStderrLogger] - stderr: ^ 04-05-2024 16:29:59.159 ERROR ChunkedExternProcessor [3373974 ChunkedExternProcessorStderrLogger] - stderr: SyntaxError: invalid syntax
Seems that I need to force it to run as python3, but unable to

Hi,
how did you install it in Splunk Cloud?
I see in that the app is still pending to be available in the cloud. Here https://splunkbase.splunk.com/app/6957 it does not specify compatibility to Cloud so it's not downloadable from the cloud Splunkbase.
As far as I know, Python 2 was removes from Splunk cloud, what version and build are you using? (in Splunk cloud, go to "[Support & Services] on the upper right, then [About])
Thanks

I just downloaded from the above URL and then installed it directly using splunk cloud web UI as a private app.

I am not sure why python 2 is still being used for our tenant.

I uploaded a new version that is now pending for Victoria with python.version = python3, I hope it will help. Anyways maybe Splunk support know why python 2 exists in your environment, because I think it should have been deleted completely.

I talked to splunk support, they have been playing ball and refusing to remove python 2.  Anyway,  did you put that in app.conf, as I tried to put it into commands.conf and it didn't work.

I didn't put it in app.conf because according to the docs it should use "Default: the system-wide Python version". The new version is stuck pending for cloud, I tried to create a new app but it is still pending. you can try to add this setting to app.conf, but I think that if python2 is your system-wide Python version it can be a security risk so it might be worth to escalate this issue with their support. I hope they will help


v1.7 backports 2020-07-30

#11912 -- contrib: Fix submit-backport PR set-labels detection (@joestringer)
#12606 -- fqdn/dnsproxy/proxy_test: increase again timeout for DNS TCP exchanges (@qmonnet)
#12640 -- backporting: Report progress in set-labels.py (@pchaigno)
#12639 -- docs(identity): Correct discrepancy between label and descriptions (@sayboras)
#12704 -- contrib: Print PR number in set-labels.py (@christarazi)
#12703 -- contrib: Tighten search for list of PRs (@christarazi)

Once this PR is merged, you can update the PR labels via:
$ for pr in 11912 12606 12640 12639 12704 12703; do contrib/backporting/set-labels.py $pr done 1.7; done

test-backport-1.7


whitelist ton.twitter.com

Please whitelist ton.twitter.com
This domain is required for sharing images in Twitter DMs
Also can you please enable 'Issues' on this git so people can report issues without needing a pull request thanks
Thanks

done


[REQUEST] Import all folder config files

Is your feature request related to a problem? Please describe.
I would like to have the option to import the entire folder of configuration files.  Example domains.
Describe the solution you'd like
routes = [
import("/opt/proksi/sites/*.hcl")
]
Describe alternatives you've considered
Additional context
Better and faster management.

Maybe something like this would be a good solution:
fn getImportedRoutes(file_data: str) -> &str {     let re = Regex::new("import\\(\"[^\"]*\"\\)").unwrap();     let mat = regex.find(file_data).unwrap().as_str();     let path = mat.split("\"").collect::<Vec<&str>>()[1];     //if it contains wildcard, grab all files with extension within that directory     if path.contains("*") {         let splitPath: Vec<&str> = path.split("*").collect();         let directory = splitPath[0];         let extension = splitPath[1];         /*             TODO: Iterate through directory and grab data from each file with the given extension and replace import         */         return path;     }     return path; }


A bug of Blank plots in workflow: Seurat V5 (with image) ->toSpatialFeatureExperiment -> plotSpatialFeature

Excellent work of your team in creating voyager!!! Thank you！
And I have to report a bug in using  toSpatialFeatureExperiment.
workflow: Seurat V5 (with image) ->toSpatialFeatureExperiment -> plotSpatialFeature
toSpatialFeatureExperiment function seurat delete the image info (should be placed in imgData) which result in blank plotSpatialFeature().
In your example, the image were not embedded in  example visium data, which resulting in failure of plotSpatialFeature() in data from seurat.
But the function of  read10xVisiumSFE from original data from space ranger outputs is totally no problem.
Could you help me to fix this? Or I should use addImg function after transformation?

Hi @huiyijiangling
Thanks!
Could you please show your code and sessionInfo(). I guess it is Visium data and not image-based ST like Xenium, since for those techs Seurat doesn't store any image.
Currently toSpatialFeatureExperiment from Seurat to SFE doesn't support adding images yet (that's something I have on todo list) since Seurat stores H&E Visium image differently.
You can try to add image manually addImg but coordinates of image or spot geometries would need to be flipped to match spots and corresponding image.


Output on Execute tab stuck

Hi. Excellent app here.
I have a problem. The output on the execute page is hung. Even after uninstalling and reinstalling.
The execute tab no longer processes the scripts and instead is fixed on a previous output.
Could it be because I had some html code in the code tab?

Thank you very much.
No. Your PC is failing to make the in built local server re-execute your code again. Any local server will have same issue. Its your PC problem not the app. If I can help find a way for you, I will update your issue.. Thanks.


Boosting performance: UDP Offloading and GSO

Hello, I've been instrumenting numerous QUIC implementations for performance testing.
In particular, I see [quiche] from CloudFlare implemented UDP offloading and GSO earlier this year. [link]
quic-go has given me 470.3 Mbps with loopback setting, so it seems to have no support for both accelerations yet. (I briefly looked up the code)
Would anyone confirm this for quic-go?
Maybe we could keep open this issue for future implementation, too.

Support for ReadBatch (which translates to sendmmsg) is being worked on in the batched-read branch.
I'm not sure if Go allows us to use GSO. Do you have any information about that? I'd be very interested in adding support for it in quic-go.

Thank you for the quick reply and reference.
Not that I'm aware of. Please, anybody, feel free to further the discussion.
I understand both are indispensable to achieve gigabps throughput.

https://godoc.org/github.com/google/netstack/tcpip/stack#GSO

@gedw99 Thanks for the link, that's very interesting. It's only for TCP though, isn't it?

Hi! GRO and GSO can be used in Go by setting appropriate socket options and then using ReadMsgUDP and WriteMsgUDP to get and specify segment size respectively. Feel free to use the following fragment as an example: https://github.com/nanokatze/quic-at-home/blob/main/internal/udp/gso_unix.go .

https://pkg.go.dev/github.com/tredeske/u/unet#Socket.SetOptGso

Maybe @tredeske can answer that?

This is an interesting discussion.
GSO allows sending of a large (up to 64k) datagram, to a single destination.  The datagram you send will be split into equal size actual datagrams by GSO.  The performance gain is from having a single, large datagram transit the network stack instead of a bunch of smaller ones.  It's a large gain in our experience.
http://vger.kernel.org/lpc_net2018_talks/willemdebruijn-lpc2018-udpgso-paper-DRAFT-1.pdf
For best performance, using sendmmsg (note extra m) will allow you to send multiple large datagrams with a single system call, each of which will be sent on the wire as multiple MTU sized datagrams.  Each large datagram can be sent to a different destination.  The performance gain using this is also quite large.
The variability using cmsghdr is not necessary for our application, but I can see how that would be useful.  The benchmark test for this interface shows how to do it in c.
https://github.com/torvalds/linux/blob/master/tools/testing/selftests/net/udpgso_bench_tx.c

@tredeske Thank you for chiming in here!

http://vger.kernel.org/lpc_net2018_talks/willemdebruijn-lpc2018-udpgso-paper-DRAFT-1.pdf

The link doesn't seem to work.

For best performance, using sendmmsg (note extra m) will allow you to send multiple large datagrams with a single system call, each of which will be sent on the wire as multiple MTU sized datagrams. Each large datagram can be sent to a different destination. The performance gain using this is also quite large.

Would you recommend combining these two? E.g. pass multiple (up to) 64k buffers to the kernel, if I'm sending to multiple remote addresses at the same time?

Just stumbled upon Tailscale's blog post from yesterday, which is excellent (as always): https://tailscale.com/blog/more-throughput/

The link doesn't seem to work.

Make sure that you're accesing it with http://

Huh.  I just clicked that link in your comment and it brought up the pdf.
Yes.  It's a big win.  it lets you send multiple frames of the same size (except possibly the last one) at once to each destination.  If you have variable sized frames, then in practice you may not be able to fill up to 64 kb in each element of the msghdr array.  Worst case, you can send two per element, as the last one in each can be a different size.

Looks like my Brave is aggressively upgrading HTTP to HTTPS, to the point where links fail. Sorry for the noise!
Now I'm trying to wrap my head around how I'd use that with the new Go API (#3563). API proposal here: https://github.com/golang/go/issues/45886#issuecomment-1218301564
If I understand correctly, I'd just pass up to UDPMsgs with 64k buffers to WriteUDPMsgs after setting the respective socket option. The cmsg that tells the kernel how large each UDP datagram (except the last one) will be would go in UDPMsg.Control.
Not sure I understand why UDPMsg.Buffer and UDPMsg.Control are [][]byte and not []byte though, it seems like we'll only ever set the first element of those slices.

I built a PoC, and it works! This is exciting! https://gist.github.com/marten-seemann/a549773b53f30960b966a9f4068b6e48
However, the Go standard library currently doesn't provide a function to serialize a Cmsghdr: https://github.com/golang/go/issues/59653. This is pretty much a requirement for us to actually use this syscall.

Would it be feasible to implement it for a subset of prominent architectures with a fallback to non-GSO sending?

Would it be feasible to implement it for a subset of prominent architectures with a fallback to non-GSO sending?

Probably. From looking at x/sys/unix, the main difference between architecture seems to be the size of the Len field (is it a uint32 or a uint64). One could look at unix.SizeofCmsghdr. If it's 12, then the length field is probably a uint32 (or int32?). If it's 16, it's a uint64 (or int64?). I haven't checked if this works for all architectures, but it seems to cover most of them.

@marten-seemann you could take a look at how wireguard-go is handling this.

I've been working on GSO support in the gso branch. Initial benchmarks look very promising, I'm seeing more than a doubling of the transfer speed on localhost, and that's without tuning of any parameters.
However, GSO support raises an interesting API question: Once GSO is enabled, calls to WriteTo on the original net.UDPConn will fail with a sendto: invalid argument error. The kernel requires us to set the UDP_SEGMENT cmsg with every sendmsg call (which is what WriteTo does). That's not a problem inside of quic-go (we can keep track of setting the sockopt and act accordingly), but users might want to multiplex other protocols on top of the same connection (e.g. STUN). QUIC is explicitly designed to allow such demultiplexing. The user however has no indication if setting the UDP_SEGMENT sockopt succeeded (and when!).
I'm wondering if we should make the API more explicit: Instead of doing interface assertions on the net.PacketConn set on the Transport, we could introduce an explicit way:
// OOBCapablePacketConn is a connection that allows the reading of ECN bits from the IP header.
// If the PacketConn passed to Dial or Listen satisfies this interface, quic-go will use it.
// In this case, ReadMsgUDP() will be used instead of ReadFrom() to read packets.
type OOBCapablePacketConn interface {
	net.PacketConn
	SyscallConn() (syscall.RawConn, error)
	ReadMsgUDP(b, oob []byte) (n, oobn, flags int, addr *net.UDPAddr, err error)
	WriteMsgUDP(b, oob []byte, addr *net.UDPAddr) (n, oobn int, err error)
}

// EnableOptimizations takes a connection and enables a range of optimizations that are crucial for QUIC performance.
// 1. increase UDP send and receive buffers
// 2. enable ECN support
// 3. enable GSO support
// 4. enable GRO support (in a future PR)
func EnableOptimizations(conn OOBCapablePacketConn) net.PacketConn {
    // crazy syscalls
}

If enabling GSO succeeds, the returned net.PacketConn would then wrap the WriteTo method, such that the UDP_SEGMENT message would be set.
quic-go users would need to call EnableOptimizations with the connection they're using for their QUIC server / client.
Does that make sense? Or is there a better solution?

@bt90 What are your thoughts on the suggested EnableOptimizations API here? Would that work for your case, assuming that at some point we'll have a callback / function on the Transport that allows you to retrieve the non-QUIC packets?

I believe it would, yes.


Services auto-restart even if it's set to never

v0.16.0
Steps:

Create an Environment
Add the Docker: hello-world as a service
Make sure Auto-Restart is set to never
Wait a few minutes
Check the logs

Results:
The service ran twice
Expected:
Service to only run once

This seems to happen to the first service you add to environment and can be seen better if you change scale to 6.  Then they will restart a few times.

Tani, could you retest on the latest? Restart policy should be set on the service containers now

This is still happening.  Although i don't think it's because of the restart policy.  For some reason, the containers in services will restart if they are automatically stopped until the Service is completely done starting.
Hello-world, just prints some data then stops.  If you have a high scale (like over 3 or 4), the first service container is created and stopped before the rest of the containers... it will then restart again until all containers are created and started.

@tfiduccia right, thats the recently added feature. Service containers management (stop/start/destroy) should be triggered by the service operation (scaleup/scaledown/deacivate). If the container is stopped/destroyed from the outside (either by stop api, or on the docker side), the service will reconcile the deployment by bringing up the containers to match the scale. Closing the issue for now.


bump terraform version

Increase the Terraform patch version.

Closing this since this folder is for Terraform 1.1.2.


"abstract" keyword not highlighted

The abstract keyword, when applied to both interfaces and derived types, is not properly highlighted.

Fixed in #42


select list disabled if form is open inside a tab

Entities -> Author List -> Select Author -> Author db relations -> Books -> Add
"Co Author" select box is disabled, form not working.

fixed
changed
'pack-angular/celerio/pack-angular/web/src/app/entities/entity-detail.component.html.e.vm'
'
<${relation.toEntity.model.var}-auto-complete [(ngModel)]="${entity.model.var}.${relation.to.var}" id="${relation.to.var}" name="${relation.to.var}" [disabled]="sub"></${relation.toEntity.model.var}-auto-complete>
'
to
''
<${relation.toEntity.model.var}-auto-complete [(ngModel)]="${entity.model.var}.${relation.to.var}" id="${relation.to.var}" name="${relation.to.var}" [disabled]="false"></${relation.toEntity.model.var}-auto-complete>
''


⚠ Account has degraded performance

In 3844cfc, Account (https://account.wrk.com/health) experienced degraded performance:

HTTP code: 200
Response time: 188 ms

Resolved: Account performance has improved in 4ce185f.


Adds scarfs to Secdrobe and hydrobe.

Thats it.

About the PR

I added 2 yml lines to give secdrobe and hydrobe scarfs.
Why / Balance

Because scarfs are very important to be warm and it adds to the fashion factor.
Technical details

It adds 2 lines of yml code
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

-add: Adds scarfs to SecDrobe And Hydrobe.

these are already in the winterdrobe

these are already in the winterdrobe

I mean yes, I just simply want it to be more convenient.


[HUDI-1396] Fix for preventing bootstrap datasource jobs from hanging

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
Bootstrap job via Hudi datasource hangs at the end of the spark-submit job.
This issue is similar to https://issues.apache.org/jira/browse/HUDI-1230. Basically, HoodieWriteClient at https://github.com/apache/hudi/blob/release-0.6.0/hudi-spark/src/main/scala/org/apache/hudi/HoodieSparkSqlWriter.scala#L255 will not be closed and as a result, the corresponding timeline server will not stop at the end. Therefore the job hangs and never exits.
Brief change log
Closed HoodieWriteClient after bootstrap action.
Added corresponding test cases.
Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[x] Has a corresponding JIRA in PR title & commit

[x] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #2253 (92c4a41) into master (430d4b4) will decrease coverage by 43.14%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master    #2253       +/-   ##
=============================================
- Coverage     53.54%   10.39%   -43.15%
+ Complexity     2770       48     -2722
=============================================
  Files           348       50      -298
  Lines         16109     1779    -14330
  Branches       1643      211     -1432
=============================================
- Hits           8626      185     -8441
+ Misses         6785     1581     -5204
+ Partials        698       13      -685

Flag
Coverage Δ
Complexity Δ

hudicli
?
?

hudiclient
100.00% <ø> (ø)
0.00 <ø> (ø)

hudicommon
?
?

hudihadoopmr
?
?

hudispark
?
?

huditimelineservice
?
?

hudiutilities
10.39% <ø> (-59.70%)
0.00 <ø> (ø)

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


File Upload broken?

File upload seems to be broken. Removing the timeout parameter allows the upload. Is this parameter still needed here?
/deploy/viur/core/modules/file.py", line 296, in initializeUpload
uploadUrl = blob.create_resumable_upload_session(content_type=mimeType, size=size, timeout=60)
TypeError: create_resumable_upload_session() got an unexpected keyword argument 'timeout'

Should be resolved by using the latest google-cloud-storage, or isn't it?

using latest (1.35.1) google-cloud-storage resolves this problem.


[Graphqlcache] The parent sometimes undefined field value in resolver

Hi,
urql version & exchanges: 1.10.0 & 3.0.2
const cache = cacheExchange({
  schema,
  resolvers: {
    Property: {
      slug(parent) {
        const {type} = parent;

        console.log({type, parent});

        return `${type.slug}-${parent.slug}`;
      },
    },
});

Check in the console.log:
type is undefined but the parent object contains type field value. 🤦
The log run many times, and the last time it's show correct data.
Final the resolver does not work well in any cases.
Additional. I'm using next and next-urql.

Hey,
Could you provide a reproduction? This is very limited in terms of information, it would speed up a potential fix a lot if we had the information.

I having created a reproduction https://codesandbox.io/s/holy-snowflake-xi2d9?file=/utils/urql.js.
Steps to reproduce:

Click About
Click Index
Click About
....

Btw: could it be that you're asking for the parent.type to be resolved after the other, this could be a reason. In GraphQL server the same occurs.

This should solve it

@JoviDeCroock Thanks for your answer, I'm clear my problem.


Missing exports

There are no export macros on JsonBox classes (something like JB_EXPORT?), it would be useful if the library is compiled as a dynamic library, or statically linked to a dynamic library.
(Currently, I have to statically compile the library with every module of my game engine, multiplying the binary size).

I'll look into it.

CMake's GenerateExportHeader module makes this pretty easy; three commands in the CMakeLists.txt (include the module, call the function, add the binary directory to include directories), then just include the export header in the relevant headers and add the ABI export decoration symbol in front of class names (and free functions, if any).

Sounds great... but I thought it would be even easier if there was an empty macro in front of exported classes (maybe not all have to be exported), and this macro could be user-defined. This way, anyone just has to set a value to this macro to have needed exports, without having to rely on anything but the C++ compiler.

I thought it would be even easier if there was an empty macro in front of exported classes (maybe not all have to be exported), and this macro could be user-defined.

No, really, it won't be. If you went this way, every Windows user would need to define that symbol twice; once to build JsonBox, and again in their own projects to be able to use it. With GenerateExportHeader, JsonBox adds a few lines of CMake, and users don't need to do anything. There's a reason that GenerateExportHeader is the accepted standard way to define export symbols.

Strange... I use libraries defining exports this way, doing this myself too and I never had any issues on Windows. I'm curious to learn the reason why a second definition of symbols would be needed (also, I use another build system, and compile JsonBox as static lib).

When you build a shared library on Windows, you MUST decorate anything exported with declspec(dllexport). Then, when you use the library, you MUST decorate anything imported with declspec(dllimport). Or, if it's static, you must omit any such decorations. If you just have 'an empty symbol that the user defines', then everyone using the library must define it to declspec(dllimport).
Good libraries will provide a header that correctly defines the ABI export symbol to the appropriate declspec based on a preprocessor symbol that is defined when the library itself is being built, so that everyone includes the One True Header, and everything Just Works™. GenerateExportHeader creates this header for you. (It's possible to create such a header "by hand"; I just wouldn't bother in any project that doesn't already have one, because using GenerateExportHeader is just much, much easier and makes it much easier to update the headers when things changes, e.g. adding or renaming libraries.)
Frankly, if I must add a compile definition when compiling my code in order to use your library, then your library is poorly designed. Unless I am misunderstanding something, this would be the case with your proposed "solution".
(If you ignore the build system that is provided with JsonBox, then, frankly, you have taken it on your own head to take care of all of this yourself.)

The part of my project that is used as a library has such header (maybe not as complete as what CMake would generate, I have to admit), and one of the libraries I use even has this "define your exports yourself as [some_macro]" thing. Not very convenient, but I set that macro as mine easily.
I try to unify the build system in my project as much as possible so it works out of the box. Unless I make JsonBox an "external" and introduce a dependency to CMake, I guess i'll have to take care of this myself then.
Thank you for explaining :)

Why is this closed? It's not fixed, is it?
I might look into this... how would folks feel about bumping the minimum CMake requirement to 2.8.12?

I am not good with CMake, thank your for the help. I just noticed the pull requests... My bad.

I don't mind bumping the minimum CMake requirement to 2.8.12, it was released a year and a half ago.

Since the default Makefile included, the default Xcode projects and the default Visual Studio 2010 are now broken because they cannot find the Export.h file, I guess I'll remove them.

Since the default Makefile included, the default Xcode projects and the default Visual Studio 2010 are now broken because they cannot find the Export.h file, I guess I'll remove them.

Heh :smile:... I am admittedly biased, but I've long been in favor of just using CMake rather than trying to maintain multiple build systems.
That said, if you wanted to keep them, you could add platform-specific Exports.h (or possibly a generic one; you'd have to write it yourself, however, as GenerateExportHeader generates non-generic ones that are only suitable for the build platform) and stick them in the source somewhere, and (as is done by #32) install the appropriate one alongside the other headers.
If you don't object to dropping the non-CMake builds, would you like for me to do that in #32?

Ah, never mind, I see you did this already :grin:.

First of all, thank you for you hatd word.
I don't know why the issue is still open, but when I used CMake to build the project to VS2015, it generated the Export.h file which I added to my project.


Enhancement: px-->rem unit for CSS Styling

@smaranjitghose I can see that all the styles follow px units are their measure which isn't a good practise. I propose to refactor the codebase to work on rem units rather than px units.
Note: Since there still is a lot of work going on other components in order to avoid any conflicts I would like to keep the refactored code into a different stylesheet or as you say it.

No need for this


sphobjinv-textconv

Is the PR a fix or a feature?
feature
Describe the changes in the PR
Adds entrypoint sphobjinv-textconv
Does this PR close any issues?
Closes #295
Does the PR change/update the following, if relevant?

azure-pipelines adjust coverage fail under reduced 100% --> 90%. Purposefully in a separate commit, for later easy adjustment via git rebase

No CHANGELOG entry. No adjustment to version

pyproject.toml reformatted by pre-commit

Unit tests. No integration test. Some fixtures added to conftest.py

Minimal adjustments to doc/conf.py to pass linkcheck.

# pragma: no cover used within the entrypoint, not for non soi-textconv modules. In non soi-textconv modules, using # pragma: no cover would return coverage to ~99%.

[*] Documentation

[*] Tests

[  ] CHANGELOG

Sorry for the delay here, needed to release #299 to make the package play nicer with Debian's build process, and then the holidays hit.
First thing -- your fork's main still isn't current with upstream, which might be the cause of the merge conflict:

It's possible you didn't push your updated main to your fork?

Dear Brian,
Was wondering why the commits/PR was taken out of chronological order. As long as there is a good reason.

First thing -- your fork's main still isn't current with upstream

Before a merge, since #299 occurred, so will have to rebase msftcangoblowm:textconvMight be able to just rebase msftcangoblowm:textconv and continue ignoring msftcangoblowm:main
msftcangoblowm/sphobjinv:textconvHave never done a serious rebase

It's possible you didn't push your updated main to your fork

That's most definitely the case and might not matter at all. What's important is your main. And keeping up to date with your main. That's what a rebase will solve.
Taken directly from the #301 PR merge page
[msftcangoblowm](https://github.com/msftcangoblowm) wants to merge 4 commits into [bskinn:main](https://github.com/bskinn/sphobjinv/tree/main) from [msftcangoblowm:textconv](https://github.com/msftcangoblowm/sphobjinv/tree/textconv)
Working in a branch is normal.
After the merge, can resync both msftcangoblowm:main and msftcangoblowm:textconv
Will do the rebase and message you (on mastodon) once that's done.
Dave
On Saturday, December 28th, 2024 at 5:41 AM, Brian Skinn @.***> wrote:

Sorry for the delay here, needed to release #299 to make the package play nicer with Debian's build process, and then the holidays hit.
First thing -- your fork's main still isn't current with upstream, which might be the cause of the merge conflict:
image.png (view on web)
It's possible you didn't push your updated main to your fork?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Cannot create new user?

Have tried using the default
env_settings_example.py as well as using my own env_settings.py, but they all cannot register new users?
Have been able to sign in using default admin and user:
Test users:

<EMAIL_ADDRESS>/ Password1
<EMAIL_ADDRESS>/ Password1

But cannot create new user:
<IP_ADDRESS> - - [07/Sep/2015 13:07:34] "GET /user/register HTTP/1.1" 200 -
<IP_ADDRESS> - - [07/Sep/2015 13:08:10] "POST /user/register HTTP/1.1" 500 -
Traceback (most recent call last):
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask/app.py", line 1836, in __call__
    return self.wsgi_app(environ, start_response)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask/app.py", line 1820, in wsgi_app
    response = self.make_response(self.handle_exception(e))
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask/app.py", line 1403, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask/app.py", line 1817, in wsgi_app
    response = self.full_dispatch_request()
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask/app.py", line 1477, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask/app.py", line 1381, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask/app.py", line 1475, in full_dispatch_request
    rv = self.dispatch_request()
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask/app.py", line 1461, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask_user/views.py", line 423, in register
    _send_registered_email(user, user_email, require_email_confirmation)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask_user/views.py", line 662, in _send_registered_email
    emails.send_registered_email(user, user_email, confirm_email_link)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask_user/emails.py", line 148, in send_registered_email
    user_manager.send_email_function(email, subject, html_message, text_message)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask_user/emails.py", line 49, in send_email
    mail_engine.send(message)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask_mail.py", line 491, in send
    with self.connect() as connection:
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask_mail.py", line 144, in __enter__
    self.host = self.configure_host()
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/site-packages/flask_mail.py", line 156, in configure_host
    host = smtplib.SMTP_SSL(self.mail.server, self.mail.port)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/smtplib.py", line 796, in __init__
    SMTP.__init__(self, host, port, local_hostname, timeout)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/smtplib.py", line 256, in __init__
    (code, msg) = self.connect(host, port)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/smtplib.py", line 316, in connect
    self.sock = self._get_socket(host, port, self.timeout)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/smtplib.py", line 801, in _get_socket
    new_socket = socket.create_connection((host, port), timeout)
  File "/home/osboxes/anaconda/envs/py27/lib/python2.7/socket.py", line 557, in create_connection
    for res in getaddrinfo(host, port, 0, SOCK_STREAM):
TypeError: getaddrinfo() argument 1 must be string or None
<IP_ADDRESS> - - [07/Sep/2015 13:08:10] "GET /user/register?__debugger__=yes&cmd=resource&f=style.css HTTP/1.1" 200 -
<IP_ADDRESS> - - [07/Sep/2015 13:08:10] "GET /user/register?__debugger__=yes&cmd=resource&f=jquery.js HTTP/1.1" 200 -
<IP_ADDRESS> - - [07/Sep/2015 13:08:10] "GET /user/register?__debugger__=yes&cmd=resource&f=debugger.js HTTP/1.1" 200 -
<IP_ADDRESS> - - [07/Sep/2015 13:08:10] "GET /user/register?__debugger__=yes&cmd=resource&f=console.png HTTP/1.1" 200 -
<IP_ADDRESS> - - [07/Sep/2015 13:08:10] "GET /user/register?__debugger__=yes&cmd=resource&f=source.png HTTP/1.1" 200 -

I'm having the exact same problem. Same error message:
TypeError: getaddrinfo() argument 1 must be string or None

Any idea what's going on with this or plans to fix it?

I found the solution to the problem!
So this system will attempt to email the users as they register. It's failing to email users because your env_settings_example.py isn't correct.
The env_settings_example.py is setting the MAIL_SERVER variable like this:
MAIL_SERVER = 'MAIL_SERVER', 'smtp.gmail.com'
When python uses the above MAIL_SERVER variable, it is coming in as a Tuple data type. This is causing the TypeError @Hendeca mentions above. The socket.getaddrinfo() function requires a String for the 1st argument (the 1st argument is the host; See Here
Try tweaking your env_settings so the mail server is in the format below. The variable should simply equal a string.
MAIL_USERNAME =<EMAIL_ADDRESS>MAIL_PASSWORD = 'gmailpassword'
MAIL_DEFAULT_SENDER = '"AppName"<EMAIL_ADDRESS>MAIL_SERVER = 'smtp.gmail.com'
MAIL_PORT = 465
MAIL_USE_SSL = True
MAIL_USE_TLS = False


Add appveyor support

There's a failure in Python 2.7 - see https://ci.appveyor.com/project/pfmoore/pep517/build/job/gq9h9qabohh03kt2
It looks like it might be something in the testpath library at first glance (the modified_env) decorator) although I can't immediately see what would be wrong there.

By the way - it looks like the travis config is relying on some preinstalled packages (I needed to add pytest and mock to get the tests to work). It might be worth adding an explicit dev-requirements.txt file, and/or instructions on how to run the tests. I'll do that in a follow-up PR once I get the Appveyor tests working.

I'm looking into it now. I wonder why it doesn't show up on Unix?

Maybe it's retrieving a path from somewhere which returns unicode on Windows and bytes on Linux, corresponding to the platforms' native path types?

OK, pytoml.load returns Unicode strings on Python 2.7. On Windows under Python 2.7, it looks like the env argument for subprocess.call requires str values (it calls CreateProcess under the hood, which is where the difference with Unix arises). I've just pushed what's hopefully a fix (that has more comment than actual code change - encoding issues are always messy to explain!)

I think the actual code change is OK, it's only the comment I'm quibbling with :-)

Thanks for the review. I'll actually change the code to use sys.getdefaultencoding() because while ASCII should be fine, the PEP technically doesn't specify encoding, it just says "letter" and I wouldn't want a horde of non-English speakers yelling at me about their letters ;-)

sys.getdefaultencoding() is also Python's default encoding, i.e. always ASCII for Python 2. If you want the locale encoding from the platform, I think that's locale.getpreferredencoding() (which, incidentally, is not threadsafe on all platforms).
However, since the build_backend refers to Python modules and objects, it has to be ASCII for Python 2 anyway, because Python 2 identifiers can't have non-ascii characters. So I'd just make it explicitly 'ascii'.

Bah, you're right. I'd forgotten how annoying Python 2's Unicode handling is...

:+1:

Thanks! I always like it when adding CI actually does pick up an issue to solve - makes it feel worthwhile :-)


Update Yasumi::create to allow for the instantiation of external holiday providers

I thought it was kind of silly that Yasumi can only load it's own holiday providers (using Yasumi::create), so I wrote this update that allows it to instantiate external ones.
External Holiday providers must be an instance of ProviderInterface.

Nice one! Could you perhaps provide/write an example how to use it? We can then use it in the documentation somewhere... :)


Provide a way for a different language to receive html language features

Hi, it would be great if there was a way for different HTML-like languages to receive HTML language features. Templating language extensions in the VS Code Marketplace could benefit from this.
Our use case:
We are working with a new HTML templating language with its own language config and TextMate grammar and would like to have the built-in HTML language features for the language. Features like auto indent, auto close tags, auto rename tags.
In our package.json we've created a new language called "Qute", for the Qute Templating Engine, with its own language config and grammar.
I don't think doing "files.associations": {"*.(our-extension)": "html"} in settings.json would help here because changing the file association would override the Qute grammar and language config.
Maybe there could be a way to register new HTML-like languages to the HTML language server?
Or is there a better way to handle this?
Thanks!

https://github.com/microsoft/vscode/issues/55088 seems like a solution.
Please feel free to close this issue

Hi @aeschli, it looks like the comment in https://github.com/microsoft/vscode/issues/55088#issuecomment-408031810 suggests forwarding requests by executing VS Code commands like vscode.executeCompletionItemProvider to get completion support, for example.
But what about html features like auto close tags and auto rename tags? The HTML LS accepts html.autoClosingTags and html.mirrorCursorOnMatchingTag to facilitate those features but I don't think it's possible to call specific requests to a specific LS using VS Code commands.
Would the solution here be to create our own LS that accepts autoClosingTags and mirrorCursorOnMatchingTag requests? To avoid redundancy, I think it would be ideal if I could communicate with the HTML LS instead.
Another solution would just be to add our language in this array: https://github.com/microsoft/vscode/blob/76d0b308ededd3a706d26fb1ccc564428248cd29/extensions/html-language-features/client/src/htmlMain.ts#L73
but because the Qute language is new, I understand if that's not favorable in general, to have random languages in the VS Code source code.

Yes, we want to make the full-html language (html + css + javascript) server more reusable
a. as a service like the current html-language-service, to be used as library by other language servers
b. as a new contrib point so html-like languages (e.g. html template languages) can provide a custom scanner and ask to be served by the html server  (and get added to the array that you were pointing to). The issue for that is https://github.com/microsoft/vscode/issues/49210
autoClosingTags and mirrorCursorOnMatchingTag would be made available in both approaches.
It is also planed to make  autoClosingTags and mirrorCursorOnMatchingTag language features for all (using regular provider). So they would be reusable like code completions.
If you have your own language server, I'd recommend for adding html as a service (a.) so you are self contained, avoid versioning issues and are able to give context to the HTML language service (e.g.) globals) gets as well as have more control over the user experience.
Approach (b) to enable a fast adoption of a template language where there is no language server. The capabilities added will be limited to inheriting HTML support.


Feature/bi 564

Archived Traits Table
Hey! Please take a look at how Vuex can be used and make any comments. The purpose of this PR is to make it easy to make comments and discuss specifics of how vuex could be used for biweb. This is not intended to be a final review before merging.
Required State Data
All traits in a program are pulled from the backend and stored locally. Filtering the existing all-traits collection for archived traits will not suffice because all-traits data stored is only one page of the collection, and the archived traits can be distributed over all pages.
An additional GET archived-traits endpoint could eliminate the need to store an entire collection on the frontend, but that doesn't exist, now.
The pagination and pagination controls state for the archive table must be independent of that of all other tables.
Vuex
Vuex modules for traits, archive, and pagination were added to the store with the hierarchy:
root --> traits --> archive --> pagination
             \
              \--> pagination

The all-traits collection is stored in the traits module; the archived-traits and paginated-archived-traits are stored in the archive module; and the pagination state and control data is stored in the respective pagination module, although only the archive controls are currently set up.
You can explore the state tree using the state tab on the chrome debugging tool Vue extension.  Also, you will see a history of mutations committed as well as a list of getters and mutations in each module.
Vuex-specific Component Changes
@/components/trait/TraitsArchiveTable.vue was necessarily created for the new table but also the SidePanelTable and child components were copied over into @/components/tables/ArchiveSidePanelTable.vue, @/components/tables/ArchiveBaseTable.vue, and @/components/tables/ArchivePaginationControls.vue. These last three files are temporary to hold the changes made to these child components in order to use Vuex for state management for the archive table.
The props and methods originally used for the all-traits table was ported into vuex module state, getters, mutations, and actions which are then added to an archive component using the vuex helper functions mapState, mapGetters, mapMutations, and mapActions.  State and getters are mapped to component computed values; mutations and actions are mapped to component methods.
For input forms like the page size selector box two-way data binding is not allowed since the store operates in strict mode. v-model is simply replaced with v-bind and the existing v-on:change.
The pagination event listeners don't need to bubble up from the ArchivePaginationControls to the TraitsArchiveTable component level so those have been removed from the top level.
Work in Progress
This branch is only supposed to illustrate how Vuex could be used to manage state on the front end as the UI gains in complexity in order to make any discussions and decision specific and meaningful. I only went as far as getting the pagination controls working, but Vuex would also need to manage the all-traits data and pagination as well as sidebar panel state information for the table to function property. For example, editing traits at the all-traits table will not affect the archived traits.
Also, the archived traits right now only return all traits since the filtering has been commented out since the new backend features supporting the active prop haven't been merged in yet.

@dmeidlin This is really helpful to see a working example in our codebase of Vuex, thank you!!  When a user navigates away from the archive table, then back to it later on, does the state get reset? Is the reset a responsibility of the Vuex module or of the component utilizing the Vuex module?
I see two different types of state that we currently have -> 1) system state like the user's auth info, and 2) page state, information needed for a specific page to load.  For the second type, what advantages does Vuex have over the state being held in the page component?

An additional GET archived-traits endpoint could eliminate the need to store an entire collection on the frontend, but that doesn't exist, now.

I think you should be able to use /programs/{programId}/traits/search to get the archived traits.

I see two different types of state that we currently have -> 1) system state like the user's auth info, and 2) page state, information needed for a specific page to load. For the second type, what advantages does Vuex have over the state being held in the page component?

Some additional thoughts, if we do the right side panel we could have whatever is loaded in that persist independently of the loaded page content potentially.

I see two different types of state that we currently have -> 1) system state like the user's auth info, and 2) page state, information needed for a specific page to load. For the second type, what advantages does Vuex have over the state being held in the page component?

The questions is how to handle communication in bi-web between components that must share access to component state data. This PR involves one type of scenario that already occurs in the app; the pagination controls component is deeply nested in the tree below the archive table component. In general, we will have the need also arise between sibling components or between grandchildren components on different roots as well. So we are talking about what to do when:
multiple sibling components use the same data; or
multiple roots need data access; or
there is deep nesting of components.
The goal is to avoid the clutter of having to pipe state data through intermediary components.
We are currently using Vue version 2.6.10.  In version 2 there were only two real ways to handle the component state access: an event bus or vuex.  Vue 3 has deprecated support for event busses:https://v3.vuejs.org/guide/migration/events-api.html#_3-x-update. So, going forward with event buses would require another approach after upgrading to the next major version of Vue.
Alternatively, Vue 3 enables inter-component access to state via Provide/Inject. This is fine for small apps but doesn't scale well since tracing where data was provided can be challenging with multiple devs contributing. It would also require us to upgrade to Vue 3.
Vue 3.0 was released in Sept. 2020.  All major versions of Vue support Vuex, so by using Vuex there is no need to change how we handle state management and inter-component communication when we eventually upgrade to the next major version. Also, there is no need to upgrade now in order to use alternatives that are only available in the latest major version.
In this example of the archive table with paginations controls using Vuex to manage state the pagination methods and event handlers are contained in the pagination component and module and the the archiveTable component and module contain the archive logic and data, with the namespace being passes as a prop to the pagination component and watches setup to describe how to respond to pagination control events. Intermediary components like the sidepanel table don't need to re-emit pagination events up to the archive table. So, it generally reduces the need to pipe through intermediaries and aids in encapsulating components better.
Mapping the state data and getters to computed values allows updates using Vue's reactive flow, which can make updates to components easier.
Also, the chrome vue extension makes it super easy to explore the state, view a history of mutations, list any getters in addition to the component tree and history of events fired. You can also reset the state to what it was when a mutation occurred, so it is really helpful for debugging and exploring new features. I'm sure you could do most of the same with IDE debugging features; it just is a convenience to have the plugin. But I think that also reflects the general high level of continued support for Vuex.
If component state data does not need to be shared then Vuex wouldn't be necessary, but the use of observables would be very useful.
Observables are available starting with Vue 2.6, and should be used for managing state needed within a single component:
https://vuejs.org/v2/api/#Vue-observable


CVAT new UI: Cancel or tune image shaking while drawing a polygon

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Expected Behaviour

An image mustn't shake while drawing any shapes.
Current Behaviour

The left mouse button uses to draw any object and to move an image. It leads to image shaking when we draw some objects, especially polygons.
Possible Solution

Create another mode to move an image while drawing an object. For example, it can be the mouse wheel or Ctrl+LMB
Steps to Reproduce (for bugs)

Just try to draw any polygon quickly enough

Context
It's very uncomfortable for the concentration and for the precisely annotation. Difficult to annotate objects' boundaries.

@TOsmanov , please confirm that the problem was resolved.

@nmanovic problem resolved.


Install Issue: Rails on localhost

Very good instructions to get this going but I am a Rails n00b, so I hope someone can help. Everything went well but I have one annoying issue. RoR bound to localhost rather than <IP_ADDRESS>.  I am not sure why.  When I try a curl from the local command line I can see stories running on http://localhost:3000 but not on http://<IP_ADDRESS>:3000
Anybody else run into this?
No work:
$ curl -I http://<IP_ADDRESS>:3000
HTTP/1.1 403 Forbidden
Server: nginx/1.8.1
Works:
$ curl -I http://localhost:3000
HTTP/1.1 200 OK
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Content-Type: text/html; charset=utf-8
Cache-Control: no-store, must-revalidate, private, max-age=0
Set-Cookie: request_method=HEAD; path=/
Set-Cookie: _stories_session=YURHN1FDaG41ZFo1bk1sWkpWNEtTQVp0VVVEMGVkVnhqMklETDR5MnBiZjBHLzkyek1wQ1ZGc0RhcXJQak00UnB5eEVoSzVwSStJelJFTnFpNGxZbWw3WGZhSmxhOUtBMkJyYTN1NzYya1pvS1pldHNZNi9qajloa1J1WDNtYjVIelVXdk0rNm1JM1phc3hUOFVHRHVBPT0tLXZuR0RVZzhUaUh0SkV2Mlo5dW90eFE9PQ%3D%3D--10f8b331fe6ded5d0f90f4ae314f7261bff62468; path=/; HttpOnly

Solved this by commenting a line in /etc/hosts:
#::1            localhost ip6-localhost ip6-loopback
Now my problem remains is how to reverse proxy port 3000 to 80 with nginx.  Possible for someone to share their nginx vhost config please?

Fixed.  I'll contribute my nginx config when I get a minute.
Software looks great, so glad this project is so far along.  I think it's really important stuff.  Well done Kenny!

Thanks!! Looking forward to the PR!!


Fixes #21 Replace webcomponents.js with webcomponents-lite.js

The webcompontents.js polyfill, used by the Chromecast framework,
interferes significantly with jQuery. Especially jQuery's patch to
consitantly bubble events across browsers. In addition,
webcomponents.js polyfills much more than is needed by the framework.
The polyfill comes in a "lite" version (webcomponents-lite.js). This
version of the polyfill polyfills registerElement, but not the shadow
DOM. With this polyfill our plugin will work without interfering with
jQuery. However, the <google-cast-button> custom element will not
work. Since we don't use this element, we have determined that this is
the least of all evils.
This commit changes our include of webcomponents.js in
preloadWebComponents to include webcomponents-lite.js instead.

back to you @onebytegone

@onebytegone Back to you again.

Back to you @onebytegone

Thanks @jimjenkins5!


Add MIT license for repository

Add MIT License to the repository

Closes #57

@devdattaT thank you! Theres one more https://github.com/datameet/maps/pull/58

@devdattaT thank you! Theres one more https://github.com/datameet/maps/pull/58

@planemad  I seem to have missed that. I have merged it.

@planemad  I seem to have missed that. I have merged it.


[magic-enum] Fails to configure because name is wrong

Currently, the package magic-enum installs correctly, but if you try to use it as suggested at install time:
The package magic-enum:x64-linux provides CMake targets:

    find_package(magic-enum CONFIG REQUIRED)
    target_link_libraries(main PRIVATE magic_enum::magic_enum)

It will fail as below:
  Could not find a package configuration file provided by "magic-enum" with
  any of the following names:

    magic-enumConfig.cmake
    magic-enum-config.cmake

  Add the installation prefix of "magic-enum" to CMAKE_PREFIX_PATH or set
  "magic-enum_DIR" to a directory containing one of the above files.  If
  "magic-enum" provides a separate development package or SDK, be sure it has
  been installed.
Call Stack (most recent call first):
  src/lib/CMakeLists.txt:54 (find_package)

The files are in fact not named that what it is expecting:
$ ls installed/x64-linux/share/magic-enum
copyright  magic_enumConfig.cmake  magic_enumConfigVersion.cmake  vcpkg_abi_info.txt

I have tried a few renames, but the only way I can get it to work is to rename the port from magic-enum to magic_enum again.  Is there a better way to do this?

Hi @geiseri thanks for posting this issue. I submitted a PR to fix this issue.
Could you help confirm if it can work for you?
Thanks.

@NancyLi1013 yes it works!

@geiseri the PR has been merged. Please update vcpkg and try to use it.
Thanks.


Could you share C++ version of Succinct?

Hi,
I recently read the Succinct paper. I think it would be a great tool for text analysis and want to explore more use cases with Succinct. I wonder if you could share the C++ implementation for the Succinct core, so I could do more experiments?
Thanks

Hi,
Thanks for your interest in Succinct! The C++ implementation of Succinct can be found here.


Remove tag related code

Changes Unknown when pulling 4cedae085f0cc0ef7ceec3107d3f0ffa2da31802 on remove-tag-related-code into ** on master**.


[BUG]: LEO NOT WORKING

When using brave leo in python tgpt it gives:-
I'm unable to answer your query as your version of Brave is too out of date. Please update your browser.
Desktop (please complete the following information):

OS [Android Termux]:
Architecture:- [armv7i]:
Python version [3.11]:

Also I have tried to took only a part of leo code and this is the json I found as a result after much debugging your code:-
{"completion":"I'm unable to answer your query as your version of Brave is too out of date. Please update your browser.","stop_reason":null,"truncated":false,"stop":null,"model":"llama-2-13b-chat","log_id":"cmpl-aG244Co4GSo2br8x9kJPzz","exception":null}

As it stands we can say LEO is no longer supported. This obeys its provider's request to do so.
Refer to https://github.com/aandrew-me/tgpt/issues/199#issuecomment-1907808474


fixfix fs specifics, broker and tvf params

Proposed changes
fix fs specifics, broker and tvf params, and NPE

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 44.91 seconds
stream load tsv:          554 seconds loaded<PHONE_NUMBER>9 Bytes, about 128 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
insert into select:          29.3 seconds inserted 10000000 Rows, about 341K ops/s
storage size:<PHONE_NUMBER>2 Bytes

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 45.12 seconds
stream load tsv:          554 seconds loaded<PHONE_NUMBER>9 Bytes, about 128 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.3 seconds inserted 10000000 Rows, about 341K ops/s
storage size:<PHONE_NUMBER>4 Bytes

run external


Bug fix: test_time_pool would be set to a non-False value

If args.no_test_pool is False but apply_test_time_pool() returns False because test-time pooling is not available, then the local variable test_time_pool would not be set to True or False but to a copy of the model. In turn, this would cause the crop_pct to be set to 1.0 further down in the code. This bug causes the results from validate.py to be slightly different from the validation score shown during training due to the different crop rectangle (unless training happened to use crop_pct = 1.0, of course).
Also possibly the cause of this issue: https://github.com/rwightman/pytorch-image-models/issues/235

@hollance thanks, not related to #235 because this change is quite recent but an issue none the less.


Helm ignores %KUBECONFIG%

helm is ignoring my KUBECONFIG setting and trying to read from my %HOMEDRIVE%, which is not where my config is located.
C:\Users\rmorrise>echo %KUBECONFIG%
C:\Users\rmorrise\.kube\config

Output of helm version:
Client: &version.Version{SemVer:"v2.14.3", GitCommit:"0e7f3b6637f7af8fcfddb3d2941fcc7cbebb0085", GitTreeState:"clean"}
Error: could not get Kubernetes config for context "": open X:\/.kube/config: Access is denied.

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:36:53Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.6", GitCommit:"96fac5cd13a5dc064f7d9f4f23030a6aeface6cc", GitTreeState:"clean", BuildDate:"2019-08-19T11:05:16Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.): Docker Desktop for Windows (win 10 x64)

Same issue exists with helm v2.15.0-rc.2

Some additional steps that I've tried...
C:\Users\rmorrise>kubectl config current-context
docker-desktop

C:\Users\rmorrise>helm --kubeconfig "C:\Users\rmorrise\.kube\config" init --upgrade
$HELM_HOME has been configured at C:\Users\rmorrise\.helm.
Error: could not get kubernetes client: could not get Kubernetes config for context "": open X:\/.kube/config: Access is denied.

Can confirm the behaviour for windows systems.
Strangely it works fine for PowerShell @ Mac.

Have you tried a more recent version of Helm 2?
Gentle reminder that the support window for bugfixes closes in a month. If nobody works on fixing this, we'll have to close this out and consider this as Helm 2's intended behaviour.

We are no longer accepting bug fixes for Helm 2. See https://helm.sh/blog/helm-v2-deprecation-timeline/ for more details.


Dependency conflicts

CDK deployment fails with the following error:
...
#7 11.32 INFO: pip is looking at multiple versions of langchain to determine which version is compatible with other requirements. This could take a while.
#7 11.47 ERROR: Cannot install -r requirements.txt (line 38) and langsmith==0.0.14 because these package versions have conflicting dependencies.
#7 11.47
#7 11.47 The conflict is caused by:
#7 11.47     The user requested langsmith==0.0.14
#7 11.47     langchain 0.1.11 depends on langsmith<0.2.0 and >=0.1.17
#7 11.47
#7 11.47 To fix this you could try to:
#7 11.47 1. loosen the range of package versions you've specified
#7 11.47 2. remove package versions to allow pip attempt to solve the dependency conflict
#7 11.47
#7 11.47 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
...

Using the latest langchain, langsmith and langchainplus-sdk in requirements.txt fixed this error for me.
langchain
langchainplus-sdk
langsmith

As @jsmey says, you have to look for this elements:
langchain==0.1.11
langchainplus-sdk==0.0.17
langsmith==0.0.14
in the requirements.txt files under "handler-claude-agent", "handler-claude-simple" and "handler-claude-websocket" directories and replace them with:
langchain
langchainplus-sdk
langsmith
so the pip install process can deal with package dependencies by installing latest versions.


docs(progress-steps): progress steps component RFC

Thanks for knocking this out!!
How do you see this supporting the last case, would additional internal items just be children of Step?

@abmai I was thinking those would be just children of a Step. Do you think we should rather define these type of children through the props or maybe just provide additional styled components like StyledStepSubtitle, StyledStepAction?

@abmai I was thinking those would be just children of a Step. Do you think we should rather define these type of children through the props or maybe just provide additional styled components like StyledStepSubtitle, StyledStepAction?

I think providing more styled components is nice, maybe not the action since it's just a button but <StyledStepSubtitle> and <StyledStepText> would be good to have. What do you think?

Added the two mentioned to the exports list ^


Add missing space between words

And add required semicolon at end of example t-sql commands

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

Hi @lowlyDBA, thank you so much for your contribution and for making our docs better :) #sign-off


Minor improvements and wider file support

I was using this app "for real" today (meaning I was parsing real chats and not just tests) and I found a few flaws and also got a few ideas for improvements, so I implemented them.
Changes:

When the input prompts are displayed, they already contain the current values
The name of the output file is the same as the name of the input file (apart from the extension) - this makes it possible to convert multiple files after each other without making a mess in the "Downloads" folder
The download button now hides again, while the next file is being processed (so the user doesn't accidentally download the previous output)
Many new file extensions of media files are now supported (this includes e. g. the format used for stickers)
Non-media files are now supported too - here is how it looks like in the output:

There are a few other things that I might want to change (such as choosing the name of user whose messages will be darker), but it can wait. Maybe I make time for that somewhen.

Oh, I almost forgot. The file icons are dynamically downloaded from this repository. It's under the MIT licence, so there shouldn't be any problems because of that.

Great additions @HonzaSTECH, I'm happy you're using this for real!
And also I'm happy the refactoring I made was useful, doing this with the old code structure would be a real mess, thanks for your contribution I'm happy to merge this :))


Atom stopped open plots in Julia

Hello!
I’m using Julia and Atom for it, operation system Linux Mint. This morning I pressed “update” button in Atom and typed “] update” in Julia terminal.
So that is all, program is calculating right numbers, but Atom ignores plotting commands. No warnings, no information. REPL behaves exactly like everything is plotting.
Also plotting in Julia terminal still works. So it should be some problems with Juno and Atom I suppose
This warning emerges only if I try to recompile Julia:
[ Info: Precompiling Atom [c52e3926-4ff0-5f6e-af25-54175e0327b1] WARNING: Method definition displayable(Atom.JunoDisplay, Base.MIME{Symbol("application/prs.juno.jlpane")}) in module Atom at /home/mikhail/.julia/packages/Atom/v2iqN/src/display/showdisplay.jl:92 overwritten at /home/mikhail/.julia/packages/Atom/v2iqN/src/display/showdisplay.jl:94. WARNING: could not import Base.endof into StringDistances

Thanks for contributing @MMalakhov. It looks like this is a specific issue with the Juno package -- I would recommend looking through their troubleshooting steps to try and resolve this issue. If you continue to have problems you can post in the Juno discussion board or issue tracker for further help.


[1.1] [FanControl] set FanMode to Auto, value of PercentSetting is 0xFF

Reproduction steps

set FanMode Attribute on FanControl Cluster to Auto(0x05)

FanMode was set to Auto, then void MatterFanControlClusterServerAttributeChangedCallback(const app::ConcreteAttributePath & attributePath) set PercentSetting to NULL.
However,
void MatterPostAttributeChangeCallback(const chip::app::ConcreteAttributePath & attributePath, uint8_t type, uint16_t size, uint8_t * value) *value is 0xFF.
As my understanding, *value should be 0x00.
How do I resolve it?
Bug prevalence
always
GitHub hash of the SDK that was being used
commit 8f66f4215bc0708efc8cc73bda80620e67d8955f (HEAD, tag: v<IP_ADDRESS>)
Platform
core
Platform Version(s)
No response
Type
Common Cluster Logic
Anything else?
No response

@mmt-10 The representation of spec "null" for an 8-bit unsigned integer/enum value in MatterPostAttributeChangeCallback is 0xFF.
"null" does not mean "0"; it means "not a value".  The spec reserves some value space of this purpose, note: 0xFF is not a valid value for a nullable enum8 or uint8 or anything derived from them.

@bzbarsky-apple
Thank you for your reply.
I understand it.
When I read PercentSetting after FanMode was set Auto, PercentSetting is 0.
However, MatterPostAttributeChangeCallback is 0xFF.
So, I confused.

When I read PercentSetting after FanMode was set Auto, PercentSetting is 0.

That is strange...  How are you reading it, exactly?


About checkpoint

Hello, Can you please share the checkpoint folder with us? which could save lots of time for people. It will be greatly appreciated.
Thanks.

the checkpoints have been uploaded to Google Drive


Automatic scroll up

SQL Operations Studio Version: 0.31.4

From one day to the other, every time I change of tabs and then return to any of them, the query  automatically scrolled up to beginning. How can I disable this? I want to go back to my query and be in the same line where I left it

This is a bug and unfortunately I don't think there's a workaround for it. We're tracking it in #114 so I'll close this one as a duplicate


Fix a document issue

The issue is here https://github.com/deepjavalibrary/djl/issues/2107

Codecov Report
Base: 72.08% // Head: 71.40% // Decreases project coverage by -0.68% :warning:

Coverage data is based on head (548ad89) compared to base (bb5073f).
Patch coverage: 71.66% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2114      +/-   ##
============================================
- Coverage     72.08%   71.40%   -0.69%
- Complexity     5126     6285    +1159
============================================
  Files           473      624     +151
  Lines         21970    27811    +5841
  Branches       2351     2998     +647
============================================
+ Hits          15838    19858    +4020
- Misses         4925     6493    +1568
- Partials       1207     1460     +253

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...rc/main/java/ai/djl/modality/cv/MultiBoxPrior.java
76.00% <ø> (ø)

...rc/main/java/ai/djl/modality/cv/output/Joints.java
71.42% <ø> (ø)

.../main/java/ai/djl/modality/cv/output/Landmark.java
100.00% <ø> (ø)

...main/java/ai/djl/modality/cv/output/Rectangle.java
72.41% <0.00%> (ø)

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <0.00%> (-5.24%)
:arrow_down:

.../modality/cv/translator/ImageFeatureExtractor.java
0.00% <0.00%> (ø)

.../ai/djl/modality/cv/translator/YoloTranslator.java
27.77% <0.00%> (+18.95%)
:arrow_up:

...modality/cv/translator/wrapper/FileTranslator.java
44.44% <ø> (ø)

...y/cv/translator/wrapper/InputStreamTranslator.java
44.44% <ø> (ø)

... and 557 more

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

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


Logical operators return incorrect results when used on forgiving expressions.

Version: 1.4.0-rc.2
Given the following statements:

scope.$eval("true && does.not.exist");
scope.$eval("true && !does.not.exist");

Both return true, as long as does.not is not an object on the current scope.
However scope.$eval("true && doesnotexist"); and scope.$eval("true && undefined"); both return false as expected as long as doesnotexist is not a truthy value on the current scope.
This makes me think it has something to do with using scope.$parse as it only occurs when attempting to access nested properties of undefined values on the scope which scope.$parse suppresses errors for.
For this reason any directive such as ng-if and ng-switch. For examples see: http://jsbin.com/pesatiloku/1/edit?html,js,output

Another example: scope.$eval("true && doesnotexist()"); returns true.
I guess that in general this weird behaviour happens when using boolean operators on the results of "forgiving" expressions. But nothing in the docs about forgiving expressions suggests that this behaviour should occur, and it's bizarre; it's a violation of the simple mental model of "calling undefined as a function or accessing properties of undefined returns undefined" that the docs give us.
Of course, any fix to this will be a breaking change, but it seems like a clear bug.

The issues originally posted are fixed as part of d19504a179355d7801d59a8db0285a1322e04601 the other is a real issue. Should have a patch soon

@lgalfaso are you sure the first issue has been fixed? In the jsbin, the first ng-if for 'AND' should evaluate to undefined, i.e. be not visible. This doesn't work with the snapshot, but it does work in 1.3.16

Mmm.. @Narretz you are right, updated the PR to fix

true && a.b.c
true && a()
true && a()()
false || a.b.c
false || a()
false || a()()

where a == null
These are all small variations of the same issue, hopefully this should fix all the variations

@lgalfaso just a note - although @georeith gave the example of true && a.b.c, the same bug occurs for just true && a.b if a is null. I notice that your commit message refers to the a.b.c form but not the a.b form; I don't know whether you've in fact fixed both.

@ExplodingCabbage they are all fixed, in fact we have tests for

true && a
true && a()
true && a()()
true && a.b
true && a.b.c
false || a
false || a()
false || a()()
false || a.b
false || a.b.c


function to identify tsv harmonization need

For each matching column in two dataframes (datasets from different or comparable):

Using numpy.polyfit() on both dataframe columns see if polynomials are close
calculate 'spread' on polynomials
create data on distributions
return information on if polynomials and spread are matched
return data on distribution

This is a research question no longer a simple code issue- broken into issues, therefore close


[Feature Request] hover local graph of current file

[x] add hover local graph command
[x] hover local graph setting tab
[x] update document

closed by #14


Popover nested in Dialog does not open

Bug report
Current Behavior
Slightly complicated, but..

A Popover who's trigger renders differently based on open state
and uses a Portal
and is rendered in a Dialog

Does not open when the trigger is clicked. In my minimal reproduction case it only doesn't open on the first click, but in our production application it doesn't open at all. This happens because onOpenChange is being called twice in quick succession.
Expected behavior
The popover should open
Reproducible example
https://codesandbox.io/s/sad-darwin-rvpy1o?file=/src/App.tsx
Suggested solution
Not sure, but it looks possibly introduced by https://github.com/radix-ui/primitives/commit/568fdc5927d91b50acb106a4931d8e865639de53. 🤷
Additional context
We recently saw this behaviour when bumping radix-ui versions, specifically popover from ^1.0.5 to ^1.0.6.
Your environment

Software
Name(s)
Version

Radix Package(s)
popover
1.0.6

React
n/a
18.2.0

Browser
chrome
latest

Assistive tech
n/a
n/a

Node
n/a
16.15.1

npm/yarn
yarn
3.5.1

Operating System
macos
13.4

The issue in our app seems to have been caused by the mutationObserver here. I was able to achieve the expected behavior by reverting it locally.


bump develop version

Closing this in favor of https://github.com/data-integrations/google-cloud/pull/112


[Design] - Redesign Manager Dashboard

Design Goal
Please describe the ask.
In order to better accommodate the new job poster builder, we want to modify the flow in which a job poster is submitted once complete. Alongside this, we want to enhance the manager dashboard to better indicate the priority action for the job poster based on its current state.
Related Features:

Job Poster Builder

Related Issues:

Issue #1722

Notes
Elements of the job action on the dashboard:

job status

draft
in review
approved
published
closed
complete

action required indicator
job title
classification
timer
number of applicants (specific to published, closed, and complete statuses)
primary action button

edit job poster (specific to draft)
preview and submit poster (specific to in review)
edit screening plan (specific to approved, published)
view applicants (specific to closed)
*complete jobs have no primary action

secondary action buttons

edit job poster (active for draft, in review)
view preview / poster (active for draft, in review, approved, published, closed, complete)
edit screening plan (active for draft, in review, approved, published)
view applicants (active for closed)
delete poster (active for draft, in review, approved)

Wireframes
Prototype Link: TBD

Please also take into consideration a long term plan for a complete overview of a process and its sections. For consideration, take a look at prototype for some ideas: https://xd.adobe.com/view/3d2cfadf-d5ed-46f8-4f5f-94a6df0b7e14-4b1d/?fullscreen

Yes, but also no, because this is something we're building long before any of that other stuff. It will 100% need to be modified afterwards, but as long as some of that is wishy washy, I don't want it to dictate things too too much. I'll take a peek and see if anything directly impacts the existing information.

I mentioned to Josh that "in review" and "draft" are kinda meshed together right now, and he seems to have a plan for it. The question is whether the primary action is "edit" or "preview and submit". We prefer "edit" but will need to test to see if real managers can find the publish button at the bottom of the "review" page on the job poster builder.
And I'm with Josh, I think the work you put forward Jerbo is too far in the future to plan towards right now.


send emails when people are removed/added

when an owner is added/removed, the archive should send an email to the everyone involved in that transaction.

Emails seem to be working nicely.


Add tests and fixes for AWS helpers

In #1, I had test for everything but the two AWS bash scripts, as those are tricky to unit test. I started to use those scripts in another project, and, not too surprisingly, hit a bug.
So, I bit the bullet, and figured out how to unit test these suckers using moto, a mock EC2 metadata server, and some other hacks. It was a PITA, that included some yak shaving around bats, but the upside is I actually found and fixed several bugs, so I guess it was worth the effort.

Merging now. Please take a look, as there are some handy patterns here for mocking out EC2 metadata, AWS APIs, overriding AWS CLI behavior, etc. Feedback welcome!


Ability to turn searchOnEnterKeyPressOnly off or on for searchbox widget

It will be great to be able to target this option through javascript to turn it off or on.
Our use case is we want to turn this off or on depending on when certain events are triggered.

Hi @urbanitedesign, it is currently not possible to update options after initialisation, we might provide this in the future.
In the meantime the easiest way is to instantiate two searchBox widget and hide/show them when you want.
This should work pretty well and still be performant.
Let met know

Yes I was told that it wasn't possible just yet, but would definitely be useful if you could.
I will give the 2 search boxes a go, nice idea hadn't thought of that. Thanks!

Ok, reopen the issue if that fails, I take good note of the "be able to update options dynamically", it's a recurring need.


Small devices graphics error

57 pixel bottom overflow on short device - obscuring some of the user interface
Kind of would make more sense to pop this over the bottom tab bar, perhaps? Not sure.

Another one