[e2e]: nodejs tag main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.59
Run: https://github.com/slsa-framework/example-package/actions/runs/5185196971
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.59
Date: Tue Jun  6 06:15:11 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.65
Run: https://github.com/slsa-framework/example-package/actions/runs/5185635456
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.65
Date: Tue Jun  6 07:14:58 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.67
Run: https://github.com/slsa-framework/example-package/actions/runs/5185855847
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.67
Date: Tue Jun  6 07:40:01 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.68
Run: https://github.com/slsa-framework/example-package/actions/runs/5185897042
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.68
Date: Tue Jun  6 07:45:16 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.69
Run: https://github.com/slsa-framework/example-package/actions/runs/5189328313
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.69
Date: Tue Jun  6 13:50:50 UTC 2023
Tests are passing now. Closing this issue.


Configurable SQL table prefix

I would like to see this on the config for better order when i read my database, since it got a lot of table

There is a sql refactoring in the works at the moment. As I am the one coding it, I can assure you that a table prefix will be configurable when the changes have been released.
Until then I would suggest just creating a database dedicated to TE.


Ortelius in a box v2 | Repo creation | Terraform foundations

As a DevOps Engineer, I would like a repo for me to begin the foundational work to deploy Ortelius version 2 with Terraform.
Thank you.

@sachajw here is the new repo https://github.com/ortelius/ortelius-v11-dev-env


Netatmo: Hotfix for hass 0.29

Description:
Hotfix for hass 0.29
Related issue (if applicable): fixes #

🐬


Refactor analysis waiting page

To look nicer with all the buttons on the left side, in a tabular way

This has to be solved on MOI - PR done there: https://github.com/biocore/mustached-octo-ironman/pull/37

@josenavas if this was solved in moi, can we close this?


Allow pallet-election-provider to accept smaller solutions as well

fixes #9478
Amended some tests that were failing and won't fail after this change.
@kianenigma
Polkadot address: 131dPecTmpTC1p1ofemufqFBJo9vNbV7dkgN7vWwKnaSMkC4

Just waiting until audited to merge.

Just waiting until audited to merge.

good to merge?

audit ongoing and will be done soon. speculatively merging to keep the upstream PRs not in too much delay/pain.

bot merge


[clkmgr] Change software external clock control

Currently software external clock control is qualified with lc_dft_en.  This creates some complications during the secure manufacturing process and potentially makes it significantly more difficult to ship parts.
To resolve this, we need to change this to lc_hw_debug_en. Since clkmgr has already reached D2, we need to double check the impact on DV, although this change is required for production.

@matutem

@zi-v


File-type components and hashes

currently, SBOM "components" are detected based an a package.json file.
thats cool for most situatons.
but what if there is just no package.json? or it is untrusted for reasons?
Let's add file-based (sub-)components, that have a proper hash to them.
-> the feature is disabled by default, can be enabled by a new config option. name to be defined.
expected outcome:

components that represent "packages" have sub-components, one for each file that us used.

each of the file-based sub-components has a computed set of hashes on them.
each of the file-based sub-components name is the relative path of the file. relative to the root component.

if no package.json can be found (other than the projects own one), then the file used by webpack should be resulting in a SBOM component of type "file",

each of the file-based components has a computed set of hashes on them.
each of the file-based components name is the relative path of the file. relative to the root component.

May need an extra property taxonomy cdx:webpack according to https://github.com/CycloneDX/cyclonedx-property-taxonomy

as soon as this is implemented, publish example files here: https://github.com/CycloneDX/bom-examples/issues/38


test: 17 tests from others

Related Issue(s)
#546

Description
Contains 17 tests from others category, a minor change to expiration-for-policyexceptions, and installs Kyverno CLI in workflow for future jmesPath queries.

Checklist

[x] I have read the policy contribution guidelines.
[x] I have added test manifests and resources covering both positive and negative tests that prove this policy works as intended.
[x] I have added the artifacthub-pkg.yml file and have verified it is complete and correct.

TODO: limit-configmap-for-sa AH update, Policy Change if required.

Thank you for being diligent about resolving conversations as changes are pushed. This greatly helps with organization.


fixes for 0.2.1

[ ] May close #218

Codecov Report

Merging #219 (b3dedc9) into develop (5f3db15) will decrease coverage by 0.32%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           develop     #219      +/-   ##
===========================================
- Coverage    79.55%   79.23%   -0.32%
===========================================
  Files           51       51
  Lines         6475     6468       -7
===========================================
- Hits          5151     5125      -26
- Misses        1324     1343      +19

see 6 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


add def to pityriasis alba

address #7144

@nicolevasilevsky This could be merged, but please take a look at the question about the synonym. Maybe we can remove it in this PR? otherwise the PR can be merged.


Prevent comment command conflict on OS X as well

Addition to #115.
Let me know if I misunderstood something.

Crap, that conflicts with an OS X shortcut which opens the Help menu.


how do we manage traffic split resources over time

How do people manager TrafficSplit resources over time? Do you just update the same TrafficSplit resource forever? Is there some pattern people have come up with that we could document?

Shouldn't traffic split vanish after some time? that is - deleted?
For example, for Canary or A/B testing, after the evaluation period, it will be determined whether the new version is good to go, and then the older one will be deleted/undeployed and then there won't be any need in traffic split afterwards?

It isn't harmful to keep it around, or delete it. From a complexity perspective, I'm 👍 to @abonas. Fewer things to reason about.

Thanks! I see this is already mentioned in the Workflow section of TrafficSplit so I'll close this out. Cheers.


path: make path/filepath suggestion more visible

Forking from https://github.com/golang/go/issues/18581#issuecomment-294511925, it is not clear that path/filepath needs to be used for operating system path manipulation and path is only for slash-separated. Make it easier for users to see the path/filepath suggestion.

From #18581 it sounds like we don't want to add redundant text on each method, so I just sent CL 45653 to at least cross-link the path and path/filepath package docs to each other.


Avoid embedding CUDA_PATH to RPATH in wheels

Currently we are embedding CUDA_PATH (/usr/local/cuda), which is the CUDA installation path of the environment that builds wheel, to DT_RPATH of CuPy shared libraries.
(In addition, in Python 3.x, the same value is also appended to DT_RUNPATH).
This is inappropriate because /usr/local/cuda may point to the different version of CUDA in users’ environment.
As DT_RPATH cannot be overridden by users using Python 2, so we should avoid embedding it to wheels.
I added --cupy-no-rpath option to the installer.
This option is intended to be used by cupy-release-tools.

Please merge https://github.com/cupy/cupy-release-tools/pull/9 after this PR.

LGTM!


Make githooks run require the --name argument

Previously, not passing a hook name would result in trying to execute a hook named None:
githooks run
No hooks called None found. Add a [tool.githooks] section to your pyproject.toml with the desired hook

Now, this fails earlier with a more intuitive message:
 githooks run
Usage: githooks run [OPTIONS] [ARGS]...
Try 'githooks run --help' for help.

Error: Missing option '--name'.  Choose from:
	applypatch-msg,
	pre-applypatch,
	post-applypatch,
...

Nice! Thanks for your contribution

You're very welcome! Thanks for making this very useful project!


[Feature Request] [InputNumber] Add mouse wheel event support

Existing Component
Yes
Component Name
el-input-number
Description
Would be awesome to have the mouse wheel event supported for input.
On mouseover on input number, allow to use mouse wheel to increase or decrease input value.

Seems it can already be done: https://jsfiddle.net/3cdxv147/

Actually, this is browser default behavior. You don't have to do anything if you use el-input[type=number].
https://jsfiddle.net/xianshenglu/cgtm7kfn/4/
https://stackoverflow.com/questions/9712295/disable-scrolling-on-input-type-number/20838527
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/number
@Elfayer


[CI] build TEST_FILES for CI based on build manifest

Description
Within the CI, we know the location of the build manifest of
the OpenSearch Dashboards that got scaled up in prep for the
execution of these tests within this repo.
We can use that knowledge to determine the set of tests that
are valid against the distribution that this repo is being
executed on.
Signed-off-by: Kawika Avilla<EMAIL_ADDRESS>Alternative to:
https://github.com/opensearch-project/opensearch-dashboards-functional-test/issues/153
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Relevant portion from the CI when triggering a current 1.3.1:
found 6 vulnerabilities (3 moderate, 3 high)
  run `npm audit fix` to fix them, or `npm audit` for details
run security enabled tests
yarn run v1.22.17
$ env TZ=America/Los_Angeles NO_COLOR=1 cypress run --headless --env SECURITY_ENABLED=true,openSearchUrl=https://localhost:9200 --browser chromium --spec 'cypress/integration/core-opensearch-dashboards/opensearch-dashboards/*.js,cypress/integration/plugins/security/*'
It looks like this is your first time using Cypress: 5.6.0

Thanks @seraphjiang,
If @tianleh and @Tengda-He desire to reject this I will create the revert commit but for the sake of getting 1.3.1 test passing I will merge this.

The backport to 1.x failed:
The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.x 1.x
# Navigate to the new working tree
cd .worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-157-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 23bb48ba59f6d03fc8623a45c14c6c887a13d2d9
# Push it to GitHub
git push --set-upstream origin backport/backport-157-to-1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.x

Then, create a pull request where the base branch is 1.x and the compare/head branch is backport/backport-157-to-1.x.

For my curious, are these commands generated automatically? Looks very useful.

Yes they are. When the bot can't backport due to conflicts then it requires backporting manually but it outputs what it tried to do so I just copy line by line until after the cherry-pick where I have to fix the conflict then I can push.


display progress bar until history is loaded

Checklist

[x] Bug Report - The issue you are reporting might be there already. Please search on the issues tracker before creating or reporting a issue.
[x] Don't forget to tag your issue, it makes it easier to discover.
Summary:

use progress bars to notify user of loading history.
Expected behavior:

I am working on this.

Yeah, it would be good :).


Report for Default Dashboard: Google Analytics - 28 day active users over time

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1769
Originally created by @dmor on 2020-02-20 15:28:25

chart time: line graph
x-axis: time (by day)
y-axis: number of 28-day active users

https://analytics.google.com/analytics/web/?utm_source=marketingplatform.google.com&utm_medium=et&utm_campaign=marketingplatform.google.com%2Fabout%2Fanalytics%2F#/report/visitors-actives/a132758957w192645310p188384771/_u.date00=20190220&_u.date01=20200220&active_users.metricKeys='Reference to deleted milestone 5'B3%5D

View 9 previous comments from the original issue on GitLab


Updating dependencies

This PR is an effort to take torchmd-net dependencies to the latest possible versions.
Mainly taking torch to 2.0.
After pressing the conda-forge guys to update some of the dependencies to torch 2 the env file I updated installs on my machine and all test pass. Lets see how the CI likes it :P

:confetti_ball:

Working now. Updating torch-lightning requires changing stuff I do not understand ( #168 ), however the current version seems to play along with torch 2, so I say if it aint broke do not fix it.
This is ready to merge on my part. I will anyhow work on lightning and will PR again if I get around it.


Generify getting the channel ID so this can be used by other people

Getting the Channel ID is a required step in order to subscribe to the correct topic for channel points events. There is a manual step involved with that, in which the user has to log in and manually grant access to the application with the scopes requested.
Today, I went through the process of finding my own channel ID, and it's a multi-step process with a couple hoops to jump through. Need to smooth this out before I can open this out to other people to use.

This shouldn't be too terrible. The issue is going to be how we receive input, and how we manage scaling.


No-Op rebuild of GEOSgcm triggers rebuilds of GOCART2G

I think there is something slightly off with the CMake in GOCART2G, probably involving the automatic code generator.
First, build and install GEOSgcm. Now, doing nothing to the source code, go to your build directory and re-run make -jN install. When you do, you'll see what I think is the ACG re-running:
...
[  8%] Generating automatic code for CA2G_StateSpecs.rc
[  8%] Built target NCEP_bacio_r8i8
Consolidate compiler generated dependencies of target NCEP_bacio_r8i4
[  8%] Built target Process_Library
[  8%] Generating automatic code for NI2G_StateSpecs.rc
[  8%] Built target acg_phony_CA2G_GridComp
[  8%] Generating automatic code for SU2G_StateSpecs.rc
...

which I'm guessing generates code with a newer timestamp and so CMake has no choice but to re-compile:
...
[ 80%] Building Fortran object src/Components/@GEOSgcm_GridComp/GEOSagcm_GridComp/GEOSphysics_GridComp/<EMAIL_ADDRESS>[ 80%] Built target ec_prs2eta.x
[ 80%] Building Fortran object src/Components/@GEOSgcm_GridComp/GEOSagcm_GridComp/GEOSphysics_GridComp/<EMAIL_ADDRESS>[ 80%] Built target convert_eta.x
...

which then triggers a library re-link and a rebuild of all of GOCART2G's dependencies:
...
[100%] Linking Fortran static library ../../../../../../../../../../lib/libNI2G_GridComp.a
[100%] Built target NI2G_GridComp
[100%] Linking Fortran static library ../../../../../../../../../../lib/libCA2G_GridComp.a
[100%] Built target CA2G_GridComp
Scanning dependencies of target GOCART2G_GridComp
[100%] Building Fortran object src/Components/@GEOSgcm_GridComp/GEOSagcm_GridComp/GEOSphysics_GridComp/<EMAIL_ADDRESS>[100%] Linking Fortran static library ../../../../../../../../../lib/libGOCART2G_GridComp.a
[100%] Built target GOCART2G_GridComp
Scanning dependencies of target Aerosol_GridComp
[100%] Building Fortran object src/Components/<EMAIL_ADDRESS>[100%] Building Fortran object src/Components/@GEOSgcm_GridComp/GEOSagcm_GridComp/GEOSphysics_GridComp/<EMAIL_ADDRESS>[100%] Linking Fortran static library ../../../../../../../../../lib/libAerosol_GridComp.a
[100%] Built target Aerosol_GridComp
[100%] Linking Fortran static library ../../../../../../lib/libGEOSchem_GridComp.a
[100%] Built target GEOSchem_GridComp
[100%] Building Fortran object<EMAIL_ADDRESS>[100%] Linking Fortran static library ../../../../../lib/libGEOSphysics_GridComp.a
[100%] Built target GEOSphysics_GridComp
[100%] Building Fortran object<EMAIL_ADDRESS>...

Obviously, if no code has changed, CMake shouldn't need to rebuild.

I will leave that to the cmake gurus...


feat: Create total monthly amounts view

Description

Pull-request quality

[ ] The title adheres to this guide
[ ] Tests are written and executed locally
[ ] Subsystem tests have been tested (by manually deploying to dev_002)

outdated


Offline (using offline manifest)

Using service workers ?
https://developer.mozilla.org/fr/docs/Web/API/Service_Worker_API/Using_Service_Workers


DockerDriver: Add support for flavors without ephemeral

DockerDriver needs to support the new cPouta flavors that do not have ephemeral disk

The current code actually works, even if it thinks that the volume in /dev/vdb is an ephemeral disk. However, some cleaning up is needed to make this neater.

fixed by #475 and #477


Embedded Terminal

Proxy the input and output of a terminal via web sockets.
Ideally Ineed to find a library which handles this as it is complex and not a feature I care to maintain.
This should be added via an extension: #9

xterm.js is pretty decent in my experience
It's also what VS Code uses


Switch to the built-in Java HttpClient

Currently an API client generated using OkHttp is uses, which generates Kotlin code. Kotlin doesn't currently support Java 21. Additionally, when switching to virtual threads (#533), it will matter less what's async or not, so OkHttp won't be needed.

How will HTTP caching work? Perhaps this depends on the ESI Proxy project being completed. Specifically https://github.com/autonomouslogic/esi-proxy/issues/4 and https://github.com/autonomouslogic/esi-proxy/issues/8

Or move the generated client code into a submodule that's configured for Java 17.


[MM-45935]: remove post forwarding feature flag

Summary
removed feature flag getter and all props that this is passed into as
Ticket Link
MM-45935
Related Pull Requests

Has server changes here

Screenshots
n/a
Release Note
NONE

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/229665

/update-branch

@michelengelen I see the flag is shown in System Console>Experimental>Feature Flags PostForwarding | false  and at the same time post forwarding is enabled on the server. Can you please take a look - thanks 🙂

E2E report looks good, no PR related failures

@michelengelen I see the flag is shown in System Console>Experimental>Feature Flags PostForwarding | false and at the same time post forwarding is enabled on the server. Can you please take a look - thanks 🙂

Hi @jgilliam17 ... this is due to the fact that with this PR I removed all of the connections to the feature flag ... the server in this instance still has the feature flag set and it is also still present in code as long as https://github.com/mattermost/mattermost-server/pull/20714 is not merged

/update-branch

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/233719

Thanks @michelengelen
Tested, looks good to merge.
Verified post forward feature flag has been removed. Post forwarding is enabled and working as expected.
E2E report looks good, no PR related failures

/cherry-pick cloud

Cherry pick is scheduled.


Function Creation via REST API throws error

Tried to create a function for a already deployed web app as mentioned in https://docs.microsoft.com/en-us/rest/api/appservice/webapps/createfunction. The response was a 500 - internal server error.
The error message was:
"System.NullReferenceException: Object reference not set to an instance of an object.\r\n at Kudu.Core.Functions.FunctionManager.d__6.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Core\\Functions\\FunctionManager.cs:line 99\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Kudu.Services.Functions.FunctionController.d__7.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Services\\Functions\\FunctionController.cs:line 67\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Threading.Tasks.TaskHelpersExtensions.d__3`1.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.Controllers.ApiControllerActionInvoker.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown --- at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()--- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext()--- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()--- End of stack trace from previous location where exception was thrown --- at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()--- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext()--- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.d__2.MoveNext()--- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ExceptionFilterResult.d__0.MoveNext()"

Submitted this error here as it is seems like a problem in the FunctionController.cs

Can you provide a minimal (but complete) sample body that you are sending to this API when you see this? Thanks!

Also, do isolate, do you see the same if you try it on a brand new empty Function App?

@IshamMohamed that last error looks completely unrelated, like some general issue calling ARM API. Let's leave that part out.

@IshamMohamed will really need to payload sample to move forward as per my previous request.

The root of the issue is that you are sending an invalid payload which is missing the properties envelope (see [details](https://github.com/projectkudu/kudu/wiki/Functions-API
67d48c3bcee0fb1ef92c018985baf95fd4a77afb.
Bt more importantly, you should probably not be using this API. See https://github.com/Azure/Azure-Functions/wiki/Deploying-Function-Apps-vs-individual-Functions for more info.


[ Question ] Is it possible to stop the server if too many errors are found?

Problem
When opening CHANGELOG.md files harper-ls can cause everything else to halt(most likely caused by Neovim waiting for the response from the LSP).
Is it possible for the server to stop sending more responses if there are too many errors detected?

Or is it possible to only send part of the buffer text(current context can be retrieved from tree-sitter, as it should be much faster) to the LSP instead of sending the entire buffers text?

That's an excellent question. With current builds of Harper, this is not the case. I'd love a copy of the kinds of files you are opening, so I can get a better handle on the issue (and hopefully solve it!)

Any significantly  largeCHANGELOG.md file should be enough.
In my case, noice.nvim's CHANGELOG.md file would cause it to get slow.
But you could also test it with other popular plugin's CHANGELOG files too.

I looked into this and it seemed to be a pretty significant performance issue (some caches were getting busted WAY too often). I've made some changes that are in the v0.10.0 release. Once Mason has picked up the changed, would you give it spin?

Diagnostics not being removed even though they are disabled on insert mode.
It looks like performance has improved by quite a bit. However, it still not bullet-proof yet, as diagnostics seems to struggle a bit(but that could be a hardware limitation).
I would have preferred if it was possible to only send part of the buffer(specifically 200 lines around the cursor) to make LSPs faster but I guess that's not a solution.
Anyway, thanks for fixing the issue! I will close the issue.

On a side note, is it possible to add my own dictionary to the LSP?
For example, @param commonly used in luaCATS annotations is picked up by this LSP leading to a lot of "misspelling" being shown on the screen on large files.

On a side note, is it possible to add my own dictionary to the LSP?

There should be a code action on spelling errors to add to a personal dictionary. Let me know if that's not working for you.

For example, @param commonly used in luaCATS annotations is picked up by this LSP leading to a lot of "misspelling" being shown on the screen on large files.

This is a larger issue. Harper should ignore these by default. Would you mind opening a new issue with a couple examples of this?

There should be a code action on spelling errors to add to a personal dictionary. Let me know if that's not working for you.

I am quite new to programming so I wasn't aware of Code actions.
Yes, it works.

Would you mind opening a new issue with a couple examples of this?

I have opened a new issue about this.


Revamp method names

Name changes

ssv.and ~ssv.meet~
ssv.gum ~ssv.concat~
ssv.jam ~ssv.compact~
ssv.not ~ssv.diff~
ssv.or ~ssv.union~
ssv.say ~ssv.slate~
ssv.yolo ~ssv.uniq~

Reasoning

Breaking changes are ok now because next release will be major release
This library is unpopular

Strategy

Favor simple names because being simple is critical
Favor universal names for wider adoption
Favor roots for easier interpretation
Favor verbs for easier speaking
Favor vivid names for easier remembering

Gates

&& ! || != correlate to and not or xor
Gates are similar to programming keywords
Gates are more basic than set theory

jam

jam  is a fun simple vivid verb or noun
jam seems clearer than compact because compact is sometimes an array operation to remove falsey values but for us 0 becomes "0" and is therefore truthy

gum
I considered cat like the unix concatentate command but cat does hella. cat seems confusable with category. I'm allergic to cats. I next considered jams like plural form of jam but at least for now am avoiding plural names. I considered removing it entirely too but it seems simple and useful enuf to keep for now. I figure the name gum is sticky enuf to remember. It seems easy to grok being near jam in the alphabetized documentation.

say

I liked slate but it can read as s late and slate has some slang meanings
Alternatives considered include sup and text but say seems best combo of simple, descriptive, universal
3 and 5 letter names seem extra aesthetic with ssv being 3

yolo

uniq is common but hard to remember if uniq vs unique
yolo feels inspiring


cnspec: 11.17.0 -> 11.18.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mondoohq/cnspec/releases.
meta.description for cnspec is: Open source, cloud-native security and policy project
meta.homepage for cnspec is: https://github.com/mondoohq/cnspec
meta.changelog for cnspec is: https://github.com/mondoohq/cnspec/releases/tag/v11.18.0
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 11.18.0 with grep in /nix/store/d6613hjz5pizvxchlgiwwxlhghc5bcvd-cnspec-11.18.0
found 11.18.0 in filename of file in /nix/store/d6613hjz5pizvxchlgiwwxlhghc5bcvd-cnspec-11.18.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

cnspec

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/03fe93b79412c99abdfeebf701853113e4a9b6f4#cnspec

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d6613hjz5pizvxchlgiwwxlhghc5bcvd-cnspec-11.18.0
ls -la /nix/store/d6613hjz5pizvxchlgiwwxlhghc5bcvd-cnspec-11.18.0/bin

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

1 package built:

cnspec

Maintainer pings
cc @fabaff @mariuskimmina for testing.

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

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

Result of nixpkgs-review pr 336308 run on aarch64-darwin 1

1 package built:

cnspec


Create spdarea.txt

i added a different file before by mistake with a wrong name, please refere to this one for the domani of scuola politecnica di design - spdarea.it

@ferile8 I am sorry, I have to close this request without merging, because you requested to add a non-existent domain(s) to this repository:
~$ host spdarea.it
Host spdarea.it not found: 3(NXDOMAIN)
~$ host spdarea.edu
Host spdarea.edu not found: 3(NXDOMAIN)

Please ensure you are familiar with this repository rules located at the bottom of this page and submit a new request with correct information. Thank you for the understanding!

i'm sorry, the correct domain is spdarea.com
my mail is<EMAIL_ADDRESS>the website https://spdweb2016.scuoladesign.com/showPage.php?template=menu_valutazioni_studenti&id=2&masterPage=login-studenti.html

@ferile8 I am sorry, you still did not give me the information which I need to satisfy your request. We need:

the university official website URL, if different from the domain you are submitting, I assume that it is http://www.scuoladesign.com
an URL of a page on the official website where an IT-related long-term (>1 year) course is offered by the university
an URL of a page or another proof (.pdf or a screenshot are OK) showing that the university recognizes the domain which you are submitting as an official email domain for the students. In particular, the official website says that the school's email domain is @scuoladesign.com, and there shall be some document which proves that the students use @spdarea.com.

@ferile8 You might miss my previous comment. Please reply.

@ferile8 I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the abovementioned issue. Thank you for the understanding!


TypeScript definition file missing for responsive.js?

Hi, I'm using an Angular 2 starter project which is identical to the quickstarter app on Angular 2's website (https://angular.io/docs/ts/latest/quickstart.html) to test out ng2-responsive. I think it's pretty close to your demo app structure. After I follow your instructions to install and try to run the app when including some responsive directives, I get the following on "npm start". I got the same errors in your demo project even after I commented out the lines pertaining to responsive-directives-angular2 in systemjs.config.js.
Workaround for me at the moment is that to get the server running using "npm start" while ng2-responsive code is commented out. Once the server is running, if I comment the code back in, everything works fine.
I get almost identical errors if I remove the TS definition file for another ng2-responsive JS file, thus I think the following errors may be simply because of a missing TS definition file.
---------------------------------------Output of "npm start"-------------------------------------------
<EMAIL_ADDRESS>start C:\angular2\responsiveTest
tsc && concurrently "npm run tsc:w" "npm run lite"
node_modules/responsive-directives-angular2/index.d.ts(6,28): error TS2307: Cannot find module './responsive/responsive'.
node_modules/responsive-directives-angular2/index.d.ts(14,15): error TS2307: Cannot find module './responsive/responsive'.
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\tools\nodejs\node_modules\npm\bin\npm-cli.js" "start"
npm ERR! node v6.2.0
npm ERR! npm  v3.9.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: tsc && concurrently "npm run tsc:w" "npm run lite"
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'tsc && concurrently "npm run tsc:w" "npm run lite" '.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the angular2-quickstart package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     tsc && concurrently "npm run tsc:w" "npm run lite"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs angular2-quickstart
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls angular2-quickstart
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\angular2\responsiveTest\npm-debug.log

hum .... vamos a ver el error.

Similar issue I have when I run 'npm start' into 'demo' directory.

Bugs fixed, Thanks!! Any mistake, let me know. ; )


BIAS with Fly Track breaks?

I cannot replicate the error at this point, but have observed it 3 times in the past 2 days. Each of these 3 times, the two BIAS windows I was running on my machine disappeared.
The condition when this happened:

BIAS was running for > 20min
Fly Track was enabled and in "Track Fly" mode
The "fly" was moving near the edge of the tracking area

The "fly" is currently a piece of wire insulation taped to a transparent film.
This is just to keep track of the problem…

I'm guessing the BIAS windows disappearing can happen with a seg fault. Sounds like a corner case I didn't think of.

From: Frank Loesche @.>
Sent: Tuesday, August 20, 2024 9:50 AM
To: FlyVirtualReality/BIAS @.>
Cc: Subscribed @.***>
Subject: [FlyVirtualReality/BIAS] BIAS with Fly Track breaks? (Issue #2)
External Email: Use Caution
I cannot replicate the error at this point, but have observed it 3 times in the past 2 days. Each of these 3 times, the two BIAS windows I was running on my machine disappeared.
The condition when this happened:

BIAS was running for > 20min
Fly Track was enabled and in "Track Fly" mode
The "fly" was moving near the edge of the tracking area

The "fly" is currently a piece of wire insulation taped to a transparent film.
This is just to keep track of the problem…
—
Reply to this email directly, view it on GitHubhttps://github.com/FlyVirtualReality/BIAS/issues/2, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABTTNCXPLI5J4OPJQFG6XLZSNCSTAVCNFSM6AAAAABMZ6VVKOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ3TKNZRGE4TGNA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

This time I saw the error:

OpenCV: terminate handler is called! The last OpenCV error is:
OpenCV(4.10.0-dev) Error: Assertion failed (axes.width >= 0 && axes.height >= 0 && thickness <= MAX_THICKNESS && 0 <= shift && shift <= XY_SHIFT) in cv::ellipse, file C:\Users\labadmin\Documents\FlyVR\opencv\modules\imgproc\src\drawing.cpp, line 1955

I think this came from lambda2 (2nd eigenvalue) being either -0.0 or even a large negative number (buffer overflow?). This caused the sqrt being nan, which is not >=0 for axes.height.

Today, the value of<PHONE_NUMBER>637375100788921474948653063872130805290232570150243779024747834499840167795073442172120003040386203254784.00 in flyEllipse_.b broke cv::ellipse. One idea to work around in dbf82691b4729f09bc9dcffdd2913d28c7eea298.


Capture with video texture

I have a complex scene that is successfully rendering out at just under 2 frames per second using Ccapture. All the objects in the scene are textured with video which is playing back behind the scenes at its normal speed (25FPS). The result is the scene plays back super well but the video texture plays back at several times the correct speed.
I've tried setting the video currentTime to synchronise it with time delta like so.
var video = document.getElementById("source");
video.currentTime += dt;

Strangely that, and just console.log(video.currentTime);, both pause the video texture completely (but not the actual video in the page). console.log(video.played); does not.
This is using Chrome Version 51.0.2704.103 (64-bit).
Any thoughts on a work around? And thank you very much for the beautiful library!

I've made a fiddle that demonstrates the error.
https://jsfiddle.net/queenvictoria/j32d7o1y/
If you uncomment line 44 and 50 (the ones marked Uncomment...) then the video pauses -- both the texture and the HTML5 player. Uncommenting either one is fine. Both together -- no good.

Yes, the problem is that I'm assuming that the effects are usually timed with an audio or video track, so those elements are modified to drive the time, not to follow it. I can make a modification so you can tell the capturer "i'm not using video|audio for syncing, so make video|audio elements follow"

Do you think that would fix it?
I've taken another approach which I can't tell fixes it (somethings gone strange with the webm output) but might (unless Ccapture is too clever and undoes my fix).
Instead of setting the position of the video I've set the frame rate and adjust it if the FPS of the canvas changes. Something like this.
var fps = 1000/dt;
document.getElementById('video').playbackRate = fps/25;


Not able to run all the bottlenecks together for any given model

The above image shows an error of "can't start a new thread" when I am trying to run all the bottlenecks together for inception5h. i.e,
bottlenecks = [ 'mixed3a','mixed3b','mixed4a','mixed4b','mixed4c','mixed4d','mixed4e','mixed5a','mixed5b']
At max, I can run only two bottlenecks at a time. For three and above no. of bottlenecks, I am facing this issue.
Please let me know if there is any way to proceed further to avoid this error. Looking forward to suggestions.

This most likely is happening because your system cannot create more threads to run the TCAV processing in parallel.  Does it work if you set run_parallel to False? How many concepts are you trying out in your TCAV.run call as well? Would be helpful to see the full stack trace.
Mitigations could include running on a machine with more cores, or not in parallel, or changing the TCAV code to have a smaller number of workers used in the multithreading.pool calls.

Yes I get these errors when I don't have enough computation resources. Please try with run_parallel False and reopen this issue if you still experience the same error!


doc(Binding): fromView, capture

@EisenbergEffect @jdanyow Still not confident with what I put in 😅 . Please review

looks good to me :+1:


gx_studio_auto_event_handler calls event function on a deleted widget

I am using the Screen Flow in GUIX Studio.
I have configured 2 Actions for a Runtime Allocated widget when a button is pressed.

Detach itself
Attach another widget

This seems to work most times fine but sometimes not!
To me it looks like there is a problem in the auto generated gx_studio_auto_event_handler function.
In this function all the GUIX Studio Actions are handled in a switch case .
I debugged into the case GX_ACTION_TYPE_DETACH and I can see that the widget is detached gx_widget_detach(target) and also deleted gx_widget_delete(target).
Now the problem I think is that still the event function of that widget is called at the end status = record->chain_event_handler(widget, event_ptr);
The widget might contain random data at that point. Most times it works fine because of the checks in the "_gxe..." functions, but sometimes there is random valid data in that widget and then i get a null pointer exception.

@Serpet-coder Try to add the following code to the relevant gxe function to check invalid widget and see if this change solve the problem.
if (button-> gx_widget_type == 0)
{
return(GX_INVALID_WIDGET);
}

All the gxe functions have that check already.
Here is a code snippet which seems to fix the problem. I made some changes to the auto-generated function gx_studio_auto_event_handler(). (But since it's auto-generated it will be overwritten next time i generate)
My changes basically delay detach/delete operations on the widget itself until the end of the function (after all actions are handled). I think the problematic cases are GX_ACTION_TYPE_DETACH and GX_ACTION_TYPE_TOGGLE where we delete the widget itself.
The event processing function of a detached/deleted widget won't be called anymore with this change.
UINT gx_studio_auto_event_handler(GX_WIDGET *widget, GX_EVENT *event_ptr, GX_CONST GX_STUDIO_EVENT_PROCESS *record)
{
    UINT status = GX_SUCCESS;
    GX_CONST GX_STUDIO_ACTION *action;
    GX_CONST GX_WIDGET *parent = GX_NULL;
    GX_WIDGET *target = GX_NULL;
    GX_CONST GX_STUDIO_EVENT_ENTRY *entry = record->event_table;

    GX_BOOL detach_self = GX_FALSE;              // remember to detach ourself
    GX_BOOL delete_self = GX_FALSE;              // remember to delete ourself
    GX_WIDGET *toggle_target = GX_NULL;          // remember the toggle target

    while(entry->event_type)
    {
        if (entry->event_type == event_ptr->gx_event_type)
        {
            if((entry->event_type == GX_EVENT_ANIMATION_COMPLETE) &&
               (entry->event_sender != event_ptr->gx_event_sender))
            {
                entry++;
                continue;
            }
            action = entry->action_list;

            while(action->opcode)
            {
                switch(action->opcode)
                {

               ...

                case GX_ACTION_TYPE_DETACH:
                    target = gx_studio_action_target_find(widget, action);
                    if (target)
                    {
                        if(widget == target)
                        {
                            detach_self = GX_TRUE; // we might need our parent for another action, so don't detach yet
                        }
                        else
                        {
                            gx_widget_detach(target);
                        }

                        if (target->gx_widget_status & GX_STATUS_STUDIO_CREATED)
                        {
                            if(widget == target)
                            {
                                delete_self = GX_TRUE; // we might need widget data for another action, so don't delete yet
                            }
                            else
                            {
                                gx_widget_delete(target);
                            }
                        }
                    }
                    break;

                case GX_ACTION_TYPE_TOGGLE:
                    if(action->flags & GX_ACTION_FLAG_POP_TARGET)
                    {
                       gx_system_screen_stack_get(GX_NULL, &target);
                    }
                    else
                    {
                        target = gx_studio_action_target_get(widget, action);
                    }
                    // gx_studio_screen_toggle(widget, target);
                    toggle_target = target; // we might need widget data for another action, so don't toggle yet
                    break;

                ...

                default:
                    break;
                }
                action++;
            }
        }
        entry++;
    }

    if(toggle_target)
    {// all actions are handled now we can toggle
        gx_studio_screen_toggle(widget, toggle_target);
    }
    else if(detach_self)
    {// all actions are handled now we can detach and delete
        gx_widget_detach(widget);
        if(delete_self)
        {
            gx_widget_delete(widget);
        }
    }
    else if (record->chain_event_handler)
    {
        status = record->chain_event_handler(widget, event_ptr);
    }
    return status;
}

@Serpet-coder The first parameter widget is normally a top level screen. The detached widget might be a child of the widget. So, in some case, this might not work, as we the chained event handler not been called once there is a child widget being detached. I have checked that some gxe functions do not have the widget type check, for example, gxe_button_event_processing is missing this checking. If a widget has been deleted, the widget type is set to 0, if the gxe event processing function does the widget type checking, it will return directly.

Isn't problem here that if you have a GX_STATUS_DYNAMICALLY_ALLOCATED widget. When it is deleted the widget is freed. Your check would then dereference an invalid adress somewhere on the heap.

@Serpet-coder Thanks for your feedback! I'll investigate the issue and keep you informed of any progress.

@Serpet-coder A new version of GUIX Studio <IP_ADDRESS> has been released to the Microsoft App Store that addresses the mentioned issue. Please let me know if the fix has solved your problem.

@Serpet-coder Thank you for your advice! We'll continue refining the fix and keep you informed.

@Serpet-coder A new version of GUIX Studio <IP_ADDRESS> has been released to the Microsoft App Store that addresses the additional issues you mentioned. If you encounter any further issues, please feel free to reopen it.


PostgreSQL migration error

I am using postgres, in the migration I got this error:
 [Illuminate\Database\QueryException]
  SQLSTATE[42601]: Syntax error: 7 ERROR:  zero-length delimited identifier at or near """"
  LINE 1: alter table "" add column "current_team_id" integer null
                      ^ (SQL: alter table "" add column "current_team_id" integer null)

Any advice?

Which version of teamwork do you use?
Can you take a look at the migration file? It should use the users table:
Schema::table( 'users', function ( Blueprint $table ) {
        $table->integer( 'current_team_id' )->unsigned()->nullable();
} );

Sorry, it turns out that Config::get( 'auth.table' ) results into blank value, as 'auth.table'  is not defined in Config, I had to add \Config::set( 'auth.table', "users" ); to run the migrations..
By the way, where would I define 'auth.table' ?

Looks like your migration is from an older version of this package, which was not optimized for laravel 5.2 - there's still an open PR that I need to look at.
In the meantime you can just set it to your users table name. Probably just users :)

Ok, thank you :+1:


Unable to Set S3 Bucket URL for Team Workspace

Background
We use AWS IAM to grant Kubernetes pods access to an S3 bucket for our services via  adding annotation iam.amazonaws.com/role in Deployment yaml. The bucket is accessible only by the Livebook team's service account, which means that access is restricted to pods within the Kubernetes cluster. As a result, I am unable to access the S3 bucket from a local Livebook instance, and I can only set the bucket URL for my personal workspace using the Livebook team's instance.
However, I am facing an issue when trying to set the bucket_url for my team's workspace from the Livebook team's pod. I encounter the following error message:
You are not authorized to perform this action, make sure you have the access and you are not in a Livebook App Server/Offline instance

Proposed Solution
To resolve this issue, I propose adding a new environment variable that allows us to set the bucket_url when LIVEBOOK_AWS_CREDENTIALS is set to true. This would help in configuring access appropriately when running in environments with restricted access, such as within a Kubernetes pod.
BTW, there is A TYPO in above snapshot. https://github.com/livebook-dev/livebook/pull/2824

Hey @zhihuizhang17! Just to make sure we are on the same page. When developing locally you use a Teams workspace and have an S3 file system that is accessible for you locally. Then, on the pod instance running Livebook app server, you want to use a different URL for that file system, which is only accessible from the pod. I assume your use case is using notebook files from the S3 file system, so the expectation is that both S3 buckets have file at the same path. Is this correct?

Hey @jonatanklosko! Thanks for your reply. I think there might be a misunderstanding. Let me clarify our use case:

I'm not trying to use different S3 buckets for local and pod environments. There is only one S3 bucket that I want to access.

The current situation:

This S3 bucket is only accessible from within the Kubernetes cluster via IAM role (through the iam.amazonaws.com/role annotation in our Deployment)
I cannot access this bucket locally because I don't have direct AWS credentials
I can only access this bucket through pods in the Kubernetes cluster

The specific issue I'm facing:

I can successfully set the bucket_url for my personal workspace using the Livebook instance running in the pod
However, when I try to set the bucket_url for my team's workspace from the same pod, I get the error:You are not authorized to perform this action, make sure you have the access and you are not in a Livebook App Server/Offline instance

This happens despite the pod having the correct IAM role and being able to access the S3 bucket

My proposed solution:

Add a new environment variable that would allow setting the bucket_url when LIVEBOOK_AWS_CREDENTIALS is true
This would help in scenarios where the Livebook instance has indirect access to S3 (like through IAM roles) rather than direct AWS credentials

@zhihuizhang17 you are getting that error because the Livebook instance you are using is an "agent" instance. It is only meant to run deployed notebooks and therefore it is read only (in fact, we should not be allowing you set the file system for the personal workspace).
You should deploy a regular Livebook instance, listed here, and then they should all work. We should probably make this clearer.

You should deploy a regular Livebook instance.

@josevalim Sorry, I'm a bit confused now. I followed the guide you mentioned to deploy my Livebook team service. The only change I made was to change type: LoadBalancer to type: ClusterIP since there is no load balancer in my Kubernetes mesh. I believe I have already set it up correctly. How can I determine whether it's an agent instance or a regular Livebook instance?

@zhihuizhang17 when you deployed it, did you have to manually add your Livebook Teams workspace to that instance or it was already there? Have you set LIVEBOOK_TEAMS_AUTH or LIVEBOOK_TEAMS_KEY env vars?

when you deployed it, did you have to manually add your Livebook Teams workspace to that instance or it was already there?

Yes, it was already there.

Have you set LIVEBOOK_TEAMS_AUTH or LIVEBOOK_TEAMS_KEY env vars?

Yes. I set them in deployment.yaml as follow
            - name: LIVEBOOK_COOKIE
              valueFrom:
                secretKeyRef:
                  name: livebook-secret
                  key: LIVEBOOK_COOKIE
            - name: LIVEBOOK_SECRET_KEY_BASE
              valueFrom:
                secretKeyRef:
                  name: livebook-secret
                  key: LIVEBOOK_SECRET_KEY_BASE
            - name: LIVEBOOK_TEAMS_AUTH
              valueFrom:
                secretKeyRef:
                  name: livebook-secret
                  key: LIVEBOOK_TEAMS_AUTH
            - name: LIVEBOOK_TEAMS_KEY
              valueFrom:
                secretKeyRef:
                  name: livebook-secret
                  key: LIVEBOOK_TEAMS_KEY

Yes, that's precisely the issue. Once you set those two env vars, it becomes an "agent". You should remove them and then you will be able to add your org as usual, as you did on your local machine, with full access. I will improve the docs.

@josevalim It works!!! However, there are still some unusual behaviors:

After I removed LIVEBOOK_TEAMS_KEY and LIVEBOOK_TEAMS_AUTH, the warning 'You are running a Livebook app server. This workspace is in read-only mode.' disappeared, and I was able to set the bucket_url. However, when I refreshed the UI after I set it, the warning returned. Additionally, I am unable to detach the S3 bucket URL from the cluster instance—I have to detach it from my local Livebook instance. This means that I can only set the S3 bucket via the cluster instance but can only remove it via the local instance.

After executing kubectl rollout restart deployment/livebook to redeploy the pods, the Web UI becomes unstable when refreshing the page. The team workspace sometimes disappears and then reappears intermittently.

Update
As of now, the best practice for me seems to be:

Deploy instances without setting LIVEBOOK_TEAMS_KEY and LIVEBOOK_TEAMS_AUTH.

Set the S3 bucket URL for the team workspace from a Kubernetes instance, which allows the Livebook-dev console to store the configuration and sync it across all instances.

Redeploy instances with LIVEBOOK_TEAMS_KEY and LIVEBOOK_TEAMS_AUTH set.

This ensures that the team workspace is always present when I refresh the UI after the next deployment.

After executing kubectl rollout restart deployment/livebook to redeploy the pods, the Web UI becomes unstable when refreshing the page. The team workspace sometimes disappears and then reappears after next refresh. Local apps I deployed disappear too. My version is v0.14.4.

This is happening because you have multiple instances and the workspace connection is per instance. We currently don't sync them across the cluster.
Thank you for the feedback, we will discuss internally how to improve the workflow. Meanwhile, I will update the docs to mention it should be a single instance.

Closing this in favor of #2827.


Implement add deployment slot

Fixes #156
I changed the implementation of AppServiceNodes.  There are some features that are exclusive to different plan tiers, so I thought it would be useful to check the AppServicePlan when populating children.  For example, Basic tier does not allow for DeploymentSlots.

Are the gray icons okay?  They are just some assets I made by altering the hex color of the .svg files.  Any opinions on it?


Why is sendgrid.net “greylisted”?

https://sendgrid.com/docs/Classroom/Deliver/Undeliverable_Email/why_is_sendgrid_net_greylisted.html

Hi Sendgrid Support,
For your kind assistance and checking.  We are having problem with the emails from sendgrid domain, Based on our Email gateway, sender email address from sendgrit starts with "bounces...". Also sendgrid.net domain was monitored blacklisted in our Public Utility tool (MX Toolbox).
With this, kindly check and request for removal of your domain to their blacklisted.

Hello @rhodamae,
Thanks for submitting a GitHub issue! We are very sorry that you are running into this problem. In order to better serve you, as this does not present itself as a library specific issue, we would like to ask that you reach out to our support team at https://support.sendgrid.com.
Thank you!
SendGrid DX Team


Publish Sanity schema

Depends on
Other tickets:

N/A

Third parties:

N/A

Description
I'm interested in forking the editor and enhancing the toolkit with some custom functions/code. Upon reviewing your repository, I couldn't locate the underlying Sanity CMS schema used to request content for the toolkit, ideas, and API. Would it be possible for you to share the schema model?

Hi @felixerdy. Sorry for the delayed response.
The schema is currently part of a larger schema but we'll look at how best to extract the relevant part. It looks like we might be able to extract it as a sanity plugin which we could then open source. We’ll take a look and get back to you soon.
The schema covers the content model for the Reference and Ideas tab content as well as a mapping from Reference content to API entries. The Reference and Ideas content itself is not open source.
The API content is managed differently: it's generated at runtime from the Python type stubs that we provide to our fork of Pyright. These stubs are available in this repo. There's a script there to generate the typeshed.{lang}.json file that we use to initialize Pyright.
We're also considering spending some time on an alternative way to source Reference and Ideas tab content. For example, a version based on markdown in the git repository. Is that something that would be useful to you? We'd be unlikely to switch to such an approach ourselves (there are benefits to using Sanity for collaboration with our education team) so it would be a more open-source-friendly alternative.

Thank you for your answer @microbit-matt-hillsdon! Publishing the schema as a sanity plugin would be great of course, but the markdown approach would also be a great alternative. If I find some time I'll try to work on a first draft with markdown files (or something similar) that we could discuss on

@felixerdy we've created an initial cut of a Sanity plugin with Python Editor schemas here: https://github.com/microbit-foundation/sanity-plugin-python-editor-v3/
We hope the README will be enough to add it to a blank Sanity studio given some experience with Sanity itself. Feedback very welcome.
We made some supporting changes in the Python Editor:

https://github.com/microbit-foundation/python-editor-v3/pull/1157
https://github.com/microbit-foundation/python-editor-v3/pull/1158

It's also worth noting that we recently updated the tooling from Create React App to Vite/Vitest as one of these changes use Vite-flavoured environment variable configuration (this change on main and live on our beta deployment but not yet released).
I'll spend some time later in the week planning out what a markdown alternative could look like. I'll create a new issue and tag you there. There are some features of the current documentation (particularly the dropdowns with alternative content) that don't have an obvious mapping to markdown so I'll try to capture those. Once done I'd be interested in your input on what features are important to you for your content. We've also considered using markdown documentation for extension module documentation so it would be good to consider that usecase.

Markdown tracked by #1160.

Added some docs on #1159. Calling this done but please feel free to add feedback here or open a new issue for any problems.


Comments are not terminated by newline

Example:
--
-- Table structure for table 'tx_digibordauthentication_activity_log'
--
CREATE TABLE tx_digibordauthentication_activity_log
(
  uid         int(11) unsigned    NOT NULL auto_increment,
);

Adding a space to the -- above CREATE does not help.
Adding any letter does help, however:
--
-- Table structure for table 'tx_digibordauthentication_activity_log'
-- X
CREATE TABLE tx_digibordauthentication_activity_log
(
  uid         int(11) unsigned    NOT NULL auto_increment,
);

Could the problem be this regex being eager-matching / greedily-matching?
https://github.com/DerekStride/tree-sitter-sql/blob/main/grammar.js#L331
Could a lazy /.*?\n/ do the trick?

Could a lazy /.*?\n/ do the trick?

Yeah I think that would do it, want to open a PR for it?

I tried locally and couldn't make it work. Am I doing something wrong?
Here's what I do, using helix:

In $HELIX_RUNTIME/grammars run rm sql.so
In $HELIX_RUNTIME/grammars/sources/sql edit grammar.js
Run hx --grammar build
Open a fresh hx instance to check if it changed something.

It confirms rebuilding sql - but my changes to grammar.js appear to have no effect at all. (Even if I change "--" for something bogus, comments in the SQL file are still highlighted as comments.)
Could you try verifying the fix?

I have tested it on my machine and the suggested regex does not fix the issue:
    comment: _ => seq('--', /.*?\n/),
with following SQL:
--
CREATE TABLE tx_digibordauthentication_activity_log
(
  uid int(11) unsigned NOT NULL auto_increment,
);

produces this AST:
(program [0, 0] - [5, 0]
  (comment [0, 0] - [2, 0])
  (ERROR [2, 0] - [4, 2]
    (keyword_not [3, 23] - [3, 26])
    (keyword_null [3, 27] - [3, 31])
    (keyword_auto_increment [3, 32] - [3, 46])))
playground.sql	0 ms	(ERROR [2, 0] - [4, 2])

Tree-sitter regexes are single-line by default so I think the explicit newline is actually throwing it off. Other grammars like JS, Python or Bash use .* sans newline for single-line comments; the Java grammar has what seems like an unnecessary negative (anything but a newline) character class.
I've created https://github.com/DerekStride/tree-sitter-sql/pull/74 , please check it out!

Fixed https://github.com/DerekStride/tree-sitter-sql/pull/74


Enhancement of JOBS check

Is your feature request related to a problem?

I wanted to use the library to check whether I have any pending commits on the firewall (commit result == PEND).
Describe the solution you'd like

I wanted to enhance check_non_finished_jobs method so I can parametrise it and specify what type, status and result of a job I want to check.
Describe alternatives you've considered

Adding a new module to pan-os-ansible.

We figured out that original check_non_finished_jobs method actually does the job (we don't have to check the result for PEND value because that equals to status other than FIN).


Inviting participant to participate in the challenge by Host

Feature Introduced through this PR:

Host can now send an invitation to the participant for participating in his/her hosted challenge.

Work Done in this PR:

[x] Added Invite participant field in the challenge setting Tab

[x] Host can now send an invitation to the participant using their Email Id

work left to be done:

[ ] Add the feature to let the participant accept the invitation using accept_challenge_invitation Api

[ ] Add the required tests

Note: This is a WIP Pr

Codecov Report

Merging #311 into master will decrease coverage by 0.26%.
The diff coverage is 25.92%.

@@            Coverage Diff             @@
##           master     #311      +/-   ##
==========================================
- Coverage   50.62%   50.35%   -0.27%
==========================================
  Files          66       66
  Lines        3771     3815      +44
  Branches      444      451       +7
==========================================
+ Hits         1909     1921      +12
- Misses       1767     1799      +32
  Partials       95       95

Impacted Files
Coverage Δ

...e/challengesettings/challengesettings.component.ts
36.53% <25.00%> (-8.63%)
:arrow_down:

src/app/services/endpoints.service.ts
64.58% <50.00%> (-0.32%)
:arrow_down:

...bliclists/challengelist/challengelist.component.ts
47.57% <0.00%> (+0.97%)
:arrow_up:

Impacted Files
Coverage Δ

...e/challengesettings/challengesettings.component.ts
36.53% <25.00%> (-8.63%)
:arrow_down:

src/app/services/endpoints.service.ts
64.58% <50.00%> (-0.32%)
:arrow_down:

...bliclists/challengelist/challengelist.component.ts
47.57% <0.00%> (+0.97%)
:arrow_up:

Continue to review full report at Codecov.

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

@Shekharrajak  I am using invite_users_to_challenge API but i am getting Error 400 i.e Bad request error after i tried to hit the API. Though the API is being hit, it's not able to find the challenge with the challenge id i provided as mentioned here.

I think this is still an WIP PR, @Kajol-Kumari Please let us know when it is ready to review.


Cannot declare and define an integer array using the colon operator

Summary:
It is a parser error to declare and define a one-dimensional integer array using the colon operator.
Description:
It is a parser error to declare and define a one-dimensional integer array using the colon operator.
Reproducible Steps:
Try to parse the following Stan program
data {
  int<lower=1> K;
}
transformed data {
  int arr[K] = 1:K;
}

Current Output:
SYNTAX ERROR, MESSAGE(S) FROM PARSER:

variable definition dimensions mismatch, definition specifies 1, declaration specifies 0  error in 'model_int_array' at line 5, column 17
  -------------------------------------------------
     3: }
     4: transformed data {
     5:   int arr[K] = 1:K;
                        ^
     6: }
  -------------------------------------------------

Error in stanc(model_code = paste(program, collapse = "\n"), model_name = model_cppname,  :
  failed to parse Stan model 'int_array' due to the above error.

Expected Output:
Nothing. It should assign the integers from 1 to K to arr
Additional Information:
Current Version:
v2.17.0

This sounds like it'd be reasonable to add.  It shouldn't be too hard.  : will have to be defined as an infix operator.
What should its precedence be? It would make sense to me to allow 1+2:3 + 9 with interpretation (1 + 2):(3 + 9)?    R goes the other way (for all arithmetic), making : bind more tightly:
> 1+2:3+4
[1] 7 8

Associativity doesn't matter since it's output isn't the same type as its input.

I guess it should be whatever it is for x[1 + 2:3 + 9].
On Sat, Oct 21, 2017 at 7:13 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

This sounds like it'd be reasonable to add. It shouldn't be too hard. :
will have to be defined as an infix operator.
What should its precedence be? It would make sense to me to allow 1+2:3 +
9 with interpretation (1 + 2):(3 + 9)? R goes the other way (for all
arithmetic), making : bind more tightly:

1+2:3+4
[1] 7 8

Associativity doesn't matter since it's output isn't the same type as its
input.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/stan/issues/2424#issuecomment-338438835, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADOrql7_AYgLU3LB7Przg6z2en1Ar9F-ks5sunqYgaJpZM4QBvjF
.

Excellent point.  Current Stan treats : as binding more loosely than arithmetic.  So we get 1+2:3+9 with the same denotation as `3:12 in both of the existing contexts:
  for (i in 1 + 2 : 3 + 9) ...

and
x[1+ 2 : 3 + 9]

This is difficult to add to Stan currently as it would lead to ambiguity. For example, is the following a valid Stan program if we add this behaviour
model {
  int n = 5
  for (i in 1:n) {
    n += 1;
  }
}

?
Observe that the for could then either be interpreted as a for-loop over the range 1:n or a foreach-loop over the array 1:n. Both have slightly different operational semantics. Because our for-loops are like C for-loops, the upper bound gets reevaluated after each pass through the loop body. In particular, for-loops might not terminate. For foreach-loops, the array gets evaluated once before we enter the loop and then becomes immutable.

This program is currently valid and will evaluate the loop body for i in { 1, 3, 5 }.
With "1:n" this would be ambiguous between a foreach loop where "1:n" denotes an int[] and a regular loop where "1:n" are just the loop bounds.
This is a behavior we could change in Stan 3.  I believe Matthijs has suggested making the loop bounds immutable in the body, so it's effectively the foreach interpretation.
his could get tricky syntactically if the bound is a function, say
for (i in 1:f(x,y,z))
We presumably wouldn't want any of x, y, z being mutated in the loop body.  This would settle on the foreach s

On Dec 13, 2018, at 8:03 AM, Matthijs Vákár<EMAIL_ADDRESS>wrote:
This is difficult to add to Stan currently as it would lead to ambiguity. For example, is the following a valid Stan program if we add this behaviour
model {
int n = 5
for (i in 1:n) {
n += 1;
}
}
?
Observe that the for could then either be interpreted as a for-loop over the range 1:n or a foreach-loop over the array 1:n. Both have slightly different operational semantics. Because our for-loops are like C for-loops, the upper bound gets reevaluated after each pass through the loop body. In particular, for-loops might not terminate. For foreach-loops, the array gets evaluated once before we enter the loop and then becomes immutable.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


when i useing  thead Grouping. only set  subHeader enableColumnFilter work, parent Column didn't work

TanStack Table version
v8.16.0
Framework/Library version
v18.2.0
Describe the bug and the steps to reproduce it

go to the grouping example (https://tanstack.com/table/latest/docs/framework/react/examples/grouping)
set {enableColumnFilter: true} for parentColumn and subParent
wirte the debug code for  or console.log(header.column.getCanFilter())
that result was false

Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
https://codesandbox.io/p/sandbox/modest-lederberg-lzppdp
Screenshots or Videos (Optional)

Do you intend to try to help solve this bug with your own PR?
None
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

how can i resolve this problem. Is it fixed in latest version?

@KevinVandy please have a look, it confused me, help!

You can only filter from a leaf column

You can only filter from a leaf column

Is it a column doesn't have subColumn call Leaf Column.

i didn't define any sub columns, but it not work either

TanStack Table itself doesn't let you sort, filter, group by, etc. from the header groups (parent group columns) because what values would it be performing those actions on? You can ignore the default logic from TanStack Table and shove in your own UI anyway though.


Temp robocup docker image

plz help

The problem is this:

On the Arch Linux website, python-distlib version 0.3.4-1 was signed by Antonio Rojas on the 2022-01-04.
Our docker file is date locked to 2021-08-29, so the version of python-distlib in the docker image is always going to be 0.3.2-1. This was signed by Eli Schwartz.
The install-package command updates the keychain to trust the same signers as what Arch Linux uses. Unfortunately, Eli Schwartz’s certificate is no longer trusted because his certificate expired.

So we have to install packages by explicitly trusting Eli Schwartz’s certificate, or update the dependency.
@TrentHouliston, you bet met to it. 😜


Readme

It would be nice to have a more detailed readme that state what Starlog do, and maybe a screenshot.
I'm saying this because even if I follow IPFS development, I have no idea what Starlog is.

Agreed. I tried on both the new feature branch for the front end in #8, and on master, and got nothing both times. I suspect you need to have IPFS running first. I'm looking into that now.
@lgierth had the same issue.

@MichaelMure Did you run bower install and npm install first?

@MichaelMure Readme is now here! What do you think? Anything you would like to be clearer?

The readme is nice, closing this.


More flexible homepage spec

Summary
I want to combime a folder path and moment syntax to specify the homepage
Details
I use the daily notes core plugin.  There you can specify the folder for daily notes and the note name.  It turns out you can use:
YYYY/MM-MMMM/YYYY-MM-DD
as the note name.  This will let it make a directory under the folder for each year, each month and a new page.  So if I have a base folder of /stuff/Inbox/DailyNotes I get a hierarchy that looks like:
stuff/

Inbox/

DailyNotes/

2022
2023

01-January
02-February

2023-02-01
2023-02-02
......
can you use the same kind of logic for specifying the note to open.

This should work fine with the current version of the plugin. Let me know if you have any issues doing this.


Feature render block health bar

@nsg Added basic health bar rendering looking like this:

This is based on #188

Or as in this video

@petterarvidsson nice!
Just a thought, I feel like that I naturally expects the "almost broken block" to be no more than maybe 50% or so. Feels like we need a little stronger effect. What do you think?

Quick and dirty edit:

... and with a damage_weight set to 0.6. I like it better.

@nsg Like it! Please commit.
I was also thinking that we do ahve the option of having a much higher resolution for the damage texture. That could look cool as well, with gradients so that the cracks also deepens.

@petterarvidsson commited
Sounds interesting!

@nsg thinking more like

I see, do you not think it would conflict a little with the block-y art style?

@nsg Like your new texture and setting!

Not sure, since it is an effect on the block-y art it could look cool :smile:

basically I am only thinking lines growing from the center, but also becoming deeper the more damage the block gets (not only longer)

@nsg Anyway, let's try that in another branch, I'd say this one is ready for merging?

@petterarvidsson sure


Add SolvationToolkit recipe

SolvationToolkit allows easy setup of simulation inputs for arbitrary mixtures of small organic compounds. This adds a recipe for it.
This is my first crack at adding a new recipe for one of my own packages, so likely I'll have some issues at first. I've modified recipes before, though, so hopefully that means I haven't botched this too badly.

Ahh, right. Currently my tests require OpenEye tools to run, which is fine as long as I'm running them on MY Travis-CI, but won't work on here. Hence this is failing on Travis.
I knew there had to be some good reason to have the tests skip if OpenEye tools aren't available...
I'll fix this soon and try again.

I knew there had to be some good reason to have the tests skip if OpenEye tools aren't available...

Yep.
We've generally been excluding all tests (except a simple import packagename) from the official conda recipes included here, since otherwise builds+tests take forever.

@jchodera : This is failing because of something relating to a docker image of an omnia build box:
 $ if [[ "$TRAVIS_OS_NAME" == "linux" ]]; then docker pull jchodera/omnia-build-box; fi
Using default tag: latest
latest: Pulling from jchodera/omnia-build-box
nia-build-box
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
The build has been terminated

Ideas?

This is a stochastic failure due to high network traffic

@rmcgibbo - do you have any advice on this? It seems to be timing out during the testing and I don't really have enough experience with this to troubleshoot much yet. I basically just copied the recipe from openmoltools (where John wrote it) and adjusted it for this, so I don't THINK it's a problem with the recipe.

There is a big bug that's causing every single package to be scheduled for rebuild.

@rmcgibbo @mpharrigan - any chance you could help me understand what's going wrong with Travis and AppVeyor here? The errors I'm seeing don't seem to obviously have to do with my recipe, but maybe I've somehow asked for conflicting versions of things or for builds I shouldn't have...
For AppVeyor I'm seeing things like this:
ERROR: File does not exist: C:\Miniconda\conda-bld\win-32\msmbuilder-3.4.0-np111py27_0.tar.bz2
Removing old build environment
BUILD START: pyemma-2.2-np111py27_0
Fetching package metadata .............
Solving package specifications: .Using Anaconda Cloud api site https://api.anaconda.org
...
Error: The following specifications were found to be in conflict:
  - numpy 1.11*
  - python 2.7*

and for Travis-CI I'm getting a failure on OS X for Python 3.4 only. I'm seeing something like this:
TEST START: solvationtoolkit-0.4.1-py34_1
Using Anaconda Cloud api site https://api.anaconda.org
Fetching package metadata ...........
Solving package specifications: .
Error: Package missing in current osx-64 channels:
  - solvationtoolkit 0.4.1 py34_1
ERROR: File does not exist: /Users/travis/anaconda/conda-bld/osx-64/solvationtoolkit-0.4.1-py34_1.tar.bz2
Removing old build environment

which is odd, because it seems inconsistent with what I'm seeing for the python2.7 and python2.5 builds (naively I was not expecting to see it looking for a build file yet at this point since this is a section where it looks like it's trying to start to build, and in the Python2.7 and Python3.5 sections it doesn't seem to be looking for a build file).
I'm just trying to sort out where I've gone wrong...
Apologies for all of the "newb" questions here.

The appveyor issue is not specific to this PR. If you look in the log for other recent PRs, the same issue is there. Some mdtraj/pyemma dependency is missing for py27np110. Not a big deal.
idk exactly what the py34 osx issue is though.

@rmcgibbo - does this mean we should be bypassing py27np110 somehow? Naively it seems like the point of tests is to only fail when something is wrong that we want to fix.

You can add skips if you want. There's a trad eoff either way.

On one hand: I'm just guessing, but the underling issue might be something like that Continuum hasn't uploaded a win32 py27np110 package for pytables. If we add a skip that prevents Appveyor from trying to build msmbuilder/pyemma for that configuration, and Continuum happens to remedy the issue tomorrow by uploading such a package, then we won't notice it and msmbuilder/pyemma will probably never get built for that configuration.
On the other hand: if the build is red, you have to kind of read through the log file and understand the root causes of a failure when filing a PR, and know whether you should be merging even you see a red X.

Honestly, there's almost always something wrong here that's beyond our control such that it's very common for the PR tests to fail, even when the PR should be merged. So I think it's generally pretty necessary to read the log files and merge even in the face of a red X.

We dropped support for mdtraj running under Python 2.7 on Windows, because no one was willing to  maintain it.  See https://github.com/mdtraj/mdtraj/pull/1125.

FWIW, it looks from the log like the windows build for msmbuilder/mdtraj is failing for every version of python with np111, so it's not just a Python 2.7 thing.

We dropped support for mdtraj running under Python 2.7 on Windows, because no one was willing to maintain it. See mdtraj/mdtraj#1125.

We haven't made a release that drops that support yet though

@jchodera - is this read to merge? I'm still not used to looking at the output of the tests on conda recipes. I tried to mirror what you're doing in smarty with the meta.yaml; it's passing some of travis's tests, and none of appveyor, but it looks like the last PR you merged behaved somewhat similarly (no success on appveyor).

@jchodera - comments addressed (except for the import test question above) so it may be ready to merge depending on your answer to that.


Bug report when reloading it trigers all switches

Hello when I reload the integration or enable feature of device my automations that are cofigured to run when state of a switch is changed runs is there any way to fix this its realy scary when my Tesla unlocks randomly :) i have it configured on my switch in garage for children that they can go in the car.

I didn't understand anything at all from your question.

I have sonoff M5 switch installed and created on it automation and when electricity goes out in our house and the switch shuts off. In home assistant I have created automations on that switch that is: "When this switch is turned on or off do this.". And the point is, that when the electricity goes out in my home asistant all the automations runs like the switch was pressed.
Thank you for your time.

Show device diagnostics for this switch.

Your attachment has not uploaded to GitHub.

Here my attachment on GitHub.
sonoff-c8978584075f5b31ec4a011d65709faa-Vypinac garaz tesla-b4be86a423b2ab257fa78cb7362545aa.json

Show yaml code of automation.

alias: Tesla charge open (vypinac)
description: ""
triggers:

type: changed_states
device_id: b4be86a423b2ab257fa78cb7362545aa
entity_id: c3c1476ddfc17ae1f0cc4e153a8e3f11
domain: switch
trigger: device
conditions:
condition: device
device_id: eccb630cdf4a459ee8c2627921d80c27
domain: device_tracker
entity_id:<PHONE_NUMBER>5d33e6ab431fab9377b5b6
type: is_home
actions:
action: notify.mobile_app_marek_12
metadata: {}
data:
message: firstf
device_id: eccb630cdf4a459ee8c2627921d80c27
domain: cover
entity_id: 5b6ae9cf654f74d8f15fba24e52265b9
type: open
enabled: true
mode: single

changed_states also means to unavailable state. So the automation is working quite well.

Okay my bad thank you for your help. Sorry for wasting your time. :(

So its an home assistant issue look, when coding in visual editor its like this.


Crash while importing a database. Seems to happen on a fresh install only

6.2.5 (631)
Thought the iCloud environment was not set correctly. After verification in the log on AppStore Connect, it seems it is ok. Now I can't access the crash log from the Organizer - not sure if more information is available than from the downloadable crash log from AppStore Connect site.
A new version has been published for testing.

@kirvanp I was able to reproduce and noted there were some unsaved data (6 updates in my cases).
To resolve the issue, we must issue a managedObjectContext.reset, which was done but after the database was imported.
Now we need to find out where those 6 updated come from and what other operations are required before importing the other database.


LXD vs. LXC: Which one is "more secure"?

My friend told me today that I should never use LXC without changing its default configuration. Instead, I should prefer to use LXD, as it is "more secure" by default (e.g. AppArmor profiles).
Is that true? What are the differences between LXC and LXD with regard to security?
I know that LXD is a wrapper for LXC, but does it really matter which system I use in terms of "basic" features? I don't need LXD's REST API for example.

The LXC/LXD Devs did a lot to make LXD secure by default:

A LXD container runs unprivileged, you have root inside the container but its mapped to a "normal" user.
The Networking API is disabled by default, it listens only on Localhost
No Script Hooks - no API calls that can an Arbitary script.
Everything just works on Xenial and is in a good place, no hacking needed.

To answer your question about Apparmor profiles, I think BUT I'm not sure these are the same for LXC and LXD. Except the "unprivileged" container I think these products are the Same.
Lets wait for a core dev. for more details about this question.

The LXC/LXD Devs did a lot to make LXD secure by default:

A LXD container runs unprivileged, you have root inside the container but its mapped to a "normal" user.
The Networking API is disabled by default, it listens only on Localhost
No Script Hooks - no API calls that can an Arbitary script.
Everything just works on Xenial and is in a good place, no hacking needed.

To answer your question about Apparmor profiles, I think BUT I'm not sure these are the same for LXC and LXD. Except the "unprivileged" container I think these products are the Same.
Lets wait for a core dev. for more details about this question.

Since LXD is using LXC behind the scenes (through go-lxc), it's certainly possible to make a LXC container as safe as a LXD one.
LXD does however make it easy by defaulting to a safe setup, using unprivileged containers by default, generating a per-container seccomp and apparmor policy and detecting and tweaking a number of extra options depending on container configuration options (automatically configures the devices cgroup, updates various list of bind-mounts, ...).
So I guess the answer is that yes, LXD is safer, simply because it does all of those things for you, right out of the box, significantly reducing the risk of you forgetting to tweak some particular options.
That does come at the cost of some flexibility obviously. LXC is still your go to option if you're building your own solution and want to have low level access to all the kernel features. But if you only care about running containers and have those be safe and have clear, well defined configuration options, LXD is the way to go nowadays.

(Also, just a reminder that LXC and LXD are both developed by the same people. We do the low level bits in LXC and then use them in LXD by adding the right user experience on top and any automatic logic which makes sense.)

@stgraber thank you so much for this detailed answer! This should be put somewhere on the LXC / LXD websites (please!)

@stgraber Just for curiosity; is this the same team which developed LXC in 2008?

@inf3rno no, the LXC team has evolved and changed quite a bit over the years. It started with @dlezcano who wrote the initial LXC codebase and was its top contributor and maintainer until around 2011 when @hallyn started pushing a number of changes to LXC for Ubuntu, I got active in 2012 and started maintaining a staging branch that Daniel would then pull from. In late 2013, Daniel made @hallyn and myself maintainers for LXC. We've since added Dwight and Christian as committers to it.
So it's certainly still the same project but people have been coming and going over the past decade as their interests change.


[protobuf-3] Build against protobuf 3

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Closing for now since we prefer users to comply with protobuf version support for Python and thus use protobuf 4. We might reopen if we get an explicit request.


Add Proyecto26 Open Source Organization

Thank you for contributing! Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md

Which change are you proposing?

[x] Suggesting edits to an existing topic or collection

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[x] Content (and my changes are in index.md)

Adding other Open Source Organization :)

Hi,
Thanks for starting this pull request. In order to review it for acceptance, we need to make sure that all of the prerequisites are satisfied. I see that you didn't check this:

I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee)

This is a requirement so that we can maintain a high level of independence in this project. Please update if you are able to verify that you meet that requirement.
Thanks!


Storage: compress model to flashpages blocks

Contribution description
This PR implement a solution to compress the data blocks in a flashpage of mtd.  The actually module presents a change in mtd_save, and mtd_load, here will be the save a defined struct or variable by the storage block
note: the current mode saves the data in the respective order, this means that when it's necessary read the data, you will received it in the same order that was saved.
features added:

Support to compressed mode --> (This will allow use correctly the memory size distribution)
Support to load storage --> (Allow load all data compressed in the storage).
Better definition of the MAX_SIZE_STORAGE,  MAX_NUMOF_FLASHPAGES, LAST_AVAILABLE_PAGE
The initialization of device was fixed making the param _pages persector take the value of FLASH_PAGES_PER_ROW

Testing procedure
go to test
make -C test/storage flash term

Expected Results:
2022-07-11 01:35:13,393 # START
2022-07-11 01:35:13,399 # main(): This is RIOT! (Version: 2022.07-devel-934-g6b7d8-HEAD)
2022-07-11 01:35:13,399 # ..
2022-07-11 01:35:13,400 # Saving data:
2022-07-11 01:35:13,404 # .
2022-07-11 01:35:13,404 #
2022-07-11 01:35:13,405 # Loading data:
2022-07-11 01:35:13,405 #
2022-07-11 01:35:13,407 # varui8_attr1 [1]: 2
2022-07-11 01:35:13,409 # varui8_attr1 [2]: 5
2022-07-11 01:35:13,411 # varui8_attr1 [3]: 6
2022-07-11 01:35:13,412 # varui8_attr1 [4]: 7
2022-07-11 01:35:13,414 # varui8_attr1 [5]: 8
2022-07-11 01:35:13,416 # varui8_attr1 [6]: 9
2022-07-11 01:35:13,416 #
2022-07-11 01:35:13,418 # varui32_attr2 [1]: 1555
2022-07-11 01:35:13,421 # varui32_attr2 [2]: 2556
2022-07-11 01:35:13,423 # varui32_attr2 [3]: 477
2022-07-11 01:35:13,425 # varui32_attr2 [4]: 8975
2022-07-11 01:35:13,427 # varui32_attr2 [5]: 987
2022-07-11 01:35:13,429 # varui32_attr2 [6]: 414
2022-07-11 01:35:13,429 #
2022-07-11 01:35:13,433 # varstr_attr3: Welcome to mesh storage!!!
2022-07-11 01:35:13,433 #
2022-07-11 01:35:13,435 # vari32_attr4 [1]: 1550
2022-07-11 01:35:13,437 # vari32_attr4 [2]: 5544
2022-07-11 01:35:13,439 # vari32_attr4 [3]: -698
2022-07-11 01:35:13,441 # vari32_attr4 [4]: -789
2022-07-11 01:35:13,443 # vari32_attr4 [5]: -97852
2022-07-11 01:35:13,444 #
2022-07-11 01:35:13,460 # ..68 65 6c 6c 6f 20 77 6f 72 6c 64 0 96 0 0 0 c8 14 0 20 1 0 0 0 b4 9 0 20 40 0 0 0 1 0 0 0 2 0 0 0 0 0 0 0 4c 48 0 0 0 4 0 0 4 0 0 0 40 0 0 0 10 0 0 0

Issues/PRs references

Good job :+1:


NegativeArraySizeException when maximize terminal window

NegativeArraySizeException when maximize terminal window when using connection over TCP

Thank you for reporting this.  Will look into it.

Closing this one.  Fix is in git head here and in the newest repo at https://gitlab.com/klamonte/jexer .


bmd / bhyve segfault (maybe due to jail?)

Hi Yuichiro,
we met on Michael Dexter's bhvye production user's call a few months back and you showed us bmd. Thanks for taking the time back then!
I'm prepping for a tutorial on bhyve for EuroBSDCon and I'd like to also point out bmd with a quick intro. I just tried working with bmd in a jail and I believe I got everything set up right, but I can't seem to get bmdctl install freebsd working - neither with uefi nor with bhyveload loader.
Here's what I get for bmdctl inspect freebsd for either case:
Running with bhyveload gives the same as uefi actually:
root@host:~user # bmdctl list
                name ncpu memory    loader       state       owner
 ------------------- ---- ------ --------- -----------  ----------
              centos    2     4G      uefi        STOP        root
             freebsd    2     2G bhyveload        LOAD        root
              netbsd    2     2G      grub        STOP        root
             openbsd    2     2G      grub        STOP        root
              ubuntu    2     4G      uefi        STOP        root
root@host:~user # bmdctl list
                name ncpu memory    loader       state       owner
 ------------------- ---- ------ --------- -----------  ----------
              centos    2     4G      uefi        STOP        root
             freebsd    2     2G bhyveload        STOP        root
              netbsd    2     2G      grub        STOP        root
             openbsd    2     2G      grub        STOP        root
              ubuntu    2     4G      uefi        STOP        root
root@host:~user # bmdctl inspect freebsd
installcmd = (null)
Segmentation fault

After running bmdctl install freebsd, the loader works fine with uefi and then bhyve seems to crash:
root@hostl:~user # bmdctl inspect freebsd
installcmd = (null)
Segmentation fault

I should probably point that raw bhyve generally works in the jail otherwise - I've used it without any other management tool as well as vm-bhyve and cbsd. I have not tried to run it bare metal yet, though I'd prefer to keep it in the jail, if possible.
Also, I somehow got a 100% CPU process with bhyve-grub launched, though I'm not completely sure why. I might have broken things because I initially didn't set boot=no for the non-FreeBSD guests in the sample config. However, the process appears to be related to the FreeBSD guest?
root@host:~user # ps ax|grep bhyve
60131  3  RJ   1:16.48 grub-bhyve -n -e -m /tmp/bmd.freebsd.59409.FdOxDQ ins-freebsd
76519  3  S+J  0:00.00 grep bhyve
99832  3  RJ   5:09.27 grub-bhyve -n -e -m /tmp/bmd.freebsd.98805.1gbwHZ ins-freebsd

Any help you could provide for troubleshooting this, is very much appreciated!
Chris

Ha, I guess I might have found the issue. I did not set up the ZFS disk volume beforehand.
Feedback: it might be helpful, if bmd would point out that the backing storage path does not exist.
I stell get the grub-bhyve process in the background, running at 100% though. Not sure where that is coming from?
You can see on the bmdctl list above, that the other guests are disabled.

Hi, I appreciate that you will make a presentation about bmd at the next EuroBSDcon.
Your guess is right. The bmd doesn't create disk images. They have to be created by hand.
I added the check code if disk images exist by the following commits.

https://github.com/yuichiro-naito/bmd/commit/9c3db56d8a4a3b52ff82a96bb600b8b9e79dc75d

https://github.com/yuichiro-naito/bmd/commit/12f172629a5bd4d6da43433660764efc035a874c

I think you are running bmd-2.3_1 from the FreeBSD packages which misses these patches.
And bmdctl inspect crash is a bug of NULL pointer dereference.
I fixed it by the following commit.

https://github.com/yuichiro-naito/bmd/commit/9726122ac2359b8c51dc7083d3c5f41b33c23cb1

grub2-bhyve is invoked from bmdctl inspect. The inspection has two phases.
The first phase tries to mount disk and iso images and looks for the OpenBSD or
NetBSD kernel. If it fails, the second phase invokes grub2-bhyve as an interpreter.
bmdctl sends commands and receives filenames to search the kernel.
While executing grub2-bhyve, bmdctl stops suddenly because of the bug.
It causes to close the pipes connected to grub2-bhyve's stdin and stdout.
grub2-bhyve reads a closed file descriptor that always returns 0 bytes.
Probably grub2-bhyve doesn't handle this case and tries to read commands infinitly.
If you have a chance to update from this repository, try the latest source or 2.5 release.


bullet-featherstone: implement WorldModelFeature feature

Part of #545.
Desired behavior
Implement the gz::physics::WorldModelFeature in bullet-featherstone.
Alternatives considered

Implementation suggestion
Reference implementation from dartsim plugin.
Additional context

feature implemented in https://github.com/gazebosim/gz-physics/pull/574