Classy student delay cannot be set under 900 seconds

Issue: The student delay cannot be set lower than 900 seconds from the UI.
Actual: After setting the time in the range of 0 to 899 seconds and saving the deliverable settings in Portal, the student delay time defaults back to 900 seconds.
Expected: After setting the time in the range of 0 to 899 seconds and saving the deliverable settings in Portal, the student delay time is set in the range of 0 to 899 seconds.
AutoBot is responding with the incorrect timing delay:

Steps to recreate:

Open a deliverable in Portal's Admin Configuration.
Set the time as anywhere between 0-899 seconds.
Click the 'save' button.
Re-open the deliverable and see that the time is set as 900 seconds.

Update:
This is not actually a bug, but the UI instructions offered more options than were available due to this restriction. The restriction of a 15 minute minimum delay has been modified. It can now be substituted with a time preference to default to if it is parameterized in the .env file.
Work done in this PR: https://github.com/ubccpsc/classy/pull/295.

Merged

@andrewstec I might recommend some docs cautioning setting too low of limits. We already get multi-hour pile ups during busy times for 310 with a 12 hour timeout. While 15 minutes makes sense for labs, it could expose the server to untenable load if, for instance, all 600 210 students had a 5 minute timeout and a common deadline.

@rtholmes
I fully understand and I think that is a good idea. We can explain how to avoid pile-ups in general and mention the greater likelihood of the pile-up with a smaller minimum delay. I will turn that into an issue that I will work on.
Out of curiosity, is there any future plan to increase the number of running queue items? I realize that scaling up is a limitation, but are there future horizontal scaling plans to process queue items?

@andrewstec this is a good question and is probably worth opening an issue on so we can have a longer discussion. There are two approaches:

The easy one. Provision the VMs larger, and tell Queue to run more concurrent runs. This will work and can be done in 15 minutes.

The hard one. Have a dedicated AutoTest VM that is shared across all courses with the understanding that most of the time courses are not facing deadlines so the average utilization will be low, but when it is high many more concurrent instances can be handled (e.g., as a first stab I would aim to handle ~50 concurrent instances across all courses). This would require some backend work, but we thought about this in advance so it would be compatible (although not exactly easy) with our current architecture.


Fix mismatched brackets in govuk_jenkinslib.groovy

I've admin merged this, as it's attempting to fix the issue that is currently causing the CI process to fail.


[Bug]: Coin selection / Batching.  Wallet replaced and merged a previous transaction without adjusting the new total.

Impacted Library name
No response
Impacted Library version
LEDGER LIVE OSX
Describe the bug
While I understand this could be a fee saving technique to batch unfirmed, The accounting is wrong AND not much was saved since an extra input was needlessly selected.

Final transaction : https://mempool.space/tx/1858f2bca7d94b5d7f4596fb1c1aa60770a82554c81a1e6fd17fee1ac4678a5a
The 0.001 BTC was replaced but the new transaction didn't include that 0.001
Expected behavior
Two transactions,
Or a replacement that sums up to both.
Additional context
No response

additionally Ledger Live keep the transaction in the history once the replacement is confirmed, even after refreshing the wallet.
Here is what wasting time on shitcoin integration leads you to.
Fail at basic Bitcoin support.

Hi @nostitos visit the official page to initiate a chat with our support team on the live chat to report your errors for review and for further assistance via Ledger Support

@nostitos
maybe you can try the "clear cache" button(top right corner settings -> Help -> clear cache)
it would recalculate the transactions and fix the balance. Thanks.

The damage is done, Had to fight with the person who claimed he sent two transaction.
Ledger Live crafted a RBF transaction that include the inputs of another previous unconfirmed transaction. Cancelling the first one via double spend in the process.
Do you see the inputs of that one?
https://mempool.space/tx/1858f2bca7d94b5d7f4596fb1c1aa60770a82554c81a1e6fd17fee1ac4678a5a
Ledger Live is such a broken and bloated piece of shitcoin trash.

@nostitos I guess that the person who claimed that he sent two transactions doesn't use Ledger-live to do the transactions.
All the transactions sent by Ledger-live is non-Rbf transactions with today's implementation

he sent two transactions doesn't use Ledger-live to do the transactions.

It was done by a noob users using Ledger X on ipad.
The only issue was that the customer thought he sent two Tx instead of one. And that's what ledger live was showing even a day later.


reorganize files, refactor, add comments, type hint pointers

Hi, how about reorganize struct?

Hi @robotomize,
I'm okay with the restructure because the file is getting too long.
But I've got a few requests before we proceed:

Could you update the unit tests and make sure they pass?
Please rename FlightCache.php to FlightsCache.php

Thanks,
Ardy

This is not the final version, it was interesting to find out what you think about it.


.env issue

the .env file contains private information that shouldn't be included

I already remove .env files from github, Thanks for the contribution.


net: lwm2m: Fix deregistration timeout state handling

Socket faults or timeouts in CoAP deregistration messages caused RD client state machine to restart registration.
Fixes #54136
@chmielewskiandreas  please review.

Socket faults or timeouts in CoAP deregistration messages caused RD client state machine to restart registration.
Fixes #54136
@chmielewskiandreas please review.

Thx. This PR looks fine :)

related issue #54504


ARSSTB-449 Added save as draft button to Upload Supporting Docs

Screenshot on ticket of completed.

@Ewan-James-Donovan have you tried using the SaveButtons helper like on most of our pages?


[jxrlib] fix iOS build

Describe the pull request

What does your PR fix?
Fixes building jxrlib on ios

Which triplets are supported/not supported? Have you updated the CI baseline?
arm64-ios, arm-ios

Does your PR follow the maintainer guide?

Yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

@russelltg, Thanks for your pr, vcpkg_configure_cmake and vcpkg_install_cmake  are deprecated functions,
please consider migrating them to the new functions:
vcpkg_install_cmake -> vcpkg_cmake_install (from port vcpkg-cmake)
vcpkg_configure_cmake -> vcpkg_cmake_configure (Please remove the option PREFER_NINJA) (from port vcpkg-cmake)
In the ports that use the new function, you have to add the corresponding dependencies:
{
  "name": "vcpkg-cmake",
  "host": true
},
{
  "name": "vcpkg-cmake-config",
  "host": true
}

And please consider adding a "license" field to the ports/jxrlib/vcpkg.json files:

Also the absolute path in the ports/jxrlib/portfile.cmake file should be enclosed in double quotes

Thank you!


[BUG] Error when building app

Information

Version: 6.41.0
Packages:

@tsed/schema

Example

Create project using latest version

tsed init .

Build project

npm run build

Acceptance criteria
Run without error
I think it's pointing to the wrong path. should be lib instead of src

:tada: This issue has been resolved in version 6.41.1 :tada:
The release is available on:

v6.41.1
GitHub release

Your semantic-release bot :package::rocket:

Hello @nxvxl
Thanks for the issue. It's released :)
See you
Romain


Limit Slack message to 50 most affected countries

To limit the size of the Slack message, this PR limits the number of countries shown to 50.
Additionally, it adds a informational top message at the beginning.

Thanks for your contribution!


Clarify what happens in the case of a tie

tie-breaker awarded to the earliest submission

hey on a totally unrelated note, when do you expect to pay out the winners? to my understanding there is nothing special we have to do; the DAI should just flow into our wallet right?

@lbrendanl


[Safe Apps] Long safe-app description is displayed out of the box

Description
Long safe-app description is displayed out of the box. As we are controlling the apps adding through the admin panel, it would make sense to add limitation on the description to escape such cases on UI
Environment

Browser: Chrome
Wallet: MetaMask
Safe:  0x1230B3d59858296A31053C1b8562Ecf89A2f888b
Environment:

https://pr2351--safereact.review.gnosisdev.com/rinkeby/app/#/welcome

Steps to reproduce

Go to the admin panel -> safe apps
add a new app with a very long description
Current result:

Expected result
It should not be possible to enter very long description

Hey @katspaugh I've some doubts here: Where we can set a limit to the description length when a new sApp is created? If we can't control this I suggest 3 options:

Show 3 lines and add a ellipsis at the end. The user will be able to read the full description once he/she open the sApp.
Add a small scroll (with styles) in each card that exceeded thous 3 lines.
Option 1 + Tooltip (but isn't recommended to present long texts inside a tooltip)

What do you suggest? Thanks! :)

3 lines sounds the best!


Installing doods2 using python virtual environment

Since docker isn’t supported well on macOS I would prefer an installation in a python venv. Can this be done and if so, is there a guide available?

The hard part will be getting tensorflow installed. There is an arm64 docker image. I haven't personally tried it but might work well. I don't have a guide. Getting tensorflow to work is a pain.

This should be the easy part:
https://www.tensorflow.org/install/pip

Did you ever try the aarch64 docker image? There's a requirements and you can try it. Tensorflow usually requires a lot of C compiliation.


DocumentRegistry bucket key contains [object Object]

As of 93c3a30edc7cc4be94bbeb3074a6a678ffd45d3b
getKeyForCompilationSetting joins compiler options as strings to form the key, but paths is an array.  There may be other non-primitive settings values.
Example value: "1|99|true|1|true||2|c:/project|[object Object]||||true||||true||"

Note that this means that we won't catch differences between path mappings and will inappropriately reuse SourceFiles.

This issue has been a wild ride. The fix is obvious and simple - serialize the paths option into the key; easy enough. The problem comes when you try to write a failing test. To spoil the ending: it's hard. That this cache key doesn't actually include the paths option doesn't usually matter. Now, the reason for that is because of two other issues, both to do with /// <reference types directives (and one extending to all module resolutions as a whole).
So, let's start from the beginning. To make an example that fails because of this cache key requires us to reuse a source file between LS program builds with incorrect data cached onto a SourceFile, derived from the paths compiler option. There are fields that are exactly that, the resolvedTypeReferenceDirectiveNames member, which includes the path a type reference directive resolves to, and the resolvedModules field, which includes the resolution locations for normal imports. So you'd think, "oh, great! just change what an import or ///<reference types points to and we should see the old resolution result leak into the new program!" Sadly, not so! As it happens, even when we reuse source files from old programs, we reassign all of the resolved resolution members! We redo all the resolution work, unconditionally. It's unclear if this is strictly a bug - if a file we load already has resolved resolutions, we should probably be reusing them rather than redoing them; this alone prevents us from actually writing a test that fails because of this incomplete cache key. This means it's possible that this cache key issue could induce conflicts in a source file shared between two LS projects with different paths settings (rather than a single project that changes over time) because the second's program build will overwrite the resolutions done in the first, but writing a multi-project test is kind of annoying (maybe fourslash can be coaxed into it, but it'd be awkward).
Fixing that allows imports to actually exhibit bad behavior because of this cache key, but isn't quite enough for ///<reference types. Why's that? As it turns out, ///<reference types doesn't do any lookups via the types compiler option. So that's another issue.
I'm probably going to put up a separate PR for the later issue, while the former will probably get fixed alongside this.


Initialize Backend CI

Simple Build Workflow has been added, more jobs are able to be added later on, as well as specifying which project (frontend or backed) to test


Question: support for Lambda Layers in TypeScript?

I could't find any indication in the documentation, but does serverless-esbuild support lambda layers written in Typescript? There's currently an open issue with serverless-webpack (https://github.com/serverless-heaven/serverless-webpack/issues/556) which does not compile the TS into JS before packaging the layer.
I was hoping I could use this package to deploy may layers.

I think that this may be a tough feature to add. Seeing as layers could have any number of entry points, I don't know if there would be a one size fits all approach.
I guess this could support single file entry point layers but I can't see how multiple entry points world work. The benefit of esbuild may be minimised if we set multiple entry points seeing as they may pull the same packages into their code.
There would also be a big question mark around how you want to pack the node modules.

This could be an interesting thing to add. I think there would be a question around how to set entry points.
I think if they specify only a path, we should treat every file in there as an entry point, otherwise people should specify what files they want as entry points.
If they have a nodejs folder we should leave it untouched to preserve the library dependency behaviour of lambda

Yes I agree. I think a convention would make sense here that if a layer points to a folder, then every file should be treated as entry point. If the layer points to a specific file like index.ts/js, then only this should be considered an entry point.
layers:
  layerOne:
    path: src/layers/one # take every file as entry point
    name: layerOne
  layerTwo:
    path: src/layers/two/index.ts # take this file as entry point
    name: layerTwo

Alternatively, the layers property inside serverless.yml could be extended with an entries property.
What would be a good starting point here? I found the [rootFileNames](https://github.com/floydspace/serverless-esbuild/blob/d9f9b41df87388dfd4d3f0d79997b4126fe2ecd3/src/index.ts#L190) as point that must potentially be extended to return functions and layers.
What else needs to be considered?

Sounds like you're keen to contribute this, very nice! Some consideration will definitely need to be taken around packaging patterns + exclude.
A few questions come to mind:

Should the external esbuild functionality affect the packaging of layers?
What if the user wants to pack some static files in the layer? Should they use package patterns? Or should we include them by default when they specify a path? (Some documentation would definitely be needed around this)

Need to also handle ignoring lambda layers which are ARNs.
Might need to check with the big man Floydspace himself. I've been using this for about a couple months only.

Hi @chriszirkel @samchungy what is the common scenario of using layers? So far in my experience, I have used layers to push there some heavy artifacts (chrome binary from puppeteer for instance) or pre-installed node_modules folder. Could you share your use case, do you push there like shared helper functions? then I have a couple of questions: do you need them to be bundled or just transpiled? Are layers one and two are managed by separate package.jsons, or the same with the app?
And apparently, lambdas reference the code from layers, so we also somehow have to avoid bundling these files, currently, it's not supported, only packages from node_modules can be marked as external.

Ah yep that makes sense. I haven't used layers in a while but my usecase was similar. I would pre-install node_modules too. So I guess we can ignore external.
I think if we make users manage their own lambda layer nodejs folder  & nodejs/package.json it would make more sense. Then we don't need to worry about it. I think the logic should be just to copy over the nodejs folder in the layer path if we see it.
When I used layers before -> I would use it almost like a common lib between lambdas to avoid having to re-upload the same files so yep, a mix of shared functions and heavy artifacts.
I think there could be a usecase for both bundling and/or transpiling layers

I currently use layers to share common code and dependencies between multiple services. Also my serverless service only contains layers and doesn't contain any functions, so I don't have the issue of lambdas referencing the code from the layer.
I agree to @samchungy logic about layer/nodejs folder. I think the existence of a package.json file inside that folder could determine the way forward. If package.json exists, the layer should be bundled and transpiled. If it doesn't exist, just transpiling all files in that folder should be enough. This distinction also affects the way the code is imported in the lambda function.  When the layer is attached to a lambda function, its content gets merged with the existing /opt/nodejs folder (https://docs.aws.amazon.com/lambda/latest/dg/configuration-layers.html).
If the layer contains a package.json file, the layer itself should be considered a package and should be imported by its package name. Therefore, the bundled and transpiled files should be outputted into its own layer/nodejs/node_modules/<package_name> folder. Then the lambda function can require('package_name') it like a normal package. On the other hand, if the layer only contains source code files, then these files should be transpiled and outputted in the same folder layer/nodejs/<file_name>. These files are available during runtime in /opt/nodejs and can be required as require('./file_name.js').
What do you think?

Guys, any solution for this? I'm trying to use layers in a serverless project with esbuild but without success. The deploy is done successfully but I have an import error

the layers problem is actually an AWS bug with the ES module. There's a serverless plugin to fix this problem (by creating a symlink from the node_modules folder inside all the lambdas). Follow the link: https://www.npmjs.com/package/serverless-esm-layer

the layers problem is actually an AWS bug with the ES module. There's a serverless plugin to fix this problem (by creating a symlink from the node_modules folder inside all the lambdas). Follow the link: https://www.npmjs.com/package/serverless-esm-layer

That is not an aws issue i guess. The lambda layers are not getting packaged or transpiled


feat(extension): allow users without memberships to tip

Allows users without a membership to tip if they have tip credits. This is accomplished by maintaining a per-iframe (which is further grouped by tab) object that maps payment pointers to them. This is similar to the way that the extension maps ILP streams to iframes grouped by tab.
This allows the tip command to complete without relying on the existence of an ILP stream to get the payment pointer it needs to send to.
Closes COIL-1831.

will revisit this for next release, see also https://github.com/coilhq/web-monetization-projects/pull/2617
https://coiltech.slack.com/archives/C01Q12WE5MG/p1645160293161159?thread_ts=1645156942.198099&cid=C01Q12WE5MG

Pulled in changes from https://github.com/coilhq/web-monetization-projects/pull/2617. Thanks @sublimator!


Fix conflict fail graph #865

This fix #865.
As the example in #865, here's the new fail graph :

But different from the workaround #1086 which has been pointed out is not reliable, this PR is done by fixing resolve graph generation.
The root cause was, scope node in graph is being selected to form a conflict edge, without checking if scope's request is really conflicted. Which may leads to the case like #865 had, scope node takes the precedence and the real conflicting request node gets left out and pruned.

Fantastic work, cheers David


How use plugin by source code?

[09:34:54.042] [Server thread/CRITICAL]: Error: "Class "CortexPE\Commando\PacketHooker" not found" (EXCEPTION) in "plugins/Smaccer/src/aiptu/smaccer/Smaccer" at line 49 --- Stack trace ---   #0 pmsrc/src/plugin/PluginBase(119): aiptu\smaccer\Smaccer->onEnable()   #1 pmsrc/src/plugin/PluginManager(454): pocketmine\plugin\PluginBase->onEnableStateChange(true)
I got this error

Is there a reason why you want to run from source?

I write plugin. I want see tips in VS code

well, you need install the dependency plugin

https://github.com/Paroxity/Commando
https://github.com/AIPTU/forms
if you don't need auto updater, you can set false in the config
https://github.com/ifera-mc/UpdateNotifier.git


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes; or I'm proposing the module to be migrated from CARML/TFVM.

Bicep or Terraform?
Terraform
Module Classification?
Resource Module
Module Name
avm-res-network-applicationsecuritygroup
Module Details
Terraform equivalent of Bicep Module
Do you want to be the owner of this module?
No
Module Owner's GitHub Username (handle)
No response
(Optional) Secondary Module Owner's GitHub Username (handle)
No response

I'm happy to contribute to this with an owner :)

I'm happy to contribute to this with an owner :)

Thank you @ASHR4, as you as we find a Microsoft FTE to own this, we'll ask him to work with you to be able to contribute

@mbilalamjad  I could help own this and work with @ASHR4  if no FTE owns it yet

I would also be willing to contribute 👍

@herms14 ,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:

Team Definitions & RACI
Shared Specification (Bicep & Terraform)
Module Support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR

I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER

@ASHR4 , @CiucurDaniel  would you like to write the code? I can make you contributors once repo has been made available

Repo created - https://github.com/Azure/terraform-azurerm-avm-res-network-applicationsecuritygroup/settings
Pending business review

@ASHR4 , @CiucurDaniel  would you like to write the code? I can make you contributors once repo has been made available

Sounds good to me, once I can access the repo I can make a start.
I'll ensure there is work left for @CiucurDaniel :)

@ASHR4 , @CiucurDaniel  would you like to write the code? I can make you contributors once repo has been made available

Sounds good to me, once I can access the repo I can make a start.
I'll ensure there is work left for @CiucurDaniel :)

Sure, sounds good to me!

@herms14
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
Before starting development, please ensure ALL the following requirements are met.
Please use the following values explicitly as provided in the module index page:
For your module:
ModuleName - for naming your module
TelemetryIdPrefix - for your module's telemetry
For your module's repository:
Repo name and folder path are defined in RepoURL
Create GitHub teams for module owners and contributors and grant them permissions as outlined here.
Grant permissions for the AVM core team and PG teams on your GitHub repo as described here.
Check if this module exists in the other IaC language. If so, collaborate with the other owner for consistency. 👍
You can now start the development of this module! ✅ Happy coding! 🎉
Please respond to this comment and request a review from the AVM core team once your module is ready to be published! Please include a link pointing to your PR, once available. 🙏
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team

@herms14 I'm still unable to access the repo, mind adding me in?

@ASHR4  I've already added you but the repo is still in private since its still pending internal business review. Will let you know once its now available publicly.

@ASHR4 @CiucurDaniel  repo is now set to public. Please start writing the code
https://github.com/Azure/terraform-azurerm-avm-res-network-applicationsecuritygroup

Hi @CiucurDaniel, I've made a draft PR of some of my changes, mostly removing unsupported interfaces for this resource
https://github.com/Azure/terraform-azurerm-avm-res-network-applicationsecuritygroup/pull/6/
Feel free to suggest any improvements/suggestions :)

Hi @CiucurDaniel, I've made a PR of some of my changes, mostly removing unsupported interfaces for this resource
https://github.com/Azure/terraform-azurerm-avm-res-network-applicationsecuritygroup/pull/6/
Feel free to suggest any improvements/suggestions :)

Hi @CiucurDaniel,
I just wanted to check in and see how you're getting on?
Feel free to shout if you need a hand with anything :)

Hi @ASHR4,
Sorry for the delay, had some time away form the office due to Eater holiday :)
I prepared some of the changes:

add outputs
fix the header of the Readme

Changes are here. Please check and if all it's good, we can re-open a PR and merge our work.
Also, for this module I would like it to also have the option to create azurerm_network_security_rules.
Do you agree with this proposal, @herms14 @ASHR4 ? Let me know if this if something you want because I would like to add that as well.

Hi @ASHR4,
Sorry for the delay, had some time away form the office due to Eater holiday :)
I prepared some of the changes:

add outputs

fix the header of the Readme

Changes are here. Please check and if all it's good, we can re-open a PR and merge our work.
Also, for this module I would like it to also have the option to create azurerm_network_security_rules.
Do you agree with this proposal, @herms14 @ASHR4 ? Let me know if this if something you want because I would like to add that as well.

Hi @CiucurDaniel,
Amazing work!
I think like the functionality should reside with the network security group AVM IMO; rather than sharing functionality with another AVM.
I'm aware the NSG AVM currently does not offer that functionality, best to raise an issue or contribute, but I believe the rules should belong to the same module that creates the NSG.
I'll take @herms14 opinion and I'm happy with either :)

Taking over ownership from @herms14 as he has switched roles.


HTTP Binary Sensor 401 authorization failure with legacy API password approach in 0.83.2

Home Assistant release with the issue:
0.83.2
Last working Home Assistant release (if known):
0.82.1
Operating environment (Hass.io/Docker/Windows/etc.):
Hassbian
Component/platform:
https://www.home-assistant.io/components/binary_sensor.http/
Description of problem:
Using x-ha-access: YOUR_PASSWORD type authentication for the http binary sensor has stopped working.  Changing it to use the long lived access token approach it works again.
Appears to be related to the other API auth issues introduced in 0.83.
E.g. this fails now with a 401 Unauthorized but worked in 0.82.1:
curl -X POST -H "x-ha-access: PASSWORD" -H "Content-Type: application/json" -d '{"state": "on", "attributes": { "friendly_name": "Driveway Motion", "device_class": "motion" }}' https://homeassistant.duckdns.org:8123/api/states/binary_sensor.drivewaymotion
And this works in 0.83.2:
curl -X POST -H "Authorization: Bearer LONG-LIVED-TOKEN" -H "Content-Type: application/json" -d '{"state": "on", "attributes": { "friendly_name": "Driveway Motion", "device_class": "motion" }}' https://homeassistant.duckdns.org:8123/api/states/binary_sensor.drivewaymotion
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
http:
  # Secrets are defined in the file secrets.yaml
  api_password: !secret http_password
  ssl_certificate: !secret ssl_certificate
  ssl_key: !secret ssl_key
  trusted_networks:
    - <IP_ADDRESS>/24
  ip_ban_enabled: False
  login_attempts_threshold: 3
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  base_url: !secret base_url

No config required for http binary sensor.
Traceback (if applicable):
Nothing in log as HA is treating the request as "401 unauthorised".
Additional information:
Happy to move to long lived tokens, but logging an issue as it appears to be a bug as the legacy password is still supported as far as I'm aware.  Thanks!

This has prevented me from upgrading. I understand the push to use the token but the way I am using homeassistant, as an API hub makes with a couple of dozen apps on various controllers calling its API makes it much too tedious to migrate. Is there anyway to continue supporting the legacy API auth as an option?

I don't think this is going to be fixed because password authentication is going away. If you can't update your callers, maybe you can use a simple proxy that takes off matching x-ha-access headers and replaces them with a token.


Bump to at least Sphinx 1.6.6

Sphinx 1.6.6 added support for emphasize-lines in PDFs.
https://github.com/sphinx-doc/sphinx/issues/1238
Currently RTD is at 1.6.5, so our PDFs are slightly less pretty than they could be.

If you need a different version of Sphinx, you can create a requirements.txt and pin the one you want.
On the other hand, we have a "feature" setting where we can mark your project to use sphinx<2. That's an admin setting that we need to enable in your project. Let me know if you want me to enable it for your project (providing its name) and I can do it. You test it, and let me know :)

I think we can bump up the default sphinx default version and the feature flag version. I'm not certain which ones we pick, but if sphinx 1.7 looks well tested on the feature flag projects, I think we can pin 1.7 at least

1.7.4 was released today. Make sure to exclude 1.7.3 because it had a recursive import.

@humitos BTW, your suggestion worked, and thank you! I assumed wrongly that I could not override the Sphinx version, since it's at the core of what y'all do. Silly me.


Universidade Save

commit_universidade_save

@Onesimo23 First stage of verification passed, official domain is unisave.ac.mz as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.


Add Python API reference [13580]

This PR adds a new section Python API Reference. This section shows the generated PyDoc documentation from eProsima/Fast-DDS-python, which just comes from the C++ doxygen documentation.
Also this branch was tested against RTD: https://fast-dds.docs.eprosima.com/en/feature-python-bindings/

@richiprosima please test this


Tiny copywriting in Readme

Two commits with this PR:

1st, let's favor our official name Bump.sh
2nd, a suggestion to redirect a link to dashboard (instead of root marketing page).

Oupsi, it looks like I forgot this PR.
Thanks for suggestion, may I ask you a new review please 🙏


fromEither

Would this be useful?
      fromEither :: (e -> a) -> Either e a -> a
      fromEither = flip either id

Example usage:
let val = fromEither error someFuncThatReturnsEither

@srid Thanks for the suggestion. I don't think that fromEither name is descriptive enough. There are several functions on Hackage that has the name fromEither and have a different type. And relude also has a few combinators for dealing with Either. I personally almost never needed a function with a type like (e -> a) -> Either e a -> a so I don't consider it common enough for inclusion into relude.

I named it such because conceptually it is similar to fromMaybe. "Conceptually", because both functions pull the value out of the structure, while using whatever fallbacks (for Maybe, that is a default value; for Either, that is applying a function).
I looked for this function more than a few times, and would come across only fromLeft and fromRight (not exactly what I wanted of course) from relude which are similar, except they discard the error value.
I'm somewhat surprised that fromEither is not commonly asked for ...


Problem bumping to 0.3.2

Hi,
First, thanks for this library which saved me days learning SwiftSyntax 😁
Second, I am having a problem updating SwiftSemantics from version 0.2.0 to 0.3.2 in my project's Package.swift
The error shown in XCode is
Dependencies could not be resolved because root depends on 'SwiftSemantics' 0.3.2..<1.0.0.
'SwiftSemantics' >= 0.3.2 cannot be used because no versions of 'SwiftSemantics' match the requirement 0.3.3..<1.0.0 and package 'swiftsemantics' is required using a stable-version but 'swiftsemantics' depends on an unstable-version package 'swift-syntax'.

Has anyone encountered this problem ?
Thanks

My Package.swiftfile is:
// swift-tools-version:5.3
import PackageDescription

let package = Package(
    name: "ModelGenerator",
    platforms: [ .macOS(.v10_15) ],
    products: [
        .executable(name: "ModelGenerator", targets: ["ModelGenerator"])
    ],
    dependencies: [
        .package(
            url: "https://github.com/apple/swift-argument-parser",
            from: "0.4.3"
        ),
        .package(
            name: "SwiftSemantics",
            url: "https://github.com/SwiftDocOrg/SwiftSemantics",
            from: "0.3.2"
        ),
    ],
    targets: [
        .target(
            name: "ModelGenerator",
            dependencies: [
                "ModelGeneratorCore",
                .product(name: "ArgumentParser", package: "swift-argument-parser"),
            ]
        ),
        .target(
            name: "ModelGeneratorCore",
            dependencies: [
                "SwiftSemantics",
            ]
        )
    ]
)

@cflorion Thanks for the kind words!
The issue you're running into stems from a limitation in how Swift Package Manager resolves transitive dependencies. Because SwiftSemantics depends on an exact version of swift-syntax, you can't depend on SwiftSemantics with a non-exact requirement.
The installation instructions in the README should work (if they don't, please let me know!) https://github.com/SwiftDocOrg/SwiftSemantics#installation

I think the point is that:
...but 'swiftsemantics' depends on an unstable-version package 'swift-syntax' ?

@wgy6055 That's right, you'd need to specify an exact version of SwiftSemantics, too. I had that wrong in the README, but just updated it. Can you still reproduce with the latest instructions?
// swift-tools-version:5.3

import PackageDescription

let package = Package(
  name: "YourProject",
  dependencies: [
    .package(
        name: "SwiftSemantics",
        url: "https://github.com/SwiftDocOrg/SwiftSemantics",
        .exact("0.3.2")
    ),
    .package(name: "SwiftSyntax",
         url: "https://github.com/apple/swift-syntax.git",
         .revision("release/5.4")),
  ]
)

@mattt I can still reproduce. I'm using Xcode build-in Swift Package Managing function instead of editing Package.swift. So I just set like this 👇

But I got this 👇

I think we should change .revision("release/5.4")) into .exact("some.stable.version") to fix this problem.

I too had to target "main" to add the package dependency as my source code doesn't live at the root of the repo and thus Package.swift doesn't work. Everything builds fine, but any time I try to run the project, I get a runtime error:
dyld: Library not loaded: @rpath/lib_InternalSwiftSyntaxParser.dylib
  Referenced from: ...
  Reason: image not found

I too had to target "main" to add the package dependency as my source code doesn't live at the root of the repo and thus Package.swift doesn't work. Everything builds fine, but any time I try to run the project, I get a runtime error:

dyld: Library not loaded: @rpath/lib_InternalSwiftSyntaxParser.dylib

  Referenced from: ...

  Reason: image not found

@tjprescott
I found something from README of SwiftSyntax. I believe this is what you need.

SwiftSyntax depends on the lib_InternalSwiftSyntaxParser.dylib/.so library which provides a C interface to the underlying Swift C++ parser. When you do swift build SwiftSyntax links and uses the library included in the Swift toolchain. If you are building an application make sure to embed _InternalSwiftSyntaxParser as part of your application's libraries.


Inconsistent behavior between 0.9 and 0.10 with constructor_type schema

Given the code:
# frozen_string_literal: true
class RootClass < Dry::Struct
  constructor_type :schema
end
class BookTest < Dry::Struct
  attribute :id, Valkyrie::Types::ID.optional
  attribute :title, Valkyrie::Types::Coercible::Array
end

In 0.9.4 I get the following:
[1] pry(main)> BookTest.new
=> #<BookTest id=nil title=[]>
[2] pry(main)> BookTest.new.title
=> []

That's perfect!
In 0.10.3 I get:
[5] pry(main)> BookTest.new
Dry::Struct::Error: [BookTest.new] :id is missing in Hash input
from /Users/tterrell/.rbenv/versions/2.3.3/lib/ruby/gems/2.3.0/gems/dry-struct-0.3.0/lib/dry/struct/class_interface.rb:109:in `rescue in new'

If I move constructor_type down to BookTest, it initializes, but I get the following:
[9] pry(main)> BookTest.new
=> #<BookTest id=nil title=nil>
[10] pry(main)> BookTest.new.title
=> nil

Defaults are no longer generated for properties that aren't passed in - which I thought was the purpose of the schema constructor_type. Is this a bug, or has the opinion of the library changed?
Thanks!

There were breaking changes for hash schemas but that was from 0.9 being released https://github.com/dry-rb/dry-types/blob/master/CHANGELOG.md#changed-3
Have you looked at the different schema options? We intentionally added schemas which support defaults. See http://dry-rb.org/gems/dry-types/hash-schemas/

Ah - I think my issue here is I just misunderstood what defaults were. For some reason I thought it would pre-populate with whatever happens when you pass nil into the type. Looks like it used to - now I can just set defaults on my type definitions. Thanks!


Add paging feature to the recordset app

Where can we review this feature?  and please assign the reviewer that can review and close this issue.

This seems to be working well, but did we want to update the permalink and the window location (replacing not adding to the window history) before considering this done? That was my impression from this morning's meeting.

Oh, also I can imaging we will want some tweaks to the UX, but I suggest that once the above is resolved  we mark it done and then have a broader review of UX as a group. That's kind of a general comment that applies to other chaise components not just this one.

the paging is working. just for anyone else reviewing this issue, we decided not to put the paging key into the bookmark because we don't have a (good) way of getting the count of the lower bound when dropped back into a recordset from such a bookmark.


Bug in DeepOnion Windows App as Windows Defender Detects a Trojan in the Installation Pack.

Expected behavior
DeepOnion is an open source project running an anonymous and 100% untraceable cryptocurrency sent through the TOR network, has a link provided in its website meant for downloading and installing its app in Windows, Mac and Linus powered systems, users are expected to get the app in installed in their system before they will create and or run an account in the program.
The 11.1Mb compressed file for Windows is expected to unzip and installation starts till completion.
Actual behavior
On downloading the app through the link provided in the in https://deeponion.org, I tried to unzip and install the app but could not because an error message displays once the compressed file extracts and a threat report is displayed by my windows defender.
The details of the threat shows that there are two files Windows Defenders see as harmful. After the threat warning, installation of the app will not run again.
How to reproduce
To reproduce the error:
Download the windows app named Window Wallet V1.5.1 from the website.
Open the zipped folder to extract the app installer
Click to open the installation file named DeepOnion-qt.exe

Browser: Mozilla Firefox (58.0.1 version)
Operating system: Windows 10 pro (64 Bit)

Recording Of The Bug
If the bug can be recorded on screen, please provide a short video or an animated GIF, otherwise delete this section.

Posted on Utopian.io -  Rewarding Open Source Contributors

Thanks for your report.
However, on our website there isn't v1.5.1 but 1.5.5
Maybe the older version you downloaded was incorrectly blacklisted by your scanner. This too could happen to harmless software if there are routines that call certain System APIs or run other packages, like we do with Tor.

Even till now v1.5.1 is still the labeling of the app form windows on your
website.
Thanks
On Sun, Feb 11, 2018 at 9:39 AM, Harris Brakmić<EMAIL_ADDRESS>wrote:

Thanks for your report.
However, on our website there isn't v1.5.1 but 1.5.5
Maybe the older version you downloaded was incorrectly blacklisted by your
scanner. This too could happen to harmless software if there are routines
that call certain System APIs or run other packages, like we do with Tor
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/deeponion/deeponion/issues/62#issuecomment-364734029,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfyGab1i9VNaPPETJ2-is9EiWOvy-GDtks5tTqcrgaJpZM4SBO3J
.

When I go to our website I see 1.5.5 there. Also the binary. I do not understand what you mean.
Anyway, the problem here is that some malware scanners recognize our binaries as "virus" or "trojan".
This, of course, isn't the case and we try hard to make all of them "happy". However, we simply don't have enough resources to make all of them happy with our software.
But you can use our DeepVault feature to check the binary you download. The DeepVaul address is below the download links.


PopupInput()

Update needed, found on firmware <IP_ADDRESS>.
It seems like PopupInput() has changed its way of handling arguments and parameters.
The example code on the wiki throw errors.
This is the new way of writing it accordingly to the system_test example files:
local function myFunction(display_handle)
	local modes = {"test1", "test2"};
	local popup = PopupInput({title="test", caller=display_handle, items=modes})
end

Rewritten Option1 example:
local function Main(display_handle) -- we need this display_handle
    local titlename = "Select your type of pizza"
    local options = {"Pineapple", "Pepperoni", "Mushroom"}
    local r = PopupInput({title=titlename, caller=display_handle, items=options, "Pepperoni"}) -- defaults to "Pepperoni"
    Printf("result: " .. r .. " is type: " .. type(r)) -- print returned number and type
end

Thanks for the update. I actually noticed back in 1.5 when I was writing a plugin for something but hadn't had time to fix the documentation. I'll get to this today.
Thanks for this!

Now I recall why I didn't fix the documentation: the signature does not seem to work as soon as I try adding the selectedValue key and there are a lot more keys that I need to figure out.
PopupInput(
   {
      title:str,
      caller:handle,
      items:table:{
         {'str'|'int'|'lua'|'handle', name, type-dependent} ...
      },
      selectedValue:str,
      x:int,
      y:int,
      target:handle,
      render_options: {left_icon,number,right_icon},
      useTopLeft:bool,
      properties:{prop:value}
   }): string:value

I think I should at least document as much as I can make work.

Fixed. There is still some missing info but the examples should now work.


The document outdated

There's no paramter called total but has one last_page as following code.
            if(to >= this.pagination.last_page) {
                to = this.pagination.last_page;
            }

Minor copy/paste error. Readme updated
see issue #2


Generalize storage implementations to support generalized accessors

The storage kind has been replaced with three separate "impl kinds", one for each of the basic access kinds (read, write, and read/write).  This makes it far easier to mix-and-match implementations of different accessors, as well as subtleties like implementing both a setter and an independent read/write operation.
AccessStrategy has become a bit more explicit about how exactly the access should be implemented.  For example, the accessor-based kinds now carry the exact accessor intended to be used.  Also, I've shifted responsibilities slightly between AccessStrategy and AccessSemantics so that AccessSemantics::Ordinary can be used except in the sorts of semantic-bypasses that accessor synthesis wants.  This requires knowing the correct DC of the access when computing the access strategy; the upshot is that SILGenFunction now needs a DC.
Accessor synthesis has been reworked so that only the declarations are built immediately; body synthesis can be safely delayed out of the main decl-checking path.

Please test with following pull request:
https://github.com/apple/swift-lldb/pull/722
@swift-ci Please smoke test.

Please test with following pull request:
apple/swift-lldb#722
@swift-ci Please smoke test.

Please test with following pull request:
apple/swift-lldb#722
@swift-ci Please smoke test.

Please test with following pull request:
apple/swift-lldb#722
@swift-ci Please smoke test.

Please test with following pull request:
apple/swift-lldb#722
@swift-ci Please smoke test.

Please test with following pull request:
apple/swift-lldb#722
@swift-ci Please smoke test.

Please test with following pull request:
apple/swift-lldb#722
@swift-ci Please smoke test.

PR #17623 may result in a manual merge for the SILGen LValue access scope stuff.

Please test with following pull request:
apple/swift-lldb#722
@swift-ci Please test.

Build failed
Swift Test OS X Platform
Git Sha - d769b175ffdadd5c94ffcf63fa1e626ed4704ded

Build failed
Swift Test Linux Platform
Git Sha - d769b175ffdadd5c94ffcf63fa1e626ed4704ded

Please test with following pull request:
apple/swift-lldb#722
@swift-ci Please test.

Build failed
Swift Test OS X Platform
Git Sha - e6cf4c69cbb99b0f005ad62dd0a51f118a67bdd9

Build failed
Swift Test Linux Platform
Git Sha - e6cf4c69cbb99b0f005ad62dd0a51f118a67bdd9

Please test with following pull request:
apple/swift-lldb#722
@swift-ci Please test.

Build failed
Swift Test OS X Platform
Git Sha - 7868489d4dab0581226ed544a8e247d7d46099c3

Build failed
Swift Test Linux Platform
Git Sha - 7868489d4dab0581226ed544a8e247d7d46099c3


Streamline support for Fork based workflows

Currently the recommended approach for dealing with fork based workflows is to do the following.
If I am was working on an open source project where I have a fork of the official repository.
I would have my local clone of my fork with main as the local branch and origin/main as the configured tracking branch. Then I would have separate remote named upstream that would point to official repository.
My stack of changes would be on main and would effectively be the commits from origin/main  to main.
Ideally you would want to probably request review with gps rr <patch-index> however currently this would create a pull request to your origin/main which you DO NOT want.
To work around this at the moment instead of doing a request review you can do a gps sync <patch-index> which will created the request review branch for you and then you can go to GitHub, Bitbucket, etc. and manually create a Pull Request from that branch into the upstream of the fork.
Then once your PR is accepted and integrated into the fork's upstream main you would pull changes down from it using the following.
git fetch --all
git push -f origin upstream/main:main
gps pull

Looking at this workflow it seems like there are two areas we could probably improve this pretty easily.

Add support to the gps rr command to specify a different base branch. There is actually already a ticket for this, #19 .
Add support to the gps pull command to be able to "match" the remote tracking branch to a specified branch, e.g. gps pull -m upstream/main

i was looking into how this would work, but it looks to be a bit more complicated for what data would be passed to the hook.
If we assume we've got:

An upstream owner: UPSTREAM_OWNER
An upstream repo: UPSTREAM_REPO
An upstream trunk we want to merge into: TRUNK
A forked owner: ORIGIN_OWNER
A forked repo: ORIGIN_REPO
A forked branch we want to merge: FORK_BRANCH

Then what we do for Bitbucket, GitHub, and GitLab is all different:

For Bitbucket, you:

Open a PR against upstream:POST /2.0/repositories/{UPSTREAM_OWNER}/{UPSTREAM_REPO}/pullrequests

And provide a body like:{
    "destination": {
        "branch": {
            "name": "TRUNK"
        }
    },
    "source": {
        "branch": {
            "name": "FORK_BRANCH"
        },
        "repository": {
            "full_name": "ORIGIN_USER/ORIGIN_REPO"
        }
    }
}

For GitHub, you:

Open a PR against upstream:POST /repos/{UPSTREAM_OWNER}/{UPSTREAM_REPO}

And provide a body like:{
    "base": "TRUNK",
    "head": "ORIGIN_REPO:FORK_BRANCH"
}

For GitLab, you:

Open a MR against the fork:POST /projects/{ORIGIN_OWNER}%2F{ORIGIN_REPO}/merge_requests

And provide a body like:{
    "source_branch": "FORK_BRANCH",
    "target_branch": "TRUNK",
    "target_project_id": "UPSTREAM_ID"
}

It's totally possible to figure these things out. But it seems like it'd take a bit more work to actually let the hooks be reusable instead of being specific to GitHub. In particular, it seems that GitLab uses numeric ids instead of the owner/repo approach for the upstream. It might actually accept both, but it's kind of unclear. In any case, that's kind of a think a hook specific to GitLab would have to figure out.
The question I guess is where does the logic live? If the logic needs to live in the hooks, then every hook is going to have to re-figure out how to interpret something like upstream/main and main into the six variables it needs (FORK_BRANCH, TRUNK, etc.).
If the logic lives in gps, then It seems like the hooks would need to have seven! arguments given:

RE_REQUESTING_REVIEW (required, this already exists)
FORK_BRANCH (required, this already exists)
TRUNK (required, this already exists)
UPSTREAM_OWNER (optional, this would be new)
UPSTREAM_REPO (optional, this would be new)
ORIGIN_OWNER (optional, this would be new)
ORIGIN_REPO (optional, this would be new)

Seven arguments is a lot. So, I recognize that this might seem overkill. I'm not sure how else to keep a separation between the methodology and the hook short of introducing some ad-hoc encoding scheme. But, this approach means that the logic only has to be figured out once and the hooks can case on whether they receive three arguments or seven.
I didn't look into the gps pull side, so I dunno if there's similar issues there. But I was considering making a PR for this, and it got a bit complex so I wanted to see what your thoughts were.

Oh, I guess another thing to mention is that the gh CLI works in a "smart" way in that you decide up front whether you're making PRs against origin or upstream and it does the rest for you. So in the case where someone is using gps on a forked GitHub repo and also using the gh CLI in the hook, the first step is kind of already done if they setup gh properly. On the flip side, if they don't set it up properly, or if they aren't using gh, it's back to square one.

So not that this is a 100% ideal solution. But gps has repository specific hooks so that things like this can be currently hard coded into the hook.
Maybe it would make sense to provide a shell library that can be used in the hooks. That way people can just call a function and pass hard coded values in for the service specific differences, and pass in the shared variables from gps.

As a general rule of thumb gps shouldn't know anything about GitHub, Bitbucket, GitLab or any other SCM hosting provider. All gps should know about is Git.
At least that is the separation that I am trying to maintain.

Would it be possible to configure the push remote as a workaround for git-ps branches? It would still something that would have to be configured, but at least it should be possible to do so only once (if your remotes are named consistently across repos).

Yeah, we could always add a repos specific configuration for this as well that we could use to address gps rr working with the correct remote.

The current recommended workflow is as follows and assumes that you have a fork of a repository which origin maps to.
If we have a patch stack setup from origin/main and main we can develop our patches directly on top of it as usual with gps. Once we have a patch or series of patches ready we need to create a branch and push it up to origin. With gps this is as easy as the following.
gps branch -p -n some-branch-name <start-patch-index> [end-patch-index]

The above command will create a local branch from the patch(es) and push it up to the remote, in this case origin. Then you simply create a pull request from that branch on your fork to the upstream repository manually using Bitbucket or GitHub.
If your PR is approved and integrated into main of upstream. Then you would update your your origin/main based on upstream/main. This would look something like the following.
git fetch upstream
git push origin upstream/main:main
gps pull

This will collapse the integrated patch(es) out of your stack as they are now included in origin/main.
If your PR wasn't approved and they had some comments you simply modify your patches with gps as you normally would and then use the gps branch command as follows again with the same branch name.
gps branch -p -n some-branch-name <start-patch-index> [end-patch-index]

This will update the branch with the updated version of the patch(es).
The above is what we should probably look at simplifying in some way to better support this workflow.


poland.js: Is maryMotherOfTheChurch a feast in Poland?

@pejulian added this comment in the poland.js, so I believe @jarosz should confirm this possible issue. Below is the relevant code.
// [pejulian] Needs confirmation: In Poland this day is a feast
    {
      "key": "maryMotherOfTheChurch",
      "type": Types[4],
      "moment": ( y => Dates.pentecostSunday( y ).add( 1, 'days'))( year ),
      "data": {
        "prioritized": true,
        "meta": {
          "liturgicalColor": LiturgicalColors.WHITE
        }
      }
    },

It's a memorial in general calendar since 2018. Some countries, dioceses and religious families who petitioned the Holy See were allowed to add this celebration to their particular calendars. It's been a feast in Poland since 1971 and it continues to be like that.
Sources mention, that it was celebrated like that in Argentina as well (e.g. https://www.ncronline.org/news/vatican/pope-adds-feast-mary-mother-church-universal-calendar), but I can't verify. It's not in romcal.

@jarosz, good to know that this is not an issue in pl.js. I just wanted you to confirm this. We should create a PR to remove comment.
As for the argentina.js, as this celebration is not listed in that calendar, I would keep it that way (the optional memorial from GRC is still loaded) … until someone with enough knowledge would improve this calendar.

And what to do with ukraine.js? Is it confimed to be a feast?

Managed to confirm, try if you can read it :)

Although, I can read it, how  do you know what celebration rank (type) it is? But in this I would partially rely on the Wiki, which clearly states it is a feast, therefore that comment should be removed too.
By the way: good catch! :smiley:

I've found it also on other website: Пресвятої Діви Марії, Матері Церкви, свято
https://risu.org.ua/ua/index/resourses/calendar/calendar_archive/74133/


Instana blog post and images

Description

Urgency

[ ] Blocker
[x] High
[ ] Medium

Requirements

Test all commands and procedures.
Build content locally and test for formatting/links.
Add redirects to dcos-website/redirect-files.
Change all affected versions (e.g. 1.7, 1.8, and 1.9).
See the contribution guidelines.

@ryadav88 The Instana post is finally ready! Want to give it a last look over and merge it if you don't find anything? Also, should I start assigning these to Sara now that she's here?

should I start assigning these to Sara now that she's here?
For now, you can continue to assign them to me.


Fix - esp32c6 support as MCU

Modified the chip and build to support the new MCU

Added support for MCU esp32c6
Disabled autodiscovery for Risc target

I've implemented similar changes to the proposed here, yet I had to extend the fixes a bit so that the used GCC is correctly detected and there is no need to set CC flags.
As for MCU auto-discovery - I've lowered this to a Cargo build warning. I don't want to set all builds to fail if MCU is not defined, and anyway most of the folks are still running with esp32c3 w.r.t. riscv MCUs; c3 is picked as the default MCU if the user has not specified an MCU for a riscv target, and furthermore, a visible build warning is issued in that case.

Thanks, imho, the template creator should ask for the target model from a list and write down the mcu variable for further iterations and precision/control of the developer.

Thanks, imho, the template creator should ask for the target model from a list and write down the mcu variable for further iterations and precision/control of the developer.

I do not understand what you are saying. Can you elaborate?

In both repositories, esp-template and esp-idf-template, I think this file should have the condition to add based on the input from the user, the correct MCU variable by default.
By that, you can keep this autodiscovery functionality as a secondary utility but start to provide an explicit reference in new projects for the MCU so, let's say, 'we' start some good practices among the future developers and not entirely rely in an auto-discover that in case of failure, it's a very 'black-box' function and you can get frustrated.
Mostly based on my recent experience, where it took days to detect that the bootloader used was the C3 instead of C6 because nothing in the process tells you that. That opaque behaviour simplifies, yes, only if they are extremely resilient but in case of failure, god bless you to find the proper alternative.
In the end, if I start a new project, is because I have already a board on my table, I know the board and ensure that ALL the systems in the process are doing the right thing for the right board, is a much more pleasant developer experience IMHO.

yeah but that is not related, to esp-idf-sys itself. We just need to use the MCU env variable inside the templates for the variants, and i think we currently don't even have an option for an esp32c6 since we didn't have support for it so far.


uncrustify: add space before name of typedef

typedef enum {
     vvv
}name;

becomes
typedef enum {
     vvv
} name;

Signed-off-by: Patrick Boettcher<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #6647   +/-   ##
=======================================
  Coverage   53.51%   53.51%
=======================================
  Files         438      438
  Lines       41462    41462
  Branches     7941     7941
=======================================
  Hits        22190    22190
  Misses      16050    16050
  Partials     3222     3222

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 7f28edc...53b5a83. Read the comment docs.


peer to peer code review

Hi @manzitresor,

Great job done so far there are some required changes:

Requred Changes ♻

Please add the line-through styling over the text when we click the checkbox.

https://github.com/manzitresor/todolist_review/blob/f16db0d3cd0f30068f065dbcfa9f47861e86a4bd/src/functionality.js#L34-L37

Your Live Demo link is not working properly please deploy the page correctly over GitHub pages.

Hi @Chandan-devs-tech  Thanks  so much for Review feedback 👍
I will take all suggested changes into consideration,
cheers 🍾


[feature request] Reader support seek by timestamp.

Motivation
CPP client already supported, In python client, just need wrapper it.

I am confused why this was opened. There has been a test for seeking by timestamp for a while: https://github.com/apache/pulsar-client-python/blame/8c36eb70f981c6cc1dec7691c7ab759a5520204d/tests/pulsar_test.py#L1001 .
Though the time.sleep(0.5) right after looks questionable. Do we have to guess when the seek is finished before attempting to read?

I am confused why this was opened. There has been a test for seeking by timestamp for a while:

You are right. I missed it.

Though the time.sleep(0.5) right after looks questionable. Do we have to guess when the seek is finished before attempting to read?

I think not. It is a sync method. I push a PR to remove sleep.

Fantastic. Thank you!


HSEARCH-4260 Display Java version during builds

https://hibernate.atlassian.net/browse/HSEARCH-4260

Merged, thanks!


Doc procedures for developing this repo on acq PCs and set up git hooks on Aeon3 and Aeon4

Duplicate of #356


[DO NOT MERGE] Avoid YETUS-994 for testing

Check whether hadoop-multibranch job works or not.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 33s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
shadedclient
21m 25s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
shellcheck
0m  0s

There were no new shellcheck issues.

+1 :green_heart:
shelldocs
0m 14s

There were no new shelldocs issues.

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
shadedclient
15m  1s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 40s

The patch does not generate ASF License warnings.

39m 39s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2346/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2346

Optional Tests
dupname asflicense shellcheck shelldocs

uname
Linux 1d4702482602 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 984875c624b

Max. process+thread count
422 (vs. ulimit of 5500)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2346/1/console

versions
git=2.17.1 maven=3.6.0 shellcheck=0.4.6

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

OK. Reverting YETUS-994 worked.

The new token worked as expected, so we don't need to revert YETUS-994 in our setting.
Closing.


Issue: 6399 Avoid duplicate AES requests 4.x Releases?

Please ask your question
At present we are trying to work around this issue by increasing buffer size to give more tolerance for slower license requests.
I did see that the issue: https://github.com/shaka-project/shaka-player/pull/6399 had been merged and was hoping it would make it into latest 4.7 releases as well as 5.0.
I do not see it listed in the release notes though. If it has not been included would it be possible to have in backwards compatible releases?

We plan to release version 4.8 soon, which will include this change.


Bug 2114504: flip menu vertically when it reaches the boundary

Before:

After:

/hold

/hold cancel

/lgtm cancel

/test odf-console-e2e-aws

/lgtm cancel

this PR works totally fine and we can merge this as well if we want.
cancelled lgtm because PF also provides a prop isFlipEnabled for a Dropdown, but passing that prop is not working as expected. In sync with PF team as it's a known bug from PF side.

isFlipEnabled

ack

/lgtm cancel

this PR works totally fine and we can merge this as well if we want. cancelled lgtm because new version of PF also provides a prop isFlipEnabled for a Dropdown, but passing that prop is not working as expected. In sync with PF team as it's a known bug from PF side.

@GowthamShanmugam @bipuladh we can go ahead and merge this PR for now (until it is fixed in newer version of PF).
PF has opened an issue on there end https://github.com/patternfly/patternfly-react/issues/8013 to fix the bug with isFlipEnabled prop !

/lgtm


Add statement cache to insert/update/delete

This makes introducing the Ecto.Integration.Post schema a thousand times in a row almost twice faster since we avoid a round trip to the database.

Closing this for now as the one in Postgres will have less contention (at the cost of memory).


Fix Greengrass reset_deployments responding in 403 AccessDeniedException

Please help keep the CHANGELOG up to date by providing a one sentence summary of your change:
Fixes GreenGrassClient reset_deployments method that was responding with 403 AccessDeniedException

PR


Allow option to build in root, not dist/

Type of Issue
[X] Feature Request

Description
Currently ng-packagr always produces packages in a dist/ folder underneath the root of the project.  I propose providing an option to create the output directly in the root.
My use case:
I am building a monorepo of several angular components, and am using lerna to manage the build for the monorepo.  By default, lerna does not have the ability to publish out of the dist folder, and they will not implement that because building to a dist folder does not follow established npm best practices.  See:  lerna/lerna#91 lerna/lerna#901 lerna/lerna#1282
In the discussion of lerna/lerna#1282 I learned that the dist folder is really an anti-pattern in npm.  It causes npm link to a module using ng-packagr to fail because the root folder will be linked, not the dist folder.  I'm worried this is going to become a real problem for my project once I start to have dependencies between packages within my monorepo.
From what I can tell, it shouldn't be that difficult to implement this.  The package.json that is produced in the dist folder doesn't really have to be any different than the one in the project root with the exception of a few additional properties: (main, module, es2015, metadata, typings, etc.)
Ideally, I would love to see this change also backported to 1.x and 2.x because of #814

Have you tried setting the dest in your ng-package.json ?

Try setting the dest to the root directory.
It's an anti-pattern in npm to not have made the dist folder layout a pattern. Gradle writes output to the build directory, maven writes it to target and others do similar. Lerna should update their code for managing and linking dependencies. They should not use npm link at all, as it is flawed either way.

It's by the way not going to work by design as it would override the package.json.
I'm staying baffled at what is the right and wrong way and strongly believe that anyone should be allowed to find and go their way. Generating the distribution-ready package.json is a key benefit and is not going to go away.


Support lazy TsdFrame/TsdTensor

Currently, this call will load all LFP data into RAM, which is prohibitive for very large datasets:
data = nap.NWBFile(nwb)
data["ElectricalSeriesProbeA-LFP"]

Would it be possible to make a lazy TsdFrame (and probably TsdTensor) representation?
This would also allow to speed up and minimize the memory footprint for the compute_perievent_continuous and other LFP-related processing

Adding comments from another issue here :
I was going through TsdTensor and I'm wondering if it supports lazy compute.
Example use case:
With calcium imaging data, the outer product of spatial & temporal components can result in a huge array that is hundreds of gigabytes or terrabytes in size. It is almost never necessary to actually compute the entire array, so using a lazy compute data structure works well. The implementation in mescore computes the outer product only when the array is sliced: https://github.com/nel-lab/mesmerize-core/blob/master/mesmerize_core/arrays/_cnmf.py#L131-L141
As discussed:
So far, feeding a numpy memmap to d in TsdTensor seems to work.
It's probably possible that any object that implements the numpy array API could work if fed to d. Will test with our LazyArray implementation, as well as other array types (like zarr, dask etc.)

Thanks @gviejo
This seems related but the in memory object is created by nap when accessing the NWB field. So I think that this might need a patch to pass directly the h5py.dataset or the zarr.array to the TsdFrame

Fixed by https://github.com/pynapple-org/pynapple/pull/264


Breadcrumb: missing focus state, remove hover from "last" item

What happened?

the "last" item should be completely inactive --> remove hover effect
the other (active) items should also have a focus state (blue outline)

What type of frontend frameware are you seeing the problem on?
Others
Which version of iX do you use?
v1.3.0
Code to produce this issue.
No response

Moved to JIRA


Some suggestions

This PR contains a list of suggestions for sinkhorn and sinkhorn2 (maybe one could use a bit more descriptive names? I guess they are motivated by the POT counterparts but it was completely unclear to me that one computes the map and the other one the cost without reading the documentation) that allow to use different array and number types such as CuArray and Float32. I also added some tests and some preliminary Travis integration (but I guess you have to activate it as well).

Hi @devmotion,
This is great! Thanks for the suggestions. Merging now.

maybe one could use a bit more descriptive names? I guess they are motivated by the POT counterparts but it was completely unclear to me that one computes the map and the other one the cost without reading the documentation

Yes, that was the motivation for the naming. Although I agree with your comment, and could definitely change that.


fixing issue with view sizes for specific multitasking case

when running app with side menu on iPad device in Split View mode - it
takes wrong size for main view controller and side menu table view
controller (it is caused by taking sizes from UIScreen not from
UIApplication)

Hi @IgorSavynskyi!
First, thanks for wanting to contribute to SideMenu -- I really appreciate anyone that's willing to take the time to help!
Correct me if I'm wrong, but I think the problem you're experiencing is that when in split-mode, SideMenu may end up being larger than the app width itself since it's calculating its width from the screen and not it's portion of the screen. Is that correct?
Regarding your proposed changes, I am slightly weary of your solution because it's possible for keyWindow == nil depending on how an app is architected. This is very unlikely, but possible. If this happens, SideMenu will cause a crash.
Perhaps instead of a forced unwrap ('!'), it would be better to use a Nil Coalescing Operator ("??") as a fallback to use the screen size in case keyWindow == nil. Alternatively, are there any other non-nil system methods that could be used to determine the size? I was going to suggest UIScreen.mainScreen().applicationFrame but that appears to have been deprecated in iOS9. This article seems to post one alternative for that but it seems hackish: https://forums.developer.apple.com/thread/16083

Hi @jonkykong !
Your are absolutely right concerning the problem I am facing with.
Seems that "keyWindow" really can be "nil" in some specific cases.
I've found in this thread https://forums.developer.apple.com/message/102967#102967 helpful advice from Apple's engineer Rincewind. He says just to create new UIWindow  and it will pick correct app's size. I've tested it in code and it seems to work correct and it doesn't cause performance issue. How do you like this solution?

I think that might work -- I still don't like it but I don't see a better, cleaner way!

@IgorSavynskyi any updates here?

@jonkykong  I've added separate computed property which is to provide us relevant correct size of the window has been allocated for our app. Thus we are using this property both in SideMenuTransion and SideMenuManager.

This looks great! Last question -- does appScreenRect need to be public?

Yes, as it is currently used only inside module - "public" marker will be unnecessary)

@IgorSavynskyi Thanks for contributing! I will be validating and merging your branch soon.

Note: I made small adjustments to scope and logic.


Sponsors modular

Referencing issue #12
Add modularity to sponsors using the same YAML files located in data/clients/.
Size of the sponsors was homogenized to 357 × 76 pixels. A background in SVG was added for easier resizing of the logos.

I'll make this PR again.


Docker Compose Deployment for securing unorchestrated container

Feature Request
Short Description
We currently have a systemd deployment which helps manage unorchestrated containers and host policies
Ref https://github.com/kubearmor/KubeArmor/blob/main/getting-started/kubearmor_vm.md
Is your feature request related to a problem? Please describe the use case.
Folks might want to just start another container and not deal with the package management hassle to start systemd service.
Describe the solution you'd like
Docker Compose File and Documentation to run KubeArmor directly with docker.
Here's how you can do it
docker run -v /opt/kubearmor/BPF:/opt/kubearmor/BPF --privileged kubearmor/kubearmor-init:stable

# Followed by

docker run -v /opt/kubearmor/BPF:/opt/kubearmor/BPF -v /sys/fs/bpf:/sys/fs/bpf -v /sys/fs/bpf:/sys/fs/bpf -v /sys/kernel/security:/sys/kernel/security -v /sys/kernel/debug:/sys/kernel/debug  -v /var/run/containerd/containerd.sock:/var/run/containerd/containerd.sock -v /run/containerd:/run/containerd -v /var/lib/docker:/var/lib/docker --privileged  --pid=host --ipc=host --net=host kubearmor/kubearmor:latest -k8s=false

This is privielged but we won't need the privileges and can mention exact capabilities as well in the docker compose file.

hey @daemon1024 . Could you pls assign this to me , i would like to work on this

I would love to solve this issue @daemon1024 Pls assign this issue to me

#1343

hey @daemon1024 can you please guide me related to the capabilities  which is to mention ?

@yashvardhanmishra I am really sorry I by mistake link my pull request with other issue and you haven't get noticed and created pull request

Folks @yashvardhanmishra @sarthaksarthak9 Thanks a lot for the interest and raising the PRs already. Both of them look duplicated efforts, let's handle it in a single PR.
@sarthaksarthak9 why don't you help review @yashvardhanmishra PR since he wanted to work on the issue first. I appreciate both of your efforts a lot so thank you.

Folks @yashvardhanmishra @sarthaksarthak9 Thanks a lot for the interest and raising the PRs already. Both of them look duplicated efforts, let's handle it in a single PR.
@sarthaksarthak9 why don't you help review @yashvardhanmishra PR since he wanted to work on the issue first. I appreciate both of your efforts a lot so thank you.

yah sure why not

This is an open issue again

I want to work on this issue. Please assign this issue to me

@daemon1024 I'm trying to solve this.
The docker compose file works and starts kubearmor after kubearmor-init has finished running.
But the policy enforcement doesn't seem to work.
For example, I created container for wordpress-mysql via the docker-compose file:
services:
  wordpress:
    container_name: wordpress-mysql
    image: wordpress:latest
    ports:
      - 80:80
    restart: always
    environment:
      - WORDPRESS_DB_HOST=db
      - WORDPRESS_DB_USER=wordpress
      - WORDPRESS_DB_PASSWORD=wordpress
      - WORDPRESS_DB_NAME=wordpress
volumes:
  db_data:

The creation of the container is successfully detected by KubeArmor (which is running as a docker container).
Then, I applied a block policy via karmor vm policy add ksp-wordpress-block-policy.yaml which is:
apiVersion: security.kubearmor.com/v1
kind: KubeArmorPolicy
metadata:
  name: ksp-block-policy
spec:
  severity: 3
  selector:
    matchLabels:
      kubearmor.io/container.name: wordpress-mysql
  process:
    matchPaths:
    - path: /usr/bin/apt
    - path: /usr/bin/apt-get

      # apt update
      # apt-get update

  action:
    Block

The security policy is also detected by KubeArmor -
Detected a Container Security Policy (added/container_namespace/ksp-block-policy)
But now if I exec into the wordpress-mysql container and run apt update it isn't blocking that!

Just checked that while running KubeArmor as a docker container I get the error:
2024-05-20 10:46:32.776962      ERROR   Failed to read /etc/apparmor.d (open /etc/apparmor.d: no such file or directory)

and
2024-05-20 10:46:32.777088      INFO    Disabled KubeArmor Enforcer since No LSM is enabled

Since the KubeArmor Enforcer is disabled, the policy is not enforced.
However, KubeArmor enforcer works fine for k8s env in the same machine.

@DelusionalOptimist I want work on this issue, please assign me.

you can work on this issue, my friend

@navin772 can you check the output of cat /sys/kernel/security/lsm?
If it doesn't have bpf in it, check this out - https://github.com/kubearmor/KubeArmor/wiki/Support-for-non-orchestrated-containers#policy-enforcement-for-containers-running-in-docker-with-apparmor

@DelusionalOptimist I have bpf as the lsm:
$ cat /sys/kernel/security/lsm
lockdown,capability,landlock,yama,apparmor,bpf

containerd runtime is currently not supported as mentioned in https://github.com/kubearmor/KubeArmor/issues/1426. Enforcement with docker runtime works.
Commands:

docker run -v /tmp/:/opt/kubearmor/BPF kubearmor/kubearmor-init:stable
docker run -v /tmp/:/opt/kubearmor/BPF -v /sys/fs/bpf:/sys/fs/bpf -v /sys/kernel/security:/sys/kernel/security -v /sys/kernel/debug:/sys/kernel/debug  -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/docker:/var/lib/docker --privileged  --pid=host --ipc=host --net=host kubearmor/kubearmor:latest -k8s=false

--privileged flag is not required for kubearmor-init when using the /tmp/ dir but in the kubearmor container it is required (even if we explicitly list the capabilities).

@navin772 Do we get any specific errors while running with explicitly listed capabilities or it's just that enforcement doesn't work? :eyes:

@DelusionalOptimist kubearmor fails to start with error:
kubearmor-1       | 2024-06-21 10:05:50.066540	INFO	Node Name:
kubearmor-1       | 2024-06-21 10:05:50.066545	INFO	Node IP:
kubearmor-1       | 2024-06-21 10:05:50.066550	INFO	OS Image:
kubearmor-1       | 2024-06-21 10:05:50.066554	INFO	Kernel Version:
kubearmor-1       | 2024-06-21 10:05:50.066807	INFO	Initialized KubeArmor Logger
kubearmor-1       | 2024-06-21 10:05:50.067695	INFO	Detected mounted BPF filesystem at /sys/fs/bpf
kubearmor-1       | 2024-06-21 10:05:50.067968	INFO	Initializing eBPF system monitor
kubearmor-1       | panic: runtime error: invalid memory address or nil pointer dereference
kubearmor-1       | [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x193ebc6]
kubearmor-1       |
kubearmor-1       | goroutine 1 [running]:
kubearmor-1       | github.com/cilium/ebpf.(*Map).Update(0x1d3ed20?, {0x1d3ed20?, 0xc0000e3e80?}, {0x1f2aa80?, 0xc000182280?}, 0xc00030f1f8?)
kubearmor-1       | 	/go/pkg/mod/github.com/cilium/ebpf@v0.12.3/map.go:724 +0x26
kubearmor-1       | github.com/cilium/ebpf.(*Map).Put(...)
kubearmor-1       | 	/go/pkg/mod/github.com/cilium/ebpf@v0.12.3/map.go:719
kubearmor-1       | github.com/kubearmor/KubeArmor/KubeArmor/monitor.(*SystemMonitor).UpdateNsKeyMap(0xc0001fcc00, {0x1f69ac7?, 0x1f74be5?}, {0x0, 0x0}, {0x12?, 0x2b?, 0x55?, 0x0?})
kubearmor-1       | 	/usr/src/KubeArmor/KubeArmor/monitor/systemMonitor.go:343 +0x52e
kubearmor-1       | github.com/kubearmor/KubeArmor/KubeArmor/monitor.(*SystemMonitor).UpdateVisibility(0xc0001fcc00)
kubearmor-1       | 	/usr/src/KubeArmor/KubeArmor/monitor/systemMonitor.go:435 +0x22a
kubearmor-1       | github.com/kubearmor/KubeArmor/KubeArmor/monitor.(*SystemMonitor).initBPFMaps(0xc0001fcc00)
kubearmor-1       | 	/usr/src/KubeArmor/KubeArmor/monitor/systemMonitor.go:228 +0x116
kubearmor-1       | github.com/kubearmor/KubeArmor/KubeArmor/monitor.(*SystemMonitor).InitBPF(0xc0001fcc00)
kubearmor-1       | 	/usr/src/KubeArmor/KubeArmor/monitor/systemMonitor.go:470 +0x1f8
kubearmor-1       | github.com/kubearmor/KubeArmor/KubeArmor/core.(*KubeArmorDaemon).InitSystemMonitor(0xc000525800)
kubearmor-1       | 	/usr/src/KubeArmor/KubeArmor/core/kubeArmor.go:257 +0x8a
kubearmor-1       | github.com/kubearmor/KubeArmor/KubeArmor/core.KubeArmor()
kubearmor-1       | 	/usr/src/KubeArmor/KubeArmor/core/kubeArmor.go:533 +0xf56
kubearmor-1       | main.main()
kubearmor-1       | 	/usr/src/KubeArmor/KubeArmor/main.go:79 +0x3ed
kubearmor-1 exited with code 2


[STA-140] Fish location and inconsistencies

Goby season and locations are incorrect
Tiger Trout season and locations are incorrect

Currently our fish.json file pulls from the fish.py parser - but given the fact that the wiki is not consistent with the games Fish.xnb file, we'll need to use Locations.xnb for the more up to date data.
From SyncLinear.com | STA-140

I will tackle this one here. Will have a fix tonight.

Appreciate you taking a stab @tindolt! The issue with this one is that the Fish.json apparently isn't the best source of truth for the seasons they're in. We were going to swap to using Locations.json for this, but it's a bit of a pain to process. Hope that context helps out 👍

Absolutely would appreciate it @tindolt - would love if you joined our Discord as well so we could chat more there :)


Export armature animation with bones - more than two NLA animations does not deflect same amount

Describe the bug
I have an armature with two NLA animations. A joystick that move fore and aft (anim1) and left and right(anim2). In blender the animation moves the entire distance when both animations are active. In the export to gltf/bin the animations seems to be about 1/2 the displacement.
To Reproduce
Create joystick - cylinder.
Add armature
add bones, 4 bones. main, fore_aft, left_right and base.
weight piant fore_aft bone to
weight paint left_right
make animation 0,1,2 KF, 0 is left 1 center 2 right
make second animation, 0 fore 1 center 2 aft
animation displacement rotation 45 degrees.
make animations and push down stack NLA
make default state bone (not required) 0,1,2, all center. - required for MSFS
Expected behavior
in blender it moves 45 degrees, in gltf export if does not only say 30 degrees.
Screenshots
https://youtu.be/kkNUBM_1kqE
.blend file/ .gltf
If applicable, a zipped folder containing a .blend file for exporter issues and a .gltf file for importer issues. Please take care to include all resources, such as textures in the .zip file.
TestPlaneMSFS_Interior_LOD99.zip
Version
windows 10
Blender 2.93.4
Additional context
this issues started in branch on khronos version traced back to existing

Hello,
Please test again with a recent build. https://builder.blender.org/download/daily/
I think the issue is linked to way animation are mixed and should be fixed by #1433 + #1468
Before #1433, all bones has some keyframes, so the mix is done between 0 and keyframes (your angle)
Now, only animated bones has keyframes, so they is no mix between 0 and your angle.

Thanks will test - Is this also part of the ver 3.x cadidate?

No it did not work with 2.93.
TestPlane6-1_MSFS_v17_2935_test.zip
5

This is a recent change, not in any stable version. Please test with 3.0 alpha

Ok tested in ver 3.0 alpha 12e8c783535c.  The result is almost what I require. If I enable the two animation fore/aft and left/right then the displacement is 100% the same as blender.  However (and this may be a feature request) for MSFS (Microsoft Flight Simulator 2020) there is a third animation at to top of the stack. This is the rest position and it is the same position for and ALL the KF. The same location KF 0,1,2 all center straight up.  When I enable all three animation then the gltf viewer goes back to half deflection.  So there is still some calculation reducing it to approx 1/2 deflection.

Well, I don't think there is any issue in Blender now in your case.
This is the way animation are used (how there are mixed) by the viewer that is your problem. Currently, seems animation are mixed (using average), and you probably want it to be added

Thanks for all your help.  I guess we can close this issue.


Shift operators: emphasize the shift count logic

Fixes #16652

I think this should help, as it will make people more aware there is something else to read, which could be (is) important.


Themes command

Add at least 1 more theme

See https://github.com/CS2103AUG2017-W14-B1/main/pull/129 for more details


Permission issue

Hi, I use LuckPermsVelocity for the perms handling, I've set the permission osmc.send.send but when I do
/send player _Tbenatti_ Kingdoms it keeps saying You do not have permission to do that but I have the permission setted up

You need to open it's config and change     server-blacklist=false
to true so:
server-blacklist=true

Ok, is there any reload command or I need to restart?

restart dumbass

bruh

dont forget to close the ticket

I'm assuming that fixed it?


review only a specific deck

Hi,
first of all, I like your program so much. Simple, useful, minimal, very practical.
I wanted to know if there is a way to review a specific deck ?
When I use the review option, all the decks are in the review.
Maybe there is a way to get only the cards from a specific deck using a parameter like --deck-id <deck number> ?

Right now there isn't an easy way to review only a specific deck (the hard way would be to have a separate database for each deck and specify which database to use with --path path/to/database).
With my use for this program, I've found it to be simpler to review all decks at once, so it would be interesting to hear more about why or how you'd review one deck at a time. One thing that isn't clear is how you would decide which deck to review, since nothing exposes how many pending cards there are to review on a per-deck basis.

Hey ! Thanks for your answer :)
To be honest, the hard way will probably do the stuff.
I'm a japanese language learner at Uni, and on top of the classes, I also add some vocabulary that I found on some specialized books or some discoveries. Review all the cards from all the decks is really exhausting for me. It could take 3-4h to review all the decks regarding of all the cards in the whole collection (kanjis, vocabulary from diverse classes, specialized vocab, etc.).It is also difficult to switch from a specific deck with a specific thematic, and go for a mixed thematic from unexpected vocab from researches and discoveries. It makes it harder to memorize.
I will try the separated databases. But if you plan to add some options to have a single database and review a specific deck, it'll be marvelous !
But no matter what, good job for your work. I tried a lot of CLI-program, but yours is clear, efficient, minimalist, and enough simple in the creation of cards to be versatile, so thank you ! :)


AsyncQueryTestBase.Mixed_sync_async_query test still flaky?

While working on my EF.Core provider I ran into some weird issues with Mixed_sync_async_query test. After some experimenting it doesn't seem very trustworthy to me. For example it fails if I add .ToList() and run it against InMemory database
[ConditionalFact]
public virtual async Task Mixed_sync_async_query()
{
    using (var context = CreateContext())
    {
        var results
            = (await context.Customers
                .Select(c => new
                {
                    c.CustomerID,
                    Orders = context.Orders.Where(o => o.Customer.CustomerID == c.CustomerID)
                                    .ToList() /// <= HERE!
                }).ToListAsync())
                .Select(x => new
                {
                    Orders = x.Orders
                        .GroupJoin(new[] { "ALFKI" }, y => x.CustomerID, y => y, (h, id) => new
                        {
                            h.Customer
                        })
                })
                .ToList();

        Assert.Equal(546, results.SelectMany(r => r.Orders).ToList().Count);
    }
}

Assert.Equal() Failure
Expected: 546
Actual:   830

I went ahead a bit further and excluded the possible influence of asynchrony and also explicitly materialized the Orders collection in a separate step
[ConditionalFact]
public virtual void Mixed_sync_query()
{
    using (var context = CreateContext())
    {
        var list1
            = context.Customers
                .Select(c => new
                {
                    c.CustomerID,
                    Orders = context.Orders.Where(o => o.Customer.CustomerID == c.CustomerID)
                }).ToList();

        var list2 = list1.Select(x => new { x.CustomerID, Orders = x.Orders.ToList() }).ToList();

        var results = list2
            .Select(x => new
            {
                Orders = x.Orders
                    .GroupJoin(new[] { "ALFKI" }, y => x.CustomerID, y => y, (h, id) => new
                    {
                        h.Customer
                    })
            })
            .ToList();

        Assert.Equal(546, results.SelectMany(r => r.Orders).ToList().Count);
    }
}

and it still returns 830 rather than 546.
I have to confess I didn't check each and every line of data to prove that the test should expect 830 instead of 546, but also I can't imagine its original author doing such analysis. So for now my question is: How can one explain different results returned with and without .ToList() on the indicated position?
Further technical details
EF Core version: 2.0.0-preview1-final
Database Provider: Microsoft.EntityFrameworkCore.InMemory
Operating system: Windows 10
IDE: Visual Studio 2017

The fact that changing the test this way returns different results at first glance it looks like it could be the consequence of a bug somewhere.

This is a bug in product. The correct result is 830. We are caching the inner subquery incorrectly that in subsequent  runs of N+1 we are just reusing old results causing each customers to be associated with orders of first customer (ALFKI in this case which has 6 orders) hence 91 * 6 = 546 as answer.


tests: Bluetooth: tester: Do not memset the streams on ACL disconnection

The streams can be deallocated once bt_bap_stream_ops.released callback is called. Otherwise it may cause memory violation in the stack.
Fixes: ASCS/SR/ACP/BV-31-C

@MSEEHenrik FYI


Add back button to image viewer

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @Intellijence in #android-bugs.

Added. My beta


[Digital Twins] Migrate @azure/digital-twins-core to core-rest-pipeline

Packages impacted by this PR
@azure/digital-twins-core
Issues associated with this PR
#15816
Describe the problem that is addressed by this PR
Migrated the package to use core-rest-pipeline and test-recorder v2.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-digital-twins-core

I'm going to go ahead and merge this PR, but I'm happy to address any further feedback in a follow-up PR! 😄


SPARKC-169: Backport of SPARKC-8: Reading TTL and write time of regular columns

Cleanly cherry-picked the commit which fixed SPARKC-8

Created case classes for different kinds of columns
Changed the way the columns can be selected - select method now accepts SelectionColumn instead of String arguments
Updated JavaAPI for TTL and write time retrieval support
Updated and added test cases for TTL and write time retrieval support
Updated API docs
Applied reviewer's comments - merged ColumnSelection hierarchy into ColumnRef
Add extractor to NamedColumnRef and use it.

+1

+1, please squash

ok, thx


Clarifies and improves language in documentation

Although my previous PR (#469) on this topic was merged, it caused
quite a discussion about
the clarity of the language I wrote.
This commit seeks to clarify and improve the sentence under discussion.
Documentation should be as clear, precise, and unambiguous as possible.
Because I cannot know how a reader interprets my writing, I depend on
feedback to understand the quality of my prose. Therefore, suggestions
and conversation are welcome.

This PR seeks to improve the documentation based on the conversation about PR #469.

:+1::+1:
Much clearer, thank you.

Thanks! LGTM

Yeah :+1: from me too. Much clearer.

Alright, merging this one in, thanks @jfmercer and people who participated in the discussion! :)


Is there a way to call the Engine.scala as soon as the Recorder.scala is called in a java file.

[Help Needed]
I am a newbie in Gatling and trying to pick up the tool slowly.
I have created a maven project in scala IDE using the instructions mentioned in https://gatling.io/docs/2.3/extensions/maven_archetype/ . It works fine, both java and scala files are compiling and running successfully. The problem starts when i try using calling the recorder object and Engine object in a java file.
Problem 1: Maven throws error, when trying to call the scala objects in the java file. I think, i need to work in depth on this and might require more googling. But, if you could help me out with a pom file which does the execution of both scala and java files, would be very helpful.
Problem 2: I am calling stoprecording in the java file to stop the recording and generate the recorded scala file. But, the jvm is killed as soon as i have called the function. My objective is to start recording and stop recording and then once the recorded simulation is generated then run the simulation. All of these to be done from a java file.

Please use the community mailing list, not the bug tracker.
Then, the kind of help you're looking for is most likely consulting.


[BUG] how should i integrate with RouterProvider of React Router V6?

Describe the bug
i integrate with RouterProvider of React Router V6, and it report an error: You cannot render a  inside another . You should never have more than one in your app.
To Reproduce
ReactDOM.createRoot(document.getElementById('root') as HTMLElement).render(
  <React.StrictMode>
    <FronteggProvider contextOptions={contextOptions} hostedLoginBox={true} authOptions={authOptions}>
      <RouterProvider router={createBrowserRouter(Routes)}></RouterProvider>
    </FronteggProvider>
  </React.StrictMode>,
);

Screenshots

Hi @KaynRonan!
Can you please email us at<EMAIL_ADDRESS>with the details of your package.json or send a message in one of our community slack channels?
We will be happy to help you set this up via one of these communication channels.

Hi @KaynRonan!
Can you please email us at<EMAIL_ADDRESS>with the details of your package.json or send a message in one of our community slack channels?
We will be happy to help you set this up via one of these communication channels.

maybe you can try a demo with react-router v6，and then you can improve you docs tell developers how can we use frontegg with react-router v6.
your document does not provide any explanation about the react router, it simply refers to a  component internally

Thanks for the feedback @KaynRonan, we are actively working on improving our documentation and we'll take that into consideration! In case you'll need any help in the meantime, feel free to send us a message via one of the support channels.

The full solution for using react router v6 with @frontegg/react is described here - https://support.frontegg.com/hc/en-us/articles/11571585765789-How-to-use-React-Router-v6-with-Frontegg-

thx @MashaPav that article was super helper


bug: ./setupDB.sh script in Git Bash gives MODULE_NOT_FOUND error when Local Docker setup is chosen in Windows

Describe the bug
When Local DB with Docker is chosen for Database setup, I get the error, Error: Cannot find module 'D:\Code\100x\daily-code-main\node_modules\node_modules\prisma\build\index.js'
Since this error comes after Migrating DB log, this means it is produced by npx prisma migrate dev command.
Possible Solutions Tried:

Deleting node_modules
Reinstalling node js

To Reproduce
Steps to reproduce the behavior:

I am using Windows Machine
run ./setupDB.sh command inside Git Bash in rootDir/packages/db directory
Select Local DB with Docker Setup as config
An error saying Error: Cannot find module 'D:\Code\100x\daily-code-main\node_modules\node_modules\prisma\build\index.js' pops up.

Expected behavior
The project should run locally at the expected port.
Screenshots or GIFs

Info (please complete the following information):

Edge
Editor: VS Code

Additional context

Discord Chat on members facing similar issues

I am also facing the same issue right now, does anyone know the fix ?

replace npx with yarn inside your setupDB.sh

@iharsh02 thank you, I was also facing the same issue. now solved

hey guys 👋  after using the fix provided by @iharsh02, I found that this fix will only for an offline set-up of the project and will cause errors when using docker compose watch, so use this fix iff when setting the project offline.

do we need to install prisma separately


Cannot declare class Nexmo\Client, because the name is already in use

Expected behavior:
To be able to send out an sms via Nexmo/Vonage
Actual behavior:
I've just tried with Nexmo/Vonage, and in the recent failures tab in the automation I am getting the below

DATE
STATUS
ACTION
MESSAGE

43 seconds ago
Failed
--
Cannot declare class Nexmo\Client, because the name is already in use

--
--
--
--

Reproduce steps:
Add API settings of Nexmo/Vonage, and send out an SMS

This issue looks fixed. Closing, but please reopen if it still occurs.

This still exists unfortunately.
Regards

On Mar 3, 2022, at 4:37 PM, Sam Poyigi @.***> wrote:

This issue looks fixed. Closing, but please reopen if it still occurs.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

Just pushed a new release that drops laravel notifications and use SDK directly.