Module input name update - Affects recent SDXL modules

In my local version and the SDXL support PR to facebookincubator/AITemplate I renamed inputs from inputN.
All modules will be recompiled soon, this will include the new naming scheme, and enable 8px increment. Suggestions on resolutions, batch sizes etc that should be supported are welcome, and could be shared here or in a separate issue.
Name changes are described below and need to be applied in AITemplate/ait/inference.py.
To use the recent SDXL modules, I would recommend applying only the UNet changes and using the existing VAE modules, as the changes are less involved. Note that the changes will then be incompatible with existing UNet modules for v1 and v2.
Depending on how long compiling a new set takes, and how long adoption of new modules would take, it may be advantageous to implement some sort of compatibility check, the module has capability of returning the input and output name to index maps, I'll leave this open to comment, SM70/SM75 may take longer to replace although I'm not sure of their popularity.
UNet

input0 -> latent_model_input
input1 -> timesteps
input2 -> encoder_hidden_states
input3 -> class_labels (unused by this plugin)

VAE

vae_input -> pixels when encode, latent when decode
vae_sample -> random_sample, only used by encode

Note: module selection for VAE uses v1, meaning the recent VAE modules labelled with sd: xl will not be used, the main difference between the recent and existing is logging, they will still work.
CLIP
Unused by this plugin, but it's input0 -> input_ids and input1 to position_ids

After renaming these suggested names, I get this error:
Found 3 modules for linux xl sm80 1 1024 unet
Using b5caabe98aeb69bada9d1566c897aed66a84d4fb21f31482160d7ef9987f04fd
  0%|                                                                                | 0/20 [00:00<?, ?it/s]Got cutlass error: Error InternalError: Got cutlass error: Error Internal
  0%|                                                                                | 0/20 [00:00<?, ?it/s]
!!! Exception during processing !!!
Traceback (most recent call last):
  File "/home/cybertimon/Repositories/ComfyUI/execution.py", line 151, in recursive_execute
    output_data, output_ui = get_output_data(obj, input_data_all)
  File "/home/cybertimon/Repositories/ComfyUI/execution.py", line 81, in get_output_data
    return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
  File "/home/cybertimon/Repositories/ComfyUI/execution.py", line 74, in map_node_over_list
    results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
  File "/home/cybertimon/Repositories/ComfyUI/nodes.py", line 1206, in sample
    return common_ksampler(model, seed, steps, cfg, sampler_name, scheduler, positive, negative, latent_image, denoise=denoise)
  File "/home/cybertimon/Repositories/ComfyUI/custom_nodes/AIT/AITemplate/AITemplate.py", line 170, in common_ksampler
    samples = comfy.sample.sample(model, noise, steps, cfg, sampler_name, scheduler, positive, negative, latent_image,
  File "/home/cybertimon/Repositories/ComfyUI/custom_nodes/AIT/AITemplate/AITemplate.py", line 304, in sample
    samples = sampler.sample(noise, positive_copy, negative_copy, cfg=cfg, latent_image=latent_image, start_step=start_step, last_step=last_step, force_full_denoise=force_full_denoise, denoise_mask=noise_mask, sigmas=sigmas, callback=callback, disable_pbar=disable_pbar, seed=seed)
  File "/home/cybertimon/Repositories/ComfyUI/comfy/samplers.py", line 716, in sample
    samples = getattr(k_diffusion_sampling, "sample_{}".format(self.sampler))(self.model_k, noise, sigmas, extra_args=extra_args, callback=k_callback, disable=disable_pbar)
  File "/home/cybertimon/.local/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/cybertimon/Repositories/ComfyUI/comfy/k_diffusion/sampling.py", line 137, in sample_euler
    denoised = model(x, sigma_hat * s_in, **extra_args)
  File "/home/cybertimon/.local/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/cybertimon/Repositories/ComfyUI/comfy/samplers.py", line 319, in forward
    out = self.inner_model(x, sigma, cond=cond, uncond=uncond, cond_scale=cond_scale, cond_concat=cond_concat, model_options=model_options, seed=seed)
  File "/home/cybertimon/.local/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/cybertimon/Repositories/ComfyUI/comfy/k_diffusion/external.py", line 125, in forward
    eps = self.get_eps(input * c_in, self.sigma_to_t(sigma), **kwargs)
  File "/home/cybertimon/Repositories/ComfyUI/comfy/k_diffusion/external.py", line 151, in get_eps
    return self.inner_model.apply_model(*args, **kwargs)
  File "/home/cybertimon/Repositories/ComfyUI/comfy/samplers.py", line 307, in apply_model
    out = sampling_function(self.inner_model.apply_model, x, timestep, uncond, cond, cond_scale, cond_concat, model_options=model_options, seed=seed)
  File "/home/cybertimon/Repositories/ComfyUI/comfy/samplers.py", line 285, in sampling_function
    cond, uncond = calc_cond_uncond_batch(model_function, cond, uncond, x, timestep, max_total_area, cond_concat, model_options)
  File "/home/cybertimon/Repositories/ComfyUI/comfy/samplers.py", line 262, in calc_cond_uncond_batch
    output = model_function(input_x, timestep_, **c).chunk(batch_chunks)
  File "/home/cybertimon/Repositories/ComfyUI/custom_nodes/AIT/AITemplate/ait/inference.py", line 43, in apply_model
    return unet_inference(
  File "/home/cybertimon/Repositories/ComfyUI/custom_nodes/AIT/AITemplate/ait/inference.py", line 98, in unet_inference
    exe_module.run_with_tensors(inputs, ys, graph_mode=False)
  File "/home/cybertimon/Repositories/ComfyUI/custom_nodes/AIT/AITemplate/ait/module/model.py", line 565, in run_with_tensors
    outputs_ait = self.run(
  File "/home/cybertimon/Repositories/ComfyUI/custom_nodes/AIT/AITemplate/ait/module/model.py", line 468, in run
    return self._run_impl(
  File "/home/cybertimon/Repositories/ComfyUI/custom_nodes/AIT/AITemplate/ait/module/model.py", line 407, in _run_impl
    self.DLL.AITemplateModelContainerRun(
  File "/home/cybertimon/Repositories/ComfyUI/custom_nodes/AIT/AITemplate/ait/module/model.py", line 211, in _wrapped_func
    raise RuntimeError(f"Error in function: {method.__name__}")
RuntimeError: Error in function: AITemplateModelContainerRun

Maybe we should delete the AIT extension and reinstall it. Then you could make a step by step tutorial what changes needs to be done to get it to work with SDXL. Only if you have time of course.

Yes there appears to be an issue with the Linux modules. Linux users will need to compile their own or try Windows until I have time to look into the issue. To note it is known that modules compiled on one distro may not work on another.

ohh so I have to compile them on my buggy env 😆

The strange part is that the other user on windows has the same input0 issue which I think is not related to the model. The SD 1.5 linux unet models work by the way on my system so I don't see a issue why it shouldn't work.

input0 -> latent_model_input
input1 -> timesteps
input2 -> encoder_hidden_states
input3 -> class_labels (unused by this plugin)

I don't really understand this. the lines you mentioned have: "input0": latent_model_input.permute((0, 2, 3, 1)) which I think is what you said is necessary..?

I'm not sure what is unclear, the current name on the line linked is to be changed to the new name
Current name -> New name
That section is regarding UNet, it says input0 is renamed to latent_model_input, input1 is renamed to timesteps, input2 is renamed to encoder_hidden_states and you can safely ignore input3.
The new modules use the new name, to use them the input names in the code need to match the names used by the module.
This is described in the initial post.

I'm not sure what is unclear, the current name on the line linked is to be changed to the new name Current name -> New name That section is regarding UNet, it says input0 is renamed to latent_model_input, input1 is renamed to timesteps, input2 is renamed to encoder_hidden_states and you can safely ignore input3. The new modules use the new name, to use them the input names in the code need to match the names used by the module. This is described in the initial post.

did that, now it does: ValueError: Did not get correct number of inputs expected 4, got 3

okay, now it does the first stage perfectly with the speed boost, but when starting second stage it says in the terminal: [20:42:19]: NVIDIA GeForce RTX 4070 Ti [20:42:19]: AITemplate modules compiled by hlky [20:42:20]: Error: SetConstant did not receive correct number of bytes for unbound constant time_embedding_linear_1_weight: expected 819200 but got 1179648. Check that the provided tensor's shape is correct. @hlky

I can't say for certain due to the limited information provided regarding the second stage, however the time_embedding_linear_1_weight is part of UNet, its size is determined block_out_channels, as the error states it got a larger size than expected I believe you are attempting to use XL refiner, which is a different architecture to the base model and therefore incompatible with the modules you are using. You can compile modules for refiner yourself, or await precompiled modules being provided.

I can't say for certain due to the limited information provided regarding the second stage, however the time_embedding_linear_1_weight is part of UNet, its size is determined block_out_channels, as the error states it got a larger size than expected I believe you are attempting to use XL refiner, which is a different architecture to the base model and therefore incompatible with the modules you are using. You can compile modules for refiner yourself, or await precompiled modules being provided.

oh gotcha. for some reason I can't compile them myself, so I'll wait

I can't say for certain due to the limited information provided regarding the second stage, however the time_embedding_linear_1_weight is part of UNet, its size is determined block_out_channels, as the error states it got a larger size than expected I believe you are attempting to use XL refiner, which is a different architecture to the base model and therefore incompatible with the modules you are using. You can compile modules for refiner yourself, or await precompiled modules being provided.

are you sure it's a different architecture? I thought modules.json just didn't specify the refiner modules

xl-base
xl-refiner
It is a different architecture. Refiner modules will be available soon.

No change required, just use --hf-hub-or-path stabilityai/stable-diffusion-xl-refiner-1.0 instead of --hf-hub-or-path stabilityai/stable-diffusion-xl-base-1.0.

is this with the built AIT dir you linked yesterday? if yes what is the directory I should run this?

Please refer to the documentation and comments on related issues for compilation instructions. Precompiled refiner modules will be available soon, please be patient.

Closing this as #19 is nearing completion.


Next.js app uses previous commit

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d2hbdzl31vlu96
AWS Region
us-east-1
Amplify Hosting feature
Frontend builds
Describe the bug
When my app is updating, the previous code is still being deployed and not the latest. I have confirmed this by including the version number from package.json in NEXT_DATA. The only symptom I can find that indicates where the issue may be occurring is in the following warning during the Cloning Repository phase of the build:
2022-11-21T19:09:17.980Z [INFO]: # Cloning repository: git@github.com:[removed]/[removed].git
2022-11-21T19:09:20.414Z [INFO]:
2022-11-21T19:09:20.416Z [INFO]: Cloning into 'removed'...
2022-11-21T19:09:20.416Z [INFO]: # Checking for Git submodules at: /codebuild/output/src132231801/src/[removed]/.gitmodules
2022-11-21T19:09:20.426Z [INFO]: # Retrieving environment cache...
2022-11-21T19:09:20.491Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}
2022-11-21T19:09:20.491Z [INFO]: ---- Setting Up SSM Secrets ----
2022-11-21T19:09:20.492Z [INFO]: SSM params {"Path":"/amplify/d2hbdzl31vlu96/main/","WithDecryption":true}
2022-11-21T19:09:20.553Z [INFO]: # Defaulting to Node version 16
2022-11-21T19:09:31.668Z [INFO]: # Node version 16 is available for installation
2022-11-21T19:09:31.752Z [INFO]: # Installing Node version 16
2022-11-21T19:09:44.351Z [INFO]: # Now using Node version 16
2022-11-21T19:09:44.565Z [INFO]: # Retrieving cache...
2022-11-21T19:09:44.565Z [INFO]: # Retrieved cache

Expected behavior
Application should update to the latest code when RELEASE job is triggered.
Reproduction steps

Create application with CloudFormation as follows:

AWSTemplateFormatVersion: '2010-09-09'
Description: >
  This template deploys the web application via Amplify

Parameters:
  Environment:
    Type: String
    AllowedValues:
      - dev
      - qa
      - test
      - prod
      - demo
  Index:
    Type: String
    Description: 'Numeric part of Id'
  Repository:
    Type: String
    Description: GitHub Repository
  DomainName:
    Type: String
    Description: 'Domain'
  DomainPrefix:
    Type: String
    Description: 'Subdomain Prefix'
    Default: 'www'
  Branch:
    Type: String
    Description: Branch to deploy
    Default: main
  AccessToken:
    Type: String
    Description: GitHub Personal Access Token (needs admin:repo_hook)
  UseQA:
    Type: String
    Description: Set to true to use qa settings
    AllowedValues:
      - true
      - false
    Default: 'false'

Mappings:
  EnvironmentMap:
    Stage:
      dev: DEVELOPMENT
      qa: BETA
      test: BETA
      demo: PRODUCTION
      prod: PRODUCTION

Conditions:
  UseQA:
    Fn::Equals: [ !Ref UseQA, 'true' ]

Resources:
  AmplifyApp:
    Type: AWS::Amplify::App
    Properties:
      AccessToken: !Ref AccessToken
      BuildSpec: |
        version: 1
        applications:
          - frontend:
              phases:
                preBuild:
                  commands:
                    - cd ../.. & yarn install
                    - echo "NEXT_PUBLIC_CLIENT_ID=${NEXT_PUBLIC_CLIENT_ID}" >> .env
                    - echo "NEXT_PUBLIC_COGNITO_URL=${NEXT_PUBLIC_COGNITO_URL}" >> .env
                    - echo "NEXT_PUBLIC_BASE_URL=${NEXT_PUBLIC_BASE_URL}" >> .env
                    - echo "NEXT_PUBLIC_CONTENT_URL=${NEXT_PUBLIC_CONTENT_URL}" >> .env
                build:
                  commands:
                    - yarn build
              artifacts:
                baseDirectory: .next
                files:
                  - '**/*'
              cache:
                paths:
                  - node_modules/**/*
            appRoot: packages/subscriber
      Description: !Sub 'Amplify application for ${Environment}-${Index}'
      EnvironmentVariables:
        - Name: AMPLIFY_DIFF_DEPLOY
          Value: false
        - Name: AMPLIFY_MONOREPO_APP_ROOT
          Value: packages/subscriber
        - Name: NODE_OPTIONS
          Value: --max_old_space_size=4096
        - Name: _LIVE_UPDATES
          Value: '[{"pkg":"next-version","type":"internal","version":"latest"}]'
      IAMServiceRole: !Sub arn:aws:iam::${AWS::AccountId}:role/AmplifyRole
      Name: !Sub '${Environment}-${Index}'
      Repository: !Ref Repository
  AmplifyBranch:
    Type: AWS::Amplify::Branch
    Properties:
      AppId: !GetAtt  AmplifyApp.AppId
      BranchName: !Ref Branch
      Description: !Sub 'Amplify deployment for ${Environment}-${CreatorIndex} master'
      EnableAutoBuild: false
      EnvironmentVariables:
        - Name: NEXT_PUBLIC_CLIENT_ID
          Value:
            Fn::If:
              - UseQA
              - {'Fn::ImportValue': !Sub 'qa-UserPoolClient'}
              - {'Fn::ImportValue': !Sub 'serverlessrepo-${Environment}-${Index}-UserPoolClient'}
        - Name: NEXT_PUBLIC_COGNITO_URL
          Value:
            Fn::If:
              - UseQA
              - !Sub 'https://qa-${AWS::AccountId}.auth.${AWS::Region}.amazoncognito.com'
              - !Sub 'https://${Environment}-${Index}-${AWS::AccountId}.auth.${AWS::Region}.amazoncognito.com'
        - Name: NEXT_PUBLIC_BASE_URL
          Value:
            Fn::If:
              - UseQA
              - {'Fn::ImportValue': !Sub 'qa-1-creator-WebEndpoint'}
              - {'Fn::ImportValue': !Sub 'serverlessrepo-${Environment}-${CreatorIndex}-WebEndpoint'}
        - Name: NEXT_PUBLIC_CONTENT_URL
          Value:
            Fn::If:
              - UseQA
              - {'Fn::ImportValue': !Sub 'qa-1-creator-ContentURL'}
              - {'Fn::ImportValue': !Sub 'serverlessrepo-${Environment}-${CreatorIndex}-ContentURL'}
      Stage: !FindInMap [ EnvironmentMap, Stage, !Ref Environment ]
  DomainRecord:
    Type: AWS::Amplify::Domain
    Properties:
      AppId: !GetAtt AmplifyApp.AppId
      DomainName: !Ref DomainName
      SubDomainSettings:
        - Prefix: !Ref DomainPrefix
          BranchName: !GetAtt AmplifyBranch.BranchName

Outputs:
  URL:
    Description: Application URL
    Value: !Sub 'https://${Branch}.${AmplifyApp.DefaultDomain}'
  AppId:
    Description: Application ID
    Value: !GetAtt AmplifyApp.AppId
    Export:
      Name: !Sub '${AWS::StackName}-AppId'
  Branch:
    Description: Branch Name
    Value: !Ref Branch
    Export:
      Name: !Sub '${AWS::StackName}-Branch'

Set main branch via UI (this appears to not be set when creating app via CloudFormation)
Push commit to GitHub
Trigger RELEASE job via aws amplify start-job --branch-name main --app-id d2hbdzl31vlu96  --job-type RELEASE
Repeat 3-4 until app no longer appears to update

Build Settings
version: 1
applications:
  - frontend:
      phases:
        preBuild:
          commands:
            - cd ../.. & yarn install
            - echo "NEXT_PUBLIC_CLIENT_ID=${NEXT_PUBLIC_CLIENT_ID}" >> .env
            - echo "NEXT_PUBLIC_COGNITO_URL=${NEXT_PUBLIC_COGNITO_URL}" >> .env
            - echo "NEXT_PUBLIC_BASE_URL=${NEXT_PUBLIC_BASE_URL}" >> .env
            - echo "NEXT_PUBLIC_CONTENT_URL=${NEXT_PUBLIC_CONTENT_URL}" >> .env
        build:
          commands:
            - yarn build
      artifacts:
        baseDirectory: .next
        files:
          - '**/*'
    appRoot: packages/subscriber

Log output

# Put your logs below this line
2022-11-21T19:09:17.980Z [INFO]: # Cloning repository: git@github.com:[removed]/[removed].git
2022-11-21T19:09:20.414Z [INFO]:
2022-11-21T19:09:20.416Z [INFO]: Cloning into 'removed'...
2022-11-21T19:09:20.416Z [INFO]: # Checking for Git submodules at: /codebuild/output/src132231801/src/[removed]/.gitmodules
2022-11-21T19:09:20.426Z [INFO]: # Retrieving environment cache...
2022-11-21T19:09:20.491Z [WARNING]: ! Unable to write cache: {"code":"ERR_BAD_REQUEST","message":"Request failed with status code 404"})}
2022-11-21T19:09:20.491Z [INFO]: ---- Setting Up SSM Secrets ----
2022-11-21T19:09:20.492Z [INFO]: SSM params {"Path":"/amplify/d2hbdzl31vlu96/main/","WithDecryption":true}
2022-11-21T19:09:20.553Z [INFO]: # Defaulting to Node version 16
2022-11-21T19:09:31.668Z [INFO]: # Node version 16 is available for installation
2022-11-21T19:09:31.752Z [INFO]: # Installing Node version 16
2022-11-21T19:09:44.351Z [INFO]: # Now using Node version 16
2022-11-21T19:09:44.565Z [INFO]: # Retrieving cache...
2022-11-21T19:09:44.565Z [INFO]: # Retrieved cache

Additional information
No response

Hi @foxbox-doug 👋🏽 we apologize for this inconvenience. Thank you for providing thorough reproduction steps. We will investigate this behavior and report back with next steps for a possible work around.

Upon further investigation, this can be the result of a race condition. If a new job is starting while a previous job is still running, then it is possible that the previous job will be deployed while the newer job fails, causing the previous commit to be deployed instead of the new commit. You can prevent this by canceling any currently running builds before starting a new job:
aws amplify stop-job --app-id <value> --branch-name <value> --job-id <value>
Please let us know if this race condition is not applicable to your scenario and we will continue to investigate.

Upon further investigation, this can be the result of a race condition. If a new job is starting while a previous job is still running, then it is possible that the previous job will be deployed while the newer job fails, causing the previous commit to be deployed instead of the new commit. You can prevent this by canceling any currently running builds before starting a new job:
aws amplify stop-job --app-id <value> --branch-name <value> --job-id <value>
Please let us know if this race condition is not applicable to your scenario and we will continue to investigate.

Definitely not race condition. Waited for all previous jobs to complete before queuing new job.

@foxbox-doug it appears you have deleted this application. Please let us know if you still need assistance with this issue.

@hloriana We had to recreate the app to get it to update. I will provide more info if the issue repeats itself.

Hi everyone! I don't have a functional evidence here, but I found the same issue when I migrated my application to web compute platform through the wizard.

My feature branches started to use another unrelated branch, and was actually using a previous commit before HEAD.
My solution was to create a whole new app in web compute and it worked from the start.

Hi @GabrielArakaki 👋🏽 thank you for providing details around this behavior. Do you happen to have the App ID of the application that was migrated? This could potentially help us investigate this behavior further.

Hi @hloriana Sorry, I have also deleted the old application!

is there any update about sites not reflecting changes after migration ? @hloriana

Hi! 🙂
We are experiencing the same issue, that is even though we successfully push and build new code changes, a previous/old commit is being deployed.
This started happening after pressing the "Migrate" button, which came after the announcement of Next.js 12 and 13 support in the new web compute platform.
Next.js version 12.3.4
Node.js 16.18.1
App ID d7rf8fcnzpljj
Region us-east-1
Please help, thank you.
CC: @hloriana

@edenriquez @kivohin It looks like Amplify Hosting now directly manages the resources that were previously deployed to CloudFront, Lambda, etc.
My issue involved rewrite rules, which pointed to old distributions, not being automatically removed.
See answer here

Thank you @foobarnes! Indeed, that was one of the issues for us as well, i.e. we had some old rewrite rules pointing to old CloudFront distributions.
Our other issue was that we manage our custom domain name configurations through Route53, and not through Amplify's Domain management section.
Since the Amplify Hosting model changed, and they are now directly managing all the resources, we are now forced to setup our custom domain through Amplify's Domain management section.
After doing that everything came back to normal.
Definitely an interesting change Amplify Hosting is heading into. More into the Vercel/Netlify direction where they have the control over everything.

Hi, we are still experiencing same issue of sites not reflecting changes post-migration even after removing old rewrite rules.
@foobarnes @hloriana any ideas?
App ID is d9vnksjwvp8m7
Builds are successful and the frontend seems to be in the right commit? But it is definitely an older one that is getting deployed.

Regarding @zevi-wiply's issue, this is also happening to my app as well. Started happening after switching to Web compute.

We are experiencing this issue also.
We have a NextJS app deployed to an amplify environment.
When using NextJS version 12.1.8 and WEB_DYNAMIC it works perfectly.
When using NextJS version 13.0.6 and WEB_COMPUTE  it fails to display the latest commit.

After some investigation, this is what we did to solve the issue:

Upgrading to NextJS 13, requires changing the platform to WEB_COMPUTE.
Moving to WEB_COMPUTE, requires deleting the rewrite rules as they are no longer needed, maintaining the rules, redirects to the last successful deploy made with WEB_DYNAMIC.
This is a configuration on the Amplify dashboard that needs to be removed manually.

Using WEB_COMPUTE expects the build to export a standalone app (server and frontend).
We needed to configure NextJS for generating a build to be a standalone app by doing in nextjs.config:
output: 'standalone',
experimental: {
  outputFileTracingRoot: path.join(__dirname, '../../'),
},

Using WEB_COMPUTE and, a Monorepo, expects the server output to be located in other folder different from the exported standalone default.
We had to configure the Amplify build script to move the assets to the expected location so, Amplify can locate and start the server, by doing in amplify.yml:
postBuild:
  commands:
    - echo FRONTEND POSTBUILD
    - shopt -s dotglob
    - mv -f .next/standalone/app/app-name/node_modules/* .next/standalone/node_modules
    - rm -rf .next/standalone/app/app-name/node_modules
    - mv -f .next/standalone/app/app-name/* .next/standalone
    - rm -rf .next/standalone/app/app-name

Im not sure if this is the correct thing to do, but I hope this helps someone or the Amplify team

At the time this issue was opened, Amplify was failing to remove the redirect rule that points to the previous CloudFront distribution after migrating the application. This has since been resolved and should no longer be an issue for folks who need to migrate to WEB_COMPUTE.


"chipset" command freezes on Ryzen 9 7945HX platform

Hello,
On my Ryzen 9 7945HX, the chipset command does not work properly. I will provide the log with debug messages enabled:
>>> debug
-> Debug: enabled
>>> chipset
Detected chipset:
=> Family: 19
=> Model: 61

-> One dword read from 00:14:03 offset 00000000h: 790e1022h
-> One dword read from 00:14:03 offset 00000004h: 0220000fh
-> One dword read from 00:14:03 offset 00000008h: 06010051h
-> One dword read from 00:14:03 offset 0000000ch: 00800000h
-> One dword read from 00:14:03 offset 00000010h: 00000000h
-> One dword read from 00:14:03 offset 00000014h: 00000000h
-> One dword read from 00:14:03 offset 00000018h: 00000000h
-> One dword read from 00:14:03 offset 0000001ch: 00000000h
-> One dword read from 00:14:03 offset 00000020h: 00000000h
-> One dword read from 00:14:03 offset 00000024h: 00000000h
-> One dword read from 00:14:03 offset 00000028h: 00000000h
-> One dword read from 00:14:03 offset 0000002ch: 14331043h
-> One dword read from 00:14:03 offset 00000030h: 00000000h
-> One dword read from 00:14:03 offset 00000034h: 00000000h
-> One dword read from 00:14:03 offset 00000038h: 00000000h
-> One dword read from 00:14:03 offset 0000003ch: 00000000h
-> One dword read from 00:14:03 offset 00000040h: 0000001ch
-> One dword read from 00:14:03 offset 00000044h: ffffffffh
-> One dword read from 00:14:03 offset 00000048h: ffffffffh
-> One dword read from 00:14:03 offset 0000004ch: ffffffffh
-> One dword read from 00:14:03 offset 00000050h: ffffffffh
-> One dword read from 00:14:03 offset 00000054h: ffffffffh
-> One dword read from 00:14:03 offset 00000058h: ffffffffh
-> One dword read from 00:14:03 offset 0000005ch: ffffffffh
-> One dword read from 00:14:03 offset 00000060h: ffffffffh
-> One dword read from 00:14:03 offset 00000064h: ffffffffh
-> One dword read from 00:14:03 offset 00000068h: ffffffffh
-> One dword read from 00:14:03 offset 0000006ch: ffffffffh
-> One dword read from 00:14:03 offset 00000070h: ffffffffh
-> One dword read from 00:14:03 offset 00000074h: ffffffffh
-> One dword read from 00:14:03 offset 00000078h: ffffffffh
-> One dword read from 00:14:03 offset 0000007ch: ffffffffh
-> One dword read from 00:14:03 offset 00000080h: ffffffffh
-> One dword read from 00:14:03 offset 00000084h: ffffffffh
-> One dword read from 00:14:03 offset 00000088h: ffffffffh
-> One dword read from 00:14:03 offset 0000008ch: ffffffffh
-> One dword read from 00:14:03 offset 00000090h: ffffffffh
-> One dword read from 00:14:03 offset 00000094h: ffffffffh
-> One dword read from 00:14:03 offset 00000098h: ffffffffh
-> One dword read from 00:14:03 offset 0000009ch: ffffffffh
-> One dword read from 00:14:03 offset 000000a0h: ffffffffh
-> One dword read from 00:14:03 offset 000000a4h: ffffffffh
-> One dword read from 00:14:03 offset 000000a8h: ffffffffh
-> One dword read from 00:14:03 offset 000000ach: ffffffffh
-> One dword read from 00:14:03 offset 000000b0h: ffffffffh
-> One dword read from 00:14:03 offset 000000b4h: ffffffffh
-> One dword read from 00:14:03 offset 000000b8h: ffffffffh
-> One dword read from 00:14:03 offset 000000bch: ffffffffh
-> One dword read from 00:14:03 offset 000000c0h: ffffffffh
-> One dword read from 00:14:03 offset 000000c4h: ffffffffh
-> MSR:[c0010058]: 00000000F000001D
-> 000000c4 bytes read from physical Memory 00000000FFFFFFC0
-> Successfully mapped physaddr ffffffc0 to<PHONE_NUMBER>860FC0

It seems there are some major differences in the way things are mapped in this particular model.

Is there any way I can help?

I have same issue on ryzen 7 8840u apu. gpd win max 2, tho the same soc on gpd win mini it works fine.

So for me ryzen 7 8840u zen4 for sum reason it was failing too accurately distinguish between new and old amd in function amd_retrieve_chipset_information,  failing to set "spi_addr = AMD_DEFAULT_NEW_SPI_ADDR" or "isNewAmdChipset = true" once i hard coded those it goes thru fine now. @moldimolt  I would try this. In PlatboxLib/src/amd/amd_chipset.cpp function amd_retrieve_chipset_information replace;
} else {
spi_addr = spi_addr & 0xFFFFFFC0;
_isNewAmdChipset = false;
with
} else {
    spi_addr = AMD_DEFAULT_NEW_SPI_ADDR;
    _isNewAmdChipset = true;

This is a dirty dirty hack, but at least see if its the same issue/area to fix.

I'll be updating some of this portion with the release of the sinkclose exploit soon.

Thank you! And again thank you for all your work and time, unbelievably
awesome project.
On Sat, Aug 24, 2024, 4:09 PM Enrique Elias Nissim @.***>
wrote:

I'll be updating some of this portion with the release of the sinkclose
exploit soon.
—
Reply to this email directly, view it on GitHub
https://github.com/IOActive/Platbox/issues/9#issuecomment-2308523794,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADAWMP7YIOJ5YO6YSTQGPYTZTDR7ZAVCNFSM6AAAAABNBSIVJ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGUZDGNZZGQ
.
You are receiving this because you commented.Message ID:
@.***>


fetch host address from hostdb for renter/contracts call

Waiting on review from @lukechampine

uh oh: In the Travis build:
panic: Critical error: no contract with that id

goroutine 3210 [running]:
github.com/NebulousLabs/Sia/build.Critical(0xc4206e6338, 0x1, 0x1)
	/home/travis/gopath/src/github.com/NebulousLabs/Sia/build/critical.go:20 +0xce
github.com/NebulousLabs/Sia/modules/renter/proto.(*ContractSet).Return(0xc42020dc50, 0xc420201900)
	/home/travis/gopath/src/github.com/NebulousLabs/Sia/modules/renter/proto/contractset.go:84 +0x2dc
github.com/NebulousLabs/Sia/modules/renter/proto.(*ContractSet).NewDownloader(0xc42020dc50, 0x1, 0x1100000, 0x6540, 0x1100000, 0xc42020e000, 0xf, 0xf4000, 0x1000, 0x100000, ...)
	/home/travis/gopath/src/github.com/NebulousLabs/Sia/modules/renter/proto/downloader.go:185 +0x7a5
github.com/NebulousLabs/Sia/modules/renter/contractor.(*Contractor).Downloader(0xc42023c820, 0x5a0f4b6fc7ff3fea, 0x707fcf18857a1694, 0xe0a7f232dc201ac2, 0x43ce143a358aa943, 0xc4203448a0, 0x0, 0x0, 0x0, 0x0)
	/home/travis/gopath/src/github.com/NebulousLabs/Sia/modules/renter/contractor/downloader.go:160 +0x847
github.com/NebulousLabs/Sia/modules/renter.(*worker).download(0xc4205c1180, 0xd2aa789623714d61, 0xf3d0cf8726c31cb8, 0x652be5af1f1257ed, 0xd3c1a055b17e6cf4, 0x0, 0xc4201bd180, 0xc420344a80)
	/home/travis/gopath/src/github.com/NebulousLabs/Sia/modules/renter/workerdownload.go:36 +0x147
github.com/NebulousLabs/Sia/modules/renter.(*worker).threadedWorkLoop(0xc4205c1180)
	/home/travis/gopath/src/github.com/NebulousLabs/Sia/modules/renter/worker.go:64 +0x203
created by github.com/NebulousLabs/Sia/modules/renter.(*Renter).managedUpdateWorkerPool
	/home/travis/gopath/src/github.com/NebulousLabs/Sia/modules/renter/worker.go:144 +0x801

It seems like the renter is returning a contract after it's been deleted from the set. The reason this is surprising is that in order to delete a contract from the set, you have to have previously Acquired it. Which implies that one thread is calling both Delete and then Return on the same contract.

However, I don't believe that this panic has anything to do with this PR, which seems pretty obviously correct to me. I'll merge if I can get the build to pass.


Tytack

Created a shed game object at spawn point. I put the universal lighting under past as well as a campfire. I added a couple lamps on the ground for path lighting in the present. I had issues with my skybox materials so let me know if the skybox can be fixed liked Justin's version.

Lets keep one PR for the outdoors scene to avoid conflicts and divergent branches. When ready, @jjones1512 should merge this branch into his scene, for his PR


fix: use the most general selectable-overload by default

Workaround for #311
This issue was fixed in ikatyang/dts-element-fp#80

before: use the first signature's selectable-overload, i.e. list in this case

after: use the last (most general) signature's selectable-overload, i.e. mixed in this case

Closes #325

So the error says it used the mixed overload, yet with the extra parentheses it fixes it by choosing that one too? I think I'm confused...
I mean, if TS broke our stuff and this can fix it now, great. Too bad about needing the parens now though, wish we could just get a usable mixed overload without it.
This fix is fine, as it's just damage control right now, but we may wanna keep the original issue open. Since it seems like a TS regression, we might wanna escalate it and file an issue for it over there, if there wasn't one already.

Opened https://github.com/Microsoft/TypeScript/issues/19913.


Some source files miss Apache license headers

Following Apache license header guideline, all human-readable Apache-developed files that are included within a distribution must include the header text with few exceptions. You can find few exceptions here: which files do not require a license header.
I used Apache Rat to check this repository after excluding a few files, and I got this report. We need to add Apache licensing header to those files.
Unapproved licenses:

  openwhisk-runtime-php/core/php7.1Action/Dockerfile
  openwhisk-runtime-php/tests/src/test/resources/application.conf
  openwhisk-runtime-php/ansible/environments/local/group_vars/all
  openwhisk-runtime-php/ansible/environments/local/hosts

The excluded files are:
**/*.json
**/**.gradle
**/gradlew
**/gradle/**
**/.**
**/templates/**
**/*.j2.*
**/.github/**
**/auth.whisk.system
**/auth.guest
**/i18n_resources.go

I suggest to add below files to excluded file list, because they are configuration files with few creativity.
  openwhisk-runtime-php/tests/src/test/resources/application.conf
  openwhisk-runtime-php/ansible/environments/local/group_vars/all
  openwhisk-runtime-php/ansible/environments/local/hosts

I think is done now


How to use rexray/csi-nfs with docker plugin ?

I'm tyring to use rexray for my docker and NFS server.
I found this page, https://rexray.readthedocs.io/en/stable/user-guide/schedulers/docker/plug-ins/csi-nfs/ .
But it is not clear to me : (
Anyone can inform me how to use it by docker plugin ?

Hello @keyolk,
You're right I think we're definitely missing some examples. This is the plugin page https://github.com/thecodeteam/csi-nfs
@codenrhoden Do you have any examples that you can drop in here for now?

I'm pretty sure that the following commands might work on the client:
docker plugin install rexray/csi-nfs
docker volume create --driver rexray/csi-nfs --name test
docker volume ls
docker run -v test:/data busybox mount | grep "/data"

But I can't figure out how to set the address of the server and directory? The last command fails with the following:
docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/1a4940d2e0ab04a9363bd36b69c4018c555ad88c25be7d2525eb3896dfa900f1/rootfs': VolumeDriver.Mount: NodePublishVolume failed: 6: mount failed: exit status 1
mounting arguments: -t nfs : /dev/csi-nfs-mounts/:
output: mount: bad address ''.
ERRO[0000] error getting events from daemon: net/http: request canceled

Try using the following environment variables when you install the plugin.
https://github.com/thecodeteam/csi-nfs/blob/master/nfs/nfs_test.go#L12-L13

Thanks, I saw those, but it seems they are only used for triggering the call to the imported Mount in the test, no?
https://github.com/thecodeteam/csi-nfs/blob/master/nfs/nfs_test.go#L28

Sorry, deleted that comment. I believe it is just looking for a host and export separated by a dash. For example, nfshost-volume1 woudl equal nfshhost://volume1

Can you also try this? docker volume create -d rexray test2 -o host=<IP_ADDRESS> -o export=/data

That does seem to work when the command is of the form docker volume create -d rexray/csi-nfs test2 -o host=<IP_ADDRESS> -o export=/data

Ok, it's close. Here's what I am seeing:

In my case, the command is docker volume create -d rexray/csi-nfs test5 -o host=<IP_ADDRESS> -o export=/mnt/tank/dcos/grafana
When I run a container with docker run -v test5:/data busybox ls "/data" the output of the docker run is the following:

[root@public01 ~]# docker run -v test5:/data busybox ls "/data"
docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/1a4940d2e0ab04a9363bd36b69c4018c555ad88c25be7d2525eb3896dfa900f1/rootfs': VolumeDriver.Mount: NodePublishVolume failed: 6: mount failed: exit status 255
mounting arguments: -o bind /dev/csi-nfs-mounts/<IP_ADDRESS>:#mnt#tank#dcos#grafana /var/lib/rexray/docker/volumes/test5
output: mount: mounting /dev/csi-nfs-mounts/<IP_ADDRESS>: on /var/lib/rexray/docker/volumes/test5 failed: No such file or directory.
ERRO[0000] error getting events from daemon: net/http: request canceled

But that's not all bad. When I run mount to see what is mounted on the host, I see the mount that is defined in the docker volume create. Examining the mount, I can see the contents of the volume. That's a huge success so far, thanks!

Not sure if any of this word jumble is making sense, I may have to RTFM more.

@briantopping Can you try an export path that is just one level deep? The example I had comes from testing that occurred so I'm wondering if its related to the path structure submitted when you create the volume.

Thanks @clintkitson I can do that but need to create a new server for it. My NAS doesn't allow shares that are not in a data volume mount point, which is at least two directories deep.
Is there any way you could try the reverse, to quickly mount a deep directory? Then we could converge with results.

Indeed, same problem:
[root@public01 ~]# mount -v dev.coglative.com:/data /mnt
[root@public01 ~]# ls /mnt
test
[root@public01 ~]# umount /mnt
[root@public01 ~]# docker volume create -d rexray/csi-nfs data -o host=dev.example.com -o export=/data
data
[root@public01 ~]# docker run -v data:/data busybox
docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/1a4940d2e0ab04a9363bd36b69c4018c555ad88c25be7d2525eb3896dfa900f1/rootfs': VolumeDriver.Mount: NodePublishVolume failed: 6: mount failed: exit status 255
mounting arguments: -o bind /dev/csi-nfs-mounts/dev.example.com:#data /var/lib/rexray/docker/volumes/data
output: mount: mounting /dev/csi-nfs-mounts/dev.example.com: on /var/lib/rexray/docker/volumes/data failed: No such file or directory.
ERRO[0000] error getting events from daemon: net/http: request canceled
[root@public01 ~]# mount
...
dev.example.com:/data on /dev/csi-nfs-mounts/dev.example.com:#data type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=<IP_ADDRESS>,local_lock=none,addr=x.x.x.15)

Does /var/lib/rexray/docker/volumes exist?
On Mon, Nov 20, 2017 at 7:58 PM Brian Topping<EMAIL_ADDRESS>wrote:

Indeed, same problem:
[root@public01 ~]# mount -v dev.coglative.com:/data /mnt
[root@public01 ~]# ls /mnt
test
[root@public01 ~]# umount /mnt
[root@public01 ~]# docker volume create -d rexray/csi-nfs data -o host=dev.example.com -o export=/data
data
[root@public01 ~]# docker run -v data:/data busybox
docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/1a4940d2e0ab04a9363bd36b69c4018c555ad88c25be7d2525eb3896dfa900f1/rootfs': VolumeDriver.Mount: NodePublishVolume failed: 6: mount failed: exit status 255
mounting arguments: -o bind /dev/csi-nfs-mounts/dev.example.com:#data /var/lib/rexray/docker/volumes/data
output: mount: mounting /dev/csi-nfs-mounts/dev.example.com: on /var/lib/rexray/docker/volumes/data failed: No such file or directory.
ERRO[0000] error getting events from daemon: net/http: request canceled
[root@public01 ~]# mount
...
dev.example.com:/data on /dev/csi-nfs-mounts/dev.example.com:#data type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=<IP_ADDRESS>,local_lock=none,addr=x.x.x.15)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thecodeteam/rexray/issues/1114#issuecomment-345909931,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVMMdMYnjbstIoT5RFZKnzKaJUbuetqks5s4kqAgaJpZM4Qhbbs
.

[root@public01 ~]# ls -alf /var/lib/rexray/docker/volumes
.  ..
[root@public01 ~]# df !$
df /var/lib/rexray/docker/volumes
Filesystem              1K-blocks    Used Available Use% Mounted on
/dev/mapper/centos-root  17811456 3949020  13862436  23% /

And the data directory? It is trying do a bind mount to that path if you
reference the error.
On Mon, Nov 20, 2017 at 8:02 PM Brian Topping<EMAIL_ADDRESS>wrote:

[root@public01 ~]# ls -alf /var/lib/rexray/docker/volumes
.  ..
[root@public01 ~]# df !$
df /var/lib/rexray/docker/volumes
Filesystem              1K-blocks    Used Available Use% Mounted on
/dev/mapper/centos-root  17811456 3949020  13862436  23% /
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thecodeteam/rexray/issues/1114#issuecomment-345910398,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVMMfJGT9oLHYCss0gm_u-og58x3hTcks5s4ktjgaJpZM4Qhbbs
.

And the data directory? It is trying do a bind mount to that path if you reference the error.
Ah good point. /var/lib/rexray/docker/volumes/data does not exist, the directory is mounted at /dev/csi-nfs-mounts/dev.example.com:#data, which is what I guess I meant by "same problem".

This is some of the first bind mounting I am doing, do I actually have to create directories for this stuff? I would have thought Docker does that automatically?

RR and the plugin should be doing this for you so very surprised you are
hitting this error. Trying to troubleshoot based on what you're error is
saying.
What is the current RR config?
On Mon, Nov 20, 2017 at 8:09 PM Brian Topping<EMAIL_ADDRESS>wrote:

And the data directory? It is trying do a bind mount to that path if you
reference the error.
Ah good point. /var/lib/rexray/docker/volumes/data does not exist, the
directory is mounted at /dev/csi-nfs-mounts/dev.example.com:#data, which
is what I guess I meant by "same problem".
This is some of the first bind mounting I am doing, do I actually have to
create directories for this stuff? I would have thought Docker does that
automatically?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thecodeteam/rexray/issues/1114#issuecomment-345911165,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVMMdoBIskdnuurWlZsLTI5j5MTyFhXks5s4kzjgaJpZM4Qhbbs
.

Thanks! Is this easier on Slack?
[root@public01 ~]# cat /etc/rexray/config.yml
rexray:
#  loglevel: debug
  modules:
    default-docker:
#      disabled: true

Behavior is the same regardless of whether default-docker.disabled: true is commented or uncommented.

Want to capture this for others as well. What command are you using and
what relevant env variables are set?
On Mon, Nov 20, 2017 at 8:14 PM Brian Topping<EMAIL_ADDRESS>wrote:

Thanks! Is this easier on Slack?
[root@public01 ~]# cat /etc/rexray/config.yml
rexray:
loglevel: debug
modules:
default-docker:
disabled: true
Behavior is the same regardless of whether default-docker.disabled: true
is commented or uncommented.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thecodeteam/rexray/issues/1114#issuecomment-345911901,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVMMaVn4ihqS0a8L4NEUuGUVHCTZDNOks5s4k47gaJpZM4Qhbbs
.

Sure thing. No environment variables visible in export that are beyond standard profile:
[root@public01 ~]# export
declare -x HISTCONTROL="ignoredups"
declare -x HISTSIZE="1000"
declare -x HOME="/root"
declare -x HOSTNAME="public01.mc1.example.com"
declare -x LANG="en_US.UTF-8"
declare -x LESSOPEN="||/usr/bin/lesspipe.sh %s"
declare -x LOGNAME="root"
declare -x LS_COLORS="rs=0:di=38;5;27:ln=38;5;51:mh=44;38;5;15:pi=40;38;5;11:so=38;5;13:do=38;5;5:bd=48;5;232;38;5;11:cd=48;5;232;38;5;3:or=48;5;232;38;5;9:mi=05;48;5;232;38;5;15:su=48;5;196;38;5;15:sg=48;5;11;38;5;16:ca=48;5;196;38;5;226:tw=48;5;10;38;5;16:ow=48;5;10;38;5;21:st=48;5;21;38;5;15:ex=38;5;34:*.tar=38;5;9:*.tgz=38;5;9:*.arc=38;5;9:*.arj=38;5;9:*.taz=38;5;9:*.lha=38;5;9:*.lz4=38;5;9:*.lzh=38;5;9:*.lzma=38;5;9:*.tlz=38;5;9:*.txz=38;5;9:*.tzo=38;5;9:*.t7z=38;5;9:*.zip=38;5;9:*.z=38;5;9:*.Z=38;5;9:*.dz=38;5;9:*.gz=38;5;9:*.lrz=38;5;9:*.lz=38;5;9:*.lzo=38;5;9:*.xz=38;5;9:*.bz2=38;5;9:*.bz=38;5;9:*.tbz=38;5;9:*.tbz2=38;5;9:*.tz=38;5;9:*.deb=38;5;9:*.rpm=38;5;9:*.jar=38;5;9:*.war=38;5;9:*.ear=38;5;9:*.sar=38;5;9:*.rar=38;5;9:*.alz=38;5;9:*.ace=38;5;9:*.zoo=38;5;9:*.cpio=38;5;9:*.7z=38;5;9:*.rz=38;5;9:*.cab=38;5;9:*.jpg=38;5;13:*.jpeg=38;5;13:*.gif=38;5;13:*.bmp=38;5;13:*.pbm=38;5;13:*.pgm=38;5;13:*.ppm=38;5;13:*.tga=38;5;13:*.xbm=38;5;13:*.xpm=38;5;13:*.tif=38;5;13:*.tiff=38;5;13:*.png=38;5;13:*.svg=38;5;13:*.svgz=38;5;13:*.mng=38;5;13:*.pcx=38;5;13:*.mov=38;5;13:*.mpg=38;5;13:*.mpeg=38;5;13:*.m2v=38;5;13:*.mkv=38;5;13:*.webm=38;5;13:*.ogm=38;5;13:*.mp4=38;5;13:*.m4v=38;5;13:*.mp4v=38;5;13:*.vob=38;5;13:*.qt=38;5;13:*.nuv=38;5;13:*.wmv=38;5;13:*.asf=38;5;13:*.rm=38;5;13:*.rmvb=38;5;13:*.flc=38;5;13:*.avi=38;5;13:*.fli=38;5;13:*.flv=38;5;13:*.gl=38;5;13:*.dl=38;5;13:*.xcf=38;5;13:*.xwd=38;5;13:*.yuv=38;5;13:*.cgm=38;5;13:*.emf=38;5;13:*.axv=38;5;13:*.anx=38;5;13:*.ogv=38;5;13:*.ogx=38;5;13:*.aac=38;5;45:*.au=38;5;45:*.flac=38;5;45:*.mid=38;5;45:*.midi=38;5;45:*.mka=38;5;45:*.mp3=38;5;45:*.mpc=38;5;45:*.ogg=38;5;45:*.ra=38;5;45:*.wav=38;5;45:*.axa=38;5;45:*.oga=38;5;45:*.spx=38;5;45:*.xspf=38;5;45:"
declare -x MAIL="/var/spool/mail/root"
declare -x OLDPWD
declare -x PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/opt/mesosphere/bin/dcos-path:/root/bin"
declare -x PWD="/root"
declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SSH_CLIENT="<IP_ADDRESS> 58822 22"
declare -x SSH_CONNECTION="<IP_ADDRESS> 58822 <IP_ADDRESS> 22"
declare -x SSH_TTY="/dev/pts/0"
declare -x TERM="xterm-256color"
declare -x USER="root"
declare -x XDG_RUNTIME_DIR="/run/user/0"
declare -x XDG_SESSION_ID="49"

Command to create volume and start docker container is:
docker volume create -d rexray/csi-nfs data -o host=dev.example.com -o export=/data
docker run -v data:/data busybox`

First command is fine, second as in output above.

What was the command to start RR?
On Mon, Nov 20, 2017 at 8:23 PM Brian Topping<EMAIL_ADDRESS>wrote:

Sure thing. No environment variables visible in export that are beyond
standard profile:
[root@public01 ~]# export
declare -x HISTCONTROL="ignoredups"
declare -x HISTSIZE="1000"
declare -x HOME="/root"
declare -x HOSTNAME="public01.mc1.example.com"
declare -x LANG="en_US.UTF-8"
declare -x LESSOPEN="||/usr/bin/lesspipe.sh %s"
declare -x LOGNAME="root"
declare -x LS_COLORS="rs=0:di=38;5;27:ln=38;5;51:mh=44;38;5;15:pi=40;38;5;11:so=38;5;13:do=38;5;5:bd=48;5;232;38;5;11:cd=48;5;232;38;5;3:or=48;5;232;38;5;9:mi=05;48;5;232;38;5;15:su=48;5;196;38;5;15:sg=48;5;11;38;5;16:ca=48;5;196;38;5;226:tw=48;5;10;38;5;16:ow=48;5;10;38;5;21:st=48;5;21;38;5;15:ex=38;5;34:.tar=38;5;9:.tgz=38;5;9:.arc=38;5;9:.arj=38;5;9:.taz=38;5;9:.lha=38;5;9:.lz4=38;5;9:.lzh=38;5;9:.lzma=38;5;9:.tlz=38;5;9:.txz=38;5;9:.tzo=38;5;9:.t7z=38;5;9:.zip=38;5;9:.z=38;5;9:.Z=38;5;9:.dz=38;5;9:.gz=38;5;9:.lrz=38;5;9:.lz=38;5;9:.lzo=38;5;9:.xz=38;5;9:.bz2=38;5;9:.bz=38;5;9:.tbz=38;5;9:.tbz2=38;5;9:.tz=38;5;9:.deb=38;5;9:.rpm=38;5;9:.jar=38;5;9:.war=38;5;9:.ear=38;5;9:.sar=38;5;9:.rar=38;5;9:.alz=38;5;9:.ace=38;5;9:.zoo=38;5;9:.cpio=38;5;9:.7z=38;5;9:.rz=38;5;9:.cab=38;5;9:.jpg=38;5;13:.jpeg=38;5;13:.gif=38;5;13:.bmp=38;5;13:.pbm=38;5;13:.pgm=38;5;13:.ppm=38;5;13:.tga=38;5;13:.xbm=38;5;13:.xpm=38;5;13:.tif=38;5;13:.tiff=38;5;13:.png=38;5;13:.svg=38;5;13:.svgz=38;5;13:.mng=38;5;13:.pcx=38;5;13:.mov=38;5;13:.mpg=38;5;13:.mpeg=38;5;13:.m2v=38;5;13:.mkv=38;5;13:.webm=38;5;13:.ogm=38;5;13:.mp4=38;5;13:.m4v=38;5;13:.mp4v=38;5;13:.vob=38;5;13:.qt=38;5;13:.nuv=38;5;13:.wmv=38;5;13:.asf=38;5;13:.rm=38;5;13:.rmvb=38;5;13:.flc=38;5;13:.avi=38;5;13:.fli=38;5;13:.flv=38;5;13:.gl=38;5;13:.dl=38;5;13:.xcf=38;5;13:.xwd=38;5;13:.yuv=38;5;13:.cgm=38;5;13:.emf=38;5;13:.axv=38;5;13:.anx=38;5;13:.ogv=38;5;13:.ogx=38;5;13:.aac=38;5;45:.au=38;5;45:.flac=38;5;45:.mid=38;5;45:.midi=38;5;45:.mka=38;5;45:.mp3=38;5;45:.mpc=38;5;45:.ogg=38;5;45:.ra=38;5;45:.wav=38;5;45:.axa=38;5;45:.oga=38;5;45:.spx=38;5;45:*.xspf=38;5;45:"
declare -x MAIL="/var/spool/mail/root"
declare -x OLDPWD
declare -x PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/opt/mesosphere/bin/dcos-path:/root/bin"
declare -x PWD="/root"
declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SSH_CLIENT="<IP_ADDRESS> 58822 22"
declare -x SSH_CONNECTION="<IP_ADDRESS> 58822 <IP_ADDRESS> 22"
declare -x SSH_TTY="/dev/pts/0"
declare -x TERM="xterm-256color"
declare -x USER="root"
declare -x XDG_RUNTIME_DIR="/run/user/0"
declare -x XDG_SESSION_ID="49"
Command to create volume and start docker container is:
docker volume create -d rexray/csi-nfs data -o host=dev.example.com
-o export=/data
docker run -v data:/data busybox`
First command is fine, second as in output above.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thecodeteam/rexray/issues/1114#issuecomment-345912928,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVMMcR6R-xOnUiMVZdlemQ7n3BGqTQcks5s4lBdgaJpZM4Qhbbs
.

[root@public01 ~]# cat /etc/systemd/system/rexray.service
[Unit]
Description=rexray
Wants=scini.service
Before=docker.service
After=scini.service

[Service]
EnvironmentFile=/etc/rexray/rexray.env
ExecStart=/usr/bin/rexray start
ExecReload=/bin/kill -HUP $MAINPID
KillMode=process

[Install]
WantedBy=docker.service

I just noticed the /etc/rexray/rexray.env file, but it is empty.
[root@public01 ~]# systemctl status rexray
● rexray.service - rexray
   Loaded: loaded (/etc/systemd/system/rexray.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2017-11-20 21:31:50 MST; 2s ago
 Main PID: 1693 (rexray)
   Memory: 7.3M
   CGroup: /system.slice/rexray.service
           └─1693 /usr/bin/rexray start

Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="registered custom context key" externalID=Libstorage-Localdevices internalID=4 keyBitmask=2
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="registered custom context key" externalID=Authorization internalID=5 keyBitmask=2
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="http request" host="unix:///var/run/rexray/691450720.sock" route=services server=quill-crystal-si time=1511238713065 tls=false
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="initializing supported cache" host="unix:///var/run/rexray/691450720.sock" server=quill-crystal-si service=vfs storage...me=1511238713066
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="initializing instance ID cache" host="unix:///var/run/rexray/691450720.sock" server=quill-crystal-si service=vfs stora...me=1511238713101
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="http request" host="unix:///var/run/rexray/691450720.sock" route=serviceInspect server=quill-crystal-si time=1511238713137 tls=false
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="successefully dialed libStorage server" host="unix:///var/run/rexray/691450720.sock" server=quill-crystal-si service=v...me=1511238713139
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="storage driver initialized" host="unix:///var/run/rexray/691450720.sock" service=vfs storageDriver=libstorage time=1511238713140
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="os driver initialized" host="unix:///var/run/rexray/691450720.sock" osDriver=linux service=vfs storageDriver=libstorag...me=1511238713156
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="linux integration driver successfully initialized" host="unix:///var/run/rexray/691450720.sock" integrationDriver=linu...te.default.avail
Hint: Some lines were ellipsized, use -l to show in full.

Yes, but I am seeing you reference it as rexray/csi-nfs preivously? This
indicates you also have the managed plugin running simultaneously?
On Mon, Nov 20, 2017 at 8:36 PM, Brian Topping<EMAIL_ADDRESS>wrote:

[root@public01 ~]# cat /etc/systemd/system/rexray.service
[Unit]
Description=rexray
Wants=scini.service
Before=docker.service
After=scini.service
[Service]
EnvironmentFile=/etc/rexray/rexray.env
ExecStart=/usr/bin/rexray start
ExecReload=/bin/kill -HUP $MAINPID
KillMode=process
[Install]
WantedBy=docker.service
I just noticed the /etc/rexray/rexray.env file, but it is empty.
[root@public01 ~]# systemctl status rexray
● rexray.service - rexray
Loaded: loaded (/etc/systemd/system/rexray.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2017-11-20 21:31:50 MST; 2s ago
Main PID: 1693 (rexray)
Memory: 7.3M
CGroup: /system.slice/rexray.service
└─1693 /usr/bin/rexray start
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="registered custom context key" externalID=Libstorage-Localdevices internalID=4 keyBitmask=2
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="registered custom context key" externalID=Authorization internalID=5 keyBitmask=2
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="http request" host="unix:///var/run/rexray/691450720.sock" route=services server=quill-crystal-si time=1511238713065 tls=false
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="initializing supported cache" host="unix:///var/run/rexray/691450720.sock" server=quill-crystal-si service=vfs storage...me=1511238713066
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="initializing instance ID cache" host="unix:///var/run/rexray/691450720.sock" server=quill-crystal-si service=vfs stora...me=1511238713101
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="http request" host="unix:///var/run/rexray/691450720.sock" route=serviceInspect server=quill-crystal-si time=1511238713137 tls=false
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="successefully dialed libStorage server" host="unix:///var/run/rexray/691450720.sock" server=quill-crystal-si service=v...me=1511238713139
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="storage driver initialized" host="unix:///var/run/rexray/691450720.sock" service=vfs storageDriver=libstorage time=1511238713140
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="os driver initialized" host="unix:///var/run/rexray/691450720.sock" osDriver=linux service=vfs storageDriver=libstorag...me=1511238713156
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="linux integration driver successfully initialized" host="unix:///var/run/rexray/691450720.sock" integrationDriver=linu...te.default.avail
Hint: Some lines were ellipsized, use -l to show in full.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thecodeteam/rexray/issues/1114#issuecomment-345914466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVMMZv0GPyiTbRGm0nP3vvMZhE1Y55sks5s4lNWgaJpZM4Qhbbs
.

Good catch, I hadn't considered that nuance, thanks!
The eventual goal is the docker containers run under dc/os, but for now just testing them at the command line. So I guess I don't need to worry whether rexray.service is running if I am just launching with docker run, correct?

I just performed a test of this locally on a single host.
docker run --net=host -d --name nfs --privileged -v /data1:/nfsshare -e SHARED_DIRECTORY=/nfsshare itsthenetwork/nfs-server-alpine:latest
X_CSI_NATIVE=true X_CSI_DRIVER=csi-nfs rexray start &
docker volume create -o host=<IP_ADDRESS> -o export=/ -d rexray test2
docker run -ti -v test2:/test2 alpine sh

Filesystem           1K-blocks      Used Available Use% Mounted on

overlay                8065444   1629688   6419372  20% /

tmpfs                    65536         0     65536   0% /dev

tmpfs                  1023420         0   1023420   0% /sys/fs/cgroup

<IP_ADDRESS>:/            8065536   1629696   6419456  20% /test2

/dev/xvda1             8065444   1629688   6419372  20% /etc/resolv.conf

/dev/xvda1             8065444   1629688   6419372  20% /etc/hostname

/dev/xvda1             8065444   1629688   6419372  20% /etc/hosts

shm                      65536         0     65536   0% /dev/shm

It is important to mention however that I am experiencing a problem with
the managed plugin, rexray/csi-nfs. As standalone managed via systemctl or
on the cmd line does seem to be working as expected. The error is below
which references a problem with the nfs utilities in the alpine image.

mounting arguments: -t nfs <IP_ADDRESS>:/test1 /dev/csi-nfs-mounts/<IP_ADDRESS>:
#test1

output: flock: unrecognized option: e

BusyBox v1.26.2 (2017-06-11 06:38:32 GMT) multi-call binary.

Usage: flock [-sxun] FD|{FILE [-c] PROG ARGS}

[Un]lock file descriptor, or lock FILE, run PROG

-s Shared lock

-x Exclusive lock (default)

-u Unlock FD

-n Fail rather than wait

mount.nfs: requested NFS version or transport protocol is not supported

mount: mounting <IP_ADDRESS>:/test1 on /dev/csi-nfs-mounts/<IP_ADDRESS>:#test1
failed: Not supported.

On Mon, Nov 20, 2017 at 8:50 PM, Clinton Kitson<EMAIL_ADDRESS>wrote:

Yes, but I am seeing you reference it as rexray/csi-nfs preivously? This
indicates you also have the managed plugin running simultaneously?
On Mon, Nov 20, 2017 at 8:36 PM, Brian Topping<EMAIL_ADDRESS>wrote:

[root@public01 ~]# cat /etc/systemd/system/rexray.service
[Unit]
Description=rexray
Wants=scini.service
Before=docker.service
After=scini.service
[Service]
EnvironmentFile=/etc/rexray/rexray.env
ExecStart=/usr/bin/rexray start
ExecReload=/bin/kill -HUP $MAINPID
KillMode=process
[Install]
WantedBy=docker.service
I just noticed the /etc/rexray/rexray.env file, but it is empty.
[root@public01 ~]# systemctl status rexray
● rexray.service - rexray
Loaded: loaded (/etc/systemd/system/rexray.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2017-11-20 21:31:50 MST; 2s ago
Main PID: 1693 (rexray)
Memory: 7.3M
CGroup: /system.slice/rexray.service
└─1693 /usr/bin/rexray start
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="registered custom context key" externalID=Libstorage-Localdevices internalID=4 keyBitmask=2
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="registered custom context key" externalID=Authorization internalID=5 keyBitmask=2
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="http request" host="unix:///var/run/rexray/691450720.sock" route=services server=quill-crystal-si time=1511238713065 tls=false
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="initializing supported cache" host="unix:///var/run/rexray/691450720.sock" server=quill-crystal-si service=vfs storage...me=1511238713066
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="initializing instance ID cache" host="unix:///var/run/rexray/691450720.sock" server=quill-crystal-si service=vfs stora...me=1511238713101
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="http request" host="unix:///var/run/rexray/691450720.sock" route=serviceInspect server=quill-crystal-si time=1511238713137 tls=false
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="successefully dialed libStorage server" host="unix:///var/run/rexray/691450720.sock" server=quill-crystal-si service=v...me=1511238713139
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="storage driver initialized" host="unix:///var/run/rexray/691450720.sock" service=vfs storageDriver=libstorage time=1511238713140
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="os driver initialized" host="unix:///var/run/rexray/691450720.sock" osDriver=linux service=vfs storageDriver=libstorag...me=1511238713156
Nov 20 21:31:53 public01.mc1.coglative.com rexray[1693]: time="2017-11-20T21:31:53-07:00" level=info msg="linux integration driver successfully initialized" host="unix:///var/run/rexray/691450720.sock" integrationDriver=linu...te.default.avail
Hint: Some lines were ellipsized, use -l to show in full.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/thecodeteam/rexray/issues/1114#issuecomment-345914466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVMMZv0GPyiTbRGm0nP3vvMZhE1Y55sks5s4lNWgaJpZM4Qhbbs
.

I just performed a test of this locally on a single host.
docker run --net=host -d --name nfs --privileged -v /data1:/nfsshare -e SHARED_DIRECTORY=/nfsshare itsthenetwork/nfs-server-alpine:latest
X_CSI_NATIVE=true X_CSI_DRIVER=csi-nfs rexray start &
docker volume create -o host=<IP_ADDRESS> -o export=/ -d rexray test2
docker run -ti -v test2:/test2 alpine sh

Filesystem           1K-blocks      Used Available Use% Mounted on
overlay                8065444   1629688   6419372  20% /
tmpfs                    65536         0     65536   0% /dev
tmpfs                  1023420         0   1023420   0% /sys/fs/cgroup
<IP_ADDRESS>:/            8065536   1629696   6419456  20% /test2
/dev/xvda1             8065444   1629688   6419372  20% /etc/resolv.conf
/dev/xvda1             8065444   1629688   6419372  20% /etc/hostname
/dev/xvda1             8065444   1629688   6419372  20% /etc/hosts
shm                      65536         0     65536   0% /dev/shm

It is important to mention however that I am experiencing a problem with
the managed plugin, rexray/csi-nfs. As standalone managed via systemctl or
on the cmd line does seem to be working as expected. The error is below
which references a problem with the nfs utilities in the alpine image.
mounting arguments: -t nfs <IP_ADDRESS>:/test1 /dev/csi-nfs-mounts/<IP_ADDRESS>:
#test1
output: flock: unrecognized option: e
BusyBox v1.26.2 (2017-06-11 06:38:32 GMT) multi-call binary.

Usage: flock [-sxun] FD|{FILE [-c] PROG ARGS}

[Un]lock file descriptor, or lock FILE, run PROG

-s Shared lock
-x Exclusive lock (default)
-u Unlock FD
-n Fail rather than wait
mount.nfs: requested NFS version or transport protocol is not supported
mount: mounting <IP_ADDRESS>:/test1 on /dev/csi-nfs-mounts/<IP_ADDRESS>:#test1
failed: Not supported.

If you can, I suggest starting over re Docker. Stopping RR, stopping Docker, rm -rf /var/lib/docker, start Docker. Then start RR and I give you an example of above.

I shall, thanks, that use case explains quite a bit. Appreciate you staying up late! Will report back with results.

Sorry for the delay on this on my end, life interruptions. It's top of my stack tho... Happy holidays!

Hi all,
I am getting the "no such file or directory" error when I am installing rexray with the docker plugin command:
 docker plugin install rexray/csi-nfs
error message
mounting /dev/csi-nfs-mounts/dev.example.com: on /var/lib/rexray/docker/volumes/data failed: No such file or directory.
Nevertheless, when I am running the rexray driver directly from the shell as below, it works fine.
X_CSI_NATIVE=true X_CSI_DRIVER=csi-nfs rexray start & docker volume create -o host=<ip> -o export=/vol/data/ -d rexray test5 docker run -ti -v test5:/test5 alpine sh
Is there any extra configuration required when installing Rexray with the docker plugin command?
Thanks!

Hello @benfab,
We did identify a problem in this thread re the rexray/csi-nfs managed plugin missing some dependencies which is why you are getting this error. We will work to get this fixed in the upcoming release.

Just getting back to this, apologies for delay. I saw last two messages between @clintkitson and @benfab, but just noticed there were no changes to the csi-nfs repo.
Clint, as I look back at the thread we were on a couple of weeks ago, it's worth noting a couple of things. The first is that I'm going to be using these elements under DC/OS and I'm kind of assuming that I will eventually have to run rexray as a service rather than standalone. The other is that I'm not going to be able to avoid a situation where the mount point is deep within a folder due to the ZFS constraints that I previously noted.
Is trying this as standalone still a sensible strategy?

@briantopping @clintkitson Did you guys managed to solve the issue? I'm getting the same errors here.

@IAPOLINARIO Looking into it for this next release. There are really two things in this issue 1) lack of example docs 2) the plugin itself doesn't have the right dependencies. Outside of the docker managed plugin it does work with examples listed here.

I am assuming the NFS error that is occurring is related to what Alpine supports. This could be remedied with building the csi-nfs managed plugin using Ubuntu as the base instead to accommodate.
For example https://hub.docker.com/r/cpuguy83/nfs-client/~/dockerfile/

@clintkitson Thanks for the quick answer.
Let me see if I understood how to configure RR as a service (using CSI-NFS):
Step 1: install RR curl -sSL https://dl.bintray.com/emccode/rexray/install | sh
Step 2: Create a configuration file at /etc/rexray/config.yml
Step 3: Start RR service with sudo X_CSI_NATIVE=true X_CSI_DRIVER=csi-nfs rexray start
Step 4: Create a volume rexray volume create pg_data --size=20
Step 5: Run the container using the pre-created volume: docker run -dit --name pg -e POSTGRES_PASSWORD=mysecretpassword --volume-driver=rexray -v pg_data:/var/lib/postgresql/data postgres
Am I missing something? Are there any other steps before those?
And I still have some questions:
1 -How the file /etc/rexray/config.yml should be configured to work with CSI-NFS?
2 - How can I change the mount point from /dev to /another-volume?
3 - What the option -o host=<IP_ADDRESS> mean?
4 - What the option -o export=/ mean?
Thanks in advance for your help.

@IAPOLINARIO: A few things:

I am running RR on a machine installed with DC/OS. I haven't looked at the origin of the package, but it has an env vars file in /etc/rexray. I put the env vars in there, no additional configuration is necessary, although the default came with a vfs service that I removed as it was giving parse errors.
Your step 4 needs to have the -o host=<IP_ADDRESS> -o export=/. The host is the NFS server, the export is the directory on that server that is being exported. These are the two fields that a typical mount command defines as host:export at the end of the command line.
Turn on maximum debugging to help you see what's going on. There are three areas, for RR itself, for libstorage, and for the plugin (documented in the plugin README, added to the env variables).

The errors in RR are good if you know the internal sequence of events, but it will take some sleuthing in the source if you see an error. Best thing you can do is look at the most recently emitted debug statement, search the source, then figure out from there.
With all that, I was able to get connections, what I am having problems with at this point are more permission related.

@briantopping Worked! Tks for your help.
Taking the chance: @clintkitson is there any plan to release a version that supports DELL SC8000?

@IAPOLINARIO How you found the correct configuration for the /etc/rexray/config.yml?


Infinite event loop with empty items array

If input array is empty the component enters infinite update event loop.
I think the reason is
if (start !== this.previousStart || end !== this.previousEnd) {
is always true when NaN value is involved.
The fix seems a bit more elaborate than just fixing the condition when no initial item sizes are given, it needs to re-init when going from empty to non-empty items and vice versa.

Meantime the below and this seem working as a quick fix to make the component functional
    start = !isNaN(start) ? start : -1;
    end = !isNaN(end) ? end : -1;
    if (start !== this.previousStart || end !== this.previousEnd) {


Complex Dynamic Keys

I'm trying to map this rather complex JSON response and am hoping to get some feedback on what I'm doing wrong.
A group has statistics about it's progress progress.
My JSON
"stats": {
      "2017": {
        "1": {
          "results": {
            "1": 13,
            "2": 3,
            "3": 1,
            "4": 1,
            "5": 0
          },
          "roi": 0.40337966202464975,
          "win": 0.8181818181818182
        },
        "2": {
          "results": {
            "1": 13,
            "2": 5,
            "3": 1,
            "4": 2,
            "5": 1
          },
          "roi": 0.26852551067922953,
          "win": 0.717948717948718
        }
      }
}

My models:
class GroupResponse: Mappable {
    var stats: [String: [String: StatsMonthResponse]]?

    func mapping(map: Map) {
        stats               <- map["stats"]
    }
}

class StatsMonthResponse: Mappable {
    var tips: [String: Int]?
    var roi: Double?
    var win: Double?

    func mapping(map: Map) {
        tips    <- map["results"]
        roi     <- map["roi"]
        win     <- map["win"]
    }
}

What I get
The response I get has the stats property in my GroupResponse class, as nil.
What other approach could I do to accomplish this, or change in my implementation to get this done?

Here's my approach: https://stackoverflow.com/questions/44806608/objectmapper-nested-dynamic-keys/44848499#44848499


Graph Encoder Decoder

❓ Questions and Help
Is it possible to have supervised end-to-end Graph neural network for Encoder-Decoder architecture, where both, input and output graphs are of different topology.
Example: Summarization, when both, original text and its summary are modeled as graphs with different topologies.
Does DGL or Graph4nlp support such supervised learning architecture?
If yes, there is another use-case for such GNN, in geometric modeling, explained in details at https://github.com/yogeshhk/MidcurveNN  just FYI

Thanks for your valuable opinion.
I think you mean the graph-to-graph applications, in which one cast the inputs (texts, graphs, etc.) to graph and then predicts another graph as output.
If yes, we highly recommend you our survey paper: Graph Neural Networks for Natural Language Processing: A Survey. We have comprehensively discussed this topic.
As for the code, currently, there are no exactly graph2graph examples in our library. However, Graph2Tree is a close task.

I will close this issue.


Methodically test and correct exception handling

There are many ways steps in which this package might fail mid-stream, and I need to make sure they're all handled in a sane way. This blocks officially supporting this as a Debian package.

Making slow progress on this, but it's getting better. Problem is that I need to set up a test rig (ideally a VM with a virtual TPM) that I can repeatedly screw up and reset to an initial state: right now I only make progress here when I'm setting up a new machine, which isn't that often.

I only make progress here when I'm setting up a new machine, which isn't that often.

You can use proxmox as a virtual machinу on your host. As far as proxmox supports nested virtualization, you can create a vm inside proxmox with tpm2.0 enabled and play with it. It works just fine. As a bonus of this approach you will have snapshots and cloning capabilities which might save you plenty of time.


Support for multiple authentication methods

Why?
There are different ways to connect to clickhouse. We should support as many as we can#18
Acceptance

It's possible to configure the datasource with:

[x] TCP
[x] TLS

[x] With a custom CA cert
[x] With TLS Skip
[x] With MTLS

[ ] ...?

@scottlepp looking at the code, this seems mostly done? Is there any other way to connect to clickhouse that we're not currently supporting?

@kirederik its possible to connect over http vs the native tcp protocol.  However that seems just an alternative that we don't need to support (unless the clickhouse-go driver has some unforeseen limitations).
Fixed by #21


env var for cypress results dir

https://issues.redhat.com/browse/RHOAIENG-8771
cc @manosnoam
Description

Provides a way to set the results dir output location when running cypress tests.
How Has This Been Tested?

Set the CY_RESULTS_DIR env variable:
CY_RESULTS_DIR=~/dev/cypress/results npm run cypress:run:mock -- -s "**/application.cy.ts"
Test Impact

N/A
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

cc @manosnoam

Thanks @christianvogt for this PR!
Since it's an Env variable and not a direct argument to the npm script (i.e -- --arg=value), it might override other Env variables in a CI job that uses "RESULTS_DIR".
Would it be possible to use either:

Direct arg like: npm run cypress:run:mock -- --results-dir=./cypress_results
or
Unique env var for cypress: "CYPRESS_RESULTS" (instead of "RESULTS_DIR")

@manosnoam i went ahead and added the prefix of CY_ to all the cypress env variables.


Use json prettyPrint in downloadApolloSchema

Hello!
In Apollo 3.0.0 result scheme.json generated as json with prettyPrint flag.
But in Apollo 3.4.0 file saved as one line without prettyPrint flag.
With prettyPrint flag, it is more convenient to track changes, is it possible to return it?

Thanks! This format is really better
The task can be closed.


US_1128025

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Exchange-Server-2013/configure-database-availability-group-properties-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/configuring-push-notifications-proxying-for-owa-for-devices-exchange-2013-help.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Exchange-Server-2013/configure-database-availability-group-properties-exchange-2013-help.md
:white_check_mark:Succeeded
View

Exchange-Server-2013/configuring-push-notifications-proxying-for-owa-for-devices-exchange-2013-help.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Exchange-Server-2013/configuring-push-notifications-proxying-for-owa-for-devices-exchange-2013-help.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


XMPP and indirect SMS/IoT support?

## Feature Request
Would be nice if there was also an option to react to and send XMPP messages. There are already quite a few django related XMPP projects, so it should be probably easy to integrate. For example this:
https://github.com/alexmorozov/django-jabber
seems like it could easily push to XMPP?
You can also easily get a free XMPP account for testing purposes on a service like jix.im
There are also a lot of interesting further bridges for XMPP (see for example http://spectrum.im/ ). In addition you can quite easily link a XMPP account to a SMS sending service, and XMPP is also emerging as a IoT interoperability standard.

Or maybe more general, this:
https://github.com/idlesign/django-sitemessage

If you want to contribute, feel free to reopen it
Otherwise I plan to rewrite everything with starlette.io


More Components

Are you accepting the component from more users?If it is possible will you consider adding the checkout form or different cards in your library if so please let me know I will be happy to add those in the library. Please let me know

Hi shubhsk88,
Yes you can add any components of your choice, the only conditions are :

Responsive
Coded only with Tailwind CSS 2.0 classes
Filed in the right category
Design is subjective, all styles are accepted but code of the components/templates must be clean

If you want add components or templates, just do a PR and I will review it :)
I have updated the readme to explain how to create new components/templates.

Hi shubhsk88,
Yes you can add any components of your choice, the only conditions are :

Responsive
Coded only with Tailwind CSS 2.0 classes
Filed in the right category
Design is subjective, all styles are accepted but code of the components/templates must be clean

If you want add components or templates, just do a PR and I will review it :)
I have updated the readme to explain how to create new components/templates.

Thanks I will open a PR as soon as I am done with it

Thanks I will open a PR as soon as I am done with it


Refactored login screen

I need to write some specs here and clean up a few things still. So feel free to tell me what I'm doin wrong here.

Should be fine to merge @broskoski

🤙


feat: Add Animated Background Gradient

Implemented a dynamic animated gradient background on the webpage using HTML, CSS, and JavaScript. The gradient smoothly transitions through a range of colors, creating a visually appealing and lively background effect. This design technique adds a touch of vibrancy to the website without compromising on loading times, as it avoids heavy video backgrounds. The animation is achieved through CSS keyframes, creating a continuous loop for a seamless experience. Feel free to customize the colors and duration to suit the desired visual aesthetic. Tested and ready for deployment."

connect with me -
Github : https://github.com/Durgesh4993
LinkedIn : https://www.linkedin.com/in/durgesh4993/

sorry @malivinayak you need to create your own issues, i'll assign you


feat(execution): compress visited PCs

This change is

Codecov Report
Attention: 19 lines in your changes are missing coverage. Please review.

Comparison is base (e6c69c6) 69.98% compared to head (efef268) 70.30%.
Report is 10 commits behind head on main.

:exclamation: Current head efef268 differs from pull request most recent head 0014049. Consider uploading reports for the commit 0014049 to get more accurate results

Files
Patch %
Lines

crates/blockifier/src/execution/contract_class.rs
77.35%
12 Missing :warning:

.../blockifier/src/blockifier/transaction_executor.rs
33.33%
4 Missing and 2 partials :warning:

crates/native_blockifier/src/py_block_executor.rs
83.33%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1564      +/-   ##
==========================================
+ Coverage   69.98%   70.30%   +0.32%
==========================================
  Files          59       59
  Lines        8220     8339     +119
  Branches     8220     8339     +119
==========================================
+ Hits         5753     5863     +110
- Misses       2002     2015      +13
+ Partials      465      461       -4

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


[BUG]: Compatibility issues with CSM Authorization and CSM Observability's Topology

Bug Description
When Authorization and Observability are installed in the same cluster, topology pod will report error logs and Grafana dashboard doesn't display values.
Logs
http: panic serving ip: runtime error: invalid memory address or nil pointer dereference
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce

install CSM Authorization and CSM Observability in one cluster
import topology dashboard to Grafana, then the topology pod will report error logs, and Grafana dashboard will display no values.

Expected Behavior
Grafana topology dashboard should display values.
CSM Driver(s)
N/A
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
N/A
Operating System
N/A

Closing this since after investigation it is not a compatibility issue. Going forward, work will be tracked in https://github.com/dell/csm/issues/430.


[Instance Assignment] Plug in instance assignment

Add instance assignment APIs including:

GET/PUT/DELETE instance partitions
Assign instances for a table
Replace instance in instance partitions

Assign instances if necessary while creating/updating table config
Backward-compatible, no change to the cluster if instance assignment is not configured

Codecov Report

Merging #4516 into master will decrease coverage by 0.05%.
The diff coverage is 73.66%.

@@             Coverage Diff              @@
##             master    #4516      +/-   ##
============================================
- Coverage     64.72%   64.67%   -0.06%
  Complexity       20       20
============================================
  Files          1073     1074       +1
  Lines         55710    55858     +148
  Branches       8116     8148      +32
============================================
+ Hits          36061    36127      +66
- Misses        16996    17075      +79
- Partials       2653     2656       +3

Impacted Files
Coverage Δ
Complexity Δ

...a/org/apache/pinot/core/util/ReplicationUtils.java
90.9% <ø> (+11.96%)
0 <0> (ø)
:arrow_down:

...ent/instance/InstanceReplicaPartitionSelector.java
97.8% <ø> (-0.03%)
0 <0> (ø)

...ache/pinot/common/metadata/ZKMetadataProvider.java
67.41% <ø> (-1.82%)
0 <0> (ø)

.../assignment/instance/InstanceAssignmentDriver.java
96.29% <100%> (+0.46%)
0 <0> (ø)
:arrow_down:

...ller/helix/core/assignment/InstancePartitions.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

...helix/core/assignment/InstancePartitionsUtils.java
38.23% <47.61%> (+8.23%)
0 <0> (ø)
:arrow_down:

...ources/PinotInstanceAssignmentRestletResource.java
67.2% <67.2%> (ø)
0 <0> (?)

.../controller/helix/ControllerRequestURLBuilder.java
83.87% <76.92%> (-1.85%)
0 <0> (ø)

...config/instance/InstanceAssignmentConfigUtils.java
78.94% <80%> (+3.94%)
0 <0> (ø)
:arrow_down:

...ntroller/helix/core/PinotHelixResourceManager.java
62.92% <92.59%> (+0.48%)
0 <0> (ø)
:arrow_down:

... and 39 more

Continue to review full report at Codecov.

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

@snleee Uniformed the API to /tables/{tableName}/instancePartitions


Retrieve the URLs of images downloaded from browser cache

I have been running Image Picka for some time with the "Try to download image from browser cache" option turned on. This option itself is working fine. The issue is that when I now go to the images in my download history, and right-click & select "Copy Download Link", I get a URL that looks like "blob:moz-extension://..." instead of a proper original URL.
Is there a way to retrieve / convert the original download URL from these blobs? Where do I find the blobs?
Any help would be appreciated!

Blob URL is a URL pointing to a "blob object",  which is a cached image in this case.
The download process looks like this:

The extension looks into the webpage and find all images, extracts their URLs.
The extension sends requests to retrieve cached data. (the cached image)
The extension creates a blob URL pointing to the cached data, then send the blob URL to download manager.

Therefore, the download manager doesn't know the original URL of the image, but only the blob URL.

Is there a way to retrieve / convert the original download URL from these blobs? Where do I find the blobs?

You can't. After downloading complete, the blob is deleted to save memory.

The only way to fix this is to make download manager support downloading from cache, then we don't need the 2nd step and we can send the original URL to download manager directly.
See also: https://bugzilla.mozilla.org/show_bug.cgi?id=1698863

Thank you for the clarification.
I was kinda expecting as much, given that we are talking about cached images.
PS Also, thanks again for this awesome extension.


Allow selection of VS version

Summary
A user should be able to select the version of VS they want UA to use for loading project files.
Motivation and goals
VS can be installed side by side and multiple versions can exist on the same machine at a time. Since UA will use VS locations to locate target files, this can pose problems when only one version has a required workload.
In scope

Pass in VS path via command line
Provide selection step for VS version if not available and multiple exist

Out of scope

None known

Risks / unknowns

Many users appreciate the non-interactive mode. There should be a way to continue using UA in non-interactive mode with multiple VS instances available

Examples
upgrade-assistant upgrade [path] --vs-path [path]

See #723 for original issue


Pytmv1 - Initial commit

Description
Pytmv1 - Initial commit
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Update of pytmv1 code into GH


Allow protocol features to be activated in genesis.json.

Change Description

When starting a new chain without --genesis-json, include all protocol features.
A few changes related to loading the genesis state from a snapshot were cherry picked from #8223.
Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

There is a comment here
https://github.com/EOSIO/eos/blob/0c7b42887a8701a6877802817de9ce20e4345f71/libraries/chain/controller.cpp#L457
about something needing to be changed if wtmsig is enabled at genesis. Does anything need to be done there?

Does anything need to be done there?

Yes, it should be updated, but I think it will work without changes.
When wtmsig_block_signatures is activated, it does not trigger an update of pending_schedule.schedule_hash.

@swatanabe-b1 Is this in a state that it is worth merging develop into it (with the submodules pain) and then doing a review to get it in, or should it be closed?

This needs some updates to be ready.

The kv configuration and wasm configuration need to be included in the genesis file.
The genesis file needs to include a version.
We need to make a decision about what nodeos should use as the default genesis state.
I meant to update it after the KV PR went in, but I've been on other tasks since then.


Error Buffered payment thread shutdown. Miners are not getting paid.

*Description of issue:
plugin doesn't pay Miners when they breaks blocks. and the following error popped out.
ERROR (DELETE IF YOU HAVE NO ERROR):
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: java.lang.NullPointerException
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at net.tnemc.core.common.api.IDFinder.getID(IDFinder.java:139)
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at net.tnemc.core.common.api.TNEAPI.hasAccount(TNEAPI.java:182)
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at net.tnemc.core.common.api.Economy_TheNewEconomy.hasAccount(Economy_TheNewEconomy.java:67)
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at net.tnemc.core.common.api.Economy_TheNewEconomy.depositPlayer(Economy_TheNewEconomy.java:188)
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at net.tnemc.core.common.api.Economy_TheNewEconomy.depositPlayer(Economy_TheNewEconomy.java:182)
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at com.gamingmesh.jobs.economy.VaultEconomy.depositPlayer(VaultEconomy.java:32)
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at com.gamingmesh.jobs.economy.BufferedEconomy.payAll(BufferedEconomy.java:158)
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at com.gamingmesh.jobs.tasks.BufferedPaymentThread.run(BufferedPaymentThread.java:48)
[19:50:02] [Jobs-BufferedPaymentThread/INFO]: [Jobs] Exception in BufferedPaymentThread, stopping economy payments!
[19:50:02] [Jobs-BufferedPaymentThread/INFO]: [Jobs] Buffered payment thread shutdown.

https://pastebin.com/g2UU3uNk
for easier view

CONFIG SECTION (DELETE IF NOT RELEVANT):
mysql:
  username: root
  password:
  hostname: localhost:3306
  database: jobs
  table-prefix: jobs_
  verify-server-certificate: false
  use-ssl: false
  auto-reconnect: true

no sure if it's a problem with MySQL

Server Type (Spigot/Paperspigot/etc):
Paperspigot
Server Version (using /ver):
1.16.1
Relevant plugins (Delete if this isn't needed):
Jobs reborn ver. 4.16.0
Economy plugin is The New Economy

[19:50:02] [Jobs-BufferedPaymentThread/WARN]: java.lang.NullPointerException
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at net.tnemc.core.common.api.IDFinder.getID(IDFinder.java:139)
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at net.tnemc.core.common.api.TNEAPI.hasAccount(TNEAPI.java:182)
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at net.tnemc.core.common.api.Economy_TheNewEconomy.hasAccount(Economy_TheNewEconomy.java:67)
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at net.tnemc.core.common.api.Economy_TheNewEconomy.depositPlayer(Economy_TheNewEconomy.java:188)
[19:50:02] [Jobs-BufferedPaymentThread/WARN]: 	at net.tnemc.core.common.api.Economy_TheNewEconomy.depositPlayer(Economy_TheNewEconomy.java:182

So this is The New Economy issue not Jobs.