Fix repo links

Fixes incorrect links in the repository listing of a user profile, as described #3035.
This PR does not address the other points raised in #3035, e.g.

whether it makes sense to have "Show more repos" link to a user's profile page
whether it makes sense to initially show only a user's repos on their profile page, but include collaborative repos when searching on the profile page

Therefore, we probably should not close #3035 if/when this PR merged.

Codecov Report

Merging #3093 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3093   +/-   ##
=======================================
  Coverage   33.26%   33.26%
=======================================
  Files         273      273
  Lines       39954    39954
=======================================
  Hits        13290    13290
+ Misses      24768    24763    -5
- Partials     1896     1901    +5

Impacted Files
Coverage Δ

models/repo_indexer.go
47.52% <0%> (-1.49%)
:arrow_down:

models/repo.go
38.15% <0%> (-0.19%)
:arrow_down:

models/issue.go
45.05% <0%> (+0.19%)
:arrow_up:

models/error.go
32.72% <0%> (+0.61%)
:arrow_up:

models/issue_indexer.go
67.53% <0%> (+2.59%)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM

LGTM

Also fix #3148


feat:  default email alert group

Description
When new users join, there is no alerting configured by default. While this is the intended behavior for things like workflow runs which may be noisy, it may be problematic for alerts for token expiration.
This change adds additional configuration settings for alerts and exposes the tenant member list as a special email group.
Type of change

[x] New feature (non-breaking change which adds functionality)

What's Changed

[x] add tenant alert setting configuration to enable workflow run failure and token expiration alerts
[x] add tenant configuration to enable tenant member email alert group
[x] add query to get emails for a tenant
[x] update alerters with config
[x] expose config on ui


Method "check_ip_address_availability" returns always None regarding the status of IP

Method "check_ip_address_availability" returns always None regardless the status of IP.

Hi @igoro1975
Could you confirm the version of your package? There is an RestAPI version change between 0.30.0rc6 and 0.30.0, it would help to know what you use.
@derekbekoe @johanste did you experience that?
I'll take a look asap

Not reproduced under 0.30.0

If you're using 0.30.0rc6, please upgrade to 0.30.0. If you're using 0.30.0, please give more context so I can try to figure out why you have a problem and not me.

FYI, just added a unit test (indeed I didn't have time to add one when this feature arrived) with success.

Thank you @lmazuel. We do use 0.30.0rc6 version. I'll check it with 0.30.0 and update the issue.

@lmazuel , it works in the version 0.30.0.
But how can we "override" the dependencies now? azure-2.0.0rc6 has requirements for azure-mgmt==0.30.0rc6 and it has requirements for azure-mgmt-network==0.30.0rc6 but we need azure-mgmt-network==0.30.0.
Thank you.

It's not a real problem actually, you have two valid solutions:

Stop using the "azure" meta-package. This package is intended to have an "easy to start" step for the Azure SDK for Python. Usually, people only use some packages only and not every dependencies. My guess is you use it for VM (resource/compute/network/storage), so you can change:

azure==2.0.0rc6

to
azure-mgmt-resource~=0.31.0
azure-mgmt-compute~=0.32.0
azure-mgmt-network~=0.30.0
azure-mgmt-storage~=0.30.0

You save time and space on installation.

Upgrade Network only, pip does not forbid update

pip install azure==2.0.0rc6
pip install azure-mgmt-network==0.30.0

I guarantee to you, you will have not conflict of version, from 0.30.0rc2 to current 0.3x.y version, underlying runtime and dependencies are equivalent. Also, this page can give you an overview of how I present the current state of packages.
ETA for 2.0.0 stable is February 2017 (in sync with other languages, we wait for the final go from the core SDK team of Azure). I think I will publish a 2.0.0rc7 in January after the holiday time, because there is currently too much gap between 2.0.0rc6 and the latest package of each service. I initially hoped to go directly from 2.0.0rc6 to 2.0.0, but unfortunately this wasn't possible,,, Sorry for the inconvenience caused by that... Be sure I do my best for the best user experience, it's why I published asap every service update as individual package.

Hi @igoro1975 , could we close the issue? Thank you,

I close this issue due to inactivity and I humbly think the problem is solved. Please add a comment here or open a new issue if you still experiment some problem. Thank you.


Rework GetSelector type inference

What
Rework how type inference works for GetSelector. The final inferred type is unchanged, just how the type inference helpers arrive at the type has changed.
Why
This will allow us to add a new selector to GetSelector via conditional compilation.
See https://github.com/Azure/communication-ui-library/pull/1927 for an example of how a new selector can be added.
How Tested
Added new type assertions to get build time coverage.
Is this a breaking change?
Confirmed that this is not considered a breaking API change.

Not needed right now because we're unblocked by https://github.com/Azure/communication-ui-library/pull/1942
#1942 is a workaround for now. We should solve this in a way that we don't require beta-only types.
But I prefer the approach in #1940 over this  one.

Decided to keep the current types and support conditional compilation for another AST node: https://github.com/Azure/communication-ui-library/pull/1967


add serde generic serialization as an optional feature

also update the CI to test the new added serde implementations
here, serde is added as an optional dependency. It not meant to be used to store the blockchain in a generic format (this would be a bad design choice as it will certainly store excessive metadata and will end up taking more and more storage).
The serde instances are used to standardise some interfaces that we will have on the side:

REST API (json, ...);
configuration files (yaml, ...);
inter process (bincode, ...).

closing this PR, this is a mistake to add serde to the low level library.


OSX install fails after homebrew installation of libgroove [node-gyp rebuild failure]

Hi,
This seems linked to issue #15 but I've tried the advice listed there with no luck.
I've installed libgroove and all the listed dependencies (pkg-config, texi2html, yasm, x264, lame, libvo-aacenc, xvid, libogg, libvorbis, ffmpeg, chromaprint, speex, libebur128, sdl2) via homebrew. When I try running:

npm install groove

I get the following error:

../src/file.h:6:10: fatal error: 'groove/groove.h' file not found
#include <groove/groove.h>
^
1 error generated.
make: *** [Release/obj.target/groove/src/groove.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-> gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Darwin 14.3.0
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/maq/source/workspace/JukeboxServer/node_modules/groove
gyp ERR! node -v v0.12.4
gyp ERR! node-gyp -v v1.0.3
gyp ERR! not ok
npm ERR! Darwin 14.3.0
npm ERR! argv "node" "/usr/local/bin/npm" "install" "groove"
npm ERR! node v0.12.4
npm ERR! npm  v2.10.1
npm ERR! code ELIFECYCLE

I've also tried building from source which installs into /usr/local/ - but still no luck running npm install:

-- Installing: /usr/local/lib/libgroove.a
-- Installing: /usr/local/include/groove/groove.h
-- Installing: /usr/local/include/groove/queue.h
-- Installing: /usr/local/include/groove/encoder.h
-- Installing: /usr/local/lib/libgroove.4.3.0.dylib
-- Installing: /usr/local/lib/libgroove.4.dylib
-- Installing: /usr/local/lib/libgroove.dylib
-- Installing: /usr/local/include/grooveplayer/player.h
-- Installing: /usr/local/lib/libgrooveplayer.4.3.0.dylib
-- Installing: /usr/local/lib/libgrooveplayer.4.dylib
-- Installing: /usr/local/lib/libgrooveplayer.dylib
-- Installing: /usr/local/lib/libgrooveplayer.a
-- Installing: /usr/local/include/grooveloudness/loudness.h
-- Installing: /usr/local/lib/libgrooveloudness.4.3.0.dylib
-- Installing: /usr/local/lib/libgrooveloudness.4.dylib
-- Installing: /usr/local/lib/libgrooveloudness.dylib
-- Installing: /usr/local/lib/libgrooveloudness.a
-- Installing: /usr/local/include/groovefingerprinter/fingerprinter.h
-- Installing: /usr/local/lib/libgroovefingerprinter.4.3.0.dylib
-- Installing: /usr/local/lib/libgroovefingerprinter.4.dylib
-- Installing: /usr/local/lib/libgroovefingerprinter.dylib
-- Installing: /usr/local/lib/libgroovefingerprinter.a

It's been a long time since I've done anything much with C - Do you have any advice about what I need to do. Should I be setting an environment variable like LD_LIBRARY_PATH?

Installing libgroove via homebrew and then node-groove via npm should work out of the box. If it doesn't then there's something about OSX that I don't understand (which is not surprising since it's not my main OS). I don't know how to fix this, but when I get some time I'll fiddle around with my mac to try to find out.

Got same error in Ubuntu 15.04.

@DonSinDRom Ubuntu 15.04 comes with libgroove. Just use sudo apt-get install libgroove-dev libgrooveplayer-dev libgrooveloudness-dev libgroovefingerprinter-dev.

Thanks for offering to look into this when you have time. I've downloaded and un-tarred the npm package. After adding /usr/local/include to the "include_dirs" sectiion of binding.gyp, I now get the following error:
maq-C02PR3Q8FVH8:temp maq$ npm install node-groove-2.4.0
\
><EMAIL_ADDRESS>install /Users/maq/temp/node_modules/groove
> node-gyp rebuild

  CXX(target) Release/obj.target/groove/src/groove.o
  CXX(target) Release/obj.target/groove/src/file.o
  CXX(target) Release/obj.target/groove/src/playlist.o
  CXX(target) Release/obj.target/groove/src/player.o
  CXX(target) Release/obj.target/groove/src/playlist_item.o
  CXX(target) Release/obj.target/groove/src/loudness_detector.o
  CXX(target) Release/obj.target/groove/src/fingerprinter.o
  CXX(target) Release/obj.target/groove/src/encoder.o
  SOLINK_MODULE(target) Release/groove.node
ld: library not found for -lgroove
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Release/groove.node] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/maq/.node/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Darwin 14.4.0
gyp ERR! command "node" "/Users/maq/.node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/maq/temp/node_modules/groove
gyp ERR! node -v v0.12.7
gyp ERR! node-gyp -v v2.0.1
gyp ERR! not ok
npm ERR! Darwin 14.4.0
npm ERR! argv "node" "/Users/maq/.node/bin/npm" "install" "node-groove-2.4.0"
npm ERR! node v0.12.7
npm ERR! npm  v2.13.0
npm ERR! code ELIFECYCLE

Looks like the problem was caused by me forgetting to install x-code command line tools. Sorry for wasting your time.

Thanks for telling me what it was. Now if someone else reports this issue on any of my projects I can offer this troubleshooting tip.

@andrewrk
donsindrom@0xn:~$ npm install groove -g
\

<EMAIL_ADDRESS>install /usr/lib/node_modules/groove
node-gyp rebuild

make: Entering directory '/usr/lib/node_modules/groove/build'
CXX(target) Release/obj.target/groove/src/groove.o
../src/groove.cc: In function ‘void Initialize(v8::Handlev8::Object)’:
../src/groove.cc:86:51: error: ‘GROOVE_EVENT_DEVICEREOPENED’ was not declared in this scope
SetProperty(exports, "_EVENT_DEVICEREOPENED", GROOVE_EVENT_DEVICEREOPENED);
^
groove.target.mk:94: recipe for target 'Release/obj.target/groove/src/groove.o' failed
make: *** [Release/obj.target/groove/src/groove.o] Error 1
make: Leaving directory '/usr/lib/node_modules/groove/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Linux 3.19.0-21-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/lib/node_modules/groove
gyp ERR! node -v v0.12.6
gyp ERR! node-gyp -v v2.0.1
gyp ERR! not ok
npm ERR! Linux 3.19.0-21-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "groove" "-g"
npm ERR! node v0.12.6
npm ERR! npm  v2.11.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the groove package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls groove
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/donsindrom/npm-debug.log

See #18

@andrewrk It works. Thanks.


fix(navbar): remove ul that's a direct child of a ul

Will fix https://github.com/zopaUK/react-components/issues/683
Also adds axe tests to the navbar dropdown component

:tada: This PR is included in version 4.43.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


This plugin is great but Lightning Charge installation and configuration is way to complicated

This plugin is great but Lightning Charge installation and configuration is way to complicated for the average Wordpress admin.
Could third parties provide Lightning Charge servers and charge a small fee for this service? No one is going to install this if they have to run, secure and maintain a complicated Linux node.
This plugin is still a huge step forward, history being made.

Yes, I agree, setting up Lightning Charge as a separate standalone server is not for the average WordPress user. This does require some tech savviness and sysadmin experience.
Third parties can definitely offer a hosted version of Lightning Charge to make that easier, if you're okay trusting them to hold funds on your behalf. I don't have any plans of offering such services.
Note, however, that the setup isn't really all that complicated. If you're comfortable with command line, have some experience managing servers over SSH and familiar with Docker, getting Lightning Charge to run is basically as simple as writing these two commands:
$ mkdir data
$ docker run -u `id -u` -v `pwd`/data:/data -p 9112:9112 \
             -e API_TOKEN=mySecretToken \
             shesek/lightning-charge

This will setup everything up and start Lightning Charge on port 9112 with mySecretToken as the API access token.
The docker image comes bundled with bitcoind+lightningd+lightning-charge, so you don't have to pre-install anything other than Docker itself.

@NicolasDorier also made an awesome one-click azure deployment solution. An instructional video is available here.

I still need to update it, will do this week. Lightning has issues with LND right now it seems from my users.


Add a joke as one of the possible joke responses

Feature description:
Add the following joke: "Did you hear about the mathematician who's afraid of negative numbers? He'll stop at nothing to avoid them."
Any ideas on how to implement it?
This joke can be added to the local data json files.

#1096 https://github.com/swapagarwal/JARVIS-on-Messenger/pull/1096

Hello I have added the following joke!

which branch should I have a PR?


Can't see any testnet releases.

I was trying to use this guide https://neoxa.net/smartnode-testnet/ , but can't find any win/linux testnet releases (neoxa-testnet-win64.zip, neoxa-testnet-linux64.zip). What should I do? May be need actualize this guide?

This is being updated right now.
You can use the latest release for testnet.


CLI auto-doc generator

CLI docs are currently split over two repositories:

In the source code https://github.com/keptn/keptn/blob/a5fec7bd69bcb33129114835cd28ada8582a2645/cli/cmd/configure.go#L8-L13
In the Keptn Docs: https://github.com/keptn/keptn.github.io/blob/master/content/docs/0.6.0/reference/cli/index.md#keptn-configure-domain

This is sub-optimal, and we should automatically generate CLI docs and put them into the Keptn Docs.
Open questions
Should we automatically sync the CLI docs to keptn.github.io? Is that even possible? Alternatively, can we use some automation in keptn.github.io to fetch the current CLI docs "on demand" for the current folder (e.g., docs/0.6.0/reference/cli)?
Definition of Done

[ ] Compare existing docs from keptn/keptn.github.io with the ones written in the CLI, and make sure the CLI docs now have all the inforation required
[ ] Auto generate docs from the CLI, and verify that the content is the same as currently in keptn.github.io

Cobra can generate docs: https://github.com/spf13/cobra#generating-documentation-for-your-command

The part

Auto generate docs from the CLI, and verify that the content is the same as currently in keptn.github.io

still needs automation


Phase noise

Context:
We need a PhaseNoise gate in MM
Description of the Change:
Adds PhaseNoise in Fock representation
Benefits:
We have the PhaseNoise gate at least in Fock representation
Possible Drawbacks:
No Gaussian implementation possible means that when it's applied, all the rest gets converted to Fock representation
Related GitHub Issues:
None

Thanks a lot for the prompt delivery, @ziofil! Very impressive!
I just tested this and I ran into errors whenever I defined a circuit with the Attenuator gate occurring after the new PhaseNoise gate.
For illustration, running this code:
circuit = (
    Sgate(0.456, modes=[0, 1])
    >> Attenuator(0.234, modes=[0])
    >> PhaseNoise(0.123, modes=[0])
    >> Attenuator(0.234, modes=[0])
)
state = Vacuum(2) >> circuit

will throw this error:
...
...
File ~/Code/MrMustard/mrmustard/math/tensorflow.py:387, in TFMath.hermite_renormalized(self, A, B, C, shape)
    384 if isinstance(shape, List) and len(shape) == 1:
    385     shape = shape[0]
--> 387 poly = hermite_multidimensional(
    388     self.asnumpy(A), shape, self.asnumpy(B), self.asnumpy(C), True, True, True
    389 )
    391 def grad(dLdpoly):
    392     dpoly_dC, dpoly_dA, dpoly_dB = tf.numpy_function(
    393         grad_hermite_multidimensional, [poly, A, B, C], [poly.dtype] * 3
    394     )

File ~/.conda/envs/xanadu/lib/python3.10/site-packages/thewalrus/_hermite_multidimensional.py:101, in hermite_multidimensional(R, cutoff, y, C, renorm, make_tensor, modified, rtol, atol)
     99 dtype = np.find_common_type([Rt.dtype.name, yt.dtype.name], [np.array(C).dtype.name])
    100 array = np.zeros(cutoffs, dtype=dtype)
--> 101 array[(0,) * num_indices] = C
    103 if renorm:
    104     values = np.array(_hermite_multidimensional_renorm(Rt, yt, array))

IndexError: too many indices for array: array is 2-dimensional, but 4 were indexed

The snippet runs fine if I comment out either the PhaseNoise gate or the bottom Attenuator gate. I tested a few other constellations and so far it seems it's really only the Attenuator gate that doesn't like to occur after PhaseNoise. Also, I can make the above snippet work if I reduce it to a one-mode circuit.
So to sum it up, this error seems to occur when PhaseNoise is followed by Attenuator in a circuit that involves more than one mode.

Thank you Fabian! The issue was with the cutoffs passed to the choi method of Transformation. It is now fixed.


Fixed text box issue ! #1043

Hello PR,
Fixes #1043
Issue fixed(for both dark & light mode) & I also customize it by adding background color and shadow for both dark and light mode like other text boxes -
Before -

After -

Pull Request Checklist

[x] I have added screenshots and videos to show before and after the working of my code.
[x] I have ensured that the screen size is set to 100% while making the video.
[x] I have synced the latest fork with my local repository and resolved any conflicts.
[x] I have mentioned the issue number which I created before making this PR .(format to mention issue number is : fixes #(issue number) )
[x] I understand that if any the above conditions are not met , my PR will not be MERGED .

@hiteashgupta1 kindly upgrade the level 1 to 2, because I fixed main text issue & I also customize it by adding background color and shadow for both dark and light mode like other text boxes


skypeforlinux: <IP_ADDRESS> -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for skypeforlinux is: Linux client for Skype
meta.homepage for skypeforlinux is: https://www.skype.com
meta.changelog for skypeforlinux is: https://support.microsoft.com/en-us/skype/what-s-new-in-skype-for-windows-mac-linux-and-web-d32f674c-abb3-40a5-a0b7-ee269ca60831
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS> with grep in /nix/store/f833b6jc9mnjq7jka713vp4ndl1rlc1b-skypeforlinux-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/f833b6jc9mnjq7jka713vp4ndl1rlc1b-skypeforlinux-<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

skypeforlinux

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/f833b6jc9mnjq7jka713vp4ndl1rlc1b-skypeforlinux-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A skypeforlinux https://github.com/r-ryantm/nixpkgs/archive/1ed2d040b18ac917207912f04a34d25d9087d198.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1ed2d040b18ac917207912f04a34d25d9087d198#skypeforlinux

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/f833b6jc9mnjq7jka713vp4ndl1rlc1b-skypeforlinux-<IP_ADDRESS>
ls -la /nix/store/f833b6jc9mnjq7jka713vp4ndl1rlc1b-skypeforlinux-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

skypeforlinux

Maintainer pings
cc @PanAeon @jraygauthier for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for skypeforlinux is: Linux client for Skype
meta.homepage for skypeforlinux is: https://www.skype.com
meta.changelog for skypeforlinux is: https://support.microsoft.com/en-us/skype/what-s-new-in-skype-for-windows-mac-linux-and-web-d32f674c-abb3-40a5-a0b7-ee269ca60831
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS> with grep in /nix/store/qmx20qkgg9ijfbg7jcpzf2qf8lhalbad-skypeforlinux-<IP_ADDRESS>
found <IP_ADDRESS> in filename of file in /nix/store/qmx20qkgg9ijfbg7jcpzf2qf8lhalbad-skypeforlinux-<IP_ADDRESS>

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

skypeforlinux

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qmx20qkgg9ijfbg7jcpzf2qf8lhalbad-skypeforlinux-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A skypeforlinux https://github.com/r-ryantm/nixpkgs/archive/6186bea91f6e97b39153ba77d55808c2e4c65e2d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/6186bea91f6e97b39153ba77d55808c2e4c65e2d#skypeforlinux

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qmx20qkgg9ijfbg7jcpzf2qf8lhalbad-skypeforlinux-<IP_ADDRESS>
ls -la /nix/store/qmx20qkgg9ijfbg7jcpzf2qf8lhalbad-skypeforlinux-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

skypeforlinux

Maintainer pings
cc @mjoerg for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


TecnoScan change their domain

Source information
Tecno Scan 1.4.36
Source language
Spanish
Steps to reproduce
1.Open Mihon
2.Go to extensions section
3.Find tecno scan and open them
4.Go to Open in Webview
5.Read and click in the link placed in the text
Expected behavior
Open the Tecnoscan source
Actual behavior
Not open the tecno scan source cause they are moved to other website
Mihon/Tachiyomi version
Beta r6654
Android version
11
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Closing in favor of #2646


More detail in error message when peering fails.

 From here https://github.com/zettajs/zetta/blob/master/lib/web_socket.js#L92-L95
Probably should at least supply the status code returned.

Fixed in #304


Tidy up branches in data models repo

Review and tidy these up, as needed. Consider any documentation or guidance that we want to add around branches and branch usage for this repo.

The following unused and feature related branches were removed:

data-models (stale/no longer in use)
nov-updates-ob (previously merged feature)
ste-model (previously merged feature)
minimal-models (no longer needed)

The remaining branches (use moving forward):

data-models-dev (staging repo for gathering all model updates related to current release/sprint)
main (production model, used to create releases)

For model development moving forward, I propose that:

we follow the Contribution Guide in the MC2 onboarding docs
use issue-based naming of branches, where applicable (e.g., 46-tidy-branches)
create PRs to merge the feature/issue branches for the sprint into data-models-dev
related to issue #40, we can run data model checks on the dev branch, to minimize the chance of errors being propagated to the main repo
after all PRs are merged and the dev branch passes all checks, merge dev --> main and create the new release, update the DCA config, etc. (steps 6 and 7 in the curation workflow defined previously)

Comments above to be included in further procedures/documentation, tracked in https://github.com/mc2-center/data-models/issues/51


Build timings

Adds timings to build steps so that we can know how long they are taking, so that we can improve them.
Additionally changes our build so that it uses the Nix version of the indexer to run the Tier-2 testing. This is so that we test that version - which is the one that is intended to be eventually distributed on an OCI image.

I have tested this on the machine that runs the Tier-2 tests, FYI, to reduce the likelihood that it will break the Tier-2 pipeline.


Binding to UNIX sockets results with RangeError

Using the first two examples (edited below) with axon v2.0.2 I replaced the port number 3000 with a UNIX socket path. 'unix://'+__dirname+'/axon.socket' will complete to unix:///axon_test/axon.socket
receiver.js
var axon = require('axon');
var sock = axon.socket('pull');

sock.connect('unix://'+__dirname+'/axon.socket');

sock.on('message',(msg) => console.log(msg.toString()));

pusher.js
var axon = require('axon');
var sock = axon.socket('push');

sock.bind('unix://'+__dirname+'/axon.socket');

console.log('push server started');

setInterval(() => sock.send('hello'), 150);

I end up with the following...
[root@centos7 axon_test]# node receiver.js
net.js:924
      throw new RangeError('port should be >= 0 and < 65536: ' + port);
      ^

RangeError: port should be >= 0 and < 65536: NaN
    at lookupAndConnect (net.js:924:13)
    at Socket.connect (net.js:901:5)
    at Socket.connect (net.js:862:37)
    at PullSocket.Socket.connect (/axon_test/node_modules/axon/lib/sockets/sock.js:294:8)
    at null._onTimeout (/axon_test/node_modules/axon/lib/sockets/sock.js:279:12)
    at Timer.listOnTimeout (timers.js:89:15)
[root@centos7 axon_test]#

...the pusher.js will run all the way through.

@METACEO
Ran into the same issue.
In my case this only happened if my equivalent of your pusher was not running before the receiver attempted to connect.


feat: useEffect is not for effects

What's the purpose of this pull request?
This PR uses https://github.com/vtex/faststore/pull/1391

After applying the same changes from nextjs.store starter, I decided to merge this to avoid mismatches between starters. If you want @eduardoformiga, we can iterate on this one later on


Fixed expandable content bug when asynchronously re-rendering Table

Changes

As reported in this issue (https://github.com/iTwin/iTwinUI/issues/2300), the expandable contents were broken due to the WeakSet data structure internally that we used in this PR to fix the issue regarding virtualization. However, due to the problem of stale data within the WeakSet between re-renders, another approach is used in this PR, where we added a Symbol property to mark each sub-row generated so that our getSubRowsWithSubComponents will not get caught in an infinite loop.
Additionally, as the user passed in the getRowId, this function got into a loop due to the duplicated IDs of both main rows and sub-rows. Therefore, we added a wrapper function to append the ID passed by users into the row's according ID conditionally generated based on the information of its parent.
Testing

Before this PR, when data is asynchronous fetched, the sub-components show up in place of the main rows as Table is re-rendered.

After the fix, the sub-components now are correctly rendered.

https://github.com/user-attachments/assets/a4a0fe87-2a63-40a3-9a0b-ce3121182cca
Docs

Added patch changeset.

Co-authored-by: Mayank<EMAIL_ADDRESS>Co-authored-by: Vykis<EMAIL_ADDRESS>Co-authored-by: Rohan<EMAIL_ADDRESS>


[IOTDB-2355] Wildcard adaption

Description
Problem
** in SQL is incompatible with v0.12
Solution
Add isPrefixMatch functions to process requests from client of v0.12

Coverage increased (+0.02%) to 68.076% when pulling 17ed4a2d979e67c2b39537f9216ed4536f984dbd on zyk990424:wildcard_adaption into 2f49925eb06055e85bc2495838783b01d6dc192b on apache:master.


Add support for fragment in HttpRequest

Currently there's no way to get to the fragment in an HttpRequest

@Eilon, my particular usage is to redirect the client to a known fragment. This has to be more common as more and more people are using SPA. Currently, when I try to create a PathString with a fragment in the URI, it gets encoded, which is not really what I want.

When generating redirects do not put the fragment into the PathString, append the fragment after the path like this: https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Http.Extensions/UriHelper.cs#L24

Ah, missed that little gem. Thanks


What is the size of the style code in global directions

I am curious about the size of the style code . And after we got Δs， should we normalize it to a unit norm?

were you able to reproduce the results for style code editing variant of styleclip?


Accept Russian Data Intensive Grid certs

GOC ticket here: https://ticket.opensciencegrid.org/31952
We should think about adding something to the documentation so that users can identify the host cert not being in the map file as an issue and how to add a regex to the condor_mapfile themselves.

I hate that we have to do this for every different certificate.  @bbockelm , is there a better way?

We actually have a ticket here but it hasn't gone anywhere. Idk if we've got a technological solution so perhaps we can solve this through some documentation (or at least have something we can point users to).

Oops, this fell by the wayside. Any objections to merging this?

go for it!
-Derek

On Jan 19, 2017, at 11:28 AM, Brian Lin<EMAIL_ADDRESS>wrote:
Oops, this fell by the wayside. Any objections to merging this?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.


Error using preFetch data!

when i use prefetch the data is persisted in vuex perfectly but devtools do not update the state
data in state

devtools showing state

thanks! fixed in 5.0.5


UNIT Test fix

Error when writing the get_context function
.signer_account_id("bob_near".try_into().unwrap())

fixed it by using a std::String and changing the line to
.signer_account_id("bob_near".to_string().try_into().unwrap())

Does this deserve a PR?

Fixed in https://github.com/near/sdk-docs/commit/0fdd780a14e030438ba12bb50a3db3083f35e872


[BindingBehavior] and subclasses are ignored on page model properties

Found while verifying #6811.
Though IsBindingAllowed and IsBindingRequired are likely now set correctly in ModelMetadata -- as part of the #6790 fixes, [BindRequired], [BindNever] and so on do not impact model binding of page model properties.
For example
[BindProperty(SupportsGet = false)]
[BindRequired]
public string Required { get; set; }

works as expected if the Required property is in a controller. But no model error occurs when the same property is in page model. (In both cases, the form does not include an <input/> field for Required.)

Note this issue basically means #6811 was not fixed.

@dougbu, looking through the details of the referenced issue it seems it was closed intentionally, without any action as that was called out as the best approach - to do nothing.
@pranavkm, is this a valid exception, or this should still be acted on so we get to consistency between Controllers and Razor Pages?

Might be a dup of https://github.com/aspnet/Mvc/issues/7358, although it would be good to verify this and add tests to cover this specific scenario.

#7358 is about [Validation] subclasses while this is about [BindRequired]. It's still possible fixing #7358 fixed these too. Or, another of our changes in this area may have fixed [BindRequired] in page model scenarios.
Should check if these symptoms occur with Preview 2 bits.

@kichalla, can you please evaluate whether this is still the case, and whether there is still any action here or not.

This was addressed as part of https://github.com/aspnet/Mvc/issues/7358. What it does need is a test or two.

a6199bbfba


Move simulations report from boreal-caribou-23 repo and into bbousuite article

using figures generated from analysis in output folder and adding figures/tables manually rather than using subreport pkg
added discussion section for some key takeaways and expanded background section a bit

any further updates will be done on dev branch


Italian Fiscal Code regex

⚠ Pull Requests not made with this template will be automatically closed 🔥
Prerequisites

[x] Have you read the documentation on contributing? https://github.com/bee-san/pyWhat/wiki/Adding-your-own-Regex

Why do we need this pull request?
Regex for Italian fiscal code (https://en.wikipedia.org/wiki/Italian_fiscal_code).
What GitHub issues does this fix?
None.
Copy / paste of output
Please copy and paste the output of PyWhat with your new addition using an example that tests this addition below:
$ pywhat "RSSMRA00A01H501C"
Matched on: RSSMRA00A01H501C
Name: Italian Fiscal Code
Description: https://en.wikipedia.org/wiki/Italian_fiscal_code

Codecov Report

Merging #243 (83cb8ac) into main (1e843aa) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #243      +/-   ##
==========================================
- Coverage   92.60%   92.59%   -0.02%
==========================================
  Files          15       15
  Lines        1217     1215       -2
==========================================
- Hits         1127     1125       -2
  Misses         90       90

Impacted Files
Coverage Δ

tests/test_click.py
98.37% <100.00%> (+<0.01%)
:arrow_up:

tests/test_regex_database.py
88.57% <0.00%> (-0.32%)
:arrow_down:

pywhat/what.py
81.52% <0.00%> (-0.20%)
:arrow_down:

pywhat/printer.py
77.69% <0.00%> (-0.16%)
:arrow_down:

tests/test_regex_identifier.py
96.42% <0.00%> (-0.13%)
:arrow_down:

tests/test_filtration.py
95.23% <0.00%> (-0.06%)
:arrow_down:

Continue to review full report at Codecov.

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

Also, please squash the commits.


Add Paralus as an application to CIVO Marketplace

This issue is a:

[ ] Bug Report
[ ] Enhancement suggestion
[x] Feature request

If the issue concerns an existing Marketplace application, please tag the maintainer of the application (found in manifest.yaml) below:
Enhancement suggestions / feature requests
If you are requesting an enhancement to a feature already present, or a new feature, please outline below the feature you would like to see, and how it would benefit you and the wider Civo Kubernetes userbase:
I would like to add the popular Paralus as an additional application for the Civo Marketplace.

@saiyam1814
I think this issue should be closed, the paralus app was added via

https://github.com/civo/kubernetes-marketplace/pull/469

cc: @kunal-kushwaha


The description field is not filled in when you are at the board view

Hello! I am facing the following problem. The development team I work with creates stories by using the board view and pressing the inline create issue button. As you can see in the video even though the "Create Issue" on top of the page works like a charm, the inline button does not. Is there a workaround for it? Some url that I can add to the domains? Or something similar?
VIDEO HERE

Hello @cstergianos
The extension is currently programmed to only inject into the create-issue-dialog modal and the create-subtask-dialog modal. There will be some difficulties in getting inline injection working since how/where the Issue Type and Project Key are located is significantly different than in the modal. We do welcome Pull Requests if you are able to tackle those problems. A good starting point would be here: https://github.com/rdbrck/jira-template-injector/blob/master/src/jti_content.js#L244
I will create a ticket for us to add this in the future, but there is no immediate time frame for this.
Thanks for your feedback!


[BUG] AI not spawning in system

Attestation
[ ] I have verified this bug with all other mods disabled
[ ] I am not using one of the documented incompatible mods
[ ] I have confirmed this happens after verifying the games files
[ ] I was using the latest graphics drivers
Describe the bug
When I play on the Galatic War, enemy Commanders do not spawn at the start of the system. I and my sub-commanders are the only ones that spawn. By the time the intro sequence ends and I get to the surface, It brings up the "Victory" soundcard and gives me the win card. Why this happens I don't know, and I don't like the fact that I have to play around Tech landmines that break the game if I take them
To Reproduce
I have found this error to happen when I have more than 2 Sub-Commanders, and I have the Commander Duplication Tech.

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behaviour
I can play the game Normally
Screenshots

GWO Info
Taken from the top-right GWO panel:

Version: Current
Difficulty: Diamond
Size: Huge
AI:
Options:

Additional context
Logs
Please attach the most recent client and server log immediately following the bug occurring.

Please update the issue with required attestations, steps to reproduce, GWO Info, and logs.

encountered same issue with no apparently cause of issue.
my tab

Log:
server-2022-07-14_175225.txt

@laodie666 please open a new issue with details

This should be fixed by https://github.com/Quitch/GW-AI-Overhaul/commit/fc40b72bd6d9921b861d9ef944ea5bc92ce64092


Alex  mobile UI updates game code

addresses both item #480 (UI updates on game code) and #479 (UI updates on player name)


is Search delegatable?

the Search function is not listed in the table of delegatable functions like in other connector documentation, but it seems to delegate to data verse tables.  wondering if docs need updating

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

ID: b6ef9b3a-5d99-1ca0-0e7f-80c2de740313
Version Independent ID: 80900e35-c8da-10a1-9902-343e84d823d0
Content: Connect to Microsoft Dataverse - Power Apps
Content Source: powerapps-docs/maker/canvas-apps/connections/connection-common-data-service.md
Service: powerapps
Sub-service: canvas-maker
GitHub Login: @tapanm-MSFT
Microsoft Alias: lanced

Thanks for your comment, @drdamour. This issue has been assigned to the doc author for review.

@drdamour I'm looking into this and will get back to you as soon as I hear back.
Thanks,
Mints

I'm not the author here but has there been any updates on this?

@drdamour
The table has been updated for delegation of sort by columns, sort, and in membership.
Thanks you,
Mints

@mduelae but nothing was added about the search function which is why this was opened in the first place, can you please explain

Search is delegable to both Dataverse and SQL Server.  Both are documented.  Search is basically an in / contains operation on multiple fields.  Not all data sources support the Or'ing necessary to support this properly.

See here:  https://learn.microsoft.com/en-us/connectors/sql/#power-apps-functions-and-operations-delegable-to-sql-server  for SQL Server and here for Dataverse: https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/connections/connection-common-data-service

@drdamour - sorry about the confusion. Now the table has been updated with the search function.
https://learn.microsoft.com/en-us/power-apps/maker/canvas-apps/connections/connection-common-data-service#power-apps-delegable-functions-and-operations-for-dataverse
Thanks.

Looks good now, thanks


ContainerInvalidImage on Azure Nodes Standard F8s_v2

Hello Im not able to bake, my nodes turn to unusable and spit the following error.

operating system: microsoft-azure-batch ubuntu-server-container 20-04-lts (latest)

@mozahzah we've been able to reproduce this issue on our end and it appears to be an issue with the Microsoft Container Registry which hosts the Docker images for the toolset.  We are following up with the Microsoft Container Registry devs to figure out the root cause of this issue.  We'll let you know as soon as we find anything out.

@mozahzah it appears that there has been a change to the way the container image name is parsed that we are looking into.  Please update the Toolset Version in the Azure Configuration settings to specify a lower case "M" for the word Microsoft.
e.g.: mcr.microsoft.com/acoustics/baketools:2.0.143_Linux
This update to the parameters should allow Azure Batch to pull the image from the Microsoft Container Registry (MCR) correctly.  Sorry for the inconvenience.

@NoelCross Thank you for taking the time to investigate! appreciate it!


ImportError: No module named 'MySQLdb'

I have a MySQL running already on my Raspberry Pi.  I have created a DB and tables in it.
On python program, I tried to connect to it but I got this error.

@rfonacier, I'm afraid that the issue tracker here is for questions regarding the easysnmp library. We cannot help you with questions/problems in trying to get code working for other projects. If you need assistance, I would recommend posting at help sites like StackOverflow.com or www.reddit.com/r/learnprogramming
Sorry! :)


could you share the dataset's youtube id list ？

RT

We provide download links of the youtube-id list in the official website (https://acav100m.github.io/#downloads).
I will update README.md with this information.


1.20.1

Hi, I am looking forward to updating this project. I can probably manage to do it until Friday. If that is not as fast as you would like please create pull request and I will happily merge it.


strip slashes from the end of generated url

paths like /path/:a?/:b?/:c? and no parameters, generates /path///

Thanks for the PR!
I think this would solve the problem, but only partially. What if you omit only a and b, but provide c. In that case you'd get:
router.generate('hello', {c: 3})
// => /hello///3

On the other hand, if you output /hello/3 and reload the page, 3 will now be assigned to param a, not param c. So I'm wondering - what's your use case here? If all these segments are optional, wouldn't they be better of as query parameters? And if /hello//// is not ok - would /hello///3/ be ok if we were to merge this PR?

Yes query parameters would be an option, but sometimes you don't want or really need them. I'm ok with /hello///3 although it doesn't look right, but in case of /hello//// slashes on the end are useless. In my case I have a route path defined like this /car/:company?/:model? where model can't exists without company.

You could also handle this with the route nesting:
router.map(function (route) {
  route('car', function () {
    route('car.model', {path: ':company/:model'})
  })
})

There are 2 urls in this setup, /car or /car/foo/bar, the first one resolves to routes [{name: 'car'}], the second one resolves to [{name: 'car'}, {name: 'car.model'}].

Thats an option too. What are your thoughts agains this PR?

Well, mostly just thinking about why this is happening. I think I can see how it can be useful to have such a url with multiple optional segments.
This PR would have to be updated though, because the logic should be somewhere in this function https://github.com/QubitProducts/cherrytree/blob/bed5d93c71a813a8e1d4c0a97e2bfb5388a5ad96/lib/path.js#L74-L95. Location.formatURL is only used for prefixing with a # if required. Also, current PR won't work if there's also queryParams at the end of the URL. However, doing this in injectParams will work as expected in those cases.

Ok we can then close this PR. You will better know where to put the fix. Thanks.


Add service principals to the evaluation scope of AAD ScubaGear policy checks 7.1 through 7.5

💡 Summary
The scope of this task is to enhance ScubaGear AAD policy checks 7.1 through 7.5 to include service principal identities. The existing code only processes regular user accounts and groups. It makes sense to add service principals to the assessment because they are frequently assigned to highly privileged roles and therefore carry a lot of risk just like regular users.
Implementation notes

[x] Examine the current code to determine where the gaps are (i.e. which parts are missing the processing of service principals)
[x] Determine which MS Graph modules and cmdlets we need to add to support the new capability
[x] Perform hands-on prototyping of the new cmdlets to understand their parameters and outputs
[ ] Modify the ScubaGear code to include the capability
[ ] Test against all tenant types
[ ] Update the unit tests
[ ] Update the functional tests

Hands on Code Review and AAD Functional Analysis
I performed a review of the ScubaGear AAD Get-PrivilegedUser function because this is the code that creates a list of privileged_users that the Rego uses for AAD policies 7.1 through 7.5. Via the code review and hands-on testing in AAD by assigning service principals to various privileged roles, I determined:

You can only assign a service principal to a role as an Active assignment so we don't need to check for service principals in Eligible assignments. The same applies in PIM for Groups. In PIM for Groups you can only assign a service principal to a PIM group as Active. Below is an example of a service principal assigned to the Exchange Administrator role.

The Get-MgBetaDirectoryRoleMember cmdlet we are using to get a list of items Active assigned to a role returns a list which can include the type #microsoft.graph.servicePrincipal. We can add code for this case and then grab the metadata about the service principal and add it to the privileged_users JSON object that gets sent to the Rego.

MS Graph Powershell cmdlet Analysis
To get the metadata about the service principal (including Displayname), we need the Cmdlet below. Since it is in a Graph module that we don't currently have in ScubaGear (microsoft.graph.beta.applications), we'd need to add the module to the setup script. The cmdlet can work with the existing permission in ScubaGear Directory.Read.All so we don't need a new permission.
install-module microsoft.graph.beta.applications

Get-MgBetaServicePrincipal -ServicePrincipalId 4e56eea2-2307-4f1a-8c4e-3eaec5c21a3c

ScubaGear AAD Policy Impact Analysis
This section describes how the addition of service principals to the code will enhance or impact each of the policies in section 7 of the Azure AD baseline. It is important to understand that organizations that previously used ScubaGear may receive different assessment outputs from the tool after we include the service principal functionality.

Policy 7.1 - The policy check will have the ability to include service principals in the count of Global Administrators.
Policy 7.2 - If any service principals are assigned to highly privileged roles, they will be counted in the least privileged calculation.
Policy 7.3 - This policy should not be impacted because we do not expect service principals to have an OnPremisesImmutableId value.
Policy 7.4 - If any service principals are assigned to highly privileged roles, the organization will Fail this policy if the assignments are permanent. Since we expect service principals to have permanent active assignments in common cases, the user of ScubaGear will need to create an exception for this policy by adding the service principal identifier to the config file exclusions.
Policy 7.5 - If any service principals are assigned to highly privileged roles outside of Azure AD PIM, they will be included in this policy check and Fail the policy. If the user assigns the service principals to roles using AAD PIM, then they will Pass the policy. No surprises with this policy - it will behave the same as with regular users but include service principals as well.

Changed the issue status to Blocked at the request from CISA to have a discussion about how to integrate service principals into our baseline. It may require new baseline statements that are specific to service principals.

After discussing with CISA, the plan is to augment ScubaGear to grab the list of service principals and their respective highly privileged roles and display them in the report. Once this is implemented, CISA will work with agencies to examine the data for a period of time, and then we will determine if new Scuba policies are necessary and design what they should be. #934 was created for the coding enhancement.


test(probes): test unit of isArrayExpression probe

Closing the PR has this is now a bit out date and not updated


Error : Unbound module Infix while running the example given in the readme file

I am trying to run(build) the example program to set key values using irmin given in the readme file. But I am getting the below mentioned error.
$ dune build main.exe
 Entering directory '/home/sahana/work/irmin_ocaml/ocaml_ex'
 File "bin/main.ml", line 1, characters 5-17:
 1 | open Infix.Option
  ^^^^^^^^^^^^
Error: Unbound module Infix

Can you please show the code that you are trying to compile (or just the beginning if it's too long)? The example in the readme does not contain open Infix.Option on its first line, but open Lwt.Infix.

I am sorry the error is
$dune build main.exe
Entering directory '/home/sahana/work/irmin_ocaml/ocaml_ex'
File "bin/main.ml", line 1, characters 5-14:
1 | open Lwt.Infix
     ^^^^^^^^^
Error: Unbound module Lwt

And the program is the one in the readme file.

Can you check that:

lwt is correctly installed (if you installed irmin-unix it also installed lwt).
You mentioned lwt is in the libraries stanza of your dune file

Yes I had not mentioned lwt in the dune file . Now there is another error.
23 |     Store.set t ~info:(info "Updating foo/bar") ["foo"; "bar"] "testing 123" >>= fun () ->
                                                                                ^^
Error: This variant pattern is expected to have type
         (unit, Store.write_error) result
       The constructor () does not belong to type result

Is there any tutorial or something that i can refer for Irmin other than the official document(because it does not contain the build steps) or any prerequisites to start working with irmin

See https://irmin.org/, which contains a similar example on the index (updated to use the current API), and also an extended tutorial.

Yes I had not mentioned lwt in the dune file . Now there is another error.
23 |     Store.set t ~info:(info "Updating foo/bar") ["foo"; "bar"] "testing 123" >>= fun () ->
                                                                                ^^
Error: This variant pattern is expected to have type
         (unit, Store.write_error) result
       The constructor () does not belong to type result

There was indeed an issue un the README example. Store.set_exn should be used instead of Store.set. You can find this examples under examples/ (readme.ml) where all examples are checked and working. Thanks for noticing, we'll fix it!

Thanks it's working now.


returns wrong type from filter operator

Bug Report
Current Behavior
when I'm trying to filter via filter(Boolean) it returns Observable<unknown>
Reproduction
https://stackblitz.com/edit/rxjs-nywjdc?file=index.ts
const source = of(true).pipe(
  filter(Boolean)
);
// Observable<unknown>

Expected behavior
I expected to get type of source Observable<true> or Observable<boolean>
Environment

RxJS version: 6.5.2

Possible Solution
maybe that issue on typescript side or I'm just doing bad practice.

This is fixed in the alpha of rxjs 7 and will land in the next major release.


SQLite's real(float) datatype is not supported

I got an invalid error Invalid Error: FLOAT while trying to read an attached SQLite table with a real/float column. Here are the steps to reproduce:
Create a SQLite database:
echo "CREATE TABLE my (a REAL); INSERT INTO my VALUES (10.34), (0.042);" | sqlite3 my.db

Attach it from DuckDB (./build/release/duckdb -unsigned):
D LOAD 'build/release/extension/sqlite_scanner/sqlite_scanner.duckdb_extension';
D CALL sqlite_attach('my.db');
D SELECT * FROM my;
Error: Invalid Error: FLOAT

I was able to load tables of other data types (e.g., text, integer).
Also, thank you for making this extension. Now it's much easier to transfer/load data from existing SQLite databases to DuckDB.

I've encountered the same error, hopefully this will get fixed soon.

Thanks for the report! This should be fixed by #18 now.


Several problems cross continents

Hi,
I'm figuring out that there are a lot of functionalities not working cross continents.
I'm working from Asia on a European server. ( But I already had the same working from Europe to an Asian server )
Problems already face because of the continents :

Subscriptions
export data

I didn't tested if it was fixed or not.
What I have now :

permissions
hook functions

Permissions :
I get the classic old problem message :  "Cannot query field 'SomeUserExists' on type 'Query'. "
See my last post on :  https://www.graph.cool/forum/t/testing-permission-queries/1661/29?u=aspro
Hook functions :
When I try to deploy a hook function like
  cascadeDelete:
    type: operationBefore
    operation: Video.delete
    handler:
      code:
        src: src/video/onDeleteVideo.js

It ends up by getting the classical error message : "software.amazon.awssdk.services.lambda.model.CodeStorageExceededException: Code storage limit exceeded."
Please, assume that I can make everything working if I'm using the current continent where I'm working from.  Therefore it can't be a problem of my code, moreover I lost a lot of days investigating a lot of different solutions from internet before figure out it was related to the server's continent
I know the VPN can be a temporary solution but I don't want to have to pay a membership to a VPN service just to use graphcool.

Hey @Kisepro 👋

subscriptions: I'm not aware of any problems here, can you point me to an issue report? Is this still a problem?
Export data: we're taking a look at this soon! See #456
Permission Endpoint: Could you please create a new issue for this? 🙂
This is not a region-specific problem, please see #517 for more information and a workaround.

Please, assume that I can make everything working if I'm using the current continent where I'm working from.

Totally agreed!

Therefore it can't be a problem of my code, moreover I lost a lot of days investigating a lot of different solutions from internet before figure out it was related to the server's continent.

I'm sorry about the time you investigated! Feel free to reach out with questions if you are uncertain about something, that can sometimes be the quicker router 🙂
I'll close this issue, please create individual issues as I mentioned above 🙏


Option to reduce verbosity or turn off logging

Request type
Extension of existing module
Request description
This is a really useful easy-to-use package. I have been using this for relatively large requests and I was wondering if there is a way to reduce the verbosity of the logging info or turn off the logging completely?
Example command
No response
Example return value
No response

Hi Kenny, thanks for reaching out! Which module(s) are you using?
gget info and gget blast have a -q / --quiet (Python: verbose=False) argument that mutes the info level logging. The logging of all gget modules is handled using the package logging. I agree we should add a quiet argument to all modules in future releases. In the meantime, you could try something like this when using gget in a Python environment:
import logging
logger = logging.getLogger('gget')
logger.setLevel(level=logging.WARNING)

Sorry for the second message, even with the below code I still get an INFO message
import logging
import gget
logging.getLogger('gget').setLevel(level=logging.WARNING)
gget.seq('ENSE00001549666')

Output:
Mon Mar 20 17:29:10 2023 INFO Requesting nucleotide sequence of ENSE00001549666 from Ensembl.
['>ENSE00001549666 chromosome:GRCh38:1:26361634:26362022:-1',
 'GTGTGCCACAAGCGCTTCAGCAGCTCCAGTAACCTCAAGACCCACCTGCGCCTGCACTCCGGGGCCCGGCCCTTCCAGTGCAGTGTCTGCCGGAGTCGCTTCACCCAGCACATCCACCTGAAGCTGCACCATCGGCTGCATGCCCCACAGCCCTGTGGCCTGGTGCACACCCAGCTGCCCCTGGCCTCTCTGGCCTGCCTTGCCCAATGGCACCAGGGGGCACTAGATCTTATGGCGGTGGCATCTGAGAAACACATGGGCTATGACATAGATGAGGTCAAAGTGTCCTCGACATCCCAGGGGAAAGCAAGAGCAGTGAGCCTGAGCAGTGCCGGGACTCCCCTGGTGATGGGGCAGGACCAGAACAATTAAAAATGTTTCTTCTGTCA']

Hi Kenny,
We are sorry that the logger solution did not work. The next gget version (0.27.5) will support reducing verbosity with an added argument -q / --quiet (Python: verbose=False) for all modules. You can already install this version from the dev branch using pip install git+https://github.com/pachterlab/gget.git@dev. Please be aware that this branch is still actively under development.


[ONNX] Fix types in roi_align_opset16

Ensure that inputs to RoiAlign are the same type.

Hi @justinchuby , is this PR still draft or is it ready for review?

I don’t think this fix does what I hoped it would do perfectly so I will close for now


All Create ops when no Props passed

Description of changes: allow create operation when there is no props passed
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v1
Commit ID: 5401f7841767b08d0777e24496bc3f88ce1d1f5c
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 5401f7841767b08d0777e24496bc3f88ce1d1f5c
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Thanks - I'm currently OOTO for a couple weeks, but will review this when I return. Sorry for the delay.

Hello,
Thanks for the contribution. The builds are currently failing, a quick look suggests your change breaks at least one integration test. Please include an explanation as to why you think this change should be made - what behavior is currently reflected in the integration tests that you feel is incorrect and should be altered. I am OOTO for another week or two, but will review the PR when I return.
Thanks.

OK, I'm back now and took a second look and see that this indeed fixes a bug. We can't merge this yet as the builds are failing since it changes the CloudFormation output of the integration tests. You can run cdk-integ in the docker container to update the *.expected.json files yourself, or we can open a new PR that addresses your change and updates the *.expected.json files ourselves.

Going back to implement this, on second look the current code is redundant, but correct. The documented behavior of the construct is that allowCreateOperation defaults to false, which is what this code accomplishes. It probably doesn't need the initial props.allowCreateOperation reference, but that doesn't change the behavior. The suggested code changes the behavior to allowCreateOperation defaulting to true. The change matches the subsequent Read Operation code, but Read Operation is documented to default to true.
In hindsight, the defaults may not be optimum, but to change them now would be a breaking change.


test: use the swift_only_stable_abi feature instead of adhoc checks

Use the proper swift_only_stable_abi check to ensure that the tests do
not run on targets that do not support the pre-stable ABI.
Thanks to @slavapestov for pointing out that there was a better way!

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @slavapestov @kubamracek

@swift-ci please test

This looks great to me, Slava, can you confirm?


[CLI]: Incorrectly detects running in Jupyter (in PyCharm Console)

Describe the bug
PyCharm has the option to use IPython in the console:

With this set, W&B incorrectly returns True for the in_jupyter() check (in this code). It appears to conflate "in Jupyter" with "in IPython" in this case.
The result is output like the following:

And no way to override it that I can tell (maybe with environment variables?).
I believe 'ipykernel' in sys.modules in a more robust check for whether or not you're in Jupyter, although I only tested in Google Colab, PyCharm (with IPython), IPython, and a vanilla Python repl. And obviously you need to check this before you import ipykernel.
There's a second issue actually: you're importing ipykernel in jupyter_servers_and_kernel_id(), even though you're not in Jupyter, which means if any other packages use 'ipykernel' in sys.modules to test if they're in Jupyter, they'll erroneously return True if the user is using W&B with the setup I've described.
Perhaps the most robust way is to use _repr_html_ as described in https://ipython.readthedocs.io/en/stable/config/integrating.html. This is what Pandas does.
Additional Files
No response
Environment
WandB version: 0.13.7
Additional Context
No response

Hi @davidgilbertson, thank you for reporting these issues. I will pass these on to our engineering team and be able to follow up once they have a chance to look into this.
There is not an env variable you can pass to explicitly state if this is a notebook environment but that is a great idea and I will pass this on as well. You can set WANDB_NOTEBOOK_NAME to suppress the warning but this won't really help with the other issues you mentioned.
Thank you,
Nate

To add to this, you might like to copy what Pandas does to detect if it's running in a terminal: https://github.com/pandas-dev/pandas/blob/main/pandas/core/config_init.py#L337-L352.
def is_terminal() -> bool:
    """
    Detect if Python is running in a terminal.
    Returns True if Python is running in a terminal or False if not.
    """
    try:
        # error: Name 'get_ipython' is not defined
        ip = get_ipython()  # type: ignore[name-defined]
    except NameError:  # assume standard Python interpreter in a terminal
        return True
    else:
        if hasattr(ip, "kernel"):  # IPython as a Jupyter kernel
            return False
        else:  # IPython in a terminal
            return True

I assume that's been tested in all sorts of environments.

@davidgilbertson thank you for the suggestion! I've added this to the bug report as well.


Question: oAuth2

It seems the Challenger and SignInForm in Toolkit support username/password but not oAuth2. However, our clients may access both types of sources, so I need a challenger to handle both situations. Right now, my approach is this:

Follow the example to set up oAuth2 challenger (https://github.com/Esri/arcgis-runtime-samples-dotnet/tree/main/src/WPF/ArcGISRuntime.WPF.Viewer/Samples/Security/OAuth).
When the function CreateCredentialAsync(CredentialRequestInfo info) is called, try oAuth2 first.
If oAuth2 failed, try username/password with the SignInForm.

This approach is kind of working, but not a good solution. The CredentialRequestInfo parameter does not tell whether it is oAuth2 or username/password, and both of them belong to AuthentiationType.Token enum. So, it seems I can only try both.
Is there a better way to do it? In addition, is the Challenger and SignInForm in Toolkit going to support oAuth2 later?
Thanks.

SignInForm only deals with username/password. OAuth is performed in a browser window.


Adding/Removing Models

Original report (archived issue) by Pedro Osório (Bitbucket: pedroosorio88).

Hi IGN team !
I'm working on a custom gazebo client and i'm using IGN to render the scene. Whenever i add a model it throws :
[Err] [SceneManager.cc:1639] invalid parent name: minho_robot_2::base
[Wrn] [SceneManager.cc:1640] using scene root node
The model isn't displayed properly at first.

If i close and re-open the client, now it is properly displayed.

It means that "refreshing" makes everything work correctly, as parents are correctly assigned. What am i doing wrong here, where is this behavior coming from ?

This is a very old issue, so I'll go ahead and close it. Feel free to open if the problem is still relevant

So I think maybe this is also covered by: https://github.com/gazebosim/gz-sim/pull/824


Add localhost support

Using an account impersonation feature (like ganache-cli --unlock or hardhat_impersonateAccount) on a network fork in conjunction w/ Impersonator allows you to interact with dapps as if you were another user
This is helpful for debugging issues specific to an account which is not owned by you.
This PR simply adds another network to the network configs to support this flow

nvm kek doesn't handle signing from UI (like metamask)


Integration with PlantUML Standard Library

Not really an issue.
Would you mind if we integrate your library to the PlantUML Standard Library ?
(see http://plantuml.com/stdlib )
This would be useful for users.
Thanks!

Hi @arnaudroques no problem, go for it. Do you need any other action from me?

No other action from you!
We'll post a message here when the integration will be done.
Thanks!

Ok, we've just published V1.2019.12 with your library ( http://plantuml.com/stdlib )
The only change we have to do was in file naming : we use .puml instead of .uml
Thanks again for your contribution !

Looks good, thanks @arnaudroques


cosmetic: Improve identity / allocator logs

The allocator log here was duplicated with one that follows two lines
down; and one of the identity API calls was missing a debug log for the
calls.

This change is

Coverage decreased (-0.003%) to 46.114% when pulling 5d80c6bab70eae30e46b7151dc4330c2b365b05e on joestringer:submit/fix-allocator-logs into ae878faa9cd8deb85b463a395d537ce41ae9dd20 on cilium:master.

test-me-please

test-me-please

Potential CI issue?
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/15969/execution/node/105/log/
05:55:27      runtime: Warning: Remote connection disconnect. Retrying...
05:55:36  Timed out while waiting for the machine to boot. This means that
05:55:36  Vagrant was unable to communicate with the guest machine within
05:55:36  the configured ("config.vm.boot_timeout" value) time period.

test-me-please


mapDispatchToProps creating a Uncaught TypeError: webpack_require.i(...) is not a function

Trying to isolate the reason for this error,
trying to dispatch an action which will then be hooked by a saga, but it's failing and logging this error when I try to call the function.

fixed issue - not related to this boilerplate.

@eddiewang I'm running into the same error message.  I know that it's not related to the this repo, but can you provided details on how you fixed it?

@spdaly hi, it usually has to do with the template or saga. probably a typo. the error message isn't very clear on that. if you send me the code i'll take a look for you!

@eddiewang I cloned your fork to compare the code.  I think I found the problem.  I'll post if it continues to be an issue.

Here's the error message:
utils.js:188uncaught at rootSaga
 at setWatcher
 TypeError: __webpack_require__.i(...) is not a function

And the source code:
import { take, takeEvery, call, fork, cancel, put } from 'redux-saga/effects';
import { LOCATION_CHANGE } from 'react-router-redux';
import { GET_DOCUMENTS } from './constants';
import { getDocumentsSuccess, getDocumentsError } from './actions';
import * as firebaseRef from 'firebase-saga';

export function* getDocuments() {
  const documents = yield call(firebaseRef.get, 'documents');

  if (!documents.err) {
    yield put(getDocumentsSuccess(documents.data.results));
  } else {
    yield put(getDocumentsError(documents.err));
  }
}

export function* setWatcher() {
  while (yield takeEvery(GET_DOCUMENTS)) {
    yield call(getDocuments);
  }
}

export function* rootSaga() {
  const watcher = yield fork(setWatcher);
  yield take(LOCATION_CHANGE);
  yield cancel(watcher);
}

export default [
  rootSaga,
];

@spdaly check for typos... that's what mine ended up being. the webpack require isn't a very clear error. if you upload your code or add me i can pull and see if i can fix it for you.

Agree. I ended up using the generator to create a new container and copied code over. I'm still learning this whole stack so I'm sure that I fat fingered something somewhere.
Thanks for your time in commenting/reviewing.
I cloned your Tinder app to look at that code. #ThatTimeWhenCodeCanEffectYourMarriage. ;)

@spdaly - haha I never ended up finishing that. funny enough, my girlfriend wants me to finish that app more than I do. send me a follow, I'll make a note to update you when (and if) it ever gets complete! hope you fix all your bugs.

@spdaly you import your takeEvery from a wrong place. try import { takeEvery } from 'redux-saga'; instead of import { takeEvery } from 'redux-saga/effects';
takeEvery is not in effects but in the main package instead :)


undefined method `now_and_every'

I get undefined method `now_and_every' for #Timers::Group:0x89c3378 (NoMethodError) on windows and on linux. I have to manually replace installed lib directory with one from this repo to get rid of this error. What's the cause of it? Thanks in adv.

What gem version or branch commit? It might be that we need to cut a new gem.

:+1:  found out this error right now, wonder if i can do the same thing just with every

If you set an every timer, you can immediately issue .trigger on it to accomplish now_and_every without the method.

Will do, thank you!

undefined method `trigger' for #Timers::Timer:0x199e3c0 (NoMethodError)
Well... for me it didn't solve the issue.
I use rubygems 2.4.8 on windows and 2.4.6 on linux it's kinda weird. Thank you for your help.

When is the next version of the gem (including now_and_every) going to be released?

I'll drop in a point release today/tomorrow.

Hi, I saw that you updated to 4.0.2 but ruby gem is still serving 4.0.1. any ETA for the official release?

4.0.2 has been cut and released on rubygems.


crm457-1109: Fix missing translations on CYA page

Description of change
Fix missing translations on CYA page
Link to relevant ticket
The check your answers page for NSM encounters
multiple missing translation errors when running
in local/development. This error does not occur on
hosted environments because any missing translations fall back to using a humanized version of whatever “key” has been supplied.
Notes for reviewer
Screenshots of changes (if applicable)

Before changes:
After changes:
How to manually test the feature

Closing as now fixed in another way


[BUG] gridding_plot only work for global and WGS84 currently

Hi @chenyangkang,
Exporting the plot for the grid of the quadtrees only works when using WGS84. Is there a way to access the grid itself and or export the figure under another CRS?
Thanks!

Hi @juangallegozamorano !
Thanks for opening the issue!

The grid plot extent is currently set to (-180,180) and (-90, 90). You can changed it to your CRS extent by setting plot_xlims and plot_ylims params during model class initiation. For example plot_xlims=(-64000, 64000). I will add an auto-estimator in the next PR.
The girds are generated based on your input data. So it makes less sense to project the grids to another CRS, and imaginably they will be twisted if you do that.
You can still access the grids by calling model.ensemble_df.

Hi @chenyangkang, I accessed the ensemble_df but unfortunately I'm not able to plot the stixels. Can you tell me how to do it? Thanks!

@juangallegozamorano  There is not function implemented for this in stemflow. But you can do:
from stemflow.utils.jitterrotation.jitterrotator import JitterRotator
from shapely.geometry import Polygon
import geopandas as gpd

# define a function
def geo_grid_geometry(line):
    old_x, old_y = JitterRotator.inverse_jitter_rotate(
        [line['stixel_calibration_point_transformed_left_bound'], line['stixel_calibration_point_transformed_left_bound'], line['stixel_calibration_point_transformed_right_bound'], line['stixel_calibration_point_transformed_right_bound']],
        [line['stixel_calibration_point_transformed_lower_bound'], line['stixel_calibration_point_transformed_upper_bound'], line['stixel_calibration_point_transformed_upper_bound'], line['stixel_calibration_point_transformed_lower_bound']],
        line['rotation'],
        line['calibration_point_x_jitter'],
        line['calibration_point_y_jitter'],
    )

    polygon = Polygon(list(zip(old_x, old_y)))
    return polygon

# Make a geometry attribute for each stixel
model.ensemble_df['geometry'] = model.ensemble_df.apply(geo_grid_geometry, axis=1)
model.ensemble_df = gpd.GeoDataFrame(model.ensemble_df, geometry='geometry')

Which create a spatial object for each stixel.
Then:
model.ensemble_df.plot(alpha=0.2)

The stixel will stack on the temporal dimension. You may want to pick only one time range (since the spatial splitting pattern will be the same for all temporal windows in one ensemble).
model.ensemble_df[
        (model.ensemble_df['DOY_start']>=90) & (model.ensemble_df['DOY_start']<120)
].plot(alpha=0.2)

Which will look less messy.
You may also want to add scatter point on top of this:
fig,ax = plt.subplots()

model.ensemble_df[
        (model.ensemble_df['DOY_start']>=90) & ((model.ensemble_df['DOY_start']<120))
].plot(alpha=0.2,ax=ax)

ax.scatter(
        X_train['longitude'],
        X_train['latitude'],
        c='tab:orange',s=0.2,alpha=0.7
)

plt.show()

Cheers!

Thanks a lot!! This is really helpful!

Hi @chenyangkang, for some reason the geometries are all empty in my case...

@juangallegozamorano You could provide details e.g. the model.ensemble_df original data frame for debugging purpose.

Here are two examples of ensemble_df that I would like to represent in a figure
53970_larcan_ensemble_grid.csv
Common_Gull_ensemble_df.csv

@juangallegozamorano I cannot reproduce the bug. This is what I got for 53970_larcan_ensemble_grid.csv:
data = pd.read_csv('53970_larcan_ensemble_grid.csv', index_col=0)

from stemflow.utils.jitterrotation.jitterrotator import JitterRotator
from shapely.geometry import Polygon
import geopandas as gpd

# define a function
def geo_grid_geometry(line):
    old_x, old_y = JitterRotator.inverse_jitter_rotate(
        [line['stixel_calibration_point_transformed_left_bound'], line['stixel_calibration_point_transformed_left_bound'], line['stixel_calibration_point_transformed_right_bound'], line['stixel_calibration_point_transformed_right_bound']],
        [line['stixel_calibration_point_transformed_lower_bound'], line['stixel_calibration_point_transformed_upper_bound'], line['stixel_calibration_point_transformed_upper_bound'], line['stixel_calibration_point_transformed_lower_bound']],
        line['rotation'],
        line['calibration_point_x_jitter'],
        line['calibration_point_y_jitter'],
    )

    polygon = Polygon(list(zip(old_x, old_y)))
    return polygon

# Make a geometry attribute for each stixel
data['geometry'] = data.apply(geo_grid_geometry, axis=1)
data = gpd.GeoDataFrame(data, geometry='geometry')

I also successfully plotted the Common_Gull_ensemble_df.csv. Maybe you could provide more information? For example:
add a "print" line in the function:
def geo_grid_geometry(line):
    old_x, old_y = JitterRotator.inverse_jitter_rotate(
        [line['stixel_calibration_point_transformed_left_bound'], line['stixel_calibration_point_transformed_left_bound'], line['stixel_calibration_point_transformed_right_bound'], line['stixel_calibration_point_transformed_right_bound']],
        [line['stixel_calibration_point_transformed_lower_bound'], line['stixel_calibration_point_transformed_upper_bound'], line['stixel_calibration_point_transformed_upper_bound'], line['stixel_calibration_point_transformed_lower_bound']],
        line['rotation'],
        line['calibration_point_x_jitter'],
        line['calibration_point_y_jitter'],
    )

    polygon = Polygon(list(zip(old_x, old_y)))
    print(polygon) # this line should print out the polygon string.
    return polygon

I just tried again and now I can see the stixels...I cannot explain why there were empty geometries before, thanks a lot and sorry for the hassle!

No worries! Good to hear you solved it!


Respond with an appropriate error message when the email provider is not configured

While resetting the password, if the email provider is not configured the user should be notified to contact the admin

@sainak this looks like a good first issue.

If the issue still persists , i would like to work on this.

@Sulochan-khadka  Since there are no update since past 3 weeks , I'll like to work on it and make a PR to fix this.

Sure ... Go ahead @DraKen0009 ... Am working on some other issues ...


Does react-native version 0.51 support AppTrackingTransparency?

No Template
Does react-native version 0.51 support AppTrackingTransparency ?

react-native-permissions 3.0.0 only supports RN 0.63: https://github.com/zoontek/react-native-permissions#support


Updated outdated Taquito code

The Taquito code present in the article about FA1.2 and Ligo is not compatible with the changes introduced in version 7, it has been fixed to work with the latest version of Taquito.

I removed the links to PascaLigo and ReasonLigo as the corresponding files were deleted from the Ligo repo a week ago. Having an up-to-date code for Taquito is more important than having an example for each Ligo flavour so I created a new commit to make it available quickly. I will keep looking for PascaLigo and ReasonLigo FA1.2 contract examples and add them later.

I removed the links to PascaLigo and ReasonLigo

corresponding bullet points in the list also should be removed


About processed dataset download

Hello, I always receive server errors when trying to download the processed DSIFN and LEVIR datasets(DSIFN-CD-256.zip and LEVIR-CD-256.zip in dropbox). Can you provide an alternative download method, such as Baidu Netdisk or Google Drive?

@Ozone-oo Thanks for raising this issue. I have just fixed the broken links.


Documentation on expressions should be updated

In the documentation on expressions it says the following:

You might also want to remove the attribute if the value is not truthy so that values of false or empty string '' remove the attribute

Empty string '' is truthy.  So an empty string will leave the attribute in place.
This is the demo snippet in the documentation.
html`<button aria-label="${this.ariaLabel || nothing}"></button>`

This will leave the attribute in place if ariaLabel=''.
https://stackblitz.com/edit/vitejs-vite-d25wmw?file=package.json

Empty string is falsy and as such it the code snippet correctly falls back to nothing when using ||, therefore removing the attribute.
See this playground example. If you inspect the <p> element, foo attribute does not exist, but bar does.
I also do not see any attribute on the <button> element in the provided stackblitz example either.

@augustjk good catch .... I got my wires crossed ... :)


Add "Diff Checker" extension

Description
Adds a new extension. The extension helps to compare two files by outputting a line-by-line difference.
Type of change

New extension

Screencast
https://user-images.githubusercontent.com/4247901/152709119-932453b8-a95d-4800-9ef5-aab8115f7d98.mov
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast

Thanks for testing the extension and providing feedback @pernielsentikaer!
I've merged the changes, should be good now.


[stable/metallb] Add initContainer support to metallb speakers.

What this PR does / why we need it:
Adds support for adding custom initContainers to metallb speakers
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @davidkarlsen

/lgtm


Inconsistent focus style behavior

Focus ring on touch devices
<vaadin-text-field autofocus>

The field gets the focus-ring (and focused, judging by the blue label text) state also on touch devices. It should not, as at least iOS prevents autofocus from working at all (it will not focus the field and open the keyboard).
No focus ring when focusing programmatically
textField.focus();

Works differently from autofocus and does not apply the focus-ring state, although it should. You can use the same https://vaadin-login-proto.glitch.me example to see the behavior (click the “Log in” button which moves the focus to the “Username” field).
Since the focus is moved programmatically (vs by the user) we should let the user know visually more prominently where the focus has been moved.

Also faced this while working on accordion, actually it might make sense to handle this in vaadin-control-state-mixin. I had to duplicate some styles - especially, for accordion panel, I apply the styles to focused state instead of just using focus-ring.


write(): Connection reset by peer [core/stats.c line 389]

when i use hug+uwsgi and nginx, i met this problem.
[uwsgi]
http = <IP_ADDRESS>:7974
wsgi-file = app_hug.py
callable = __hug_wsgi__
master = true
process = 4
threads = 2
vacuum=true
stats = <IP_ADDRESS>:9191

import hug
from hug_middleware_cors import CORSMiddleware

app = hug.API(__name__)
app.http.add_middleware(CORSMiddleware(app))

@hug.post()
def plag(p1, p2):
    res = {"res": p1+p2}

    return res

upstream uwsgi {
    server http:<IP_ADDRESS>:7974
}

server {
  listen 80;
  server_name myhost.com;

  access_log /var/log/nginx/myhost.access.log;
  error_log /var/log/nginx/myhost.error.log;

  charset     utf-8;
  client_max_body_size 75M;

  location / {
    root /myhost;
    index index.html index.htm;
  }

  location /api/ {
    uwsgi_pass  uwsgi;
    include     /etc/nginx/uwsgi_params;
  }
}

is there anyone who met the same problem?

i got that, use the use config in the document is going well.


Sm/levenshtein-missing-types

What does this PR do?
nicer error messages for unresolvable types.
Error (RegistryError): Missing metadata type definition in registry for id 'Worflow'.

Try this:

Did you mean one of the following types? [Workflow]

Confirm the metadata type name is correct. Validate against the registry at:
<https://github.com/forcedotcom/source-deploy-retrieve/blob/main/src/registry/metadataRegistry.json>

If the type is not listed in the registry, check that it has Metadata API support via the Metadata Coverage Report:
<https://developer.salesforce.com/docs/metadata-coverage>

If the type is available via Metadata API but not in the registry

- Open an issue <https://github.com/forcedotcom/cli/issues>
- Add the type via PR. Instructions: <https://github.com/forcedotcom/source-deploy-retrieve/blob/main/contributing/metadata.md>

shares a bunch of logic with suffix-levenshtein, so that's all now in one place.
What issues does this PR fix or reference?
@W-16324102@

Does the ComponentSetBuilder.build not need the catch anymore? It was just moved down a level to the RegistryAccess itself?

Does the ComponentSetBuilder.build not need the catch anymore? It was just moved down a level to the RegistryAccess itself?

yeah, it was intercepting only that one error (where something was missing from the registry) and re-throwing all others.  Now that the RegistryAccess returns a nicer error, there was nothing left to catch.

QA Notes

✅ :
➜  dreamhouse-lwc git:(main)  hub:(GLOBAL - DevHub<EMAIL_ADDRESS> ➜  sf project deploy start -m Foox
Error (SfError): The specified metadata type is unsupported: [foox]

➜  dreamhouse-lwc git:(main)  hub:(GLOBAL - DevHub<EMAIL_ADDRESS> ➜  ../../oss/plugin-deploy-retrieve/bin/run.js project deploy start -m Foox
Error (RegistryError): Missing metadata type definition in registry for id 'Foox'.

Try this:

Did you mean one of the following types? [Flow,Form]

Confirm the metadata type name is correct. Validate against the registry at:
<https://github.com/forcedotcom/source-deploy-retrieve/blob/main/src/registry/metadataRegistry.json>

If the type is not listed in the registry, check that it has Metadata API support via the Metadata Coverage Report:
<https://developer.salesforce.com/docs/metadata-coverage>

If the type is available via Metadata API but not in the registry

- Open an issue <https://github.com/forcedotcom/cli/issues>
- Add the type via PR. Instructions: <https://github.com/forcedotcom/source-deploy-retrieve/blob/main/contributing/metadata.md>


Issue 552: Fix checking of test modules

Closes #552

@treiher Do you see a way to avoid such issues in the future (i.e. detect when an __init__.py is missing)?

@treiher Do you see a way to avoid such issues in the future (i.e. detect when an __init__.py is missing)?

You are right, we should make sure that such issues are prevented in the future. This option should remove the need for __init__.py for mypy. I will add this option in this PR and check if other linters are affected as well.

You are right, we should make sure that such issues are prevented in the future. This option should remove the need for __init__.py for mypy. I will add this option in this PR and check if other linters are affected as well.


typescript as dependency necessary?

Is it necessary to specify typescript as dependency and not as devDependency?
We are using typescript@4 and when installing express-oas-generator it installs a second typescript instance, and for some reason breaks our tsc builds.

Heyo, last time we discussed this when we introduced typescript's type definitions - see https://github.com/mpashkovskiy/express-oas-generator/pull/43#issuecomment-554895376
Not sure if it's still the case - we could try to make it a dev dependency and see if the mentioned scenario, as well as the normal ones, do not break. /cc @mpashkovskiy

Looks like nobody had time to test it, @yss14 would you try @kiprasmel suggestion and get back with the result? Or should we close the issue?

@mpashkovskiy Thanks for the reply, I guess we can close this issue since I moved my job in the meantime and express-oas-generator is our of stack.


fix: Prevent a memory leak on AndroidView which may not call ON_DESTROY

This PR fixes a memory leak that can happen in AndroidView when navigating to another screen.
The Lifecycle ON_DESTROY event is never called because in onDispose we remove the mapLifecycleObserver and this method is called before the Lifecycle ON_DESTROY event. It will correct the problem that occurred in https://github.com/googlemaps/android-maps-compose/pull/188
We have to handle any Lifecycle ON_DESTROY in the onDispose method.

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open a GitHub issue as a bug/feature request before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #138  🦕

v2.7.2 containing this fix has been released to Maven. Thank you for your contribution @polivmi1!


Improve the events report

1.add timeout in ttrpc ctx
2.add queue in publisher report
3.add reconnect client method

#312

CI test has some problem ..  Hello @mxpv

need a rebase, the CI problem was resolved in #321


[Enhancement] (nereids)implement showWhitelistCommand in nereids

What problem does this PR solve?
Issue Number: close #42725
Related PR: #xxx
Problem Summary:
implement showWhitelistCommand in nereids
Release note
None
Check List (For Author)

Test

[ ] Regression test // added
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run fe_ut

run buildall

run buildall

run buildall

run buildall


etebase-server: use python, not python3

I noticed that using python3 here refers to pkgs.python3 while python is always the one from the calling interpreter.
In other words: before that change
legacyPackages.x86_64-linux.python311.pkgs.etebase-server.python would give me a python 3.12 release, now it's 3.11 as it should be.
Tests might currently fail as python-ldap is broken on master. (see e.g. https://github.com/NixOS/nixpkgs/pull/326321). You can check locally by overriding withLdap = false.
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 326398 run on x86_64-linux 1

2 packages built:

python311Packages.etebase-server
python311Packages.etebase-server.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1821

This package almost works in an ugly way.

I agree with that. As it's an application it probably shouldn't be a python module as well, but I ofc don't know if there's any out of tree users of the module. The nixos module currently depends on python and pythonpath in passthru in the package, but that could of course be fixed.

This PR only makes it more confusing to read, because normally people think of python2 when seeing python (because top-level python is python2)

Hm, I was about to write that in the context of a python-module it makes sense. But yeah, the file isn't in pkgs/development/python-module, so thats a good argument to actually turn things around.

I agree with that. As it's an application it probably shouldn't be a python module as well, [...]

The etebase-server NixOS module currently relies on the python module. If it could be refactored to work without it I would be happy removing the python module altogether.
It's been a while since I initially added the package & NixOS module, but I remember some issues why I couldn't get it working without the python module. The NixOS module invokes etebase-server via uvicorn, so that's a bit special.
I didn't know about toPythonModule yet, with that migrating to pkgs/by-name seems to be the best option to streamline the package.


Implement CS checking based on the WPCliCS ruleset

Composer: use wp-cli-tests ^2.0.14
... as that version contains the new WPCliCS PHPCS standard.
.gitignore/.distignore: ignore phpcs/phpunit config files

.distignore: no need to distribute the phpcs/phpunit config files.
.gitignore: Allow devs to overwrite config files for PHPUnit and PHPCS

The .dist files should be committed. However, for their personal use, devs can overrule those files with versions without .dist.
Those personal versions should never be committed.

As a side-note: for PHPCS, having a personal version while still using the original .dist file is made very easy, as you can just import the .dist file as a starting point, like so:
<?xml version="1.0"?>
<ruleset name="WP-CLI">
    <rule ref="./phpcs.xml.dist"/>
</ruleset>

PHPCS: add a ruleset for this project
The file is completely documented in-line.

Remaining issues list:
20190417-phpcs-result-i18n.txt
Once these issues have been resolved, either by fixing them, whitelisting individual issues or pinging me to adjust the ruleset, this PR will need to be rebased.
After that it can be marked Ready for review and the build should go green.

@jrfnl I pushed changes into this PR, it should now pass PHPCS.

Whoops 🙃 Sorry about that.

@schlessera Thanks. I have a couple of remarks, but it seems that @swissspidy already merged this....

Just post the remarks here, and I'll follow up in a separate PR as needed.

I just have ;-)

I replied to them. Do you agree with my assessments, or is there something I did not consider?

@schlessera I agree with the one, not so much the other ;-)

The mb_ereg/preg_quote mismatch, I assume.
I'm happy to look into actually fixing the bug for this release if I end up having time once the blocking bugs are fixed. This one hasn't bitten anyone yet and doesn't block the release, so it is low priority for me right now.


Update description.md

Sorry, @prathambekal87, but this change does not make any sense. Please reopen with a proper change if needed. Thanks.