libipl: Adding function to check FCO override bit

Change:
-Adding new function update_master_proc_fco_state, which will
check the FCO bit of master proc children, if that is set,
will mark the functional state of that child as set.
Tested:
Setting the FCO bit i.e. 10000100
attributes write p10.c:k0:n0:s0:p00:c1 ATTR_HWAS_STATE 0x00000000 0x84
After istep 0, can see the value is changed to 0xe4
attributes read p10.c:k0:n0:s0:p00:c1 ATTR_HWAS_STATE
ATTR_HWAS_STATE: complex  = 0x00000000 0xe4
Signed-off-by: Chirag Sharma<EMAIL_ADDRESS>

Merged.


"Invalid highway tag" for valid tags

I'm submitting a bug report
Brief Description
Checking my edits, I've noticed that OSMCha flagged some edits in which I changed highway=bus_stop to highway=platform with the alert "Add invalid highway tag" (see for example https://osmcha.org/changesets/132583417)
What is the motivation / use case for this feature?
The highway=platform tag is a well established tag feature and it's not invalid (as per wiki)
What  is the current behaviour, (attach relevant screenshots) ?
Changeset is flagged
What  is the expected behaviour ?
Changeset should not be flagged
When does this occur ?
When adding highway=platform to a node/way
How do we replicate the issue ?

Find a node
Add highway=platform

Please tell us about your environment:
I don't think it's browser related, anyway I'm using Firefox 110.0 (64 bit) on Windows 11 Home Version 10.0.22621 build 22621

This is a 2 liner simple fix for a growing number of flagged changesets - Would be nice if we could merge and deploy this.


chore: update toolchain

A recent serde upgrade broke this crate, so navigating dependency hell
to make everything play nce again. In summary:

change toolchain to stable
update workflows
Some workflows need to run on nightly, but update to stable where
possible
re-introduce --all-features to test workflow, since simd has since
been updated
add asref and asmut to NonDebug to make clippy shut up

ACK

ACK


fix: CHK_AWS_79

Related to #10

Sadly, while the metadata options are explicitly set in the launch template, checkov is flagging the external module. I would need to disable the the download of the external module to get it to not report on those files. I would rather have a holistic view of all of the templates from here, so instead I'll just leave it as is.


Swagger CLI generated spec missing Minimal API endpoints (but they do show up in Swagger UI)

I have a requirement to use minimal APIs in a .NET 6 application, but with generic host, rather than WebApplicationBuilder (for reasons of not breaking the existing build/release pipelines, at least in the short term).
In this scenario, when I add minimal API endpoints, they show up in the Swagger UI, but if I then try to generate a spec using the CLI they are missing.
Steps to recreate:

Create a new .NET 5 application
Update it to .NET 6 (by changing the .NET version number in csproj)
Register a minimal API endpoint in startup.cs Configure method:

app.UseEndpoints(endpoints =>
{
    endpoints.MapGet("HelloWorld", (int subscriberId) => "Hello World").WithName("Test");
    endpoints.MapControllers();
});

Add this call to ConfigureServices

services.AddEndpointsApiExplorer();

Update Swashbuckle.AspNetCore to 6.4.0

Launch the app, notice that the endpoint shows up in Swagger UI.
Launch the swagger CLI to generate a spec from the resulting web application's .dll file:
swagger tofile --output api-spec.json ./bin/Debug/net6.0/YourWebApplication.dll v1

The minimal api endpoint for "Hello World" is not included in the generated api-spec.json file (but the controller actions are).

I can confirm it still exists on Swashbuckle.AspNetCore 6.5.0.

Duplicate of #2290


Fixed windows share is not idempotent when using local groups

Description
windows_share is not idempotent when using local groups
Related Issue
Fixed: https://github.com/chef/chef/issues/9242
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.

@sanga1794 Can you add some specs for the various scenarios of user inputs? We'll want to make sure whatever solution works for local users with the hostname, local users w/o the hostname, and domain users.

Hi @tas50, I have added some specs
when full_users are passed
 behaves like when users are passed
   add hostname to user with hostname
   add hostname to user without hostname
when change_users are passed
 behaves like when users are passed
   add hostname to user with hostname
   add hostname to user without hostname
when read_users are passed
 behaves like when users are passed
   add hostname to user with hostname
   add hostname to user without hostname

@tas50, if still missing something, please do inform

@tas50 Please review the change.
Thanks!!

Something went wrong in this rebase and it brought in a bunch of other commits.

Duplicate PR https://github.com/chef/chef/pull/10122


[WIP] Translating Pacenotes from one scheme to another

Describe the contribution to the taxonomy

translating entries from mapping tables with additional noise.
or translating rally pacenotes from one format into another format

Input given at the prompt
| Numeric | Reverse Numeric | Desriptive |
|---------|-----------------|------------|
| 1       | 6               | Hairpin    |
| 2       | 5               | Bad        |
| 3       | 4               | 90         |
| 4       | 3               | Medium     |
| 5       | 2               | Fast       |
| 6       | 1               | Easy       |

In a rally roadbook, given the the pacenotes in Numeric format: "1 left", "3 right", "6 right",  "2 left", "4 left", "5 right". Refor
mat the notes into descriptive format.

Response that was received

│ The reformatted pacenotes in descriptive format are: "Hairpin left", "90 right", "Fast right", "Easy left", "Medium left", "Bad right". │
│ In this format, "90" represents a 90-degree right turn, making it easier for the driver to understand the road conditions better.       │

Response that is now received instead

  ...

Contribution checklist

[ ] Contribution was tested with lab generate
[ ] No errors or warnings were produced by lab generate
[ ] All commits are signed off (DCO)
[ ] The qna.yaml file was linted and prettified (yaml-validator can do both)

Thank you for your contribution to InstructLab! Unfortunately, once a Github repo is made public, all open PRs are automatically closed since they link against a private repo. We have detected that your PR might have been one of the ones affected by this change. If you are still interested in contributing your improvement, please fill out the following short form by no later than May 3rd, and we will get back to you with the additional steps necessary once we have had time to assess the PRs of those still interested:
https://forms.gle/V7SrPPMZDo6iGDYu8


[Bug]: shopify cli 3.69.2 overreporting wasm size

Please confirm that you have:

[x] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[x] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Extension
Expected behavior
shopify app deploy succeeds when the wasm is only 200kb
it3@it3s-MacBook-Pro-2 jaanuu_shopify_backend % ls -lh extensions/cart-embroidery-fee/target/wasm32-wasi/release/cart-embroidery-fee.wasm
-rw-r--r--  2 it3  staff   199K Oct 23 16:03 extensions/cart-embroidery-fee/target/wasm32-wasi/release/cart-embroidery-fee.wasm
it3@it3s-MacBook-Pro-2 jaanuu_shopify_backend %

Actual behavior
Shopify rust wasm deployment failing with errors about wasm is over 250kb even though it is under after upgrading shopify cli to @shopify/cli/3.69.2.
╭─ error ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  Version couldn't be created.                                                                                │
│                                                                                │
│  cart-embroidery-fee                                                                                │
│                                                                                │
│  Validation errors                                                                                │
│    • Wasm file size must be less than 256KB                                                                                │
│                                                                                │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

downgrading shopify cli to 3.68 fixes the issue and the shopify app deploy succeeds again with the same resulting file size for the wasm:
it3@it3s-MacBook-Pro-2 jaanuu_shopify_backend % ls -lh extensions/cart-embroidery-fee/target/wasm32-wasi/release/cart-embroidery-fee.wasm
-rw-r--r--  2 it3  staff   199K Oct 23 16:03 extensions/cart-embroidery-fee/target/wasm32-wasi/release/cart-embroidery-fee.wasm

Verbose output
n/a
Reproduction steps

npm install -g<EMAIL_ADDRESS>shopify app deploy

Operating System
MacOS
Shopify CLI version (check your project's package.json if you're not sure)
3.69.2
Shell
No response
Node version (run node -v if you're not sure)
No response
What language and version are you using in your application?
No response

Hi @mironov @andrewchen5678 can you try again and let me know if it works for you now? thanks!

It is working for me with @shopify/cli/3.69.4, thanks.

Awesome, thanks for reporting this 🙏


When modify maven.compiler.source to 1.8 we got issue in PerfTestServiceConfig.class

when you modify your pom of below part.
	<properties> 		<webappdir>${basedir}/src/main/webapp</webappdir> 		<deploy.dir>${basedir}/../../deploy</deploy.dir> 		<maven.compiler.source>1.8</maven.compiler.source> 		<maven.compiler.target>1.8</maven.compiler.target> 	</properties>
Then you will got error in org.ngrinder.perftest.service.PerfTestServiceConfig and it says:
"ClusteredPerfTestService.class and PerfTestService.class are not imcompitable".
mainly it caused by the compiler language "level 7" doesn't check inheritation properly.

oh .~~ it seems you had already changed code. sorry for this ticket. let's close it.

@molihan
Maven will be not used in the next version.


fix: remove marsshal and unmarshal modification in changelog

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

/azp run go - generator

/check-enforcer override

Override check enforcer because of some issue for the recent added Dump Package properties.


Mention images are bootc compliant in docs/readme

I noticed that ucore images derive from fedora-coreos. I think having bootc images deriving from fedora-bootc would also be a good addition. Is this a planned feature?
I rebased from a bootc system to ucore and it seems that the ucore:stable image is a bootc image given the containers.bootc label.
I wonder if this is a documentation error?

I welcome a PR to add something to the docs.
Since ucore only builds upon Fedora CoreOS, we should be bootc compliant if it is.

Thanks for the reply. I think given how new everything is combined with the fact that fedora coreos doesnt advertise its bootc compliance well led me to this confusion. I'll see what I can do in terms of a PR. (Can close the issue if desired)


pipfile is not updating

Hi there, I have a use case, I've created a project and did pipenv shell in that, then I wanna use this environment for other projects as well, for that I copied the environment path using pipenv --venv then in the desired second project I just did source {pasting the output of last command}/bin/activate so now I've activated the environment of first project in second project. Now When I am installing anything with pipenv install {any package} it creates(pipfile) in second project , but the pipfile in first project is not updated even I go in first project folder and trying using pipenv install, pipenv update, pipenv lock. Is there any solution/workaround for this problem and better if pipfile is not created in second project and just updated in first project whenever I install new package.
Thanks
$ pipenv --support
Pipenv version: '2020.8.13'
Pipenv location: '/home/myounus/.local/lib/python3.6/site-packages/pipenv'
Python location: '/usr/bin/python3'
Python installations found:

3.8.4: /home/myounus/.pyenv/versions/3.8.4/bin/python3.8
3.8.3: /home/myounus/.pyenv/versions/3.8.3/bin/python3.8
3.8.2: /home/myounus/.pyenv/versions/3.8.2/bin/python3.8
3.8.1: /home/myounus/.pyenv/versions/3.8.1/bin/python3.8
3.8.0: /home/myounus/.pyenv/versions/3.8.0/bin/python3.8
3.7.4: /home/myounus/.pyenv/versions/3.7.4/bin/python3.7
3.6.9: /usr/bin/python3.6
3.6.9: /usr/bin/python3.6m
3.6.9: /usr/bin/python3
2.7.17: /usr/bin/python2
2.7.17: /usr/bin/python2.7

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.6.9',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '4.15.0-117-generic',
 'platform_system': 'Linux',
 'platform_version': '#118-Ubuntu SMP Fri Sep 4 20:02:41 UTC 2020',
 'python_full_version': '3.6.9',
 'python_version': '3.6',
 'sys_platform': 'linux'}

System environment variables:

LC_ADDRESS
XDG_CONFIG_DIRS
LC_TELEPHONE
LANG
DISPLAY
SHLVL
LOGNAME
XDG_VTNR
MANDATORY_PATH
LC_NAME
PWD
USER
XAUTHORITY
GTK_IM_MODULE
GJS_DEBUG_TOPICS
XDG_SESSION_ID
COLORTERM
GNOME_TERMINAL_SCREEN
DESKTOP_SESSION
XDG_SESSION_DESKTOP
GDMSESSION
GNOME_DESKTOP_SESSION_ID
DEFAULTS_PATH
WINDOWPATH
PAPERSIZE
LC_MEASUREMENT
LC_NUMERIC
LC_MONETARY
IM_CONFIG_PHASE
DBUS_SESSION_BUS_ADDRESS
QT_ACCESSIBILITY
USERNAME
CLUTTER_IM_MODULE
GNOME_TERMINAL_SERVICE
TEXTDOMAIN
LC_PAPER
TEXTDOMAINDIR
QT4_IM_MODULE
LC_IDENTIFICATION
XDG_MENU_PREFIX
SHELL
GNOME_SHELL_SESSION_MODE
XDG_DATA_DIRS
LC_TIME
TERM
SESSION_MANAGER
GJS_DEBUG_OUTPUT
XDG_SESSION_TYPE
GTK_MODULES
QT_IM_MODULE
SSH_AGENT_PID
PATH
XDG_CURRENT_DESKTOP
XMODIFIERS
HOME
XDG_RUNTIME_DIR
SSH_AUTH_SOCK
XDG_SEAT
VTE_VERSION
GPG_AGENT_INFO
OLDPWD
ZSH
PAGER
LESS
LSCOLORS
LS_COLORS
CONDA_EXE
_CE_M
_CE_CONDA
CONDA_PYTHON_EXE
CONDA_SHLVL
_
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PIP_SHIMS_BASE_MODULE
PIP_PYTHON_PATH
PYTHONFINDER_IGNORE_UNSUPPORTED

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: /home/myounus/bin:/usr/local/bin:/home/myounus/anaconda3/condabin:/home/myounus/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
SHELL: /usr/bin/zsh
LANG: en_US.UTF-8
PWD: /home/myounus

Here is a workaround: After you enter the subshell with pipenv shell, clear the env var PIPENV_ACTIVE (unset PIPENV_ACTIVE and everything is as expected).

Here is a workaround: After you enter the subshell with pipenv shell, clear the env var PIPENV_ACTIVE (unset PIPENV_ACTIVE) and everything is as expected.

But that will create new virtual environment related to second project, right?But I dont wanna do that I just wanna use 1 common environment for multiple projects.

But that will create new virtual environment related to second project, right?

No, do this step before any pipenv install operations

But that will create new virtual environment related to second project, right?

No, do this step before any pipenv install operations

No difference it still creating pipfile in new other project, and pipfile in first main project is not updated.

You need to check this https://pipenv.pypa.io/en/latest/advanced/#pipenv.environments.PIPENV_PIPFILE

You need to check this https://pipenv.pypa.io/en/latest/advanced/#pipenv.environments.PIPENV_PIPFILE

Thanks its working.


Update Saucelabs credentials

Currently using the ones from Steal which is messing up the matrix on the readme page.

we still need to fix this

This is how Steal's matrix looks right now because of some broken steal-css build.

@matthewp were you able to create the account for steal-css? I can't remember what was the problem
I'm going to merge one of the greenkeeper PRs in steal to trigger a new build, hopefully that fixes the matrix.


TensorFlow-GPU random GPU crashes while training

System information

Custom code - Simple q learning model using Keras with TF and Open AI Gym
Windows 10
Tensorflow installed with pip
TensorFlow-gpu 1.7.0
Python 3.6.4
CUDA 9.0, cuDNN 7
Nvidia GeForce GTX 1050 Ti GDDR5 4GB

Describtion
When I'm running a script randomly two types of errors happen:

Blue Screen with Driver Power State Failure
TensorFlow cannot locate gpu " failed call to cuInit: CUDA_ERROR_NO_DEVICE"

This happens approximately once per 10 runs. GeForce is my secondary gpu card, so I assume, that it is not related to watchdog timer.
Result od deviceQuery:

Device 0: "GeForce GTX 1050 Ti"
CUDA Driver Version / Runtime Version          9.0 / 9.0
CUDA Capability Major/Minor version number:    6.1
Total amount of global memory:                 4096 MBytes<PHONE_NUMBER> bytes)
( 6) Multiprocessors, (128) CUDA Cores/MP:     768 CUDA Cores
GPU Max Clock rate:                            1620 MHz (1.62 GHz)
Memory Clock rate:                             3504 Mhz
Memory Bus Width:                              128-bit
L2 Cache Size:                                 1048576 bytes
Maximum Texture Dimension Size (x,y,z)         1D=(131072), 2D=(131072, 65536), 3D=(16384, 16384, 16384)
Maximum Layered 1D Texture Size, (num) layers  1D=(32768), 2048 layers
Maximum Layered 2D Texture Size, (num) layers  2D=(32768, 32768), 2048 layers
Total amount of constant memory:               65536 bytes
Total amount of shared memory per block:       49152 bytes
Total number of registers available per block: 65536
Warp size:                                     32
Maximum number of threads per multiprocessor:  2048
Maximum number of threads per block:           1024
Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
Max dimension size of a grid size    (x,y,z):<PHONE_NUMBER>, 65535, 65535)
Maximum memory pitch:<PHONE_NUMBER> bytes
Texture alignment:                             512 bytes
Concurrent copy and kernel execution:          Yes with 2 copy engine(s)
Run time limit on kernels:                     Yes
Integrated GPU sharing Host Memory:            No
Support host page-locked memory mapping:       Yes
Alignment requirement for Surfaces:            Yes
Device has ECC support:                        Disabled
CUDA Device Driver Mode (TCC or WDDM):         WDDM (Windows Display Driver Model)
Device supports Unified Addressing (UVA):      Yes
Supports Cooperative Kernel Launch:            No
Supports MultiDevice Co-op Kernel Launch:      No
Device PCI Domain ID / Bus ID / location ID:   0 / 1 / 0
Compute Mode:
< Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >
deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 9.0, CUDA Runtime Version = 9.0, NumDevs = 1
Result = PASS

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Windows 10
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.7.0
Python version: 3.6.4
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: 9.0/<IP_ADDRESS>
GPU model and memory: GeForce GTX 1050 Ti GDDR5 4GB
Exact command to reproduce: N/A

I can add, that that BSOD happens at the end of the script, so it might be an issue with delating objects or freeing GPU memory.

Do you have a reproducible code that contains tensorflow script only? It might be a Open AI Gym issue

This happened previously without Open AI Gym when I was using Jupyter notebook from Intel's course on tensorflow.
I tried to reproduce this bug using both example code and my script but since I've updated tf-gpu to 1.8.0 issue seems to go away. I'll update if problem returns.

20 mins after posting previous comment error returned. When I was training my DDPG agent error occured after ~600 episodes:

2018-05-03 15:24:23.086336: E T:\src\github\tensorflow\tensorflow\stream_executor\cuda\cuda_event.cc:49] Error polling for event status: failed to query event: CUDA_ERROR_UNKNOWN
2018-05-03 15:24:23.091324: F T:\src\github\tensorflow\tensorflow\core\common_runtime\gpu\gpu_event_mgr.cc:208] Unexpected Event status: 1

Maybe it is related to GPU running at full speed for a long time?
I will try to reproduce this using code without open ai gym, but I have to find an example that uses gpu for extended time first.

Nagging Assignee @bignamehyp: It has been 23 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @bignamehyp: It has been 37 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 29 days with no activity and the awaiting response label was assigned. Is this still an issue?

Hi @NightCrawler96!
I'm facing the same issue as you described.
Here is my setup:

Custom code - Keras with TF on
Windows 10
Tensorflow installed with pip
TensorFlow-gpu 1.8.0
Python 3.6.2
CUDA 9.0, cuDNN 7
Nvidia GeForce GTX 1070 GDDR5 8GB

By the way, did you find any solution for it?

It has been 15 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 30 days with no activity and the awaiting response label was assigned. Is this still an issue?

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!

Sorry for long time without an activity. I had some health issues and had to focus on that first.

I think this issue has been solved.
My laptop finally broke and I had to reinstall everything. With my current setup everything runned for about 9 hours using GPU, so I think it is unlikely to return again.
When I was writing this comment I figured out, that I had forgotten to install cuDNN. It was running smoothly without it.
Current setup:

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.9.0
Python version: 3.6.6
CUDA/cuDNN version: 9.2.148/None
GPU model and memory: GeForce GTX 1050 Ti GDDR5 4GB


2.0" ST7789 display wraps right 1/4 around to the left

https://www.adafruit.com/product/4311
I noticed that this topic https://github.com/juj/fbcp-ili9341/issues/91 is also about a 320x240 display, but curiously if I change the code to set DISPLAY_NATIVE_WIDTH to 320 instead of the HEIGHT, what ends up being displayed is mirror flipped and unreadable.
So, here is the diff showing what I edited in the code to support this display:
diff --git a/st7735r.h b/st7735r.h
index 789b4b6..2801309 100644
--- a/st7735r.h
+++ b/st7735r.h
@@ -17,7 +17,7 @@

 #if defined(ST7789) || defined(ST7789VW)
 #define DISPLAY_NATIVE_WIDTH 240
-#define DISPLAY_NATIVE_HEIGHT 240
+#define DISPLAY_NATIVE_HEIGHT 320
 #elif defined(ST7735R)
 #define DISPLAY_NATIVE_WIDTH 128
 #define DISPLAY_NATIVE_HEIGHT 160

This yields a result of:

As you can see if you look closely, the raspberries on the top should be aligned to the left. What appears to be happening is that the left-most (or top most?) 80 pixels are displaying the right-most 80 pixels of the buffer, it is wrapping...
I'd like to just inquire if anyone else has tried this display and encountered this or could comment on what i might be able to edit to cleanly resolve the issue.

I've gotten the offset fixed by having the code changed to:
diff --git a/st7735r.cpp b/st7735r.cpp
index ceac386..5b73c3f 100644
--- a/st7735r.cpp
+++ b/st7735r.cpp
@@ -92,7 +92,7 @@ void InitST7735R()
     // memory in row addresses Y = 319-(0...239) = 319...80 range. To view this range, we must scroll the view by +80 units in Y
     // direction so that contents of Y=80...319 is displayed instead of Y=0...239.
     if ((madctl & MADCTL_ROW_ADDRESS_ORDER_SWAP))
-      SPI_TRANSFER(0x37/*VSCSAD: Vertical Scroll Start Address of RAM*/, 0, 320 - DISPLAY_WIDTH);
+      SPI_TRANSFER(0x37/*VSCSAD: Vertical Scroll Start Address of RAM*/, 0, 0);
 #endif

     // TODO: The 0xB1 command is not Frame Rate Control for ST7789VW, 0xB3 is (add support to it)
diff --git a/st7735r.h b/st7735r.h
index 789b4b6..2801309 100644
--- a/st7735r.h
+++ b/st7735r.h
@@ -17,7 +17,7 @@

 #if defined(ST7789) || defined(ST7789VW)
 #define DISPLAY_NATIVE_WIDTH 240
-#define DISPLAY_NATIVE_HEIGHT 240
+#define DISPLAY_NATIVE_HEIGHT 320
 #elif defined(ST7735R)
 #define DISPLAY_NATIVE_WIDTH 128
 #define DISPLAY_NATIVE_HEIGHT 160

The intent is that display_native_width and _height are inherent to the display in question and are defined by the panel scan order. Try using the landscape/portrait rotation define in config.h primarily if that solves the issue?

In my testing, the only way to get this particular display to utilize all of its surface is to set DISPLAY_NATIVE_HEIGHT to 320, rather than DISPLAY_NATIVE_WIDTH to 320. This is regardless of whether the #define DISPLAY_OUTPUT_LANDSCAPE gets commented out.
Perhaps that is enough to reveal what the scanline direction is for the display. There are no datasheets to be found yet for this product.
it really does seem like for this product the 80 px "offset" just doesn't apply, because changing that math fixes the issues.

I can confirm that the 320x240 pixel ST7789 (in my case this one from Adafruit) does work with the changes suggested in this issue.
As there are also ST7789-displays with 240x240 pixel I'd also vote for adding an option to select the pixel resolution for the ST7789 driver.

I can also confirm it works fine, adding the -DST7789_240X320 variant would be great!

I can also confirm it works fine, adding the -DST7789_240X320 variant would be great!

Recently tested this on an Adafruit 2.0" 320x240 Color IPS TFT Display with microSD Card Breakout like others in this thread.
The display would just show a black screen with -DST7789=ON, and would only work with -DST7789VW=ON.
The only change I needed to make was to DISPLAY_NATIVE_HEIGHT, it seems to work fine with or without the offset change in st7735r.cpp.
I'm not familiar with what the difference is with the VW variant, but perhaps some batches of the display are using different controllers. The panel on mine says 2018/05/30.
The panel itself is a STP240320_0200B, seemingly only sold by this one vendor on aliexpress.
Unfortunately the "datasheet" appears to just be a mechanical drawing and the pinout.
I've purchased a few from them directly and used them to assemble a breakout equivalent to the Adafruit one and they seem to have the same behavior.


Add support for Android SDK 23

[ ] Change minSDK to 23
[ ] Test if code is compatible with sdk 23

Just to points out that in your article,  Beginner Guide to WalletConnect v2.0 Sign Protocol, you currently mention the min Android SDK as 23 but not supported (yet).


Organizations / groups from LDAP

As the subject says, this would be a nice feature to have. Rationale: as I said, KDE is evaluating Gogs for its public Git infrastructure, and this is one of the features that are important. Since th number of accounts are large (1000+) the idea would be to use LDAP to get groups ("Organizations" in gogs speak) and assign people to them.
For reference, this is a feature that GitLab has, but only it its for-pay variant.

What is the status of this issue?

Any updates?

Close due to lack of feedback.

I would like to re-open this issue. It would be nice to be able to sync LDAP groups with gogs organizations. I'm thinking about replacing a gitlab instance by gogs and this feature would be very useful.

@Fnux If I might ask, why would you want to replace gitlab with gogs? Not to dis gogs, love it all day long. Just wondering what your thinking is here.

We should allow - on a specific LDAP source - to sync some groups with the local "Organizations".
A way would be to add this part in each LDAP source configuration page. You should be able to add as many "links" as you can : just two fields per "link".

the LDAP group
the local "Organization"

And when an user sign up using this source, gogs should check if it belongs to the specified group. If that's the case, add him to the related organization. We also have to check if the user was removed from the specified group : check once every X hours ? First login of the day ? Every login ?
Sadly, I do not have the time/knowledge to do it by myself right now. (Maybe in late January/February?)

We should allow - on a specific LDAP source - to sync some groups with the local "Organizations".
A way would be to add this part in each LDAP source configuration page. You should be able to add as many "links" as you can : just two fields per "link".

the LDAP group
the local "Organization"

And when an user sign up using this source, gogs should check if it belongs to the specified group. If that's the case, add him to the related organization. We also have to check if the user was removed from the specified group : check once every X hours ? First login of the day ? Every login ?
Sadly, I do not have the time/knowledge to do it by myself right now. (Maybe in late January/February?)

@Dasoren Well, I used GitLab a while for myself and I'm actually maintaining a GitLab instance for an association. We're in an university. We have our own LDAP, the school has its LDAP and an authentification system called "Tequila". GitLab CE allows a single LDAP server, so I had to change few things in order to allow authentification through "Tequila". It's awful to maintain (really). It takes a lot of ressources. It's way to complex.
About Gogs :

Easy to maintain (:heart: that's the big point). No dependencies except database.
Way more simple than the whole GitLab-sutff.
The interface is great.
Use something like 50 times less resources

@Dasoren Well, I used GitLab a while for myself and I'm actually maintaining a GitLab instance for an association. We're in an university. We have our own LDAP, the school has its LDAP and an authentification system called "Tequila". GitLab CE allows a single LDAP server, so I had to change few things in order to allow authentification through "Tequila". It's awful to maintain (really). It takes a lot of ressources. It's way to complex.
About Gogs :

Easy to maintain (:heart: that's the big point). No dependencies except database.
Way more simple than the whole GitLab-sutff.
The interface is great.
Use something like 50 times less resources

@Fnux great points!
Is it a one-way sync or two-way sync?

+1
I would also add a third option to select the team and rights. In order to distinguish between read, write and admin access. So given the LDAP groups:

group1
group1-admin
Then in gogs there would be 1 organization (group1) with 2 teams (admin and default?), the first one with admin rights by default. The organization and team are created after the configuration, and then the users are added to each team (at login time or via batch process)

Usage of LDAP groups is a must have if using Gogs in a company. As @nestabur said: Automatic distinction between different permissions will be a great advantage.

Thanks @nestabur ! Will consider that definitely.

+1

I'm interested in this as well.  However, I wanted to ask, does Gogs even have a self hosted Groups feature at the moment to build this LDAP group support on top of?  Perhaps that feature should be a seperate task from this?

Same we will be moving to gitlab without ldap group integration. Basically we want some groups to see certain repos others cannot

It would also be a useful feature for OSGeo, another organization using LDAP and evaluating a switch from trac to Gogs: http://www.osgeo.org

I would suggest this to work as a one-way sync. When an LDAP user logs in, a search is performed to find out the user's LDAP group memberships and the gogs groups memberships would be updated to match. How will groups be mapped to LDAP groups? Just by cn? or should groups/organizations have an LDAP-dn attribute? That could be nice if you want to keep a mix of ldap and gogs groups, but a lot of work with lots of groups.

One-way is how email information also works, right ?
That is, if the mail field is updated in the LDAP server,
Gogs won't notice the update, correct ?

Do you mean one-time? One-way would be information moving only from LDAP -> gogs. Two-way would be LDAP -> gogs and gogs -> LDAP, i.e. LDAP <-> gogs.

Yes, I meant one-time. Is the email field only retrived one-time from LDAP to Gogs ?
I don't see a way to change email in Gogs so I guess it is also one-way.

It could check the information from LDAP on every login

I've just checked and as of Gogs Version <IP_ADDRESS>8 the local user email is not updated on a new login after changing the email in the LDAP server. I agree it would be recommendable to sync on login (new login, new sync). Then there'll need to be a way to enforce logging out every user as an administrator, when important changes are made to the LDAP directory.

+100 We also definitely need this feature - this would make "!the!" big difference against gitlab

Yes, we would also consider moving from gitlab to gogs if we could sync LDAP->gog groups :)

I would love this feature!
LDAP group -> Gogs : one-way synchronization.
I'd think that it should check the groups on each login (when it does lookup in ldap anyway?).
Note there's generally 2 direct methods for LDAP/AD groups (that are usually both applied for consistency)

Specify the 'MemberOf' or 'UniqueMemberOf' attributes on the User (DN). The attribute usually contains one or more CN's to groups (ex: CN=DevOps,OU=Development,DC=organisation,DC=com).

Specify the 'Member' or 'UniqueMember' attributes on the Group (DN). The attribute usually contains  one or many more of either the full DN or UID of the User(s).

Depending on security settings for directly authenticated users and visibility of the groups, often an 'admin account' is used to be able to parse groups without restrictions.
Most of the times I've seen this requiring 3 parameters:
BindDN: full DN to authenticate the admin account
BindPassword: password to authenticate admin account
GroupSearchBase: DN from where to parse the group structure (ex: OU=Development,DC=organisation,DC=com)
Sometimes the attribute for members can also be specified (Member/UniqueMember).

For me this is absolutely key to have an oneway group-sync between LDAP and GOGS organisations.
What jortkoopmans describes above would work for me too. +100 if this gets completed.

Also +1 to what @jortkoopmans said. We do want to switch to Gogs instead of Gitlab but there's no group from LDAP support in gogs.

@jortkoopmans - I'd also add that a configurable group filter is necessary, for OUs that aren't necessarily clean (ie: non-group objects are - unfortunately - lumped into the same group search base).
'(objectClass=group)' (or anything else, as necessary)
GitLab EE also had - and fixed - a similar group filtering issue (GitLab support ticket 16230), for their LDAP group sync feature.

In my opinion, it does not make sense to synchronize ldap groups to gogs. While we can live without this feature, here's a suggestion how to implement this.

Add new configuration items for ldap: membership filter (list of groups for given user) and user member filter (list of users for given group) Ignore support of nested groups for now
Add new configuration item for team: security groups. For ldap you would store full name of security group (listed/verified using member filter)
When listing team members, include such members from ldap that are not in any other team (again, use member filter)
When checking for user rights, prefer highest. User that belongs to administrative privileges should be granted them (even if same user is part of a team with read only privileges) (this is where you would prefer use of membership filter for performance reasons)
Finally when you have everything in place, implement caching (While ldap can ben fast - really fast, sizes of groups can be huge. Querying list of group members for each page view, might not make sense)

I'm seeing a new feature in the changelog that might be related, generated from pull req #4398?

@jortkoopmans right... but I think #4398 is a start, not yet complete all the requests in this thread maybe... since this is very long, not really sure :sweat:

I can have a look at it next week. Having authentication and authorization code in one place makes it a bit cumbersome to follow. If I got it right, team name is used for searching ldap when checking user's permissions for repo.

I see, the patch #4398 is not what I expected it to be. It allows controlling access to gogs using ldap groups. However, it does not allow settings read/write access of repositories using ldap groups.
I'm not quite sure, if this is the right way to go. These queries can't be reused later on for repository access / control. You will have to almost identical queries / filters defined in config. I'd rather see group filter defined using the same parameter format that was used with user filter. This filter should be used with a list of allowed groups and the query should be executed once per item - until allowed group is found. This would also allow one to implement restrictions based on groups without defining additional queries. And it would also allow one to reuse queries when implementing access control for repositories

Phew, that was a lot of work. (Learning basic of new language in a day and fixing ldap-configuration to something that most people are more used to). I won't be bothering to post a pull request before I get repository to use ldap as an authorization source, but you can check/track changes here on my fork at ldap_repositories -branch.
There's bunch of new mandatory configuration items, as you can see from the picture:

Some of them will get default values later on (most organizations use standard values)
While I am at it, I will propably look, if it would be possible not to copy user data to gogs, when using ldap for authentication and authorization (or at least sync data on every login). While I can't see any benefit for doing so, I can find many issues that this causes. I think gogs's internal database should be just one of many authentication / authorization sources. As in real world, also in gogs, accounts should be accessible using various authentication methods.

I have now integrated ldap for access control and verified mechanism with manual testing (there's no unit tests in go / in this project?). Implemented algorithm is quite naive, but it's best I could come up with current domain model.
Important part is in models/access.go:
   // If this repository is linked to teams
    err := repo.GetOwner()
    if err != nil {
            return mode, err
    }
    if repo.Owner.IsOrganization() {
            // We need user for name. Id is just pointer to database
            user, err := GetUserByID(userID)
            if err != nil {
                    return mode, err
            }
            // We need to check, which authorization source user is bound to
            // It would be nice, if we had an interface to work with :-(
            // Otoh. LDAP is currently only true authorization source
            if user.LoginType == LOGIN_LDAP {
                    lsrc, err := GetLoginSourceByID(user.LoginSource)
                    if err != nil {
                            return mode, err
                    }
                    ldap := lsrc.LDAP()
                    // Get UID
                    uid, ok := ldap.GetUID(user.Name)
                    if !ok {
                            return mode, fmt.Errorf("could not get uid for: %v", user.Name)
                    }

                    // Reusing existing queries...
                    // We could use a query, that gets all teams for given repo
                    // But... I don't like the current domain model - so I won't do it :-)
                    teams, err := GetTeamsByOrgID(repo.Owner.ID)
                    if err != nil {
                            return mode, err
                    }
                    for _, team := range teams {
                            // Get access level from team,
                            // if team grants higher access level, AND
                            // if team is actually linked to repository, AND
                            // if user is member of team
                            if team.Authorize > mode && HasTeamRepo(repo.Owner.ID, team.ID, repo.ID) && **ldap.IsMemberOf(uid, team.Name)** {
                                    mode = team.Authorize
                            }
                    }
            }
    }

From here you can see, that I chose to do 1:1 binding between team and group names. You can also see, that I did not bother to do any other modifications to code. I hinted in my #4599 that, full ldap integration with current domain model is just not worth the effort. It would take days to implement all required queries. And there's a high risk, that I would get something fundamentally wrong.

It seems I would need to modify SearchRepositoryByName operation in order to get explore working properly with ldap authorization. Currently it's not utilizing access.go and it relies heavily on SQL operations (access table is joined against repository table) Because the search is returning a count, only reasonable thing to do is to fetch all repositories and filter them by access. If done correctly, this should work quite well, when gogs is managing reasonable number of repositories (N < 10000)

This is almost done. I decided to move access control related code to access.go (there was some in repo.go). Now there's only one query left that needs to be changed in order to avoid N+1 problem. I just hope, that my decision to use IN queries (for avoiding N+1 query problem) will not cause problems on sites, that have very high number (thousands) of repos

Implementation is now complete. For readability I actually ended up moving all repository related access level checks in repository.go and I modified interfaces for repository. Repository has now a new function called HasAccess with parameters user id & required access mode. For single repository code is quite clean, but for listing, it's a bit more complex (I opted for sql with nested queries instead of bombarding database with possibly thousand of queries or doing insanely long IN conditions)

Final version of settings:

As promised, there's bunch of defaults. Filters no longer have magical %v's - instead queries are built on runtime

@skorhone thanks for all the effort!
I think the OP means the LDAP group maps to an organization not a team in Gogs?

While it is possible, I don't think it would work for most/everyone. It would solve single use case where everyone in given organization has full access to organization's repos. Having privileges bound to teams (ldap groups) provides much more flexibility (you can give everyone full access, or you can give read access to some and full access to others) btw. If you are interested in the update, I can try to merge changes done since I wrote it. I took liberty to do modifications in access checks (obsoleted access table in db)

@skorhone I'm not sure why "It would solve single use case where everyone in given organization has full access to organization's repos"?

Any news? it looks great! and indeed for our use case (association) we'd most likely rather have groups mapped to teams than to organizations.
I guess something like one LDAP <-> one organization and one group in this LDAP <-> one team would make most sense (with “one LDAP” potentially including metadata such as “server:port with group_filter”), but even then the first step of a single LDAP and mapping each group in it to a team would already be a great first step, that can later on be extended to support multiple LDAPs.

Any updates on this?

We've implemented mapping LDAP groups to teams in (all) organizations (by group/team name) for Gitea and published it here, if anyone is interested,
https://github.com/tws-inc/gitea-group-sync

@alexattws can it be used for Gogs?

If the Gogs API calls that are being used match Gitea API calls, then the answer is yes.

@alexattws I have no idea (what APIs this tool uses), if it's not working with Gogs, posting here would be considered as unrelated.

The code is here: https://github.com/tws-inc/gitea-group-sync/blob/master/gitea-group-sync.go
It uses the following Gitea calls,
/api/v1/users/search
/api/v1/admin/orgs
/api/v1/orgs/orgname/teams
/api/v1/teams/teamid/members
It is related to the discussion here, as far as I understand, as Gitea is a fork of Gogs and is somewhat compatible.  I haven't tested it myself with Gogs, but if it doesn't work, someone would potentially be able to make it work by making small changes.

@alexattws Thanks! Unfortunately, I think Gogs does not have this endpoint: /api/v1/teams/teamid/members, but should be easy to add.


no pubspec.yaml found

when I create a new flutter project,out log print 'no pubspec.yaml found'

Hi @WhereareUmylove
Can you please provide your flutter doctor -v and the reproducible steps?
Thank you

Hi @WhereareUmylove
Can you please provide your flutter doctor -v and the reproducible steps?
Thank you

thankyou verymuch,I deleted the flutter SDK and downloaded a new version to solve the problem，

thankyou verymuch,I deleted the flutter SDK and downloaded a new version to solve the problem，

Hi @WhereareUmylove
Given your last message I feel safe to close this issue, if you disagree please write in the comments and I will reopen it.
Thank you

Hi @WhereareUmylove
Given your last message I feel safe to close this issue, if you disagree please write in the comments and I will reopen it.
Thank you


Migrate whenever jobs to Heroku scheduler

It looks like the whenever tasks are not currently running on Heroku. The solution is to migrate these jobs to Heroku Scheduler.

Looking at the current date/time, the sitemap hasn't been updated since March 2017:
2015-07-07 09:36:35          0 sitemaps/
2017-03-20 21:53:18        245 sitemaps/agencies.xml.gz
2017-03-20 21:53:18      22215 sitemaps/agencies1.xml.gz
2015-09-21 12:40:55         53 sitemaps/google949221dfa5e420ae.html
2017-03-20 21:53:17        240 sitemaps/sitemap.xml.gz
2017-03-20 21:53:17      71501 sitemaps/sitemap1.xml.gz

It looks like the sitemap task is running correctly:
2015-07-07 09:36:35          0 sitemaps/
2017-09-06 11:01:05        245 sitemaps/agencies.xml.gz
2017-09-06 11:01:04      23622 sitemaps/agencies1.xml.gz
2015-09-21 12:40:55         53 sitemaps/google949221dfa5e420ae.html
2017-09-06 11:01:00        240 sitemaps/sitemap.xml.gz
2017-09-06 11:01:00      78594 sitemaps/sitemap1.xml.gz


Getting error while running  setup-ara.yml file using On-Premise Solutions documentation.

Is this a BUG REPORT or FEATURE REQUEST?
Choose one: BUG REPORT or FEATURE REQUEST

What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

kubectl get nodes
kubectl get pods --all-namespaces
kubectl get services
kubectl get sc
kubectl get pv
kubectl get pvc
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:
root@rafi-virtual-machine:/home/rafi/openebs/e2e/ansible# ansible-playbook setup-ara.yml
[WARNING]: provided hosts list is empty, only localhost is available

PLAY ***************************************************************************
TASK [setup] *******************************************************************
ok: [localhost]
TASK [ara : Install ara apt packages] ******************************************
changed: [localhost -> <IP_ADDRESS>] => (item=[u'gcc', u'python-dev', u'libffi-dev', u'libssl-dev', u'python-pip', u'libxml2-dev', u'libxslt1-dev'])
TASK [ara : Install ara pip packages] ******************************************
changed: [localhost -> <IP_ADDRESS>] => (item=tox)
changed: [localhost -> <IP_ADDRESS>] => (item=ara)
TASK [ara : Get ara location] **************************************************
changed: [localhost]
TASK [ara : Create plugins folder in playbook directory if it doesn't exist] ***
ok: [localhost]
TASK [ara : Copy ara callback plugin to openebs custom plugins location] *******
changed: [localhost]
TASK [ara : Copy ara action plugins to openebs custom plugins location] ********
changed: [localhost]
TASK [ara : Copy ara modules to openebs custom plugins location] ***************
changed: [localhost]
TASK [ara : Update ansible.cfg with ara module library path] *******************
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "unsupported parameter for module: path"}
PLAY RECAP *********************************************************************
localhost                  : ok=8    changed=6    unreachable=0    failed=1
root@rafi-virtual-machine:/home/rafi/openebs/e2e/ansible#

@rafihnl Which ansible version you are using?
This error likely to happen if it the ansible version < 2.3
Prerequisite is Ansible > 2.3

I'm using anisble version 2.4

The e2e has been moved to openebs/litmus, where the dependencies are handled by the litmus container.


Google Ads API V1 Sitelink

Unable to create Sitelink.  I receive the following error:  Google Error:  Status(StatusCode=InvalidArgument, Detail="Request contains an invalid argument.")
I'm also unable to set the FinalUrl with creating  a SiteLinkFeedItem. As you can see from the code below set is not available.
public RepeatedField FinalUrls { get; }
Please attached for more detail
SiteLinkIssue.docx

You can Add() items to FinalUrls, just like you’d do in a List.
On Tue, Mar 26, 2019 at 6:56 PM RentCafeDev<EMAIL_ADDRESS>wrote:

Unable to create Sitelink. I receive the following error: Google Error:
Status(StatusCode=InvalidArgument, Detail="Request contains an invalid
argument.")
I'm also unable to set the FinalUrl with creating a SiteLinkFeedItem. As
you can see from the code below set is not available.
public RepeatedField FinalUrls { get; }
Please attached for more detail
SiteLinkIssue.docx
https://github.com/googleads/google-ads-dotnet/files/3010774/SiteLinkIssue.docx
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googleads/google-ads-dotnet/issues/61, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AETkiAcptobYibngXRHf6tpWICHXw7gyks5vaqWBgaJpZM4cMnL7
.

--
Anash P. Oommen | Developer Programs Engineer |<EMAIL_ADDRESS>|
+1-650-440-2854

When I use the following:
        return new SitelinkFeedItem()
        {
            LinkText = SiteLinkText,
            //FinalUrls = SiteLinkURL,
            Line1 = DescriptionLine1,
            Line2 = DescriptionLine2

        };

It indicates that the FinalUrls is read only.

The right way to use the field would be
var retval = new SitelinkFeedItem()
{
    LinkText = SiteLinkText,
    Line1 = DescriptionLine1,
    Line2 = DescriptionLine2
};
retval.FinalUrls.Add(...);
return retval;

The same goes for all repeated fields in the API.

Does the brackets below indicate that it's a repeated field?
final_urls[]

The fieldtype indicates so.
The type of FinalUrls is RepeatedField
On Wed, Mar 27, 2019 at 1:42 PM RentCafeDev<EMAIL_ADDRESS>wrote:

Does the brackets below indicate that it's a repeated field?
final_urls[]
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/googleads/google-ads-dotnet/issues/61#issuecomment-477274420,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AETkiAy5dqv6GBQhKiXLX9HJvCcrPdL1ks5va62PgaJpZM4cMnL7
.

--
Anash P. Oommen | Developer Programs Engineer |<EMAIL_ADDRESS>|
+1-650-440-2854


doc: fix configure indentation examples

When configuring copilot I came across those examples that didn't work, removing the . solved the issue.
Another case:
https://github.com/copilot-emacs/copilot.el/issues/312

Thanks!


Add raf.polyfill

Thanks! My only gripe with this change is that it doesn't polyfill global in a node environment. Perhaps global = typeof window === 'undefined' ? {} : window should be expanded to also check the actual global object (the variable will probably have to be renamed).

I'm not sure what you mean - global will work in node, and browserify/webpack will make the same work in browsers.

global is a local var here that hides node's global

Looking at it now, I'm not even sure it's necessary. requestAnimationFrame looks like it should get attached to window w/o this PR... I might have just needed to go to bed.

aha, that's a good point. We shouldn't have a local variable named "global".

shabam :tada:

Good stuff! Published to npm as 3.2.0.


Generate ast/pos.go automatically

This PR introduces the parser for the POS expressions (the pos/end notation in ast/ast.go) and the generator for ast/pos.go using it.
Makefile is also updated, so go generate is executed automatically in most cases.
Also, this PR adds -dig and -pos options to tools/parser for testing the POS expression.

That's a great thing for us contributors.
We can now focus on getting the Node definition right without having to worry about pos.go.
If you merge it, it will resolve the conflict in my PR.
Since the importance of tools/parse in the development flow seems to have increased, it would be nice to have examples documented on how to use -dig and -pos.

@apstndb Some examples are added to the usage of tool/parse/main.go.


Incorrect extra equals in trait docs

https://github.com/FuelLabs/sway/blob/5396f18e806f88536d8dfcb0bdcd146694d129fc/docs/src/advanced/traits.md?plain=1#L14
Should just be
!self.equals(b)

https://github.com/FuelLabs/sway/pull/1565
Fix


Workflow broken on Monterey 12.3

Apple removed Python 2 support in Monterey 12.3, and the workflow is no longer functional. A rewrite into Python 3 is needed.

Is there any progress?

mark, I hope it can be resolved soon.

I have the same issue, when trying to change the python path to another python2 executable that doesn't seem to fix it either.

I've tried setting all the workflow script paths to /usr/local/bin/python2 but that doesn't work either.

It's time to fully migrate to python3.

Manually running pwgen.py gives this error
./pwgen.py", line 200
os.makedirs(user_generator_dir, 0700)
^
SyntaxError: leading zeros in decimal integer literals are not permitted; use an 0o prefix for octal integers

We can still install python 2 as explained here:
https://www.alfredapp.com/help/kb/python-2-monterey/

We can still install python 2 as explained here:
https://www.alfredapp.com/help/kb/python-2-monterey/

Yes but it doesn’t work unfortunately 🤔

Is there any update on this? or a solution being worked on?

I got it to work by installing py27 as described here on stackoverflow (Im on m1 and using conda, other ways to get py27 working should be fine, too).
Then, all the occurences of /usr/bin/python in the workflow need to be replaced with the path to your python2 exectuable (in terminal, which python2 should give you the path).
This includes:

the script filters
the bin/bash run script actions
the hardcoded string that is located in the workflow directory: rightlick the workflow, show in finder, open the file ./workflow/background.py and search for /usr/bin/python. There should only be one occurence.

If I find a free weekend, I might add this as a workflow-wide variable that can be set, but for now this is a quick and dirty way to get it running again.

I think it's great that  a workaround exists, but a rewrite of the workflow is probably what we need. Having to install a somewhat outdated Python version just for this workflow is not really what I want to be doing.

It's hard to believe there is not even one maintainer who might be able to migrate this to python3. As I remember, the difference is not so huge for pyhton2 and python3. Unfortunately, I'm not familiar with this kind of development. Otherwise, I'd do it even by myself.

It's hard to believe there is not even one maintainer who might be able to migrate this to python3. As I remember, the difference is not so huge for pyhton2 and python3. Unfortunately, I'm not familiar with this kind of development. Otherwise, I'd do it even by myself.

Hey, chill. The maintainer has worked on this package for years completely free, they have no real obligation to continue working on it if they do not wish to do so, or perhaps they have just not had the time yet. I'm sure you might find someone who's willing to fork it and/or submit a PR to update it to Python 3 if they're compensated 🙂
Anyhow, I'm also a great fan of this package and needed a substitute, so I made somewhat of a port to Node (olssonm/alfred-password-generator) albeit with lots of fewer features if anyone's interested.

@olssonm sorry if I was too direct, but I didn't mean the repo owner by "maintainer". I meant anyone who is able to make a fix (even me if I will figure out how, hehe).

I found a project replaced it, I hope it is useful to you. alfred-password-generator

I found a project replaced it, I hope it is useful to you. alfred-password-generator

I tried it and work as advertised. The script itself is very simple, I like it a lot.

@olssonm your Node.js workflow is quite nice, and very tidy. Nicely done! 👏🏼👏🏼👏🏼

I got the workflow running again on 12.3:

Installed Python 2.7.18 on Homebrew/pyenv (https://www.alfredapp.com/help/kb/python-2-monterey/)
Installed the PyObjC-package: python -m pip install pyobjc==5.2. The latest version for Python 2.7 of PyObjC (5.3) produced a bus error on my 12.3 installation, so I installed version 5.2, which works fine
Changed the Python-paths in the Script Filters and Run Scripts to /usr/local/bin/python (in my case)

Works fine.

What if we add a custom env var that sets Python binary directory?
This way, I could just add the var in the workflow config, and it'd be used at run time, WDYT?

💡

What if we add a custom env var that sets Python binary directory? This way, I could just add the var in the workflow config, and it'd be used at run time, WDYT?

I did something similar in my ProxmoxControl-Workflow. Before running a Python-script, I exported the PYTHON_PATH variable. Seems to work fine.

I found a project replaced it, I hope it is useful to you. alfred-password-generator

This is great, super simple and straightforward. Thanks for creating this!

Manually running pwgen.py gives this error ./pwgen.py", line 200 os.makedirs(user_generator_dir, 0700) ^ SyntaxError: leading zeros in decimal integer literals are not permitted; use an 0o prefix for octal integers

change : os.makedirs(user_generator_dir, int('0700',8))

https://github.com/alfred-workflow-collections/password


Add 3 new regex pattern to bot

Hey, I added 3 more patterns to Psychobabble to improve the bot.
The first one is to detect an email. The second one is to detect a few bigger cities.
The last one is to detect the German word for a bomb (Bombe) to prevent the misusage of information surrounding that topic.

I really like your additions to the dailiza-bot. Your regex-patterns are very creative. Good job!

@l4nz8 pull request ready to be merged


How to share metastore between libraries and current project ?

I develop a library that uses tst-reflect and I want to share the metastore of a project with my library (and conversely, share the metastore of my library with the project).
In 1 word, have a common metastore.
Is it possible?

Hi @leohubert, check the discussion #58.

Now the end application using reflection should generate types, even for an npm packages.
Package built with current version can contain metadata and the package can work with them and also package can work with Types from end application.

What is not supported yet is listing of all the types using Type.getTypes(). Well, it will work partly, but... it wasn't meant to work like this in current version. It will be available in the next version.

Thanks for the reply @Hookyns!
I'll see how I can help you to move forward :)

I've designed system for this in v1. Partially implemented.

Implemented for the v1. Not in the current version.


Generate SVG (from path)

Can this also do the opposite? Can it create an SVG file based on paths? I want to make a drawing app and export the SVG.
Thanks

Will have to check if it's possible.

great to hear. svg export would provide a ton of value


Fetch new turn data automatically

At the moment, the game needs to be refreshed in order to fetch new turn data. This action should be automated.

Handled by adding refresh button


Does Front Door supported HTTP to HTTPS redirection?

I wanna elect to redirect HTTP traffic to HTTPS as-is Using the Azure CDN to access blobs with custom domains over HTTPS | Microsoft Docs. Does Front Door supported ?

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

ID: 6b393c2f-c603-6287-743f-9c169673ce41
Version Independent ID: 475325a1-e953-2723-b626-80ea86a4d347
Content: Azure Front Door Service - URL Rewrite
Content Source: articles/frontdoor/front-door-url-rewrite.md
Service: frontdoor
GitHub Login: @sharad4u
Microsoft Alias: sharadag

@nnasaki
Thanks for your feedback! We will investigate and update as appropriate.

@MarileeTurscak-MSFT Thank you! I'm looking forward to!

@nnasaki I have reached out to get more information, and will update you as soon as I am able.

@nnasaki it is not supported at this time. You can leave your feedback Here if you would like this feature to be enabled in the future.

@nnasaki We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@TravisCragg-MSFT I would like to easily redirect from HTTP to HTTPS. For example, in the AWS Cloud Front, you can do it by simply turning on the check box.

I do not want to implement such a basic function in the application.

Another +1 for http -> https and leaving other components of the URI intact (to be processed in the subsequent request by any URL rewriting, etc.)

I would love to have that too!

@nnasaki @thiezn @daveaglick @SergeBerwert This feature is currently being worked on, and you can Upvote the Feature Request Here! You can also make additional suggestions or provide additional as well.

A tip from Nathan J. Robinson's comment on the feature upvote page worked for me:

This is now supported, although not yet documented. You can add a new routing rule and set the "Accepted Protocol" to "HTTP Only", "Route Type" to "Redirect", "Redirect Protocol" to "HTTPS Only", and "Destination Host" to your Front Door host name. Set the "Accepted Protocol" on all your other routing rules to "HTTPS Only". This works to redirect HTTP to HTTPS.

A tip from Nathan J. Robinson's comment on the feature upvote page worked for me:

This is now supported, although not yet documented. You can add a new routing rule and set the "Accepted Protocol" to "HTTP Only", "Route Type" to "Redirect", "Redirect Protocol" to "HTTPS Only", and "Destination Host" to your Front Door host name. Set the "Accepted Protocol" on all your other routing rules to "HTTPS Only". This works to redirect HTTP to HTTPS.

While this does work, it requires a second routing rule, with a service charging model based on number of routing rules I feel there should be something more intrinsic to the service to support this.

The documentation has been updated with this workaround: https://docs.microsoft.com/en-us/azure/frontdoor/front-door-how-to-redirect-https

A tip from Nathan J. Robinson's comment on the feature upvote page worked for me:

This is now supported, although not yet documented. You can add a new routing rule and set the "Accepted Protocol" to "HTTP Only", "Route Type" to "Redirect", "Redirect Protocol" to "HTTPS Only", and "Destination Host" to your Front Door host name. Set the "Accepted Protocol" on all your other routing rules to "HTTPS Only". This works to redirect HTTP to HTTPS.

While this does work, it requires a second routing rule, with a service charging model based on number of routing rules I feel there should be something more intrinsic to the service to support this.

I agree. It doesn't make sense to pay a routing rule just to redirect http -> https.


Showcase Submission for code/7-arrays/4-mouse-interaction

Thank you aweya for your contribution! A member of the Coding Train team will review it shortly.

Gridifier
aweya

Great work!


Wide-mode

Expands the width of articles, from smallest width to biggest:

Also took a look at bringing comments back re - #171

OK, this is going in on green


alm does not work when external diff/mergetool for git configured

I have defined external diff and merge tools in my .gitconfig. Everytime I open alm it automatically opens my mergetool several times and I cannot work in the editor anymore. When deleting the configuration from .gitconfig alm works fine again.
[merge]
	tool = extMerge
[mergetool "extMerge"]
	cmd = extMerge \"$BASE\" \"$LOCAL\" \"$REMOTE\" \"$MERGED\"
[mergetool]
	trustExitCode = false
[diff]
	external = extDiff
[difftool "sourcetree"]
	cmd = /Applications/p4merge.app/Contents/MacOS/p4merge \"$LOCAL\" \"$REMOTE\"
	path =
[mergetool "sourcetree"]
	cmd = /Applications/p4merge.app/Contents/MacOS/p4merge \"$BASE\" \"$LOCAL\" \"$REMOTE\" \"$MERGED\"
	trustExitCode = true

Everytime I open alm it automatically opens my mergetool several times

I don't see how it can happen. Sorry if it is indeed my fault. I have absolutely no clue. Are you sure its alm doing this?

Yes, I`m sure. When I delete the gitconfig settings alm is working without problems.
But I close the ticket now if you have no idea what the reason is. I don't need the settings anymore. Found other ways for diff and merge.
Thx and regards
Helmut

Sorry, I realised something that might (obviously) be causing it and fixed it in the attached commit ^. Released it with 0.1.38 :rose:

The connection missing in my brain was opening alm vs. opening any file in alm :)

Thx, works fine now. Congratulations for this great typescript editor. Even though I'm using IntelliJ Idea for my larger projects I will give alm a try for smaller projects in the future.


GraphQl SDL conversion tool generates a weird output converting empty String default values

Summary
I came across with a weird conversion migrating our GraphQl json schema to sdl where empty string is converted to a value that the compiler doesn't support.
Version
2.5.9
Description
Migrating a String field with default value equal to empty String defined like this in the json:
{
   "name": "comment",
   "type": {
      "kind": "SCALAR",
      "name": "String",
      "ofType": null
   },
  "defaultValue": "\"\""
}

results in:
comment: String = """"""""

in the .sdl file
This causes a compilation error while running generateDebugServiceApolloSources that complains with:
Unsupported token """`
If I manually replace comment: String = """""""" by comment: String = """""", everything works fine

Yikes good catch! I would have hoped that https://github.com/apollographql/apollo-android/pull/2917 fixed this one but maybe the SDL conversion is different. Will look into it but that might take a bit of time so replacing like you did looks good 👍

I took a loot at this this morning, """""""" (8 double quotes) is not a valid GraphQL String value so the SDL writer was wrong. I could verify it's working ok with 3.x:
https://github.com/apollographql/apollo-android/blob/9ef26ff8fee08e9773a656fbf17d6edc17a0c47c/apollo-compiler/src/test/kotlin/com/apollographql/apollo3/compiler/SdlWritingTest.kt#L96


Fix MirrorPeer status updates

This commit fixes the issue where the status is always ExchangedSecret.
This will check if the secret is not found, then requeue for reconcile
after 5 seconds.
Also add integration tests for Status
Fix for https://github.com/red-hat-storage/odf-multicluster-orchestrator/issues/36
Signed-off-by: Vineet Badrinath<EMAIL_ADDRESS>

/ok-to-test

/retest

/cherrypick release-4.9


Problem Description
Solution Description
Alternatives Considered
No response
Additional Context
No response

最简单的做法就是用one-api或者new-api中转一下，大模型太多了，靠前端一一适配是有点吃力的。

QAbot-zh's answer is the most convenient way right now. If you are refer to support them in NextChat, you can refer to progress at https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/issues/4030


"Lock the dependencies"

Publish node_modules to main branch.
:)

"We don't need no stinkin' lockfile"


chore(CHANGELOG): update

Proposed Changes

FIX: add focus to checkboxes and buttons (#390)
DEPS: update to<EMAIL_ADDRESS>
Checklist
To ensure you provided everything we need to look at your PR:

[ ] Brief textual description of the changes present
[ ] Visual demo attached
[ ] Steps to try out present, i.e. using the @bpmn-io/sr tool
[ ] Related issue linked via Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}

DEPS: update to<EMAIL_ADDRESS>
I'd frame this as support diagram-js@15, no real "dependency bump" happened as I see it.


Fix for dumping exif data loaded from images that contain a Gps Versi…

…onID tag

This puts in python2 specific conditional check into _value_to_bytes() that
will make sure a raw_value of type str uses struct.unpack to generate int's
to send to the _pack_byte() function, otherwise it crashes trying to create
ints from the chars in the str object.

This crash was found when loading exif data from a picture shot with a
Canon PowerShot SX50 HS (according to the exif data), and it's Gps/VersionID
value was <IP_ADDRESS> but at run time was loaded as '\x02\x03\x00\x00'.
This probably needs an equivalent fix for Python 3.
I haven't added a test as I'm not sure if this is conceptually the right fix, as it could be a problem with all sorts of fields. I see you haven't addressed #67, so maybe this isn't something you want the library to deal with? Seems like there's way too many interpretations of the exif spec so I understand this is a tough problem.
My use case for using this library was to auto-rotate images using Pillow based on their exif orientiation value, update the exif data's orientation flag, and then save the updated image without losing it's exif data. Right now I'll have to throw away the exif data if there's a problem creating the new exif bytes - it would be nice if it was more reliable to load/save the exif.
What are you thoughts?

Coverage decreased (-0.06%) to 94.832% when pulling 9acce90340d3ae2082c10abd8b5a4d404ab53a43 on wynnw:fix/exif-dump-gps-version into 48ced13646e8e85cc0bf30be5874d644c28ccdd4 on hMatoba:master.


Can't install

$ npm install arpjs -g

><EMAIL_ADDRESS>preinstall C:\Users\inf3rno\AppData\Roaming\npm\node_modules\arpjs\node_modules\typechecker
> node ./cyclic.js

><EMAIL_ADDRESS>install C:\Users\inf3rno\AppData\Roaming\npm\node_modules\arpjs\node_modules\pcap
> node-gyp rebuild

C:\Users\inf3rno\AppData\Roaming\npm\node_modules\arpjs\node_modules\pcap>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  pcap_binding.cc
  pcap_session.cc
  win_delay_load_hook.cc
..\pcap_binding.cc(2): fatal error C1083: Cannot open include file: 'pcap/pcap.h': No such file or directory [C:\Users\inf3rno\AppData\Roaming\npm\node_modules\arpjs\node_modules\pcap\build\pcap_binding.vcxproj]
..\pcap_session.cc(2): fatal error C1083: Cannot open include file: 'pcap/pcap.h': No such file or directory [C:\Users\inf3rno\AppData\Roaming\npm\node_modules\arpjs\node_modules\pcap\build\pcap_binding.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:258:23)
gyp ERR! stack     at emitTwo (events.js:125:13)
gyp ERR! stack     at ChildProcess.emit (events.js:213:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:197:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\inf3rno\AppData\Roaming\npm\node_modules\arpjs\node_modules\pcap
gyp ERR! node -v v8.1.2
gyp ERR! node-gyp -v v3.6.2
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\inf3rno\AppData\Roaming\npm-cache\_logs\2017-06-20T16_02_40_905Z-debug.log

Ohh I see this is a pcap error.

The pcap does not seem to be maintained any longer. https://github.com/node-pcap/node_pcap

Have you read our README first?
First of all arpjs has never been tested on Windows.
I'm not sure the issue is strictly related to node_pcap.
Do you have libpcap for windows installed?

I installed this: https://www.winpcap.org/ . Is there a way to test somehow from CLI (git bash) whether this is really working?


fix: add unique rule to email of auth migration

Proposed changes
Default auth migration was updated. I have added .unique() to email. It was allowed to add multiple records with the same email.
Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

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

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added necessary documentation (if appropriate)
[x] I have read the CONTRIBUTING doc

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

Thanks. A helpful change 👍


Add missing globalize/mobility migrations

TODO

Check out this project: https://github.com/7AXEL/Web2APK


RFW Wasm web example

https://github.com/flutter/packages/tree/main/packages/rfw/example/wasm should probably have a web directory at this point, since I think it's possible now?

@xster is this something you're still working on?


Always use SSD device class for internal clusters

If cluster is not external, then always use SSD as the device class for OSDs
Rook does not update the device classes on a existing cluster. This change will only reflect in the new clusters.
EPIC - https://issues.redhat.com/browse/RHSTOR-4326
Testing
OCS operator is passing the correct annotations VolumeClaimTemplates:
- oc get cephclusters.ceph.rook.io -o yaml

 volumeClaimTemplates:
        - metadata:
            annotations:
              crushDeviceClass: ssd
          spec:
            accessModes:
            - ReadWriteOnce
            resources:
              requests:
                storage: "1"
            storageClassName: sp-test
            volumeMode: Block

sh-4.4$ exit
exit
❯ oc rsh -n openshift-storage $(oc get pods -o wide -n openshift-storage|grep rook-ceph-operator|awk '{print$1}') ceph --conf=/var/lib/rook/openshift-storage/openshift-storage.config  status
  cluster:
    id:     be1781b1-e9c7-4835-a55e-b437d8f53791
    health: HEALTH_OK

  services:
    mon: 3 daemons, quorum a,b,c (age 18m)
    mgr: a(active, since 17m)
    mds: 1/1 daemons up, 1 hot standby
    osd: 3 osds: 3 up (since 17m), 3 in (since 18m)
    rgw: 1 daemon active (1 hosts, 1 zones)

  data:
    volumes: 1/1 healthy
    pools:   12 pools, 353 pgs
    objects: 337 objects, 131 MiB
    usage:   347 MiB used, 300 GiB / 300 GiB avail
    pgs:     353 active+clean

  io:
    client:   1.6 KiB/s rd, 5.0 KiB/s wr, 2 op/s rd, 0 op/s wr

❯ oc rsh -n openshift-storage $(oc get pods -o wide -n openshift-storage|grep rook-ceph-operator|awk '{print$1}') ceph --conf=/var/lib/rook/openshift-storage/openshift-storage.config  osd tree
ID  CLASS  WEIGHT   TYPE NAME           STATUS  REWEIGHT  PRI-AFF
-1         0.29306  root default
-7         0.09769      host compute-0
 2    ssd  0.09769          osd.2           up   1.00000  1.00000
-3         0.09769      host compute-1
 0    ssd  0.09769          osd.0           up   1.00000  1.00000
-5         0.09769      host compute-2
 1    ssd  0.09769          osd.1           up   1.00000  1.00000

Changes look good to me, But can you please add some commit message too.

@sp98 this is going to be stale soon


IoT: parent ticket

We've had a request for adding IoT bits to Rusoto.  This would handle all the AWS side communication: setting up Things, etc...
The API has a boto core definition: https://github.com/boto/botocore/blob/develop/botocore/data/iot/2015-05-28/service-2.json .

Punting on this for a while.  Hopefully it'll get caught when we have our codegen whipped into shape.

Is there an issue tracking what codegen changes would need to be completed for this to be reopened?

It's entirely possible that this just works with existing codegen, and it just hasn't been tried yet.  The IOT API is rest-json protocol, and we have codegen for that.
I just got one of these https://www.amazon.com/gp/product/B01C7WE5WM/ref=od_aui_detailpages00?ie=UTF8&psc=1 in the mail last week, and finally got it set up last night, so getting IOT working is actually on my mind.  I'll take a stab at getting it working today and report back.

@groteworld - got IoT working with just a couple minor tweaks.  There's a PR in for it - #345 but you can just check out the feature_iot branch if you want to start using it now.


release/1.8.0

1.8.0 (2021-02-01)
Added

fixed sync command: blacklisted files now fully working
updated sync code to the latest version and added logging
added a output-directory parameter option to create command, allowing users to specifify the
directory, where the project should be created
added a user information before the user is prompted to create a GitHub repo with mlf-core
added flake8 linting for each create template workflow
GitHub workflow badges in README now link to the corresponding workflow
[ALL TEMPLATES] added vscode files to .gitignore for templates
[ALL TEMPLATES] now feature a mlf-core lint workflow with colored linting result output
[ALL TEMPLATES] renamed train_cpu workflows to use project_slug (was project_slug_no_hyphen)
[MLFLOW TEMPLATES] refactored the common files for all mlflow templates into a common files directory
config default values are now preconfigured values (if any)
added logging to all commands mlf-core offers
refactored sync, bump-version and create code (added type hints, fixed some variable scoping)
[ALL TEMPLATES] replaced click with argparse
[ALL TEMPLATES] renamed some parameters to harmonize between templates
[PyTorch Template] New template with autologging via pytorch-lightning and mlflow 1.13.1

Fixed

fixed publish_docs WF for all templates working on main or master branch

fixed gh_pages setup for default branch main

fixed a bug causing the check upgrade version function to fail if local version is a SNAPSHOT version

Dependencies

LGTM after the small fixes


Seg fault

@MikeMcQuaid
Ad #1626
First of all, if I insulted you or people behind this great (still won't change opinion on that) extension, please accept my apologies. I consider words meaningless, so any time (but soon to be sure I will be still in that city) you will be in Warsaw let me know and I will buy you a beer (or lemonade if you avoid alcohol). Also could send you a bottle (give details where to ship on priv).
Secondly, the message you quoted existed only for 10s. I didn't want to post it in the first place, just typed it to let off steam. Unfortunately, I use Wasavi Chrome addon, which is great, but this time instead of the new line (not accustomed that in issue message one can just press 'enter' for that') I 'summoned' (wrong shortcut) it and posted a message.
Maybe I wasn't clear and forgot to mention it - every brew command gives me that result. I assumed, that it would be obvious that I followed these steps, if I hadn't posted things like "my X-code is up to date".

First of all, if I insulted you or people behind this great (still won't change opinion on that) extension, please accept my apologies.

Your apologies are very much accepted and genuinely appreciated.

Secondly, the message you quoted existed only for 10s.

Sorry about that, I didn't realise you had deleted it for that reason.
Let's continue the issue discussion in #1626, I've reopened it.


SSL Error: The certificate for https://packages.microsoft.com is expired.

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command

Describe the bug

To Reproduce

Expected behavior

Environment summary

Additional context

Using any packages on  https://packages.microsoft.com/  generates a SSL error.

Thank you for opening this issue, we will look into it.

The certificate for https://packages.microsoft.com is expired.
packet@ip-10-255-254-4:~/tmp$ get-cert.sh packages.microsoft.com
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
33:00:38:cd:96:ef:e8:07:13:f5:d9:78:97:00:00:00:38:cd:96
Signature Algorithm: sha384WithRSAEncryption
Issuer: C = US, O = Microsoft Corporation, CN = Microsoft Azure TLS Issuing CA 05
Validity
Not Before: Apr 23 18:00:41 2022 GMT
Not After : Apr 18 18:00:41 2023 GMT
Subject: C = US, ST = WA, L = Redmond, O = Microsoft Corporation, CN = packages.microsoft.com
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:b8:ce:cd:ad:37:98:ea:6c:0b:f0:37:1f:01:04:
82:f5:a7:5a:4a:8a:a2:b9:dc:da:33:8b:ca:37:ac:
10:1e:51:4b:a2:54:51:80:a9:7b:a7:6c:ec:f9:1f:
41:ca:71:ec:b5:f4:c8:5a:65:6d:01:8f:e1:59:35:
23:ee:23:6b:d2:1e:36:bf:d5:51:c1:b5:b7:55:55:
2f:96:84:b5:85:eb:76:93:e1:b8:9d:a0:a8:a0:c9:
e5:6a:4b:b8:75:1b:65:7d:f2:5e:ec:21:1f:82:ac:
d3:63:bd:86:d2:24:3b:0b:fd:88:a4:fd:a9:fc:49:
d5:21:b4:a8:bd:4f:5e:65:c7:37:55:8f:3c:63:3d:
6a:00:15:47:f5:1a:2f:6b:64:4b:b1:58:7d:e3:50:
e1:15:54:6a:3c:69:0f:79:24:47:1b:20:17:b0:37:
8c:10:6e:18:1e:92:4a:8e:18:1b:5d:8c:3e:7b:21:
65:c8:22:ca:57:83:cb:4f:a7:40:f2:64:7a:77:75:
6f:5e:ea:9d:7c:aa:be:94:26:96:45:41:3a:e7:82:
a5:74:b6:db:e3:25:05:09:87:f7:32:1b:4c:2f:69:
54:da:7b:c0:b8:8f:61:a2:31:4c:de:c7:4a:97:51:
29:dc:67:0b:26:f7:e8:21:2f:23:78:e3:9c:8c:2f:
ce:cd
Exponent: 65537 (0x10001)
X509v3 extensions:
CT Precertificate SCTs:
Signed Certificate Timestamp:
Version   : v1 (0x0)
Log ID    : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
Timestamp : Apr 23 18:10:42.976 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:77:D2:92:B3:4F:06:62:9C:3A:8D:FF:81:
BB:54:78:4B:5B:E0:44:CD:8F:7D:C7:47:4F:87:58:3B:
BB:EB:0D:50:02:20:0B:EC:8E:5F:7E:B0:4C:36:6E:E0:
F6:4A:AC:1E:F3:84:62:26:81:79:27:E8:4F:2F:33:B2:
84:D1:BA:22:89:46
Signed Certificate Timestamp:
Version   : v1 (0x0)
Log ID    : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
Timestamp : Apr 23 18:10:42.685 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:45:62:29:76:D7:E3:10:D4:EA:87:14:A2:
9E:1E:C4:7F:1E:1F:49:94:0F:DC:B0:C6:4F:F7:2C:1B:
75:F3:D4:E7:02:20:5B:7D:7B:35:01:E2:4D:9C:57:D4:
7F:2E:0D:93:F3:19:4A:F5:21:D1:B9:78:D9:A7:32:ED:
92:46:D1:6B:3F:17
Signed Certificate Timestamp:
Version   : v1 (0x0)
Log ID    : B3:73:77:07:E1:84:50:F8:63:86:D6:05:A9:DC:11:09:
4A:79:2D:B1:67:0C:0B:87:DC:F0:03:0E:79:36:A5:9A
Timestamp : Apr 23 18:10:42.971 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:49:0C:5E:6E:F9:0F:7F:45:B1:3F:F6:62:
55:3D:64:BE:69:FF:72:D2:FF:24:2E:73:48:44:65:C4:
24:2F:D3:D0:02:21:00:98:5D:19:1D:6F:DC:C6:D4:51:
93:21:81:1E:2A:60:72:F4:02:86:24:A0:3B:AB:8F:6A:
D1:22:74:13:EE:CB:E4
<IP_ADDRESS>.4.1.311.21.10:
0.0
..+.......0
..+.......
<IP_ADDRESS>.4.1.311.21.7:
0-.%+.....7.........F...........]...i...>..d..%
Authority Information Access:
CA Issuers - URI:http://www.microsoft.com/pkiops/certs/Microsoft Azure TLS Issuing CA 05 - xsign.crt
OCSP - URI:http://oneocsp.microsoft.com/ocsp
X509v3 Subject Key Identifier:
AD:3B:CD:EC:93:BD:6C:0D:41:D6:CB:DD:B2:E0:99:0E:B4:E8:B6:AA
X509v3 Key Usage: critical
Digital Signature, Key Encipherment, Data Encipherment
X509v3 Subject Alternative Name:
DNS:packages.microsoft.com, DNS:apt-mo.trafficmanager.net
X509v3 Basic Constraints: critical
CA:FALSE
X509v3 CRL Distribution Points:
Full Name:
URI:http://www.microsoft.com/pkiops/crl/Microsoft Azure TLS Issuing CA 05.crl
X509v3 Certificate Policies:
Policy: <IP_ADDRESS>.4.1.311.76.509.1.1
CPS: http://www.microsoft.com/pkiops/Docs/Repository.htm
Policy: <IP_ADDRESS>.2.2
X509v3 Authority Key Identifier:
C7:B2:9C:7F:1C:E3:B8:5A:EF:E9:68:1A:A8:5D:94:C1:26:52:6A:68
X509v3 Extended Key Usage:
TLS Web Client Authentication, TLS Web Server Authentication
Signature Algorithm: sha384WithRSAEncryption
Signature Value:
8a:77:7b:ef:29:83:30:b6:1e:da:01:0a:ef:24:1c:7a:06:52:
95:bb:e7:6c:89:fc:d9:e4:99:f8:e6:f5:34:56:41:8b:bb:89:
46:52:d6:2d:9d:0e:e8:38:d9:20:4e:0e:67:c6:47:d5:12:c6:
a2:c4:45:b5:34:5b:c5:20:2d:e9:4b:9f:b6:0b:f8:3d:73:39:
5d:f2:41:d8:f0:69:00:94:03:4a:05:8a:e5:0e:73:d2:a4:84:
4a:eb:cd:e6:0a:1d:0b:0a:05:bf:e7:b9:f0:94:8e:c2:9f:f7:
a8:9d:ad:3c:d5:69:25:34:72:8b:76:96:34:35:74:fc:67:f4:
b4:32:96:0a:d9:aa:8b:60:4d:1d:fb:02:b5:9c:f0:3b:88:0d:
8b:e5:c7:4f:87:4b:c7:10:19:8d:6b:78:02:16:3e:bf:d3:b4:
f4:20:4a:3d:37:2b:89:38:e1:4a:d3:e5:73:6a:0e:04:76:e2:
b5:c1:71:72:d2:7f:d0:e0:4d:96:ba:6a:0c:2d:c3:42:31:75:
9c:6a:7b:c7:ea:55:e5:11:f7:c0:e0:83:a9:25:56:7f:a8:3b:
f6:b3:4b:12:68:10:3e:53:8b:81:a2:91:49:f4:c2:c6:c4:2e:
37:46:cf:f1:1a:2f:82:76:e3:2d:66:06:7a:0f:45:f1:6e:1a:
42:64:3e:02:95:5c:35:9e:21:a6:4f:72:48:87:f9:8e:fe:57:
0e:7a:bd:0e:64:24:f2:21:d5:60:13:18:ff:a7:67:dc:86:eb:
6e:56:5e:37:cf:99:46:0d:0d:0c:f6:82:06:c7:28:35:26:94:
4b:8d:1d:34:55:54:0f:ce:05:6c:9a:b4:9b:e7:10:b6:8c:d0:
b3:3f:67:44:17:fd:41:9a:34:43:f1:ff:64:46:eb:71:d2:80:
08:57:f1:cd:23:93:71:84:cb:eb:7c:55:99:47:7c:4c:81:01:
35:c6:8b:af:49:51:d4:6f:60:7e:4a:8c:38:ac:33:93:15:98:
a2:50:4b:47:aa:2e:d1:02:2a:bd:21:d9:06:0d:a6:12:51:ed:
b2:12:33:77:73:5a:43:ab:f3:7f:c0:0e:05:4d:6d:e1:f2:5d:
8a:7f:24:f3:4b:e1:00:e2:5a:f2:d3:52:1d:08:f4:82:27:3d:
0a:c8:b5:1f:0c:0f:c4:15:39:10:3a:98:04:6f:a1:4d:7e:be:
03:57:fa:35:4a:58:d1:9c:dd:80:8b:4e:01:67:c8:eb:62:67:
e5:65:52:33:bf:a0:91:f9:af:b8:dd:ae:30:cc:07:5b:5f:f3:
aa:db:a4:54:77:30:d2:a4:2e:b8:b4:6c:ff:50:e4:48:17:36:
d5:cf:88:45:b1:7a:53:98
issuer=C = US, O = Microsoft Corporation, CN = Microsoft Azure TLS Issuing CA 05
CN=packages.microsoft.com
packet@ip-10-255-254-4:~/tmp$

A new cert has been deployed to all mirrors of https://packages.microsoft.com/ on 2023-04-18 18:42:00 UTC. This issue has now been fixed. Please retry the operation and let us know if it works as expected.

Thanks, that fixed it.

I am having this issue, testing by running
curl -i https://packages.microsoft.com

command works after more than 2 retry but often failed with SSL_ERROR_SYSCALL


Problem adding Raspi Alexa device to MRM group

Hi there!
I have issues with my newly created Alexa device running on a Rasberry 3 B+ (Stretch)
After everything had been set up like described at https://developer.amazon.com, I tried to connect the new device to my MRM group via the IOS Alexa app.
Unfortunately it tells me that the Alexa device on the Raspi needs a firmware update.
Briefly summarize your issue:
Cannot add Alexa on raspberry to Multiroom Music group due to "firmware update needed"
What is the expected behavior?
Adding MRM should be possible
What behavior are you observing?
If I want to add the Alexa device i just created on my raspberry via the IOS Alexa app to my MRM group, but if i try then the IOS app reports "firmware update needed".
Provide the steps to reproduce the issue, if applicable:
-Installed and set up everything like described at https://developer.amazon.com/
Tell us about your environment:
-Rasberry 3 B+
-Raspbian stretch with up to date packages
What version of the AVS Device SDK are you using?
  not sure, did it with the actual available version

Tell us what hardware you're using:

[ ] Desktop / Laptop
[X] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[X] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Hello @leramleram,
MRM is an optional feature that requires additional software.  You will need to work through your Amazon business contact to get access to the additional software required.
Best regards,
-SWH


[ISSUE-702] Bump sidecars versions

Purpose
Resolves #702

csi-provisioner 3.0.0 -> 3.1.0
csi-node-driver-registrar 1.3.0 -> 2.5.0
csi-resizer 1.1.0 -> 1.4.0
livenessprobe 2.1.0 -> 2.6.0

PR checklist

[x] Add link to the issue
[x] Choose Project
[x] Choose PR label
[ ] New unit tests added
[ ] Modified code has meaningful comments
[ ] All TODOs are linked with the issues
[ ] All comments are resolved

Testing
Provide test details

/ci
operator_branch=feature-bump-sidecar-versions


I broke PEX on my server.

No joke, I joined my server and the PermissionsEx plugin was broken, when I did /plugins it was in red, which obviously means it's disabled, and I have no clue why.
My log file: http://pastebin.com/jsypRUfU
Thanks,
Fightface.
EDIT: I know why it's being disabled, but I never even touched my Permissions file or messed with it the day it broke, and it was woring fine before.
Permissions File: http://pastebin.com/TRLGDA1r

PEX 1.20.4 is for your 1.6.4 server.  Start by downloading that here.

This didn't work, I followed everything you said.

Post pastebin links to the new startup console log and your permissions.yml file.

Permissions: http://pastebin.com/aiQPLNxK
Logs: http://pastebin.com/WpgKARH4

Pastebin link for your PermissionsEx\config.yml too please.

Delete line 208 from your permissions.yml file.

Config: http://pastebin.com/2Bfb5rgm

Corrected permissions.yml file: http://pastebin.com/zib7Y1jC
Replace your file with the download (don't just copy and paste) of that link.

Thank you a lot for helping me out with this, it's working fully now.

Excellent.  :)  You're welcome.

Now whenever I add a permission, it breaks, do you know why?

Considering you haven't given me anything to work with about why-- no.

I just would add a single permission and the permissions would break.
"Broken" permissions file: http://pastebin.com/XypMuem3

Correct the spacing on all of your group's prefixes.
Also, remove all of the lines with &f:

Your file should follow this example.


Add support and tests for individual AOAI keys

Fixes #32
@jjczopek, take a look at this PR, please. When I remove the identity and use real API keys for each of my backends, I can see successful requests. I also see failing requests for incorrect keys. Would love to know what your experience is, please.
@pamelafox, while I don't love adding individual API key support and much prefer managed identities instead, I realize the use case. I'm very interested in your thoughts.

The PR also externalizes test harness configuration into a new config.py.

Outstanding item is to update the Package Readme.
This is a non-breaking feature addition. The package version will move from 1.0.9 to 1.1.0.

@simonkurtz-MSFT I think it's fine for packages to support multiple forms of credentials. We avoid keys in our azd template samples since we provide the full infrastructure to create the RBAC roles, but I know devs sometimes use keys in other codebases.


LogicAppConnectionAuth is not actually an automation solution

At the bottom of this page, there is a section claiming:
"For automated deployments, you can use a script that provides consent for each OAuth connection. Here's an example script in GitHub in the LogicAppConnectionAuth project."
This is incorrect. That script relies on opening a window for a user to login. It cannot be run without user interaction therefor to suggest it can be used for automated deployments is false.
As an additional nail in the coffin, the script implements Login-AzureRmAccount which, when run from a pipeline will fail with the error Login-AzureRmAccount : The handle is invalid
Finally, the script has not been maintained in 4 years.
This documentation should stop linking to a 4-year-old script that doesn't do as claimed.

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

ID: 10846a19-893f-4d39-326d-66a7e4e1983c
Version Independent ID: d9888016-e329-ba76-ab3d-12e0c84863e4
Content: Deploy logic app templates - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-deploy-azure-resource-manager-templates.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

@iBrooks, Thank you for your feedback! We will review and update as appropriate.

@iBrooks While this approach is not like other traditional automations, I believe the script would still work if a CI worker runs in user space on a VM which has a browser session with logins made and consents provided, making it work without user interaction but might not be guaranteed to work with systems implementing 2FA.
The best approach would be to share API Connection resources which are pre-authorized, especially for connections requiring a login.
It would be best to state these prerequisites and limitations in the doc, so we are assigning this issue to the content author for further review and to update accordingly.

Draft update is pending review and elaboration by @PramodValavala-MSFT.

Here's the revised version for this section that we'll publish live later today:
Authorize OAuth connections
After deployment, your logic app works end-to-end with valid parameters. However, you still have to authorize or use preauthorized OAuth connections to generate valid access tokens for authenticating your credentials. Here are a few suggestions:

Preauthorize and share API connection resources across logic apps that are in the same region. API connections exist as Azure resources independently from logic apps. While logic apps have dependencies on API connection resources, API connection resources don't have dependencies on logic apps and remain after you delete the dependent logic apps. Also, logic apps can use API connections that exist in other resource groups. However, the Logic App Designer supports creating API connections only in the same resource group as your logic apps.
Note
If you're considering sharing API connections, make sure that your solution can handle potential throttling problems. Throttling happens at the connection level, so reusing the same connection across multiple logic apps might increase the potential for throttling problems.

Unless your scenario involves services and systems that require multi-factor authentication, you can use a PowerShell script to provide consent for each OAuth connection by running a continuous integration worker as a normal user account on a virtual machine that has active browser sessions with the authorizations and consent already provided. For example, you can repurpose the sample script provided by the LogicAppConnectionAuth project in the Logic Apps samples repo in GitHub.

Manually authorize OAuth connections by opening your logic app in Logic App Designer, either in the Azure portal or in Visual Studio.

If you use an Azure Active Directory (Azure AD) service principal instead to authorize connections, learn how to specify service principal parameters in your logic app template.


getting 404 error after changing assetsPublic path to '/manage/' instead of '/'

i am building my first project using vue-cli and webpack template, i am using nginx reverse proxy to serve it on 8090/manage, and the cli is running on 4500.
i supposed that editing  assetsPublicPath in config/index.js to be like this:
dev: {
        env: require('./dev.env'),
        port: 4500,
        autoOpenBrowser: false,
        assetsSubDirectory: 'static',
        assetsPublicPath: '/manage/',
        proxyTable: {},
        // CSS Sourcemaps off by default because relative paths are "buggy"
        // with this option, according to the CSS-Loader README
       // (https://github.com/webpack/css-loader#sourcemaps)
       // In our experience, they generally work as expected,
       // just be aware of this issue when enabling this option.
       cssSourceMap: false
 }

but it gives an errors of 404 and "Cannot GET /manage"
i even tried change other values in build/dev-server.js but nothing seemed to work. any clues ?

Since this is already being discussed on the forum, I will close this:
https://forum.vuejs.org/t/using-vue-cli-webpack-template-how-to-change-publicpath-correctly/10485


fix: Update expected empty data error

A change in ec-policy modified the rule that matches the case where test
data is not available:
https://github.com/hacbs-contract/ec-policies/pull/38

/retest
It seems to be an unrelated failure.

/lgtm


Add metrics endpoint to maya api service

Currently maya-api server does not have any monitoring feature so that we can be aware of what is happening in the background.So Prometheus will be used to scrap the metrics.

Merged #106