CI and GreenKeeper

I'm looking at trying to get the /spec directory and some configs sorted out so we could potentially use Travis CI and GreenKeeper to try to limit issue sources. @Sorunome, do you think this is worth perusing? Right now (working in my fork), I've found that arduino-upload-view-spec.coffee introduces an impossible test, so I've removed. but arduino-upload-spec.coffee throws a few errors as well.
~$ apm test
FF

ArduinoUpload
  when the arduino-upload:toggle event is triggered
    it hides and shows the modal panel
      Expected '
<button click="close" class="btn">close</button>

' not to exist.
        at jasmine.Spec.<anonymous> (file:///C:/Users/Res/Desktop/arduino-upload/spec/arduino-upload-spec.coffee:19:66)
      TypeError: Cannot read property 'isVisible' of null
        at jasmine.Spec.<anonymous> (file:///C:/Users/Res/Desktop/arduino-upload/spec/arduino-upload-spec.coffee:35:31)
        at <anonymous>
    it hides and shows the view
      Expected '
<button click="close" class="btn">close</button>

' not to exist.
        at jasmine.Spec.<anonymous> (file:///C:/Users/Res/Desktop/arduino-upload/spec/arduino-upload-spec.coffee:48:66)
      Expected '
<button click="close" class="btn">close</button>

' to be visible.
        at jasmine.Spec.<anonymous> (file:///C:/Users/Res/Desktop/arduino-upload/spec/arduino-upload-spec.coffee:60:34)
        at <anonymous>

Finished in 0.215 seconds
2 tests, 7 assertions, 4 failures, 0 skipped

Tests failed

@Sorunome sorry for the silence. I've gotten dragged in a completely different direction by a number of things. Atom fell back on Electron4 (going against my rolling release mentality and pushing me to Neovim, a tool I had been using for quite some time now) and I've started playing with FPGAs, Assembly, Java, Machine Learning, and SysAdmin stuff to boot. I still intend on helping out wherever possible but this project is currently on the back-burner as I keep getting thrown stray projects at college.
One idea I had been working on for a revamp (to address several issues all at once) was to dump the Arduino IDE dependency and board selection stuff and just add hooks for Arduino-Makefile support. It would be a little jarring for current users but way faster and make board support and selection way cleaner. Just a thought. Best of luck with this project, dude.


[BUG] "Invalid condition" when editing a sigma rule that uses wildcard notation

What is the bug?
When you clone/edit an existing simga rule using the dashboard GUI - there are many rules which use a wildcard pattern notation in the conditional. (see screenshots). You cannot edit/save these rules because the dashboard GUI validation thinks this notation is invalid. Additionally, if you want to modify a rule and use wildcard notation - youcannot save the change using the dashboard gui.
How can one reproduce the bug?
Steps to reproduce the behavior:

Clone and edit a rule which contains wildcard notation
Try saving the rule and you will see the red error text preventing continuation
See screenshot below.

What is the expected behavior?
A clear and concise description of what you expected to happen.
What is your host/environment?

OS: 2.10 fresh install with security analytics plugin

Do you have any screenshots?

I am not sure if I should open a seperate ticket - but I found a couple more instances where the GUI validation seems to not play well with the SIGMA rule editor screen. Rather than opening a new ticket to provide the new information I thought I would start by adding it here.
Getting a validation error when editing a clone of a rule for some author names:

Also getting the following GUI validation error on certaing rule where the tag: field within the rule starts with something other than "attack."


Release snapshots to feedz.io

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #148 opened

Start Time: 2021-06-01T03:30:15.241+0000

Duration: 25 min 8 sec

Commit: 90eefb7e7f289c4b55561993559bf6235e2cc2fc

Test stats :test_tube:

Test
Results

Failed
0

Passed
78

Skipped
0

Total
78

Trends :test_tube:


Add troubleshooting guidance development section of enketo-core README.

Hello Enketo maintainers 👋.
This PR adds solutions to small problems I encountered during my first install of the enketo-core development environment on my M1 Mac using nvm. I'm new to the enketo code base, so I understand if these hints don't make sense to include from your perspective. No pressure to land this if they don't. I just wanted to offer the solutions I found to the problems I had when getting started. Also happy to edit these hints to be more appropriate from your perspective if you have feedback.
I have verified this PR works with

[x] Online form submission
[x] Offline form submission
[x] Saving offline drafts
[x] Loading offline drafts
[x] Editing submissions
[x] Form preview
[x] None of the above

What else has been done to verify that this works as intended?
This is a readme change only.
Why is this the best possible solution? Were any other approaches considered?
I wrote down solutions to problems that I encountered as I experienced them first hand.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Not applicable.
Do we need any specific form for testing your changes? If so, please attach one.
None needed.

[ ] Recommend Volta more strongly / add a generic troubleshooting item around node version instead of a specific one for the current versions https://github.com/enketo/enketo/pull/1338#discussion_r1714307935
[ ] Make sure all the package readmes point to the root readme for run instructions, add top-level instructions for managing node versions https://github.com/enketo/enketo/pull/1338#discussion_r1720089978
[ ] Remove address in use item https://github.com/enketo/enketo/pull/1338#discussion_r1714245498


Cannot switch to local stoarage, GitLab sync cannot be removed from Figma file

Describe the bug
I have imported a document into my Figma account that was originally synced with Tokens Studio and GitLab. When I start the Tokens Studio plugin on this file, I get the message "Couldn't load tokens stored on GitLab". I don't use GitLab and want to store the tokens locally, but the GitLab data seems to stuck somewhere in the file and I cannot get rid of them. Whenever I create new Tokens, leave TS and re-open TS again I get the same GitLab error message and all my tokens are gone.
To Reproduce
Steps to reproduce the behavior:

Export a Figma file with styles managed with Tokens Studio and a GitLab sync
Import this .fig file into another Figma account

To reproduce from here use the provided Link

Open that file and start the Tokens Studio plugin
Result: Error message, you can only click "Enter Credentials"
You don't have access to GitLab nor the credetials so you only can cancel the following credential dialog.
Result: No Tokens loaded
Create some new Tokens in this file
Close Tokens Studio
Re-open Tokens Studio
You will be asked "Recover local change?".
Click yes
You get the Missing Credentials message again
You again cannot enter the credentials, so you only can cancel the dialog.
Go back to the "Tokens" tab
All Tokens are gone.

Expected behavior
When Tokens Studio recognizes a missing sync credential it should also offer a way to set the storage to "local".
Or at least, somewhere in the settings should be the option to switch to local stoarage.
Screenshots or Screencasts

Figma file (optional)
https://www.figma.com/file/Xr5LAnhE6bHZ6QvSNqkoHU/iX-Foundation-Classic-Dark?type=design&node-id=0-1&mode=design&t=vxezPSwpSPBypgJu-11

Migrated to Featurebase


chore: release 0.11.2

:robot: I have created a release *beep* *boop*
0.11.2 (2022-06-20)
Bug Fixes

add executableName (40062b2)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ethersphere/bee-desktop/releases/tag/v0.11.2 :sunflower:


add onboarding temporarily in leadership.

See meeting minutes from 9/19/2018
(copied from minutes)
Nicole: Is the mentorship analysis / concept already incorporated in the current set of metrics we have so far? (Leadership Category)
Add questions related to the existence of mentorship programs, and check if there are mentorship programs focused on underrepresented groups of people.
Eg: Outreachy or GSoC, or internal programs such as the Upstream Program by the OpenStack Foundation.
Study on patterns or anti patterns, work done at Kubernetes
Look at the rate of newcomers
Result from OpenStack:
Mentoring via Outreachy lead to longer participation
Need to explore this metric
Data from Google Summer of Code as well
Level of contribution and longevity were positively impacted
Both K8s and OS have solid ways of welcoming newcomers
Want to make sure this is reflected in some way
On boarding may be seen as the umbrella for helping newcomers, and mentorship might be part of this. Others may apply.
Metrics:
Type of onboarding: 1:1, 1:x, groups
Ascending membership ladders (e.g. member -> reviewer -> maintainer)
Inclusion in decision-making (e.g. elections, OWNERS files)
Governance leadership: SIG leader, Steering Committee membership
In speed mentoring program (OS, and Linux communities)
Paris Pittman on mentoring: https://thewomenintechshow.com/2018/06/11/scaling-mentorship-in-kubernetes-with-paris-pittman/

This is saying that onboarding is role of leadership?  Or falls under leadership?

No, it is a placeholder only. During the meeting, we were discussing to put
onboarding as a new focus area.

@GeorgLink can you please merge your local codebase with the latest changes and commit ?   I'l lbe able to merge then. thank you!

Thanks Emma. I merged the local codebase. Merge conflict is resolved

Thank again!


highly available ?

Description
Hello, looking through the documentation https://github.com/fnproject/docs/blob/master/fn/operate/runner_pools.md.
This scheme deployed  multiple "fn-runner", but it has  single points of failures as well.
If  the application must be  highly available, how to deploy  fn-node on some  machines  as  cluster?
Additional environment details (OSX, Linux, flags, etc.):
Containers: 12
 Running: 10
 Paused: 0
 Stopped: 2
Images: 224
Server Version: 18.09.0
Storage Driver: overlay2
 Backing Filesystem: xfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Security Options:
 seccomp
  Profile: default
Kernel Version: 3.10.0-957.21.3.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 4
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Registry Mirrors:
http://hub-mirror.c.163.com/
Live Restore Enabled: false

Hi, have you seen Fn Helm charts?


  That shouldn't be necessary.
There's another thing i'm having difficulty telling from the diffs, but I assume it compiles :).  When retrieving the support for aniso and storing the max aniso value, that info is gathered in GVRViewManager, but the variables are declared in GVRContext.  I think i'll have to do a check-out and look at the full source file.

Hi @thomasflynn ,
We removed the .so files in the last commit. This happeened because of the modification in the .gitignore file which now allows for .so files to be tracked.
The aniso varible was declred in the GVRContext and the calculation was done in the GVRViewManager becuase we had to be run the aniso code on the gl thread and make the value available as public api. Since the GVRViewManager extends the GVRContext, it looked like a good place to put those things.
Please let us know if you find any more issue.

Thanks, that's what I was missing.  Makes sense now.


Speed up docs CI/DC

Is your feature request related to a problem? Please describe.
Docs build slow.
Describe the solution you'd like
The plugins are already tested separately. It would be great if the docs were also built on a plugin-per-plugin basis, since typically contributions target one specific plugin at a time.

yes, we can run them with papermill and then jupyterbook just combines them,
the main tricky part is to avoid the execution that do not work :) or catch any errors


Add cupyx.scipy.ndimage.grey_erosion and cupyx.scipy.ndimage.grey_dilation

This PR is to support scipy.ndimage.grey_erosion and scipy.ndimage.grey_dilation in CuPy.

Measured results on Quadro GV100 and CUDA 10.2
( grey_erosion, dtype:int32, footprint:None )

mean (stdev) [unit: ms]
SciPy
CuPy
speedup

shape:(1000, 1000), size:3, structure:None
8.141 (0.096)
0.331 (0.007)
24.6

shape:(1000, 1000), size:5, structure:None
8.155 (0.080)
0.367 (0.005)
22.2

shape:(1000, 1000), size:7, structure:None
8.256 (0.113)
0.441 (0.016)
18.7

shape:(2000, 2000), size:3, structure:None
50.188 (17.763)
0.516 (0.002)
97.3

shape:(2000, 2000), size:5, structure:None
47.706 (17.059)
0.743 (0.010)
64.2

shape:(2000, 2000), size:7, structure:None
43.215 (12.248)
1.036 (0.002)
41.7

shape:(4000, 4000), size:3, structure:None
283.721 (2.885)
1.203 (0.003)
235.9

shape:(4000, 4000), size:5, structure:None
284.863 (2.372)
2.085 (0.005)
136.6

shape:(4000, 4000), size:7, structure:None
285.476 (2.791)
3.274 (0.002)
87.2

shape:(100, 100, 100), size:3, structure:None
10.205 (0.051)
0.352 (0.004)
29.0

shape:(200, 200, 200), size:3, structure:None
101.400 (0.636)
1.243 (0.003)
81.6

shape:(300, 300, 300), size:3, structure:None
341.785 (0.478)
3.484 (0.005)
98.1

shape:(1000, 1000), size:3, structure:random
37.608 (0.049)
0.329 (0.012)
114.3

shape:(1000, 1000), size:5, structure:random
111.643 (0.379)
0.397 (0.023)
281.1

shape:(1000, 1000), size:7, structure:random
222.572 (0.804)
0.481 (0.025)
462.6

shape:(2000, 2000), size:3, structure:random
151.798 (1.905)
0.565 (0.005)
268.5

shape:(2000, 2000), size:5, structure:random
447.465 (2.728)
0.784 (0.002)
570.8

shape:(2000, 2000), size:7, structure:random
891.057 (2.194)
1.092 (0.003)
816.3

shape:(4000, 4000), size:3, structure:random
619.138 (0.790)
1.262 (0.005)
490.8

shape:(4000, 4000), size:5, structure:random
1801.868 (1.595)
2.125 (0.005)
847.8

shape:(4000, 4000), size:7, structure:random
3577.451 (4.309)
3.350 (0.005)
1067.9

shape:(100, 100, 100), size:3, structure:random
120.812 (0.331)
0.403 (0.014)
299.5

shape:(200, 200, 200), size:3, structure:random
966.162 (1.004)
1.305 (0.004)
740.3

shape:(300, 300, 300), size:3, structure:random
3290.474 (1.351)
3.548 (0.003)
927.4

test script
import numpy
import scipy.ndimage as ndimage
import cupy
import cupyx.scipy.ndimage as cpx_ndimage
import time
from statistics import mean, stdev

nmeasure = 10
dtype = numpy.int32
structure = None
size_set = [
    [2, 1000, 3],
    [2, 1000, 5],
    [2, 1000, 7],
    [2, 2000, 3],
    [2, 2000, 5],
    [2, 2000, 7],
    [2, 4000, 3],
    [2, 4000, 5],
    [2, 4000, 7],
    [3, 100, 3],
    [3, 200, 3],
    [3, 300, 3],
]

for st in (None, 'random'):

    for j in range(len(size_set)):
        ndim = int(size_set[j][0])
        x_size = int(size_set[j][1])
        shape = (x_size,) * ndim
        size = int(size_set[j][2])
        if st is None:
            structure = None
        else:
            structure = numpy.random.random((size,) * ndim) * 10
            structure = structure.astype(numpy.int32)

        cpu_time = []
        gpu_time = []
        for i in range(nmeasure+1):
            x = numpy.random.random(shape).astype(dtype)
            cp_x = cupy.array(x)

            t1 = time.time()
            y = ndimage.grey_erosion(x, size=size, structure=structure)
            elapsed_ms = (time.time() - t1) * 1000
            if i > 0:
                cpu_time = cpu_time + [elapsed_ms]

            t1 = time.time()
            cp_y = cpx_ndimage.grey_erosion(cp_x, size=size, structure=structure)
            cupy.cuda.runtime.deviceSynchronize()
            elapsed_ms = (time.time() - t1) * 1000
            if i > 0:
                gpu_time = gpu_time + [elapsed_ms]

            cupy.testing.assert_array_almost_equal(cp_y, y)

        print('shape:{}, size:{}, structure:{} | {:.3f} ({:.3f}) | {:.3f} ({:.3f}) | {:.1f}'.format(shape, size, st, mean(cpu_time), stdev(cpu_time), mean(gpu_time), stdev(gpu_time), mean(cpu_time) / mean(gpu_time)) )

pfnCI, test this please.

Jenkins CI test (for commit 6d6aed0ae600a7995ddd1c43be12a612850a8a48, target branch master) succeeded!

Thanks for your review! I fixed the PR based on your feedback. Could you run CI tests?
Thanks!

pfnCI, test this please.

Jenkins CI test (for commit b0171d91e0de2c2138e503e3701e4a196c7b5078, target branch master) succeeded!


pre-commit hook does not work on Windows

When I try to use the pre-commit hook on Windows it always fails with
UnicodeEncodeError: 'charmap' codec can't encode character '\u2705' in position
1: character maps to <undefined>

or
UnicodeEncodeError: 'charmap' codec can't encode character '\u274c' in position
1: character maps to <undefined>

The unicode characters mentioned in the error are ✅ and ❌.
I tried it in cmd, Powershell and Git Bash and always got these errors.
I can reproduce this issue by just creating an empty git repo with just a .pre-commit-config.yaml with:
repos:
  - repo: https://github.com/scientific-python/cookie
    rev: 2024.04.23
    hooks:
      - id: sp-repo-review

and running pre-commit run --all-files.

As a quick fix, you can set PYTHONUTF8=1 and I think that will fix it (Python 3.15 would fix it too, but that's a couple of years away). Something is missing the encoding specifier, hopefully in repo-review or sp-repo-review. Will check.

This has been fixed in https://github.com/scientific-python/repo-review/releases/tag/v0.11.1 - though pre-commit caches globally, so there will be a new release here soon which should ensure that gets picked up.

Fixed in latest releases!


[POC] Add support for Material You (add new component)

What's the PR about
This is a proof of concept of how we can add support for Material You incrementally without introducing breaking changes (see https://github.com/mui/material-ui/issues/29345) and at the same time allow the new components to co-exist in an environment where @mui/material is used. This would mean that we would support both Material Design 2 and Material Design 3 in parallel. In a future major release, we can then drop the support for MD2.
👉 Playground link (inspired by https://github.com/mui/material-ui/issues/29345#issuecomment-1163463199)
👉 Default theme showcase link - it should work without using CssVarsProvider
👉 Showcase of coexisting with @mui/material (Material Design 2) link

Implementation details
This POC uses a new factory for creating a Material Design 3 theme. It adds behind the scenes a new useMaterialYou flag, and adds the necessary design tokens for the new design systems (the palette values are added under under palette.md3, and all other tokens are under the md3 key so that we can avoid conflicts with the existing theme).
Usage
import * as React from 'react';
import { extendTheme, CssVarsProvider } from '@mui/material-next/styles';
import Button from '@mui/material-next/Button';

// Default MD3 theme
const theme= extendTheme();

// Or with custom palette
const theme= extendTheme({
    colorSchemes: {
      light: {
        ref: {
          palette: { md3: palette }
        },
      },
      dark: {
        ref: {
          palette: { md3: palette }
        },
      }
    }
  });

function App() {
  return (
    <CssVarsProvider  theme={theme}>
      <Button variant="filledTonal">MD 3 button</Button>
    </CssVarsProvider>
  );
}

how do we specify components css vars

We can follow the specs and apply each token directly to the components (this is similar to Joy UI):
const Button = styled('button', ...)({
  '--md-comp-extended-fab-secondary-container-color': '...',
  color: 'var(--md-comp-extended-fab-secondary-container-color)',

  // or
  'ExtendedFab-secondary-container-color': '...',
   color: var(--ExtendedFab-secondary-container-color),
})

What we need to decide is the variable prefix, should we keep it or remove it?

is the theme structured fine?

In long term, I'd say no. We should follow the m3 design specs to leverage their design tools, e.g. the Material Theme Builder (figma plugin) that generates tokens. If we have the theme structure close to their spec, I think we will have less unknown work from our side.

in general any other suggestions you may have

I am writing my thought in the discussion. I will post the link here when it is done.

I would not add all of the variables defined in the specs yet until we see them useful.

How do we decide which ones are useful? Btw, I was using the components' spec: https://m3.material.io/components/buttons/specs And how would we document which ones we support vs which ones we don't. Once we release stable long term, we cannot change them, as they would be public API.

Is the theme structured fine?

In long term, I'd say no. We should follow the m3 design specs to leverage their design tools, e.g. the Material Theme Builder (figma plugin) that generates tokens. If we have the theme structure close to their spec, I think we will have less unknown work from our side.

What exactly is your concern with this? Is it about how they are structured in object, or their structure inside an md3 key? I've generated the theme structure out of the exported tokens in https://github.com/material-foundation/material-tokens/blob/main/dsp/dist/styledictionary/js/tokens.js, I've just converted the constants names in objects based on the prefix.

I am writing my thought in https://github.com/mui/material-ui/discussions/34738. I will post the link here when it is done.

Perfect, thanks!

I believe it's ready for the first round of reviews.
@danilo-leal would be great if you can confirm the usage of the tokens. The pressed don't have much contrast, but as far as I could read the tokens I am using the right values.
@siriwatknp I restructured the theme to reflect what is in the spec. I partially implemented the sx prop to pull values from sys.color for example, but for the typography it may be trickier because of the structure of theme, but I left this for afterwards, just to be able to iterate faster.
@michaldudak tagging you for double checking the @mui/base usage :)
Lastly, I didn't add the ripple effects as per the spec, but if we see a push back from the community I would lean towards maybe including it 🤷♀

I've noticed that the sandboxes sometimes crash when the random color generator comes up with a 5-character string.

Fixed it.

MUI System: from the changes in packages/mui-system/src/cssVars/createCssVarsProvider.js, I think we should revisit MUI System to make it more flexible. Ideally, I think MUI System should not limited to any theme structure by providing utilities for the design system to create their own. I remember that we had a discussion to improve the MUI System, so may be this is the right time.

Agree, we need to be able to move the changes outside, I will look into this. We probably need an option to tell the CssVarsProvider, what key in the theme contains the palette.

I feel like having Material You as a separate package is an opportunity to improve the CSS implementation for each component (may be using the same component variables as Joy UI?). What's your thought on this?

Makes sense, I went from defining variables to everything to defining variables for nothing (except icons). I will try to think what variables we should add and check what we have in Joy UI

Sweet, this is looking great⎯awesome work! Aside from the missing letter spacing declarations in a few of the text styles, there's nothing really standing out for me. I do wish though that the Playground demo would follow the same layout as in the Material 3 Figma file, just for the sake of ease of comparison as I think a bunch of folks will do the back & forth.

The main reason why I didn't structure it like this, is because most of the items in figma are dependent on some interactions, like hover, focused etc. I guess we can think a bit more about how we want to document these components in a follow-up PR. We need to somehow fit them with the rest of the docs.


Something went wrong  - user created but can't view zones

I can see in logs that ldap login is accepted and it created a user:
[Thu Sep 13 14:21:49.365300 2018] [:error] [pid 10479] [client <IP_ADDRESS>:51256]<PHONE_NUMBER>: UserAlreadyExistsException: A user already exists with uid Bill.James in /var/www/dnsui_prod/model/userdirectory.php:54, referer: https://prod.billj7-6.test.j2noc.com/zones
...
[Thu Sep 13 14:44:26.513216 2018] [:error] [pid 10484] [client <IP_ADDRESS>:52134]<PHONE_NUMBER>: #1 /var/www/dnsui_prod/requesthandler.php(24): UserDirectory->get_user_by_uid('bill.james'), referer: https://prod.billj7-6.test.j2noc.com/zones
[Thu Sep 13 14:44:26.513218 2018] [:error] [pid 10484] [client <IP_ADDRESS>:52134]<PHONE_NUMBER>: #2 /var/www/dnsui_prod/public_html/init.php(18): require('/var/www/dnsui_...'), referer: https://prod.billj7-6.test.j2noc.com/zones
[Thu Sep 13 14:44:26.513220 2018] [:error] [pid 10484] [client <IP_ADDRESS>:52134]<PHONE_NUMBER>: #3 {main}, referer: https://prod.billj7-6.test.j2noc.com/zones
dnsui_proddb=# SELECT * FROM "user";
id |    uid     |    name    |       email       | auth_realm | active | admin | developer | csrf_token
----+------------+------------+-------------------+------------+--------+-------+-----------+------------
1 | Bill.James | Bill James |<EMAIL_ADDRESS>| LDAP       |      1 |     1 |         0 |
but I notice no csrf_token.
I'm not sure how to troubleshoot php code.
I'm running the latest git version on centos7.5. Unfortunately the error output is not very useful.
I just know its getting a 500 error on / or /zones.
How do I troubleshoot what is causing error?
I can run api commands fine against pdns master.
Is there a debug option that causes 'error_details' to get filled in?
I do have LogLevel debug set.

This looks like a bug related to case-sensitivity of the username. I say this because of the difference between the function call in the exception (->get_user_by_uid('bill.james')) compared to what you have in the database (Bill.James), and the fact that it appears to be trying to insert a new user record.
To confirm whether or not this is the case, try logging in with the username exactly as it is in the database.

ah, yes! it get's further now. We had seen that before and use this to fix postgres:
psql  -c 'CREATE EXTENSION IF NOT EXISTS citext WITH SCHEMA public; ALTER TABLE public."user" ALTER COLUMN uid TYPE citext  COLLATE pg_catalog."default";'  database_name
now on to my next error...:
PHP Fatal error:  Uncaught ErrorException: htmlspecialchars() expects parameter 1 to be string, object given in /var/www/dnsui_prod/core.php:114\nStack trace:\n#0 [internal function]: exception_error_handler(2, 'htmlspecialchar...', '/var/www/dnsui_...', 114, Array)\n#1 /var/www/dnsui_prod/core.php(114): htmlspecialchars(Object(User))\n#2 /var/www/dnsui_prod/templates/error500.php(55): out(Object(User))\n#3 /var/www/dnsui_prod/pagesection.php(69): include('/var/www/dnsui_...')\n#4 /var/www/dnsui_prod/pagesection.php(57): PageSection->generate()\n#5 /var/www/dnsui_prod/templates/base.php(74): PageSection->get('content')\n#6 /var/www/dnsui_prod/pagesection.php(69): include('/var/www/dnsui_...')\n#7 /var/www/dnsui_prod/views/error500.php(32): PageSection->generate()\n#8 /var/www/dnsui_prod/requesthandler.php(82): require('/var/www/dnsui_...')\n#9 [internal function]: exception_handler(Object(Error))\n#10 {main}\n  thrown in /var/www/dnsui_prod/core.php on line 114
fun times. At least other links work, Templates, Users, Settings, just not Zones.
btw, I added this line to end of templates/error500.php and at least it display the error.
But doesn't make it any easier to understand.
 error number: get('error_number')) ?>, error_details:  get('error_details')) ?>, user: get('active_user')) ?>

The stack trace above is actually related to the code you have added: you're trying to output the active user, which is an object, not a string.
If you (temporarily) want the application to display more useful error messages prior to the login step, you can do this a little more easily by commenting out the following line numbers in views/error500.php: 20, 21, 24 & 25. You shouldn't leave this permanently like this though, since it allows all users to view the details of the stack traces.

when I take that code out I just get the "oops" page. No error in ssl_error_log or anywhere else I've seen.  I know zones are fine, because I have another dnsui server that can read them fine.

Did you try commenting out the lines I suggested? (In views/error500.php, not templates/error500.php)

If you're logged in successfully though, you shouldn't need to do that. You can update your user entry in the database to have developer = 1 and it will show full errors to you in the UI.

yes, commented out lines 20-25 in views, still no error info displayed.
I also tried setting my user developer = 1; no error detail, just "oops".

Don't comment out lines 22 and 23 :)

oops.  :-)
that's much more helpful.

Function
Arguments
Location

punycode_to_utf8
am-i-pdns-corp.
/var/www/dnsui_corp/templates/zones.php line 68

include
/var/www/dnsui_corp/templates/zones.php
/var/www/dnsui_corp/pagesection.php line 69

generate

/var/www/dnsui_corp/pagesection.php line 57

get
content
/var/www/dnsui_corp/templates/base.php line 74

include
/var/www/dnsui_corp/templates/base.php
/var/www/dnsui_corp/pagesection.php line 69

generate

/var/www/dnsui_corp/views/zones.php line 79

require
/var/www/dnsui_corp/views/zones.php
/var/www/dnsui_corp/requesthandler.php line 64

require
/var/www/dnsui_corp/requesthandler.php
/var/www/dnsui_corp/public_html/init.php line 18

i left out the error part:
Error "Call to undefined function idn_to_utf8()"
Occurred in /var/www/dnsui_corp/core.php line 459

oh, is that because my encoding is wrong?
Name     |   Owner    | Encoding  | Collate | Ctype |   Access privileges
--------------+------------+-----------+---------+-------+-----------------------
dnsui_corpdb | dnsui-user | SQL_ASCII | C       | C     |
guess I need to look into how to change that....

Actually, I'd say it's because you don't have the PHP-intl module installed. idn_to_utf8 is a function provided by that module.

ah ha, it works now!
Thank you VERY much for your help!!
I like dns-ui very much, just having problems duplicating the install process.


sort-vars

Current dependencies on/for this PR:

main

PR #67   👈

This comment was auto-generated by Graphite.


In-plane tip deflection

Hello all,
I derived the in-plane speed of the tip of the blades of ‘5MW_Land_DLL_WTurb’ (by finding the derivatives of their respective in-plane tip deflections ’IPDefl1’, ’IPDefl2’, ’IPDefl3’) and it gave me results that are close to zero. Is there what I’m missing in the setup because the one I’m comparing it with has their in-plane speed of the tip of the blades close to the speed of the rotor.

Dear @jjonkman,
Thank you very much for this response, absolute accelerations helps.

 Would it be correct to use the accelerations as the in-plane speed in this case without any conversion?

Dear @OEziuzo,
The absolute acceleration of the blade tip is output in a local reference frame that is oriented with the blade tip.  It would not make sense to integrate this acceleration without first expressing the absolute acceleration in a frame of reference that is consistent between time steps, e.g., the global inertial frame.
Best regards,

Dear @jjonkman,
Thank you very much for the feedback.


cannot build for webgl

Assets\Scripts\SunVox\SunVox.cs(307,15): error CS0103: The name 'LIBRARY_NAME' does not exist in the current context

Unfortunately, javascript version is not easily embedded into project, although it's available on the warmplace website
Were you able to make it work in the end?

sadly no


namespace fix

fixes https://github.com/rm-hull/luma.core/issues/164
blocked by new luma.core release (also needs to be updated in setup.py)

ran tests locally and seems fine (python 3.7.3)


Add CRI support for windows container/pod updates

This PR adds support to CRI for requesting updates for windows containers/pods as well as LCOW containers/pods.
This PR also pulls in a beta version of cri-api in order to get recent changes to the container update API to allow for passing windows container resources in requests.

@kevpar @ambarve @dcantah @anmaxvl fyi

LGTM... again 😆

LGTM... again 😆


DNN-6134 Compatibility with LocalDB

QA has been unable to verify this change as localdb is not working - as we are at code-freeze I am going to revert this and we can handle it in 7.4.2 - please update https://dnntracker.atlassian.net/browse/DNN-6134 with step-by-step instructions to get localdb working (sorry for the inconvenience)


To use sqlalchemy instead of raw sql commands

@dvarrazzo has strong opinions on this so I am closing :)
We will not pursue this as SQL alchemy is proving yo be inefficient.


Ross needs bio, and list goals

[ ] Learn git and github
[ ] Explore ways to collaborate, branch, merge, etc.

Let @me know @ross if you have any feedback

Thanks @githubteacher

I think you've got the wrong @ross :-)

And the wrong @me :)


Ec2 - Add security group id lookup

See sanction / slate / seesaw

@nhibberd if you happy with slate's implementation I can move it to Mismi.EC2.. Otherwise there is sanction's Take you pick.

The pre-filter is definitely better, would be nice to have a maybe name or two implementations so people don't get stuck downstream

Interface from sanction, implementation from slate? :) I was not sure if it would be useful to allow lookup of a set of security groups..

Yeah that's a good idea, input can always be a list

Yeah that's a good idea, input can always be a list

But the interface becomes awkward. What would return type of this version? Property list? Map? [Maybe SecurityGroupName]? Meanwhile: https://github.com/ambiata/mismi/pull/250

Could create a data type and wrap a map or something


支持 Openshift Route 模型

背景
K8s 环境中已通过 Openshift Route 配置部分路由，希望 bfe-ingress-controller 兼容。

Route CRD

配置示例
apiVersion: route.openshift.io/v1
kind: Route
metadate:
  name: app
  namespace: default
spec:
  alternateBackends:
  - kind: Service
    name: app1
    weight: 20
  host: example.com
  path: /
  port:
    targetPort: 8080
  to:
    kind: Service
    name: app
    weight: 80
  wildcardPolicy: None

Reference
Ingress (V1) model: https://github.com/kubernetes/api/blob/master/networking/v1/types.go
Openshift Route model: https://github.com/openshift/api/blob/master/route/v1/types.go

Main diff btw the two models -
#1. TLS config -

Ingress reuses k8s secret tls config with proper name
Route configures key & cert in its spec with termination type

#2. Path -

An ingress spec has a path array with PathTypes(Exact, Prefix, ImplementationSpecific)
One route spec has just one path entry without PathType (Somehow reasonable that one route entry only contains one path)

#3. Backend -

An ingress can have a default backend and specify a backend in an ingress rule
A route can set a To backend and at most 3 alternative backends for one path with weights

#4. Balance weight -

BFE ingress uses annotation to set the balance weight - Weight values are assigned to sub-services that constructs a service which is specified in backend service name in a rule
A route assigns weight for different backend (To + alternative) in the spec, and the weight ranges from 0 to 256 with default 100

#5. Annotations -

Customize new annotations for openshift route in accordance with BFE annotation definitions (cookie, header, redirct, etc)

#6. IngressClass -

Should openshift route have such annotation?


[Bug]: Error when CA-Root-PW to short

What is the bug?
While the script is running it creates a root ca using easy-rsa. It asks for a passphrase to encrypt the private key of the ca. If the password is too short or skipped by the user, there will be errors while creating clients.
There should be a hint in the README and in the script.
Relevant log output
Using SSL: openssl OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
read EC key
writing EC key
Enter PEM pass phrase:

---------------------------------------

Missing expected CA file: ca.crt (perhaps you need to run build-ca?)
Run easyrsa without commands for usage and command help.

Client Test added.
cat: /etc/openvpn/easy-rsa/pki/ca.crt: No such file or directory
awk: cannot open /etc/openvpn/easy-rsa/pki/issued/Test.crt (No such file or directory)
cat: /etc/openvpn/easy-rsa/pki/private/Test.key: No such file or directory

I installed on a plain system. So openssl was installed by the script, or not?

Hi @petterpet, I found that the problem was a duplicated "vars" file ("/etc/openvpn/easy-rsa/vars" : old location, "/etc/openvpn/easy-rsa/pki/vars" : new location).
So I tweaked the script to store the variables in /tmp and then overwrite the "pki/vars" with it.
I do not create a pull request because you may want to make it cleaner or change the arrangement of this section.
Here is the modified code (line 704 to 734) :
if [[ ! -d /etc/openvpn/easy-rsa/ ]]; then
		local version="3.1.0"
		wget -O ~/easy-rsa.tgz https://github.com/OpenVPN/easy-rsa/releases/download/v${version}/EasyRSA-${version}.tgz
		mkdir -p /etc/openvpn/easy-rsa
		tar xzf ~/easy-rsa.tgz --strip-components=1 --directory /etc/openvpn/easy-rsa
		rm -f ~/easy-rsa.tgz

		cd /etc/openvpn/easy-rsa/ || return

		case $CERT_TYPE in
		1)
			echo "set_var EASYRSA_ALGO ec" >/tmp/vars
			echo "set_var EASYRSA_CURVE $CERT_CURVE" >>/tmp/vars
			;;
		2)
			echo "set_var EASYRSA_KEY_SIZE $RSA_KEY_SIZE" >/tmp/vars
			;;
		esac

		# Generate a random, alphanumeric identifier of 16 characters for CN and one for server name
		SERVER_CN="cn_$(head /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 16 | head -n 1)"
		echo "$SERVER_CN" >SERVER_CN_GENERATED
		SERVER_NAME="server_$(head /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 16 | head -n 1)"
		echo "$SERVER_NAME" >SERVER_NAME_GENERATED

		echo "set_var EASYRSA_REQ_CN $SERVER_CN" >>/tmp/vars

		# Create the PKI, set up the CA, the DH params and the server certificate
		./easyrsa init-pki
		mv /tmp/vars pki
		./easyrsa --batch build-ca nopass

I now have my client generated normally, with latest easy rsa and openssl version (tested on ubuntu:20.04)  !

@Abyss-W4tcher's fix works perfectly for me on Debian bookworm (testing)!
Here's the diff from the original, not including a whitespace change, if that's an easier format to review (it was for me):
--- openvpn-install.sh.ref      2022-08-31 15:50:25.983213571 +0000
+++ openvpn-install.sh  2022-08-31 15:51:50.058884463 +0000
@@ -702,7 +702,7 @@

        # Install the latest version of easy-rsa from source, if not already installed.
        if [[ ! -d /etc/openvpn/easy-rsa/ ]]; then
-               local version="3.0.7"
+               local version="3.1.0"
                wget -O ~/easy-rsa.tgz https://github.com/OpenVPN/easy-rsa/releases/download/v${version}/EasyRSA-${version}.tgz
                mkdir -p /etc/openvpn/easy-rsa
                tar xzf ~/easy-rsa.tgz --strip-components=1 --directory /etc/openvpn/easy-rsa
@@ -711,11 +711,11 @@
                cd /etc/openvpn/easy-rsa/ || return
                case $CERT_TYPE in
                1)
-                       echo "set_var EASYRSA_ALGO ec" >vars
-                       echo "set_var EASYRSA_CURVE $CERT_CURVE" >>vars
+                       echo "set_var EASYRSA_ALGO ec" >/tmp/vars
+                       echo "set_var EASYRSA_CURVE $CERT_CURVE" >>/tmp/vars
                        ;;
                2)
-                       echo "set_var EASYRSA_KEY_SIZE $RSA_KEY_SIZE" >vars
+                       echo "set_var EASYRSA_KEY_SIZE $RSA_KEY_SIZE" >/tmp/vars
                        ;;
                esac

@@ -725,10 +725,11 @@
                SERVER_NAME="server_$(head /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 16 | head -n 1)"
                echo "$SERVER_NAME" >SERVER_NAME_GENERATED

-               echo "set_var EASYRSA_REQ_CN $SERVER_CN" >>vars
+               echo "set_var EASYRSA_REQ_CN $SERVER_CN" >>/tmp/vars

                # Create the PKI, set up the CA, the DH params and the server certificate
                ./easyrsa init-pki
+               mv /tmp/vars pki
                ./easyrsa --batch build-ca nopass

                if [[ $DH_TYPE == "2" ]]; then

Sorry for the delay, this is fixed in https://github.com/angristan/openvpn-install/commit/2f76bb5e40f6f41a5bb2928379499b74da93f653


Add University of Science and Technology of Hanoi

@namluu25 Please tell us what is a difference of your request and #3773? It looks like a duplicate but with another domain. What is incorrect here?

It's 2 different university. My school was established under the Intergovernmental Agreement between Vietnam and France in 2009, while in #3773 was formed by Vietnamese Government long time ago.

@namluu25 Thank you for the clarification. Pull request merged.


datapath: remove support for legacy DSR path in bpf_lxc

https://github.com/cilium/cilium/pull/22978 added support for DSR RevDNAT at the native device-level. This was introduced in v1.14, and backported to v1.13.3. We kept the support in bpf_lxc for old-style DSR around a bit longer, to not break established connections. But with v1.16 it is about time to remove this legacy path.
Service connections that use ``Direct-Server-Return`` and were established prior to Cilium v1.13.3 will be disrupted, and need to be re-established.

/test

/test


Draft content structure in Engineering Hub docs site

Update current Engineering Hub docs site to start content migration.
Success criteria

Outdated content is removed
Landing page and ToC are updated with draft placeholders

Tasks

[x] Create content plan for new structure / IA hierarchy
[x] Update with placeholders in Engineering Hub

Links
https://eng.ms/docs/products/azure-developer-experience/

Completed

Drafted initial IA here
Met with Konrad to discuss
Removed all existing content from current eng.ms site
Requested eng.ms admin access for myself and Mariana
Updated repo with placeholders: https://eng.ms/docs/products/azure-developer-experience/

Next steps

Meet with API stewardship board next week to discuss v-team effort
Look into changing the URL /azure-developer-experience to /azure-sdk
Get folks to review general structure for feedback
Start migrating / re-swizzling some docs


Avoid redirect to the same region

Avoid s3 region redirect when the client region and the region received from the server are the same.
https://github.com/boto/botocore/blob/ac039ce8bd861d5d6dd2fa1c260b9987893181dd/botocore/utils.py#L1356-L1360

Hi @colored-paper, thanks for the PR. Do you have some examples of where you're seeing this happening? Preferably a log showing the response history from S3. I'm surprised we'd be receiving a same-region redirect that didn't materially change the target domain.

Hi @colored-paper, thanks for the PR. Do you have some examples of where you're seeing this happening? Preferably a log showing the response history from S3. I'm surprised we'd be receiving a same-region redirect that didn't materially change the target domain.

https://github.com/boto/botocore/blob/ac039ce8bd861d5d6dd2fa1c260b9987893181dd/botocore/utils.py#L1320-L1343
According to the code above, when response 400 occurs, the region redirect condition is true.
Added the command and debug log to receive response status 400 below(same region redirect).
aws s3api head-object --bucket test-region-apnortheast2 --key profile.jpeg --sse-customer-algorithm AES256

...
2021-07-28 01:27:37,932 - MainThread - botocore.utils - DEBUG - S3 client configured for region ap-northeast-2 but the bucket test-region-apnortheast2 is in region ap-northeast-2; Please configure the proper region to avoid multiple unnecessary redirects and signing attempts.
2021-07-28 01:27:37,932 - MainThread - botocore.utils - DEBUG - Updating URI from https://s3.ap-northeast-2.amazonaws.com/test-region-apnortheast2/profile.jpeg to https://s3.ap-northeast-2.amazonaws.com/test-region-apnortheast2/profile.jpeg
...

Full
aws s3api head-object --bucket test-region-apnortheast2 --key profile.jpeg --sse-customer-algorithm AES256 --debug
2021-07-28 01:27:37,711 - MainThread - awscli.clidriver - DEBUG - CLI version: aws-cli/2.2.22 Python/3.8.8 Darwin/20.5.0 exe/x86_64
2021-07-28 01:27:37,712 - MainThread - awscli.clidriver - DEBUG - Arguments entered to CLI: ['s3api', 'head-object', '--bucket', 'test-region-apnortheast2', '--key', 'profile.jpeg', '--sse-customer-algorithm', 'AES256', '--debug']
2021-07-28 01:27:37,723 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_s3 at 0x7fa7717cfca0>
2021-07-28 01:27:37,723 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_ddb at 0x7fa7716103a0>
2021-07-28 01:27:37,723 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <bound method BasicCommand.add_command of <class 'awscli.customizations.configure.configure.ConfigureCommand'>>
2021-07-28 01:27:37,723 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function change_name at 0x7fa7715b4af0>
2021-07-28 01:27:37,723 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function change_name at 0x7fa7715baaf0>
2021-07-28 01:27:37,723 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function alias_opsworks_cm at 0x7fa7717e1700>
2021-07-28 01:27:37,723 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_history_commands at 0x7fa77165c160>
2021-07-28 01:27:37,723 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <bound method BasicCommand.add_command of <class 'awscli.customizations.devcommands.CLIDevCommand'>>
2021-07-28 01:27:37,723 - MainThread - botocore.hooks - DEBUG - Event building-command-table.main: calling handler <function add_waiters at 0x7fa7717d7940>
2021-07-28 01:27:37,723 - MainThread - botocore.loaders - DEBUG - Loading JSON file: /usr/local/aws-cli/awscli/data/cli.json
2021-07-28 01:27:37,725 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <function resolve_types at 0x7fa771709c10>
2021-07-28 01:27:37,725 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <function no_sign_request at 0x7fa77170e790>
2021-07-28 01:27:37,725 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <function resolve_verify_ssl at 0x7fa77170e700>
2021-07-28 01:27:37,725 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <function resolve_cli_read_timeout at 0x7fa77170e8b0>
2021-07-28 01:27:37,725 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <function resolve_cli_connect_timeout at 0x7fa77170e820>
2021-07-28 01:27:37,725 - MainThread - botocore.hooks - DEBUG - Event top-level-args-parsed: calling handler <built-in method update of dict object at 0x7fa77187a700>
2021-07-28 01:27:37,726 - MainThread - awscli.clidriver - DEBUG - CLI version: aws-cli/2.2.22 Python/3.8.8 Darwin/20.5.0 exe/x86_64 prompt/off
2021-07-28 01:27:37,726 - MainThread - awscli.clidriver - DEBUG - Arguments entered to CLI: ['s3api', 'head-object', '--bucket', 'test-region-apnortheast2', '--key', 'profile.jpeg', '--sse-customer-algorithm', 'AES256', '--debug']
2021-07-28 01:27:37,726 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function add_timestamp_parser at 0x7fa7717d1310>
2021-07-28 01:27:37,726 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function register_uri_param_handler at 0x7fa77139f040>
2021-07-28 01:27:37,726 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function add_binary_formatter at 0x7fa77183fdc0>
2021-07-28 01:27:37,726 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function no_pager_handler at 0x7fa77134d4c0>
2021-07-28 01:27:37,726 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function inject_assume_role_provider_cache at 0x7fa7713c49d0>
2021-07-28 01:27:37,731 - MainThread - botocore.utils - DEBUG - IMDS ENDPOINT: http://<IP_ADDRESS>/
2021-07-28 01:27:37,735 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function attach_history_handler at 0x7fa77165c040>
2021-07-28 01:27:37,735 - MainThread - botocore.hooks - DEBUG - Event session-initialized: calling handler <function inject_json_file_cache at 0x7fa77160f280>
2021-07-28 01:27:37,746 - MainThread - botocore.loaders - DEBUG - Loading JSON file: /usr/local/aws-cli/botocore/data/s3/2006-03-01/service-2.json
2021-07-28 01:27:37,756 - MainThread - botocore.hooks - DEBUG - Event building-command-table.s3api: calling handler <function add_waiters at 0x7fa7717d7940>
2021-07-28 01:27:37,766 - MainThread - botocore.loaders - DEBUG - Loading JSON file: /usr/local/aws-cli/botocore/data/s3/2006-03-01/waiters-2.json
2021-07-28 01:27:37,767 - MainThread - awscli.clidriver - DEBUG - OrderedDict([('bucket', <awscli.arguments.CLIArgument object at 0x7fa76025c9a0>), ('if-match', <awscli.arguments.CLIArgument object at 0x7fa76025c970>), ('if-modified-since', <awscli.arguments.CLIArgument object at 0x7fa76025ca00>), ('if-none-match', <awscli.arguments.CLIArgument object at 0x7fa76025ca30>), ('if-unmodified-since', <awscli.arguments.CLIArgument object at 0x7fa76025ca60>), ('key', <awscli.arguments.CLIArgument object at 0x7fa76025ca90>), ('range', <awscli.arguments.CLIArgument object at 0x7fa76025cac0>), ('version-id', <awscli.arguments.CLIArgument object at 0x7fa76025caf0>), ('sse-customer-algorithm', <awscli.arguments.CLIArgument object at 0x7fa76025cb20>), ('sse-customer-key', <awscli.arguments.CLIArgument object at 0x7fa76025cb50>), ('sse-customer-key-md5', <awscli.arguments.CLIArgument object at 0x7fa76025cb80>), ('request-payer', <awscli.arguments.CLIArgument object at 0x7fa76025cbb0>), ('part-number', <awscli.arguments.CLIArgument object at 0x7fa76025cbe0>), ('expected-bucket-owner', <awscli.arguments.CLIArgument object at 0x7fa76025cc10>)])
2021-07-28 01:27:37,767 - MainThread - botocore.hooks - DEBUG - Event building-argument-table.s3api.head-object: calling handler <function add_streaming_output_arg at 0x7fa7717d18b0>
2021-07-28 01:27:37,767 - MainThread - botocore.hooks - DEBUG - Event building-argument-table.s3api.head-object: calling handler <function add_cli_input_json at 0x7fa7713c7280>
2021-07-28 01:27:37,767 - MainThread - botocore.hooks - DEBUG - Event building-argument-table.s3api.head-object: calling handler <function add_cli_input_yaml at 0x7fa7713c7550>
2021-07-28 01:27:37,768 - MainThread - botocore.hooks - DEBUG - Event building-argument-table.s3api.head-object: calling handler <function unify_paging_params at 0x7fa7716109d0>
2021-07-28 01:27:37,778 - MainThread - botocore.loaders - DEBUG - Loading JSON file: /usr/local/aws-cli/botocore/data/s3/2006-03-01/paginators-1.json
2021-07-28 01:27:37,778 - MainThread - botocore.hooks - DEBUG - Event building-argument-table.s3api.head-object: calling handler <function add_generate_skeleton at 0x7fa7717091f0>
2021-07-28 01:27:37,778 - MainThread - botocore.hooks - DEBUG - Event before-building-argument-table-parser.s3api.head-object: calling handler <bound method OverrideRequiredArgsArgument.override_required_args of <awscli.customizations.cliinput.CliInputJSONArgument object at 0x7fa76025cd60>>
2021-07-28 01:27:37,778 - MainThread - botocore.hooks - DEBUG - Event before-building-argument-table-parser.s3api.head-object: calling handler <bound method OverrideRequiredArgsArgument.override_required_args of <awscli.customizations.cliinput.CliInputYAMLArgument object at 0x7fa76025cd90>>
2021-07-28 01:27:37,778 - MainThread - botocore.hooks - DEBUG - Event before-building-argument-table-parser.s3api.head-object: calling handler <bound method GenerateCliSkeletonArgument.override_required_args of <awscli.customizations.generatecliskeleton.GenerateCliSkeletonArgument object at 0x7fa76025c610>>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.bucket: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event process-cli-arg.s3.head-object: calling handler <awscli.argprocess.ParamShorthandParser object at 0x7fa771372f70>
2021-07-28 01:27:37,779 - MainThread - awscli.arguments - DEBUG - Unpacked value of 'test-region-apnortheast2' for parameter "bucket": 'test-region-apnortheast2'
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.if-match: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.if-modified-since: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.if-none-match: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.if-unmodified-since: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.key: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event process-cli-arg.s3.head-object: calling handler <awscli.argprocess.ParamShorthandParser object at 0x7fa771372f70>
2021-07-28 01:27:37,779 - MainThread - awscli.arguments - DEBUG - Unpacked value of 'profile.jpeg' for parameter "key": 'profile.jpeg'
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.range: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.version-id: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.sse-customer-algorithm: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event process-cli-arg.s3.head-object: calling handler <awscli.argprocess.ParamShorthandParser object at 0x7fa771372f70>
2021-07-28 01:27:37,779 - MainThread - awscli.arguments - DEBUG - Unpacked value of 'AES256' for parameter "sse_customer_algorithm": 'AES256'
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.sse-customer-key: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.sse-customer-key-md5: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.request-payer: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.part-number: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.expected-bucket-owner: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.cli-input-json: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,779 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.cli-input-yaml: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,780 - MainThread - botocore.hooks - DEBUG - Event load-cli-arg.s3.head-object.generate-cli-skeleton: calling handler <awscli.paramfile.URIArgumentHandler object at 0x7fa7601a6250>
2021-07-28 01:27:37,780 - MainThread - botocore.hooks - DEBUG - Event calling-command.s3api.head-object: calling handler <bound method CliInputArgument.add_to_call_parameters of <awscli.customizations.cliinput.CliInputJSONArgument object at 0x7fa76025cd60>>
2021-07-28 01:27:37,780 - MainThread - botocore.hooks - DEBUG - Event calling-command.s3api.head-object: calling handler <bound method CliInputArgument.add_to_call_parameters of <awscli.customizations.cliinput.CliInputYAMLArgument object at 0x7fa76025cd90>>
2021-07-28 01:27:37,780 - MainThread - botocore.hooks - DEBUG - Event calling-command.s3api.head-object: calling handler <bound method GenerateCliSkeletonArgument.generate_skeleton of <awscli.customizations.generatecliskeleton.GenerateCliSkeletonArgument object at 0x7fa76025c610>>
2021-07-28 01:27:37,780 - MainThread - botocore.credentials - DEBUG - Looking for credentials via: env
2021-07-28 01:27:37,780 - MainThread - botocore.credentials - DEBUG - Looking for credentials via: assume-role
2021-07-28 01:27:37,780 - MainThread - botocore.credentials - DEBUG - Looking for credentials via: assume-role-with-web-identity
2021-07-28 01:27:37,780 - MainThread - botocore.credentials - DEBUG - Looking for credentials via: sso
2021-07-28 01:27:37,780 - MainThread - botocore.credentials - DEBUG - Looking for credentials via: shared-credentials-file
2021-07-28 01:27:37,780 - MainThread - botocore.credentials - INFO - Found credentials in shared credentials file: ~/.aws/credentials
2021-07-28 01:27:37,781 - MainThread - botocore.loaders - DEBUG - Loading JSON file: /usr/local/aws-cli/botocore/data/endpoints.json
2021-07-28 01:27:37,786 - MainThread - botocore.hooks - DEBUG - Event choose-service-name: calling handler <function handle_service_name_alias at 0x7fa770c97280>
2021-07-28 01:27:37,788 - MainThread - botocore.hooks - DEBUG - Event creating-client-class.s3: calling handler <function add_generate_presigned_post at 0x7fa770c40700>
2021-07-28 01:27:37,788 - MainThread - botocore.hooks - DEBUG - Event creating-client-class.s3: calling handler <function add_generate_presigned_url at 0x7fa770c404c0>
2021-07-28 01:27:37,804 - MainThread - botocore.endpoint - DEBUG - Setting s3 timeout as (60, 60)
2021-07-28 01:27:37,805 - MainThread - botocore.hooks - DEBUG - Event provide-client-params.s3.HeadObject: calling handler <function base64_decode_input_blobs at 0x7fa77183a550>
2021-07-28 01:27:37,805 - MainThread - botocore.hooks - DEBUG - Event before-parameter-build.s3.HeadObject: calling handler <function sse_md5 at 0x7fa770cb54c0>
2021-07-28 01:27:37,806 - MainThread - botocore.hooks - DEBUG - Event before-parameter-build.s3.HeadObject: calling handler <function validate_bucket_name at 0x7fa770cb5430>
2021-07-28 01:27:37,806 - MainThread - botocore.hooks - DEBUG - Event before-parameter-build.s3.HeadObject: calling handler <bound method S3RegionRedirector.redirect_from_cache of <botocore.utils.S3RegionRedirector object at 0x7fa771bcfa00>>
2021-07-28 01:27:37,806 - MainThread - botocore.hooks - DEBUG - Event before-parameter-build.s3.HeadObject: calling handler <bound method S3ArnParamHandler.handle_arn of <botocore.utils.S3ArnParamHandler object at 0x7fa771bcfac0>>
2021-07-28 01:27:37,806 - MainThread - botocore.hooks - DEBUG - Event before-parameter-build.s3.HeadObject: calling handler <function generate_idempotent_uuid at 0x7fa770cb5280>
2021-07-28 01:27:37,806 - MainThread - botocore.hooks - DEBUG - Event before-call.s3.HeadObject: calling handler <function add_expect_header at 0x7fa770cb5790>
2021-07-28 01:27:37,806 - MainThread - botocore.hooks - DEBUG - Event before-call.s3.HeadObject: calling handler <bound method S3RegionRedirector.set_request_url of <botocore.utils.S3RegionRedirector object at 0x7fa771bcfa00>>
2021-07-28 01:27:37,806 - MainThread - botocore.hooks - DEBUG - Event before-call.s3.HeadObject: calling handler <function inject_api_version_header_if_needed at 0x7fa770cb4af0>
2021-07-28 01:27:37,806 - MainThread - botocore.endpoint - DEBUG - Making request for OperationModel(name=HeadObject) with params: {'url_path': '/test-region-apnortheast2/profile.jpeg', 'query_string': {}, 'method': 'HEAD', 'headers': {'x-amz-server-side-encryption-customer-algorithm': 'AES256', 'User-Agent': 'aws-cli/2.2.22 Python/3.8.8 Darwin/20.5.0 exe/x86_64 prompt/off command/s3api.head-object'}, 'body': b'', 'url': 'https://s3.ap-northeast-2.amazonaws.com/test-region-apnortheast2/profile.jpeg', 'context': {'client_region': 'ap-northeast-2', 'client_config': <botocore.config.Config object at 0x7fa771b95e20>, 'has_streaming_input': False, 'auth_type': None, 'signing': {'bucket': 'test-region-apnortheast2'}}}
2021-07-28 01:27:37,806 - MainThread - botocore.hooks - DEBUG - Event request-created.s3.HeadObject: calling handler <bound method RequestSigner.handler of <botocore.signers.RequestSigner object at 0x7fa771b95ee0>>
2021-07-28 01:27:37,806 - MainThread - botocore.hooks - DEBUG - Event choose-signer.s3.HeadObject: calling handler <function set_operation_specific_signer at 0x7fa770cb5160>
2021-07-28 01:27:37,806 - MainThread - botocore.hooks - DEBUG - Event before-sign.s3.HeadObject: calling handler <bound method S3EndpointSetter.set_endpoint of <botocore.utils.S3EndpointSetter object at 0x7fa771bcfb50>>
2021-07-28 01:27:37,806 - MainThread - botocore.utils - DEBUG - Defaulting to S3 virtual host style addressing with path style addressing fallback.
2021-07-28 01:27:37,806 - MainThread - botocore.utils - DEBUG - Checking for DNS compatible bucket for: https://s3.ap-northeast-2.amazonaws.com/test-region-apnortheast2/profile.jpeg
2021-07-28 01:27:37,807 - MainThread - botocore.utils - DEBUG - URI updated to: https://test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com/profile.jpeg
2021-07-28 01:27:37,807 - MainThread - botocore.auth - DEBUG - Calculating signature using v4 auth.
2021-07-28 01:27:37,807 - MainThread - botocore.auth - DEBUG - CanonicalRequest:
HEAD
/profile.jpeg

host:test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com
x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date:20210727T162737Z
x-amz-server-side-encryption-customer-algorithm:AES256

host;x-amz-content-sha256;x-amz-date;x-amz-server-side-encryption-customer-algorithm
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2021-07-28 01:27:37,807 - MainThread - botocore.auth - DEBUG - StringToSign:
AWS4-HMAC-SHA256
20210727T162737Z
20210727/ap-northeast-2/s3/aws4_request
132386e78b91be6ac5b6db98cdbecd58304c1533323b85d3904c108f37b5ad5a
2021-07-28 01:27:37,807 - MainThread - botocore.auth - DEBUG - Signature:
105735fe8a5b83e30ed53c387b97c7ce9771421d172c804057c8c9f3bae824e6
2021-07-28 01:27:37,807 - MainThread - botocore.endpoint - DEBUG - Sending http request: <AWSPreparedRequest stream_output=False, method=HEAD, url=https://test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com/profile.jpeg, headers={'x-amz-server-side-encryption-customer-algorithm': b'AES256', 'User-Agent': b'aws-cli/2.2.22 Python/3.8.8 Darwin/20.5.0 exe/x86_64 prompt/off command/s3api.head-object', 'X-Amz-Date': b'20210727T162737Z', 'X-Amz-Content-SHA256': b'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855', 'Authorization': b'AWS4-HMAC-SHA256 Credential=AKIAV7O4LYIAQH42HG5J/20210727/ap-northeast-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-server-side-encryption-customer-algorithm, Signature=105735fe8a5b83e30ed53c387b97c7ce9771421d172c804057c8c9f3bae824e6'}>
2021-07-28 01:27:37,808 - MainThread - botocore.httpsession - DEBUG - Certificate path: /usr/local/aws-cli/botocore/cacert.pem
2021-07-28 01:27:37,808 - MainThread - urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com:443
2021-07-28 01:27:37,871 - MainThread - urllib3.connectionpool - DEBUG - https://test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com:443 "HEAD /profile.jpeg HTTP/1.1" 400 0
2021-07-28 01:27:37,871 - MainThread - botocore.parsers - DEBUG - Response headers: {'x-amz-request-id': '9PA9S88AQJ4E9XTM', 'x-amz-id-2': 'lO0NULfRi/sZiBEiaeyYjgqBGKz/W/ZcrUNLhrfl8+68jmnyqae5KxWYquWaLyhIFE8TWal3zJY=', 'Content-Type': 'application/xml', 'Date': 'Tue, 27 Jul 2021 16:27:37 GMT', 'Server': 'AmazonS3', 'Connection': 'close'}
2021-07-28 01:27:37,871 - MainThread - botocore.parsers - DEBUG - Response body:
b''
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event needs-retry.s3.HeadObject: calling handler <bound method RetryHandler.needs_retry of <botocore.retries.standard.RetryHandler object at 0x7fa771bcf9a0>>
2021-07-28 01:27:37,873 - MainThread - botocore.retries.standard - DEBUG - Not retrying request.
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event needs-retry.s3.HeadObject: calling handler <bound method S3RegionRedirector.redirect_from_error of <botocore.utils.S3RegionRedirector object at 0x7fa771bcfa00>>
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event provide-client-params.s3.HeadBucket: calling handler <function base64_decode_input_blobs at 0x7fa77183a550>
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event before-parameter-build.s3.HeadBucket: calling handler <function validate_bucket_name at 0x7fa770cb5430>
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event before-parameter-build.s3.HeadBucket: calling handler <bound method S3RegionRedirector.redirect_from_cache of <botocore.utils.S3RegionRedirector object at 0x7fa771bcfa00>>
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event before-parameter-build.s3.HeadBucket: calling handler <bound method S3ArnParamHandler.handle_arn of <botocore.utils.S3ArnParamHandler object at 0x7fa771bcfac0>>
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event before-parameter-build.s3.HeadBucket: calling handler <function generate_idempotent_uuid at 0x7fa770cb5280>
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event before-call.s3.HeadBucket: calling handler <function add_expect_header at 0x7fa770cb5790>
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event before-call.s3.HeadBucket: calling handler <bound method S3RegionRedirector.set_request_url of <botocore.utils.S3RegionRedirector object at 0x7fa771bcfa00>>
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event before-call.s3.HeadBucket: calling handler <function inject_api_version_header_if_needed at 0x7fa770cb4af0>
2021-07-28 01:27:37,873 - MainThread - botocore.endpoint - DEBUG - Making request for OperationModel(name=HeadBucket) with params: {'url_path': '/test-region-apnortheast2', 'query_string': {}, 'method': 'HEAD', 'headers': {'User-Agent': 'aws-cli/2.2.22 Python/3.8.8 Darwin/20.5.0 exe/x86_64 prompt/off command/s3api.head-object'}, 'body': b'', 'url': 'https://s3.ap-northeast-2.amazonaws.com/test-region-apnortheast2', 'context': {'client_region': 'ap-northeast-2', 'client_config': <botocore.config.Config object at 0x7fa771b95e20>, 'has_streaming_input': False, 'auth_type': None, 'signing': {'bucket': 'test-region-apnortheast2'}}}
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event request-created.s3.HeadBucket: calling handler <bound method RequestSigner.handler of <botocore.signers.RequestSigner object at 0x7fa771b95ee0>>
2021-07-28 01:27:37,873 - MainThread - botocore.hooks - DEBUG - Event choose-signer.s3.HeadBucket: calling handler <function set_operation_specific_signer at 0x7fa770cb5160>
2021-07-28 01:27:37,874 - MainThread - botocore.hooks - DEBUG - Event before-sign.s3.HeadBucket: calling handler <bound method S3EndpointSetter.set_endpoint of <botocore.utils.S3EndpointSetter object at 0x7fa771bcfb50>>
2021-07-28 01:27:37,874 - MainThread - botocore.utils - DEBUG - Checking for DNS compatible bucket for: https://s3.ap-northeast-2.amazonaws.com/test-region-apnortheast2
2021-07-28 01:27:37,874 - MainThread - botocore.utils - DEBUG - URI updated to: https://test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com/
2021-07-28 01:27:37,874 - MainThread - botocore.auth - DEBUG - Calculating signature using v4 auth.
2021-07-28 01:27:37,874 - MainThread - botocore.auth - DEBUG - CanonicalRequest:
HEAD
/

host:test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com
x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date:20210727T162737Z

host;x-amz-content-sha256;x-amz-date
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2021-07-28 01:27:37,874 - MainThread - botocore.auth - DEBUG - StringToSign:
AWS4-HMAC-SHA256
20210727T162737Z
20210727/ap-northeast-2/s3/aws4_request
7d52efd19ebca579d318ed9cc77b4d363fbe68ffd6bfc397b0c7bc8092c42bb0
2021-07-28 01:27:37,874 - MainThread - botocore.auth - DEBUG - Signature:
a1fced4b374f631e0f046764d66fbd7d0641befdb4b9c900c1c07ee88b5b7cf5
2021-07-28 01:27:37,874 - MainThread - botocore.endpoint - DEBUG - Sending http request: <AWSPreparedRequest stream_output=False, method=HEAD, url=https://test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com/, headers={'User-Agent': b'aws-cli/2.2.22 Python/3.8.8 Darwin/20.5.0 exe/x86_64 prompt/off command/s3api.head-object', 'X-Amz-Date': b'20210727T162737Z', 'X-Amz-Content-SHA256': b'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855', 'Authorization': b'AWS4-HMAC-SHA256 Credential=AKIAV7O4LYIAQH42HG5J/20210727/ap-northeast-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=a1fced4b374f631e0f046764d66fbd7d0641befdb4b9c900c1c07ee88b5b7cf5'}>
2021-07-28 01:27:37,874 - MainThread - botocore.httpsession - DEBUG - Certificate path: /usr/local/aws-cli/botocore/cacert.pem
2021-07-28 01:27:37,874 - MainThread - urllib3.connectionpool - DEBUG - Resetting dropped connection: test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com
2021-07-28 01:27:37,931 - MainThread - urllib3.connectionpool - DEBUG - https://test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com:443 "HEAD / HTTP/1.1" 200 0
2021-07-28 01:27:37,931 - MainThread - botocore.parsers - DEBUG - Response headers: {'x-amz-id-2': 'r8tH/ZsCJZjAvrPRcy2CrpJGacclVFBbt4TcHSJykkUc+n0uz+RMHg0fmJOwyT1Yrx2vaxsESrA=', 'x-amz-request-id': '9PAFAJ7AESSZYWEA', 'Date': 'Tue, 27 Jul 2021 16:27:38 GMT', 'x-amz-bucket-region': 'ap-northeast-2', 'x-amz-access-point-alias': 'false', 'Content-Type': 'application/xml', 'Server': 'AmazonS3'}
2021-07-28 01:27:37,932 - MainThread - botocore.parsers - DEBUG - Response body:
b''
2021-07-28 01:27:37,932 - MainThread - botocore.hooks - DEBUG - Event needs-retry.s3.HeadBucket: calling handler <bound method RetryHandler.needs_retry of <botocore.retries.standard.RetryHandler object at 0x7fa771bcf9a0>>
2021-07-28 01:27:37,932 - MainThread - botocore.retries.standard - DEBUG - Not retrying request.
2021-07-28 01:27:37,932 - MainThread - botocore.hooks - DEBUG - Event needs-retry.s3.HeadBucket: calling handler <bound method S3RegionRedirector.redirect_from_error of <botocore.utils.S3RegionRedirector object at 0x7fa771bcfa00>>
2021-07-28 01:27:37,932 - MainThread - botocore.hooks - DEBUG - Event after-call.s3.HeadBucket: calling handler <function enhance_error_msg at 0x7fa7717cfee0>
2021-07-28 01:27:37,932 - MainThread - botocore.hooks - DEBUG - Event after-call.s3.HeadBucket: calling handler <bound method RetryQuotaChecker.release_retry_quota of <botocore.retries.standard.RetryQuotaChecker object at 0x7fa771bcf5b0>>
2021-07-28 01:27:37,932 - MainThread - botocore.utils - DEBUG - S3 client configured for region ap-northeast-2 but the bucket test-region-apnortheast2 is in region ap-northeast-2; Please configure the proper region to avoid multiple unnecessary redirects and signing attempts.
2021-07-28 01:27:37,932 - MainThread - botocore.utils - DEBUG - Updating URI from https://s3.ap-northeast-2.amazonaws.com/test-region-apnortheast2/profile.jpeg to https://s3.ap-northeast-2.amazonaws.com/test-region-apnortheast2/profile.jpeg
2021-07-28 01:27:37,932 - MainThread - botocore.endpoint - DEBUG - Response received to retry, sleeping for 0 seconds
2021-07-28 01:27:37,932 - MainThread - botocore.hooks - DEBUG - Event request-created.s3.HeadObject: calling handler <bound method RequestSigner.handler of <botocore.signers.RequestSigner object at 0x7fa771b95ee0>>
2021-07-28 01:27:37,932 - MainThread - botocore.hooks - DEBUG - Event choose-signer.s3.HeadObject: calling handler <function set_operation_specific_signer at 0x7fa770cb5160>
2021-07-28 01:27:37,932 - MainThread - botocore.hooks - DEBUG - Event before-sign.s3.HeadObject: calling handler <bound method S3EndpointSetter.set_endpoint of <botocore.utils.S3EndpointSetter object at 0x7fa771bcfb50>>
2021-07-28 01:27:37,932 - MainThread - botocore.utils - DEBUG - Checking for DNS compatible bucket for: https://s3.ap-northeast-2.amazonaws.com/test-region-apnortheast2/profile.jpeg
2021-07-28 01:27:37,932 - MainThread - botocore.utils - DEBUG - URI updated to: https://test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com/profile.jpeg
2021-07-28 01:27:37,932 - MainThread - botocore.auth - DEBUG - Calculating signature using v4 auth.
2021-07-28 01:27:37,932 - MainThread - botocore.auth - DEBUG - CanonicalRequest:
HEAD
/profile.jpeg

host:test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com
x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date:20210727T162737Z
x-amz-server-side-encryption-customer-algorithm:AES256

host;x-amz-content-sha256;x-amz-date;x-amz-server-side-encryption-customer-algorithm
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
2021-07-28 01:27:37,933 - MainThread - botocore.auth - DEBUG - StringToSign:
AWS4-HMAC-SHA256
20210727T162737Z
20210727/ap-northeast-2/s3/aws4_request
132386e78b91be6ac5b6db98cdbecd58304c1533323b85d3904c108f37b5ad5a
2021-07-28 01:27:37,933 - MainThread - botocore.auth - DEBUG - Signature:
105735fe8a5b83e30ed53c387b97c7ce9771421d172c804057c8c9f3bae824e6
2021-07-28 01:27:37,933 - MainThread - botocore.endpoint - DEBUG - Sending http request: <AWSPreparedRequest stream_output=False, method=HEAD, url=https://test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com/profile.jpeg, headers={'x-amz-server-side-encryption-customer-algorithm': b'AES256', 'User-Agent': b'aws-cli/2.2.22 Python/3.8.8 Darwin/20.5.0 exe/x86_64 prompt/off command/s3api.head-object', 'X-Amz-Date': b'20210727T162737Z', 'X-Amz-Content-SHA256': b'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855', 'Authorization': b'AWS4-HMAC-SHA256 Credential=AKIAV7O4LYIAQH42HG5J/20210727/ap-northeast-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-server-side-encryption-customer-algorithm, Signature=105735fe8a5b83e30ed53c387b97c7ce9771421d172c804057c8c9f3bae824e6'}>
2021-07-28 01:27:37,933 - MainThread - botocore.httpsession - DEBUG - Certificate path: /usr/local/aws-cli/botocore/cacert.pem
2021-07-28 01:27:37,943 - MainThread - urllib3.connectionpool - DEBUG - https://test-region-apnortheast2.s3.ap-northeast-2.amazonaws.com:443 "HEAD /profile.jpeg HTTP/1.1" 400 0
2021-07-28 01:27:37,943 - MainThread - botocore.parsers - DEBUG - Response headers: {'x-amz-request-id': '9PAC4JVPVR539146', 'x-amz-id-2': 'HNM42Opb/wt6eQHPrwLg84KgC3ZS3p2h0CoE5v0lFZe578llfG6YRZFNu6YDWG29e/NPoS7kxMI=', 'Content-Type': 'application/xml', 'Date': 'Tue, 27 Jul 2021 16:27:37 GMT', 'Server': 'AmazonS3', 'Connection': 'close'}
2021-07-28 01:27:37,943 - MainThread - botocore.parsers - DEBUG - Response body:
b''
2021-07-28 01:27:37,943 - MainThread - botocore.hooks - DEBUG - Event needs-retry.s3.HeadObject: calling handler <bound method RetryHandler.needs_retry of <botocore.retries.standard.RetryHandler object at 0x7fa771bcf9a0>>
2021-07-28 01:27:37,943 - MainThread - botocore.retries.standard - DEBUG - Not retrying request.
2021-07-28 01:27:37,943 - MainThread - botocore.hooks - DEBUG - Event needs-retry.s3.HeadObject: calling handler <bound method S3RegionRedirector.redirect_from_error of <botocore.utils.S3RegionRedirector object at 0x7fa771bcfa00>>
2021-07-28 01:27:37,943 - MainThread - botocore.utils - DEBUG - S3 request was previously redirected, not redirecting.
2021-07-28 01:27:37,943 - MainThread - botocore.hooks - DEBUG - Event after-call.s3.HeadObject: calling handler <function enhance_error_msg at 0x7fa7717cfee0>
2021-07-28 01:27:37,943 - MainThread - botocore.hooks - DEBUG - Event after-call.s3.HeadObject: calling handler <bound method RetryQuotaChecker.release_retry_quota of <botocore.retries.standard.RetryQuotaChecker object at 0x7fa771bcf5b0>>
2021-07-28 01:27:37,944 - MainThread - awscli.clidriver - DEBUG - Exception caught in main()
Traceback (most recent call last):
  File "awscli/clidriver.py", line 459, in main
  File "awscli/clidriver.py", line 594, in __call__
  File "awscli/clidriver.py", line 770, in __call__
  File "awscli/clidriver.py", line 901, in invoke
  File "awscli/clidriver.py", line 913, in _make_client_call
  File "botocore/client.py", line 278, in _api_call
  File "botocore/client.py", line 597, in _make_api_call
botocore.exceptions.ClientError: An error occurred (400) when calling the HeadObject operation: Bad Request

An error occurred (400) when calling the HeadObject operation: Bad Request

Codecov Report

Merging #2446 (684e722) into develop (ac039ce) will decrease coverage by 0.09%.
The diff coverage is 50.00%.

@@             Coverage Diff             @@
##           develop    #2446      +/-   ##
===========================================
- Coverage    96.64%   96.55%   -0.10%
===========================================
  Files           59       59
  Lines        11209    11074     -135
===========================================
- Hits         10833    10692     -141
- Misses         376      382       +6

Impacted Files
Coverage Δ

botocore/utils.py
96.99% <50.00%> (-0.27%)
:arrow_down:

botocore/httpsession.py
91.54% <0.00%> (-1.48%)
:arrow_down:

botocore/compat.py
71.82% <0.00%> (-0.31%)
:arrow_down:

botocore/model.py
98.02% <0.00%> (-0.23%)
:arrow_down:

botocore/docs/bcdoc/restdoc.py
96.26% <0.00%> (-0.17%)
:arrow_down:

botocore/retries/bucket.py
98.48% <0.00%> (-0.09%)
:arrow_down:

botocore/loaders.py
99.24% <0.00%> (-0.04%)
:arrow_down:

botocore/paginate.py
97.80% <0.00%> (-0.03%)
:arrow_down:

botocore/docs/bcdoc/style.py
96.15% <0.00%> (-0.03%)
:arrow_down:

... and 12 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 ac039ce...684e722. Read the comment docs.

add test code

@nateprewitt
This PR has not been reviewed for a long time.
Please check the log and commit.

Hey @colored-paper, to provide a quick update on where we're at, there are some concerns about short circuiting this behavior. While the region may stay the same, the endpoint can potentially change depending on what style s3 url has been used. Indiscriminately skipping this step now may break a class of redirects.
We can leave this PR open for the moment while we work to determine full impact, or it may be easier to track in an issue if you would like to open one describing the problem.

Hi @end-2, thanks for this pull request and for your patience. I'm going to close this pull request, not because it doesn't have value, but because the implementation details are something we want to handle internally. I'll be opening a backlog item for this. Thanks again for contributing!


Run as server to schedule backup, reduce crontab dependency

https://github.com/jasonlvhit/gocron

Add gobackup start for run GoBackup as daemon.
Allows configuration schedule in gobackup.yml.
Trigger gobackup perform command in server process.

For avoid crontab config, so we can backup the schedule setting in gobackup.yml into archive file.
When we recovery the backup to new host, the schedule setting is still in gobackup.yml.

https://github.com/huacnlee/gobackup/releases/tag/v1.3.0


L515 - Accelerometer and Gyroscope timestamps not consistent

Required Info

Camera Model
L515

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 18.04

Kernel Version (Linux Only)
5.4.0-54-generic

Platform
PC

SDK Version
2.40.0

Language

Segment
Robot

Issue Description
Got strange time values when trying to read values from the IMU. To be more specific, accelerometer and gyroscope timestamps are not consistent, making impossible to synchronize data. I don't know if the problem might be related to the warning listed below in picture.

My fault. Solved installing the correct kernel patch.


MediaRouteButton is always disabled

Hi , MediaRouteButton is always disabled. And doesn't respond to the clicks. It's the same issue even on the sample apk fr the chrome sender sample app.

Have you registered your chromecast for development?

Yes, i have registered.

I have the same problem, If anyone has any answer please let me know.

Are you running this from the emulator? I had this same problem myself, and my understanding is that this happens because the emulator is using AndroidWifi as its wireless connection, whereas your physical Chromecast device is on you home network. See documentation.
If you try your app on your physical device, it should be enabled.


x/tools/gopls: add configuration for single-line hover

Right now gopls returns only first sentence from the symbol documentation, please make it return full docs.

This is intentional. Often, documentation can be lengthy and overwhelming (token.Pos is a good example), so we try to avoid showing it all on hover. My assumption was that, if the user wanted to see more detail, they could jump to the definition of the identifier.
However, if this is not the case, and other people are also interested in this behavior, I'd be willing to make this change.
If you want to see full documentation on hover, please upvote this issue or comment with your reasoning.

Actually full docs on hover was available with all editors/tools that I was using so far:

VS Code + default command line tools
VS Code + go-langserver
VS Code + bingo
Goland

From my experience it's one of the most useful and demanded features. I wouldn't mind that gopls will have a config option to disable documentation on hover. Right now cutting it to first sentence is confusing and wrong because it creates wrong understanding by putting first phrase out of context and creating wrong impression for a developer that this first sentence IS the description, while it's not. It must either be full docs or no doc at all.

I like the small doc to not clutter everything. Before Gopls, when you have you get a mini version of the doc (or none), but if you cmd+hover you get the full doc/definition. That was quite useful, because sometimes I just want to see the signature without having to recognize it from the docs...and sometimes I want to read the docs so I just cmd+hover

Filed https://github.com/microsoft/language-server-protocol/issues/772 to get more clarity on textDocument/hover.

I personally would prefer to have full comments over the single line version, but I can understand the desire to only see the signature at times.  Is it possible to add a configuration that will change the length of comments that you see on hover?
Something like: showFullComments: true (default: false)
A setting like this would allow each developer to decide the style of comments they see when hovering.

That does seem like a reasonable solution while we wait on modifications to the LSP specification. I think the options should be 1) full, 2) shortened, 3) single line (to support clients like vim-go, which currently trims to a single line).

I think gopls must either not show doc at all or show full docs. Cutting first sentence out of the context is simply wrong. There a lot of cases where first sentence is smth like You can use that method for anything you like. and second But do it at own risk. It's not supported. It's DEPRECATED. (exaggerating)
Adding additional click to this flow is also wrong. It's degraded user experience. Documentation on hover  vs documentation on hover + CLICK is HUGE difference. In the last case you'll put VS Code with vscode-go down the bottom of rank of good Go editors.

Latest Vim have popup window. it can indicate multiple-lines. vim-lsp have already option to switch hover to popup.

@mattn: Right, I have heard that the latest versions of Vim have popups, but I think a large number of people are still using older versions. vim-go also strips hover information to turn it back into a single line, so I think it would be simpler for gopls to provide the single line, at least for now.

@stamblerre how do I use this new option?

Add this to your VSCode settings:
"gopls": {
        "hoverKind": "SingleLine", // hoverKind can be NoDocumentation, SingleLine, Synopsis, FullDocumentation
}

I will add more documentation to the gopls wiki once we solidify the supported set of configurations.

@stamblerre thanks, that works, I will use "FullDocumentation". Now with that option available, may I ask to move signature above the documentation, as it was done previously in sourcegraph's language server, bingo, and as in default vscode-go config with godoc or gogetdoc? Because now I have to scroll down to the bottom to just see the signature.


Capital Asset Planning System modernization

This issue has been auto-generated to facilitate questions about
 a paid opportunity that has just been posted on the
BCDevExchange.
To learn more or apply, visit the opportunity page.
The opportunity closes on Wednesday, August 21st, 2019 at 16:00 PDT.

Is it possible to clarify which MS Dynamics products are currently being used? Link to product suite.  And, if applicable, if a specific MS Dynamics certification is preferred?


Disable 'testNavigationTreeLargeDumpAndReadAsync()'

Summary
This test has been failing frequently in Swift CI and is blocking other projects.
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] Added tests N/A.
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

@swift-ci please test


Not working with VCC audiolink in unity 2022.3.6f1

Assets\Audiolink (USharpVideo Adapter)\Scripts\Audiolink_USVideo_Adapter.cs(17,22): error CS0234: The type or namespace name 'AudioLink' does not exist in the namespace 'VRCAudioLink' (are you missing an assembly reference?)
im using the audiolink package from the vrchat creator companion tool. and latest supported version of unity for vrchat SDK. 2022.3.6f1

I've just uploaded V1.0.0 which fixes this.


Looping at model_levels linked to #361_include_file_looping

create generic recipe for looping over variables at model level.
This will require setting the model level constant.
Beware that model levels differ sometimes!
Develop as extension of https://github.com/MetOffice/CSET/tree/361_include_file_looping and issue https://github.com/MetOffice/CSET/issues/361

[ ] generate cset-workflow/includes cylc include file
[ ] link into cset-workflow/meta/rose-meta.conf
[ ]

had to add from markdown_it import MarkdownIt
to get cset bake command running for looping over pressure levels. However on git commit this is removed by riff causing cset bake to fail.

had to add from markdown_it import MarkdownIt to get cset bake command running for looping over pressure levels. However on git commit this is removed by riff causing cset bake to fail.

Odd... That should be imported by cset bake itself.

rose-suite.conf: passing in [1000,850] does not work. Trying =1000,850 insetad.

Is the variable type in meta/rose-meta.conf set to python_list?


Tei merger rules

On second thought, I'm going to merge this. The transformer is not deployed and doesn't even have a main class so won't do anything even if accidentally deployed, so this should be a no-op until the transformer is in place.


Edit product raise error: Bad Request (Write requests to inventory_quantity and inventory_quantity_adjustment are no longer supported. Please use the Inventory Levels API.)

I can't edit any exist products. Everytime I save one, it raise error:
ActiveResource::BadRequest (Failed.  Response code = 400.  Response message = Bad Request (Write requests to inventory_quantity and inventory_quantity_adjustment are no longer supported. Please use the Inventory Levels API.).):
Note that I tested by load random product, then edit it's title only. this issue only appear today, my application still works fine a couple of days ago.
products = ShopifyAPI::Product.find(:all, :params => {:handle => handle})
product = products[0]
product.title = 'New title'
product.save

Here my gemfile config:
gem 'shopify_app', '12.0.5'
gem 'shopify_api', '9.0.1'

API version:

config.api_version = "2020-01"

I tried to update to latest shopify_app and shopify_api version, and change shopify api_version. Nothing works

I get the same - it is regardless if I changed those values

Yes, we had this yesterday: a really opaque side effect of the recent API changes.
The ShopifyAPI::Product has attributes such as inventory_quantity that are no longer writable, so what you have to do when you retrieve the existing record is to get only the attributes that you want:
remote_product = ShopifyAPI::Product.where(
          handle: id,
          fields: %w[id title body_html vendor product_type created_at handle updated_at published_at template_suffix published_scope tags admin_graphql_api_id options images image]
        ).first

Same with the ShopifyAPI::Variant.
remote_variant = ShopifyAPI::Variant.where(
            product_id: remote_product.id,
            fields:     %i[id barcode title price requires_shipping taxable]
          ).first

Hope that helps.

@EmmaB Excellent! Thanks a bunch, that really helps. I'll try that. Didn't even know could do that

Yes, it took a bit of looking through the docs, in the Endpoints section here: https://shopify.dev/docs/admin-api/rest/reference/products/product

Just want to add my experience using the where clause. It will give you whatever if you use where(id: ...).

remote_product = ShopifyAPI::Product.where(
          handle: id,
          fields: %w[id title body_html vendor product_type created_at handle updated_at published_at template_suffix published_scope tags admin_graphql_api_id options images image]
        ).first

Eventually, I dug this out:
ShopifyAPI::Product.find(shopify_id, params: { fields: %i[id title] })

This will give a 404 if not found, and the product if found returning the fields I want.
If I use where, it will just take the next available product - highly unexpected behaviour.
Thanks again @EmmaB for pointing me in the right direction

I'm currently creating a new product using the ShopifyAPI::Product.new method:
new_shopify_product = ShopifyAPI::Product.new       new_shopify_product.title = product.title       new_shopify_product.body_html = full_description       new_shopify_product.vendor = product.designer.name       new_shopify_product.product_type = product.classification_category       new_shopify_product.published = product.published       new_shopify_product.tags = tags       new_shopify_product.save
The above is working just fine. Then, in the same file under this block of code, I have another block of code that edit's the newly created product's options and variants like so:
new_shopify_product.options[0].name = "Size"       new_shopify_product.options[0].values[0] = combined_size       new_shopify_product.variants[0].price = product.price       new_shopify_product.variants[0].sku = product.generated_id       new_shopify_product.variants[0].compare_at_price = product.estimated_retail_price       new_shopify_product.variants[0].option1 = combined_size       new_shopify_product.save
I get this 400 error thrown when attempting to call .save. I've been trying to figure out how to use that fields call with the code I currently have, but no luck. Any ideas?

This will be fixed in this PR https://github.com/Shopify/shopify_api/pull/655

I'm currently creating a new product using the ShopifyAPI::Product.new method:
      new_shopify_product = ShopifyAPI::Product.new
      new_shopify_product.title = product.title
      new_shopify_product.body_html = full_description
      new_shopify_product.vendor = product.designer.name
      new_shopify_product.product_type = product.classification_category
      new_shopify_product.published = product.published
      new_shopify_product.tags = tags
      new_shopify_product.save

The above is working just fine. Then, in the same file under this block of code, I have another block of code that edits the newly created product's options and variants like so:
      new_shopify_product.options[0].name = "Size"
      new_shopify_product.options[0].values[0] = combined_size
      new_shopify_product.variants[0].price = product.price
      new_shopify_product.variants[0].sku = product.generated_id
      new_shopify_product.variants[0].compare_at_price = product.estimated_retail_price
      new_shopify_product.variants[0].option1 = combined_size
      new_shopify_product.save

I get this 400 error thrown when attempting to call new_shopify_product.save the second time. I've been trying to figure out how to use that fields call with the code I currently have, but no luck. Any ideas?

I learned that when I call save - the api reloads the full object with all fields. Pretty annoying

I'm currently creating a new product using the ShopifyAPI::Product.new method:
      new_shopify_product = ShopifyAPI::Product.new
      new_shopify_product.title = product.title
      new_shopify_product.body_html = full_description
      new_shopify_product.vendor = product.designer.name
      new_shopify_product.product_type = product.classification_category
      new_shopify_product.published = product.published
      new_shopify_product.tags = tags
      new_shopify_product.save

The above is working just fine. Then, in the same file under this block of code, I have another block of code that edits the newly created product's options and variants like so:
      new_shopify_product.options[0].name = "Size"
      new_shopify_product.options[0].values[0] = combined_size
      new_shopify_product.variants[0].price = product.price
      new_shopify_product.variants[0].sku = product.generated_id
      new_shopify_product.variants[0].compare_at_price = product.estimated_retail_price
      new_shopify_product.variants[0].option1 = combined_size
      new_shopify_product.save

I get this 400 error thrown when attempting to call new_shopify_product.save the second time. I've been trying to figure out how to use that fields call with the code I currently have, but no luck. Any ideas?

@alex-espinoza I learned that when I call save - the api reloads the full object with all fields. Pretty annoying

@iamkristian ive found even with the new update (v9.0.3) this is still happening. I'm now doing the following
variant.attributes = variant.attributes.except("inventory_quantity", "old_inventory_quantity")
variant.price = new_price
variant.save

adding that extra line
variant.attributes = variant.attributes.except("inventory_quantity", "old_inventory_quantity")
basically allows the rest of your code to function as it did before.

@Saibotx what api version are you on?

@Saibotx what api version are you on?

@tanema 2020-01

It seems like there was an issue in the PR deploy in #655, the team is working on a fix right now for it.

@tanema is there any update on this issue?
We've paused an API migration until this issue was fixed. If the fix is not released in the following weeks we'll have to resort to implementing the workaround ourselves, so I'd love to have an update so we can plan accordingly. Thanks!

@tanema I only ran into this after migrating to 2019-10. Will try the variant.attributes.except approach noted above.

Based on initial testing, the variant.attributes.except workaround noted above worked for me on 2019-10.

@tanema for what it's worth we just upgraded to 2021-01 and this problem was still persisting. I need to explicity remove "inventory_quantity", "old_inventory_quantity" from attributes before I am able to save a variant.
Worse now though, that the 400 Bad Request doesn't actually contain any useful information about what is wrong.
Is there any way to get more detailed response information from shopify to debug issues like these?
Thanks.


⚠ Bofrost.lu has degraded performance

In 8e0e2ad, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1798 ms

Resolved: Bofrost.lu performance has improved in e4d013f after 6 minutes.


Use HTTPS for Xcillion font requests

This is a copy of XCESS-NL/xcillion#4 (a slightly improved version of XCESS-NL/xcillion#2)

Related to XCESS-NL/xcillion#1


73 receive exit signal

[x] I understand that contributing to this repository will require me to agree with the CLA

Description

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[x] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 tech-docs
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

Noticed that these 3 containers are not that important

yes, these containers are auxiliary.
the main changes for this PR are here:
https://github.com/anyproto/any-sync-node/pull/105
https://github.com/anyproto/any-sync-filenode/pull/117
https://github.com/anyproto/any-sync-consensusnode/pull/46
https://github.com/anyproto/any-sync-coordinator/pull/79


feat: modifying proto library generation and optimizing docker files.

[x] Tests pass
[x] Appropriate changes to documentation are included in the PR

Added buf integration for generating python protobuf libraries.
Removed unused python package from requirements.
Consolidated docker files to a common base image with extending examples.
Modified the docker tooling to accommodate the buf changes.

cc @htuch