Package gets installed into build_env instead of host_env when cross-compiling

Hi @wolfv,
I am observing the following weird bug in RoboStack when trying to cross-build pcl-conversions for osx-arm64.
The recipe.yaml looks as follows:
(base) tobias@Tobiass-MacBook-Pro ros-noetic % cat recipe.yaml
package:
  name: ros
  version: 2021.05.21

source:
  - git_url: https://github.com/ros-gbp/perception_pcl-release.git
    git_rev: release/noetic/pcl_conversions/1.7.2-1
    folder: ros-noetic-pcl-conversions/src/work

build:
  number: 0

about:
  home: https://www.ros.org/
  license: BSD-3-Clause
  summary: |
    Robot Operating System

extra:
  recipe-maintainers:
    - ros-forge

outputs:
  - package:
      name: ros-noetic-pcl-conversions
      version: 1.7.2
    requirements:
      build:
        - "{{ compiler('cxx') }}"
        - "{{ compiler('c') }}"
        - ninja
        - sel(unix): make
        - cmake
        - sel(build_platform != target_platform): python
        - sel(build_platform != target_platform): cross-python_{{ target_platform }}
        - sel(build_platform != target_platform): cython
      host:
        - eigen
        - pcl 1.11
        - python
        - ros-distro-mutex 0.1 noetic
        - ros-noetic-catkin
        - ros-noetic-pcl-msgs
        - ros-noetic-roscpp
        - ros-noetic-sensor-msgs
        - ros-noetic-std-msgs
        - vtk
      run:
        - eigen
        - pcl
        - python
        - ros-distro-mutex 0.1 noetic
        - ros-noetic-pcl-msgs
        - ros-noetic-roscpp
        - ros-noetic-sensor-msgs
        - ros-noetic-std-msgs
        - vtk
        - sel(osx and x86_64): __osx >={{ MACOSX_DEPLOYMENT_TARGET|default('10.14') }}
    build:
      script:
        sel(win): bld_catkin.bat
        sel(unix): build_catkin.sh

Note that vtk shows up in the build and run dependencies.
I get an error that:
CMake Error at /Users/tobias/opt/anaconda3/conda-bld/ros_1621565257168/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/cmake/vtk-9.0/VTKPython-targets.cmake:392 (message):
  The imported target "VTK::vtkCommonCorePython" references the file

     "/Users/tobias/opt/anaconda3/conda-bld/ros_1621565257168/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.8/site-packages/vtkmodules/vtkCommonCore.so"

When activating the host_env, vtk does not show up in mamba list. However, it does show up in the build_env:
# packages in environment at /Users/tobias/opt/anaconda3/conda-bld/ros_1621565257168/_build_env:
#
# Name                    Version                   Build  Channel
bzip2                     1.0.8                hc929b4f_4    conda-forge
c-ares                    1.17.1               h0d85af4_1    conda-forge
ca-certificates           2020.12.5            h033912b_0    conda-forge
catkin                    0.8.10                   pypi_0    pypi
catkin-pkg                0.4.23                   pypi_0    pypi
cctools_osx-64            949.0.1             h6407bdd_22    conda-forge
cctools_osx-arm64         949.0.1             h55de48a_22    conda-forge
certifi                   2020.12.5        py38h50d1736_1    conda-forge
clang                     11.1.0               h694c41f_1    conda-forge
clang-11                  11.1.0          default_he082bbe_1    conda-forge
clang_osx-arm64           11.1.0               h40be2b1_2    conda-forge
clangxx                   11.1.0          default_he082bbe_1    conda-forge
clangxx_osx-arm64         11.1.0               hc50fe25_2    conda-forge
cmake                     3.20.2               hdbd2f3e_1    conda-forge
compiler-rt               11.1.0               h654b07c_0    conda-forge
compiler-rt_osx-64        11.1.0               h8c5fa43_0    conda-forge
cross-python_osx-arm64    3.8                  11_cpython    conda-forge
crossenv                  1.0                pyhd8ed1ab_1    conda-forge
cython                    0.29.23          py38ha048514_0    conda-forge
docutils                  0.17.1                   pypi_0    pypi
empy                      3.3.4                    pypi_0    pypi
expat                     2.3.0                he49afe7_0    conda-forge
gencpp                    0.6.5                    pypi_0    pypi
geneus                    3.0.0                    pypi_0    pypi
genlisp                   0.4.18                   pypi_0    pypi
genmsg                    0.5.16                   pypi_0    pypi
gennodejs                 2.0.2                    pypi_0    pypi
genpy                     0.6.15                   pypi_0    pypi
gettext                   <IP_ADDRESS>          h7937167_1005    conda-forge
krb5                      1.19.1               hcfbf3a7_0    conda-forge
ld64_osx-64               530                 he8994da_21    conda-forge
ld64_osx-arm64            530                 h3681fde_21    conda-forge
ldid                      2.1.2                h7660a38_2    conda-forge
libclang-cpp11.1          11.1.0          default_he082bbe_1    conda-forge
libcurl                   7.76.1               hf45b732_2    conda-forge
libcxx                    12.0.0               habf9029_0    conda-forge
libedit                   3.1.20191231         hed1e85f_2    conda-forge
libev                     4.33                 haf1e3a3_1    conda-forge
libffi                    3.3                  h046ec9c_2    conda-forge
libiconv                  1.16                 haf1e3a3_0    conda-forge
libllvm11                 11.1.0               hd011deb_2    conda-forge
libllvm12                 12.0.0               hd011deb_1    conda-forge
libnghttp2                1.43.0               h07e645a_0    conda-forge
libssh2                   1.9.0                h52ee1ee_6    conda-forge
libuv                     1.41.0               hbcf498f_0    conda-forge
llvm-tools                11.1.0               hd011deb_2    conda-forge
loguru                    0.5.3                    pypi_0    pypi
lz4-c                     1.9.3                h046ec9c_0    conda-forge
make                      4.3                  h22f3db7_1    conda-forge
ncurses                   6.2                  h2e338ed_4    conda-forge
ninja                     1.10.2               h9a9d8cb_0    conda-forge
nose                      1.3.7                    pypi_0    pypi
openssl                   1.1.1k               h0d85af4_0    conda-forge
pip                       21.1.1             pyhd8ed1ab_0    conda-forge
popt                      1.16              h112b980_2002    conda-forge
pyparsing                 2.4.7                    pypi_0    pypi
python                    3.8.10          h3a889e0_1_cpython    conda-forge
python-dateutil           2.8.1                    pypi_0    pypi
python_abi                3.8                      1_cp38    conda-forge
pyyaml                    5.4.1                    pypi_0    pypi
readline                  8.1                  h05e3726_0    conda-forge
rhash                     1.4.1                h35c211d_0    conda-forge
rsync                     3.2.3                h0d3f7e0_2    conda-forge
sed                       4.7               h3efe00b_1000    conda-forge
sensor-msgs               1.13.1                   pypi_0    pypi
setuptools                49.6.0           py38h50d1736_3    conda-forge
six                       1.16.0                   pypi_0    pypi
sqlite                    3.35.5               h44b9ce1_0    conda-forge
tapi                      1100.0.11            h879752b_0    conda-forge
tk                        8.6.10               hb0a8c7a_1    conda-forge
vtk                       9.0.1                    pypi_0    pypi
wheel                     0.36.2             pyhd3deb0d_0    conda-forge
xxhash                    0.8.0                h35c211d_3    conda-forge
xz                        5.2.5                haf1e3a3_1    conda-forge
zlib                      1.2.11            h7795811_1010    conda-forge
zstd                      1.5.0                h582d3a0_0    conda-forge

It seems to be specific to vtk, the other dependencies (including pcl) are correctly installed in the host_env (although note the sensor-msgs. It happens both locally on a Mac as well as in the CI.

Also note that some files end up in the host_env (like lib/cmake/vtk-9.0/VTKPython-targets.cmake) while others in the build_env (like lib/python3.8/site-packages/vtkmodules/vtkCommonCore.so)

hmm that's pretty weird! It's also weird that the Channel columns says pypi for vtk and sensor-msgs ... how did you activate the environment? Maybe there is something going on with either environment stacking or we're modifying the PYTHON_PATH that makes conda/mamba list think that those packages are installed through pypi?
I have checked the vtk package and I couldn't find anything suspicious, the files themeselves all look fine.
I did however see in the CMake targets files that @rpath/... is used and I believe that could lead to problems. Usually I think with conda absolute paths are preferred.

well that's an interesting case ... I am confused now what happens, too. It might actually be a trick of conda-build to copy all files from $HOST/lib/python3.8/site-packages to $BUILD/lib/python3.8/site-packages as the entire site-packages folder is empty. 😱
The file $HOST/conda-meta/vtk-9.0.1-....json however indicates that the file is in the correct place and exists.
I'll have to take a look at conda-build.

I think these lines from the cross-python activation script might be relevant:
https://github.com/conda-forge/cross-python-feedstock/blob/41083676420cef1f476a0bde41632cdf7334279b/recipe/activate-cross-python.sh#L33-L34
Maybe @isuruf has an idea (sorry to bother you!). I think for us the problem is that we need to link to the shared libs in site-packages.
However we don't try to execute these python executables so there won't be any issues with executing the wrong arch... maybe we could improve this activation script in a way to not remove some dylib or so files depending on some configured env var ...
@Tobias-Fischer we should probably move this issue to the cross-python feedstock

I am closing this as we debugged this as a cross-python behavior and there is not much we can do with boa (except implementing what cross-python does at a boa level ... but maybe that's a different discussion?!).


Add directive to update link tag

Update link elements

Add UpdateLinkDirective to update link
Extract logic for updating an attribute into UpdateAttributeService
Update example

@khisakuni — I totally missed this, sorry. This looks great!
Am I correct in assuming that this would also make #20 possible? Thank you!

@jvandemo Yeah sounds like this issue is covered by this PR

@jvandemo ping

@khisakuni — I'll have a look at this today 👍

@khisakuni — I have finally had a chance to look at this. Great work! I have a couple of questions:
1. How can we target different link elements with same rel?
Due to the nature of link elements, it is sometimes not possible to identify them using only the rel attribute. Suppose you have:
<head>
  <link rel="stylesheet" href="styles1.css" />
  <link rel="stylesheet" href="styles2.css" />
</head>

and:
<update-link rel="stylesheet" href="styles3.css"></update-link>

then we get:
<head>
  <link rel="stylesheet" href="styles3.css" />
  <link rel="stylesheet" href="styles2.css" />
</head>

So the first element is always targeted, which could potentially not be the user's intention.
Would there be a way to target which element you want to update?
2. Support for other attributes?
The link element supports other attributes such as hreflang, see https://developer.mozilla.org/en/docs/Web/HTML/Element/link#Attributes for a complete list.
Would you be able to add support for them too?
I think your PR would be a great addition if both "issues" could be solved.
What do you think?
Thanks!

@jvandemo Thanks for taking a look!
I'll look into the things you mentioned and keep you posted.

@khisakuni — Thank YOU for making this happen!

Hi and thanks for your work. I also need need this function, is it possible to merge it into the trunk?

@rolintoucour — The current status of this PR is not ready to be merged into master yet as @khisakuni is still working on it. If you need the functionality already, you can manually use the code from this PR to create your own custom library. Thanks!

@jvandemo sorry it took me a while to get around to this. Added support for specifying a link with an id attribute. So if there are two stylesheet links:
<link rel="stylesheet" href="styles1.css" />
<link rel="stylesheet" href="styles2.css" id="foobar" />

and you have
<update-link rel="stylesheet" href="styles3.css" id="foobar" ></ update-link>

it will query the DOM using the provided id.
This now also supports attributes found here.
<update-link  rel="test" href="http://example.com" hreflang="es"></ update-link>

will update both the href and the hreflang attributes.
Let me know what you think!

@khisakuni — Fantastic work, this looks great.
I will simulate some scenarios to see if the outcome is as expected.
Thank you for your efforts!

@khisakuni — Thank you, this is awesome!
One final question before merging: can you write down the pattern that you use to figure out which element to target? Then we can update the documentation to describe how the elements are matched.
E.g. does it first try to match all attributes? And then also match on ID? What happens if 2 elements have the same ID but different attributes?
It would be great to have a list of all scenario's so we can document everything nicely before merging.
Thanks again for your wonderful contribution!

@jvandemo , @khisakuni there are some news about the status of this PR ?
Thanks

@simonepri — We are waiting for @khisakuni to document the targeting pattern before we can merge this PR. Hopefully @khisakuni can chime in. Thank you!

@simonepri @jvandemo hey sorry guys, been pretty slammed with work. Will try to update tonight.

@khisakuni — No problem, take your time. We appreciate all the effort you put into this 👍

news about this guys?

Same, any updates?

@cesarvarela, @alee046 — Unfortunately, this can't be merged without proper documentation. Once the documentation is available, we can test proper behavior and merge if okay.

@jvandemo Apologies that I've neglected this for a while! I updated the documentation to reflect the changes in this PR.

@khisakuni — Thank you for your great work, much appreciated!
Your changes have been merged and released as v2.0.0. 👍

@khisakuni Thank you

@jvandemo I think you forgot to push it to bower:

@simonepri — Thank you, great catch. I re-created the tag.
Can you please try again and verify if it works as expected? Thank you!


If present use @map value from Prisma enums

Fixes: https://github.com/valtyr/prisma-kysely/issues/37
Without this PR:
export type CountryCode = "AD" | "AE";
export const CountryCode = {
  AD: "AD",
  AE: "AE",
};
export type Religion = "BUDDHISM" | "CATHOLICISM" | "CHRISTIANITY";
export const Religion = {
  BUDDHISM: "BUDDHISM",
  CATHOLICISM: "CATHOLICISM",
  CHRISTIANITY: "CHRISTIANITY",
};

With this PR:
export type CountryCode = "AD" | "AE";
export const CountryCode = {
  AD: "AD",
  AE: "AE",
};
export type Religion = "BUDDHISM" | "CATHOLICISM" | "CHRISTIANITY";
export const Religion = {
  BUDDHISM: "buddhism",
  CATHOLICISM: "catholicism",
  CHRISTIANITY: "christianity",
};

I got a question, would it be better to generate the typescript enums?
export enum CountryCode {
  AD = "AD",
  AE = "AE",
}

export enum Religion {
  BUDDHISM = "buddhism",
  CATHOLICISM = "catholicism",
  CHRISTIANITY = "christianity",
}

Hey @cayter, that's a valid question. I prefer objects with as const instead of enums. Here's a good summary from the TS docs: https://www.typescriptlang.org/docs/handbook/enums.html#objects-vs-enums
Enums are one of the few parts of typescript that actually end up bleeding into the runtime, and I prefer that we define those runtime types explicitly.

@jvandenaardweg Is this ready to be merged?

@valtyr yes, fixed the merge issues

How long does it normally take for something like this to be tagged in new release?

@cayter I'm going to release this later today along with a few other things


setOverlap programmatically

Like setPosition and setDirection, there should be a possibility to change the overlap.

Also, setPosition and setDirection like they are now, are not working because the Path is not updated.
It should look like this:
    public void setOverlap(int overlap) {
        if (this.overlap != overlap) {
            this.overlap = overlap;
            setClipPath(getWidth(), getHeight());
            this.postInvalidate();
        }
    }

Thanks for the update. But what about the issue that all set Methods are not working, because the Path is not updated.
Am i missing something?

Your example is working because you are not really using the set methods.
For example...
In the RecyclerViewSampleActivity in the bind method of the ViewHolder you are setting the position. And it works, but only because the ClipPath is generated afterwards.
If you add image.setOverlap(35); in after line 80 in the RecyclerViewSampleActivity and click on any image... you will realize that the ClipPath is only reseted, but not updated.
That's why i proposed the code above.
Btw, getOverlap method is missing.

Hi. I made the calculation in onLayout() method that's why.  I did the necessary improvements. New usage is like this:
imageView.setPosition(DiagonalImageView.BOTTOM)
        .setDirection(DiagonalImageView.RIGHT)
        .setOverlap(300)
        .invalidate();

invalidate() method immediately generates clipPath with provided parameters.
I'll create a pre release asap. Please give me feedback after trying this. Thanks in advance.


Wrong documentation about "getHeartbeatSeriesSamples" permission

Describe the bug
In the documentation is says "Permission to HeartRateVariability is required to access this data."
To Reproduce
not relevant
Expected behavior
Permission needed is "HeartRateVariability" & "HeartbeatSeries"
Screenshots
not relevant
Smartphone (please complete the following information):
not relevant

OS: [e.g. iOS8.1]
iOS

Additional context
not relevant

I'll be taking care of this one! 😄


Wrangler npm global install fails when run as 'root'

🐛 Bug report
Describe the bug
If you try to install wrangler following the instructions here:
https://developers.cloudflare.com/workers/get-started/guide
with the command:
npm install -g @cloudflare/wrangler

The wrangler npm global install fails when run as 'root'. This includes the use case of building a docker image. This seems like a regression of the bug reported in #240. Based on that the problem appears to be that wrangler install tries to create /root/.wrangler as 'nobody' instead of 'root'.
The easiest workaround in to install using yarn which doesn't have this problem:
yarn global add @cloudflare/wrangler

another workaround is add extra options to the installer when installing as root https://github.com/cloudflare/wrangler/issues/240#issuecomment-559135179
npm install @cloudflare/wrangler --global --unsafe-perm --allow-root

Reproduce the bug
Create a minimal Dockerfile with just the npm install and try to build.
Dockerfile
FROM node:14-bullseye-slim
RUN npm install -g @cloudflare/wrangler

Command: docker build .
Error:
[+] Building 8.9s (6/6) FINISHED
 => [internal] load build definition from Dockerfile-foo                                                                                0.0s
 => => transferring dockerfile: 114B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/node:14-bullseye-slim                                                                                4.0s
 => [auth] library/node:pull token for registry-1.docker.io                                                                                0.0s
 => CACHED [1/2] FROM docker.io/library/node:14-bullseye-slim@sha256:1b2caf980f422bf707f9dc64879a0a4f9f748d6d3a4e504d8485aa71884c9ec8                     0.0s
 => ERROR [2/2] RUN npm install -g @cloudflare/wrangler                                                                                4.7s
------
 > [2/2] RUN npm install -g @cloudflare/wrangler:
#6 4.341 /usr/local/bin/wrangler -><EMAIL_ADDRESS>#6 4.353
#6 4.353 ><EMAIL_ADDRESS>postinstall /usr/local/lib/node_modules/@cloudflare/wrangler
#6 4.353 > node ./install-wrangler.js
#6 4.353
#6 4.515 internal/fs/utils.js:314
#6 4.515     throw err;
#6 4.515     ^
#6 4.515
#6 4.515 Error: EACCES: permission denied, mkdir '/root/.wrangler'
#6 4.515     at mkdirSync (fs.js:1009:3)
#6 4.515     at Binary._getInstallDirectory (/usr/local/lib/node_modules/@cloudflare/wrangler/binary-install.js:52:13)
#6 4.515     at Binary.install (/usr/local/lib/node_modules/@cloudflare/wrangler/binary-install.js:78:26)
#6 4.515     at install (/usr/local/lib/node_modules/@cloudflare/wrangler/binary.js:50:10)
#6 4.515     at Object.<anonymous> (/usr/local/lib/node_modules/@cloudflare/wrangler/install-wrangler.js:4:1)
#6 4.515     at Module._compile (internal/modules/cjs/loader.js:1072:14)
#6 4.515     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
#6 4.515     at Module.load (internal/modules/cjs/loader.js:937:32)
#6 4.515     at Function.Module._load (internal/modules/cjs/loader.js:778:12)
#6 4.515     at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12) {
#6 4.515   errno: -13,
#6 4.515   syscall: 'mkdir',
#6 4.515   code: 'EACCES',
#6 4.515   path: '/root/.wrangler'
#6 4.515 }
#6 4.585 npm ERR! code ELIFECYCLE
#6 4.585 npm ERR! errno 1
#6 4.589 npm ERR<EMAIL_ADDRESS>postinstall: `node ./install-wrangler.js`
#6 4.589 npm ERR! Exit status 1
#6 4.589 npm ERR!
#6 4.589 npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
#6 4.589 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
#6 4.602
#6 4.602 npm ERR!
Environment and versions
Fill out the following information about your environment.

operating system: Linux
output of wrangler -V: 1.19.2
output of node -v: 14.17.6
content of wrangler.toml: N/A

@magicfredo suggests another workaround that enables using npm. It's not pretty but it works 🎉
npm install @cloudflare/wrangler --global --unsafe-perm=true --allow-root

e.g. Dockerfile:
FROM node:14-bullseye-slim
RUN npm install @cloudflare/wrangler --global --unsafe-perm=true --allow-root

Really the npm installer should at a minimum work with the official node.js container images! But this is a workaround that could be added to docs at: https://developers.cloudflare.com/workers/get-started/guide
https://github.com/cloudflare/wrangler/issues/240#issuecomment-559135179

Same here on node:14-alpine. I understand the Wrangler dev team wants developers to install this package globally, but there really should be out-of-the-box functionality in Docker images. CI/CD is an extremely common software practice these days, and it'd be nice if this would "just work".

Thanks for reporting - and I agree. Will bring this to the team to discuss.
/cc
@caass
@Electroid

Notes -

Even when installing with npm, we download the binary and manually save it to ~/.wrangler, which we shouldn't. That yarn uses the 'right' user, while a workaround, shouldn't be the way forward (indeed, it means postinstall scripts executed with yarn will have root, which is kinda scary). We should probably take a leaf from esbuild's playbook and make packages for each distribution, that solves it neatly. (with the knock on effect that versioning/caching will work properly)
We also use .wrangler as a store for config, specifically api tokens. In a CI/CD scenario, I'm assuming that config won't even be populated, because the tokens would be passed in with environment variables.

So there are 2 action items here to resolve this

We should fix how we 'install' the binary and not store it in .wrangler.
We shouldn't throw and error when we fail to make the folder; it should log a warning and carry on.

Further - we shouldn't be encouraging global installs; it should be local to the app/package being developed. That'll take some more work.

we shouldn't be encouraging global installs; it should be local to the app/package being developed. That'll take some more work

Absolutely agree. Making wrangler behave more similarly to other NPM packages would make this way more dev-friendly and intuitive 😄

This is how we're dealing with this in the next major version of wrangler:

We do not attempt to create ~/.wrangler on install
On first usage, we only attempt to create the configuration file if you haven't explicitly passed CF_API_TOKEN/CLOUDFLARE_API_TOKEN
We encourage folks to use wrangler like any other npm package; NOT installed with -g, and as a regular dependency of their project. The executable code is then installed under node_modules as expected (You can still install it globally if preferred, but even then it uses node's global node_modules directory, not ~/.wrangler)

You can try this today with npm install wrangler@beta (note that we don't require the @cloudflare/ scope). We're actively developing this at https://github.com/cloudflare/wrangler2, and hope to go to GA soon.

Closing this since wrangler v2 is now in GA.


Momemtjs date converting error raise.

Description of the Issue and Steps to Reproduce:
console.log('>>>>>>.', moment(value).format('MM-DD-YYYY'),moment(value).format('YYYY-MM-DD'));
I am not sure where this error generated, unable to track. I had added warning message.
Environment:
Ubuntu, chrome browser.
GETTING BELOW ISSUE
Deprecation warning: value provided is not in a recognized ISO format. moment construction falls back to js Date(), which is not reliable across all browsers and versions. Non ISO date formats are discouraged and will be removed in an upcoming major release. Please refer to http://momentjs.com/guides/#/warnings/js-date/ for more info.
Arguments:
[0] _isAMomentObject: true, _isUTC: false, _useUTC: false, _l: undefined, _i: 27/04/2016, _f: undefined, _strict: undefined, _locale: [object Object]
Error

This warning message happens when you create a Moment from a string that's not in a supported ISO 8601 format (see http://momentjs.com/docs/#/parsing/string/ for a list of supported formats).
In this case, it looks like you tried to parse the string 27/04/2016, which is not an ISO format.  You can parse this format without a warning if you tell Moment what the format is:  moment("27/04/2016", "DD/MM/2016").  Alternatively, you can change the format of your input to match the ISO spec:  moment("2016-04-27")
I'm closing this issue since it's not a bug in Moment, but if you still have questions, please mention me in a reply here and I'll try to help.

time = "Thu Oct 13 2016 14:40:26 GMT+0100 (GMT Daylight Time)";
var formatedTime = moment(time).format('HH:mm:ss');
I will get the right format which is 14:40:26 ... but I will get the same  warning.
to solve this issue I passed format
var formatedTime = moment(time, 'HH:mm:ss').format('HH:mm:ss');
I'm not getting warning any more but .....
my result is not correct is not avoiding utc ... and show me 1 hr behind 13:40:26
How can I get the right value and no warning

I Could get the right it by:
var formatedTime = moment(time, 'ddd, MMM Do YYYY, HH:mm:ss').format('HH:mm:ss');

I am not successful, when i do a supported ISO 8601 format

Doing moment(new Date("27/04/2016")).format.... seems to work. But i think their are some issues in this approach, maybe related to locales etc.

@ziaulrehmandevsinc Worked for me. Thanks.

@ziaulrehmandevsinc Also worked for me, Thanks

@ziaulrehmandevsinc It also worked for me. Thankyou so much

Worked for me. Thanks

At the moment, we would prefer to adjust code to handle this issue.   Within moment.js where it displays the warning:
function warn(msg) {
if (hooks.suppressDeprecationWarnings === false &&
(typeof console !==  'undefined') && console.warn) {
console.warn('Deprecation warning: ' + msg);
}
How does one set "hooks.suppressDeprecationWarnings"?  I reviewed the hooks function but it reports hooks is not a function.   Using aurelia.
Thanks

@pdesimone

// Suppress the warnings
const moment = require('moment');
moment.suppressDeprecationWarnings = true;

// See what else you can mess with
console.log(Object.keys(require('moment')));

Yeah I'm getting this issue using moment('2018-01-20') which, as far as I can tell is a valid ISO 8601 format.

At the time, I couldn't get the supressDepreciationWarnings or other solutions to work.
I have done this in all my uses of moment:
moment(value, format), ie:  Value: 2018-01-20, Format: MM/DD/YYYY.   Then the warning doesn't happen.   Apparently, if you let moment "try" and figure out the type of date, you get the warning...

@ziaulrehman40 worked for me, thanks so much

If you think you're handling things correctly and still seeing the error double check your input types <input type="date" /> will throw error but <input type="text" /> works.

@pdesimone
// Suppress the warnings
const moment = require('moment');
moment.suppressDeprecationWarnings = true;

// See what else you can mess with
console.log(Object.keys(require('moment')));

Thanks : Its working fine, but i need to know whether it will cause any issue while adding suppressdeprecationwarnings

Thanks, @ziaulrehman40 - :kissing_heart:

I'm also having a trouble with this.
console.log(moment(this.entities[i].created_at).isValid());
this.entities[i].created_at = moment(this.entities[i].created_at).format("DD-MM-YYYY HH:mm");

The console log returns true, but I get the error message:
value provided is not in a recognized RFC2822 or ISO format. moment construction falls back to js Date(), which is not reliable across all browsers and versions. Non RFC2822/ISO date formats are discouraged and will be removed in an upcoming major release. Please refer to http://momentjs.com/guides/#/warnings/js-date/ for more info.
Arguments:
[0] _isAMomentObject: true, _isUTC: false, _useUTC: false, _l: undefined, _i: 21-05-2020 19:43, _f: undefined, _strict: undefined, _locale: [object Object]

@kiocosta Sorry you are having trouble. You should probably parse with a format. https://momentjs.com/docs/#/parsing/string-format/ It might be a good question for Stack Overflow too.


Fix E2E Tests

Describe your changes:
Fixes PyTests e2e

Type of change:

[ ] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

Closing this as it is already merged in main from another PR


No launch in fresh win 7, 8.1, or 10 machines.

Three laptops fresh out of the box. Cannot launch anything. Dies or generates "failed" errors. Is this still a supported distro?

Hi @extractcraftlee we're currently busy releasing version 2.0 of thw rokbench. Could you see if you get the same errors using the bet2 version of 2.0?
https://evothings.com/download/

Closing this one due to no feedback.


#2411 [Investigation] Move to Vite from Rollup for project build

Closes #2411
Proposed Solutions to Speeding Up Development Experience
Proposed solutions
Vite for development, Rollup for build.
For development, to create a new dev workspace by Vite, e.g. /dev. Its functionality equals to current /example, but engined by Vite which will make the development faster.
For build, keep current Rollup configurations and the build workflow the same.
New development workflow
In root
npm install

In /dev
# For standalone
npm run start:standalone

# For remote
npm run start:remote

NB! When you finish coding, before creating a PR, you'd better preview your implementation to make sure everything works fine with Rollup. Please follow DEVNOTES -> Development to preview.
Why
Why not replace Rollup with Vite?
It'll take more effort and may cause other problems, but the optimization is a little or even none.
Ketcher uses Rollup to build libraries. If we replace Rollup with Vite, that means we use Vite to build libraries. As for build, Rollup is not worse than Vite which uses Rollup under the hood. On top of that, Vite is also blamed for non-consistency between development and production environment.
I've taken two days to replace Rollup with Vite in ketcher-core and ketcher-react, but as I thought, optimizations are a little or even none.

The following data is based on my Windows 10, with 11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz 2.61 GHz.

For ketcher-core, the build time changes from 11.5s to 13.49s

For ketcher-react, the build time changes from 23.9s to 20.42s

Why Vite for development?
Easy to answer, because Vite is fast for development. Vite leverages native ES Modules in the browser to load your code instantly, no matter how large the App is. Instead of importing a single JavaScript bundle file, it's importing our actual source code, like a raw .tsx file. It also makes TypeScript about 20–30 times faster because it skips type checking and uses esBuild to transpile your code. Vite also supports Hot Module Replacement for an extremely fast feedback loop during development.
Compared to approximately more than 30s to wait after changes when developing, Vite just needs less than 10s.
https://user-images.githubusercontent.com/27288153/228762340-9f8a9813-a72a-41e0-812c-34e368578a31.mp4
Disadvantages
Everything we do in /example, should do the same in /dev. However, considering we hardly ever change code in /example, I guess it would be not a big deal. In addition, we can replace /example with /dev step by step in the future, so this problem is gonna be fixed.
It's possible that everything works fine in /dev but when building there are some errors. I think it is inevitable if we use Vite. It's not caused by mixing Vite and Rollup. Even if we only use Vite, it's gonna happen as well. That's why I recommend previewing implementations after finishing coding.

Fix me
Alias
In dev/vite.config.ts, all alias are defined here. The question is, if there are same named alias in different packages, Vite may not find the correct package. For example, if we have domain which maps src/domain in ketcher-core, at the same time we have domain which maps src/domain in ketcher-react, then the dev/vite.config.ts looks like
resolve: {
  alias: [
    { find: 'domain', replacament: '../packages/ketcher-core/src/domain' },
    { find: 'domain', replacement: '../packages/ketcher-react/src/domain'}
  ]
}

In this case, Vite may not replace domain correctly. I have no idea how to resolve this problem at this moment. See more about resolve.alias.
Environment variables
In dev/vite.config.ts, all env variables are defined here. However, Vite can't handle same named env variables in different packages. For example, we have process.env.VERSION: JSON.stringify(pkg.version) in ketcher-react, and we have the same env variable in ketcher-polymer-editor-react. In this case, we can only define one of  them. To fix, we have to rename one of them.


Easy way for multiple accounts?

Hi,
First of all, thanks a lot for the nice framework, is there any easy way to do it for multiple accounts?

@miwi-fbsd here https://github.com/angelkurten/laravel-bittrex

@angelkurten that helps me exactly what?


Add Messenger code API

Hello,
Messenger Codes can be scanned in Messenger to instantly link the user to your bot, no typing needed. They're great for sticking on fliers, ads, or anywhere in the real world where you want people to try your bot.
This PR add the ability to programmatically get your bot's Messenger Code.
Enjoy,

👏👏👏
This is awesome! Didn't even realize this api call existed, is it new?
I'm maintaining a Botkit fork right now that supports many pages at once, and so I've been slowly removing all bot identity config (like access_token and studio token) from the controller config.
So I'd rewrite this immediately to be scoped to the bot, I might be an edge case, not sure how often people are using bots that are unconfigured/generic these days.
Personally I would add this to the bot object, and get at the access_token like so:

request.post('https://graph.facebook.com/v2.6/me/messenger_codes?access_token=' + configuration.access_token || this.config.access_token, {
             form: message
         },

What do y'all think? I think this is a great feature regardless of where it lives.

Yoo @jonchurch,
yes it's new, Facebook maked some changes last thursday (2 march) on messenger version 1.4, Among the changes announced (Messenger Profile API #690 and Messenger Code API #689) and many other cool stuff !
Glad you liked it :smile:
Just out of curiosity, why you needed one bot that supports many pages at once ?
in this case you need to call get_messenger_code as mush as the number of your pages.

It's for a client, they are providing facebook bots to their customers
(people who run HUGE conferences) to provide interactions at scale.
In order to make it so code doesn't have to be written whenever a new bot
is added, I'm making botkit support any number of bots.
So essentially, one controller, any number of instances of bots, new bots
can be added or removed at any time.
It's similar to how botkit handles Slack Bots, one controller X number of
teams. Each team has some unique config stuff, but in the Facebook case,
each page's bot would have different content. Luckily Botkit Studio handles
the scripts for us, all we have to do is route messages to the right bots
etc.
So in this case, each page would have its own Messenger Code.
It's an edge case right now, but I think that it's totally logical to see a
future where Facebook Bots are "added" to a page similarly to how Slackbots
are currently "added" to a team. So one "app" is providing services to
multiple pages at a time.
On Tue, Mar 7, 2017 at 12:10 PM, Ouadie Lahdioui<EMAIL_ADDRESS>wrote:

Yoo @jonchurch https://github.com/jonchurch,
yes it's new, Facebook maked some changes last thursday (2 march) on
messenger version 1.4, Among the changes announced (Messenger Profile API
#690 https://github.com/howdyai/botkit/pull/690 and Messenger Code API
#689 https://github.com/howdyai/botkit/pull/689) and many other cool
stuff !
Glad you liked it 😄
Just out of curiosity, why you needed one bot that supports many pages at
once ?
in this case you need to call get_messenger_code as mush as the number of
your pages.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/howdyai/botkit/pull/689#issuecomment-284790004, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMUR2zJ3wTx4KnZB_dCDjJTs4eNovkkQks5rjY-ZgaJpZM4MSgA_
.

That being said, I'm giving your PR as it stands a big thumbs up :)
On Tue, Mar 7, 2017 at 12:32 PM, Jonathan Church<EMAIL_ADDRESS>wrote:

It's for a client, they are providing facebook bots to their customers
(people who run HUGE conferences) to provide interactions at scale.
In order to make it so code doesn't have to be written whenever a new bot
is added, I'm making botkit support any number of bots.
So essentially, one controller, any number of instances of bots, new bots
can be added or removed at any time.
It's similar to how botkit handles Slack Bots, one controller X number of
teams. Each team has some unique config stuff, but in the Facebook case,
each page's bot would have different content. Luckily Botkit Studio handles
the scripts for us, all we have to do is route messages to the right bots
etc.
So in this case, each page would have its own Messenger Code.
It's an edge case right now, but I think that it's totally logical to see
a future where Facebook Bots are "added" to a page similarly to how
Slackbots are currently "added" to a team. So one "app" is providing
services to multiple pages at a time.
On Tue, Mar 7, 2017 at 12:10 PM, Ouadie Lahdioui<EMAIL_ADDRESS>
wrote:

Yoo @jonchurch https://github.com/jonchurch,
yes it's new, Facebook maked some changes last thursday (2 march) on
messenger version 1.4, Among the changes announced (Messenger Profile API
#690 https://github.com/howdyai/botkit/pull/690 and Messenger Code API
#689 https://github.com/howdyai/botkit/pull/689) and many other cool
stuff !
Glad you liked it 😄
Just out of curiosity, why you needed one bot that supports many pages at
once ?
in this case you need to call get_messenger_code as mush as the number of
your pages.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/howdyai/botkit/pull/689#issuecomment-284790004, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AMUR2zJ3wTx4KnZB_dCDjJTs4eNovkkQks5rjY-ZgaJpZM4MSgA_
.

Interesting, thank you for sharing your use case here.


bug: discord component story isn't working

The error originated from attempt to access jest.fn() to mock global.fetch or fetch function.

jest-mock package isn't installed, and even if it got installed webpack will fail to compile it.

Solution

Install fetch-mock
Follow its docs to mock each story fetch request.

Example stories fetch mock:
export const ErrorFetching: React.FC = () => {
  fetchMock.restore().mock('*', 404)
  return (
    <Wrapper>
      <DiscordBar />
    </Wrapper>
  )
}

export const EmptyMembers: React.FC = () => {
  fetchMock.restore().mock('*', { presence_count: 0, status: 200, members: [] })
  return (
    <Wrapper>
      <DiscordBar />
    </Wrapper>
  )
}

fixed in https://github.com/garageScript/c0d3-app/pull/1817

@shockz09 I replaced the solution as the previous one wasn't working. I also added more details and some examples.

i see


KAFKA-12728: version upgrades: gradle (6.8.3 -->> 7.0.1) and gradle shadow plugin (6.1.0 -->> 7.0.0)

JIRA ticket: https://issues.apache.org/jira/browse/KAFKA-12728
Related pull requests:

#10203
#10466

Note: we will wait for a Gradle 7.0.1 patch ◀

I don't think the issues are related to the shadow plugin. They're related to the gradle upgrade.

Probably they are... I will try to isolate issue(s) and compare it with Gradle 7 release notes.

So, herewith some update: on my local box (Ubuntu Linux with Java 8) around 50 test fail in a same way; details:
Gradle command: ./gradlew -PscalaVersion=2.12 test
Environment:
dejan@dejan-HP-ProBook-450-G7:~$ java -version
openjdk version "1.8.0_292"
OpenJDK Runtime Environment (build 1.8.0_292-8u292-b10-0ubuntu1~20.04-b10)
OpenJDK 64-Bit Server VM (build 25.292-b10, mixed mode)
dejan@dejan-HP-ProBook-450-G7:~$ date
сре, 12. мај 2021.  22:20:54 CEST
dejan@dejan-HP-ProBook-450-G7:~$

All failed test stacktrace starts like this:
org.apache.kafka.common.errors.InvalidConfigurationException: Invalid PEM keystore configs
Caused by: java.security.KeyStoreException: Key protection  algorithm not found: java.security.UnrecoverableKeyException: Encrypt Private Key failed: unrecognized algorithm name: PBEWithSHA1AndDESede
	at sun.security.pkcs12.PKCS12KeyStore.setKeyEntry(PKCS12KeyStore.java:677)
	at sun.security.pkcs12.PKCS12KeyStore.engineSetKeyEntry(PKCS12KeyStore.java:577)
	at java.security.KeyStore.setKeyEntry(KeyStore.java:1140)

It seems that these other people have similar issues:

https://github.com/jenkinsci/docker/issues/1112
https://github.com/bcgit/bc-java/issues/941#issuecomment-836055626

Also, Oracle opened few JIRA related tickets:

https://bugs.openjdk.java.net/browse/JDK-8266261 After 8u282 -> 8u292 update: "unrecognized algorithm name: PBEWithSHA1AndDESede"
https://bugs.openjdk.java.net/browse/JDK-8266279 8u292 NoSuchAlgorithmException unrecognized algorithm name: PBEWithSHA1AndDESede

Also... both here on Jenkins and on my laptop there is another type of problems with some test failing like this:
org.apache.directory.api.ldap.schema.extractor.UniqueResourceException: Problem locating LDIF file in schema repository
Multiple copies of resource named 'schema/ou=schema/cn=apachedns/ou=objectclasses/m-oid=<IP_ADDRESS>.4.1.18<IP_ADDRESS>.3.9.ldif' located on classpath at urls
    jarːfileː/home/jenkins/.gradle/caches/modules-2/files-2.1/org.apache.directory.api/api-all/1.0.2/5a0f957dfe453ecaa6e7cbb19d2698083116e123/api-all-1.0.2.jar!/schema/ou%3dschema/cn%3dapachedns/ou%3dobjectclasses/m-oid%3d<IP_ADDRESS>.4.1.18<IP_ADDRESS>.3.9.ldif
    jarːfileː/home/jenkins/.gradle/caches/modules-2/files-2.1/org.apache.directory.api/api-ldap-schema-data/1.0.0/eca194f6baca671c466a4eb3ebc669856d997baa/api-ldap-schema-data-1.0.0.jar!/schema/ou%3dschema/cn%3dapachedns/ou%3dobjectclasses/m-oid%3d<IP_ADDRESS>.4.1.18<IP_ADDRESS>.3.9.ldif

Short update:

first issue occurs only for Java "1.8.0_292" (not only here but worldwide and it is recognized by Oracle)
second issue... I did report it to a Gradle, but maybe it should be addressed to Apache Directory Server instead (note: this project is using apacheds version 2.0.0-M24 and it seems that this particular issue is solved in apacheds  2.0.0-M26 (good news is that upgrade is not required: good old exclusion should do the trick).

Ok, closing the gap here:

Kafka Jenkins could skip JDK update to a version "1.8.0_292" (see previous comments); note: there is a workaround in Gradle for that version, but I guess it is lot easier just to skip that JDK) FYI @ijuma
as for second issue (that affects all enviroments/all JDK versions): it seems that this dependency org.apache.directory.api:api-ldap-schema-data should be excluded out of configuration responsible for a tests executions (or mayve from all configurations); thing is that same dependency is already excluded out of testCompile configuration here: https://github.com/apache/kafka/blob/2.8.0/build.gradle#L824

@dejan2609 did the exclusion stop working with the upgrade to Gradle 7.0? That seems like the most plausible explanation I've seen so far.

@dejan2609 did the exclusion stop working with the upgrade to Gradle 7.0? That seems like the most plausible explanation I've seen so far.

Thing is that exclusion covers testCompile only (in trunk and with Gradle 6.8.3) while with Gradle 7.0.1 (this PR) test executions fail (in more details: they don't even start for a set of tests, that is).
I think I managed to get around this (just finished testing on my end).
Change is tiny (I will not squash commits until we get complete solution).

So, just to sum it up:

similar UniqueResourceException issues with api-ldap-schema-data module are solved for a testCompile level here: https://github.com/apache/kafka/blob/2.8.0/build.gradle#L824
Apache DS project solved this in a version 2.0.0.AM26 https://issues.apache.org/jira/browse/DIRSERVER-2066
Kafka project at the moment is using apache ds version 2.0.0-M24 (and upgrade is not trivial)
after Gradle upgrade form 6 to 7  UniqueResourceException errors are thrown again (but this time for a tests execution)
obviously, Gradle 7 changed dependency resolution (and many other things) but I would argue that this is not a Gradle 7 issue per-se

It seems that only one unrelated test failed.

FYI/note: Gradle 7.0.2 hotfix is released few hours ago (it solves one corner case on Alpine Linux): https://github.com/gradle/gradle/releases/tag/v7.0.2
Let me know if you want me to bump Gradle (but it also makes sense to skip this). Please have your say @ijuma

Let's bump it.

Bumped/force-pushed (I took the liberty to skipped local testing on my end just to save some time).

Test result on Jenkins shows no failures.

Thanks for the PR!


Enum

Hey! Firstly awesome project and I highly appreciate the effort put into it.
I was wondering if you had any plans to support Enums more clearly within the visualisation?

@chrisui Do you want to have enums as separate boxes on a graph?
Or do you have something else in mind?

I think if they were to be shown on the graph they could be shown with a distinctive style to show they are not necessarily "traditional" nodes in the graph.
Otherwise we might want to allow clicking/hovering the type in the node/sidebar and seeing extra information about the type. I would expect this to be a similar ux pattern to how you could show more information about existing types which are just shown as strings. Ie. nullable, lists, strings etc.

I'd put a vote in for having them displayed in the graph with a different style. We use Enums extensively, and often the fact that some data is represented as an Enum vs a Type does not matter too much, so I'd quite like to be able to view them as part of the full type graph.

+1 :)


[Feature]: Add Netlify to Docs site

Checklist

[X] I've searched for similar issues and couldn't find anything matching
[X] I've discussed this feature request in the K8sGPT Slack and got positive feedback

Is this feature request related to a problem?
None
Problem Description
No response
Solution Description
Implement Netlify for building the latest deploy preview for our Docs site just as we have for our Website. For example- https://github.com/k8sgpt-ai/website/pull/1#issuecomment-1482501595
Benefits
It would be easy to review PRs as the latest deploy preview would be available.

I am working on this.

Closing this issue as the Netlify build was implemented internally. See this comment for example.


[ROCm] benchmark_flash_attention.py failing with Memory Access Fault

I am trying to run benchmark_flash_attention.py on a ROCm system with MI300X GPUs. It runs through sequence lengths 512, 1024, 2048, and 4096 for headdim=64, but after that it hangs and gives a Memory Access Fault error. I observe this on flash-attention v2.6.3, on pytorch 2.5.1 and nightly builds of pytorch 2.6.
Here is the pystack stack trace:
Traceback for thread 3560650 [] (most recent call last):
    (Python) File "/home/tensorwave/nikhil/fa-tests/flash-attention/benchmarks/benchmark_flash_attention.py", line 126, in <module>
        _, b0 = time_fwd_bwd(
    (Python) File "/home/tensorwave/nikhil/fa-tests/flash-attention/benchmarks/benchmark_flash_attention.py", line 66, in time_fwd_bwd
        time_f, time_b = benchmark_fwd_bwd(func, *args, **kwargs)
    (Python) File "/home/tensorwave/nikhil/fa-tests/torch2.6_11-18/lib/python3.10/site-packages/flash_attn-2.6.3-py3.10-linux-x86_64.egg/flash_attn/utils/benchmark.py", line 140, in benchmark_fwd_bwd
        benchmark_backward(
    (Python) File "/home/tensorwave/nikhil/fa-tests/torch2.6_11-18/lib/python3.10/site-packages/flash_attn-2.6.3-py3.10-linux-x86_64.egg/flash_attn/utils/benchmark.py", line 66, in benchmark_backward
        m = t.timeit(repeats)
    (Python) File "/home/tensorwave/nikhil/fa-tests/torch2.6_11-18/lib/python3.10/site-packages/torch/utils/benchmark/utils/timer.py", line 274, in timeit
        self._timeit(number=max(int(number // 100), 2))
    (Python) File "/home/tensorwave/nikhil/fa-tests/torch2.6_11-18/lib/python3.10/site-packages/torch/utils/benchmark/utils/timer.py", line 264, in _timeit
        return max(self._timer.timeit(number), 1e-9)
    (Python) File "/usr/lib/python3.10/timeit.py", line 178, in timeit
        timing = self.inner(it, self.timer)
    (Python) File "<timeit-src>", line 8, in inner
    (Python) File "/home/tensorwave/nikhil/fa-tests/torch2.6_11-18/lib/python3.10/site-packages/torch/utils/benchmark/utils/timer.py", line 18, in timer
        torch.cuda.synchronize()
    (Python) File "/home/tensorwave/nikhil/fa-tests/torch2.6_11-18/lib/python3.10/site-packages/torch/cuda/__init__.py", line 969, in synchronize
        return torch._C._cuda_synchronize()

@rocking5566 I also met this error a couple of times...Could you please take a look?


[#13] Update README.md add FAQs section

Issue
#13
Details
Add FAQs section to README.md
CheckList

[x] PR starts with [#ISSUE_ID].
[ ] Has been tested (where required) before merge to develop.

Hey @Ding-Fan, following on from your comment here. That second note is meant to be your issue, just very poorly explained 😅
What might work well is if we combine your FAQs suggestions with the existing Notes section (can rename / replace it all with FAQs), see an example suggestion below:
## FAQs

### Property 'get' does not exist on type 'Promise<SuperDeno>'

Unlike [SuperDeno](https://github.com/asos-craigmorten/superdeno), `superoak()` returns a promise which will need to be awaited before you can call any method such as `.get("/")`.

\`\`\`ts
// ✅ works
Deno.test("it will allow you to make assertions if you await it", async () => {
  const request = await superoak(app);
  await request.get("/").expect(200).expect("Hello Deno!");
});

// ❌ won't work
Deno.test("it will allow you to make assertions if you await it", async () => {
  const request = superoak(app);
  await request.get("/").expect(200).expect("Hello Deno!"); // Boom 💥 `Property 'get' does not exist on type 'Promise<SuperDeno>'`
});
\`\`\`

### Request has been terminated error

Unlike [SuperDeno](https://github.com/asos-craigmorten/superdeno), you cannot re-use SuperOak instances. If you try you will encounter an error similar to below:

\`\`\`console
Error: Request has been terminated
Possible causes: the network is offline, Origin is not allowed by Access-Control-Allow-Origin, the page is being unloaded, etc.
    at Test.Request.crossDomainError
    at XMLHttpRequestSham.xhr.onreadystatechange
    ...
\`\`\`

This is because SuperOak instances automatically close the underlying Oak server once the assertion chain has completed.

Instead you should make all of your assertions on a single SuperOak instance, or create a new SuperOak instance for subsequent assertions like below:

\`\`\`ts
// ✅ works
Deno.test("it will allow your to make multiple assertions on one SuperOak instance", async () => {
  const request = await superoak(app);
  await request.get("/").expect(200).expect("Hello Deno!");
});

// ✅ works
Deno.test("it will allow your to re-use the Application for another SuperOak instance", async () => {
  const request1 = await superoak(app);
  await request1.get("/").expect(200);

  const request2 = await superoak(app);
  await request2.get("/").expect("Hello Deno!");
});

// ❌ won't work
Deno.test("it will through an error if try to re-use a SuperOak instance", async () => {
  const request = await superoak(app);
  await request.get("/").expect(200);
  await request.get("/").expect("Hello Deno!"); // Boom 💥 `Error: Request has been terminated`
});
\`\`\`

Though you've provided several nice examples, I don't think it's transparent what the works and won't work examples are showing (as it would require new users to dive into an issue for context which is another click etc.). Even with the context, I think we can use the test names to provide context why an example works vs doesn't work (sim. to the notes currently).

Hi @cmorten , your example looks good 👍
I'll make a new commit with your example to replace the existing Notes section.


Git

Please provide more info about the token.

{
"symbol": "Git",
"address": "0x3a86512cca257c4dd8a68646c7c01df084e0f87d",
"overview":{
"en": "We are an open source platform on which anyone can volunteer their code as a database to earn a reward, with the goal of automating code and changing the world within the next decade.",
"zh": "我們是一個讓任何人均可自願貢獻他們的代碼作為數據庫來賺取賞金的開放源碼的平臺，平臺目標在未來十年內，讓代碼自動化跑起來，改變世界"
},
"email"<EMAIL_ADDRESS>",
"website": "https://your-awesome-project.com",
"whitepaper": "https://your-awesome-project.com/file.pdf",
"state": "LOCKED | NORMAL",
"published_on": "2018-09-01",
"links": {
"blog": "https://weibo.com/opengit",
"telegram": "https://t.me/opengit/one",
"github": "https://github.com/your-awesome-project",
"facebook": "https://www.facebook.com/opengit",
}
}

提交格式存在问题，请仔细阅读我们教程。


GEODE-2119: gfsh user and password in clear text

Would you mind rebasing this into one commit?
It makes it easier to add review comments since there will only be one diff for a given file.


Raise concourse btrfs monitor levels

What
The concourse btrfs monitor levels appear to be too low for production as we're getting spurious warnings. This raises the levels and also ensures that we only track btrfs processes on the concourse host rather than the wider cluster.
How to review

Code review.
Check that the levels are higher than what we've seen in production: https://app.datadoghq.com/monitors#2083141?group=*&from_ts=1495098656256&to_ts=1495102256543

Who can review
Anybody, probably @paroxp.

Looks good :)


added the ability to set size on autocomplete component

##Summary:

Allows size to be set on autocomplete component

Do you think both default and value in control should be the same?

Done:


Test pandas support under Python 3.7.

Full support still blocked on pyarrow support for Python 3.7.
See #5294.

@dpebot Please merge when green.


Support Web

Please try web.
it works for me.
worth integrating into yours

I'm not sure whether to support Web or not. As far as I concern, Web could behave quite differently than other platforms.
Checkout those:

Web Bluetooth: https://github.com/woodemi/notepad_core
Web Camera: https://github.com/woodemi/quick-scan-flutter

Web would be very easy to accomplish with the universal_html package and the notifications API. Like this:
html.Notification("title");
No other code necessary.

@Sunbreak Please Support

@Sunbreak Please Support

PRs are welcome

https://github.com/woodemi/quick_notify/pull/12


Formalize the desugaring of when/unless clauses

Category
Dafny formalization, Lean formalization
Describe the feature you'd like to request
Currently a Cedar policy is represented with its condition clause being an arbitrary expression. This is not how users write policies, they break the expression up into (potentially multiple) when/unless clauses. Currently the spec does not detail how that desugaring happens, so it's implicit whether multiple clauses are anded or ored together. This should be a part of the formal spec.
Describe alternatives you've considered
Leave as is
Additional context
Due the engineering details on the DRT, it's not possible at the moment to test this, however, if in the future DRT moves to using the EST format, it will be.
Is this something that you'd be interested in working on?

[X] 👋 I may be able to implement this feature request
[ ] ⚠ This feature might incur a breaking change

Sub task for #42


Link to the documentation of latest version is broken

Hi,
It seems that the link on homepage is broken:
http://github-tools.github.io/github/docs/3.4.0/index.html

Hello, still broken, any solution today ?


Is it intended? Column loaded twice if listed twice in "columns=" when reading a Parquet file.

What happened: When loading a Parquet file, I specified a column twice in the "columns=" argument and the column was loaded twice, that is, there were two columns in the resulting DataFrame with the same name and data.
What you expected to happen: Even though I specified the column twice, I expected that the column would only be loaded once.
Minimal Complete Verifiable Example:
# assume a Parquet file has a column called "test" and then load it twice
ddf = dd.read_parquet("file.parquet", columns=['test', 'test'])
ddf.head()

Anything else we need to know?:
Environment:

Dask version: 2022.05.0
Python version: 3.8.13
Operating System: Windows Server 2016
Install method (conda, pip, source): conda

This matches with the discussion in #9122 : IMHO Dask should prevent at all costs building DataFrames with duplicate column names.

@jsignell : when I tried to reproduce I'm getting the same behaviour for pandas and dask. wondering if it's still an issue if it's consistent with pandas?
I used the minimal example above.
                      id   id         x
timestamp
2000-01-01 00:00:00  956  956 -0.731324
2000-01-01 00:00:01  994  994  0.301500
2000-01-01 00:00:02  996  996 -0.871429
2000-01-01 00:00:03  926  926 -0.963692
2000-01-01 00:00:04  989  989  0.801868
                      id   id         x
timestamp
2000-01-01 00:00:00  956  956 -0.731324
2000-01-01 00:00:01  994  994  0.301500
2000-01-01 00:00:02  996  996 -0.871429
2000-01-01 00:00:03  926  926 -0.963692
2000-01-01 00:00:04  989  989  0.801868

I believe that read_parquet (both in Pandas and Dask) should have some control of the columns parameter, so that either:

Something like sorted(set(columns)) is done silently under the hood, to remove duplicate column names before loading them.
An error is raised whenever len(set(columns)) < len(columns), asking the user explicitly to remove duplicate column names.

At a lower level anyway, both pd.DataFrame and dd.DataFrame should control that they have no duplicate column names. This means for example that you cannot call rename on columns and use already-existing column names.
Honestly, I can't think of any use case where it makes sense to have different columns, but named equally...

@jorloplaz  : I agree with the behaviour, but to make it consistent we'd need to change pandas as well. because in case of duplicate columns today both pandas and dask are behaving the same.
do you think it's worth starting a change in dask? to maintain parity, we'd need to even request a` pandas change.

Yes and no. First of all, I don't think that Pandas should allow either having duplicate column names, but they have the point that columns and rows are "symmetrical", in the sense that you can do for example df.T, and then, if you allow duplicates in the index, you should also allow duplicates in the columns.
However, in Dask that symmetry is lost. You can't exchange easily index for columns, because the index is used for internal partitioning, while columns are not. Thus, clearly Dask is more into the scheme "rows are observations, columns are features, period". So IMHO it makes more sense to force that columns have no duplicates at all, even if Pandas lets you have them.
Besides, forcing this simplifies a lot of things:

df[column_name]  always returns a dd.Series, same as df.iloc[:, n].
df.groupby(column_name) always gives a dd.SeriesGroupBy.
df.compute() guarantees that the resulting pd.DataFrame has no duplicate columns.
etc, etc


Reduce token copying

A little low-hanging fruit.
Since the Lexer instance isn't needed anymore after the lexing is complete,
we can take ownership of the tokens and errors vectors and reverse them
in-place without making a copy. Big schemas can have 100K+ tokens so
it's actually quite a lot of work to copy them.
As it is, maybe it makes sense to have the lexer just be
fn lex(input: &str) -> (Vec<Token>, Vec<Error>)

unless we're planning to add more features to it in the future?
(personally I also like the idea of a streaming lexer like in #115!)
Also spotted a few other clones in the parser that are not (or no longer)
necessary. Likely only the expect one has a chance of making a difference though.

now that the work to reverse the token list is done, it could be a good idea to revisit https://github.com/apollographql/apollo-rs/pull/115 or https://github.com/apollographql/apollo-rs/pull/322

yes! we were just talking about that on Monday. It's prioritised for the nearest of futures.


search-mod-01

@JKHeadley
I have tried to make the site look close to the existing mbt website.
There are minor differences. I guess they don't matter.
There is some leftover code, which I did not clean up at this point.

Looks great! This is perfect to give us a start. We can clean it up as we go. Thanks Sanjeev!


Binius integration

Problem
Binius is a high efficient snark proof over binary fields
See Vitalik's blog
implementation: https://gitlab.com/IrreducibleOSS/binius
Details

create ffi for
generate_binius_proof
and
verify_binius_proof
write down tests for binius proof

rust test
e2e test

documentation

how to add the adapter in a new app. e.g. halo2 adapter

Acceptance criteria

generate_binius_proof, verify_binius_proof works in mopro
tests pass

Next steps (optional)

mopro cli add the binius adapter

Hi vivian, i think we(me and my teammates) can handle this !


Codewars Red streak stats misbehaving again

For some days now my profile has said this --

-- even though I did some katas on the mornings (California time) of April 30, May 1, etc.

I'm about to go on vacation for 2 weeks, if I don't get to this by next Friday it may have to wait. I have a lot of things on my plate before I leave.
The streaks should also allow for 8 hours of padding (to compensate for some timezone issues) so its odd this is happening. Its also odd that your current streaks isnt showing up. If your streak high really had ended then it should also be showing you the status on your current streak.

No problem -- have a great vacation! My profile is https://www.codewars.com/users/tachyonlabs BTW.

Looks good now, thanks!

This is happening for me again ... my profile says

Even though I had done katas on October 4 in the early afternoon (California time) and evening. It seems to me that you're on UTC and therefore during daylight savings time here any katas I do after 5pm will be counted for what is for me the following day, but the early-afternoon one should have been counted as October 4.


No model for "changeShoppingListsConfiguration" project update action

Describe the bug
There is no model for "changeShoppingListsConfiguration" project update action
Expected behavior
Since this SDK is "generated from API reference" it seems reasonable to expect that it has models for all available update actions, including "changeShoppingListsConfiguration".
Stack information (please complete the following information):

Java: 11
SDK: 5.1.0

Having examined SDK generation process, I now realize that a bug should probably be opened in a commercetools-api-reference repository since there's no RAML definition for "changeShoppingListsConfiguration" action there.

Ah, I see. Thanks for explanation.
I also noticed that ProjectChangeShoppingListsConfiguration model was just added in #163 .
@jenschude Do you know if there is a plan for the next SDK release?

Yes next week 😄

That's great!
I'll close this issue then, since all the required changes are already in master.


Rebasing against master

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
patch
0m  6s
https://github.com/apache/hbase/pull/3282 does not apply to HBASE-24749. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/3282

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3282/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
patch
0m  5s
https://github.com/apache/hbase/pull/3282 does not apply to HBASE-24749. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/3282

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-3282/1/console

versions
git=2.17.1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Error text size is too small

🐛 Bug Report
Error text size is currently 9, but is hard to read. It should be bumped up to 11.

I have completed updating the tokens in the Nimble_Components DSP document to reflect the new typography changes for errors on controls; 11px Source Sans Pro.
I have also gone through each individual control for each UI theme and updated the error typography to use the correct tokens and adjusted the container height to 14px.

Duplicate of/Addressed with #775


Validation issue for +91<PHONE_NUMBER>

Country/region affected: IN
Example number(s) affected: +91<PHONE_NUMBER>
The phone number range(s) to which the issue applies: +918700XXXXXX
The type of the number(s): Mobile
The cost, if applicable ("toll-free", "premium rate", "shared cost"): Unknown
We've called this number. This is a Reliance Jio number.
http://libphonenumber.appspot.com/phonenumberparser?number=%2B918700983012

@anandAbhi ,
Thank you for taking the time to improve libphonenumber!
I have tried calling this number. I got automated message saying the number do not exists.
We are not able to find valid evidences for these numbers online.
Checked all popular recharge websites (like paytm.com). No website auto populates that it is Reliance Jio sim.
We need more information to fix this. Please see our contribution
guidelines.

@penmetsaa , I too Face the same problem as Anand Mentioned,
I am trying to Validate the Number Which Starts with +91 700 xxxxxxx which is valid Mobile number for the Country region code "IN" .
But When we try to validate the Number we are not able to save the Contact Number as it is mentioned as incorrect Mobile Number

@anandAbhi This issue is blocked on your or other GitHub contributors' input. Please help
us find evidence as requested by @penmetsaa. Otherwise we don't have enough information to
fix the issue and may have to close it as infeasible.
@anbarasuthresnathan This issue is about numbers beginning with 8700, not 700.
Please see our contribution guidelines and file a new issue if there is a problem with validation of 700 numbers.

Refer: https://en.wikipedia.org/wiki/Mobile_telephone_numbering_in_India#8xxx_Series

J stands for Jio
DL stands for Delhi
Will this be sufficient?

Refer: https://en.wikipedia.org/wiki/Mobile_telephone_numbering_in_India#8xxx_Series

J stands for Jio
DL stands for Delhi
Will this be sufficient?

Thanks, helpful. Any idea why we get an automated message but you can ring the number?

The number belongs to our friend. He rarely uses this number. We made sure the number was active when we called. We can arrange the same for you guys to validate.

Thanks for asking :)
No need actually. We found official evidence which mentions this prefix.
This fix will be part of upcoming release.

This is fixed in release 7.7.4
http://libphonenumber.appspot.com/phonenumberparser?number=%2B918700983012


Updated docs with accurate sample auth options

@apoggi-carecloud Thx again for your contribution. 🏆
Sry for taking that long to merge it.
I overlooked the fact that the sample was wrongly mentioning projectName instead of projectId.


Update assess-the-impact-of-security-configuration-changes-with-explo…

…rer.md
edited phish confidence level.

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

File
Status
Preview URL
Details

microsoft-365/security/office-365-security/step-by-step-guides/assess-the-impact-of-security-configuration-changes-with-explorer.md
:white_check_mark:Succeeded

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

@MSFTTracyP Please merge this PR. Thanks.

Docs Build status updates of commit 972ec2e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

microsoft-365/security/office-365-security/step-by-step-guides/assess-the-impact-of-security-configuration-changes-with-explorer.md
:warning:Warning

Details

microsoft-365/security/office-365-security/step-by-step-guides/assess-the-impact-of-security-configuration-changes-with-explorer.md

Line 18, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'mdo' is not valid with 'ms.prod' value 'm365-security'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Smartswitch (binance) pr #364

Description
Fixed smartswitch data frame syncing for coinbase
Fixed fast-sample for binanace and coinbase when smartswitch in enabled
Fixes #364
Type of change
Please make your selection.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] This change requires a new dependency
[ ] Code Maintainability / comments
[x] Code Refactoring / future-proofing

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added pytest unit tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Thanks for your work on this. Is it still being worked on or ready for merging?

Thanks for your work on this. Is it still being worked on or ready for merging?

This work is now complete 🙂


Value was not being passed to the label formatter as an array if present

Values passed in an array with a pre-formatted string were not being passed to the label formatter, only the first value from the array.
var data = [
    ['Teal',      [12000, 'USD 12,000']],
    ['Byzantium', [4000,  'USD 4,000']],
    ['Persimmon', [2500,  'USD 2,500']],
    ['Azure',     [1500,  'USD 1,500']],
];

Sorry for the delay @Ephemerality. Thanks for pointing this out and including the PR!
I generally only commit changes to /dist when a new version has been released, so I went ahead and made the change myself. I need to put this down in some contributing notes. I also added an appropriate test case.


feat: change database schema change

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


chore; use debug for pending tx log

Summary by CodeRabbit

Chores

Adjusted logging level for transaction processing messages to improve debugging granularity.

@Larkooo this is the only one annoying the logs, or we may have a quick pass on them?

@Larkooo this is the only one annoying the logs, or we may have a quick pass on them?

This should be main reason the logs fill up quick. As issue with logs only started happening when we enabled index pending to true by default. This is the one that gets spammed on networks like sepolia or mainnet


Disable repeated video data delete confirmation dialogue in Desktop

When dealing with many sequences, deleting data is a pain with confirmation dialogues on every delete. The information in the current delete dialogue should maybe only appear once, on the first user delete, or would be better suited for ? tooltip next to the delete button the user could hover over?

This is why we added a setting to turn of delete confirmation.  Did you use that?

@subdavis, is there anything blocking us from implementing checkbox-style mass delete on desktop?

Checkbox-style mass delete would not resolve this issue.
The ask is to also delete media from outside the DIVE project directory, which I'm very wary of doing.

Checkbox-style mass delete would not resolve this issue.
The ask is to also delete media from outside the DIVE project directory, which I'm very wary of doing.

I would agree with your wariness. Something halfway out-of-band might be good: remove the "deleted" items from DIVE's awareness, and generate a report of all filenames and give to the user so they can do an xargs | rm or equivalent by their own hand.


Fixed "Cannot read property 'focus' of undefined" in React-MD example

This issue was reported in the discussion to #940.
/cc @timneutkens @alexedev

great, thank you!


feat: actually release previous changes

Fix release: https://github.com/splunk/addonfactory-solutions-library-python/actions/runs/7712486609/job/21020305061#step:6:462

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


Issue on docs: no manual setup instructions

Path: /documentation/quickstarts/introduction
I tried to run @trigger.dev/cli@latest init in my project and it said that it couldn't do automatic setup. Then, it showed me a link to manual setup instructions, but there are no manual setup instructions on the linked page.

@danieldunderfelt which framework are you using? Was it one that wasn't on the page that was linked to?

I wasn't using any framework really. I am setting up my backend with Partykit (which runs on Cloudflare workers), and the Trigger app would be separate.
The issue isn't that my framework isn't listed, it's that the CLI tells me to go to a link for "manual instructions" but there are no such instructions on the linked page. There are no "here's how to set up Trigger without a framework" docs, and it is unclear why a framework is even needed.


Fixes bug causing 404 response due to Greek translation error

The Greek translation of the help_text in password field of UserChangeForm class (file: contrib/auth/forms.py), causes a 404 error when trying to change the password of a user, when following the available link.
By the way, I fixed a small typo, also!

Fixed in stable/1.11.x by e6bfd3d751278d7cfd09af1120c4bbce509c05da and in master by c52ae33a0c0c0bbaa460607a8787e95fe983a2b9.

To fix the translation mistake, use Transifex rather than GitHub. See Localizing Django for details.

Ok, Thank you!


Cannot update erlang to newer version

Cookbook version
4.0.0
Chef-client version
Chef: 12.4.3
Platform Details
CentOS 7:  3.10.0-327.13.1.el7.x86_64
Scenario:
Trying to install 19.1-1 version of erlang
Steps to Reproduce:
I'm trying to install RabbitMQ via  https://github.com/rabbitmq/chef-cookbook  they use this erlang cookbook as dependency.
Firstly, I used default version of erlang but some rabbitmq plugins does not work with it. So I updated erlang version in attributes as shown bellow:
default['erlang']['install_method'] = 'esl'
default['erlang']['esl']['version'] = '19.1-1'
default['rabbitmq']['esl-erlang_package'] = 'esl-erlang-compat-R1801-1.noarch.rpm?raw=true'
default['rabbitmq']['esl-erlang_package_url'] = 'https://github.com/jasonmcintosh/esl-erlang-compat/blob/master/rpmbuild/RPMS/noarch/'
But chef fails to update already installed erlang. I had to remove previous installation manually and then rerun chef client.
Expected Result:
erlang should be updated  if there is older version is installed
Actual Result:
Transaction check error:
file /usr/bin/epmd from install of esl-erlang-19.1-1.x86_64 conflicts with file from package erlang-erts-R16B-03.17.el7.x86_64
file /usr/bin/erl from install of esl-erlang-19.1-1.x86_64 conflicts with file from package erlang-erts-R16B-03.17.el7.x86_64
file /usr/bin/erlc from install of esl-erlang-19.1-1.x86_64 conflicts with file from package erlang-erts-R16B-03.17.el7.x86_64
file /usr/bin/escript from install of esl-erlang-19.1-1.x86_64 conflicts with file from package erlang-erts-R16B-03.17.el7.x86_64
file /usr/bin/run_erl from install of esl-erlang-19.1-1.x86_64 conflicts with file from package erlang-erts-R16B-03.17.el7.x86_64
file /usr/bin/to_erl from install of esl-erlang-19.1-1.x86_64 conflicts with file from package erlang-erts-R16B-03.17.el7.x86_64
file /usr/bin/dialyzer from install of esl-erlang-19.1-1.x86_64 conflicts with file from package erlang-dialyzer-R16B-03.17.el7.x86_64
file /usr/bin/typer from install of esl-erlang-19.1-1.x86_64 conflicts with file from package erlang-typer-R16B-03.17.el7.x86_64
file /usr/bin/ct_run from install of esl-erlang-19.1-1.x86_64 conflicts with file from package erlang-common_test-R16B-03.17.el7.x86_64

@aduckardt  Can you include the full output of the Chef run when it failed to upgrade?

@tas50 You can find chef log in attachments
erlang_cookbook error.txt

This seems to me that you're trying to go from ESL erlang to non-esl erlang which is yum is freaking out.

I'm closing this one as the logs indicate trying to switch from erlang to esl-erlang which isn't something the cookbook can easily support. If you want to use ESL builds, only use the ESL recipe and make sure distro Erlang packages aren't present.

yum remove erlang-erts-R16B-03.17.el7.x86_64


SearchServiceInstance not found

Hi there,
having an issue with creating new search topology: DSC returns error 'SearchServiceInstance is not found on server SP001.
Checked the instance on the server and it is online.
I'm usind SharePoint 2019 with German langiuage pack on Windows Server 2016.
SharePointDSC version is <IP_ADDRESS>
Any help is aprreciated...
Thanks in advance...

Hi @ThomasLie Can you please share your config and the Verbose output of the deployment?

Hi,
meanwhile we solved the issue, was due to a couple of group policies.
Regards
Thomas

Hi @ThomasLie, could you please share which policies caused this and what setting of those policies was the solution? This might be beneficial to others or we could include this in our documentation.

@ThomasLie Do you have the opportunity to share the policies that caused this issue?

Hi Yorik,
I‘m currently on vacation...going to share the GPO when I‘m back...
Mit freundlichen Grüßen / Kind regards
Thomas Lieftüchter
Lieftüchter IT-Consulting & Büroservices GbR
Ilse-Pohl-Str. 67
63303 Dreieich - Germany
Fon: +49<PHONE_NUMBER>
Email<EMAIL_ADDRESS>Web: http://www.lieftüchter.de/TL
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Von: Yorick Kuijs<EMAIL_ADDRESS>Gesendet: Wednesday, July 3, 2019 8:06:14 PM
An: PowerShell/SharePointDsc
Cc: Thomas Lieftüchter; Mention
Betreff: Re: [PowerShell/SharePointDsc] SearchServiceInstance not found (#1079)
@ThomasLiehttps://github.com/ThomasLie Do you have the opportunity to share the policies that caused this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/PowerShell/SharePointDsc/issues/1079?email_source=notifications&email_token=ALR4I435UK5F4AOZYKQYOCDP5TTBNA5CNFSM4HYYNWT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZFH64Y#issuecomment-508198771, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALR4I4462OMTMAXJXM62GS3P5TTBNANCNFSM4HYYNWTQ.

Hi @ThomasLie, are you able to share the GPO so we have the resolution of this issue properly documented>

Hi Yorick,
I discussed this with my client and I’m not allowed to share any information.
I’m sorry…
Mit freundlichen Grüßen / Kind regards
Thomas Lieftüchter
Lieftüchter IT Consulting & Büroservices GbR
Ilse-Pohl-Strasse 67
63303 Dreieich - Germany
Fon: +49<PHONE_NUMBER>
Email: thomas<EMAIL_ADDRESS>Web:  http://www.lieftüchter.de/TL
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Von: Yorick Kuijs<EMAIL_ADDRESS>Gesendet: Dienstag, 29. Oktober 2019 15:24
An: PowerShell/SharePointDsc<EMAIL_ADDRESS>Cc: Thomas Lieftüchter<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [PowerShell/SharePointDsc] SearchServiceInstance not found (#1079)
Hi @ThomasLiehttps://github.com/ThomasLie, are you able to share the GPO so we have the resolution of this issue properly documented>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/PowerShell/SharePointDsc/issues/1079?email_source=notifications&email_token=ALR4I44G4DUOPKPK47NVT23QRBBPZA5CNFSM4HYYNWT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECQVVAA#issuecomment-547445376, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALR4I43G7EKKVEVTSPE3SXLQRBBPZANCNFSM4HYYNWTQ.

That is too bad, would really help others in the future. Isn't only sharing the name of the policy and the value with which is breaks an option? Just so someone else in the future is able to check out that policy when running into the same issue.

Hi Yorick,
going to ask the client on Monday…one of the keywords is CredSSP ;-)
Mit freundlichen Grüßen / Kind regards
Thomas Lieftüchter
Lieftüchter IT Consulting & Büroservices GbR
Ilse-Pohl-Strasse 67
63303 Dreieich - Germany
Fon: +49<PHONE_NUMBER>
Email: thomas<EMAIL_ADDRESS>Web:  http://www.lieftüchter.de/TL
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Von: Yorick Kuijs<EMAIL_ADDRESS>Gesendet: Donnerstag, 31. Oktober 2019 14:10
An: PowerShell/SharePointDsc<EMAIL_ADDRESS>Cc: Thomas Lieftüchter<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [PowerShell/SharePointDsc] SearchServiceInstance not found (#1079)
That is too bad, would really help others in the future. Isn't only sharing the name of the policy and the value with which is breaks an option? Just so someone else in the future is able to check out that policy when running into the same issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/PowerShell/SharePointDsc/issues/1079?email_source=notifications&email_token=ALR4I4YUF5SEMF57PF45LCLQRLKIZA5CNFSM4HYYNWT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXWO6Q#issuecomment-548366202, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALR4I46OLGCW3RARLRLSB5DQRLKIZANCNFSM4HYYNWTQ.

Issue has been resolved, closing this issue. @ThomasLie if you are able to share the name of the policy and the value you had to configure to get it to work, please add this to the issue.

Hi Yorick,
a bit late...
My client disabled CredSSP completely...this caused some other issues as well...
Computer Configuration | Administrative Templates | System | Credentials Delegation
I good guide, how to configure CredSSP via GPO can be found here:
https://www.jfe.cloud/how-to-enable-credssp-for-powershell-remoting-through-gpo/
Regards,
Thomas


[impeller] Playground tests on macOS are strobing

WARNING: Reproducing this bug can cause distress and seizures.
details
engine hash: 0e23e60093d162e19108fcf28233f918fdafc136
platform: macos
reproduction
impeller_unittests --gtest_filter="*CanDrawPaint*Metal" --enable_playground
expected results
A window that draws a static solid color.
seen results
A window that strobes between white and black rapidly.  I tried to move the window and my have resized it on accident which caused it to stabilize onto a solid color.

I've seen it on other playgrounds as well.  I just saw it on CanDrawPaint.

I bisected the issue and here is the PR that introduced the bug https://github.com/flutter/engine/pull/52526
cc @bdero


new lock/unlock icons

Not sure about the shackle shape, the current, more geometric style fits the icon set better.


Incomplete libctx/propq support in X509 sigining

The X509 signing still relies on some legacy (non xx_ex) functions, so the digest/signature algorithm selection does not follow the given propq. This can be tracked down to the following:

The openssl req doesn't pass libctx/propq when signing the X509 CSR. It even cannot (see next item).

There is no X509_sign_ex with libctx/propq support.

The ASN1_item_sign_ex is "half-migrated" only. It takes libctx/propq (which is good), but it also takes EVP_MD as input and calls EVP_DigestSignInit (without passing the libctx/propq). In my view, the ASN1_item_sign_ex should take a const char* digest name instead and call EVP_DigestSignInit_ex, which already exists and takes also libctx/propq. This ensures the correct cipher selection, which then manages the digest.

X509_sign_ex() is not necessary as the X509 object can be setup with a libctx, propq.
ie ASN1_item_sign() should use ASN1_item_sign_ex() everywhere with x->libctx, x->propq.
In the apps all EVP_DigestSignInit() should be replaced with EVP_DigestSignInit_ex() so pkey is setup correctly.

Will be fixed by #14752


Added a unit test case

Changes:

Added one unit test case to JedisPool. Testing if it is allowing returning of same object twice.
Remove unused import from Connection.java
Ran 'make format' from command line. It adjusted few documentation comments.
Hope this small PR helps :)

@nvharikrishna thanks for the contribution. We've previously deprecated returnXXX methods of Jedis in favor of using jedis.close() directly. I believe we've missed the returnResourceObject from JedisPool.
What about making that method protected and encourage users only to return resources by calling jedis.close()?. Having multiple ways of doing the same thing it's quite confusing.
@HeartSaVioR any comments?

Thanks for contribution @nvharikrishna but I agree with @marcosnils.
We just missed changing Pool.returnResourceObject() to protected. It's better to fix it and after then PR becomes invalid.

With #971 and #972 it is not an issue now.