Inital draft for Pred docs

Documentation for the Pred crock, with a nice example :)

Coverage remained the same at 100.0% when pulling 461437a63a570977b1a72c3c7fbe210d1ab52c09 on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling 520057132fddcbcbb8a2a5810275a69cbe3603c9 on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling 57d4b9e12e77839817ebd340ee7b690bd3dd0771 on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling cdcebddec2f7ab2e5fcafa703982cb4eff59e18b on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling 2ca1347d2c6a142665dd55efa0a1d02147bb9659 on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling 2ca1347d2c6a142665dd55efa0a1d02147bb9659 on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling 2ca1347d2c6a142665dd55efa0a1d02147bb9659 on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling 2ca1347d2c6a142665dd55efa0a1d02147bb9659 on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling 782a6098e231c0d69585096d1a7bf006d90175f8 on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling e40c4b3b4b1cecdeeb0b14906697facb7eae3014 on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling cb7c0468f0bb6f0d26e2ea04f02989b004429b29 on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling cb7c0468f0bb6f0d26e2ea04f02989b004429b29 on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Coverage remained the same at 100.0% when pulling f7c6047e759593813787b89a8d661f5b7bc4c5be on galileopy:docs into 49e7f2ad6721ae9d94bd1a4ee7459ee9b8436cfa on evilsoft:docs.

Closing this for now. Going to go a different route with dat documentation.


Vendored RunC into the opengcs repo to avoid issues from mismatched O…

…CI spec support
We have seen mismatched  OCI spec support used by gcs, runcs, unitests, and docker daemon.
This vendoring is to eliminate the chance to cause this mismatch among gcs, runc, and unittests.
It also saves the OS image builder the trouble of generating a correct version of runc to run with the opengcs.

@soccerGB,
Thanks for your contribution.  To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
The agreement will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

CI caught a build failure,


Generate a docker-compose.yml file

can you elaborate on it.

Just generate a simple docker-compose.yml file based on Dockerfile and we can run it normally.
Nothing special, please feel free to take it if you have interesting. 😃

I have submitted a PR #52


As a developer, I should be able to deploy the app without manual configuration for MyUSA

need config file for config/auth.js
    authorizationURL: 'https://myusa-staging.18f.us/oauth/authorize',
    tokenURL: 'https://myusa-staging.18f.us/oauth/token',
    profileURL: 'https://myusa-staging.18f.us/api/profile'

This was fixed in midas -- when MyUSA ToS issues has been addressed, we can turn it back on with config supported by automated deploy.


Apparent formatter speed regression

Editing a simple .exs test file (340 lines) is taking around 3 seconds to format on save with no other edited files. I get a loading bar and a notification at bottom right mentioning the "ElixirLS: Elixir support and debugger" formatter running.
I installed 0.5.0 manually from the vsix and the problem is gone, so it looks like a regression in the latest release.
Any guesses on what happened between versions? Any particular logs or other diagnostic information can I provide to help debug?
This is an umbrella project of a fair size. Pure Elixir, so no large node_modules directories, etc.
Possible relation to #378?
Environment

Elixir & Erlang versions (elixir --version): Elixir 1.9.4 (compiled with Erlang/OTP 22)
Operating system: MacOS Mojave
Editor or IDE name (e.g. Emacs/VSCode): VSCode
Editor Plugin/LSP Client name: elixir-lsp/elixir-ls

Troubleshooting

[x] Restart your editor (which will restart ElixirLS) sometimes fixes issues
[x] Stop your editor, remove the entire .elixir_ls directory, then restart your editor

NOTE: This will cause you to have to re-run the dialyzer build for your project

Logs
Wasn't sure exactly what to provide in this case but happy to include what I can.

Same here :(

Do you have a sample project that exhibits this issue? And what is in your .formatter.exs inputs?

Unfortunately I don't have a sample repro :/
We're in an umbrella project, so here's the contents of our various formatter configs:
> fd --hidden ".formatter.exs" --exec cat {}
[
  inputs: ["{mix,.formatter}.exs"],
  subdirectories: ["apps/*"]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: [
    "{lib,config,test}/**/*.{ex,exs}",
    "{mix,.formatter}.exs"
  ],
  import_deps: [:absinthe, :plug],
  locals_without_parens: [
    forward: 1,
    visibility: 1,
    owning_team: 1,
    experimental_complexity: 1,
    import_autostitched_types: 2,
    import_autostitched_fields: 2
  ]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: [
    "{lib,config,test}/**/*.{ex,exs}",
    "{mix,.formatter}.exs"
  ],
  import_deps: [:absinthe],
  locals_without_parens: [
    forward: 1,
    visibility: 1,
    import_autostitched_types: 2,
    import_autostitched_fields: 2
  ]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: [
    "{lib,config,test}/**/*.{ex,exs}",
    "{mix,.formatter}.exs"
  ],
  import_deps: [:plug]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

[
  inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]

I'm getting this in the output:
[Trace - 1:44:38 PM] Sending request 'textDocument/formatting - (9569)'.
[Trace - 1:44:38 PM] Received response 'textDocument/formatting - (9569)' in 1ms. Request failed: Cannot format file from current directory (Currently in deps/telemetry_poller/deps/parse_trans) (-32603).
[Error - 1:44:38 PM] Request textDocument/formatting failed.
  Message: Cannot format file from current directory (Currently in deps/telemetry_poller/deps/parse_trans)
  Code: -32603
[Trace - 1:44:38 PM] Sending notification 'textDocument/didSave'.
[Trace - 1:44:39 PM] Sending notification 'workspace/didChangeWatchedFiles'.
[Trace - 1:44:39 PM] Sending request 'textDocument/hover - (9570)'.
[Trace - 1:44:39 PM] Sending notification '$/cancelRequest'.
[Trace - 1:44:39 PM] Received response 'textDocument/hover - (9570)' in 34ms. Request failed: Request cancelled (-32800).

Maybe it helps.
It resolves itself for a while if i restart the editor

@BlueHotDog do you have any file open from deps/telemetry_poller/deps/parse_trans? Also please post your .formatter.exs

this is my .formatter:
[
  import_deps: [:ecto, :phoenix],
  inputs: ["*.{ex,exs}", "priv/*/seeds.exs", "{config,lib,test}/**/*.{ex,exs}"],
  subdirectories: ["priv/*/migrations"]
]

I do not have any file from deps/delemetry.. open :(

Hmm the code in https://github.com/elixir-lsp/elixir-ls/blob/d7208fe42ad0a28c72d9acf2236d83cd7f785071/apps/language_server/lib/language_server/providers/formatting.ex#L43 seems strange. @axelson do you have an idea why is it checkin cwd? It was added in https://github.com/elixir-lsp/elixir-ls/commit/d1437729c0a905cad31f371eac22d4ade1195193#diff-d695db38f04b7e4e345c6f1341e4b0fd9ec92ab81ae4741577dba5ad9e7d5778 but I'm not convinced by the reasoning in the commit message.

@lukaszsamson I am agreed with you. I don't see a reason we can't format regardless of the CWD. Since we have the project dir we can always use that to find the relevant .formatter.exs. But with that said, this is a different issue that is already being tracked as #252

Can confirm that this is what we have experienced as well. Perhaps @axelson you could try using the absinthe-graphql/absinthe code base as an example? It's got quite a few files and test files.
Does elixir-ls compile the full code base before formatting? Does format on save format all files or just the one saved?

I can repro more specifically by repeatedly changing and saving a file. Eventually it'll block with the notification that the file save action is waiting on Elixir LS to format*.
In the Elixir LS logs I noticed this seemed to occur if I saved right after I saw this message:
 [ElixirLS WorkspaceSymbols] Updating index...

During that time format/save doesn't complete until it finishes. It seems like this may correlate with saving while the workspace symbol update is in progress?
If I make changes really quickly it seems like I can reproduce this in 0.5.0 too. I'm unclear why it's worse in 0.6.0 though. I noticed 0.6.0 bumps Elixir and Erlang, some change there? I didn't see anything obvious in the release notes of either of those though. Is indexing slower, and thus the problem more apparent?
One way or another it seems odd that reindexing the workspace symbols is blocking the format operation. It seems like we'd want to avoid blocking a save operation at all costs.
Is this something the Language Server spec imposes? Is something in indexing causing the formatter to have to wait?
I'm not sure when I'll next have a chance to look into this deeply, but hopefully this helps.

* If I go really fast I get a different error that feels like another issue to address at a later date:
MIX_TARGET:
[Error - 1:55:12 PM] Request textDocument/formatting failed.
  Message: Cannot format file from current directory (Currently in apps/thrift_services)
  Code: -32603

@axelson - Should I close this or would you like it to remain open? I don't want to mess with your workflow.

I want to do some more testing and collect more feedback before closing this. Also ideally we could change the code to not use Path.wildcard to remove more directory traversal.

Nice, good call 👍

I've proposed a partial fix for this problem in https://github.com/elixir-lsp/elixir-ls/pull/609 (by also fixing a bug with how :inputs are matched). It delivers a big speed-up on a project I work on, but doesn't fix the underlying problem of relying on Path.wildcard/2.
I plan to also propose a more general solution, but that will take a bit longer. In the mean time, please try out the changes above and let me know if you encounter any problems (other than performance) on your projects.

https://github.com/elixir-lsp/elixir-ls/pull/609 was expanded to fix this issue completely since with that change, ElixirLS no longer requires a call to Path.wildcard/2 for formatting now that PathGlob is used instead :confetti_ball:

That’s amazing! 🎉
On December 4, 2021, GitHub @.***> wrote:

#609 https://github.com/elixir-lsp/elixir-ls/pull/609 was expanded
to fix this issue completely since with that change, ElixirLS no
longer requires a call to Path.wildcard/2 for formatting now that
PathGlob https://github.com/jonleighton/path_glob is used instead 🎊

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/elixir-lsp/elixir-ls/issues/381#issuecomment-
986160421>, or unsubscribe
<https://github.com/notifications/unsubscribe-
auth/AAANRJSMRTYEYQB23ERA4W3UPLM75ANCNFSM4SL6QKNQ>.


test: add usage of rtcp_msg_print()

There are two problems here ...

formatting errors:

rtptest:       SR pad=print: Format: "%8s pad=%d<-- SIZE ERROR
Assertion failed: 0 && "RE_VA_ARG: arg is not compatible", file /home/runner/work/re/re/baresip-win32/re/src/fmt/print.c, line 503

recursive mutex deadlock in dbg.c when calling DEBUG_WARNING from within DEBUG_NOTICE

Some jobs are stuck in the deadlock:
  test 98 -- test_rtmps_publish
  test 99 -- test_rtp
  test 100 -- test_rtpext
  test 101 -- test_rtcp_encode  <--- Stuck here

it looks like the bitfields are promoted to int when printed:
	/** RTCP Header */
	struct rtcp_hdr {
		unsigned int version:2;  /**< Protocol version       */
		unsigned int p:1;        /**< Padding flag           */
		unsigned int count:5;    /**< Varies by packet type  */
		unsigned int pt:8;       /**< RTCP packet type       */
		uint16_t length;         /**< Packet length in words */
	} hdr;

hi @sreimers
It looks like there is a problem with gcc and printing of bitfields.

Please note than when using printf there are no compiler warnings.
#include <stdio.h>
#include <inttypes.h>
#include <re/re.h>

int main()
{
	struct rtcp_hdr hdr;

	hdr.version = 1;
	hdr.p = 1;
	hdr.count = 2;
	hdr.pt = 200;
	hdr.length = 3;

	re_printf("%8s pad=%d count=%-2d pt=%-3d len=%u \n",
	       rtcp_type_name((enum rtcp_type)hdr.pt),
	       hdr.p,
	       hdr.count,
	       hdr.pt,
	       hdr.length);
}

The default promotion for variadic function args and small data types should be int or maybe higher, so yes this is wrong, unsure how to detect bit-fields nicely. I have to think about that.

One option is to stop using bitfields, it seems to be compiler specific...

I think I found a good workaround for bit fields: https://github.com/baresip/re/pull/1110

This one is now ready for merge...


add vote.samoswap.com domain

Hi! What is your PR about?

[ ] Add or edit a skin
[X] Add custom domain for your space
[ ] Add alias for migrate your space
~Add images for your space~ (deprecated) Add the image URL on the space settings directly
~Edit your space with GitHub?~ (deprecated) Please migrate your space to ENS https://docs.snapshot.page/spaces/migrate
~Create your space with GitHub~ (deprecated) Create your space with ENS instead https://docs.snapshot.page/spaces/create

updated domain,json, and the logo has been deleted, I will add via UI, thanks

updated domain,json, and the logo has been deleted, I will add via UI, thanks

@devsamo Sorry the conflict still there, could you do it again please? Thanks

To update your fork with the remote version of snapshot-spaces you can try these GIT commands then commit your changes again.
git remote add upstream https://github.com/snapshot-labs/snapshot-spaces.git
git fetch upstream
git checkout master
git merge upstream/master

ok done

To update your fork with the remote version of snapshot-spaces you can try these GIT commands then commit your changes again.
git remote add upstream https://github.com/snapshot-labs/snapshot-spaces.git
git fetch upstream
git checkout master
git merge upstream/master

@devsamo Could you please follow this steps to try to update domains.json file?

hi, i have done with the commands, kindly recheck

hi, i have done with the commands, kindly recheck

@x0archie Hi! It doesn't work any better. If you can't update I recommend you to close this PR and start from a new fork.

oh ok... thanks anyway for your support


Report a error if grpc server is not started

Bug: http://b/168295378

Thanks a lot Dimitry! Just one question: is it possible to enable grpc log also?

I think it is but considering that we do not really expect grpc to fail, I decided not to at least for now.


[SPARK-16711] YarnShuffleService doesn't re-init properly on YARN rolling upgrade

branch-2.0 version of this patch.  The differences are in the YarnShuffleService for finding the location to put the DB. branch-2.0 does not use the yarn nm recovery path like master does.
Tested in manually on 8 node yarn cluster and ran unit tests.  Manually tests verified DB created properly and it found them if already existed. Verified that during rolling upgrade credentials were reloaded and running application was not affected.

Test build #65046 has started for PR 14997 at commit 40e6be3.

Test build #65046 has finished for PR 14997 at commit 40e6be3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65046/
Test PASSed.

cc @vanzin

LGTM.

thanks! merging to branch-2.0


There seem to be two identical problem

Thanks for pointing that out.  The question is supposed to be "Which of the following list two valid veth pairs?"  I'm not sure how it got messed up, but I think I fixed it.  You may need to submit the quiz then take it again to get a refresh, or just know what the question is so you can answer it correctly - the answer didn't change.  Thanks again.


Metadata History: "lumina: Certificate verification failed: certificate has expired"

IDA Pro 9.0.240925 - Windows
IDA Pro 9 Windows installer SHA256: e24ae161a8a9d2edde04149c270db3509cb1056841bed0763ae167902f160c9c
Only patched license check in ida.dll.

Open any file in IDA.
Analyze
Right click in the main IDA View-A Window.
Select Lumina and click Metadata History.
Error message in Output Window: lumina: Certificate verification failed: certificate has expired

Pulling/Pushing works fine. It looks like the metadata history is looking elsewhere for the history?

This makes no sense tbh, as it should be using same server for everything. Check what servers you have configured in IDA settings.
Metadata history is likely using primary server.

Sorry! I made typo. I meant to ask is the metadata history doing cert validation/checking somewhere else in the ida.dll, not the lumina server settings in IDA.
I think I found my issue due to my weird setup. Originally I was using a leaked beta2 patched lumina_server_teams that included patched certificate in the binary. The RC1 IDA and Lumina got released and I copied the crack and patched certificate in the binary to the lumina RC1 release. That seems to be the cause of the metadata history warning message.
I'll go look for existing patches for the leaked RC1 lumina90_x64linux.run (sha256: F438C94D27508D0F6D26DC88B1ECA11B35C1184CD979EC5E3BD566A3EA4D66DB)

I meant to ask is the metadata history doing cert validation/checking somewhere else in the ida.dll, not the lumina server settings in IDA.

No it's one single place for all TLS connections IDA makes.

After running with the "-z 0080000" I think I've found my issue. If the secondary server is blank, doing the metadata history attempts to localhost:443, which gives the invalid cert error message. If I set the secondary server to the same as the first I do not get the cert error message.

Guess that means this can be closed then.


Aggregate HCRIS + HIDFL data to county, state, and HRR areas

Once we have the data from #30, we can aggregate to county, state and Hospital Referral Region (HRR) areas. This should lean on the functionality from usa_beds_capacity_analysis_20200313_v2 notebook - this could be a new notebook that refactors the previous one or an edit on top of that notebook that adds the new aggregation levels.
County dataset:

https://eric.clst.org/assets/wiki/uploads/Stuff/gz_2010_us_050_00_20m.json (see existing notebook for usage) (thank you https://eric.clst.org/tech/usgeojson/)

State dataset:

http://www2.census.gov/programs-surveys/popest/datasets/2010-2019/national/totals/nst-est2019-alldata.csv from taken from https://www.census.gov/data/datasets/time-series/demo/popest/2010s-state-total.html

Hospital Referral Region (HRR):

https://atlasdata.dartmouth.edu/static/supp_research_data#boundaries
also https://hub.arcgis.com/datasets/fedmaps::hospital-referral-regions, I think these should be the same

Related issue: #14

I can take this on

Being done as part of #37


The empty string

Hi,

How can the empty string be specified as a negative or positive example?

@OlaperiHS I don't think the program let's you do this.


Manual search has different than dragged in folders auto search

[X ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

When I drag a folder into Caption it should find the same results as it does when I do manual searches. Manual searches for missing subtitles find more results than dragging in a folder.
Current Behavior

If I drag a TV show folder into Caption, it will find subtitles for some episodes but not others. If I then copy the filename of the MKV it cannot find and do a manual search in Caption, it will find several results.
Steps to Reproduce (for bugs)

Drag TV folder into Caption. There will be subtitles found for some episodes but not others.
Copy the filename of an MKV file which could not be found (via dragging in a TV show folder) and paste it into Caption search.
Several results will be found from this manual search, but none will be found when automatically searching by dragging in a TV series/season folder.

Context

Trying to be able to get subtitles for all episodes in a season or series without having to manually do searches for each episode then manually renaming.
Your Environment

Tech
Version

app version
2.0

OS
MacOS

etc

Hi @adro21,
Thanks for filing this issue! 🙌
The file search is slightly different from the text search. File search uses the file hash, file size and file name to find the best match on Open Subtitles.
A possible solution would be to run a text search query on all sources using the file name if no results were returned using file search. However, we don't know which of the results to pick for this specific file, since there may be multiple results when running a text search query.


5G roaming with sepp deployment

Hi @herlesupreeth
I am testing the SEPP of open5gs thanks to your project.
This pull request is a proposal to share my work with you.
As I did some changes in your project I am not sure you can integrate it as is.
I will be happy to update my branch if changes are needed to fit with your project.
I used the open5gs tutorial : https://open5gs.org/open5gs/docs/tutorial/05-roaming/
This imply several changes in your configuration files (use of FQDN in NF,  extra_hosts in compose...)
I added new files in the project for the visited Network:
sa-deploy_V.yaml
.env_v
srsgnb_v.yaml
The Commands to launch the setup are:
Home network:
docker compose -f  sa-deploy.yaml up
Visited network:
docker compose  -f sa-deploy_V.yaml --env-file .env_v  up
Visited gNb
docker compose -f srsgnb_v.yaml  --env-file .env_v  up -d && docker container attach srsgnb
I then succeed to connect an Asus Zenfone 8 with sysmocom SJA5 SIM (PLMN 00101)
I tried to use the radio simulated srsgnb and srsue (ZMQ). But unfortunately srsue failed on the registration AKA.
There is a MAC error in the response. Perhaps it is due to the fact that the UE must use the visited netwotk FQDN to create the response, but I didn't investigated it deeply.
I think there is an issue in Open5gs regarding network isolation. The SCP_v requests to talk in direct with Home AUSF.
I posted an issue on Open5gs project for this:
https://github.com/open5gs/open5gs/issues/3299
I hope this can help your project to grow and wait for your comments,
Have a nice day,
Julien

Hey @JulienSrcdImta Thanks for the PR. I will review today or tomorrow. Just briefly skimmed through this PR and I have a different idea about how to support roaming in this repo. I supported roaming back it was first introduced in open5gs in this branch - https://github.com/herlesupreeth/docker_open5gs/tree/roaming and I was thinking to take similar approach let me know what you think. Also, I think its okay to not support visited network as it could be deployed on an another machine/VM just by changing MNC/MCC

You should be able to test roaming with roaming branch now since its updated to use latest open5gs code


issue with fixed joints in the computeKinematics() function

Hi guys,
I'm currently working with urdf2casadi-matlab and I have encountered an issue with the computeKinematics() function when I set some joints in the urdf as fixed. In particular, I get the error on line 34 (  X{i}{1,j} = eye(smds.NB) ) and I managed to fix it by changing this line with  X{i}{1,j} = eye(6). In this way the code run but I'm not sure about the correctness of the change. I believe it is just an error about the dimension of the matrix X{i}{1,j} which should not depend on the number of active joints but should be always a 6x6 identity matrix. I would have wanted to compare the resulting kinematic with idyntree but I'm having some trouble defining which are the active joints in the object kinDynComp (which is the variable containing the idyntree object inside the computeMassMatrixIDynTree() function inside urdf2casadi-matlab). If you want I can run some test I just need to know how to set the active joints in the idyntree object.
thank you for your help

Thanks for point out this issue @VModugno. Indeed the line you mentioned has a bug:
https://github.com/robotology/urdf2casadi-matlab/blob/c91d729fd02309d5b600164665da604f78d1f23d/Utils/computeKinematics.m#L34
As you correctly noticed, it should be X{i}{1,j} = eye(6);. As for the fixed joints I have started implementing it in:
https://github.com/robotology/urdf2casadi-matlab/blob/c91d729fd02309d5b600164665da604f78d1f23d/Utils/modelExtractionFunctions/accountForFixedJoint.m#L1-L65
I have only tested it with this URDF https://github.com/robotology/urdf2casadi-matlab/blob/master/URDFs/iCub_r_leg.urdf and it seemed to work. As for how to check the number of non fixed joints in iDynTree it should be sufficient to use the following command: kinDynComp.model().getNrOfJoints(). Alternatively, if for example you have a model with only single degree of freedom joints, you can use: kinDynComp.model().getNrOfDOFs().


supports :status => false is ignored on RHEL platforms

Not all rc scripts support 'status' -- many vendor scripts don't have such a thing. These scripts will break a Chef run because the provider forcibly sets the service resource to support 'status':
https://github.com/opscode/chef/blob/master/lib/chef/provider/service/redhat.rb#L42
This breaks Chef, but I'm not totally sure why. Normally before taking a :start action, Chef should check status, and that would return exit code 1 in this situation, so the only thing I can think of is that it's blindly ignoring the exit 1 (maybe another bug...?) The output I'm seeing is that Chef then just blindly tries to start an already-running service, causing the below error.
---- Begin output of /sbin/service jira start ----
STDOUT: Starting jira
STDERR:
---- End output of /sbin/service jira start ----
Ran /sbin/service jira start returned 1
    # In /var/chef/cache/cookbooks/jira/recipes/server.rb

    100: service 'jira' do
    101:   supports :status => false
    102:   action [:enable, :start]
    103: end

    Compiled Resource:
    ------------------
    # Declared in /var/chef/cache/cookbooks/jira/recipes/server.rb:100:in `from_file'

    service("jira") do
      action [:enable, :start]
      supports {:status=>true}
      retries 0
      retry_delay 2
      default_guard_interpreter :default
      service_name "jira"
      enabled true
      pattern "jira"
      declared_type :service
      cookbook_name "jira"
      recipe_name "server"
    end

This is a dup of a bunch of other bugs.

Closing this out since RHEL is going full systemd and the need to fix this is considered low.


Android Studio 3.3 & 3.4: broken IDE integration

Update: problem fixed in Android Studio 3.5

Context: buildSrcVersions is a Gradle plugin that makes it easier to manage your dependencies inside your IDE. It extracts all your dependencies and search for available dependencies updates.
Android Studio 3.3 broke the IDE integration inside the build.gradle files for the code that is available inside the buildSrc module, which is quite sad 😢 This affects users of this plugin (build.gradle.kts files still work though) but also anyone using the buildSrc module

https://github.com/jmfayard/bug-androidstudio-buildsrc is a minimal project that demonstrate the problem
Please star bug # 123032843  IDE integration with the Gradle buildSrc module is broken in Android Studio 3.3

We won on this issue!


Fix dask statistics

Dask statistics were returning nans if any chunk was all-nan.  This fixes that issue, at a slight computational cost (I hope slight, anyway).
Example that I put in a regression test (approximately):
>>> cube = SpectralCube.read('tests/data/example_cube.fits', use_dask=True)
>>> cube._data[:,:,:2] = np.nan
>>> cube.rechunk((1,2,2)).statistics()
{'npts': 28.0,
 'min': <Quantity nan Jy / beam>,
 'max': <Quantity nan Jy / beam>,
 'sum': <Quantity 0.09592362 Jy / beam>,
 'sumsq': <Quantity 0.00211593 Jy2 / beam2>,
 'mean': <Quantity 0.00342584 Jy / beam>,
 'sigma': <Quantity 0.00813614 Jy / beam>,
 'rms': <Quantity 0.00869304 Jy / beam>}

Merging. Tests failures are unrelated.


Disqus:  in Disqus all discussions get the same title.

(I have a solution/workaround for this; documenting in case useful for others, as it involves interaction with another AngularJS Directive in common use).
After embedding a Disqus panel following all the instructions, all my discussions get the same disqus "Title" - see attached screenshot from Disqus).
My config code for the controller:
 $scope.disqusConfig = {
		  disqus_shortname: 'thehawaiiproj',
		  disqus_identifier: 'Book_' + data.bookid,
		  disqus_title: 'A discussion about ' + data.title + " by " + data.authorstring,
		  disqus_url: $scope.canonicalURL
	      };

I've verified that the config does in fact change for each different page.

Turns out the issue is related to my use of the AngularJS ViewHead (https://github.com/apparentlymart/angularjs-viewhead) directive, which allows to control the html Title of the page via a directive.
I think what is going on is that the disqus js code is grabbing the page Title before viewhead has had a chance to alter it. I changed the priority of the viewHead/viewTitle directive to 10, and that seems to have solved the problem. I would still have thought that this Disqus plugin would have overridden that as I do specify a title in the config, but I am unsure of the details here.

I'm actually not sure this is the extent of the issue. It doesn't appear that the other parameters are flowing through to Disqus - e.g. I specified a canonical URL to disqus, but if I visit a page with comments, through a slightly different URL (e.g. http://www.example.com/foo.html and then http://www.example.com/foo.html?foo=bar), the second URL does not show the comments. If I change the dirDisqus plugin as follows, it seems to work:
instead of :
$window.disqus_config = function () {
                        this.language = scope.config.disqus_config_language;
                        this.page.remote_auth_s3 = scope.config.disqus_remote_auth_s3;
                        this.page.api_key = scope.config.disqus_api_key;
                        if (scope.config.disqus_on_ready) {
                            this.callbacks.onReady = [function () {
                                scope.config.disqus_on_ready();
                            }];
                        }
                    };

this:
$window.disqus_config = function () {
                        this.language = scope.config.disqus_config_language;
                        this.page.remote_auth_s3 = scope.config.disqus_remote_auth_s3;
                        this.page.api_key = scope.config.disqus_api_key;

			this.page.identifier = scope.config.disqus_identifier;
			this.page.url = scope.config.disqus_url;
			this.page.title = scope.config.disqus_title;

                        if (scope.config.disqus_on_ready) {
                            this.callbacks.onReady = [function () {
                                scope.config.disqus_on_ready();
                            }];
                        }
                    };

it seems to work ok.
This seems to align with the current version of Disqus docs, which state:

Configuration variables are added within the disqus_config function with exception of your shortname, which is added further down. Example:

how did you solve that problem with the title? I have the same problem, everything else works fine, but the title is the same

Honests @cotts I am not sure if I did fix it. Per my note above I changed the priority on the viewHead directive, and I thought it had fixed it. But in looking at Disqus.com now, I see that the comments appear to be piling up on the same title again.

Also may be relevant: I think the title gets set the first time the thread gets created. If for example the discussion thread got created in the past (e.g. the page already existed before you had this problem), the title may already be wrong in the Disqus database, and thus changing the code in your app won't fix it. It might be possible to fix the title via an API call; I've not tried that as yet. E.g. : https://help.disqus.com/customer/portal/articles/735170-how-can-i-update-discussion-urls-

Thanks @viking2917 , I will do more tests later. I think that happens at least in my case because I make a AJAX requrest with the content of the article and load into the scope after load the disqus directive.
I still having this problem with and without your viewHead Directive.
I will check it again later because this project is paused.


Improvements to work done by @tsvietOK

Improvements to work done by @tsvietOK
In addition to his contributions, we now handle serialization exceptions during the deserialization process by reverting to the default config file's contents.
I'm leaving both PRs open for peer review purposes, but I happen to think mine is more complete unless anyone disagrees.

There is possible JsonReaderException in case of manual json editing by user(for example user made a mistake in json structure). So, i think better to unify all exceptions in this part and if for any reason it can't deserialize json, just reload it from assets.


Hhh

Ng
[Enter feedback here]

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

ID: 0c25827f-08b6-03e4-2997-d39ae6a2b6f4
Version Independent ID: 72b44c07-fd14-7335-de1a-e6e84d17e929
Content: Deployment considerations for Azure Active Directory self-service password reset
Content Source: articles/active-directory/authentication/howto-sspr-deployment.md
Service: active-directory
Sub-service: authentication
GitHub Login: @BarbaraSelden
Microsoft Alias: baselden

@Nuray201313 thanks for reaching out! If you have specific feedback related to this document, please create a new issue describing exactly how you would like this article to improve.


We shouldn't require such a pessimistic version constraint here.

Same change as in the ovirt provider:
https://github.com/ManageIQ/manageiq-providers-ovirt/pull/591
Note, we need this for rails 6.1 support as ovirt_metrics 3.1.0 allows rails 6.1

cc @kbrock (for rails 6.1)

Good catch thanks @jrafanie hard to keep the two repos in sync over 5+ months


Flatcar Container Linux w/ Nvidia Driver

Migrating this issue from GitLab https://gitlab.com/nvidia/container-images/driver/-/issues/31:
Good Afternoon,
I have had success following the instructions for getting this running on flatcar: https://gitlab.com/nvidia/container-images/driver/-/tree/master/flatcar
The only issue I am having is that I am unable to use the --gpus flag. Any advice on how to get this resolved?
Thanks!
Juan

@jpuerto-psc can you share the command you are trying to run and the output you are seeing?

How are you installing NVIDIA Container Toolkit on your machine?

@cdesiniotis - I used the instructions here (https://gitlab.com/nvidia/container-images/driver/-/tree/master/flatcar) when I tried this two years ago. I'd like to note that I have not tried this since originally experiencing these issues two years ago, not sure if this has been resolved since then or not.


Extend release pre-builds to cover Porky (Pico implementation)

Add UF2 build to release build (https://github.com/andrewdavidmackenzie/pigg/issues/399)

Duplicate


Task-83-For-Testing

Note: Will close this one as this still causes bugs and the solution is incorrect.


Hot days vs summer days

Summer days and hot days  indices are identical except for the threshold (now variable in summer days) I propose deleting hot days  function from indices.py
Objections?

So, if I want to calculate the nb of days higher than -15 Celsius between jan and march I use summerdays ? ;)

I guess  so...  Does keeping 'hot days' make more sense

I think it makes more sense!

No, I think we need a generic function like count_above, and then specialized versions that fix the threshold.
If you use a lambda expression for the compute attribute of the Indicator classes, does it work ? It might screw with the argument binding logic.

Been out of the loop for a couple of weeks so discard the suggestion if it does not make sense.
How about a simple wrapper?
def summerdays(data, args...):
    dataout = count_above(data, args... , op=">=20")
   # add metada to dataout
   # etc

That totally works. I was wondering if we could skip that, but I think it would create more trouble than it's worth. Let's do that.

Je suis d'accord pour conserver hot days car ceux-ci se produirons de plus en plus en dehors de l'été.
Je n'ai jamais été une fan de "Summer days".

Ok, I imagine we would want a count_below as well or do we want as even more generic 'count' where we send in the operator as in phil's example

Generic sounds good.
On Thu, Nov 29, 2018 at 9:37 AM Travis Logan<EMAIL_ADDRESS>wrote:

Ok, I imagine we would want a count_below as well or do we want as even
more generic 'count' where we send in the operator as in phil's example
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/Ouranosinc/xclim/issues/120#issuecomment-442856183,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAE9Qz3O6uFsPTt0RSpoSC5Oy9nsqLIiks5uz_E5gaJpZM4Y5srr
.

Proposing class and indicator name of 'tx_days_above' instead of hot days?
variable name = 'txge_30'


Conditional Parameters

This is a copy of #181 (I accidentally merged it and had to revert the main....)
This PR introduces conditional parameters.
What's the problem?
In some cases, we want parameters to take different values depending on the value of other parameters.
One example is the WIMP-mass-dependent signal efficiency uncertainty. Here, we typically have larger uncertainties for lower masses. With conditional parameters, we can now simply add the following to our parameter definition in the config file:
wimp_mass:
    nominal_value: 50
    ...
signal_efficiency:
    conditioning_parameter_name: wimp_mass
    uncertainty:
      5: 0.3
      10: 0.2
      50: 0.15
      100: 0.1
      500: 0.1
    ...

Depending on the value of wimp_mass this will result in a different value of the signal_efficiency uncertainty.
The ConditionalParameter class
Here's an example how the ConditionalParameter class works:
from alea import load_yaml, Parameters

config_path = "%SOMEPATH%/alea/alea/examples/configs/unbinned_wimp_statistical_model_mass_dependent_efficiency.yaml"
config = load_yaml(config_path)

params = Parameters.from_config(config["parameter_definition"])

#  If you directly access a property of the conditional parameter, it will just return the
#  Parameter under nominal conditions (i.e. using the uncertainty for wimp_mass = 50)
print(params.signal_efficiency.uncertainty)
# >>> 0.15

#  The same happens if you call the conditional parameter without any arguments:
print(params.signal_efficiency().uncertainty)
# >>> 0.15

#  If you provide another value though, it will return the parameter for another wimp_mass:
print(params.signal_efficiency(wimp_mass=5).uncertainty)
# >>> 0.3

#  Another way to get there is to change the nominal value of wimp_mass:
params.wimp_mass.nominal_value = 5
print(params.signal_efficiency.uncertainty)
# >>> 0.3

Caveat
So far, this doesn't work "on-the-fly" i.e. if I have a model instance and just change the wimp_mass value it won't correctly update the treatment of the signal efficiency since the likelihood is already initialized with the constraint terms. However, the structure introduced in this PR should allow introducing this feature in the future.
What I tested so far
I tested this in a notebook for a few different WIMP masses (this won't work with the config in alea since we don't have any other WIMP mass templates yet, but you can ask me for an example notebook using actual templates). So far, everything looked good and behaved as expected but heavier testing with large toyMCs will follow.
Please have a look, play around with the new class, and let me know if something unexpected happens. Also, if you have any suggestions on how to implement this better, please let me know! In the meantime, I'll write some unittests and do some first checks with toyMCs.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

75 of 92 (81.52%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.6%) to 91.601%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

alea/parameters.py
75
92
81.52%

Totals

Change from base Build<PHONE_NUMBER>4:
-0.6%

Covered Lines:
1636

Relevant Lines:
1786

💛  - Coveralls


cheq:0.2.1

I am submitting

[ ] a new package
[x] an update for a package

Description: fix bug of reflow in rotate function.

@OrangeX4, thank you for this quick fix.

Thank you :)


[Keyboard Manager] Cleanup header file references to improve incremental build time

Summary of the Pull Request
This PR cleans up many include statements in header files and refactors some code to ensure that WinUI and other large headers are only referenced from the pre-compiled header. This ensures that the WinUI libraries are not built for multiple cpp files.

PR Checklist

[X] Applies to #4867
[X] CLA signed. If not, go over here and sign the CLA
[X] Tests passed

Detailed Description of the Pull Request / Additional comments

For most of the header files, in places where a data type from a header file was only used in function arguments, the header file include was moved to the cpp file, and that data structure was forward declared in the .h file.
Several unused headers were removed or moved to the cpp side, and data structures from specific headers which were forward declared are now fully qualified.
Moved some constructors to the cpp file instead of the header file to reduce include requirements.
Missing headers were added to pch for the KBM Test project
In order to avoid the use of WinUI Xaml controls in the UI .h files (such as StackPanel, TextBlock, etc), these variables were changed to the winRT IInspectable type. In the cpp side, when these objects are constructed the IInspectable members are initialized to their corresponding UI controls (ex: IInspectable x = StackPanel();), and all the members can be accessed by typecasts using the as member function (ex: x.as<StackPanel>().Children().Append();). This was done for all the UI controls in the KeyboardManagerState, SingleKeyRemapControl, ShortcutControl and KeyDropDownControl classes.

Validation Steps Performed
Built in Debug incrementally and with a clean build of the entire solution. KBM tests passed.
TODO: Verify build passes on CI (i.e. using msbuild).

@yuyoyuppe I noticed common.h was included in the pch.h file so I've removed that. Was that the only header to be removed for #4704 or was there anything else?

@arjunbalgovind thanks, I think that was the main offender, so the #4704 could be resolved with this PR. Ideally, we could also measure full/incremental build times when:

disabling pch altogether for those projects
moving the biggest WinUI out of pch

That'd provide useful metrics on an optimal way to move forward with such issues.

@arjunbalgovind thanks, I think that was the main offender, so the #4704 could be resolved with this PR. Ideally, we could also measure full/incremental build times when:

disabling pch altogether for those projects
moving the biggest WinUI out of pch

That'd provide useful metrics on an optimal way to move forward with such issues.

@yuyoyuppe I'll look into that, I found a VS extension which creates graphs for build times of all the projects so I'll use that to analyze it. The KBM projects seem to be taking more than 10 mins of the build time, so it could be possible that pre-compiling WinUI takes longer than just using the required components from WinUI while including it normally.

@yuyoyuppe @ryanbodrug-microsoft I tried disabling pch altogether and I tried moving WinUI out of pch for one project but that resulted in the build time increasing by 4 times.
Instead of tweaking headers, I found that adding a /MP flag in the compile options improved the compile time in all the projects, improving the total KBM build time by about 100 seconds. The flag allows multiple files in the same project in parallel.
Here is the before and after (using this VS extension):

I verified that the functionality is still working and tests run properly. Could there be any caveats/negatives of adding this flag?

@arjunbalgovind based on the docs, it shouldn't be a problem if it reduces the total solution build time.
I wonder how many files msbuild supply to the cl.exe cmd line at once, because for /MP to have any effect, it must be doing that instead of invoking cl.exe for each source.


Add LED for status system restarted.

Completed in commits:
https://github.com/brucestull/raspi-zero-lamp-server/commit/4704f8ec8e16f9a4620e9b9b033b725954fb6281
https://github.com/brucestull/raspi-zero-lamp-server/commit/485412b722a2e07e8f1350df8a3cf64dd1cf53e3


[SPARK-17357][SQL] Fix current predicate pushdown

What changes were proposed in this pull request?
Currently some predicates, which should be pushdown, will not be correctly pushdown in Optimizer.
Predicates simplified to the form that can't be push down before they are pushed down
In Optimizer, Filter operator will go through the rules PushDownPredicate, CombineFilters and BooleanSimplification.
Under this rule order, it is possibly that some predicates that should be able to push down, can't be pushed down through operators.
Because Filter will not pushdown through another Filter node and will wait for combination in the rule CombineFilters later. After the Filters are combined, BooleanSimplification will simplify conditions in the combined Filter and make some predicates, which are able to push down, become unable to push down.
This is this change wants to fix.
Predicates are in the form unable to push down at the beginning
We may need to come out an approach to maintain multiple forms of predicates which at least can benefit pushdown and expression simplification. This will leave to later PRs. Need more discussion.
Change in this patch
After Filters are combined in CombineFilters, this change triggers PushDownPredicates immediately to push down the combined predicates. So the combined predicates will not be simplified by BooleanSimplification before pushing down.
How was this patch tested?
Jenkins tests.

Test build #64766 has started for PR 14912 at commit 9e1c315.

Test build #64766 has finished for PR 14912 at commit 9e1c315.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64766/
Test PASSed.

cc @srinathshankar

Test build #64929 has started for PR 14912 at commit 8f6f91d.

Test build #64929 has finished for PR 14912 at commit 8f6f91d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64929/
Test PASSed.

@srinathshankar I've addressed your comments. Please take a look. Thanks.

@viirya Could you please wait for the CNF predicate normalization rule? @liancheng @yjshen did a few related work before. See https://github.com/apache/spark/pull/10444 and https://github.com/apache/spark/pull/8200.
Let us also collect the inputs from @ioana-delaney @nsyca . They did a lot of related work in the past 10+ years. We need a good design about CNF normalization, which can benefit the other optimizer rules.

hmm, looks like there are previous works regarding CNF but none of them are really merged. @gatorsmile Thanks for the context.

The CNF exponential expansion issue is an important concern in previous works. Actually you can find that this patch doesn't produce a real CNF for predicate. I use splitDisjunctivePredicates to obtain disjunctive predicates and convert them to conjunctive form. The conversion here is not recursive. I think this should prevent exponential explosion. Of course it is a compromise and can't benefit for all predicates. But I would suspect how often a complex predicate need complete conversion of CNF is used.

@srinathshankar @gatorsmile I think CNF is another issue other then the issue this PR was proposed to solve at the first. I would like to solve the original adjoining Filter pushdown problem here. And leave CNF issue (it is not trivial and I don't expect it will be solved soon) for later PRs.
What do you think? Thanks.

Could you define the conditions in which the predicates are unable to be pushed down? Then, we can easily justify the significance.

@gatorsmile I've described it in the pr description.
Simply said, now a Filter will be stopped to pushdown once it encounters another Filter. BooleanSimplification rule will simplify the predicate to a form that can't be pushed down in next round of optimization. For example, (a > 10 || b > 2) && (a > 10 || c == 3) will be simplified as (a > 10) || (b > 2 && c == 3).
This patch does is to perform PushDownPredicate once the adjoining Filters are merged.

also cc @cloud-fan

I am thinking whether it makes more sense to maintain multiple semantically equivalent predicate sets for each Filter. In your example, we have both (a > 10 || b > 2) && (a > 10 || c == 3) and (a > 10) || (b > 2 && c == 3). If we also considering the predicate transitivity inferences and predicate simplication at the same time, we could have multiple semantically equivalent predicate sets. Then, we have more chances to push down the predicates.

To maintain the predicate sets may increase much complexity as I can think. I don't know how big the set could be. But once you change one of the predicates, you need to construct all equivalent predicates in the set too. I think we can maintain CNF and simplification predicates. CNF should be enough to push down predicates and simplification predicate can be used in Filter execution.

Thanks, @gatorsmile, for mentioning me. I will try my best to comment on this thread. Disclaimer: I have not looked at the existing code manipulating predicates/expressions in Spark. Nor have I the code in this PR. I am writing my comment here based solely on the comments I read in this PR.
One of the goals of predicate transformation, in general, is to aid the predicate pushdown. If a new form of a predicate, or a derived form of a superset of a predicate is to be generated, it should be because there is a potential the new form or the derived form can be pushed down further the plan.
Another goal of the transformation is because the new form has a potential to be simplified further.
Taking the example of (a > 10 || b > 2) && (a > 10 || c == 3), I don't see any benefit of transforming to (a > 10) || (b > 2 && c == 3) as it will form a disjunctive predicate. If only b == c by transitivity rule then we may want to do that in order to simplify further to (a > 10 || c == 3 (because b == c and c > 2 && c == 3 can be reduced to c == 3.
The most benefit in the topic of predicate transformation is the equality transitivity property as equality predicates are commonly used in SQL queries. I remember there were a few JIRAs opened, but deferred, to solve this problem. There are some capability in the current version to propagate the equality transitivity but the behaviour is not consistent.
Predicate transformation like extracting common subterms. An example is the predicate (a=1 || b=2) && (a=1 || c=4) and a is a column from a different stream of columns b and c should be transformed to a=1 && (b=2 || c=4). A more complex case is the predicate (a=1 || b=2) && (a=3 || c=4) should have a new predicate (a=1 || a=3) added as a superset predicate to early filter the stream of a to just the two values needed.
Introducing superset, redundant predicates like the last example above will complicate the computation of filter ratios of the predicates on a given stream when we introduce the Cost-based Optimization, which I assume depends on a good estimate of filter ratios on a given stream. This is because we cannot make assumption on the independent filtering affects among a set of predicates. Here the filter ratio of the newly generated superset predicate should be ignored in the filtering estimate.
Another goal of predicate transformation is to derive contradiction and/or tautology. This is achieved by building the inequality relationships among the same column of a set of predicate. A simple example is a>1 && a < 1 should be evaluated to false at the compile time and eliminate the scan of the stream completely. The stream is treated like producing an empty set. Depending on the context, the stream may be substituted by a NULL row when it is a subquery in an existential (EXISTS) or a universal (ALL) subquery, or a singleton NULL value when it is a scalar subquery.

@nsyca Thanks for your detailed comment. I would like to leave the decision of predicate transformation to later PRs, as this PR is not motivated by this.
I think to simplify a predicate such as (a > 10 || b > 2) && (a > 10 || c == 3) to (a > 10) || (b > 2 && c == 3), is to eliminate redundant filtering expressions needed to run in Filter in execution time.
As I said in before comment, my first opinion is not to complicate the predicate handling too much. We can keep a form of predicate which benefits predicate pushdown most, I guess the form should be CNF. We can also keep the simplified form of predicate which is better for execution in Filter.

ping @srinathshankar @cloud-fan @hvanhovell Can you help review this change?
Some context here:
Some predicates are unable to push down because:

Predicates are simplified to the form which is not able to push down

Filter can't push down through Filter. So the predicates in Filter will be simplified to the form unable to push down in next optimizing round. This is this change wants to fix. This change triggers PushdownPredicate in CombineFilters. So combined predicates can be pushed down before BooleanSimplification rule.

Predicates are in the form unable to push down at the beginning

We may need to come out an approach to maintain multiple forms of predicates which at least can benefit pushdown and expression simplification. This will leave to later PRs. Need more discussion.

Test build #65298 has started for PR 14912 at commit f69473f.

Test build #65298 has finished for PR 14912 at commit f69473f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65298/
Test PASSed.

@viirya, I agree that we need a separate set of PRs to address the general problem.
On your comment: "I think the goal to simplify a predicate such as (a > 10 || b > 2) && (a > 10 || c == 3) to (a > 10) || (b > 2 && c == 3), is to eliminate redundant filtering expressions running in Filter in execution time."
My two cents: If that is the case, deferring the simplification to the point just right before the execution time would be an option to consider.

ping @cloud-fan @hvanhovell @srinathshankar again, would you please take a look this? Thanks.

ping @cloud-fan @hvanhovell Can you review this if you have time? Thanks!

ping @cloud-fan @hvanhovell @srinathshankar again, please take look if you have time. Thanks!

ping @cloud-fan @hvanhovell @srinathshankar Can you take a look?

@viirya TBH this seems hacky to me and I'd rather not merge this. I think we should just focus on having proper CNF in the optimizer. I am sorry to disappoint you.

@hvanhovell OK. Let's see if we can have a proper CNF soon. Thank you.


ContainerAppConsoleLogs_CL no longer parses JSON formatted stdout

Please provide us with the following information:

This issue is a: (mark with an x)

[x] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
If the payload being logged was in a JSON format, ContainerAppConsoleLogs_CL would parse it into dynamic columns. Log_s always included the JSON string, but if your payload was:
{
   "timestamp":"2023-10-11T22:17:25.371Z",
   "level":"INFO",
   "thread":"something-1234",
   "logger":"com.nunya.Executor",
   "message":"some message",
   "context":"default"
}

I would see columns for:

Log_timestamp_s
Log_level_s
Log_thread_s
Log_logger_s
Log_message_s
Log_context_s

Now I don't see any of that anymore. This is a typical payload. My JSON objects don't have more than 6 attributes.
I'm wondering:

Why did it stop?
Will parsing of JSON come back?

I have a number of Azure Monitor queries and alerts set up that depend on columns that no longer are being populated.

Same problem on our side. We have Workbook based on these columns.

We are also having this issue.
For now with the Azure Monitor queries we are refactoring to use "parse_json", but this is still quite painful when it comes to log exploration, now that we can't easily use the drag-and-drop grouping for these columns.

We investigated this issue and sincerely apologize for the inconvenience caused by the recent changes in log parsing functionality within Azure Container Apps Log Analytics integration.
Why we made this change
There are a number of issues with dynamically generated columns based on JSON payloads in Log Analytics. This change addresses those issues and improves logging in general:

Avoiding logs dropping due to high JSON nesting levels
Enhancing logging throughput
Mitigating issues with maximum column limits in Log Analytics
Bringing parity with Azure Monitor integration

How to get columns from JSON data

Parsing JSON data in Azure Monitor Log Analytics can be achieved using the parse_json function. This function parses a JSON text and returns a record of the parsed JSON. Here's a generalized approach to parse a JSON-formatted text in a column in Log Analytics:

Example JSON
Assuming Log_s that contains JSON formatted text like this:
{
"Log_message_s": "Example message",
"Log_level_s": "Information",
"Log_trace_id_g": "example-trace-id"
}

Query Example
Here's a basic example of how you might write a Kusto Query Language (KQL) query to parse the JSON data from that column (https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/parsejsonfunction):
ContainerAppsConsoleLogs_CL
| extend ParsedJSON = parse_json(Log_s)
| project
LogMessage = ParsedJSON.Log_message_s,
LogLevel = ParsedJSON.Log_level_s,
LogTraceId = ParsedJSON.Log_trace_id_g

Next Steps:

We are working on developing a fix to allow opting into dynamically generated log columns from JSON data through a config option, to be rolled out in the upcoming weeks. We will provide an ETA for this soon.

Just to support @razum90  - this issue is causing us real pain in our production systems.
Logs are no longer intuitively searchable, our workbooks with predefined filters and links to the correlated traces in the Application Insights no longer work.
Instead of being productive we are spending time on workarounds

We, too, spent some hours investigating why our logs no longer worked – and then some more to fix our saved queries and dashboards depending on log messages. I support @razum90's appeal wholeheartedly.

First and foremost, we'd like to sincerely apologize for the recent changes in the log parsing functionality within Azure Container Apps Log Analytics integration that may have affected your experience. We recognize the importance of continued seamless integration for our users, and we regret the oversight in altering the default behavior without prior notification.
We are working on an emergency fix. Due to the nature of this issue, even rolling back to its original state will again be a breaking change for customers who have since implemented the workaround we posted. Hence, we are requesting customers who need to revert to the old behavior to reach out to us at acasupport(at)microsoft(dot)com so that we can apply a patch on your specific environments.
We are also working on a fix (after the emergency patching is done), to introduce a property on Container App Environments which makes this behavior configurable, under the name dynamicJsonColumns. Details of this feature will be shared once it is Generally Available. We will ensure environments which received the emergency patch will be automatically opted into the right values for this configuration property.
Thanks,
Azure Container Apps Team

Yesterday, in one of our subscriptions the behavior has reverted to the old one without us having requested this and without prior notice, breaking our log queries again.

@sebastian-hans-swm  can you send your subscription id and environment name to acasupport(at)microsoft(dot)com. We will analyze and find out what happened.

@JennyLawrance, I did that (on Nov, 2nd, subject: "Reverted log parsing behaviour") and did not receive feedback of any kind. 😞

First and foremost, we'd like to sincerely apologize for the recent changes in the log parsing functionality within Azure Container Apps Log Analytics integration that may have affected your experience. We recognize the importance of continued seamless integration for our users, and we regret the oversight in altering the default behavior without prior notification.
We are working on an emergency fix. Due to the nature of this issue, even rolling back to its original state will again be a breaking change for customers who have since implemented the workaround we posted. Hence, we are requesting customers who need to revert to the old behavior to reach out to us at acasupport(at)microsoft(dot)com so that we can apply a patch on your specific environments.
We are also working on a fix (after the emergency patching is done), to introduce a property on Container App Environments which makes this behavior configurable, under the name dynamicJsonColumns. Details of this feature will be shared once it is Generally Available. We will ensure environments which received the emergency patch will be automatically opted into the right values for this configuration property.
Thanks, Azure Container Apps Team

Is there any release date of this configuration?

Updates on JSON log parsing behavior
Recently, Azure Container Apps Environments introduced a new property called DynamicJsonColumns to control the logging behavior for JSON formatted logs in Azure Log Analytics.
When set to false, logs will be stored in the Log column as raw string regardless of format. When set to true, JSON formatted logs will automatically be split into dynamic columns in Log Analytics based on the property name of the JSON object, and the Log column will be empty.
For example, if DynamicJsonColumns = true, and your log content is:
{
   "timestamp":"2023-11-15T22:00:00Z",
   "logger":"my.json.logger",
   "content":
   {
      "message":"hello world message",
      "level":"info"
   }
}

You will see the following columns in Log Analytics:
Log_timestamp_s = 2023-11-15T22:00:00Z
Log_logger_s = my.json.logger
Log_content_message_s = hello world message
Log_content_level_s = info

How to change the DynamicJsonColumns property
By default, DynamicJsonColumns is false. If you were one of the customers who requested the Product team to revert the JSON parsing changes prior to the introduction of the DynamicJsonColumns property, then your environment will have DynamicJsonColumns set to true with no further action required.
The  DynamicJsonColumns property can be changed through an ARM request or with the Azure CLI.
To change the DynamicJsonColumns through the Azure CLI, you must have the containerapp extension installed with version 0.3.44 or above. Please run az version to check the current version, and az upgrade to upgrade the CLI to the latest version if necessary.
{
  ....
  "extensions": {
    "containerapp": "0.3.44",  << Make sure your containerapp extension is in 0.3.44 or above.
  }
}

To enable or disable the DynamicJsonColumns on an existing Container App Environment, you can run the following command:
az containerapp env update --subscription <subscription> --resource-group <resource_group> --name <containerapp-env-name> --logs-dynamic-json-columns true/false

To change the DynamicJsonColumns using ARM, simply set the property on the Container App Environment resource as shown here:
{
    "id": "<resource id>",
    "name": "<name>",
    "type": "Microsoft.App/managedEnvironments",
    "location": "West US",
    "properties": {
        "appLogsConfiguration": {
            "destination": "log-analytics",
            "logAnalyticsConfiguration": {
                "customerId": "<log-analytics-customer-id>",
                "sharedKey": "<log-analytics-key>",
                "dynamicJsonColumns": true
            }
        },
    }
}

Limitations:

DynamicJsonColumns currently cannot be changed from the Azure Portal. This capability is coming soon.
The DynamicJsonColumns is only supported for Azure Log Analytics. For Azure Monitor, JSON formatted logs will be store as a raw string in the Log column.
The recommended maximum number of dynamic columns is 50.
Column names have a maximum of 45 characters.
The DynamicJsonColumns for the Consumption workload in the Consumption + Dedicated environment doesn't support today.

We are continuously taking steps to improve the service and our processes to ensure such incidents do not occur in the future.
We apologize for any inconvenience.
Regards,
The Microsoft Azure Team

I like writing queries using dot path to access my log data (therefore using parse_json), however:
The function parse_json triggers full parsing of this text which might consume extensive compute resources when original string is large and volume of records is high.

Is there a way NOT to use the DynamicJsonColumns option but still having my Log_s parsed by default as a dynamic column (like Log_json or something)? Or is it exactly the same as adding a parse_json in every query?

Hi @random42, there is no way to achieve what you want. You should use either:

Set DynamicJsonColumns to split the JSON to columns in LA
Or use the parse_json to split the JSON during the query time.

@howang-ms

The DynamicJsonColumns for the Consumption workload in the Consumption + Dedicated environment doesn't support today.

I’m not sure what you mean by that. Can you elaborate?
I've tested dynamicJsonColumns: true for all workload profile combinations, but neither produces structured logs given a sample log line like this:
{"hostname":"MacBook-Pro-M2.lan","level":"info","msg":"Listening on :8000","time":"2023-12-28T15:01:41+01:00"}

Consumption tier only: No additional columns are created. The Log_s column remains empty, so now I’m losing  log messages.
Consumption profile on Consumption + Dedicated tier: Log_s contains the JSON log output written by Container App, so nothing has changed.
Dedicated profile on Consumption + Dedicated tier: The Log_s column remains empty…

Am I missing something?

@joergjo, what I mean is:

Consumption profile on Consumption + Dedicated tier: Log_s contains the JSON log output written by Container App, so nothing has changed.

This is expected for today. And we are working on the support now, which should be deployed very soon.
But another two scenarios are not expected. You should see new columns like Log_hostname_s in your LA. Can you double check by query the Log_hostname_s column directly? Sometimes the LA will hide the column from default view if you have lot of logs don't have this column. If it still not working, please send your container app env FQDN to  acasupport at microsoft dot com. So we can double check.

Big thanks to the ACA team for getting to the bottom of this. The keyword here is patience - it does take some time before the columns show up 😁.

Hi @howang-ms, is there an update as to whether the Consumption profile on Consumption + Dedicated tier is supported/when this will be supported?

In my project, I use a structured logger, but when I output logs in JSON format, I have trouble reaching the maximum number of columns, and no logs are recorded. so I had no choice but to output logs in text format. It's so bad.
Now I found this Issue. I hope this method will resolve your issue.
I will try this, thanks team.

Updates on JSON log parsing behavior
Recently, Azure Container Apps Environments introduced a new property called DynamicJsonColumns to control the logging behavior for JSON formatted logs in Azure Log Analytics.
When set to false, logs will be stored in the Log column as raw string regardless of format. When set to true, JSON formatted logs will automatically be split into dynamic columns in Log Analytics based on the property name of the JSON object, and the Log column will be empty.
For example, if DynamicJsonColumns = true, and your log content is:
{
   "timestamp":"2023-11-15T22:00:00Z",
   "logger":"my.json.logger",
   "content":
   {
      "message":"hello world message",
      "level":"info"
   }
}

You will see the following columns in Log Analytics:
Log_timestamp_s = 2023-11-15T22:00:00Z
Log_logger_s = my.json.logger
Log_content_message_s = hello world message
Log_content_level_s = info

How to change the DynamicJsonColumns property
By default, DynamicJsonColumns is false. If you were one of the customers who requested the Product team to revert the JSON parsing changes prior to the introduction of the DynamicJsonColumns property, then your environment will have DynamicJsonColumns set to true with no further action required.
The DynamicJsonColumns property can be changed through an ARM request or with the Azure CLI.
To change the DynamicJsonColumns through the Azure CLI, you must have the containerapp extension installed with version 0.3.44 or above. Please run az version to check the current version, and az upgrade to upgrade the CLI to the latest version if necessary.
{
  ....
  "extensions": {
    "containerapp": "0.3.44",  << Make sure your containerapp extension is in 0.3.44 or above.
  }
}

To enable or disable the DynamicJsonColumns on an existing Container App Environment, you can run the following command:
az containerapp env update --subscription <subscription> --resource-group <resource_group> --name <containerapp-env-name> --logs-dynamic-json-columns true/false

To change the DynamicJsonColumns using ARM, simply set the property on the Container App Environment resource as shown here:
{
    "id": "<resource id>",
    "name": "<name>",
    "type": "Microsoft.App/managedEnvironments",
    "location": "West US",
    "properties": {
        "appLogsConfiguration": {
            "destination": "log-analytics",
            "logAnalyticsConfiguration": {
                "customerId": "<log-analytics-customer-id>",
                "sharedKey": "<log-analytics-key>",
                "dynamicJsonColumns": true
            }
        },
    }
}

Limitations:

DynamicJsonColumns currently cannot be changed from the Azure Portal. This capability is coming soon.
The DynamicJsonColumns is only supported for Azure Log Analytics. For Azure Monitor, JSON formatted logs will be store as a raw string in the Log column.
The recommended maximum number of dynamic columns is 50.
Column names have a maximum of 45 characters.
The DynamicJsonColumns for the Consumption workload in the Consumption + Dedicated environment doesn't support today.

We are continuously taking steps to improve the service and our processes to ensure such incidents do not occur in the future.
We apologize for any inconvenience.
Regards,
The Microsoft Azure Team

When will the feature dynamicJsonColumns be GA ?


NTR: Purine nucleotide import into lysosome

Please provide as much information as you can:

Suggested term label:
Purine nucleotide import into lysosome

Definition (free text)
The directed import of purine nucleotide from the cytosol, across the lysosomal membrane, into the lysosome.

Reference, in format PMID:#######
PubMed=23876310, PubMed=18375752

Gene product name and ID to be annotated to this term
SLC17A9

Parent term(s)
GO:0015865  purine nucleotide transport
GO:1901679  nucleotide transmembrane transport

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?

Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)

Cross-references

For enzymes, please provide RHEA and/or EC numbers.

Can also provide MetaCyc, KEGG, Wikipedia, and other links.

Any other information

+[Term]
+id: GO:0141013
+name: purine nucleotide import into lysosome
+namespace: biological_process
+def: "The directed import of purine nucleotide from the cytosol, across the lysosomal membrane, into the lysosome."


Stuck on 0 FPS

Describe your bug here.
When i open Psych engine, it's just a black screen and it's just on 0 fps
any way to fix this?
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

Someone please help me, this is stressing me out

please help me, i just want to use psych engine again.

then goto C:\Users\ur name\AppData\Roaming\ShadowMario\PsychEngine\ninjamuffin99
and delete controls_v2.sol file

nope, didnt work

nevermind, i kinda tried ur thing and i just deleted the psych engine folder and reopened the exe
it works now i guess, thanks!


Added Windows to CI

Dependencies were installed successfully, but some tests failed due to exceeding memory limits.

For MacOS
ERROR: Cannot install ammico because these package versions have conflicting dependencies.
The conflict is caused by:
salesforce-lavis 1.0.2 depends on decord
salesforce-lavis 1.0.0 depends on decord
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

To make pycocotools work on Windows OS one needs to install vs_BuildTools.exe from https://visualstudio.microsoft.com/visual-cpp-build-tools/ and choose following elements:

Visual Studio extension development
MSVC v143 - VS 2022 C++ x64/x86 build tools
Windows 11 SDK
That requires 7.04 Gb space on one's drive.


Add temporary fix to MetaEvalNLGCITest to fix flakiness

This PR adds a workaround to fix the flakiness of MetaEvalNLGCITest as discussed in #537. The code change is cherry-picked from #532 (including suggestions by @neubig) because other pull requests get affected by the flakiness and because #532 is still in review.

@pfliu-nlp Thanks for merging!


Telemetry collector is catching BQ's internal open telemetry

Running select distinct implementation_module_name from intelligence_dwh.soda_sql_telemetry.base_soda_sql_events returns google.cloud.bigquery.opentelemetry_tracing which made one of our reporting transformation DQ test fail.
We should ideally avoid catching telemetry messages coming from other libraries so that we don't end up polluting our events with stuff that other people track.

What I'm not sure I understand is why those events get pushed into our collector. Is it something about how we implemented it that somehow redirects BQ's collector URL to ours?
It seems like the more people would implement OT the more everyone would start collecting each other's data which is less than ideal.

BigQuery library only creates spans - and provides a way to collect the instrumentation data (https://github.com/googleapis/python-bigquery#instrumenting-with-opentelemetry). The library doesn't have any collector by default.
Since we configure a collector ourselves, the data is pushed to it because the spans are created. There can be many different exporters configured in an application. And there is no easy way to (https://github.com/open-telemetry/opentelemetry-collector/issues/2310) disable it.
I'll see if we can monkey-patch python-bigquery or perhaps create a version of exporter.

fixed, we filter out any non-soda spans very strictly based on their name (span name starts with soda)


Input 'parameters' is supposed to be not required but fails when empty / not present

action.yml defines required: false for parameters, but the const is set to required=true.
    const parameters = (0,core.getInput)('parameters', {         required: true,         trimWhitespace: true,     });
Running this action with out the option parameters: for cloudformation stacks that have no parameters fail.
Also specifying 'parameters:' with empty values fails as function getInput throws on any empty value.
Input required and not supplied: parameters

Thanks for the bug report. I'll release a fix very soon.

Thanks Richard! Also, hi from the other side of the world from a fellow Yorkshire-man!

 :)
This should be fixed now. Can you try v1.0.1 and let me know if you have any probs?

Had a few issues publishing the release. v1.0.1 should be available now.

Just ran from master, seems to be working now.
Getting some errors from the following action (your github-actiion-issue-comment from the downstream 'peter-evans/find-comment@v1' action, but i will troubleshoot tomorrow and follow up on that repo if need be.
Cheers!
Matt

Hmm. Let me know once you discover what's going there.
Here's how i use the PR comments action in this repo: https://github.com/badsyntax/github-action-aws-cloudformation/blob/4b5155352c1aed34b796766792ff5d4b4199a4ab/.github/workflows/test-build-deploy.yml#L60-L84

Thanks, I got it working in a workflow dispatch. I think the errors I'm seeing are downstream in one of the sub-actions (rate limiting causing missing comments when running in a matrix), and not related to this issue.


Set Up Your SAP Cloud Platform Integration Tenant

Tutorial URL: https://developers.sap.com/tutorials/cp-starter-integration-cpi-onboard-subscribe.html
In Step 4 on 4th instruction screenshot showing  Provision button, but in application there is no  Provision button instead there is "Activate" button.

Hi Shivakumar,
Thank you for reaching out to us.
I understand your concern, could you please share with me the below details to investigate the issue further?

Global Account name & ID
Subaccount name and ID
Error message or the screenshots.

We truly appreciate your support and looking forward to hearing from you.
Regards,
Vikram Kulkarni

Hello Team,
I am facing issues with my Tenant provisioning. The same is getting stuck after completion of 18 percent. Earlier I thought maybe I will try with a new account. But I faced the same problem.
Here are my trial account details:
Global Account: ba30d83atrial
Subaccount: trial
Error Message:
Tenant provisioning is in progress and it can take 20 minutes. Please wait for the provisioning to complete before creating service broker instances.
Global Account: 931506cctrial
Subaccount: trial
Error Message:
Tenant provisioning is in progress and it can take 20 minutes. Please wait for the provisioning to complete before creating service broker instances.
Please do the needful so that I can set up the tenant provisioning successfully.
Regards
Gourav Jena

Hi Gourav,
Thank you for sharing the requested details.
I involved the internal team to check and provide the necessary fix for the concern you raised. I am working closely with them and keep you posted with an update.
We truly appreciate your support and patience.
Regards,
Vikram Kulkarni

Hi @gouravkumarjena,
Could you please share the complete application URL?
Click in the Process Integration--> Click Go to Application --> and share that URL with us.
We truly appreciate your support and looking forward to hearing from you.
Regards,
Vikram Kulkarni

Hi @Vikramkulkarni01
Please find the below URL: (for Global Account: ba30d83atrial)
https://ba30d83atrial.it-cpitrial01-app-prov-sap.cfapps.eu10.hana.ondemand.com/manageTenant/cpi-tenant/v1.0/goToApplication
Kindly let me know if you need any further information.
Regards
Gourav

Hi @gouravkumarjena ,
Thank you for sharing the information with me.
I am working closely with them and keep you posted with an update.
We truly appreciate your support and patience.
Regards,
Vikram Kulkarni

Hi @Vikramkulkarni01
Could you please let me know the status of the issues which I raised?
Did you get any kind of solution for the same?
Regards
Gourav

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


avoids cleanup logging and introduces clone_flags option

fixes https://github.com/hasura/smooth-checkout-buildkite-plugin/issues/31
Avoiding cleanup logs
Having delete_checkout option set to true, will try to remove the checkout directory files as a normal user and via sudo if faced with errors as a normal user. If there are huge number of files to be deleted and if the normal user doesn't have permissions to delete them, then we might encounter a lot of log lines in buildkite logs due to this which would be noise, because the sudo remove would most probably succeed after that.
Hence, starting from this release we default to not show the errors of rm -rf while running it as normal user.
clone_flags option
We now have clone_flags option as part of the config, which could be used to pass the command line flags that will be used while doing git clone in the smooth checkout plugin.
steps:
  - command: echo "Checks out repo at given ref"
    plugins:
      - hasura/smooth-checkout#v3.1.0:
          repos:
            - config:
              - url: git@github.com:<username>/<reponame>.git
                ref: <ref> # (optional)
                clone_flags: <flags> # (optional) flags to use with `git clone` command

Tested via this build: https://buildkite.com/hasura/smooth-checkout-buildkite-plugin-integration-tests/builds/28


Replace host str to use https if encrypted

During our testing in https://github.com/timberio/vector/pull/787 we found that there is an issue with hyper connecting to a tls connected docker engine that provided a host url of tcp://.... I found the way to fix this was to replace the tcp scheme with https. This seems to work for when encrypted tcp streams are active. The error hyper produces was a version parse error which seemed odd. This seemed to do the trick.
Related to #192

Could we add a little code comment above these  lines to capture the context. I could see my future self coming back to this a year from now and asking "why?"

@softprops Sorry for the delay I've added a comment, if we could get a release that would be very appreciated, let me know what I can do to help!

Thanks. I'm gonna shoot for at least this weekend.

Thank you Doug <3


WslRegisterDistribution failed with error: 0x80070005

While trying to install it from Windows Store, the error in the aforementioned image appears.
I tried both normally and with elevated permission.
Windows 10 2004 Build 19041

Please try to disable the WSL (+ Hyper-V if you use that) feature, reboot, re-enable it, reboot and try again.
I've seen this error before last time it was caused by a windows update.

Please try to disable the WSL (+ Hyper-V if you use that) feature, reboot, re-enable it, reboot and try again.
I've seen this error before last time it was caused by a windows update.

For the rest of us mere mortals can you translate that into steps that we can follow?

@airtonix There is a bug in some version of windows involving windows update breaking that feature.
That's:

Please try to

disable the WSL (+ Hyper-V if you use that) feature
reboot
re-enable it
reboot
and try again.


Add option to not rely on Internet connectivity during test stage

This PR fixes two issues that were introduced in #2081:

Adds a parameter JSON_TestDataDirectory to pass a directory of test files to avoid checking them out during ctest stage.
Adds label git_required to tests that require a Git checkout and would fail if library is downloaded other than via Git.
Add documentation to the test section of the README file.

Closes #2189

Coverage remained the same at 100.0% when pulling 24992003d99fefdd9fb5a605f0eb58a05a91985b on issue2189 into 74c6e4295ff0f996baa6e4e8905db4203d023216 on develop.

🔖 Release item
This issue/PR will be part of the next release of the library. This template helps preparing the release notes.
Type

[ ] ✨ New Feature
[ ] 🐛 Bug Fix
[ ] ⚡ Improvement
[x] 🔨 Further Change
[ ] 🔥 Deprecated function

Description

Add a CMake switch to use a previously downloaded folder with test files in case Internet connectivity is not present during test stage. #2189 #2190 #2202


refactor - migrate simple components to stateless functional components [ready]

This PR is one of a series to migrate some of our simple components within this library to stateless functional components.

💯

LGTM

:+1:

<3 <3 <3


cant authenticate

Hi, I downloaded symantec VIP and told schwab about it. i dont understand where I get the topt token from

Hi. Please follow the instructions at https://github.com/itsjafer/schwab-api#create-a-totp-authentication-token to get a:

Symantec ID to give Schwab
TOTP token to give the API

I figured out the code comes from Google Authenticator not VIP at all.  Did not need VIP.  Directions hard to follow on that part.
thanks


Checkbox doesn't work with callouts

When using a callout with key:: false/true, the plugin  does not convert the value to checkboxes

The checkbox not working in any "preview" block, like tables, callouts, etc. is an implementation limitation. It should still show when editing the block, but not when it is being previewed.
No support for preview blocks is planned right now.


1.2.0 and JQuery On Events Stopped Working

I just upgraded my install to 1.2.0, now my jquery on events stopped firing.
This does not work:
$('#tree').on('nodeSelected', function (event, node) {
     console.log(node);
 });

However, this does work:
 $('#tree').treeview({
          onNodeSelected: function(event, node) {
                console.log(node);
     }
  });

Not sure what I did to cause this, any ideas?
running jquery 2.1.4, and bootstrap 3.3.5

That's strange, I did make some changes to the plugin wrapper and the way it exposes the treeview instance to the caller in 1.2.  Although I'm not sure how this would have affected your events in this way.
I've just run a very basic test against the 1.2 online demo and it appears to work.  You can try it yourself, visit 1.2 online demo and copy the following into the console.
$('#treeview1').on('nodeSelected', function (event, data) {
  console.log('You clicked '  +data.text);
});

I got something else going on, I ran the code in the console on my app and the event fired just fine. Will close this thanks Jon.

Just a head's up on what I did wrong in case anyone else runs into this, I was wiring up the event outside of a callback. Not sure if this is expected behavior or not as it worked in previous versions outside of a callback.
$.getJSON('/nodes', function(data) {
  $('#tree').treeview({ data: data  });
});

$('#tree').on('nodeSelected', function(event, node) {
   console.log('test');
});

vs
$.getJSON('/nodes', function(data) {
  $('#tree').treeview({ data: data  });
  $('#tree').on('nodeSelected', function(event, node) {
     console.log('test');
  });
});

Aha, that makes sense!  Although it's not the fact that it's in the callback that makes it work, rather the order you're call them.  The events should be registered after the treeview has been initialized, as re-initializing the tree will discard any previously registered events.


fix: galoy client cors bug

Why downgrade? If galoy client has a bug we should fix it and upgrade

Why downgrade? If galoy client has a bug we should fix it and upgrade

v 1.60 is the last known good state (to me) for the web wallet code since the were both last updated about a month ago. not sure if breaking changes were introduced in later version with all the changes @nicolasburtey has been making on the mobile app https://github.com/GaloyMoney/galoy-client/pull/175/files


Compilation stuck on  Completed 'bootloader'.  (CON-472)

I am trying to compile the light example but it gets stuck on Completed 'bootloader'. All other examples have the same issue.
I am using esp-idfv4.4.2 on  mac
leep.c.obj
[75/97] Building C object esp-idf/esp_rom/CMakeFiles/__idf_esp_rom.dir/patches/esp_rom_uart.c.obj
[76/97] Building C object esp-idf/esp_common/CMakeFiles/__idf_esp_common.dir/src/esp_err_to_name.c.obj
[77/97] Building C object esp-idf/log/CMakeFiles/__idf_log.dir/log_noos.c.obj
[78/97] Building C object esp-idf/main/CMakeFiles/__idf_main.dir/bootloader_start.c.obj
[79/97] Building C object esp-idf/log/CMakeFiles/__idf_log.dir/log_buffers.c.obj
[80/97] Building C object esp-idf/log/CMakeFiles/__idf_log.dir/log.c.obj
[81/97] Building C object esp-idf/esp_hw_support/CMakeFiles/__idf_esp_hw_support.dir/port/esp32/rtc_clk.c.obj
[82/97] Linking C static library esp-idf/log/liblog.a
[83/97] Linking C static library esp-idf/esp_rom/libesp_rom.a
[84/97] Linking C static library esp-idf/esp_common/libesp_common.a
[85/97] Linking C static library esp-idf/xtensa/libxtensa.a
[86/97] Linking C static library esp-idf/esp_hw_support/libesp_hw_support.a
[87/97] Linking C static library esp-idf/esp_system/libesp_system.a
[88/97] Linking C static library esp-idf/efuse/libefuse.a
[89/97] Linking C static library esp-idf/bootloader_support/libbootloader_support.a
[90/97] Linking C static library esp-idf/spi_flash/libspi_flash.a
[91/97] Linking C static library esp-idf/micro-ecc/libmicro-ecc.a
[92/97] Linking C static library esp-idf/soc/libsoc.a
[93/97] Linking C static library esp-idf/hal/libhal.a
[94/97] Linking C static library esp-idf/main/libmain.a
[95/97] Linking C executable bootloader.elf
[96/97] Generating binary image from built executable
esptool.py v3.3.2-dev
Creating esp32 image...
Merged 1 ELF section
Successfully created esp32 image.
Generated /Users/abhijit/esp/esp-matter/examples/light/build/bootloader/bootloader.bin
[97/97] cd /Users/abhijit/esp/esp-matter/examples/light/build/bootloader/esp-idf/esptool_py && /Users/abhijit/.espressif/python_env/idf4.4_py3.8_env/bin/python /Users/abhijit/esp/esp-idf/components/partition_table/check_sizes.py --offset 0xc000 bootloader 0x1000 /Users/abhijit/esp/esp-matter/examples/light/build/bootloader/bootloader.bin
Bootloader binary size 0x6330 bytes. 0x4cd0 bytes (44%) free.
[1144/1298] Completed 'bootloader'

@abhijits3 Can you please retry with the updated IDF commit?
For ESP32, ESP32-C3, and ESP32-S3, ESP-IDF v5.0.1 release is required. and for ESP32-C2, ESP32-H2(preview) and ESP32-C6(preview) and Zigbee Bridge example, ESP-IDF branch at commit bb9200ace in branch release/v5.1 should be used.

Tried with commit bb9200ace. Now it stuck at libespressif__mdns.a
-- Components: bootloader bootloader_support efuse esp_app_format esp_common esp_hw_support esp_rom esp_system esptool_py freertos hal log main micro-ecc newlib partition_table soc spi_flash xtensa
-- Component paths: /Users/abhijit/esp/esp-idf/components/bootloader /Users/abhijit/esp/esp-idf/components/bootloader_support /Users/abhijit/esp/esp-idf/components/efuse /Users/abhijit/esp/esp-idf/components/esp_app_format /Users/abhijit/esp/esp-idf/components/esp_common /Users/abhijit/esp/esp-idf/components/esp_hw_support /Users/abhijit/esp/esp-idf/components/esp_rom /Users/abhijit/esp/esp-idf/components/esp_system /Users/abhijit/esp/esp-idf/components/esptool_py /Users/abhijit/esp/esp-idf/components/freertos /Users/abhijit/esp/esp-idf/components/hal /Users/abhijit/esp/esp-idf/components/log /Users/abhijit/esp/esp-idf/components/bootloader/subproject/main /Users/abhijit/esp/esp-idf/components/bootloader/subproject/components/micro-ecc /Users/abhijit/esp/esp-idf/components/newlib /Users/abhijit/esp/esp-idf/components/partition_table /Users/abhijit/esp/esp-idf/components/soc /Users/abhijit/esp/esp-idf/components/spi_flash /Users/abhijit/esp/esp-idf/components/xtensa
-- Configuring done (13.7s)
-- Generating done (0.4s)
-- Build files have been written to: /Users/abhijit/esp/esp-matter/examples/light/build/bootloader
[102/103] Generating binary image from built executableesptool.py v4.5.1
Creating esp32 image...
Merged 1 ELF section
Successfully created esp32 image.
Generated /Users/abhijit/esp/esp-matter/examples/light/build/bootloader/bootloader.bin
[103/103] cd /Users/abhijit/esp/esp-matter/exampl...er/examples/light/build/bootloader/bootloader.binBootloader binary size 0x6790 bytes. 0x4870 bytes (41%) free.
[626/1151] Performing configure step for 'chip_gn'Done. Made 297 targets from 230 files in 674ms
[975/1151] Building C object esp-idf/espressif__l...sif__led_strip.dir/src/led_strip_rmt_ws2812.c.objIn file included from /Users/abhijit/esp/esp-matter/examples/light/managed_components/espressif__led_strip/src/led_strip_rmt_ws2812.c:20:
/Users/abhijit/esp/esp-idf/components/driver/deprecated/driver/rmt.h:18:2: warning: #warning "The legacy RMT driver is deprecated, please use driver/rmt_tx.h and/or driver/rmt_rx.h" [-Wcpp]
18 | #warning "The legacy RMT driver is deprecated, please use driver/rmt_tx.h and/or driver/rmt_rx.h"
|  ^~~~~~~
[996/1151] Linking C static library esp-idf/espressif__mdns/libespressif__mdns.a

Thanks..thats worked

@abhijits3 Matter is a big project and compilation takes more time than usual, be patient and wait till the compilations gets successful.
There are two variants of build system being used here, gn and cmake, cmake triggers the gn for compiling files in connectedhomeip repository so when you see something being stuck it is actually compiling files in connectdhomeip repository.

Please close the issue if example compiles successfully.

v5.0.1 release keeps on giving the message Please use idf.py only in an ESP-IDF shell environment.

This means you are not using idf python environment and using different python environment for building the matter application.
Please follow development setup guide to not run into such issues.
Also, you can check the active python environments by below command
which -a python3

If the very first one shall be similar to /Users/shubhampatil/.espressif/python_env/idf5.0_py3.11_env/bin/python3.

yes. I followed this guide
which -a python3 output is:
/Users/abhijit/.espressif/python_env/idf5.0_py3.8_env/bin/python3
/usr/bin/python3

Looking at python3 interpreter path, you have installed the idf tools perfectly.
I could suspect one thing though that build directory still have the stale stuff from idf v4.4.x
Can you please clean up the build and sdkconfig and try again in fresh terminal?
/// open new terminal
cd esp-idf
source export.sh
cd  esp-matter
source export.sh
cd examples/light
rm -rf sdkconfig build
idf.py build

Sorry that didnt work. Just running
/// open new terminal
cd esp-idf
source export.sh
gave the message:
Done! You can now compile ESP-IDF projects.
Go to the project directory and run:
idf.py build
Please use idf.py only in an ESP-IDF shell environment.

I followed the complete steps again in a different folder and the issue seems resolved. Not sure what the problem with the original installation was. Closing for now. Will reopen if the issue persists

Glad to hear that you have a working setup!


[BEAM-13000] Disable Reshuffle Translation in Samza Portable Mode

Before BEAM-12999 is resolved, disable reshuffle translation in Samza Portable Pipeline
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run XVR_Samza PostCommit

Run Go Samza ValidatesRunner

Run Python Samza ValidatesRunner

Run Java Samza PortableValidatesRunner

Run Samza ValidatesRunner

Go Tests failed with a different issue https://ci-beam.apache.org/job/beam_PostCommit_Go_VR_Samza/319/
This PR is only intended to fix python and cross language tests.


Adjusted recipes to support the ore dictionary entries for sticks and…

… chests.
This helps when using mods like Charset - Storage or similar that modify the existing recipes for chests.  If no mods exist that adjust these, the recipes still work.

Merged, thanks for the adjustments ^^


Feat(plugins/Correlation ID) add new Generators

See Also [https://github.com/Mashape/kong/issues/1228]

Manually merged in the release/0.9 branch to be deployed for the 0.9 release, thanks!