Implementation of String.prototype.padStart/padEnd.

Implementation of String.prototype.padStart/padEnd.
Proposal for this ES7 feature is found at https://github.com/tc39/proposal-string-pad-start-end.
As the name suggests padStart will add padding to retrieve string up to max length by adding when needed on the front side. The padEnd will add at the rear side.
This feature is sitting behind ES7Builtins flag.
Added tests.

Hi @akroshg, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Akrosh Gandhi). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

This was reviewed and signed off earlier - but did not get pushed to master. Rebased commits and created new PR.
@abchatra could you review this? Thanks,

:+1:

(ﾉ◕ヮ◕)ﾉ*:・ﾟ✧ woot!
When will this be available in a shipping Edge browser? :-D

Changes that make it into our ChakraCore GitHub master branch have a short journey to Chakra.dll. Code flows daily from GitHub to the internal repository from which builds of Chakra.dll are produced and then it flows into Windows and Microsoft Edge. While code flows quickly on this first leg of the journey, code flow from our internal branch to a Windows flighting branch is subject to any number of delays. So it is difficult to predict when your change in our GitHub repo will make it into a particular Windows flight.
In my experience, it takes anywhere between 6 to 10 weeks for the changes to make it to windows technical preview.

Understood, thanks! Where's the best place to keep up with it? It would be amazing, for example, if Edge release announcements included a link to the SHA of ChakraCore that is included :-)

You can following the change log for the technical preview here https://dev.windows.com/en-us/microsoft-edge/platform/changelog/
Example


In upgraded setup,when the control node (that was added when in v2.0.0) is powered down , the control node continues to be in "active"  state and cluster gets stuck in "unavailable" state.

v2.0.0 rancher server upgraded to v2.0.1-rc5
Steps to reproduce the problem:
Fresh install of v2.0.0 rancher server.
Create a custom cluster with following node configuration:
1 control node (n1)
1 etcd node (n2)
1 worker node (n3)
Create few workloads.
Upgrade  rancher server to v2.0.1-rc5.
Add 3 more nodes:
1 control node(n4)
1 etcd node(n5)
1 worker node(n6)
Wait for cluster to get to active state.
Power down control node (n1) that was added to the cluster before the server was upgraded.
Control node continues to be in "active" state and does not get to "unavailable" state.
Cluster gets stuck in "unavialable" state forever with following error state:
This cluster is currently Unavailable; areas that interact directly with it will not be available until the API is ready.

Failed to communicate with API server: Get https://<ip>:6443/api/v1/componentstatuses: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

@galal-hussein @StrongMonkey I tested this use case again and I was not able to reproduce the issue where cluster gets to "Unavailable" state when control plane node was powered off.
I suspect that when I had tested this workflow , there was a etcd quorum  loss which would have been the reason for the cluster to get to "Unavailable" state.


Remove flaky test: testUpdateAndRemoveGauge

Remove flaky test introduced in #13679. This test was not testing as well of what we want to so removing for now.
We need more UTs for AbstractMetrics class and created an issue for the same: #13685.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 61.94%. Comparing base (59551e4) to head (89e1549).
Report is 798 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master   #13684      +/-   ##
============================================
+ Coverage     61.75%   61.94%   +0.19%
+ Complexity      207      198       -9
============================================
  Files          2436     2554     +118
  Lines        133233   140552    +7319
  Branches      20636    21866    +1230
============================================
+ Hits          82274    87065    +4791
- Misses        44911    46858    +1947
- Partials       6048     6629     +581

Flag
Coverage Δ

custom-integration1
<0.01% <ø> (-0.01%)
:arrow_down:

integration
<0.01% <ø> (-0.01%)
:arrow_down:

integration1
<0.01% <ø> (-0.01%)
:arrow_down:

integration2
0.00% <ø> (ø)

java-11
61.90% <ø> (+0.19%)
:arrow_up:

java-21
61.82% <ø> (+0.19%)
:arrow_up:

skip-bytebuffers-false
61.90% <ø> (+0.16%)
:arrow_up:

skip-bytebuffers-true
61.81% <ø> (+34.09%)
:arrow_up:

temurin
61.94% <ø> (+0.19%)
:arrow_up:

unittests
61.94% <ø> (+0.19%)
:arrow_up:

unittests1
46.43% <ø> (-0.46%)
:arrow_down:

unittests2
27.72% <ø> (-0.01%)
:arrow_down:

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

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


Add FAST blocks to e2e test

Checklist

[ #] You've tried latest version of SushiChain
[ #] You've confirmed there is not a same sugestion

Description
The e2e test isn't testing the FAST block feature

This involves adding the developer fund to the nodes started by e2e.. which surfaced a bug related to the transactions in the genesis block.

done


fix: no panic on missing defaultTerminalCmd

Fixes #6828
I also added a test to make sure this issue doesn't happen anymore

Before merging could you add a release note?


No module named 'bit_config'

Hi,
I try to run quant_train.py, but meet the error as below, how to solve it ?
Traceback (most recent call last):
File "quant_train.py", line 22, in
from bit_config import *
ModuleNotFoundError: No module named 'bit_config'
Thx,
Lei

Hi Lei, thanks for pointing this out. I think this issue was solved by some recent commits.
Specifically, we moved the bit_config.py into the tvm_benchmark folder and imported the module from there.
Feel free to reach out if this doesn't work.

To follow up, I submit a new commit moving bit_config.py out of the tvm_benchmark folder, I think this could make the codes more straight-forward.

great! it works!


Rename " Electrical capacity [kW]" to " Output capacity [kW]"

Electrical capacity doesn't make sense for gas technologies. Moreover the output capacity is what's more intuitive
Also for the sake of lines: https://github.com/quintel/etmoses/blob/master/app/assets/javascripts/les/profile_select_box.js#L38-L40

Moreover the output capacity is what's more intuitive

I think it's the other way around: the electricity or gas capacity is an input capacity. The output capacity is what we currently simply call capacity: that is the input/electrical/gas capacity multiplied by the performance_coefficient.
I think to avoid confusion we could call it carrier_capacity. There is a new carrier attribute which defines the type of energy used by the technology (electricity or gas), so I think this would fit quite nicely.


Employee experience

added html component for Employee Experience

In the file path: src/pages/profile/ApplicantProfile.tsx, delete the commented line on line 4. Otherwise, all good.


bug: When using go to implementation it does not open new tab

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.9.1
Operating system/version
MacOS 13.4
Describe the bug
Instead it opens in the same window.
I cannot also move next/prev tab with S-h and S-l.
Is it expected behavior? Kinda confusing imo. :)
neovim from homebrew
Steps To Reproduce

Open some ts file.
Use <leader>gI to go to implementation.
It opens the file in the same window reusing tab.
S-h and S-l does not switch to prev/next tab.

Expected Behavior
New tab is opened instead of reusing window.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  "folke/LazyVim",
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

go to implementation does indeed not open in a new tab

I custom that keymap to open in a new tab
  {
    "neovim/nvim-lspconfig",
    init = function()
      local keys = require("lazyvim.plugins.lsp.keymaps").get()
      -- change keymaps
      keys[#keys+1] = {
        "gd",
        function()
          require("telescope.builtin").lsp_definitions({
            jump_type = "tab drop"
          })
        end,
        desc = "Goto Definition (new tab)",
        has = "definition",
      }
    end,
}


Time date sensor

This is a simple 'sensor' for displaying the current date/time in the frontend. Could be useful while running the frontend in fullscreen mode.

Coverage decreased (-0.61%) to 74.92% when pulling f72cedf4464c46fa07e5bbf223df2c4561622553 on fabaff:time-date into dfc50562a16243126effd2b6c97cbb3a536d2769 on balloob:dev.

Coverage increased (+0.01%) to 75.54% when pulling b55e8fc4c4c29250c8204a943f2c83a7dd2fb299 on fabaff:time-date into dfc50562a16243126effd2b6c97cbb3a536d2769 on balloob:dev.

Thank you very much for your comments.

Coverage increased (+0.01%) to 75.54% when pulling 9f042db0f5344b4e6af6b1dd2f888ce8909cbfe3 on fabaff:time-date into dfc50562a16243126effd2b6c97cbb3a536d2769 on balloob:dev.


Guide to setup R-Pi environment

Step-by-step installation guide
OS installation (Section Incomplete)

Use Bullseye.
Install VS code.
Install Anydesk.

VS code setup (Section Incomplete)

Install git and git tools.
Install remote explorer.
Setup git.

After completing writing this, update README.md accordingly.

We need a complete installation giude including how to install all necessary dependencies (e.g., pigpio, virtual environment, etc).

@gunturiCM has this issue been resolved?

@gunturiCM has this issue been resolved?
Not yet professor. I will write the full details after I am done with my report.

@jamie-54 we can close this, right?


Improved SIMD Adler32

I took a stab at cleaning up the Adler32 SIMD implementation and plugging up a few of the performance holes.  Since the current AVX2 version works in 64 byte chunks, the tail of scalar processed bytes can be excessive in some cases.  I've rewritten it to share the AVX2 and SSSE3 code paths so the SSSE3 code can work on the leftovers from the AVX2 loop, improving perf on any lengths not an even multiple of 64 bytes.
Here are some benchmark results showing where it's most improved:
BenchmarkDotNet=v0.12.1, OS=Windows 10.0.19042
Intel Core i7-6700K CPU 4.00GHz (Skylake), 1 CPU, 8 logical and 4 physical cores
.NET Core SDK=5.0.100-rc.2.20479.15
  [Host]     : .NET Core 3.1.9 (CoreCLR 4.700.20.47201, CoreFX 4.700.20.47203), X64 RyuJIT
  DefaultJob : .NET Core 3.1.9 (CoreCLR 4.700.20.47201, CoreFX 4.700.20.47203), X64 RyuJIT

|  Method | Count |       Mean |     Error |    StdDev | Ratio |
|-------- |------ |-----------:|----------:|----------:|------:|
|    Base |     8 |   7.127 ns | 0.0256 ns | 0.0239 ns |  1.00 |
|      PR |     8 |   5.385 ns | 0.0311 ns | 0.0276 ns |  0.76 |
|         |       |            |           |           |       |
|    Base |    15 |  10.993 ns | 0.0382 ns | 0.0357 ns |  1.00 |
|      PR |    15 |   7.580 ns | 0.0492 ns | 0.0460 ns |  0.69 |
|         |       |            |           |           |       |
|    Base |    16 |   7.246 ns | 0.0240 ns | 0.0201 ns |  1.00 |
|      PR |    16 |   7.464 ns | 0.0341 ns | 0.0302 ns |  1.03 |
|         |       |            |           |           |       |
|    Base |    24 |  10.598 ns | 0.0316 ns | 0.0295 ns |  1.00 |
|      PR |    24 |   9.468 ns | 0.0443 ns | 0.0414 ns |  0.89 |
|         |       |            |           |           |       |
|    Base |    31 |  14.579 ns | 0.0475 ns | 0.0444 ns |  1.00 |
|      PR |    31 |  11.695 ns | 0.0594 ns | 0.0496 ns |  0.80 |
|         |       |            |           |           |       |
|    Base |    32 |  11.873 ns | 0.0257 ns | 0.0228 ns |  1.00 |
|      PR |    32 |   7.976 ns | 0.0781 ns | 0.0731 ns |  0.67 |
|         |       |            |           |           |       |
|    Base |    48 |  17.575 ns | 0.0676 ns | 0.0600 ns |  1.00 |
|      PR |    48 |   9.041 ns | 0.1453 ns | 0.1359 ns |  0.51 |
|         |       |            |           |           |       |
|    Base |    64 |   8.551 ns | 0.0280 ns | 0.0262 ns |  1.00 |
|      PR |    64 |   8.531 ns | 0.0270 ns | 0.0246 ns |  1.00 |
|         |       |            |           |           |       |
|    Base |    80 |  13.780 ns | 0.0551 ns | 0.0515 ns |  1.00 |
|      PR |    80 |   9.518 ns | 0.0375 ns | 0.0313 ns |  0.69 |
|         |       |            |           |           |       |
|    Base |    96 |  22.112 ns | 0.0968 ns | 0.0858 ns |  1.00 |
|      PR |    96 |  10.294 ns | 0.0628 ns | 0.0587 ns |  0.47 |
|         |       |            |           |           |       |
|    Base |   112 |  31.873 ns | 0.1630 ns | 0.1525 ns |  1.00 |
|      PR |   112 |  10.937 ns | 0.0477 ns | 0.0446 ns |  0.34 |
|         |       |            |           |           |       |
|    Base |  1024 |  24.323 ns | 0.0920 ns | 0.0861 ns |  1.00 |
|      PR |  1024 |  24.192 ns | 0.1332 ns | 0.1180 ns |  0.99 |
|         |       |            |           |           |       |
|    Base |  5552 | 131.578 ns | 0.6836 ns | 0.6394 ns |  1.00 |
|      PR |  5552 |  99.908 ns | 0.3541 ns | 0.3139 ns |  0.76 |
|         |       |            |           |           |       |
|    Base |  8187 | 194.357 ns | 0.5619 ns | 0.4981 ns |  1.00 |
|      PR |  8187 | 152.631 ns | 0.5855 ns | 0.4889 ns |  0.79 |
|         |       |            |           |           |       |
|    Base | 32768 | 667.017 ns | 3.0423 ns | 2.8457 ns |  1.00 |
|      PR | 32768 | 638.717 ns | 3.5795 ns | 3.1732 ns |  0.96 |

COMPlus_EnableAVX=0 benchmark results
BenchmarkDotNet=v0.12.1, OS=Windows 10.0.19042
Intel Core i7-6700K CPU 4.00GHz (Skylake), 1 CPU, 8 logical and 4 physical cores
.NET Core SDK=5.0.100
  [Host]     : .NET Core 3.1.10 (CoreCLR 4.700.20.51601, CoreFX 4.700.20.51901), X64 RyuJIT
  DefaultJob : .NET Core 3.1.10 (CoreCLR 4.700.20.51601, CoreFX 4.700.20.51901), X64 RyuJIT

| Method | Count |         Mean |     Error |    StdDev | Ratio | RatioSD |
|------- |------ |-------------:|----------:|----------:|------:|--------:|
|   Base |     8 |     8.568 ns | 0.1980 ns | 0.4044 ns |  1.00 |    0.00 |
|     PR |     8 |     3.691 ns | 0.0186 ns | 0.0165 ns |  0.45 |    0.04 |
|        |       |              |           |           |       |         |
|   Base |    15 |    10.985 ns | 0.0305 ns | 0.0286 ns |  1.00 |    0.00 |
|     PR |    15 |     7.533 ns | 0.0286 ns | 0.0254 ns |  0.69 |    0.00 |
|        |       |              |           |           |       |         |
|   Base |    16 |     7.235 ns | 0.0207 ns | 0.0194 ns |  1.00 |    0.00 |
|     PR |    16 |     7.428 ns | 0.0284 ns | 0.0266 ns |  1.03 |    0.01 |
|        |       |              |           |           |       |         |
|   Base |    24 |    10.523 ns | 0.0353 ns | 0.0313 ns |  1.00 |    0.00 |
|     PR |    24 |     9.471 ns | 0.0891 ns | 0.0744 ns |  0.90 |    0.01 |
|        |       |              |           |           |       |         |
|   Base |    31 |    14.657 ns | 0.0769 ns | 0.0682 ns |  1.00 |    0.00 |
|     PR |    31 |    11.714 ns | 0.0474 ns | 0.0420 ns |  0.80 |    0.00 |
|        |       |              |           |           |       |         |
|   Base |    32 |    11.821 ns | 0.0297 ns | 0.0263 ns |  1.00 |    0.00 |
|     PR |    32 |     7.657 ns | 0.0432 ns | 0.0383 ns |  0.65 |    0.00 |
|        |       |              |           |           |       |         |
|   Base |    48 |    17.536 ns | 0.0589 ns | 0.0551 ns |  1.00 |    0.00 |
|     PR |    48 |     8.503 ns | 0.0303 ns | 0.0283 ns |  0.48 |    0.00 |
|        |       |              |           |           |       |         |
|   Base |    64 |     9.387 ns | 0.0769 ns | 0.0719 ns |  1.00 |    0.00 |
|     PR |    64 |     9.145 ns | 0.0451 ns | 0.0422 ns |  0.97 |    0.01 |
|        |       |              |           |           |       |         |
|   Base |    80 |    14.359 ns | 0.0645 ns | 0.0604 ns |  1.00 |    0.00 |
|     PR |    80 |     9.707 ns | 0.0465 ns | 0.0435 ns |  0.68 |    0.00 |
|        |       |              |           |           |       |         |
|   Base |    96 |    11.482 ns | 0.2477 ns | 0.2853 ns |  1.00 |    0.00 |
|     PR |    96 |    10.188 ns | 0.0623 ns | 0.0583 ns |  0.89 |    0.03 |
|        |       |              |           |           |       |         |
|   Base |   112 |    15.146 ns | 0.0660 ns | 0.0617 ns |  1.00 |    0.00 |
|     PR |   112 |    10.839 ns | 0.0324 ns | 0.0287 ns |  0.72 |    0.00 |
|        |       |              |           |           |       |         |
|   Base |  1024 |    45.580 ns | 0.1230 ns | 0.1091 ns |  1.00 |    0.00 |
|     PR |  1024 |    43.515 ns | 0.1820 ns | 0.1702 ns |  0.95 |    0.00 |
|        |       |              |           |           |       |         |
|   Base |  5552 |   222.906 ns | 4.4200 ns | 4.3410 ns |  1.00 |    0.00 |
|     PR |  5552 |   214.824 ns | 0.5211 ns | 0.4620 ns |  0.96 |    0.01 |
|        |       |              |           |           |       |         |
|   Base |  8187 |   324.293 ns | 1.0222 ns | 0.9062 ns |  1.00 |    0.00 |
|     PR |  8187 |   318.943 ns | 1.3859 ns | 1.2964 ns |  0.98 |    0.01 |
|        |       |              |           |           |       |         |
|   Base | 32768 | 1,319.630 ns | 5.3945 ns | 5.0460 ns |  1.00 |    0.00 |
|     PR | 32768 | 1,258.779 ns | 5.9641 ns | 4.9803 ns |  0.95 |    0.01 |

Notice the current implementation actually takes longer on a 112 byte input than it does on 1024 bytes, just because it ends up with 48 trailing bytes after processing 64 with AVX2.  The new version is able to completely vectorize the 112 byte case and makes the performance much more linear as input size grows.
The implementation is slightly simplified, making it easier to follow and saving a few cycles on larger inputs as well.  Hopefully the comments make sense.
I also added a small 4-bytes-at-time loop to the scalar implementation to better handle very small inputs.  I'm not sure how often those would come up in e.g. PNG, but it's a small amount of code and shows good improvements up to 32 bytes where the SIMD code kicks in.
Oh, and I switched over from pointers to managed refs, with no perf hit.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Moving this to WIP.  I thought of an even cheaper way to do it while out on a bike ride today 😄

@saucecontrol Sorry for never getting back to you on this. For some reason I have no notifications for it!!
That looks like great speedup. It's also very, very nice to have another pair of eyes on this code. It would be great to get something I can ship.

@saucecontrol Sorry for never getting back to you on this. For some reason I have no notifications for it!!
That looks like great speedup. It's also very, very nice to have another pair of eyes on this code. It would be great to get something I can ship.

Oh yeah, I forgot to update this.  I tried out my simpler implementation, but it ended up bottlenecking on the shuffle port on Intel Haswell thru Skylake, so it's a little slower there.  But it was 30-40% faster on AMD Zen2 with its dual shuffle ports (and presumably on Icelake although I don't have one to test on), so it'll worth using someday.  I'd go ahead and keep this version until those take over more market share.
I'll definitely circle back and look at this project more once I've cleared some other things from my queue.  Presently dealing with image metadata.  What a clustercuss that is 😝

Oh yeah, I forgot to update this.  I tried out my simpler implementation, but it ended up bottlenecking on the shuffle port on Intel Haswell thru Skylake, so it's a little slower there.  But it was 30-40% faster on AMD Zen2 with its dual shuffle ports (and presumably on Icelake although I don't have one to test on), so it'll worth using someday.  I'd go ahead and keep this version until those take over more market share.
I'll definitely circle back and look at this project more once I've cleared some other things from my queue.  Presently dealing with image metadata.  What a clustercuss that is 😝

Thanks. I'll get this merged then. Looks good to me and your comments are really useful!
Yeah image metadata hasn't been something I have enjoyed working with so far. Clustercuss is apt 😆

Thanks. I'll get this merged then. Looks good to me and your comments are really useful!
Yeah image metadata hasn't been something I have enjoyed working with so far. Clustercuss is apt 😆

May need to refactor this to allow pointers so I can read/write directly to from span in the stream.

Not sure I follow... the Span you pass into these methods can wrap either an unmanaged pointer or a managed ref.  But if you're talking about pinning in the outer loop and just passing raw pointers around from there, that'll be more efficient than wrapping and unwrapping Spans for every method call.

False alarm... Turns out I don't need to. I forgot the new Span<byte>(pointer, length) constructor!


Tests don't run on first install

Steps:

Clone project
npm install
npm test

Output:
running validate...passed!
running test...failed!
/Users/kyle/Projects/splora/app/js/Editor.js:11
const { EventEmitter } = require('events')
      ^

SyntaxError: Unexpected token {
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:374:25)
    at Object.Module._extensions..js (module.js:405:10)
    at Object.require.extensions.(anonymous function) (/Users/kyle/Projects/splora/node_modules/proxyquire/lib/proxyquire.js:259:43)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Proxyquire._require (/Users/kyle/Projects/splora/node_modules/proxyquire/lib/proxyquire.js:166:19)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/Users/kyle/Projects/splora/app/js/Page.js:12:16)
    at Module._compile (module.js:398:26)

hey @kylealwyn, I think the issue is actually an outdated node version. Which version are you using? "Destructuring" (which is what is breaking) became a feature in V6.

Agh, the pains of developing on two machines.


BACKLOG-22134: Update version and add missing Nexus env var

JIRA

https://jira.jahia.org/browse/BACKLOG-22134

the signature has not been triggered by JahiaReleaseTool so I think we're good

It was updated from recent change here https://github.com/Jahia/jcontent/pull/1208

I did it manually


sp-field-severity - Incorrect Colours - SharePoint List

sp-field-severity-severeWarning & sp-field-severity-blocked appear to be using the same colour.
Left, SharePoint List, Right, Microsoft Documentation:

Instant eyedropper shows the two colours as both being #FDE7E9.
severeWarning in the Microsoft Documentation shows as #FBD9CC and blocked shows as #FCAFD3
I am using Chromium Edge.
See post here: https://docs.microsoft.com/en-us/answers/questions/263642/column-formatting-not-working-correctly-sp-field-s.html?childToView=658271#answer-658271

I'm having trouble reproducing the issue. These values can change depending on the theme applied to the site as well. Do you have a custom theme applied to your environment?

Everything on the list shows as the default sharepoint teal, but the theme does show the 'current selection' as just being black with black letters on a white background. (System admins do have a custom black bar along the very top with the company logo).
Changing the look to any of the default sharepoint themes does change the colours for the buttons, border lines, etc. But the two fields still show as the same colour for all of them. The bar at the very top with the company logo does not change (which I believe it is not supposed to).
The logic is correct with the formatting, as changing '--severeWarning' to '--warning' results in the expected yellow. Same with changing '--blocked'
This is the same in Chrome, Edge, & Internet Explorer. They are also the same colour when viewing from the Lists app in Teams.
I am applying these fields through additionalRowClass, the logic determines which field severity to use and the other properties are added on. So below is exactly what should be sent for formatting after logic (for the cancelled row):
{
"$schema": https://developer.microsoft.com/json-schemas/sp/v2/row-formatting.schema.json,
"additionalRowClass": "sp-field-severity--severeWarning sp-field-fontSizeSmall sp-css-color-LightGrayFont ms-borderColor-themeDark"
}
Using only the above and removing the logic results in all rows being the '--blocked' colour, as expected.
I am formatting the entire row through the advanced designer in the "Format this view" option. I have not tested to see if the colours render differently when formatting only the column, I will have to try that on Monday.
Thank you,
Corey

From: Beau Cameron @.>
Sent: Friday, December 10, 2021 3:02:18 PM
To: SharePoint/sp-dev-docs @.>
Cc: CoreyHunsberger @.>; Author @.>
Subject: Re: [SharePoint/sp-dev-docs] sp-field-severity - Incorrect Colours - SharePoint List (Issue #7576)
I'm having trouble reproducing the issue. These values can/do change depending on the theme applied to the site as well. Do you have a custom theme applied to your environment?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/SharePoint/sp-dev-docs/issues/7576#issuecomment-991257349, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMQGGKA6NONBHTFEWBPAHNTUQJMEVANCNFSM5JXYMDXQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I have a local repro. Looking into this.

These colors should have two versions, one for the dark themes and one for the rest, but for both, "Blocked" and "Severe warning have different colors. Here they are for light themes in the Fluent design file. Both seem to be using the hex values for "Blocked" in the bug.

We have taken a fix to address this. Please do try it out @CoreyHunsberger .
Thanks @betrue-final-final for guidance. 🍻

@CoreyHunsberger I have resolved this issue. Please reopen if this still persists for you.


Stale SEO data

Currently if I search google for grommet accordion the first link is from the old docs.

I noticed the current site does not utilize any server side rendering or SEO friendliness. Seeing as the site does not require full featured async SSR as the data is static, is there any discussion to add a static site generator to the build like Gatsby?
At a minimum, the docs should be integrated with Google Webmaster to invalidate the old links and crawl the new ones.

@MikeWalrath looks like a good discussion topic

@karatechops really like this idea and I would like to hear more from your expertise on it, did you publish on this matter a blog on the hpe dev? it could be a great topic.
@MikeWalrath can follow up with you and Ian on how can attack this one.

@ShimiSun SSR gets very complicated quickly, it would be a long blog post however a multipart blog series may make sense. Something like SEO + React = ??? 😀
For this implementation, it wouldn't need to be a super fancy setup with traversing component trees. If we want to avoid base refactor we could get by with running a simple Express server to serve React's output as a string. As long as the site's pages aren't making additional async requests to APIs this could be pretty lean.

I assume this is being hosted on netlify, this is pretty interesting -> https://www.netlify.com/docs/prerendering/

link #140


Add hash field to QueryResponse proto object

What is this pull request?
Pull request adds hash field to QueryResponse proto object.
Why do you implement it? Why do we need this pull request?
According our model QueryResponse always contains a hash of a corresponding query but it was not reflected in proto scheme.
Details/Features

Add hash field in QueryResponse proto
Hash field is set in QueryService
Tests know about hash field and check it

P.S. (optional)
Since every QueryResponse hash should be the same as hash of corresponding query I decided not to create additional test for hash but add checks for every existing test similar to status call checking.

Codecov Report

Merging #728 into feature/shared_model will decrease coverage by <.01%.
The diff coverage is 17.64%.

@@                   Coverage Diff                    @@
##           feature/shared_model     #728      +/-   ##
========================================================
- Coverage                 43.04%   43.03%   -0.01%
========================================================
  Files                       327      327
  Lines                     12293    12293
  Branches                   6705     6707       +2
========================================================
- Hits                       5291     5290       -1
+ Misses                      883      882       -1
- Partials                   6119     6121       +2

Impacted Files
Coverage Δ

irohad/torii/impl/query_service.cpp
22.22% <16.66%> (-4.1%)
:arrow_down:

test/module/irohad/torii/torii_queries_test.cpp
10.45% <17.85%> (-0.04%)
:arrow_down:

shared_model/utils/variant_deserializer.hpp
37.5% <0%> (ø)
:arrow_up:

shared_model/interfaces/polymorphic_wrapper.hpp
72.72% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Write July newsletter

posts/2023-07-01-Newsletter-July2023.qmd
Is in draft mode, so not live.

I edited and added some bits to the end. The one part I didn't edit was the first section about the scope of new membership. @opetchey would you mind please writing that part if you don't mind? Else I can do it, too (but feel you'd do a more eloquent job on that one!)
Thanks, Sam

@SamRPJRoss Hi Sam, please take a look at the newsletter now (including close proof-read) and the other two revised pages in my latest commit.

Thanks Owen, I just made very minor edits following a close proof read of the newsletter and two pages (about and who-we-are). Thanks for your edits, this all looks great now and I'm happy for this to be the final version whenever you are.

OK, the newsletter and other updates are live. Will you send an email to the network with the newsletter?

Thanks Owen! I sent a link to the newsletter, and Shyamolina pointed out we misspelled her name (oops). I'm not now 100% sure where to fix it, so would you mind please just correcting the spelling of her name in the newsletter and pushing it straight to the live branch? Thanks so much (sorry I can't see where to do it!)

Should be done now or very soon.

Thanks Owen :)


The Select style are wrong inside Dialog

Don't know why, my website other where using Select have hover effecet
But place it inside Dailog, it was gone. No hover effect

Having the same issue @lucasjinreal , any luck on figuring it out?

✋🏽 Same problem here when using the select in a dialog

+1


Cant downloadFile

Hello!
Your work is brilliant, it helps fast to build Telegram app. Thank you.
I've encountered an issue. cant donwload file of avatar with id<PHONE_NUMBER>266659755. It's a user's avatar. I got it from profilePhoto's id. downloadFile is sent, but nothing happens after that. Using json lib in cpp.
{\"@type\":\"downloadFile\",\"file_id\":\"1812616928266659755\",\"priority\":12}
What is wrong?

"1812616928266659755" - isn't a correct file_id, file_id is always small integer number.

Yes, I should took id from small_ or big_ fields, thanks!


feat: Documents token intents

Description

Documents token intents

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.188.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


changed the font family #248

changed the font

I don't see any reason for this change, and it seems to decrease the number of fallback fonts in the stack. Furthermore, you edited the files in the dist folder, which is not how updates are tracked anymore.


Tableu Server client error : (401001: Signin Error ,Error signing in to Tableau Server)

Hi Everyone,
I am using Tableau Server client. I am trying to login to the server with the python tableau server client but I cannot get past the Log in. Here is what i am trying to run just to test access.
import tableauserverclient as TSC
server = TSC.Server("https :// tableaublahblah .com")
server.add_http_options({'verify': False})
tableau_auth = TSC.TableauAuth("MyUserID","MyPassword",)
server.auth.sign_in(tableau_auth)
with server.auth.sign_in(tableau_auth):
all_datasources, pagination_item = server.datasources.get()
print("\nThere are {} datasources on site: ".format(pagination_item.total_available))
print([datasource.name for datasource in all_datasources])
I am getting this error: 	401001: Signin Error
Error signing in to Tableau Server
I am using Tableau server 2019.3 and I am able to login to the server from web ui usinf the username and password.
Please suggest How can I fix this issue.

use http instead of https at TSC.Server()
it worked for my code

https://github.com/tableau/server-client-python/issues/325#issuecomment-462948146

It doesn't look like the same as issue 325 because that one covers a 405 error.
@imondal this is an older issue but are you still having problems? If the username/password are in fact working through the web UI to the same server, it's possible you don't have access to the default site and would need to include a sitename in  TSC.TableauAuth (docs).


Player not working Smoothly and hangs the screen

Hey there
Version of react-native-audio-recorder-player
2.5.0
Platforms you faced the error (IOS or Android or both?)
android and ios both
Expected behavior
an audio player should work smoothly.
Actual behavior
When  I click on the react-native-slider to pause it or I click on the button to pause it hangs the screen and I am not able to close it. While playing it does not want me to do anything.
steps to reprodudce
code used in the render() method
<View style={{flex:1,flexDirection:'row',bottom:hp('8%'),marginLeft:wp('5%'),marginRight:wp('60%')}}>
{(this.playerStatus=='playing') ?
<TouchableOpacity onPress={()=>{
if(this.playerStatus == "playing"){
this.playerStatus = "paused";
this.onPausePlay();
}
else{
this.onStopPlay()
}
}}>
<Icon name="pause" type={'font-awesome'} size={20} color={'#fff'}/>

:<TouchableOpacity onPress={()=>{this.onStartPlay()}}><Icon size={25} name="play" type={'font-awesome'} color={'#fff'}/>
}

<View style={{flex:1,flexDirection:'row',bottom:hp('13.8%')}}>
<Slider
style={{width: wp('100%'), height: 60}}
value={this.state.currentPositionSec}
minimumValue={0}
maximumValue={this.state.currentDurationSec}
onValueChange={(data) => {
console.log(this.playerStatus);
if(this.playerStatus == "playing"){
this.setState({isLoading:true});
console.log("in value change onPause play");
this.playerStatus = "paused";
this.onPausePlay();
}
                          }}
                          onSlidingComplete={async (data) =>

{
console.log(data);
console.log("set");
await audioRecorderPlayer.seekToPlayer(data/1000);
this.onStartPlay();
this.setState({isLoading:false});
}}
thumbTintColor={'transparent'}
minimumTrackTintColor="#39B2DB"
maximumTrackTintColor="#FFFFFF"
/>

Functions used for audio play
onStartPlay = async () => {
this.playerStatus = "playing";
const msg = await audioRecorderPlayer.startPlayer(this.state.audioPath);
//   const msg = await audioRecorderPlayer.startPlayer('https://www.soundhelix.com/examples/mp3/SoundHelix-Song-1.mp3');
audioRecorderPlayer.setVolume(1.0);
if(this.seekPosition && this.playerStatus == "paused"){
audioRecorderPlayer.seekToPlayer(this.seekPosition);
}
audioRecorderPlayer.addPlayBackListener((e) => {
this.seekPosition = e.current_position;
if (e.current_position === e.duration) {
this.setState({isLoading:false});
this.playerStatus = "stopped";
audioRecorderPlayer.stopPlayer();
}
this.setState({
currentPositionSec: e.current_position,
currentDurationSec: e.duration,
playTime: audioRecorderPlayer.mmssss(Math.floor(e.current_position)),
duration: audioRecorderPlayer.mmssss(Math.floor(e.duration)),
});
return;
});
}
  async onPausePlay(){
  this.playerStatus = "paused";
    await audioRecorderPlayer.pausePlayer();
  }
 async onStopPlay(){
    console.log('onStopPlay');
    this.playerStatus = "stopped";
    audioRecorderPlayer.stopPlayer();
    audioRecorderPlayer.removePlayBackListener();
  };

Any update on this?
Is it because of the listener is way too frequent?
Please help...

Did any one solve this issue

Did any one solve this issue? i am having same problem


tonic provides no way to disable server-only dependencies

If you pull in tonic 0.7 as a dependency, the transport feature (which is enabled by default) pulls in the axum dependency. It appears only servers need the axum dependency, so for downstream users who only need client code, this is unnecessary.

I finally tried using #960 and I don't think it's an adequate fix. First of all, the tls feature still pulls in transport, so by default if you pull in tls or one of the features that depend on it, you'll still get the server-side dependencies. That part can actually be worked around by depending on the other required features directly, but then I noticed that the entire tonic::transport module is unavailable if the transport feature is disabled, so I don't have access to things like Error, Channel or Endpoint from that module.
Should I submit a PR replacing the use of transport internally with channel?


Write test case for DiscreteArray operator=

Becomes obvious when running NLOC_MPCTest with single-precision or in debug mode.

Could not not confirm issue, created a test case in DiscreteArrayTest.cpp

Could not confirm the issue.


When adding a new metadata to a submission it should also be added to the submission's project.

Bug found in the UI where the supplementary link between metadata and project is not being added correctly when posting new metadata.
This previously worked but reveals the solution should really be in core rather than the UI:
when Posting to sue/id/biomaterials the biomaterial is created and added to the submission envelope, it should also be added to the project if the submission envelope has one.

PRs to be reviewed - @aaclan-ebi if you could take a look. it would be great

Merged to master with 752, deploy to ingest ui failed over the weekend but is being re-deployed now

Alexie will continue testing on this


When item was returned back to stash, it should appear at the end of the list

When item is picked up first time - it should always appear at the start of the list.

Pros/cons for adding items to beginning of item stash:

If there are many items and player needs to scroll to see the end, then item added to beginning will be more visible to player..

Adding an item to beginning shifts all other items. If player was about to click on an item, they may misclick due to this shift.
The shift looks weird visually.

The cons outweight the pros. Also, recently I increased the amount of visible items so the one pro is not as important as it used to be.


Added SharingOwnerRules and SharingCriteriaRules

Hi !
Thanks to help me improve it :)
Have you tested it ?

I honestly don't remember.

:D I close it so


[Question] Do I Need Separate Start, Stop, and Default States for Tracking Configs?

Hi,
I’m developing a walking app using react-background-geolocation and currently have three separate configurations that I apply depending on the user's activity state:

GEO_CONFIG: Applied when .ready is called, and it initialises the geolocation settings when the user opens the app.
GEO_CONFIG_START: Applied dynamically when the user starts walking (increased tracking frequency and persistence settings).
GEO_CONFIG_STOP: Applied when the user stops the walk (tracking is disabled to save battery and prevent unnecessary processing).

What I'm Trying to Achieve:

When the user is actively walking, I want to ensure the app tracks location accurately and reliably, even in the background.
When the walk ends, I want to stop tracking to conserve resources and avoid unnecessary background activity.
I’m also worried about the app being killed by the OS while the user is not walking, which is why I disable certain features in GEO_CONFIG_STOP.

My Questions:

Do I need three separate states (default, start, stop) for my use case, or can I just handle everything with one config that I tweak dynamically?
Am I over-optimising by completely disabling tracking in the STOP state to prevent the app from being killed by the OS? Is that step even necessary, or would keeping tracking on (in a lower accuracy mode) suffice to maintain app reliability?
Would maintaining just one state with some dynamic modifications be a better approach, or is there an optimal balance between these distinct configs?

What I Have Considered:
Using three distinct states:
export const GEO_CONFIG = {
  desiredAccuracy: BackgroundGeolocation.DESIRED_ACCURACY_NAVIGATION,
  locationAuthorizationRequest: 'WhenInUse',
  showsBackgroundLocationIndicator: true,
  notification: {
    title: 'Tracking walk',
    text: 'Tracking your walk...',
  },
  foregroundService: true,
  activityType: BackgroundGeolocation.ACTIVITY_TYPE_FITNESS,
};

export const GEO_CONFIG_START = {
  stopOnTerminate: false,
  startOnBoot: true,
  heartbeatInterval: 60,
  preventSuspend: true,
};

export const GEO_CONFIG_STOP = {
  stopOnTerminate: true,
  heartbeatInterval: undefined,
  preventSuspend: false,
};

Is this overcomplicating things, or should I merge these into a single state and simply toggle key parameters dynamically depending on activity?
Thanks in advance for your advice!

Do I need three separate states (default, start, stop) for my use case

No.

Am I over-optimising by completely disabling tracking in the STOP state

Yes.  When the user clicks some sort of button signalling the end of their "walk", you call .stop().  When the user clicks some sort of UI button signalling the start of their "walk", you call .start(), followed by .changePace(true).
// Start walk
await BackgroundGeolocation.start();
await BackgroundGeolocation.changePace(true); // <-- toggle immediately to "moving" state.
.
.
.
// Stop Walk
BackgroundGeolocation.stop()

Would maintaining just one state with some dynamic modifications be a better approach

Yes.
Some notes about your config:

foregroundService: true,

I don't know where people get the idea to use this option.  It's been deprecated from the plugin for over 5 years and it does absolutely nothing.  The plugin completely ignores this option.  Delete it.

preventSuspend: false,

This iOS-only option only works with Always location authorization.  You're using WhenInUse.  Delete it and forget about it.  Also, it only applies when the device is in the stationary state, which your walking app is not interested in.
See API docs Config.stopTimeout and provide a sufficiently high value for your use case to prevent the plugin unnecessarily entering the stationary state for brief pauses in activity (eg: 20 min).

Thanks for your detailed and prompt response. I appreciate the clarification regarding the states and config options. I’ll simplify things based on your advice and remove the unnecessary configurations like foregroundService and preventSuspend.
I’ll try out the changes and will update you if any issues arise. Thanks again for the guidance.

I don't know where people get the idea to use this option. It's been deprecated from the plugin for over 5 years and it does absolutely nothing. The plugin completely ignores this option. Delete it.

It looks like the documentation still mentions preventSuspend as an option, which could be misleading for users. It might be helpful to update or remove that section to avoid any further confusion.
See: Documentation Link


prevent goimports as latest release

installer doesn't work in that case
acceptance criteria:

Taskfile updated
GitHub Actions has tests

solution: add cronjob to test installation on different machine regularly

automate publication by GitHub Action in https://github.com/kamilsk/homebrew-tap

See kamilsk/godownloader/issues/5, kamilsk/mergestat/issues/6.


Add ability to update current rules or bring your own

I now find myself fixing bugs to the SqlServer.Rules rule set and having a mechanism to update the ruleset out of band with a SDK update would be handy.
I am proposing the following simple approach, but let me hear what anyone else thinks.

Allow .dll content files to be added to the output folder actually need this path, not available today
Update DacpacTool: If CodeAnalysis is enabled, copy any .dll files from the output folder to the folder of executing assembly
DacFX Code Analysis will automagically pick up the added / updated rules

Sample .csproj addition to copy .dll files the output folder
	<ItemGroup>
	  <None Update="SqlServer.Dac.dll">
	    <CopyToOutputDirectory>Always</CopyToOutputDirectory>
	  </None>
	  <None Update="SqlServer.Rules.dll">
	    <CopyToOutputDirectory>Always</CopyToOutputDirectory>
	  </None>
	</ItemGroup>

@jeffrosenberg @jmezach @tcartwright

I did a POC, I think there are two issues;
Options.Output does not point to the bin folder.
Maybe the file copy of the .dll file happens too late.

@jmezach Sorry to bother you, but is a 2.7.1 release possible?

@ErikEJ Sure thing, unfortunately I was out sick a couple of days. But I'm back now, so I'll try to get a new release out today.

@ErikEJ Version 2.7.1 is out now

Wonderful  thanks!


Provider crashing

The provider is in version 1.8.0
The container is crashing after some tome and restart :
The last error is :
2024-11-29T15:47:06.567258246Z {"level":"info","ts":"2024-11-29T15:47:06Z","logger":"provider-keycloak","msg":"Async update callback failed","trackerUID":"fde67c29-37d6-485f-945d-80ce1a90ce71","resourceName":"XXXXXi","gvk":"client.keycloak.crossplane.io/v1alpha1, Kind=ProtocolMapper","error":"cannot get resource /, Kind=/ after an async update: ProtocolMapper.client.keycloak.crossplane.io \"\" not found"}
2024-11-29T15:47:09.187762985Z panic: assignment to entry in nil map
2024-11-29T15:47:09.187795746Z
2024-11-29T15:47:09.187799729Z goroutine 181562 [running]:
2024-11-29T15:47:09.187803949Z reflect.mapassign0(0x1f7f3e0, 0xc00481ce20?, 0xc003efcf30?, 0xc003efcf30)
2024-11-29T15:47:09.187806815Z  runtime/map.go:1370 +0x1d
2024-11-29T15:47:09.187809852Z reflect.mapassign(0xc004254240?, 0xc004295c30?, 0x8b8209?, 0xc004254240?)
2024-11-29T15:47:09.187812519Z  reflect/value.go:3877 +0x8d
2024-11-29T15:47:09.187815958Z github.com/modern-go/reflect2.(*UnsafeMapType).UnsafeSetIndex(...)
2024-11-29T15:47:09.187819942Z  github.com/modern-go/reflect2@v1.0.2/unsafe_map.go:76
2024-11-29T15:47:09.187840607Z github.com/json-iterator/go.(*mapDecoder).Decode(0xc004df1220, 0xc002797dd0, 0xc004254240)
2024-11-29T15:47:09.187843675Z  github.com/json-iterator/go@v1.1.12/reflect_map.go:191 +0x325
2024-11-29T15:47:09.187847499Z github.com/json-iterator/go.(*structFieldDecoder).Decode(0xc00481cfe0, 0xc004295d28?, 0xc004254240)
2024-11-29T15:47:09.187850777Z  github.com/json-iterator/go@v1.1.12/reflect_struct_decoder.go:1054 +0x50
2024-11-29T15:47:09.187853441Z github.com/json-iterator/go.(*eightFieldsStructDecoder).Decode(0xc0015fafc0, 0xc002797dc0, 0xc004254240)
2024-11-29T15:47:09.187860761Z  github.com/json-iterator/go@v1.1.12/reflect_struct_decoder.go:897 +0x146
2024-11-29T15:47:09.187863782Z github.com/json-iterator/go.(*Iterator).ReadVal(0xc004254240, {0x1fba220, 0xc002797dc0})
2024-11-29T15:47:09.187867062Z  github.com/json-iterator/go@v1.1.12/reflect.go:79 +0x14b
2024-11-29T15:47:09.187871072Z github.com/json-iterator/go.(*frozenConfig).Unmarshal(0xc00036e280, {0xc000e64160?, 0xc0049d2f00?, 0xc0049d2e10?}, {0x1fba220, 0xc002797dc0})
2024-11-29T15:47:09.187877035Z  github.com/json-iterator/go@v1.1.12/config.go:348 +0x99
2024-11-29T15:47:09.187885507Z github.com/crossplane-contrib/provider-keycloak/apis/client/v1alpha1.(*ProtocolMapper).SetObservation(0xc002797b88, 0x225ad80?)
2024-11-29T15:47:09.187888563Z  github.com/crossplane-contrib/provider-keycloak/apis/client/v1alpha1/zz_protocolmapper_terraformed.go:43 +0x7e
2024-11-29T15:47:09.187915931Z github.com/crossplane/upjet/pkg/controller.(*terraformPluginSDKExternal).Update(0xc002dada40, {0x26b7db0, 0xc0032c2c40}, {0x26da4c0, 0xc002797b88})
2024-11-29T15:47:09.187931549Z  github.com/crossplane/upjet@v1.4.0/pkg/controller/external_tfpluginsdk.go:699 +0x2c2
2024-11-29T15:47:09.187945829Z github.com/crossplane/upjet/pkg/controller.(*terraformPluginSDKAsyncExternal).Update.func1()
2024-11-29T15:47:09.187947801Z  github.com/crossplane/upjet@v1.4.0/pkg/controller/external_async_tfpluginsdk.go:173 +0x145
2024-11-29T15:47:09.187949917Z created by github.com/crossplane/upjet/pkg/controller.(*terraformPluginSDKAsyncExternal).Update in goroutine 5380
2024-11-29T15:47:09.187954141Z  github.com/crossplane/upjet@v1.4.0/pkg/controller/external_async_tfpluginsdk.go:169 +0x14c

After further investigation using debug mode, I discovered the issue was caused by the ProtocolMapper being reconciled infinitely.
The root cause is that if you don't specify all the fields in the config section, these fields are detected as differences, triggering constant reconciliation.
Additionally, there appears to be a minor memory leak during this process, eventually leading to an OOMKill of the container.
By updating my ProtocolMapper configuration as follows:

  "introspection.token.claim": "true",
  "userinfo.token.claim": "false"

the crash no longer occurs.

I'll look into that, we might be able to mitigate that


Please check the part about How To Use Docker

Hello, pls check part "How do I run there scrips in Docker?", as I know, the step 4(Building a Docker image and testing our code), after image build and our model training finished, we should evaluate out model using command "pyhton evaluate_model.py test_data test_outputs", but I found "model" argument exits in this command, which likely be a typo.

Please run python evaluate_model.py test_data test_outputs to evaluate your model's outputs on the data.
(This command uses the word "test", but the teams do not have access to the test data, so you would use part of the training data.)


Release Minikube deployment repository publicly

See https://github.com/datarevenue-berlin/OpenMLOps/pull/77


Add feature to query PI points directly

I made as minimal changes as possible to add the capability to query PI points directly from the dataserver. There is an abundance of unused code, much of which appears to have been initially created for this PI point feature. So as to not completely overhaul things I added minimal code to adapt the current solution to add PI point querying.
I slightly modified the GUI to allow toggling of searching via PI point or AF. In doing so I removed code that was generating a phantom segmentsrv object in the segments path. Perhaps it is necessary for something else? In my testing I didn't notice a change in performance of any features with it removed.
I added some images for explaining the difference between querying via the AF and querying via PI points as well as some documentation on how in the README.
Let me know your thoughts and if I mucked things up. I performed the grunt build but it's possible I missed thing. I live in Python, not web development.

Updated to accommodate for the bug when editing panels. Performed more testing. So far, no issues.

Dear cluffja, thanks for your great Feature to query PI points directly! It is working very good, except I can not use the "Recorded values" and also the Calculations are not working for me.
Does that work for you?

@cluffja small Update: the Recorded Values are working, when there is also a value for the "Max Recorded Values" entered.
Also regarding the Calculation I can not exclude if the problem depends on the piwebapi I´m using.
Another cool addition would be the possibility to get a list of the available pi-tags in PiPoints mode instead of exactly enter the tag-name. I´m already trying to develop this, unfortunatly I´m not having so much experience in JS to really push this forward.

@sonicdoo well that is good to know in tracking things down. The Recorded Values and Calculation fields I have not used too often for various reasons.
As for the PiPoint list idea, I agree but I'm also a bit unsure how to go about doing the implementation. Some users have millions and millions of PiPoints (the company I work for does). In this case it would break things if we listed them all. We'd need to figure out either paging or some other method to handle the size.

@cluffja you are right, just listing all PiPoints might be not practically due to the amount of PiPoints. I`m thinking about listing all relevant PiPoints which got a entered searchstring inside. And then maybe just show the list when there are max 100 points found. In my case the pi-tagnames are self-explanatory. I think this would interfere the step when the wepapi is asked for the webID.

@cluffja No need for an apology, I'm super appreciative of the work you've done so far! I'm going to go through the code tomorrow and see if I can work out what's gone wrong for me. I'll also roll back grafana and try a few previous versions. I'm currently running the docker hub latest tag which is 7.5.6. Which version did you test on? Again, thank you for what you've done so far!

I'm using the version based on Grafana v7.4.3 (010f20c1c8) and querying pipoints directly works for me. (no AF-Server available on the piwebapi I´m using)

nothing special on my datasource config:

And I was testing/developing on Grafana 7.3.7 (Linux) so it makes me think it isn't a Grafana version issue. Also, my PI Server that I'm testing against has an AF server so whether it's there or not doesn't seem to matter either. I'll keep pondering on this.

I probably should've done this before commenting, but it looks like it's a browser issue. I thought Grafana was compatible with all Chromium browsers, but Brave seems to not like executing all of the JS on a page... It's working fine in Chrome now, but calculations are still an issue. In order to get data, I have to leave the "Calculation" field completely empty.
I've just started looking into it and I'll be sure to report if I see anything that jumps out at me. I'll admit, though, my JavaScript skills are pretty lacking.

Woo! That's fantastic news. I'm a huge fan of Brave. Good to know that it might cause issues.

This is a fantastic enhancement. Is there a plan when this will be merged?
Kind regards
Michael

This patch has been very helpful to us and is an important enhancement.  I would second @Coding-Mike 's question on merging.  Happy to help if I can.  We have tested it quite a bit and it seems to work well.

I generally let @coderReview merge these as he has an environment where these features can be tested,
That said, I recently have a new PI instance setup as well - but I don't have all the web interfaces and AF configured yet - so I am not able to fully test.
That said, if @coderReview doesn't have time to review, I can merge simply based on your successful deployments.

hi @ritchiecarroll  let me see if I can find this week to check. If not let's go ahead.

Thanks to @coderReview and the rest of the team!  Great work on this plugin.

@coderReview OK to merge?

Any chance this can be merged?

@cluffja can you fix the PR conflict? I will try to look at this PR this week. Thank you


Add Input Checks for pre_aggregated

Should be iterable
Number of columns and types should match what's expected
Allow pre_aggregated on execute_df; error or warning if pandas passed in (or maybe just work?)

Spark DataFrames and RDDs might not be executed until the caller requests rows from the result of execute().  Pulling the first row of data to check types, then re-running for the map() to produce output, would result in the query used for pre_aggregated being run twice, which could be very expensive.  One way to avoid double-execution would be to do the type and column checking inside the row map.
The implementation currently ignores column names on pre_aggregated, because the column names in the typical case are generated by the private reader (including names with random strings), and all values are extracted from the subquery result recordset positionally.  This could lead to errors if the caller passes in pre-computed aggregates in a different order than what the private reader is expecting (e.g. correct number of columns, and both integer, but they are swapped). This would be tricky for the caller to debug.  And, since the values being passed in are pre-aggregated, we have no way of checking to see what expression was used to compute each column.  However, we can use some heuristic to compare passed-in column names with the names that would've been used in the typical case, and throw error or warning if they don't match.

Done


Promote deployment to production via deployctl

Deployment works great for me, I can push a site to Deno Deploy without issue (via GitLab CI). However, there's one step missing from deployctl as far as I can tell that I couldn't find in the -h or readme, which is to promote to production.
When I have merged a branch to main branch, I want to deploy it (works) but then I can not promote it to production via CLI, effectively disabling me to fully deploy to production via CI.
Is this something you're planning to support or am I missing something?

@Joostvanderlaan I don't think there's the ability to promote a preview build to production but you can run your deployctl deploy command with the --prod flag to deploy right to production, e.g.:
deployctl deploy --project my-project-name --prod server.ts

Thank you Andrew, works like a charm!


Note10 S20 - New phones with multiple cameras

Seems like there is a problem with the new multicamera phones.
On the "old" phones everything is perfect... on the new ones I can only guess, the wrong camra is used.
Is there any solution for this?

Yep.  Such as most LG phones since at least the G6, I think a bit earlier than that, you have multiple rear cameras, one of which is usually a wide-angle, and totally fisheyes whatever it is that you're looking at, which becomes unscannable with Quagga.   (maybe someone could implement an anti-fisheye effect...)
You can use Quagga.CameraAccess.enumerateDevices() to get a list of all the camera devices and allow for the user to select which one to use, based on it's deviceId.  Then you can pass the deviceId into Quagga.init instead of the 'facing' property, and it will use the given device.  I believe this is in the examples in the repo, also

Is there an example of how to use Quagga.CameraAccess.enumerateDevices()?

It works exactly the same way as the built-in [enumerateDevices][https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/enumerateDevices] but filters out everything that isn't a video input device.
(i just realized it's "Quagga.CameraAccess.enumerateVideoDevices" and updated my first comment)
Here's the test for CameraAccess.enumerateVideoDevices in my fork https://github.com/ericblade/quagga2/blob/0e7228e29793d132f8f78debcb455b369ed798ad/src/input/test/browser/camera_access.spec.ts#L31
and here's the example from the example folder in the source https://github.com/ericblade/quagga2/blob/master/example/live_w_locator.js#L85

I’m sorry for the novice question but I can’t debug this on my PC and nothing happens on my mobile (where I have no idea how to debug).
Is there any way to allow something like Dev Tools on an Iphone or Android?
From: Eric Blade<EMAIL_ADDRESS>Sent: Tuesday, May 19, 2020 8:04 PM
To: serratus/quaggaJS<EMAIL_ADDRESS>Cc: berberon<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [serratus/quaggaJS] Note10 S20 - New phones with multiple cameras (#435)
It works exactly the same way as the built-in [enumerateDevices][https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/enumerateDevices] but filters out everything that isn't a video input device.
(i just realized it's "Quagga.CameraAccess.enumerateVideoDevices" and updated my first comment)
Here's the test for CameraAccess.enumerateVideoDevices in my fork https://github.com/ericblade/quagga2/blob/0e7228e29793d132f8f78debcb455b369ed798ad/src/input/test/browser/camera_access.spec.ts#L31
and here's the example from the example folder in the source https://github.com/ericblade/quagga2/blob/master/example/live_w_locator.js#L85
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/serratus/quaggaJS/issues/435#issuecomment-630953422 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABRBNQUBFE6DJU6S5GH2XWTRSK3YXANCNFSM4NEKIUBA .

On a PC, you can serve from localhost, and Chrome will let you use the Camera APIs if you're connecting to localhost.  You can also run Web Inspector in Chrome on your desktop, and attach it to your Android phone.
Remote debugging Android: https://developers.google.com/web/tools/chrome-devtools/remote-debugging

thanks Eric, i appreciate your response.
tried for several hours today to get dev tools and my android to work. made
very little progress as this is not my strong side :)
if anyone is interested, i’ll be more than happy to pay for the fix i need.
i can be contacted at<EMAIL_ADDRESS>thanks
On Wed, 20 May 2020 at 21:07 Eric Blade<EMAIL_ADDRESS>wrote:

On a PC, you can serve from localhost, and Chrome will let you use the
Camera APIs if you're connecting to localhost. You can also run Web
Inspector in Chrome on your desktop, and attach it to your Android phone.
Remote debugging Android:
https://developers.google.com/web/tools/chrome-devtools/remote-debugging
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/serratus/quaggaJS/issues/435#issuecomment-631636450,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRBNQVSJAVQLD35O2YFE3DRSQL5DANCNFSM4NEKIUBA
.


Fileutils test cases fail

Failing test case to be fixed
TestFileExists/Existing_File

Minor glitch introduced, already fixed!!


Add 409 response when adding an existing measure

Previously we didn't catch responses for duplicate measures. This PR means we return a 409. This is consistent with how we deal with scenarios and i think we want to same behaviour with measures.

Just seen you've already done this in #265 ! There is a test here though so I think after 265 is merged, this should just leave the test to be commited.

Nevermind, #265 also has a test! I'll close this PR, its already been implemented :)


aws_launch_template issue with multiple security groups

Hello ! I have a problem when adding a second security group on my instance. It worked with the first security group but not when adding the second one.
Here is my variable : ["sg-11111", "sg-22222"]
Terraform version : 0.12.29
terraform-provider-aws : v3.22.0_x5
resource aws_launch_template "instance_template" {
  name_prefix = var.instance_name

  image_id      = var.zpa_ami_id
  instance_type = var.instance_type

  vpc_security_group_ids = var.sg_ids

  key_name = var.aws_ssh_key_name
  user_data = base64encode(data.template_file.userdata_script.rendered)
}

hi @Anthony-Quere - launch template support was only added today to v4.0. please try upgrading and let us know if your issue still persists


error in expression "move (-1)"

when I select Enable, and charge the web, on the console trace the following:

Error: [$parse:ueoe] Unexpected end of expression: move(
http://errors.angularjs.org/1.3.14/$parse/ueoe?p0=move(
    at REGEX_STRING_REGEXP (http://localhost:1908/Scripts/angular.js:63:12)
    at Parser.peekToken (http://localhost:1908/Scripts/angular.js:12018:13)
    at Parser.functionCall (http://localhost:1908/Scripts/angular.js:12318:14)
    at Parser.primary (http://localhost:1908/Scripts/angular.js:11995:24)
    at Parser.unary (http://localhost:1908/Scripts/angular.js:12271:19)
    at Parser.multiplicative (http://localhost:1908/Scripts/angular.js:12254:21)
    at Parser.additive (http://localhost:1908/Scripts/angular.js:12245:21)
    at Parser.relational (http://localhost:1908/Scripts/angular.js:12236:21)
    at Parser.equality (http://localhost:1908/Scripts/angular.js:12227:21)
    at Parser.logicalAND (http://localhost:1908/Scripts/angular.js:12218:21)

when I change the number -1 of the expression to another non-negative, the error disappears

I found a (kind off) similar error when testing an app found on builtwith.angularjs.org:
https://m.auspost.com.au/view/home
Only when Batarang is enabled does the following error show up on the console:
"Error: [$parse:lexerr] Lexer Error: Unterminated quote at columns 10-15 ['menu] in expression [showPanel('menu].
http://errors.angularjs.org/1.2.20/$parse/lexerr?p0=Unterminated quote&p1=s 10-15 ['menu]&p2=showPanel('menu
at https://m.auspost.com.au/js/app-min.js:1:675
at od.throwError (https://m.auspost.com.au/js/app-min.js:3:22687)
at od.readString (https://m.auspost.com.au/js/app-min.js:3:24535)
at od.lex (https://m.auspost.com.au/js/app-min.js:3:21392)
at pd.parse (https://m.auspost.com.au/js/app-min.js:3:24767)
at $get (https://m.auspost.com.au/js/app-min.js:2:18771)
at chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:1676:17
at Array.forEach (native)
at ngEventHandler (chrome-extension://ighdmehidhipcmcojjgiloacoafjmpfk/dist/hint.js:1671:20)
at s (https://m.auspost.com.au/js/app-min.js:1:26805) "
It then seems that Batarang cannot be disabled on that page without disabling it in chrome completely.

related: https://github.com/angular/angularjs-batarang/issues/232

I had the same issue and from my point of view this happens inside hint.js
https://github.com/angular/angular-hint/issues/98

Getting this same error.  Using Angular-UI Bootstrap Datepicker.  Thankfully StackExchange exists and I only lost 15 minutes on this.

fix landed in https://github.com/angular/angular-hint/commit/26cfc749113a599a1e11a587091c558ee2e499b6


dependency on github.com/go-fonts/dejavu v0.3.2, which doesn't exist (anymore?)

The go.mod file lists v0.3.2 of github.com/go-fonts/dejavu as a dependency:
https://github.com/go-latex/latex/blob/5c1ce85aa4ea1636d7a06434177ed7ef995a1064/go.mod#L7
However, the latest version tag of go-fonts/dejavu is v0.2.1: https://github.com/go-fonts/dejavu/tags
There seems to have been a v0.3.2 at one point: https://pkg.go.dev/github.com/go-fonts/dejavu?tab=versions

I've published all missing tags.
thanks for the issue.


language extensions to create serialization chunk

This is a mini-DSL to simplify the creation of serialization chunks

Maybe we've missed the most obvious solution: Set only the actually required properties to required, e.g. node id/classifier.
That doesn't change the API or semantics, as there are sensible defaults for the others.


Get current balance from each pool's API

Current balance should be retrieved from selected pool API

Current balance has been retrieved for two pools, unsupported for one pool


Correct the link word wrapping within a container in Chrome.

To do with #851.

This will never get merged. I assume this repo to be dead.

Considering adding this to my normalize in https://github.com/garrettw/vitals -- but only if your code matches what most browsers tend to do (i.e. needs to be more than just Firefox). If most browsers do what Chrome does, then the fix should correct Firefox's behavior.


SetOptionsOp returns an error when setting a signer

Precheck

[X] Do a quick search and make sure the bug has not been reported yet.
[X] Please disclose security vulnerabilities privately at<EMAIL_ADDRESS>[X] Finally, be nice and have fun!.

Description
SetOptionsOp returns an error when setting a signer
Environment

Elixir & Erlang/OTP versions (elixir --version): OTP23, v.1.11.2
Operating system: macOS

Current behavior
op = Stellar.TxBuild.SetOptions.new(
  signer: [ed25519: "GDPLQNBD5XXXXXXXXXXXXXXXXXXXXXXXXX", weight: 1]
)

{:error, [signer: :invalid_signer]}

Expected behavior
Allow setting a signer for an account through the SetOptionsOp.
There are multiple signer keys that need to be allowed :ed25519 | :sha256_hash | :pre_auth_tx
op = Stellar.TxBuild.SetOptions.new(
  signer: [ed25519: "GDPLQNBD5XXXXXXXXXXXXXXXXXXXXXXXXX", weight: 1]
)

%Stellar.TxBuild.SetOptions{
  ....
  signer: %Stellar.TxBuild.Signer{
    signer_key: %Stellar.TxBuild.SignerKey{
      key: "GDPLQNBD5XXXXXXXXXXXXXXXXXXXXXXXXX",
      type: :ed25519
    },
    weight: %Stellar.TxBuild.Weight{value: 1}
  }
}

Bug fixed in version 0.9.3. 👌🏻


Graph changes not updated

Hi
It seems changes to edges, are not reflected on the graph. When loading, the graph is drawn as expected, but later adding/removal of edges seem ignored.
I have tried extending the changes on the nodes object, as in the demo - without any luck. What could be the problem?

Not enough info.

Same problem here:
<cytoscape flex graph-elements="graph.elements" graph-layout="graph.layout" graph-style="graph.styles"></cytoscape>
<button ng-click="onClick()">Test</button>
{{graph.elements | json}}

$scope.graph = {
  elements: [
    {'data':{'id':'1', 'name':'1'}},
    {'data':{'id':'2', 'name':'2'}},
    {'data':{'id':'3', 'name':'3'}},
    {'data':{'source': '1', 'target': '2'}},
    {'data':{'source': '2', 'target': '3'}}
  ],
  layout: {...},
  styles: [...]
};
$scope.onClick = function() {
  $scope.graph.elements.pop();
};

You'll see how the edges disappear from the canvas, but not the nodes, despite they're really removed from the elements array.

Elements should be an object map, not an array of objects.  I wanted to realign this directive more closely with Cytoscape's Array of Objects, like you posted, I just haven't gotten around to it.


AwesomeWM Attempt to index a nil value

I'm using the dotfiles from saimoomedits and I get this AwesomeWM error:
bruh! an error has occured!

/home/admin/.config/awesome/ mods/battery-widget/init.lua:39: attempt to index a nil value

My init.lua for awesome-battery_widget is the default and I have not touched anything.
Thanks

Hello @TalinTheDev,
Do you have the full stack-trace of the error?
The failing line from the message is
    local devices = upower.Client():get_devices()

Can you make sure you have UPowerGlib correctly installed (https://lazka.github.io/pgi-docs/UPowerGlib-1.0/index.html)?

Thanks for your help but for some reason, when I booted into Arch today morning, after my computer being shutdown overnight, it works now so I think I'm good. Thanks tho!


The mass cut in hod_mock_factory should throw an informative error if all halos are removed.

When calling populate_mock on a halocat, some initial operations are run on that halocat as the mock object are created. Among these is a so-called "trivial" mass cut (line 123 of hod_mock_factory). I made a mistake when caching my catalog and my mass column was misdefined, and the cut removed all my halos. However, I didn't realize a mass cut was performed at all, and it took some digging to figure out what happened. In this instance where all or even most halos are removed from a catalog, an error should be thrown, suggesting either the user made a mistake defining their cached catalog or there is a problem with their halocat itself.

Thanks for pointing this out @mclaughlin6464 - I'll address this very soon.

@mclaughlin6464 - let me know whether this commit would have made your life easier, or if you have other suggestions for how this would have been easier to track down:
https://github.com/aphearin/halotools/commit/75f85ad864449dd7ea64b9554d49550714290cd4
Also, can you also clarify a bit more what happened with your "misdefining" the mass column? Depending on exactly what happened, I might like to add additional measures at multiple entry points to protect against what you experienced. For example, if you accidentally cached an empty halo catalog, that should have raised flags as well.
If other aspects of the catalog processing could have been more transparent, feel free to comment either here or in an independent issue.

Yes, the above commit would've fixed the issue.
And to clarify, when reading in the catalog I put the wrong column down for mvir and it read in a list of id's or something. So, none of the numbers were > 1e13 or so, so they were all cut.

Right, that's what I suspected happened. Super common, happens to me all the time. I wish there were something I could do about that at the level of the reader, but there are so many different versions of Rockstar floating around and there is nothing approximating a standardized header.
Thanks again for the feedback.


Bug deploying triggers that are started in target Data Factory

Describe the bug
When deploying triggers that are started in the target Data Factory, the deployment fails, since they need to be stopped before deployment.
This behavior leads to enable $Option.StopStartTriggers=$True, but this affect all the triggers published in Data Factory.
I think this bug is related to #51
To Reproduce
With triggers started in target Data Factory...
$Option.StopStartTriggers = $False
$Arguments = @{
    RootFolder = $this.AdfRootFolderPath;
    ResourceGroupName = $this.ResourceGroupName;
    DataFactoryName = $this.DataFactoryName;
    Location = $this.Location;
    Option = $Option;
    Stage = $this.ReplacePropertiesFilePath;
}
Publish-AdfV2FromJson @Arguments

Expected behaviour
Stop trigger if currently started, deploy trigger, and start again.
Version of PowerShell module of:
azure.datafactory.tools 0.17.0

@dsuarez993, this is not a bug, it was designed like that.
It is a user responsibility to take care of triggers and not deploy them when flag StopStartTriggers is set to $false.
However, as you noticed, the problem is wider and as such must be treated.
Let me think about the concept, I will describe it and then crossed unit tests must be prepared along with the feature.

@NowinskiK yes, that was my impression when I started trying to fix the triggers issue.
Then, suddenly I started to think that maybe the StopStartTriggers was meant for another purpose, because it makes a lot of sense that sometimes you want to Stop all the triggers during deployment in order to avoid triggers to get triggered while other Adf objects related to it are being deployed, protecting the affected pipelines from failure. So I think this functionality in this way is very useful, but shouldn't be mandatory for deploying triggers.
As a bit of a context of how we are using this module:

We have several projects co-existing in the same Data Factory. We have a Git Repository for Data Factory, and we release a new Artifact with the Adf folder every time there is a change in master branch.
We have a Git Repository per Project with it's own versioned code (including Databricks Notebooks, SQL database solution..., and Data Factory deployment config files for this PowerShell Module, specifying what Adf Objects are related to the project).
The CI/CD pipelines of each Git Repo project, (during Data Factory deployment task to TEST/PROD environments) takes the Adf Artifact, and perform the deployment using the ADF deployment config files, deploying only the Adf objects related to the project.

This is the reason why (in our case) not every trigger in the Adf folder source needs to be restarted in the target Data Facotry, and why sometimes they are not even deployed.
Regarding the specific functionality/bug discussed in this issue, we don't need to StopStart all the other triggers not included in the project we are deploying, because they are not even related to the project, and they can be triggered and run pipelines without failing.
So I think, the change in #72 fixes this behavior (maybe it should be implemented somewhere else?), allowing you to deploy triggers regardless their state in the target Data Factory. Moreover, you can still use StopStartTriggers functionallity if you need a full StopStart of all the triggers (this still should be fixed to start only the triggers present in the target Data Factory not the ones in source Adf folder).
Let me know if I can do anything to help :)

@dsuarez993 thanks for commenting this and sharding the lights onto a different way of managing and deploying ADF.
Although I'm not convenient keeping ADF code in that way - it may work for you and probably there are certain reasons behind that.
However, the assumption of using this module is that you have all files existing in the source location.
Aim of this module was to do the job and to not overcomplicate its usage.
An appropriate solution will be introduced in #51, but I hope it will cover your scenario as well.

@NowinskiK we are not doing anything far from that assumption. We, indeed, use the full Source Adf folder, but it's just made available to other CI/CD pipelines through an Artifact in the Artifact Feed. We just cherry pick from there what to deploy for each project by applying the inclusion rules in the rules.txt file (the one I called ADF deployment config file before).
And I can tell you, this PowerShell module has been a turning point for us. I think the possibility of completely decoupling projects that share the same Data Factory is awesome. So if that was not the intention, it was an great side effect of it hahah. Thanks for all the great work!
P.S.: I've disabled StopStartTriggers, and added the logic in #72 as extra step to our own PowerShell code and now it works like a charm. So from our side we are ok, but I still think it would be a great addition to this module.

Really understand. But as long as you couldn't give me a clear picture of your case or build unit tests - I had to take into consideration all possible permutations. That's the picture:

Take a look and let me know which cases are working not as you would expect.
Note: Flag DoNotStopStartExcludedTriggers (default: false) does not exist yet, but will be introduced in the new version and will change behaviour slightly. I'm wondering if "new behaviour" covers your needs.

@NowinskiK I have the feeling this is getting a bit overcomplicated.
In case you decide to go for the ´DoNotStopStartExcludedTriggers´ flag, the analysis is quite correct, but keeping in mind that the column is False for all rows, not all the permutations are covered "yet" and it would double the current list.
Although, I'm not agree with the resolution of some of the permutations:

B08 and B09: If you don't include those triggers in your deployment, why changing their state as in source? Just keep their current state. If you actually want to update the state of those triggers, just  include them to your deployment. (As an example of this, one of our data teams in their ADF have two Triggers that executes the same pipeline, one does it weekly, and the other daily. In Dev Environment they only enable the weekly, and in Test/Prod Environments they only enable the daily. If we apply this to them, in every deployment the state of those triggers will be overwritten with the Dev state, messing everything up.)
T01, T02, T09, and T10: If triggers included but not present in Source, just raise a Warning, but don't change the state (they might be already published in that Data Factory and not in Source for a reason, like a hot fix added manually).
T03: As in B08 and B09, if it's not included, keep the state even if not in Source. Again, it might be in that Data Factory and not in Source for a good reason.
T13: This is a difficult one. I think that if a Trigger is included in a deployment but not in Source, it can only mean that somebody forgot to remove that line from the rules.txt file. I would just rise a Warning, and not an error since that can stop the whole deployment for a little mistake.
T15: Also a bit difficult... I think in the safer option is to just raise a Warning and keep state, for the same reason as for T01, T02, T09, T10 and T13, that Trigger might be there enabled for a good reason. It is also true that if you are looking for "Deleting all not in source", it should be disabled, and then deleted.

What is the reasoning behind the initial design you mentioned before? Is it coming from the standard deploying approach where you have to stop all the triggers before publishing the Data Factory ARM template?

@dsuarez993, this is not a bug, it was designed like that.
It is a user responsibility to take care of triggers and not deploy them when flag StopStartTriggers is set to $false.
However, as you noticed, the problem is wider and as such must be treated.
Let me think about the concept, I will describe it and then crossed unit tests must be prepared along with the feature.

What is the issue of applying "before deploying a trigger, stop it if it's running, deploy it, and start it again if it was running before"? I think this could be the "by default" implementation, because otherwise you only get an error when deploying triggers that are already published and enabled. I don't see any potential damage of this.
In this case, I would keep StopStartTriggers to StopStart all triggers published in target Data Factory (in this case a rename of this flag by StopStartAllTriggers for transparency, keeping StopStartTriggers for retro-compatibility, and marked as "deprecated soon").
I think it will simplify really a lot the implementation, since you don't even have to add the new Flag DoNotStopStartExcludedTriggers  and put the effort of thinking about all the permutations, and implement the Unit Tests for them.
Here I attach my version of all the permutations as I would like them to be:

I hope it helps! Let me know what your thoughts are about this.
Thanks for all your time and effort! :)

Let me answer firstly on this:

What is the reasoning behind the initial design you mentioned before? Is it coming from the standard deploying approach where you have to stop all the triggers before publishing the Data Factory ARM template?

Stopping all triggers is the safest and easiest way. Some other objects (like pipelines) are dependant on triggers. Deployment all objects in serial sequence might make the whole ADF inconsistent during the process, and I prefer to not invoke any trigger then.
Nevertheless, now you will be able to choose that behaviour more granularly using publish options.

Let me answer firstly on this:

What is the reasoning behind the initial design you mentioned before? Is it coming from the standard deploying approach where you have to stop all the triggers before publishing the Data Factory ARM template?

Stopping all triggers is the safest and easiest way. Some other objects (like pipelines) are dependant on triggers. Deployment all objects in serial sequence might make the whole ADF inconsistent during the process, and I prefer to not invoke any trigger then.
Nevertheless, now you will be able to choose that behaviour more granularly using publish options.

@dsuarez993, thank you for your all comments, really appreciate it.
The following table presents planning logic when you use a new flag:

Therefore, answering your comments:

Case
Comment

T01
This is because StopStartTigeers=true. If you want to avoid stopping the trigger - add it to 'excludes' list (looks like the object should be excluded   as does not exist in the source)

T02
The same as above.

T03
Yes, new concept will not disable the trigger (when DoNotStopStartExcludedTriggers=true)

T13
Any mistakes must be fixed by developer as soon as possible and process should fail once the code or configuration is wrong. To avoid this case you may switch StopStartTriggers on.

T15
Some rules I described below.

StopStartTriggers
It allows you to decide. It stops ALL   existing and 'Started' (Enabled) triggers.
Generally you should use TRUE (default)   if you want to avoid troubles.
However, if you choose FALSE - you must   accept that process WILL NOT touch triggers. You can still do it for yourseft   in pre or post-deployment script.
DoNotStopStartExcludedTriggers
In some scenarios, people still want to   let process to manage of triggers, but with some exceptions.
Usage of this flag make sense along with   StopStartTriggers only and some objects are excluded from deployment.
It guarantees that no (excluded) objects   will be even touched in target service during the deployment.
Excluded (collection)
should completely separate group of objects from   other group.
In that way you can keep all files in the   source but control behaviour with flags.
Exclusion can be defined in two ways:

Explicitly in 'Excludes' collection
Implicitly by not adding an item in   'Includes' collection
Important: Both collections can use   wildcards as the name of objects.
It simplify defining multiple objects by   one line, or defining objects which does not exist yet.
These collections are very useful while   you want to do a selective deployment.

* DoNotDeleteExcludedObjects
Excluded object can be deleted only if   flag DoNotDeleteExcludedObjects = false
This situation could cause error when   trigger has not been deleted prior.
Otherwise, nothing will happen.
This option gives you a flexibility of deleting objects in the target, but still not touching objects from 'other'   group.
It comes from ticket #47
I hope this is now a more clear and broader picture of the whole behaviour.

@dsuarez993, thank you for your all comments, really appreciate it.
The following table presents planning logic when you use a new flag:

Therefore, answering your comments:

Case
Comment

T01
This is because StopStartTigeers=true. If you want to avoid stopping the trigger - add it to 'excludes' list (looks like the object should be excluded   as does not exist in the source)

T02
The same as above.

T03
Yes, new concept will not disable the trigger (when DoNotStopStartExcludedTriggers=true)

T13
Any mistakes must be fixed by developer as soon as possible and process should fail once the code or configuration is wrong. To avoid this case you may switch StopStartTriggers on.

T15
Some rules I described below.

StopStartTriggers
It allows you to decide. It stops ALL   existing and 'Started' (Enabled) triggers.
Generally you should use TRUE (default)   if you want to avoid troubles.
However, if you choose FALSE - you must   accept that process WILL NOT touch triggers. You can still do it for yourseft   in pre or post-deployment script.
DoNotStopStartExcludedTriggers
In some scenarios, people still want to   let process to manage of triggers, but with some exceptions.
Usage of this flag make sense along with   StopStartTriggers only and some objects are excluded from deployment.
It guarantees that no (excluded) objects   will be even touched in target service during the deployment.
Excluded (collection)
should completely separate group of objects from   other group.
In that way you can keep all files in the   source but control behaviour with flags.
Exclusion can be defined in two ways:

Explicitly in 'Excludes' collection
Implicitly by not adding an item in   'Includes' collection
Important: Both collections can use   wildcards as the name of objects.
It simplify defining multiple objects by   one line, or defining objects which does not exist yet.
These collections are very useful while   you want to do a selective deployment.

* DoNotDeleteExcludedObjects
Excluded object can be deleted only if   flag DoNotDeleteExcludedObjects = false
This situation could cause error when   trigger has not been deleted prior.
Otherwise, nothing will happen.
This option gives you a flexibility of deleting objects in the target, but still not touching objects from 'other'   group.
It comes from ticket #47
I hope this is now a more clear and broader picture of the whole behaviour.

@NowinskiK thank you so much for the effort! I’ve just saw the new release.  Looking really good! I’ll test it later on :)
The explanation on the README it’s ver clear. But, do you think it would be good to complete the “matrix-of-behaviour-logic.png” with what happens if DoNotStopStartTriggers is False?
Thanks again! And I hope I won’t bother you anymore hahah
Cheers!

@NowinskiK thank you so much for the effort! I’ve just saw the new release.  Looking really good! I’ll test it later on :)
The explanation on the README it’s ver clear. But, do you think it would be good to complete the “matrix-of-behaviour-logic.png” with what happens if DoNotStopStartTriggers is False?
Thanks again! And I hope I won’t bother you anymore hahah
Cheers!

@dsuarez993 you are right, I totally forgot to put the second part of that table. I've just added it to readme.
No worries, I'm glad and very appreciative of all your comments. Every contribution only makes this module better.
And sorry that I couldn't approve your previous PRs. Now, you can see how sophisticated this problem was, how much efforts it required, why I wanted to come comprehensively to that, and why all unit tests are so crucial.

@dsuarez993 you are right, I totally forgot to put the second part of that table. I've just added it to readme.
No worries, I'm glad and very appreciative of all your comments. Every contribution only makes this module better.
And sorry that I couldn't approve your previous PRs. Now, you can see how sophisticated this problem was, how much efforts it required, why I wanted to come comprehensively to that, and why all unit tests are so crucial.

Please create a new issue in case of any new comments.

Please create a new issue in case of any new comments.


Fix #7438 - Remove redundant skip in test

Summary
Fixes #7438 by removing redundant
Details and comments
This test was disabled wrongly, given that Pull Request 741 in aer was merged and newer versions of aer have been released since.

You're welcome to go through this and sort it out, but I think it might be a little more complex than just removing the skip. I had a very brief go before Christmas, and I think I hit some old code in the ConfigurableFakeBackend that was pretty out-of-date and might need a fair bit of updating. I don't remember 100%, though.

Okay, I shall look into it. Thanks for the update!

@jakelishman, would you be able to provide an insight to the most recent test fail as I wasn't really familiar with qiskit pulse.
Besides that, ConfigurableBackend had a parameter version which stood for backend_version. This was overlapping with the version parameter in the BackendV2 and thus was changed to fix previous traceback.

At @javabster's request, I've fixed the merge conflicts that were in this PR in order to have it run its CI again, but I don't know any context. My only comment above was just that I'd attempted to remove the unittest.skip line before and seen some failures (and sorry that I never replied to the question at the time).
It's possible that #9168 could be used instead of this PR, but I don't know the context of either PR, nor of the code in question here.

Closing in favor #9168 . Thanks!


feat: add AGWA/git-crypt

AGWA/git-crypt: Transparent file encryption in git
$ aqua g -i AGWA/git-crypt

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.
Command and output
$ git-crypt --help
Usage: git-crypt COMMAND [ARGS ...]

Common commands:
  init                 generate a key and prepare repo to use git-crypt
  status               display which files are encrypted
  lock                 de-configure git-crypt and re-encrypt files in work tree

GPG commands:
  add-gpg-user USERID  add the user with the given GPG user ID as a collaborator
  unlock               decrypt this repo using the in-repo GPG-encrypted key

Symmetric key commands:
  export-key FILE      export this repo's symmetric key to the given file
  unlock KEYFILE       decrypt this repo using the given symmetric key

Legacy commands:
  init KEYFILE         alias for 'unlock KEYFILE'
  keygen KEYFILE       generate a git-crypt key in the given file
  migrate-key OLD NEW  migrate the legacy key file OLD to the new format in NEW

See 'git-crypt help COMMAND' for more information on a specific command.

If files such as configuration file are needed, please share them.

Reference

https://www.agwa.name/projects/git-crypt/

Thank you for your contribution!

v4.149.0 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.149.0


"Cork buffer must not be held across event loop iterations!" error when doing async work inside upgrade handler

App crashes with Cork buffer must not be held across event loop iterations! error when I cork response.upgrade inside async function (version v20.30.0).
Tried this example without any modifications and it also gives me the same error.

Seems like I was using older version that didn't get updated when modifying package.json and executing npm i. npm i uNetworking/uWebSockets.js#v20.30.0 installed the latest version and now everything works fine.


Remove mutex from sessionWS

There are six different calls to s.Lock() in sessionWS.  Three of these locks are around calls to SetWriteDeadline and WriteMessage on the WebSocket.  WriteMessage will block for up to the timeout set in SetWriteDeadline, which has a default of 5000 milliseconds.  This lock is also acquired by SendBytes to determine if the session has been stopped.  This is a problem as the event processing methods in StatusRegistry and Track call SendBytes directly on the Session.  If one of the Sessions being written to has delays in writing data, this could cause backups in the event processing.
This change is more complex than https://github.com/heroiclabs/nakama/pull/1140/.  It fully removes the mutex from sessionWS.  All writes have been moved to only occur within processOutgoing so no panics are generated by concurrent writes.  The stopped variable is converted to an atomic.Bool, which is only used in the Close method to prevent more than one Close call being made.  As the outgoingCh is not closed, Send() is used to send the final messages and then the ctxCancelFn is called, which causes a Close message to be sent in processOutgoing after all messages are sent.  The ping backoff logic was also simplified.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Rename rke binary references to "rke".

Update RKE install instructions to rename binary to "rke".
Update docs that reference platform specific binaries in the examples.
Point to RKE Install docs instead of duplicating instructions.
Make shell usage more consistent (remove platform specific shell identifier '$' from examples)

lgtm. @deniseschannon , can you merge this please?


Please write up the post-mortem and checklist for the outage

cc @lukemarsden @wdbaruni
Help yourself in the future :)

We should've done it back then. I can barely remember what I ate yesterday, but I don't recall it was a significant outage. Closing this


Mark global variables as extern and implement them in iso_alloc.c

Fixes #8

Thanks for this PR. I ended up splitting out the sanity specific defines into a separate header and thanked you in CREDIT.md!


Make processId optional for initialization

Closes #177

Lint issues and you also need to correct the parameter order in the tests

Ah, I was editing this file in github and I assumed it will make spaces. I will fix issues.

Current coverage is 94.71% (diff: 100%)

Merging #178 into master will not change coverage

@@             master       #178   diff @@
==========================================
  Files            31         31
  Lines           416        416
  Methods          67         67
  Messages          0          0
  Branches          0          0
==========================================
  Hits            394        394
  Misses           22         22
  Partials          0          0

Powered by Codecov.