HDDS-5560. Update clusterId to correct value.

What changes were proposed in this pull request?
Correct setting of clusterId in the dnlayoutversion/version file.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5560
How was this patch tested?
Unit test

@ChenSammi @adoroszlai, Please help to review. Thanks

Thanks @ashishkumar50 for continuing this from #4110.  Code changes look good.
When building on others' unfinished work, please cherry-pick the original commits.  This allows Github to automatically insert additional author information.  For this PR, we'll need to add the following manually when merging the PR:
Co-authored-by: Nishit Patira<EMAIL_ADDRESS>Co-authored-by: Neil Joshi<EMAIL_ADDRESS>

Thanks @ashishkumar50 , and @errose28 @adoroszlai for the review.

Thanks @ChenSammi for merging it, but I think you missed this comment:

For this PR, we'll need to add the following manually when merging the PR:
Co-authored-by: Nishit Patira<EMAIL_ADDRESS>Co-authored-by: Neil Joshi<EMAIL_ADDRESS>

Also no response on my comment here. I was waiting to +1 until this was addressed. If it is an outstanding issue we can resolve it in a follow-up.


lsb_release fails in Oracle Linux

I'm trying Vagrant installation in Windows 10. I use the default Vagrantfile and hence boxcutter/ol72 base box (Oracle Linux).
The installation fails because Oracle Linux doesn't support lsb_release command.
PS C:\src\oxar> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'boxcutter/ol72' is up to date...
[...]
==> default: utils/os/permit_root_ssh_login.sh
==> default:
==> default: sent 199763 bytes  received 1363 bytes  134084.00 bytes/sec
==> default: total size is 195184  speedup is 0.97
==> default: /tmp/vagrant-shell: line 15: lsb_release: command not found
==> default:
==> default: * Loading configurations *
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
PS C:\src\oxar>

The problem in Vagrantfile shell provisioner:
    if [[ `lsb_release -i` =~ (Ubuntu) ]]; then
      sed -i s/^.*$/UTC/ /etc/timezone;
    fi

One way to identify Oracle Linux version:
login as: root
<EMAIL_ADDRESS>password:
Last login: Sat Apr  9 16:57:29 2016
----------------------------------------------------------------
  Oracle Enterprise Linux 7.2                 built 2016-01-05
----------------------------------------------------------------
[root@localhost ~]# lsb_release -i
-bash: lsb_release: command not found
[root@localhost ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.2 (Maipo)
[root@localhost ~]# rpm -qf /etc/redhat-release
oraclelinux-release-7.2-1.0.5.el7.x86_64
[root@localhost ~]#

Thanks for your feedback. I am aware that some of the Linux flavours do not have lsb_release out of the box. It was not a showstopper during my tests though. Did the process abort during your attempt to provision the VM using Vagrant? Which version of Vagrant are you on?

Yes, the provisioning process aborted (as you should see from the attached log), but I was able to continue manually (i.e. logged into linux and run build.sh manually as root) and got XE up and running without major fuss.
PS C:\src\oxar> vagrant --version
Vagrant 1.8.1
PS C:\src\oxar>

Yes, I can see that, but I have encountered during my tests that the build proceeds despite the error. Wanted to be sure, as I haven't seen this causing a full break during provisioning process. I will definitely look into a more stable method to detect the underlying OS. Thank you again for the feedback.

#158 removed the usage of lsb_release. I guess this can be closed now? @fuzziebrain

Indeed. Thanks for reminding me about this one.


Revert "Temporarily re-enable .NET 5 SDK install step"

Reverts Azure/azure-sdk-for-net#18298
The agent pools are supposed to have been fixed so undoing this change to test them.

/azp run net - template


[openssl] fails on windows with custom triplet

Host Environment

OS: Windows
Compiler: msvc2019

To Reproduce
Steps to reproduce the behavior:
./vcpkg install openssl:<triplet>
Failure logs
Building package openssl-unix[core]:<triplet>...
CMake Error at ports/openssl-unix/portfile.cmake:4 (message):
  This port is only for openssl on Unix-like systems
Call Stack (most recent call first):
  scripts/ports.cmake:94 (include)

Error: Building package openssl-unix:<triplet> failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: openssl-unix:<triplet>
  Vcpkg version: 2019.09.12-nohash

Additional context
Apparently the custom triplet confuses the dependencies here and vcpkg tries to install openssl-unix instead of openssl-windows.

What is the name of your triplet. Until #8601 gets merged we just do a string compare against your triplet name in resolving dependencies.

Ok, I fixed it for now by prepending "windows-x64-" to the port name.


Date editing does not follow given date locale

When you are editing a row that contains a date, the format of the date is always dd.mm.yyyy, even when the date locale is set. This bug does not exist when you are not in the middle of editing the date. I found this issue on the original material table repository that poses a potential fix for bug, but I have not looked into it enough to determine whether it is valid. https://github.com/mbrn/material-table/issues/2094
Here is an example to reproduce the bug
function Editable() {
  const { useState } = React;

  const [columns, setColumns] = useState([
    { title: 'Date', field: 'date', type: 'date', dateSetting: 'en-US' }]);

  const [data, setData] = useState([{date: new Date()}]);

  return (
    <MaterialTable
      title="Editable Preview"
      columns={columns}
      data={data}
      editable={{
        onRowAdd: newData =>
          new Promise((resolve, reject) => {
            setTimeout(() => {
              setData([...data, newData]);

              resolve();
            }, 1000)
          }),
        onRowUpdate: (newData, oldData) =>
          new Promise((resolve, reject) => {
            setTimeout(() => {
              const dataUpdate = [...data];
              const index = oldData.tableData.id;
              dataUpdate[index] = newData;
              setData([...dataUpdate]);

              resolve();
            }, 1000)
          }),
        onRowDelete: oldData =>
          new Promise((resolve, reject) => {
            setTimeout(() => {
              const dataDelete = [...data];
              const index = oldData.tableData.id;
              dataDelete.splice(index, 1);
              setData([...dataDelete]);

              resolve()
            }, 1000)
          }),
      }}
    />
  )
}

Demo of issue

So it looks like you are using the dateSetting incorrectly. It is an object, not a string: dateSetting: { locale: "en-US" }.. But even after I made those changes, I still had issues.
While this is an issue, we are currently refactoring this code to use Context. This is something we can fix for good in the refactor.
For now, if you change the columns object to below, it should work for you.
  const [columns, setColumns] = useState([
    { title: 'Date', field: 'date', type: 'date', dateSetting: { locale: "en-US", format: "MM/dd/yyyy" } }]);

Thanks for the help. It seems like you're right. I'm fine with closing this if you want to

Nice! Glad that fixes it for you.

So it looks like you are using the dateSetting incorrectly. It is an object, not a string: dateSetting: { locale: "en-US" }.. But even after I made those changes, I still had issues.
While this is an issue, we are currently refactoring this code to use Context. This is something we can fix for good in the refactor.
For now, if you change the columns object to below, it should work for you.
  const [columns, setColumns] = useState([
    { title: 'Date', field: 'date', type: 'date', dateSetting: { locale: "en-US", format: "MM/dd/yyyy" } }]);

It's not working form with type: 'datetime' sadly.


Correct behavior on window swap, right-click ready to use

Unfortunately it appears that we can't automatically resume mouse-lock state when hiding and showing the browser tab / window, but I did make a few tweaks to ensure state properly reset on hide. Right-click now does not show the context menu on the viewport. We can easily extend this to the entire window, but I thought it might be useful to be able to easily "inspect", as this is a teaching tool, in the right-side menu. I did this so that in the future the functionality could be added to right-click, like delete blocks when block tool is selected.

@jasonjmcghee I appreciate all your hard work. By the way, I've added you as a contributor so you can make changes to this repo directly. :-)

@cjdell I noticed! Thanks, but everyone makes mistakes, so I will probably always make PRs :)


Implementation in Jedis cluster, use slot to get HostAndPort

I am implementing the mset/mget command across slots in the redis cluster(JedisCluster for multiple keys, only execute if they all share the same connection slot).
I've tried to merge and forward by slot, but in the case of a small number of machines, there are too many slots on each machine (for example, 3 machines, 16384 / 3 ≈ 5460), so the efficiency of dividing keys by slot is too poor, so I need to divide them by IP:PORT.
But I can't get IP:PORT information according to key or slot, It is recorded in redis.clients.jedis.JedisClusterInfoCache#slots, so, I submit this PR.
import redis.clients.jedis.HostAndPort;
import redis.clients.jedis.JedisCluster;
import redis.clients.jedis.JedisFactory;

public class MyCluster extends JedisCluster {
    public MyCluster(HostAndPort node) {
        super(node);
    }

    public HostAndPort getHostAndPortFormSlot() {
        int slot = 1;
        return ((JedisFactory)connectionHandler.getSlots().get(slot).internalPool.getFactory())
            .getHostAndPort().get();
    }
}

@sazzad16  @gkorland Please review when you have time, I would appreciate any suggestions.

@yangbodong22011

JedisCluster already has MGET https://github.com/xetorthio/jedis/blob/5089cbd3e495232a5ae57dfb9bc32727fbbcf35d/src/main/java/redis/clients/jedis/commands/MultiKeyJedisClusterCommands.java#L26

Redis throws following ERROR for keys slotted to multiple hash slots even if those hash slots are allocated in same node.
 (error) CROSSSLOT Keys in request don't hash to the same slot

I don't see any purpose for the intention of this PR. Closing.

2. Redis throws following ERROR for keys slotted to multiple hash slots even if those hash slots are allocated in same node.

I understand, thank you for your reply.


sys/targets: fix tests when building on FreeBSD

gmake test is failing on FreeBSD since switching to clang.
To address this:

use g++ as the C preprocessor for now.
use a C compiler for compiling C sources and add -lc++ when
compiling executor.cc. Without this, clang warns about
using a C++ compiler for compiling C code.
some test configs add -no-pie, which is not used by clang.
Add -Wno-unused-command-line-argument to silence a warning
when test compiling, clang warns about remove_dir() in
executor/common.h. It wants static inline void remove_dir()
instead of static void remove_dir(). Silence this warning
by adding -Wno-unneeded-internal-declaration

Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

OK, gmake test now passed. gmake presubmit still has issues. Looking into it...

OK, gmake test now passes. gmake presubmit still has issues. One issue (the usage of gcc) is resolved by #1739.
The other one is related to the fact that I need to add -lc++ to the CFLAGS when compiling on FreeBSD. How do I do that? Right now in this PR I add -c++ to common compiler flags cflags of freebsd, but I think this is specifying the CFLAGS when compiling for FreeBSD , not on FreeBSD. It fixes compiling for FreeBSD on FreeBSD, but it is not correct. Any suggestions?
For getting make presubmit working, I also need to add -lc++ similar to -Wno-unused-command-line-argument, when compiling on FreeBSD for the test OS as a target.

Yes, we currently use a bit simplified model with some assumptions about the OS that does the build.
Strictly saying all of these parameters in sys/targets also depend on the host OS that does the build (e.g. if we try to build for Linux on Windows, it would probably look differently :)).
The simplified model is that we can use only 1 build OS for each target for now.
That's captured in osCommon.BuildOS. For freebsd it's not set, which means self-build: freebsd is only built on freebsd. So I think for now you may assume this (and capture any useful info for future generations in comments).
If we need more than 1 build OS, then plan was to make BuildOS an array of strings and then during target configuration when we form CFlags, etc we may look at runtime.GOOS (which is the current OS under us).

The last missing piece is to get golangci-lint running on FreeBSD. That is tracked in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244814.

Do I get it right that golangci-lint itself is not ported to FreeBSD yet?

OK, gmake test now passes. gmake presubmit still has issues. One issue (the usage of gcc) is resolved by #1739.
The other one is related to the fact that I need to add -lc++ to the CFLAGS when compiling on FreeBSD. How do I do that? Right now in this PR I add -c++ to common compiler flags cflags of freebsd, but I think this is specifying the CFLAGS when compiling for FreeBSD , not on FreeBSD. It fixes compiling for FreeBSD on FreeBSD, but it is not correct. Any suggestions?
For getting make presubmit working, I also need to add -lc++ similar to -Wno-unused-command-line-argument, when compiling on FreeBSD for the test OS as a target.

Yes, we currently use a bit simplified model with some assumptions about the OS that does the build.
Strictly saying all of these parameters in sys/targets also depend on the host OS that does the build (e.g. if we try to build for Linux on Windows, it would probably look differently :)).
The simplified model is that we can use only 1 build OS for each target for now.
That's captured in osCommon.BuildOS. For freebsd it's not set, which means self-build: freebsd is only built on freebsd. So I think for now you may assume this (and capture any useful info for future generations in comments).
If we need more than 1 build OS, then plan was to make BuildOS an array of strings and then during target configuration when we form CFlags, etc we may look at runtime.GOOS (which is the current OS under us).

OK. If we only build FreeBSD on FreeBSD, then this PR is OK.
The only cleanup one could do (if wanted) is to support a C and a C++ compiler. That way we could get away with the -lc++ dance. But that is a cleanup which can be done later.
Before that I would try to replace using g++ as a preprocessor by clang. But that is also a separate issue.
Any further changes suggested by you?

The last missing piece is to get golangci-lint running on FreeBSD. That is tracked in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244814.

Do I get it right that golangci-lint itself is not ported to FreeBSD yet?

The port I provided the pointer to is the necessary stuff to install it by issuing
sudo port install golangci-lint

So it is in the port collection. It does not seem to provide any real porting effort. So I would guess that it works. But my only go exposure is via this project, so I'm not an expert. I just tried to get gmake presubmit to work on FreeBSD without errors. When doing gmake -i presubmit the message about missing golangci-lint is the only one showing up. That is why I tried to install it and found that bug report.

Any further changes suggested by you?

Any further changes suggested by you?

No, looks good to me.

When doing gmake -i presubmit the message about missing golangci-lint is the only one showing up. That is why I tried to install it and found that bug report.

Maybe it makes sense to capture this knowledge in 'make install_prerequisites'? It could do necessary setup based on ${BUILDOS}. And/or in docs/freebsd/README.md.

make install_prerequisites is right now Linux specific, since it uses apt-get. I'll add it to the pkg install command  in docs/freebsd/README.md once the port is available. Can document that it is missing right now in that document later today.


operator cert-manager (1.16.1)

Signed-off-by: Richard Wall<EMAIL_ADDRESS>

/unhold

/merge possible

/merge possible


Message bodies are always NULL

Feature request or bug
Bug
If a bug, what did you expect to happen?
Get the body of an email using
$body = $message->message->text;
If a bug, what happened?
$message->message->text is NULL, but the body clearly exists in the object(s) when debugging (var_dump, print_r, etc.)
If a bug, list steps to reproduce bugs.
Try and access the "text" property on a message.
If a bug, did you do these steps?
[] Download and use the latest stable version
Yes
[] See if the issue has already been reported
Yes, there are similar issues, but they seem focused on base64 decoding.
[] Debug
Yes
If a feature request, what do you want to be added or changed?
If a feature request, is this feature already in a pull request?
If a feature request, do you know anyone who can help?
Side notes(Read then del this chunk)
It seems to come down to a problem in the getBody() method on the IncomingMessage class.
IncomingMessage.php:384
if(!is_object($obj) || !property_exists($obj, 'structure')) {
    continue;
}

Using property_exists on an object of type SubtypeBody which extends Section will never detect a property named "structure".  The property on the parent class Section is actually $_structure.  "structure" is a special property availble using the __get() method which property_exists will not detect.
This means every message will simply continue to the next section without ever setting a value to $obj->plain.  Which in turn means that is never decoded and assigned to $obj->text.  The message body properties are simply NULL ... always.
I tried changing it to look for property_exists("_structure"), but the same result occurred.  I think it has something to do with the fact the object is actually an extension of Section.  I'm not sure when class properties will be detected as existing when inherited from a parent.  Especially without having explicit __construct() methods.
I modified my local copy of the code to be like this below, and I instantly could access the email message bodies again.
if(!is_object($obj) || !$obj->__get('structure')) {
    continue;
}

I think that should work, because it looks like the verification is checking to make sue it is actually an object type, and the structure property exists ... which the result of __get() will reflect.  Feel free to patch it that way, or if there is a better way to write that code that I'm just not understanding.

I'm having the same issue.  Is there a planned fix for this?

I did a pull request with the fixed code, but It looks like it failed some build somewhere because of PSR formatting ... but that's not in the current master.  It's just a bunch of spaces added really.  I don't understand at all what's going on there.   I did the pull request ... so we'll see where that goes.

I have the same issue.

No.  It was a single line change on line 384 of the file IncomingMessage.php
if(!is_object($obj) || !property_exists($obj, 'structure')) {
becomes
if(!is_object($obj) || !$obj->__get('structure')) {

PLEASE ADD THIS TO THE COMPOSER.
UPDATED ON MY SITE BUT IF COMPOSER DOES AN UPDATE OR SOMETHING...

This is still not working.
When using $imap->incomingMessage->message->html/text/plain it always return null
When using vardump, body is there.


Rename ControlPlaneVersionsBundle to RootVersionsBundle

Our API doesn't contain a control plane version bundle. This method, used extensively throughout the code base, creates a little confusion so warrants a rename.

/approve

/lgtm


golang concurrency improvements

Using smaller integer size
Instead of allocating tagged post count slice each time, allocate one slice per worker thread and zero it with each new task
Reducing some other allocations
Removed branch in a for loop when counting tagged posts

Overall my results are much closer to rust rayon version now:
Running Go with concurrency
Benchmark 1: ./related_concurrent
Processing time (w/o IO) 6.947594ms
Processing time (w/o IO) 9.377195ms
Processing time (w/o IO) 6.417481ms
Processing time (w/o IO) 7.270459ms
Processing time (w/o IO) 7.082818ms
Processing time (w/o IO) 7.084531ms
Processing time (w/o IO) 7.056418ms
Processing time (w/o IO) 6.957182ms
Processing time (w/o IO) 7.204956ms
Processing time (w/o IO) 7.444545ms
Processing time (w/o IO) 7.835368ms
Processing time (w/o IO) 6.815176ms
Processing time (w/o IO) 6.613258ms
Time (mean ± σ):      26.2 ms ±   0.9 ms    [User: 93.0 ms, System: 11.2 ms]
Range (min … max):    25.1 ms …  27.6 ms    10 runs
Checking output
Output file: related_posts_go_con.json is valid!

Thanks for the PR, great work!


client/dbus: make Algorithm enum public under unstable feature

We need this change for server side implementation.
See: https://github.com/bilelmoussaoui/oo7/pull/56#discussion_r1482719151

thanks!


chore: update tests to use new SendPacket API

Description

closes: #2452

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (see CONTRIBUTING.md)
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Codecov Report

Merging #2567 (3fab6f6) into main (6927904) will increase coverage by 0.02%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2567      +/-   ##
==========================================
+ Coverage   78.74%   78.76%   +0.02%
==========================================
  Files         178      178
  Lines       12298    12298
==========================================
+ Hits         9684     9687       +3
+ Misses       2190     2188       -2
+ Partials      424      423       -1

Impacted Files
Coverage Δ

modules/core/04-channel/keeper/timeout.go
94.92% <0.00%> (+1.52%)
:arrow_up:


Remove .deb file after installation

Https:t.me/Lilymusicloud

@lilymusiCloud

@christianbundy thanks man


Pick up webdriver from PATH by default

Let selenium pick webdriver from PATH by default - in case of exception - locate_webdriver and use the helium supplied drivers

Said exception may occur in the following scenarios

Webdriver is not in PATH
Webdriver is on PATH but selenium is not able to access it (permission denied)
Webdriver does not match locally installed browser
In any of the above cases, helium will fallback to pre-supplied webdrivers (whether or through the separate package as discussed in #33 or through this root package).

If this fallback webdriver is missing, non-executable, or incompatible - an appropriate exception will be thrown and no more fallbacks will be present

The tests were all passing (tested for chrome) - though no additional tests have been added.
Should fix #33

 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.

@mherrmann Hi, could you review this PR and let me know if anything needs modifying?

I implemented this myself now and published it as release 3.0.5 on PyPI. Thank you for the PR!


MSFT_xSQLServerNetwork Set-TargetResource Question

Question: why is the TCPDynamicPorts parameter defined in the following way:
[Parameter()]
[ValidateSet('0', '')]
[System.String]
$TcpDynamicPorts,
Why set this as a string instead of a Boolean? Thanks

I imagine because zero (0) indicates dynamic ports are in use, and an empty string indicates a static port is in use when configuring this in SQL Configuration Manager.
Reference: Configure a Server to Listen on a Specific TCP Port
I think your point is valid though. It would seem more consistent with other DSC resources to use a Boolean operator to indicate the status.

When this resource was used to

When tests was created for this resource it was determined that it did not handle setting back to a static port. To resolve that at that time, without making a breaking, the '' was added and issue #534 was opened, which agrees this should be a System.Boolean.
@NikCharlebois If you like to help resolve this, please let me know in the other issue, and I lable that issue as in progress. Closing this since we are tracking this in the other issue.


fix(sdk-node): Fall back to secret key if no JWT key is set, per defaults behavior

Description
when verifying a session with the Node SDK, a JWT key is required. if no custom JWT key is set, Clerk falls back to the secret key. this change makes the SDK implement the stated default behavior

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[x] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Hi Jason 👋 Long time no see 😊
I've asked internally if this is the right change and it turns out that the default behavior described there is already happening:
https://github.com/clerkinc/javascript/blob/7636abc105c9436bc6ada93df3fa7da2b53ca340/packages/backend/src/tokens/verify.ts#L46-L60
The SECRET_KEY and API_KEY are related to authenticate with Clerk's backend API. jwtKey is for validating the session token JWT.
In that above flow the two keys are used on https://clerk.com/docs/reference/backend-api/tag/JWKS#operation/GetJWKS to get the jwtKey (since it doesn't exist).
Hope that makes sense! If something is not working as intended and that was the reason for the PR, please let us know. Thanks!

hey @LekoArts! yes, I had to make this change to get the code to work. without that env var, every session was reported as invalid
so I'm not sure where things are disconnecting, but something is misbehaving along the lines

@jlengstorf Ok, gotcha. Do you have an example/minimal reproduction at hand where I could see this behavior?
Was this part of this repo? https://github.com/learnwithjason/4d1a-productivity-tracker
I see that you changed implementation a bit

@LekoArts sorry I missed this reply. yeah, your team did a pretty extensive rewrite of how I was implementing this 😅


Anisotropic diffusion coefficient

Hi, thanks for this nice library.
I've been working on a Poisson equation with different diffusion coefficients by directions.
I believe it should be somehow included in a 2nd order tensor form.
Something like shown here;
https://fenicsproject.org/olddocs/dolfin/1.5.0/python/demo/documented/tensor-weighted-poisson/python/documentation.html
But I'm not sure how it's done in skfem.
Is there any example of this?

There is no example AFAIK, but it should be something along the following lines:
from skfem.helpers import *

@BilinearForm
def anipoisson(u, v, w):
    C = np.array([[1.0, 0.1],
                              0.1, 1.0]])
    return dot(mul(C, grad(u)), grad(v))

Oh yes,
This works with tutorial 1 just fine.
Thanks!


Tim select v1

Select
Install dependencies by npm i

Note - no new dependencies in this component from main

The select component works as a dropdown list in which the user can select one item in the rendered options list passed as a property.
When an option is selected the component will emit a change event back to the parent with the value. In order to handle the emit, add a @change to the component.
While the options list is open - and the component is selected - the user can search the options in the options list by typing on the keyboard and the component will focus an option that it finds. Every 2.5 s the query variable will be reset and a new search can be done.
Features -

Storybook
Unit tests with Vitest

How to use -
Properties
name - type - example

label - string - 'Countries'
position - string - 'top'

Note - Acceptable values are 'top' and 'inside'. Default value is 'top'

sort - boolean - true

Note - Sorts the array alphabetically by the text value

defaultoption - string - 'Choose item'

Note - Defaul value is '-- Choose an option --'

options - array of objects - [{id: 'id-1', value : 'value-1', text : 'Item 1'}]

Note - The array must follor the type {id : string, value : string, text : string}[]

How to use
<foam-select
    label="countries"
    sort
    defaultoption="Select a country"
    :options="[countryArr]"
    @change="handleCountry"
/>

Added feature sort order
New property added sortorder, type string
How to use
The sortorder prop only works if sort is added as well.
Acceptable values are ascending and descending

Ascending sorts A -> Z
Descending sorts Z -> A

Default value is 'ascending' and if an unacceptable value is passed - it will be default to 'ascending'.

<foam-select options="[optionsArr]" sort sortorder="descending" />

Tab trap should be working correctly now.


Add dual of mandatoryIvyDeps for runtime (and compile-time) deps

I think the new JavaModule.mandatoryIvyDeps opens convenience for various modules, e.g. in AspectJ we always want to add a runtime lib.
I propose to introduce mandatoryRunIvyDeps and maybe also mandatoryCompileIvyDeps in JavaModule. WDYT?
Originally posted by @lefou in https://github.com/com-lihaoyi/mill/issues/1487#issuecomment-925779704

It's probably not needed.


Docs notebooks generate errors

The notebooks in the documentation generate errors. See, for example, this link

There are also several latex errors that need to be fixed

The link is broken (error 404). Is this issue still relevant?

Not anymore. Let's pay attention when we create new notebooks for this.


Switch to cmux so we can use HTTP and gRPC on single port

The idea is to use https://github.com/soheilhy/cmux so we can serve HTTP(S) and gRPC on the same port.
This could simplify things as we won't need multiple ports for every component.

Let's focus on Pros & Cons.
Does it really help to simplify deployment, is it a big deal to expose a new port internally? How? Let us know, it's definitely not a problem for docker or K8s user AFAIK, but would love to hear feedback from other users as well.
The Cons is big as it blocks the scenario when you want different certs/TLS/auth/loadbalancing per different port. By having all on the same one, we basically drops that ability.


Tracked exceptions not showing up in portal

I've added the insights sdk to my code in order to attempt to track errors in my code for function apps. I can't use the default method of tracking failures for function apps (passing the error to context.done(error)), because that interrupts the HTTP response the function is supposed to give.
However, the exceptions do not show up in my insights instance. I assume the configuration is correct, since my custom events are showing up (although not associated with the actual request...is that supposed to happen?)
The test function I'm using:
module.exports = function (context, myTimer) {
    const appInsights = require("applicationinsights");
    appInsights.setAutoDependencyCorrelation(true);
    const client = appInsights.getClient();
    client.trackException(new Error("handled exceptions can be logged with this method"));
    client.trackEvent('custom event');

    context.log('JavaScript timer trigger function ran!');
    context.done();
};

I don't know whether this is a bug in the SDK or in the portal. Errors passed to context.done() are properly marked as exceptions in the portal.

In a quick test against the latest version of the SDK, this small sample seems to work
var appInsights = require("applicationinsights");
appInsights.setAutoDependencyCorrelation(true);
var client = appInsights.getClient("ikey");
client.trackException(new Error("handled exceptions can be logged with this method"));

Perhaps you are running into a problem with your function app ending before the telemetry is sent? You can try using this instead of context.done() : client.sendPendingData(()=> context.done())
This will ensure you don't end the request until all pending telemetry is sent.
As for custom events being associated with your request. In ideal circumstances they should, but there are cases where we can't make correlation work (depending on what libraries you have in your system). For this simple example, you wouldn't have correlation because there is no server request (a req/res pair as generated by http.createServer) to make a request telemetry item to pair against. You might not make these directly in function apps, so #148 may be an issue as far as making request telemetry goes.

Thanks for your answer. First of all, a little context that I probably should have provided beforehand: I am running this code on Azure Functions, with the function app hooked up to Azure Insights as well.
Turns out exceptions were actually reaching insights, they were just not being associated with the request (just like events). I didn't think this was the problem since there wasn't a link to an events list in insights, but there was a link to exceptions. My apologies for that.
However, the association issue still stands. Perhaps this is not the proper thread to discuss it, but I'll just quickly put down my thoughts:

All traces (logging to the Azure Functions environment, exceptions logged by Azure Functions) are nicely put together and encapsulated in 1 "Insights request". So how come function calls to the SDK cannot be correlated? You know when a new client is created or a new instance has been setup (through the getClient() and setup() methods), so couldn't you treat any function call following as a single request, if no other method is available (i.e. no linking between request response objects)?
The issue you linked isn't entirely relevant, in my opinion. The author there is working with websockets, which implies some sort of persistence in the server, whereas in Azure Functions there is no persistence at all. I create a new instance of the SDK for every request.
Most of our Azure Functions are HTTP request based, with at least a request object available. The response object is probably in a different format from what you expect, since the full response is only generated by the Azure Functions runtime, after the Azure Function is finished. Could there be a way to emulate the request and response objects used by the SDK to recognize a request?

Thanks for the follow up! I linked #148 not because of similar situations, but because a resolution is the same - a way to track requests without a req/res pair.
As for why they cannot be correlated, we simply don't currently support automatic request collection for anything but the standard node server. Our correlation logic also correlates on requests, so without an automatically generated request context, or a manually generated one, you have no correlation.
Your suggested solution "so couldn't you treat any function call following as a single request, if no other method is available " is interesting, but presents some issues. For example, it is a perfectly valid use case to use this SDK outside of a server context (eg, a desktop app using node like VSCode or Electron apps in general). In this situation, assuming a correlation context merely from the lack of requests could be unexpected behavior.
This all said, because you have a single client for each request, you can work around this for your particular use case with a telemetry processor. Code like the following may work for you (make sure it's done before recording any telemetry):
var correlationId = Math.random().toString(36).substr(2, 10);
appInsights.client.addTelemetryProcessor((envelope) => {
     envelope.tags = envelope.tags || {};
     envelope.tags['ai.operation.id']  = correlationId;
});

We can look into creating an emulated response object if this workaround isn't working out right - though the real solution is for us to stop requiring one to make request telemetry.

@OsvaldoRosado that was a great suggestion! Using the invocationId from the function app (context.bindingData.invocationId), I've been able to link custom telemetry to output traces from the functions environment. Now everything's showing up in 1 beautiful set of debugging data. Thanks!
Is there any documentation on what other tags are available? And can I make my own? Assuming I can search on tags in insights (which I haven't been able to figure out...yet), it would even allow me to (manually) correlate events between requests.
Our function apps often send requests to eachother, so being able to track a whole chain throughout multiple apps using a tag or something similar would be amazing.
Do you know of any mechanism to do so?

Custom properties are indeed what you're looking for. These tags are searchable as well, but not intended for generic use. These tags get transformed into other fields by our backend and you can read their values in details blades (after clicking the ... at the end of the properties grid) in the portal, or as raw data to query against in Analytics.
As for this:
Our function apps often send requests to eachother, so being able to track a whole chain throughout multiple apps using a tag or something similar would be amazing.
This would work out of the box if we had proper request tracking working in Function apps. As a workaround, you can use custom properties to recreate something close like you mention and then correlate with some hand built Analytics queries (or Metrics Explorer may be able to do this too).
If your function apps all share the same ikey, it may not be too difficult to do this in a way the Portal UI will recognize rather than rolling your own properties to do it. You'll need to use the tags ai.operation.id, as well as ai.operation.parentId, and have a way to pass this data across to your next function app (the SDK uses headers to do this). The idea is that the first function app determines the operationId that should be recorded in the telemetry for the entire chain, and then parentId is always set as the id of the current request. (There's more complication here if we had request telemetry - the parentId of the request telemetry should be the id of the service that called into it).
Once #148 is addressed, you wont need to do any of this - just call trackRequest at the beginning of your code. Then the Portal buttons for "all available telemetry for this root operation" or "external Application Insights dependency for this request" (if using different ikeys in each app) should show the data you're looking for.

I don't entirely follow you yet. So there are two tags: ai.operation.id and ai.operation.parentId. Currently, I'm setting ai.operation.id to the invocationId in order to correlate my own events, exceptions and tracing to the telemetry and tracing generated by the AF version of Azure Insights (the built in one). I am not using operation.parentId yet.
If I understand you correctly, I should now be setting operation.parentId to the invocationId, and set operation.id to an idea that identifies a set of requests across functions? To me, it makes more sense the other way around, given the names of the tags.
Also: should this be included in the documentation for the SDK(s)? It seems to me like this could help more people achieve what they want to do. I assume it's designed to be used by our code, not just the SDK (since you're suggesting it), so it would be useful if we didn't have to bother you guys in order to figure these things out. Will leave you more time to develop awesome features :)

To me, it makes more sense the other way around, given the names of the tags.

I understand the names are confusing and seem backwards :smile: Essentially id is the identifier for the entire operation (cross-service) and parentId is the identifier for the direct parent of the telemetry in question (since you have all dependencies, the parent is what the id of the request telemetry would have been if you could collect it - invocationId is a good stand-in)
Internally when you don't provide a parentId, we set it the same as operation.id, if that helps clarify why the code sample I gave before works.
These tags are documented in the endpoint docs for the service overall ( https://github.com/Microsoft/ApplicationInsights-Home/blob/master/EndpointSpecs/Schemas/Docs/ContextTagKeys.md ). Their definitions are also included in our typescript typings. Look at the properties on new appInsights.contracts.ContextTagKeys() to see them.
We don't typically provide complete code examples on rolling your own for this because correlation gets surprisingly complex - especially when you want to coordinate cross-sdk or cross-ikey. In the majority of cases the SDK will handle this correctly for you. I suggested using these tags in your case because you happened to have a simple enough scenario where it would be the same amount of work as using your own custom properties.
Hope this helps!

The names do indeed seem backwards, but thanks to your explanation I understand them now.
I've got the correlation working the way I want to now, except for one small detail, but I don't believe that's fixable. I would like the requests in application insights to be associated with the operationId as well, however since they're generated by the Azure Functions runtime I have no way of accessing their tags. I assume this is impossible for me to fix right now, since I only know the operationId once my function run has already started.
However, thank you so much for your help. You've helped me understand a great deal and achieve what I wanted, within the bounds of possibility. I look forward to seeing what kind of improvements you guys bring in the next couple of months!

Schema now at: https://github.com/microsoft/ApplicationInsights-Home/blob/master/EndpointSpecs/Schemas/Bond/ContextTagKeys.bond


Updated Day-60 work

 Updating Day-60 work [Sathyan Madhavan]

 Updating Day-60 work [Sathyan Madhavan]


Change endpoints to be compatible with stellate

@Razzmatazzz We good now, thanks @GrantBirki

.deploy

.deploy


Cannot configure oauth2_client from env

Description
I'm provisioning an OAuth2 (authentik) client using env variables in the docker compose file.
Here is the complete env variables I'm passing to the container :
 - GITEA__ENABLE_AUTO_REGISTRATION=true
 - GITEA__SECURITY__INSTALL_LOCK=true
- GITEA__openid__ENABLE_OPENID_SIGNIN=false
- GITEA__openid__ENABLE_OPENID_SIGNUP=false
- GITEA__service__ALLOW_ONLY_EXTERNAL_REGISTRATION=true
- GITEA__oauth2_client__ENABLE=true
- GITEA__oauth2_client__ENABLE_AUTO_REGISTRATION=true
- GITEA__oauth2_client__REGISTER_EMAIL_CONFIRM=false
- GITEA__oauth2_client__PROVIDER_NAME=Authentik
- GITEA__oauth2_client__CLIENT_ID=<REDACTED>
- GITEA__oauth2_client__CLIENT_SECRET=<REDACTED>
- GITEA__oauth2_client__ISSUER_URL=https://auth.tld/application/o/gitea
- GITEA__oauth2_client__AUTO_DISCOVER_URL=https://auth.tld/application/o/gitea/.well-known/openid-configuration
- GITEA__oauth2_client__USE_ADMIN_GROUP=true
- GITEA__oauth2_client__OPENID_CONNECT_SCOPES=profile,email
- GITEA__oauth2_client__ACCOUNT_LINKING=auto
- GITEA__oauth2_client__USERNAME=preferred_username

These variable correclty populates the app.ini.
However I don't see the "Sign it with Oauth" button on the homepage.
What do I miss in my configuration ?
Thanks
Gitea Version
1.22.1
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots

Git Version
No response
Operating System
No response
How are you running Gitea?
docker-compose
Database
MySQL/MariaDB

You should add Authentication Source in admin panel.

So no way to define this in a headless way ? Is env-to-ini not working ?

Actually, I can not found some settings like PROVIDER_NAME, ISSUER_URL.... in oauth2_client
Where did you find them?
The usable settings are here: https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini#L1552

I could do it by modifying the docker file to add it via CLI though

If you only want to add the oauth2 source, it will only work on the existing instance. as DB needs init first.
So for a new one, you should init the instance first, and of cause, this can be done by CLI.

Anyway, authentik is just a standard OpenID provider, it should work ;)

I think so. But maybe you need more settings in app.ini.
I didn't try it, maybe others can give you more advices.

I don't recall where I found them.
Anyway, I ended up writing a python script to run the command afterwards.
For others having the same issue, here is the snippet:
#!/usr/bin/env python3

import docker
import time

# Get container by name
def find_container_by_name(client, container_name):
    # List all containers (including stopped ones)
    containers = client.containers.list(all=True)

    # Find container by name
    for container in containers:
        if container_name in container.name:
            return container
    return None

# Run command in container
def run_command(container, command):
    # Wait until the container is running
    while container.status != "running":
        print(f"Waiting for container '{container_name}' to be ready...")
        time.sleep(2)
        container.reload()  # Refresh container status

    print(f"Container '{container_name}' is running.")

    # Run the command inside the container
    exec_result = container.exec_run(command)
    print(f"Command output: {exec_result.output.decode('utf-8')}")

# Run the command to configure the OAUTH inside Gitea.
# This can only be done via a CLI inside the container.
# Initialize Docker client
client = docker.from_env()

# Find container by name
container_name = "gitea-server"
gitea_container = find_container_by_name(client, container_name)
if gitea_container is None:
    print(f"Container '{container_name}' not found!")
    exit

command = """
su -c "gitea admin auth add-oauth --name Authentik \
--provider openidConnect --key """ + client_id + """ \
--secret """ + client_secret + """ \
--auto-discover-url """ + autodiscover_url + """ \
--icon-url """ + icon_url + """ \
--scopes profile,email" git
"""

run_command(gitea_container, command)

Maybe it could be good to have the feature to provide the DB from the config file, to allow for a headless configuration of the service with env variables.


Improve documentation

It seems the documentation is not good enough because I see people struggling to install the plugin, suggesting a Loom end-to-end, especially Templater configuration is difficult to understand at first.

duplicate


Future Plan: taxi and shared mobility

Currently, a vehicle in UXsim just travel from A to B and disappear. This is like a private owned vehicle.
In the future, in order to model taxi and shared mobility, specific vehicles can travel through a network by passing through specific nodes that are dynamically updated.

Would love this feature!

This feature would actually be quite useful for me, is there any way I can help with it. Have you any thoughts on how the implementation should look on a high level?

This is my next plan.  The vehicle behavior part involves modification of the simulation core logic, so I will do it by myself.
On the other hand, vehicle-passenger matching is also important for this feature. I think I will release very naive implementation first (as a submodule). It would be great if you can develop simple yet efficient implementation.

Awesome! Really looking forward to playing with it!


GVM dependency analysis performance fixes

Rewriting the GVM dependency analysis for better performance.
GVMDependencyNodes are created whenever there is a RuntimeMethodHandle/ShadowConcreteMethodNode/MethodCodeNode created for a GVM.
GVMDependencyNodes now report static dependencies: each GVMDependencyNode will report its target method entrypoint [and ShadowConcreteMethodNode] if it is not abstract and passes constraint validation.
The list of types interesting for GVM analysis is now reduced to only the types that override GVMs of base types, or that implement GVMs of interfaces they directly implement (otherwise, we use GVMDependencyNodes to track GVMs).
The GVM dynamic instantiation expansion propagates from GVMDependencyNodes to any GVM on types that inherit from the containing type of the GVM associated with the GVMDependencyNodes (top to bottom only).
Finally, the analysis is performed based on type castability/equality between base types and derived types (or types and their implemented interfaces). Previously, this was done based on castability/equality of their canonical forms, producing way more GVM instantiations that really needed.
Fixed a couple of corner cases missed by the previous GVM analysis logic: replaced incorrect logic of virtual method resolution by calls to more correct TypeSystem APIs.
Re-introduced the previously existing and now broken GVM resolution logging at runtime.
ASP.Net benchmark: previously GVM analysis took more than 50% of execution time. Now it's down to 0.8%. Total compilation time using Release build down from 2:06 mins to 40 seconds (now the majority of execution time is spent writing the obj file and in JIT).

@davidwrighton PTAL

cc @nattress @sergiy-k @MichalStrehovsky

Could you also unblock the tests in CoreCLR.issues.targets that you're fixing so that we don't forget/regress it?

Yes. Thanks for reminding me.


[Doc Improvement][Support deep links to chat messages][2529296]

Added content for deeplinks to chat messages in Teams.

Docs Build status updates of commit b40ea7d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
93
22
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 75e9752:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
94
21
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 53e1b8b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
94
20
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit fc5814c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
92
30
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 7b67edc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
92
31
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 6625484:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
92
31
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 68cfe82:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
92
31
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 4643108:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
92
31
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 58a8a1f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
92
31
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 4fcbd4b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
93
26
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 387440e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
94
22
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit fca4f34:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
94
22
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 5e98e65:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
95
16
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit e8622fc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
95
16
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 2de8685:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/build-and-test/deep-links.md
95
16
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 925137f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Unit tests delegation transition [wip]

Issue Number
#1386
Overview

718f931ef53846a325b816a09169adb927b987be
expose guardQuit and guardJoin for unit testing

5d39855aee45220c5878aa12f05216644ee7ff75
Further next/active delegation tests

Comments
I have cherry-picked integration tests from #1374 on top of 718f931ef53846a325b816a09169adb927b987be. There are following integration tests (all are passing). The ones tagged TO_REMOVE can be translated to unit tests or property I think. I think that first two should stay as they are testing e2e integration.
STAKE_POOL_NEXT_01 - Can join/re-join another/quit stake pool
STAKE_POOL_NEXT_02/STAKE_POOLS_QUIT_01 - Cannot quit when active: not_delegating

TO_REMOVE - STAKE_POOL_NEXT_02 - Override join with join in the same epoch => delegating to the last one in the end
TO_REMOVE - STAKE_POOL_NEXT_02 - Override join with quit in the same epoch => not_delegating in the end
TO_REMOVE - STAKE_POOL_NEXT_02 - Override quit with join in the same epoch => delegating to the last one in the end
TO_REMOVE - STAKE_POOL_NEXT_03 - Join and quit in two subsequent epochs => delegating in epoch X + 2, not_delegating in epoch X + 3
TO_REMOVE - STAKE_POOL_NEXT_03 - Join 2 in two subsequent epochs => delegating to 1st in epoch X + 2 and 2nd in epoch X + 3
TO_REMOVE - STAKE_POOL_NEXT_04 - Cannot quit when most recent delegation next: not_delegating
TO_REMOVE - STAKE_POOL_NEXT_04 - Cannot quit when 'next 1': not_delegating, 'next 2': not_delegating
TO_REMOVE - STAKE_POOL_NEXT_05/STAKE_POOLS_JOIN_01 - Cannot join A, when active: A
TO_REMOVE - STAKE_POOL_NEXT_05/STAKE_POOLS_JOIN_01 - Cannot join A, when 'next 1': A and there is no 'next 2'
TO_REMOVE - STAKE_POOL_NEXT_05/STAKE_POOLS_JOIN_01 - Cannot join A, when 'active' : A, 'next 1': B and 'next 2': A

bors try

In the end I have left 4 integration tests:
STAKE_POOL_NEXT_01 - Can join/re-join another/quit stake pool
STAKE_POOL_NEXT_02/STAKE_POOLS_QUIT_01 - Cannot quit when active: not_delegating
STAKE_POOL_NEXT_02 - Override join with join in the same epoch => delegating to the last one in the end
STAKE_POOL_NEXT_03 - Join 2 in two subsequent epochs => delegating to 1st in epoch X + 2 and 2nd in epoch X + 3

The rest should be covered by unit tests and two properties: https://github.com/input-output-hk/cardano-wallet/pull/1392/commits/f617302842774bc87bcf6559ec68cd4306f11447

bors r+

I hope it is going to spark initiative to move also other parts that reside now on integration test

I think that whenever it is possible and makes sense we should do it. That also requires writing code in a way that it is feasible to test reliably and exhaustively on unit level. I think that ideally integration tests should not be testing many specific cases for particular requirement but just a few e2e scenarios to make sure that integration of all components works fine.


مشكلة في جهازي انا بسبب حذف بعض البرامج الاعتمادية

قمت بحذف بعض الاعدات ونزلت الكونفج مره اخرى لكن هناك خطا ما
الالوان تظهر هكذا

هذا هو الـ log الخاص ب age
 ags

(com.github.Aylur.ags:2342): Gjs-Console-WARNING **: 15:07:40.636: Window.popup is DEPRECATED. the click away functionality depends on a bug which was patched in Hyprland and it never worked on Sway anyway. to close on the esc key use self.keybind("Escape", () => App.closeWindow("window-name"))

(com.github.Aylur.ags:2342): Gjs-Console-WARNING **: 15:07:40.943: passing the config object with default export is DEPRECATED. use App.config() instead

(com.github.Aylur.ags:2342): Gjs-Console-WARNING **: 15:07:40.944: cacheNotificationActions config option has been removed: use Notifications.cacheActions instead
SyntaxError: JSON.parse: unexpected character at line 3 column 16 of the JSON data
SyntaxError: JSON.parse: unexpected character at line 3 column 16 of the JSON data
SyntaxError: JSON.parse: unexpected character at line 3 column 16 of the JSON data
SyntaxError: JSON.parse: unexpected character at line 3 column 16 of the JSON data

(com.github.Aylur.ags:2342): Gjs-CRITICAL **: 15:07:50.186: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
The offending signal was destroy on Ags_Label 0x650ffb9e1cb0.
== Stack trace for context 0x650ffb635150 ==
#0   650ffb6fcc38 i   resource:///org/gnome/gjs/modules/core/overrides/GLib.js:266 (f316147c420 @ 139)

(com.github.Aylur.ags:2342): Gjs-CRITICAL **: 15:07:50.188: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
The offending signal was destroy on Ags_Label 0x650ffd27f080.
== Stack trace for context 0x650ffb635150 ==
#0   650ffb6fcc38 i   resource:///org/gnome/gjs/modules/core/overrides/GLib.js:266 (f316147c420 @ 139)
SyntaxError: JSON.parse: unexpected character at line 3 column 16 of the JSON data
SyntaxError: JSON.parse: unexpected character at line 3 column 16 of the JSON data
SyntaxError: JSON.parse: unexpected character at line 3 column 16 of the JSON data
SyntaxError: JSON.parse: unexpected character at line 3 column 16 of the JSON data
SyntaxError: JSON.parse: unexpected character at line 3 column 16 of the JSON data

جرب التحديث الجديد
تم اضافة ثيمات Kvantum واعتمادها لتطبيقات qt6

المشكلة اتحلت بعد تطبيق Kvantum


Update readme.

Make CodeIgniter website references use https, and update the IRC link to the freenode page.
Signed-off-by:Master Yoda<EMAIL_ADDRESS>

I checked, and yes, freenode can take advantage of https.
I did not put https for the forum ... it breaks the retrieval of assets.
I think there might be one more place I have to change inside the forum before that will be a go.

Should the Github description be updated as well?

Also, I noticed every file referenced a link of the user guide, which still uses http. I wonder if they should be updated. I am willing to do the work if it is a need.

@zhanghongyi You are correct! Global serach & replace should fix that - I have updated my PR.

The webchat link was the only thing worth modifying and now I have to use Ctrl+F to find it ...


WACI flow diagram needs updating

The flow diagram in the WACI context should be updated to match the existing examples and flow of the spec.

https://swimlanes.io/d/C5HnpvA4f
feel free to apply changes directly to the source and PR in new versions without me in future WG meetings

ack tried recreating in mermaid mode and don't have the time this week, will just PR in a PNG for now, will try again on V1 timeline.  would rather have something in before review at CCG and/or interop WG

PR was added, but rendering is currently broken.

looks like rendering is working. Closing.


feat: windows support and example

Fixes issue with the windows compiler choosing the right ver
Fixes int64_t include on windows
Added very basic example (cargo run --example union)

Closes #1

Thanks for the merge request! It still builds fine on my Linux machine as well.
Nice with the example as well. I have been meaning to add more examples using macroquad and with screenshots, but had not gotten around to it yet.
As you probably noticed the Polygons/Polygon/Vertex structs are quite verbose to create. Maybe for example improving the From impls and removing the Polygons struct and rely on only Vec instead somehow to make it as easy as possible to contruct each Polygon.
Any suggestions for improvements are welcome.

As you probably noticed the Polygons/Polygon/Vertex structs are quite verbose to create. Maybe for example improving the From impls and removing the Polygons struct and rely on only Vec instead somehow to make it as easy as possible to contruct each Polygon.

You can make it more versatile and easier to construct by using impl Iterator<Item = T> (or IntoIterator), impl Into<T> or even impl Iterator<Item = impl Into<T>> as constraining it to a vec is a bit clunky at times.


add region in resources resolvers

Add  AWS::Region in ref of resource resolvers to allow cfn-resolver-lib to map Availability Zones through FnGetAZs.
Closes https://github.com/bboure/serverless-appsync-simulator/issues/55

I published v0.8.1 which includes this fix.
Thanks again


Use Atmosphere engine migrations in project using Atmosphere

See http://pivotallabs.com/leave-your-migrations-in-your-rails-engines for details.
For vph, plgrid and exp dedicated sql script which removes copied atmo migrations numbers from schema table and add origin numbers need to be created and performed before pushing this change.
This change requires dependent projects to remove old migration timestamps from DB and add original atmosphere migration timestamps.
Below is the status of dependent projects preparation for this change:

[x] https://github.com/VPH-Share/atmosphere-vph/pull/10 vph (responsible @mkasztelnik)
[ ] plgrid (responsible @tbartynski)
[ ] exp (responsible @mkasztelnik)

@dice-cyfronet/atmo-dev-team please take a look

@mkasztelnik Maybe it's just me but while I understand the basic concept I don't really know what rake task I'm supposed to run, when and where. Linking a devblog is not a substitute for documentation. :)
So:

I have a vphshare checkout, a plgrid checkout and an atmosphere checkout. I can write my own SQL scripts to purge the imported migration numbers from my DBs but once I do that, how do I install any new migrations? Do I need to run db:migrate in my wrapper project dir or in the Atmosphere dir?
How do I manage interleaved migrations? I assume I will need to configure my wrapper projects to look for migrations in Atmosphere's db/migrate dir, but how do I accomplish that?

I described update procedure in this PR for vph deployment https://github.com/VPH-Share/atmosphere-vph/pull/10.  The most crucial thing is to update schema_migration versions before executing rake db:migrate.
To prepare rake script for other project it is enough to invoke this in your bash:
for f in `ls /path/to/other/deployment/db/migrate | grep atmosphere`
do
echo `echo "$f" | cut -d'_' -f1`
done

and update this part of rake task with printed timestamps.
The beauty of this solution is that you don't need to install any new migrations :smile:, rails migration path will be extended and automatically all atmosphere migrations will be added.
According to interleaved migrations: everything is fine here since atmosphere migrations have earlier timestamps than e.g. vph project migrations. And you don't need to configure anything. It is done automatically thanks to  this initializer. It extends path where project which mount atmosphere is searching migration files. As a conclusion migrations from project/db/migrate and atmosphere/db/migrate are used.

Aaa one more thing: mentioned rake task is valid until new migration is added into atmosphere master. In such a way rake task need to be updated.

@tbartynski, @nowakowski I created 3 separated branches for vph, exp and plgrid - we should coordinate deployment in these 3 projects. Is 20.04.2015 (next Monday) OK with you?

@mkasztelnik Affirmative.

I think this PR should not have a ready for review label since we don't really review the code. It should have a ready-for-test label.

:+1:

This PR was already deployed into ismop and vph-dev environments.


npm run dev gives "Cannot GET /"

After I followed all install instructions (using node v.4.47 and v.7.20, same for both) I run npm run dev and all looks green (web pack saying webpack: bundle is now VALID).
When opening http://localhost:4000 in a web browser I get "Cannot GET /".
On MacOS Sierra.
No to JSX support vue-cli config.
Yes to electron in vue-cli config.
Any pointers?
I've tried to remove node_modules and run installation again, with the same result.

It works as expected when not adding electron support on the vue-cli config.

Sure, just don't open http://localhost:4000 then, since you're building an electron app.

Oh, npm run dev is not supposed to work when electron support is enabled?
That should be more clear in the README then, since that's how I interpret it here: https://github.com/egoist/vuepack/blob/master/docs/electron.md

I've enabled the html output for Electron mode in dev server, but you'll still get a require is undefined error. doc has been updated for this.


Daily recompute power

What do you think about this version ?
For the arg (when I do -h), it shows :
usage: compute_power.py [-h] [-d]
optional arguments:
-h, --help   show this help message and exit
-d, --daily  By adding this argument, the script will recompute
yesterday's power data for each house in the database.


Frontend: Send coins using jQuery and Ajax

If we use jQuery and Ajax, we can send coins using the correct HTTP method and Content-Type.
The frontend now shows a validation message below the input field, depending on the given address.

1st commit pair-programmed w/ @ferencdg
Fixes #106

Requesting @hewison-chris for review :)


Updated the installation guide

Modified the Installation Guide to be more accurate and updated the pictures

Looks good! Tested by team Machester

Looks good!


Run reading hooks on Table.bulkGet

Fire the reading hooks on the results of Table.bulkGet, as in Table.get.
This fixes the problem where Table.bulkGet results don't match Table.get results when Table.mapToClass is in effect. (mapToClass leverages the reading hook.)
Fixes #1079

Thanks a lot! 👍


JSON, wrong number of arguments (given 0, expected 1+)

#<ArgumentError: wrong number of arguments (given 0, expected 1+)>
  /app/vendor/ruby-2.3.1/lib/ruby/2.3.0/json/common.rb:467:in `JSON'
  /app/vendor/bundle/ruby/2.3.0/gems/librato-metrics-2.0.0/lib/librato/metrics/persistence/direct.rb:21:in `block in persist'
  /app/vendor/bundle/ruby/2.3.0/gems/librato-metrics-2.0.0/lib/librato/metrics/persistence/direct.rb:20:in `each'
  /app/vendor/bundle/ruby/2.3.0/gems/librato-metrics-2.0.0/lib/librato/metrics/persistence/direct.rb:20:in `persist'
  /app/vendor/bundle/ruby/2.3.0/gems/librato-metrics-2.0.0/lib/librato/metrics/processor.rb:34:in `submit'

started happening when upgrading to 2.0.0

Thanks for the bug report, @chancefeick assume you're taking a look at this?

Patched in 2.0.1 (#123). Thanks for the report, we've added 2.3.1 to our build matrix as a result.


add Simplified Chinese(zh-CN) translation for ValidationMessages.

Hi Brock, I've added zh-CN resource file for ValidationMessage.cs, I hope this could help.
Thanks,
Cheng

ok, thanks!


cargo-1.58.0 - build problems

Hi! Thank you for this amazing overlay.
I am having trouble lately with building the 1.58.0 toolchain with it.
This is the error, that I am getting:
nix log /nix/store/gjlydwwdlfqmd59ksng7ha2k7h7bh2lv-cargo-1.58.0-x86_64-unknown-linux-gnu.drv
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/b4dg6532dfg1grk3949z6xgcvl6fcxz6-cargo-1.58.0-x86_64-unknown-linux-gnu.tar.xz
source root is cargo-1.58.0-x86_64-unknown-linux-gnu
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file cargo-1.58.0-x86_64-unknown-linux-gnu/version
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
@nix { "action": "setPhase", "phase": "installPhase" }
installing
Installing component cargo
@nix { "action": "setPhase", "phase": "fixupPhase" }
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/9mpy78rkzx5h7q5q7mwj3hp3gzxnvjcb-cargo-1.58.0-x86_64-unknown-linux-gnu
shrinking /nix/store/9mpy78rkzx5h7q5q7mwj3hp3gzxnvjcb-cargo-1.58.0-x86_64-unknown-linux-gnu/bin/cargo
shrinking /nix/store/9mpy78rkzx5h7q5q7mwj3hp3gzxnvjcb-cargo-1.58.0-x86_64-unknown-linux-gnu/libexec/cargo-credential-1password
gzipping man pages under /nix/store/9mpy78rkzx5h7q5q7mwj3hp3gzxnvjcb-cargo-1.58.0-x86_64-unknown-linux-gnu/share/man/
patching script interpreter paths in /nix/store/9mpy78rkzx5h7q5q7mwj3hp3gzxnvjcb-cargo-1.58.0-x86_64-unknown-linux-gnu
checking for references to /build/ in /nix/store/9mpy78rkzx5h7q5q7mwj3hp3gzxnvjcb-cargo-1.58.0-x86_64-unknown-linux-gnu...
automatically fixing dependencies for ELF files
/nix/store/sds4msgr38nfs2zg3fsrd54wv8sndlyx-auto-patchelf-hook/nix-support/setup-hook: line 220: -l: command not found

Maybe it is also an issue with my setup?
It has been happening now in two different environments for me:
Here is an example: https://github.com/a-kenji/zellij-nix/runs/6046299076?check_suite_focus=true#step:5:424

Duplicate of #83

Oh, my bad! I didn't realize they were the same issue, thanks!


Document garbage collection

@joaofnfernandes commented on Tue Aug 30 2016
As a DevOps, I noticed that my disk space is increasing without bounds, and I want to be able to do something about it.
We already have docs for the open-source registry garbage collection, but that's not enough.
Also, document that the garbage collection scheduler is in UTC as described in #2473

@sarahpark commented on Tue Aug 30 2016
Thank you for including a user story (thus a purpose) for a ticket 🙌 👏

fixed


Detect/report on redirect loops

Currently, if a redirect loop is hit while using -fw then gobuster spins a few times, then returns the following (at least if it's on the initial/base URL):
[-] Unable to connect: https://example.com/somepath/

https://github.com/OJ/gobuster/blob/7a6d1c068e3e89ee9b3c0c01cb3946957143a0c9/main.go#L412
Looking at my logs, the server is redirecting like so:
301 https://example.com/somepath/
301 https://example.com/somepath
301 https://example.com/somepath/
..etc..

ooh! Great catch! This could be the kind of thing that's causing other issues as well.


Create an empty unittest process

create an empty unittest case under the "test" folder
include gtest to the project
create a script to run the unittest
can run test by Makefile command:  make test

/assign


Spec: typo/layout fixes

This PR fixes a number of typos/spelling errors/layout bugs/TODO comments which weren't hidden from the generated output. It also begins to split up unrelated sections into their own files (e.g. identity server from appendices)
Finally, it fixes a bug with event schemas introduced in https://github.com/matrix-org/matrix-doc/pull/48 which rendered the kind of event as None instead of Message Event State Event etc.
None of this should be controversial.

Minor nits, otherwise LGTM


Bump to the latest version

WIP

It appears the sqlcipher is correctly being linked but react native is conflicting and removing it. Fixes this upstream in react native instead


Replace GRUB with systemd-boot

As the image becomes UEFI-based, we can safely replace GRUB with systemd-boot to make the setup simpler and more robust.
GRUB is known to be complex, and it is easy to be broken if we update the kernel without regenerating its config. Its recent update even breaks in some situation if we didn't reinstall it.
Systemd-boot is simpler, and its configs can be written by hands, which enables us to manually fix it without chrooting. Also, because we don't need to deal with various hardware environments, we don't need the complexity of GRUB.
All in all, I think systemd-boot is a better choice for using with GCE than GRUB.

This sounds reasonable to me; @lcastelli do you have any concerns?
@skbeh do you want to prepare a patch and see if this works?

I have tested systemd-boot in GCE environment and it worked. Patch for this project will be delayed for a few days because of my lack of time.

Sounds reasonable. The only drawback I see is that we need to store the kernel in vfat rather than ext4, as systemd-boot can't read ext4, but I guess that's the price to pay for simplicity. I also remember GRUB was explicitly listed as the only supported bootloader for GCE years ago, but I don't see that mentioned anywhere anymore, so probably that's not really a concern anymore.
OK, let's go with this, thanks!


contracts: Refactor instantiate with code

Remove some optimizations from instantiate_with_code and transform the body of this function into both operations done back to back, this work will simplify future PR where we need to access informations from storage that are currently only available at the end of the dispatchable

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3114037

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3114141

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3114917

bot bench $ pallet dev pallet_contracts

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3115096

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3115616

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3116097

bot rebase

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3116193

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3116412

Does it fix #14494?

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3118902

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3121086

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3123787

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3126646

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3126647

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3126648

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3128644

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/3128645

bot bench $ pallet dev pallet_contracts

bot cancel 2-e1470165-44a6-41ba-9ae2-e1c71c7b44a9

bot bench $ pallet dev pallet_contracts

https://weights.tasty.limo/compare?unit=weight&ignore_errors=true&threshold=10&method=asymptotic&repo=substrate&old=pg/simplify_instantiate_with_code&new=master&path_pattern=frame/**/src/weights.rs

bot bench $ pallet dev pallet_contracts

The +155% performance decrease for seal_ecdsa is related to this PR that revert a recent attempt to start using a C lib instead of k256  see https://github.com/paritytech/substrate/pull/14499

bot merge


Allow users to accept/decline a commit

So we want to add some sort of "status" column to the audits table, right?


fix migrate failed and org dashboard failed on MSSQL database

This will update xorm to a5cb21c@go-xorm/xorm  and fix #1443

LGTM, but why is cryptocast5 being also moved ? different govendor version ?

@strk maybe it's govendor's bug?

LGTM

let L-G-T-M work


build(client): Bump build-tools dependencies to 0.46.0

Updates the build-tools to 0.46.0 in the client release group.
Primary changes:
The biggest changes in this release are in the type tests.

The tests are now output in order sorted by type name.
New in 0.46, the type tests no longer depend on any other build task, so the task config has been updated accordingly. Also, the default entrypoint that is tested in each package is now explicitly recorded in package.json (those changes are in #22495).

Additional changes:

The config now has a version property set to 1. This is a schema version that we can change as needed when we make schema changes to the config(s).
The "check:exports" task config for test-loader-utils needed manual updates because it does not have an api task. It has been updated with a custom task definition.
Several packages had task overrides that were incomplete/incorrect because they did not inherit the global task config. Those packages have been updated to inherit the global config.
The same packages from the previous step also have an additional task config for the "build:esnext" task to depend on typetests:gen; this is needed so that ESM and CJS can be built separately.

Not sure I understand the "so they can be built separately" bit. I think I understand that both ESM and CJS builds want the typetests already generated, so the build:esnext->typetests:gen dependency would make sense to me from that perspective. If there is something besides that ("built separately" makes me think "positioned in the build graph so that they can be run concurrently"), it's not clear to me.

Eventually, one should be able to run pnpm fluid-build -t build:esnext and build ONLY the ESM of all packages. That's what I mean by built separately. The CJS and ESM builds should not depend on each other, though they can share common deps (e.g. this one).
Without the build:esnext -> typetests:gen dependency, running that fluid-build command would not trigger typetests:gen in that package. The packages in question do not have a build:test task, so they're building tests as part of tsc/build:esnext -- that's why the package-local deps are needed. (However, right now there are some other tasks in the chain that end up mixing CJS and ESM builds, so there is other cleanup needed before we can build them independently. This just ensures we don't incur more debt.

Got it, thanks for the clarification 👍


test(filter): enable type inference to marble diagram

⚠ Targeting master ⚠

[x] Non-breaking change

Description:
This PR resolves long-pending issue #1633, provides type inference to marble-diagram based test cases while does not hurt documentation for specs. It is using TypeScript compiler's feature to import type signature without real module import and assign it to existing ambient declaration - ambient declaration will provide same type inference to exported modules.
Why Targeting master?
Originally test case were designed to be used as validating type definition as well for most common use cases to prevent issue like https://github.com/ReactiveX/rxjs/issues/2163 . Due to current setup ergonomics, all of tests are running without any compiler validation so there wasn't any regression testing for type definitions which would be considered as breaking change if occurs.
This PR will enable all test cases to have correct compiler type inference, allows all test cases become first-guard to type definition validation. Once this PR is accepted, I'll work on other test cases to have same changes.
Related issue (if exists):
#1633

I have assigned @david-driscoll , @staltz as reviewer for code / document side changes just in case.

This is generated doc with PR, which preserves transpiled spec

with type inference supported.

Coverage remained the same at 97.674% when pulling d86e9186cdcbd3d1f028b2e724431e9a5a5d32a0 on kwonoj:fix-test-type-inference into dc06e017d1cf7f1336cc38a4ab81033a057a6794 on ReactiveX:master.

@jayphelps @blesh updated PR with changes to watch PR to validate certain behaviors like large PR, missing type definition import. It'll looks like https://github.com/ReactiveX/rxjs/pull/2327#issuecomment-277484394

make status checker fail if those validation does not passes.

Coverage remained the same at 97.689% when pulling e338ca61585f5e34833139a18521b017408444a4 on kwonoj:fix-test-type-inference into 3ec315dce56cf9509ad27ded219caf978d1ab141 on ReactiveX:master.

🔥


add documentation packs

Summary

initial attempt at migrating integrations from https://newrelic.com/integrations

Resolves: #128

I just noticed that the documentation field is supposed to be an array of objects and this has them as a single object. I'm not quite sure if this matters in yaml, but I figured it would be worth calling out.
documentation:
  name: thing
  description: stuff
  url: url.com

VS
documentation:
  - name: thing
    description: stuff
    url: url.com

Yes that does indeed matter in yaml and that's the correct way to go:
documentation:
  - name: thing
    description: stuff
    url: url.com


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1864 ms

Resolved: Bofrost.lu performance has improved in e1ce654 after 7 minutes.


Set default file Path using wti pull

I'd like to set default file path in .wti  when I pull from webtranslateit.
As I've seen it, I couldn't find any configuration to set default file path to sync with my project and webtranslateit.
So, Whenever I use wti, I command like wti pull -c FILE_PATH.
But if you support to set default download path in configuration of wti, I would command like only wti pull without file path. It would be better.
Thanks for this useful open source.

You can set up it from admin panel