Second call of gpioSetTimerFunc doesn't work in some cases

Hi joan,
with the following test program I have a strange effect with pigpio v56:
#include <stdio.h>
#include <pigpio.h>

void Timer0()
{
	printf("Timer0 triggered\n");
}

void Timer1()
{
	printf("Stop timer0\n");
	gpioSetTimerFunc(0, 500, NULL); // deactivate timer0
	gpioSetTimerFunc(1, 2000, NULL); // deactivate timer1
}

int main() {
	if(gpioInitialise() == PI_INIT_FAILED)
	{
		printf("gpioInitialise failed!\n");
		return -1;
	}
	else
		printf("gpioInitialise o.k.\n");

	printf("1st trial\n");
	gpioSetTimerFunc(0, 500, Timer0);
	gpioSetTimerFunc(1, 2000, Timer1);
	gpioDelay(5*1e6);
	printf("2nd trial\n");
	gpioSetTimerFunc(0, 500, Timer0);
	gpioSetTimerFunc(1, 2000, Timer1);
	while(1);

	gpioTerminate();
	return 0;
}

output is
gpioInitialise o.k.
1st trial
Timer0 triggered
Timer0 triggered
Timer0 triggered
Timer0 triggered
Stop timer0
2nd trial
Timer0 triggered
Timer0 triggered
Timer0 triggered
Timer0 triggered
Timer0 triggered
Timer0 triggered
...

As you can see the 1st trial works without problems, but the 2nd call of gpioSetTimerFunc(1, 2000, Timer1); seems to have no effect (return value is 0). Timer1 is not called to stop Timer0.
Could you have a look on it?
Thank you.
absalom

It's definitely behaviour I would prefer not to happen so from that point of view it is a bug.
It's probably related to killing the timer within itself.  When I get time I'll look in more detail.  If it is easy to allow this action I will do so, if it isn't I'll probably just add a note to say don't kill a timer within a timer.
#include <stdio.h>
#include <pigpio.h>

void Timer0()
{
    printf("Timer0 triggered\n");
}

void Timer1()
{
    printf("Timer1 triggered\n");
    printf("Stop timer0\n");
    gpioSetTimerFunc(0, 500, NULL); // deactivate timer0
    //gpioSetTimerFunc(1, 2000, NULL); // deactivate timer1
}

int main()
{
    if(gpioInitialise() == PI_INIT_FAILED)
    {
        printf("gpioInitialise failed!\n");
        return -1;
    }
    else
        printf("gpioInitialise o.k.\n");

    printf("1st trial\n");
    gpioSetTimerFunc(0, 500, Timer0);
    gpioSetTimerFunc(1, 2000, Timer1);

    time_sleep(10);

    printf("2nd trial\n");
    gpioSetTimerFunc(0, 500, Timer0);
    gpioSetTimerFunc(1, 2000, Timer1);

    time_sleep(10);

    gpioTerminate();

    return 0;
}

$ sudo ./issue90
gpioInitialise o.k.
1st trial
Timer0 triggered
Timer0 triggered
Timer0 triggered
Timer0 triggered
Timer1 triggered
Stop timer0
Timer1 triggered
Stop timer0
Timer1 triggered
Stop timer0
Timer1 triggered
Stop timer0
Timer1 triggered
Stop timer0
2nd trial
Timer0 triggered
Timer0 triggered
Timer0 triggered
Timer1 triggered
Stop timer0
Timer1 triggered
Stop timer0
Timer1 triggered
Stop timer0
Timer1 triggered
Stop timer0
Timer1 triggered
Stop timer0
$

Okay, I have made a change which seems to work.  The following code/output shows the new behaviour.

Should be okay now in V57.

Thank you joan


mapCoverage true by default

feature request - set mapCoverage to true by default
What is the current behavior?
mapCoverage is false by default
What is the expected behavior?
mapCoverage to be true by default
I maintain a jest-vue preprocessor.
A lot of users have problems with source maps. They don't realize you need to tell Jest to use source maps in the coverage reporter, so they think it's a problem with jest-vue.
Is there a reason it's false by default? I would think Jest would use source maps in coverage reporters by default
I'm happy to make a PR to change this

Could I get some feedback on this? I'm happy to create a PR if you want to make this change 😀. @thymikee @cpojer

I'd rather ask @aaronabramov about that. Setting this to true by default could potentially make Jest slower for regular users.

I've had issues with mapCoverage fixing code coverage for vue, but it scrambles the code coverage for js files.  I've tried modifying script_transformer.js to only apply mapCoverage to .vue files, and that worked great (actually, better for vue files which were included only because of collectCoverageFrom).
I'm using<EMAIL_ADDRESS>@eddyerburgh have you experienced anything similar?  Currently I've worked around this by running jest twice with mapCoverage on for vue and off for js files but it would be nicer to be able to run jest once.

@sparecycles I've encountered this issue recently. I'll look into it

See #5177, mapCoverage has been removed as of 22.4.0, its behaviour being the default


Process more than 50 manufacturer seo urls

The SearchCriteria's limit property has to be set to NULL to process more than 50 manufacturer seo urls. :)

Couldn't you achieve the same results if you provide a high value for the limit, e.g. 9999?

What happens with the 10000st manufacturer? ;-)

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-19163.
Please use this issue to track the state of your pull request.


chore: add vxe-table export example

Description

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Checklist

ℹ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

[ ] If you introduce new functionality, document it. You can run documentation with pnpm run docs:dev command.
[ ] Run the tests with pnpm test.
[ ] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

vxe-table 导出功能依赖 VxeUI.saveFile 工具函数来下载文件，此工具函数在 VxeUpload 组件中才会挂载。所以必须导入 VxeUpload


Documentation Error

Hello, the documentation for Tenable and Varonis have spaces and capitalized letters in the index configuration code. Is this an error? When importing the index configurations under vendor_product_by_source.conf, the container fails.
Feb 16 07:57:05 servername docker[36247]: 100         host("Thycotic Software_Secret Server" type(glob))
Feb 16 07:57:05 servername docker[36247]: 101         #or netmask(xxx.xxx.xxx.xxx/xx)
Feb 16 07:57:05 servername docker[36247]: 102     };
Feb 16 07:57:05 servername docker[36247]: syslog-ng documentation: https://www.syslog-ng.com/technical-documents/list/syslog-ng-open-source-edition
Feb 16 07:57:05 servername docker[36247]: contact: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Feb 16 07:57:05 servername docker[36247]: [2022-02-16T12:57:05.857221] Error parsing filters of rule engine; filename='/etc/syslog-ng/conf.d/local/context/vendor_product_by_source.conf'
Feb 16 07:57:05 servername docker[36247]: [2022-02-16T12:57:05.857239] Error initializing message pipeline; plugin_name='add_contextual_data', location='/etc/syslog-ng/conf.d/enrich/vendor_product_by_source.conf:9:17'
Feb 16 07:57:06 servername docker[36247]: syslog-ng failed to start; exiting...
https://splunk-connect-for-syslog.readthedocs.io/en/latest/sources/Thycotic/
Sourcetype and Index Configuration
key	sourcetype	index	notes
Thycotic Software_Secret Server	thycotic:syslog	netauth	none
https://splunk-connect-for-syslog.readthedocs.io/en/latest/sources/Varonis/
Index Configuration
key	sourcetype	index	notes
Varonis Inc._DatAdvantage	varonis:ta	main

In vendor_product_by_source.conf there is a missing ; most likely prior to Thycotic_Software_Secret_Server

A ";" isn't missing. Tthe documentation online does not reflect Thycotic_Software_Secret_Server.
It has spaces and is reflected as Thycotic Software_Secret Server. I have to add the underscores to the sourcetype for sc4s to work properly.

Any update on this?

Sorry I lost track of this one.
Thycotic is CEF based so no need to use vendor_product_by_source
in splunk_metadata
Thycotic Software_Secret Server,index,newindex


How to extract I3D features on different span and stride

TSPNet/
├── i3d-features/
│   ├── span=8_stride=2
│   ├── span=12_stride=2
│   └── span=16_stride=2
├── data-bin/
│   └── phoenix2014T/
│       └── sp25000/
│
├── README.md
├── run-scripts/
└── test-scripts/
I want to extract i3d features on 3 different span (span = 8 _ stride= 2, span = 12_ stride = 2, span = 16 _ stride =2), how can I do this using your i3d feature extraction code. Can you please guide me?

https://iashin.ai/video_features/models/i3d/
I am not dure what you are referring to. Perhaps, span=stack_size; stride=step_size


Missing option name in icinga2_master/tasks/main.yml

In line 38 in icinga2_master/tasks/main.yml the name of the option is missing. Line 38 should be:
--database={{ icinga2_master__database_name | quote }}

No, just the order of the parameters is a bit stupid. The synopsis of the mysql command is mysql [options] db_name. I corrected the sort order to make it clearer.

Ok, thank you. My yaml-editor in eclipse reported an error in the file, so I thought, the option is missing. You are right, the '--database'-option is optional and with the changed order, the editor no longer shows an error.


local cache not working

Hey, I just started using lage. It runs my build just fine. But I get cache hit? false for every package. And I can't find how to debug it.
Any ideas?

@kenotron, can you please take a look. This regressed in #172. Reverting to 0.33.0 works.

I added outputGlob with the needed globs and it works :)
Now I want to try remote caching.
It would be amazing if you can improve the docs. Both in lage and in backfill the docs are a bit limited. Makes it hard to know exactly how to configure.
Thanks

@shaulgo - yes, admittedly, the docs ARE very lacking. I'm not happy at the state that it's in right now. But we've got something in the works! I frankly wasn't happy with v1's codebase in it's monolithic state, so went heads down for a refactor. I'm finished with that now, so I can concentrate on the docs - and improve on the "local cache doesn't work in zero-conf case"


[SPARK-42380][BUILD] Upgrade maven to 3.9.0

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

wait https://github.com/apache/spark/pull/40065

Need to wait for a stable CycloneDX version, close this first


Create Custom fields name issue

Hi,
Creating Custom Fields suggests that "name - The name of this field, in the form model that is posted to the server." Does this work as documented as the submitted value is not bound to the name value I'm setting in the model when looking formData in preRegistrationHandler's ?
With the following I see the value in preRegistrationHandler to be 'foo,' but I'd expect it to be 'bar'?
foo: {
  enabled: true,
  label: 'Test',
  name: 'bar',
  required: true,
  type: 'text'
}

Thanks,
Matti

Thanks for the report, we'll look into this.  It should be 'bar' as you expect.

@robertjd, I thought we changed it so the name field is no longer required, and is instead based on the property label like foo?
https://github.com/stormpath/stormpath-framework-spec/commit/01d8745bb46cea6b6f6204732e7d235b064f20cd#diff-38a8983f478dea556d71617301415c7f

According to spec it should be kept as it is.
@robertjd Any input here?

Correct, we did change this such that the name field is implied by the field definition property, I'm updating the docs in #453, @typerandom please review


How will Microsoft notify customers about a needed worker node reboot?

Hi,
This is stated in this article:
“When a security patch requires worker node reboots, Microsoft will notify customers of this requirement.“
Who is notified and how?
Regards Peter

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

ID: 36ecef62-68f2-9e81-f4b6-da2b49d1a653
Version Independent ID: a6c2c35a-8a12-a9de-0a4e-669cf8506892
Content: Support policies for Azure Kubernetes Service (AKS)
Content Source: articles/aks/support-policies.md
Service: container-service
GitHub Login: @jnoller
Microsoft Alias: jenoller

Thanks for the question. We are currently investigating and will update you shortly.

Related comment in another issue https://github.com/MicrosoftDocs/azure-docs/issues/35195#issuecomment-511754085
@theheatDK After applying patched to the node, AKS created a file /var/run/reboot-required.
Other than that , I am not aware of any notification process. I will check with the team and update you

@jnoller @jluk Please add your comments

@theheatDK I checked with my team.
Currently no  notifications will be send other than the file creation which is happening inside the server.
We can achieve notification by various means. Easiest way is to deploy a daemon set which will check the files existence and notify if its there.
My team suggested a Medium article written by Dennis Zielke, which you can use as a starting point. In that article author used a daemon set to find the files existence and then writing a message in console. Later the author is using log analytics to created a dashboard. We can use the same log analytics alert to trigger a alert as well.
There is an existing feedback item here https://feedback.azure.com/forums/914020-azure-kubernetes-service-aks/suggestions/38173222-addon-for-automatic-reboot-of-nodes which is related to the rebooting of AKS nodes.
You can upvote there or create a new one herehttps://feedback.azure.com/forums/914020-azure-kubernetes-service-aks
Product teams look into these feedback and review them.
You can also submit a feedback in

@theheatDK
I will close this out for now. If you need additional help please let me know and we can reopen and continue.

Thanks @jakaruna-MSFT,
Maybe somebody should update the documentation since it is currently wrong :-)
Regards Peter

Assign this issue to me. /var/run/reboot-required is only for operating system security updates, not AKS cluster, kubernetes, or other updates. Those notifications are sent via Portal notification, the AKS release notes, etc.
I will clarify the wording

Hi @jnoller ,
Is there any "/var/run/reboot-required" équivalent for Windows nodes requiring a reboot ?
I thnik the whole reboot responsibilty problem is same for Windows nodes, isn't it ?

Hi @jnoller,
Do you still plan to clarify the wording in the article or should I close it? :-)
Regards Peter

Please clarify how the customer will be notified? Also, please update the document.

@theheatDK thank you for your feedback!
@jnoller added updated wording here in the note:
https://docs.microsoft.com/en-us/azure/aks/support-policies#microsoft-responsibilities-for-aks-worker-nodes
#please-close


Not executing the command in second window

While executing the commands("ds.clean-slate()") that you written in demo section of window 2, I am getting the following error:
The given ECU is not in this Primary's list of known Secondary ECUs. Register the ECU with this Primary first.">
can you tell me the possible solution. As well which is stable release, and how to build your package effectively?

It looks like you're running the Secondary before running the Primary.  The second window in the demo is the Primary.

Hi,
Thanks for your reply @awwad
And we were able to build and run the demo, but I have few questions:

How to update primary itself?
How to push new image to image repository?
How to add multiple secondary ECUs to same vehicle and update it?

See #174.


Configuration option is not described in help options

When running phinx without commands or when running the help (-h|--help) command it does not mention the --configuration option as described here: http://docs.phinx.org/en/latest/configuration.html .

It's defined at the sub commands


Repeated xmlns in html.php view layout

Hi,
dektrium\views\mail\layouts\html.php
has duplicated xmlns declaration:
<html xmlns="http://www.w3.org/1999/xhtml" xmlns="http://www.w3.org/1999/xhtml" style="font-family: 'Helvetica Neue', 'Helvetica', Helvetica, Arial, sans-serif; font-size: 100%; line-height: 1.6; margin: 0; padding: 0;">
This does not parse through loadHTML of a DOMDocument while sent through PHPMailer.

Thank you, fixed now!


How do you ensure that the comparisons are fair?

Hello, this work is wonderful. However, I have one question: How do you ensure that the comparisons are fair? Data leak may occur if some of the models use the train/test data for pretraining or finetuning, particularly for new models to submit.

Yeah, we mention that in the paper, where for Reranking MPNet & MiniLM perform very well likely due to SciDocsRR being part of their training data.
However, in the limit, i.e. the more datasets are benchmarked, this effect becomes negligible. So our solution is to just benchmark on a lot of datasets & samples.
Even if one were to adversarially train a model on all benchmarked test datasets, I think it would be hard to achieve a great score due to the variety of datasets & evaluation regimes.

@huangshenno1 seems like this answers your question I will close this issue for now.


 See documentation.

:robot: Release is at https://github.com/wholesome-ghoul/allaround-configs/releases/tag/configs-webpack-v1.6.0 :sunflower:


Is reset supported?

Hi, I want to do git reset --hard with go-git but I can't find any info. Is reset command supported? If not, are there any workarounds?
Thanks!

I don't think reset is implemented now. Still welcome to see if there is a workaround but I'm closing this issue now.


Bug in version check; does not detect e.g. 2.13.3

Some vulnerable versions, like log4j-core 2.13.3, are not found.
The version check, (major == 2 && minor <= 14 && patch <= 1), is wrong. It should be (major == 2 && (minor < 14 || (minor == 14 && patch <= 1))).

OMG.. Thank you for bug reporting!

@csemrau Released v1.1.1. May I close this issue?

That release works for me. Thanks for the quick fix! And thanks for the scanner itself! ❤


searching for phrases...

Is such a thing(e.g. Son of Man) possible at all with this app?  If so, how can it be done?  If not, will such a feature be implemented for this app in future versions?

Yes, use /<phrase>. Example:
kjv /Son of Man

I'll give it a try.  It works!  Thanks for such an awesome app!


server: support cluster_version

Signed-off-by: qupeng<EMAIL_ADDRESS>What problem does this PR solve?
PD distributes cluster version to TiKVs. So that TiKV can do some special things when rolling update.
Check List
Tests

Unit test

Side effects
Release note

No release note.

/merge


Text optimization website (user friendly)

I don’t know who is responsible for the texts on
The website. The point 01 is pretty complicated for most of the people. Where can be submitted a suggestion for optimization? Best Jan
![9C915304-7F4A-4C03-9726-300AF1FFC52D](https://user-images.githubusercontent.com/8312244/85177706-ea036000-b27c-11ea-99bd-088158089e98.jpeg

Here is the source of this section.
https://github.com/corona-warn-app/cwa-website/blob/master/src/data/index_de.json#L31-L36


Dapr build flavors.

Description

Separate unit tests into a separate job and runs on Linux only (can change if needed).
Builds flavors of Dapr sidecar for Linux builds only.

See example of a successful run in https://github.com/artursouza/dapr/actions/runs/4812847523
Issue reference

Please reference the issue this PR will close: #3168
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

@artursouza JFYI. Now, the debug of dapr in local fails for me with:
Starting: /home/deeagarwal/go/bin/dlv dap --listen=<IP_ADDRESS>:40207 --log-dest=3 from /home/deeagarwal/dev/daprDev/march/dapr_11/cmd/daprd
DAP server listening at: <IP_ADDRESS>:40207
Build Error: go build -o /home/deeagarwal/dev/daprDev/march/dapr_11/cmd/daprd/__debug_bin -gcflags all=-N -l .
package github.com/dapr/dapr/cmd/daprd
	imports github.com/dapr/dapr/cmd/daprd/components: build constraints exclude all Go files in /home/deeagarwal/dev/daprDev/march/dapr_11/cmd/daprd/components (exit status 1)

I changed directory to cmd/daprd/components and removed first line from all files: sed -i '1d' *
Then, I was able to debug

May be I should have provided some build tag for new options possible

You need to add the all_components tag in your debug command.


fix: [M3-7256] - Added spacing for Hively external link

Description 📝
Feedback Smiley Ratings should be easily clickable, however it overlaps with the "How did I do?" link
Changes  🔄

margin is overwritten due to being in a Stack, so switching to padding which is the more better approach.
Added Storybook

Preview 📷

Before
After

How to test 🧪
Prerequisites

Run storybook yarn storybook

Reproduction steps

Go to http://localhost:6006/?path=/docs/components-hively--documentation

Verification steps

Observe that there's no more overlapping happening in component

As an Author I have considered 🤔
Check all that apply

[x] 👀 Doing a self review
[x] ❔ Our contribution guidelines
[x] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[x] 🧪 Providing/Improving test coverage
[x] 🔐 Removing all sensitive information from the code and PR description
[x] 🚩 Using a feature flag to protect the release
[x] 👣 Providing comprehensive reproduction steps
[x] 📑 Providing or updating our documentation
[x] 🕛 Scheduling a pair reviewing session
[x] 📱 Providing mobile support
[x] ♿  Providing accessibility support

@mjac0bs What browser / version are you using? I'm on Chrome - Version 117.0.5938.149 (Official Build) (arm64)

@mjac0bs What browser / version are you using? I'm on Chrome - Version 117.0.5938.149 (Official Build) (arm64) !

Hmm, the same, it appears: Version 117.0.5938.149 (Official Build) (arm64).

@bnussman-akamai that would require a refactor of Link. I will create a separate ticket / PR for this.


[CONTRACT] setup liquidity addition

Complete this issue according to this article: How to manage liquidity in a P2P ramping app

Please add integration tests

@0xChqrles i

Hi @0xChqrles, an i work on this?

Hi @0xChqrles Can i work on this issue if it's available?

Hey @0xChqrles I would like to work on this so I can work on #67 which is a dependant.

@0xChqrles, can I work on this?

@0xChqrles am available to work on this ,
With previous experience working on this codebase,
I have read the article
I can implement this with 3 days
ETH: 72hrs

@0xChqrles am available to work on this


Ability to auto-import from nested folders

Acknowledgement

[X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment
I recently switched from a simple NextJS project to a monorepo and because of that all my shareable code as been split into the packages folder meaning that I now have a components folder, a utils folder and so on.
Now I'm trying to auto-import some of my utils functions in my components files. The thing is that I get no suggestion. However, if write the path by hand it works.
For example I can do this:
import { tailwindBreakPoints } from "@company/utils/src/lib/tailwind/getTailwindConfig".
Now, if I comment out this line and try to auto-import tailwindBreakPoints, I'll have no suggestion.
If I understood correctly everything I read online (sorry I'm new to npm packages), there are only 2 solutions to fix my problem:

Create an index.ts at the root of my utils folder and export every file from here
Add the exports property inside the utils package.json and export all of my folders and subfolders from here

The thing is that, I would rather not do any of those 2 solutions because doing all of this work by hand for every folder I have would take me days of manual exports.
So is there a way to auto-import directly from nested folders ?
Structure of the utils folder and any folder I have inside packages:
/utils
-- package.json
-- tsconfig.json
-- /src
---- all of my previous code (files, folders, nested folders)

Auto-import doesn't directly care about folder structure. It's likely the target file isn't part of the project already. Please log a full repro.

As a repro you can:

Clone the basic example of Turborepo: https://github.com/vercel/turbo/tree/main/examples/basic
Go in the ui package
Create a src folder
Move the card.tsx file inside the src folder
Delete the index.tsx file
Now in the web or doc  app, try to auto-import the Card component. You'll have no suggestion


OutputMapOfObjects throws "Type switching to map[string]interface{} failed." when output objects contain values of type list

I have a test which grabs a Terraform output which is a list of objects (Azure public IP addresses).
output "public_ip_addresses" {
  value = azurerm_public_ip.all
}

The referenced resource azurerm_public_ip.all contains the for_each argument, so the output is a list of objects. So terraform output -json public_ip_addresses would give something like
{
  "pip1": {
    "allocation_method": "Static",
    "availability_zone": "2",
    "domain_name_label": null,
    "fqdn": null,
    "id": "/subscriptions/someguid/resourceGroups/example/providers/Microsoft.Network/publicIPAddresses/pip-example-1",
    "idle_timeout_in_minutes": 15,
    "ip_address": "<IP_ADDRESS>",
    "ip_tags": null,
    "ip_version": "IPv4",
    "location": "westeurope",
    "name": "pip-example-1",
    "public_ip_prefix_id": null,
    "resource_group_name": "example",
    "reverse_fqdn": null,
    "sku": "Standard",
    "sku_tier": "Regional",
    "tags": {
      "foo": "bar"
    },
    "timeouts": null,
    "zones": [
      "2"
    ]
  },
  "pip2": {
    "allocation_method": "Static",
    ...etc...
  }
}

I have a unit test that tries to retrieve this output in a useful form using
tfOutput := terraform.OutputMapOfObjects(t, terraformOptions, "public_ip_addresses")

But it throws an error "Type switching to map[string]interface{} failed."
This seems to happen at the point it tries to parse the zones property of the first object in the map, as it is a list: https://github.com/gruntwork-io/terratest/blob/cb603f158b50492e429b17ea17bbbb1399a68a73/modules/terraform/output.go#L62

Do you know of any work-around to validate a map content if it happens to contain a list?

It's not a great workaround, but I just added new outputs to my Terraform confirm which effectively return only the map properties I'm interested in (which happen not to be those of list type in my case).

Facing the same issue in my case also. I have an output file with the list of data disk names of the linux_vm module. Any help, please.

Just stumbled into the same issue. We will also workaround with a separate output but it's not what I would have preferred

Just ran in to this as well


Instarepl Hoplon file

Hi,
I've revised my issue.
I just looked in  Nightlight/src/cljs/nightlight/editors.cljs, and see that Nightcode has provision for processing Hoplon files (.hl).
Nightlight appears to be instarepl'ing my cljs files but, doesn't offer the Instarepl switch option for my hoplon code.
I am getting to grips with these tools and, just now, managed to see my first clojurescript instarepl!
Regards,

Would it actually be possible to do this? I thought hoplon files had special implicit requires that normal clojure files didn't. In that case, anything using those requires would fail in the instarepl.

I hope that this is the short answer, from the hoplon wiki, "How is a hl file different?":
A .cljs.hl file is almost the same as a .cljs file. There are two differences:
The .cljs.hl file includes the hoplon and javelin namespaces. And
It can optionally begin with a page form rather than a ns form.

The hoplon compiler uses the page form to know how to make the html files and such. When the hoplon compiler compiles a .hl file into an html file and a cljs file, it only reads the first form (the page declaration). The rest of the file is left as-is, hoplon doesn't even look in there.
The conversion from .hl -> .cljs just involves adding (:require [javelin.core :refer [cell ...]]) and (:require-macros [javelin.core :refer [cell= ...]]) to the ns declaration, because cljs itself doesn't support (:require [javelin.core :refer :all]).
Is the javelin.core reference the implicit require that you speak of?
I shall try this code change in my project and see the effect but, I post this in case it is of use to you, even in assisting me!

Yep that's the implicit require. Right now the instarepl will fail since it doesn't require those functions and macros.

I think for now I have to close this until I can think of a simple way of implementing it.


[Feature Request]: Implement logger or use existing logging library?

Contact Details
No response
Feature Request
Having one central library to use for all serverless lambda logging makes sense for us but could this library be a wrapper for another external library? Does a library already exist which has all the functionality we require.
For example: LambdaLog
Are you currently using a workaround / alternative solution instead?
Currently using logger based from lambda-starter which has been adapted to work with SQS.

Just to throw an external example in the mix: Winston. I imagine looking at the stats it's the most widely used logger in JS. I have also used Pino before which was pleasant and simplistic.
For Winston, the methods are pretty much like-for-like with our current interface, to use it seems straightforward:
const winston = require('winston');

const logger = winston.createLogger({
  format: format.json(),
  transports: [
    new transports.Console({
      format: format.combine(
        format.colorize(),
        format.simple()
      )
    })
  ]
});

logger.info('Log this message to the console');

Winston looks good! Looks like it covers what we already have plus a lot more. I like this for use with reference id's as "child" loggers.

You can create child loggers from existing loggers to pass metadata overrides:

const logger = winston.createLogger({
  transports: [
    new winston.transports.Console(),
  ]
});

const childLogger = logger.child({ requestId: '451' });

Pino looks good too but seems to be more focussed on web frameworks so might not be as extensible as Winston.
We might be at the point of adding one in CPMS, currently leaning towards Winston. Does anyone have any experience with either they can comment on or prefer one over the other?
For Winston, add  🚀
For Pino, add  🎉
Neither, add  😕


Add third parameter's sortByKeysParameter to Arr::only

Haven't third parameter
$array = ['size' => 10, 'name' => 'Desk', 'price' => 100, 'orders' => 10];
$array = Arr::only($array, ['name', 'price', 'size']);

array:3 [
  "size" => 10
  "name" => "Desk"
  "price" => 100
]

Have third parameter
$array = ['size' => 10, 'name' => 'Desk', 'price' => 100, 'orders' => 10];
$array = Arr::only($array, ['name', 'price', 'size'], true);

array:3 [
  "name" => "Desk"
  "price" => 100
  "size" => 10
]

collect([
    'size' => 10,
    'name' => 'Desk',
    'price' => 100,
    'orders' => 10,
])->only(['name', 'price', 'size'])->sortKeys()->all();
// [
//     "name" => "Desk",
//     "price" => 100,
//     "size" => 10,
// ]

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

@derekmd It's not sort by a-z, actual it's sort by the second parameter's keys.
For example:
$array = ['orders' => 10, price' => 100, 'size' => 10, 'name' => 'Desk'];
$array = Arr::only($array, ['size', 'name', 'price'], true);

array:3 [
  "size" => 10
  "name" => "Desk"
  "price" => 100
]


[ci]: WinGet publish action failed

Dev Home version
No response
Windows build number
No response
Other software
N/A
Steps to reproduce the bug
See - https://github.com/microsoft/devhome/actions/runs/10908161759/job/30273488330
A contributor submitted a PR for the latest version, but we should fix the action for future release runs
Probably a case of incorrect/expired token?
Expected result
PR submitted to microsoft/winget-pkgs
Actual result
Action run failed
Included System Information
No response
Included Extensions Information
No response

Duplicate of #2967


Check Android server version

These commits replace the RenderDoc server if it doesn't match the version of the RenderDoc host.

The first commit changes the versionCode and versionName of the RenderDocCmd.apk.  Rather than hard code them in AndroidManifest.xml, assign them as part of the build process.  The versionCode must be an integer that increments for newer versions, so it becomes ${RENDERDOC_VERSION_MAJOR}${RENDERDOC_VERSION_MINOR} .  The versionName is a string, so for development builds, it becomes a matching hash of the RenderDoc build, ${GIT_COMMIT_HASH}.  For stable builds, it becomes the ${RENDERDOC_VERSION}.  These values match what the host components are assigning.

The second commit checks the value at runtime to determine if the server is compatible with the host.  If it doesn't, uninstall and allow the clean install logic to kick in.

This prevents one of the common crashes I get when working on RenderDoc.
We also need to check the layer's implementationVersion, but I'd like to bounce some ideas around before I work on that.

Adding @michaelrgb for Android coverage, feel free to add others.

Looks good to me, I will wait for :+1: from @michaelrgb then merge.

The version checking worked fine for me.
This is slightly unrelated, but I only noticed this after the version checking kicked in: I was building from source in 64bit mode (to get the 64bit layer), and I had to modify this line:
adbInstall = adbExecCommand(deviceID, "install -r --abi armeabi-v7a " + serverApk).strStdout;
Is it necessary to specify the ABI after you have found the apk location? It is only built with either 32bit or 64bit .so files, so maybe the --abi can be removed.

So that's interesting.  When you build locally, whatever you specify as ABI gets packaged into the APK.  So even though we've established that 32-bit is fine for the server, it wasn't built due to the make system in use, which only builds one ABI at a time.
That whole switch statement in the code is designed to support an APK that has both 32-bit and 64-bit libs for a given arch, but we select 32-bit for installation.  If we allow the APK's contents to dictate whether we support the platform, we can just check for failure of the install.  I'd want to test that on a few other platforms, but we can probably reduce the complexity of that code quite a bit.

FWIW, trying to debug 64-bit apps unearths some other problems.  For instance, when I try to push the Vulkan layer to an arm64 app, the /data/data/<package>/lib/ path does not exist.
If we're going to support 64-bit (which I wholeheartedly support) we'll want to do some better testing.


Foes can still ping you in chat even if you can't see what they write

Nothing much else to say:
When you have someone foed, if they write your name you will still get the ping message, but their message is missing, which is intended. These messages should not ping the user.

I think we got that issue somewhere already but yeah good catch

Fixed in #2015


[RFE] Fix vSphere CSI images installed by default

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Fix CSI default images! The image versions for the CSI driver we install in association with kubernetes versions is backwards. 2.7.0 supports k8s 1.23-1.25 but we are installing driver 2.5.2 by default.
Describe the solution you'd like
A clear and concise description of what you want to happen.
We should be installing the latest CSI driver image that supports kubernetes 1.25 / latest by default, with the options in values.yaml to install other images if the kubernetes version is not latest
Checklist for items that need completed

[ ] Update Image-mirror repo
[ ] Update manifests in rancher/vsphere-charts
[ ] Verify Slack hook notified about chart "release" in relevant channels
[ ] Update chart in rancher/charts
[ ] Update chart in rancher/rke2-charts (RKE2 team)
[ ] Updated RKE2 to consume new chart (RKE2 team)

SURE-6083

Testing will be covered while testing this issue here. Testplan can also be found here. 41017

This has been an outstanding issue for a while and a fix has been included in @brandond's PR https://github.com/rancher/vsphere-charts/pull/55 to set CSI/CPI default cloud controller images to latest to make it obvious when version overrides are not working properly.


Update dependencies

npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142

node_modules/jsdom "version": "15.2.1" depends on<EMAIL_ADDRESS>which depends on those old libraries above.
$ npm audit
# npm audit report

ansi-html  *
Severity: high
Uncontrolled Resource Consumption in ansi-html - https://github.com/advisories/GHSA-whgm-jr23-g3j9
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/ansi-html
  webpack-dev-server  2.0.0-beta - 4.1.0
  Depends on vulnerable versions of ansi-html
  Depends on vulnerable versions of chokidar
  Depends on vulnerable versions of yargs
  node_modules/webpack-dev-server
    @angular-devkit/build-angular  0.8.8 - 13.0.0-rc.3
    Depends on vulnerable versions of webpack
    Depends on vulnerable versions of webpack-dev-server
    node_modules/@angular-devkit/build-angular

ansi-regex  >2.1.1 <5.0.1
Severity: moderate
 Inefficient Regular Expression Complexity in chalk/ansi-regex - https://github.com/advisories/GHSA-93q8-gq69-wqmw
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/angular-playground/node_modules/ansi-regex
node_modules/angular-playground/node_modules/string-length/node_modules/ansi-regex
node_modules/jest-junit/node_modules/ansi-regex
node_modules/string-length/node_modules/ansi-regex
node_modules/webpack-dev-server/node_modules/cliui/node_modules/ansi-regex
node_modules/webpack-dev-server/node_modules/string-width/node_modules/ansi-regex
node_modules/webpack-dev-server/node_modules/wrap-ansi/node_modules/ansi-regex
node_modules/wide-align/node_modules/ansi-regex
  pretty-format  20.1.0-alpha.1 - 25.0.0
  Depends on vulnerable versions of ansi-regex
  node_modules/angular-playground/node_modules/pretty-format
    jest-config  20.1.0-alpha.1 - 24.9.0
    Depends on vulnerable versions of @jest/test-sequencer
    Depends on vulnerable versions of jest-jasmine2
    Depends on vulnerable versions of pretty-format
    node_modules/angular-playground/node_modules/jest-config
      @jest/core  <=25.5.4
      Depends on vulnerable versions of @jest/reporters
      Depends on vulnerable versions of jest-config
      Depends on vulnerable versions of strip-ansi
      node_modules/@jest/core
      node_modules/angular-playground/node_modules/jest-cli/node_modules/@jest/core
        angular-playground  5.8.0 - 7.1.1
        Depends on vulnerable versions of @angular-devkit/schematics
        Depends on vulnerable versions of @jest/core
        Depends on vulnerable versions of jest
        node_modules/angular-playground
        jest-cli  20.1.0-alpha.1 - 25.0.0
        Depends on vulnerable versions of @jest/core
        Depends on vulnerable versions of jest-config
        Depends on vulnerable versions of jest-validate
        Depends on vulnerable versions of yargs
        node_modules/angular-playground/node_modules/jest-cli
          jest  24.2.0-alpha.0 - 24.9.0
          Depends on vulnerable versions of jest-cli
          node_modules/angular-playground/node_modules/jest
      jest-runner  21.0.0-alpha.1 - 24.9.0
      Depends on vulnerable versions of jest-config
      Depends on vulnerable versions of jest-jasmine2
      Depends on vulnerable versions of jest-leak-detector
      node_modules/angular-playground/node_modules/jest-runner
        @jest/test-sequencer  <=24.9.0
        Depends on vulnerable versions of jest-runner
        node_modules/angular-playground/node_modules/@jest/test-sequencer
      jest-runtime  20.1.0-alpha.1 - 25.0.0
      Depends on vulnerable versions of jest-config
      Depends on vulnerable versions of jest-snapshot
      Depends on vulnerable versions of jest-validate
      Depends on vulnerable versions of yargs
      node_modules/angular-playground/node_modules/jest-runtime
        @jest/reporters  <=26.4.0
        Depends on vulnerable versions of jest-runtime
        Depends on vulnerable versions of node-notifier
        Depends on vulnerable versions of string-length
        node_modules/@jest/reporters
        node_modules/angular-playground/node_modules/@jest/reporters
        jest-jasmine2  20.1.0-alpha.1 - 24.9.0
        Depends on vulnerable versions of jest-each
        Depends on vulnerable versions of jest-matcher-utils
        Depends on vulnerable versions of jest-runtime
        Depends on vulnerable versions of pretty-format
        node_modules/angular-playground/node_modules/jest-jasmine2
    jest-diff  20.1.0-alpha.1 - 24.9.0
    Depends on vulnerable versions of pretty-format
    node_modules/angular-playground/node_modules/jest-diff
      jest-matcher-utils  20.1.0-alpha.1 - 24.9.0
      Depends on vulnerable versions of jest-diff
      Depends on vulnerable versions of pretty-format
      node_modules/angular-playground/node_modules/jest-matcher-utils
        expect  21.0.0-beta.1 - 24.9.0
        Depends on vulnerable versions of jest-matcher-utils
        node_modules/angular-playground/node_modules/expect
          jest-snapshot  20.1.0-alpha.1 - 24.9.0
          Depends on vulnerable versions of expect
          Depends on vulnerable versions of pretty-format
          node_modules/angular-playground/node_modules/jest-snapshot
            jest-resolve-dependencies  23.0.0-alpha.5 - 24.9.0
            Depends on vulnerable versions of jest-snapshot
            node_modules/angular-playground/node_modules/jest-resolve-dependencies
    jest-each  23.0.1 - 24.9.0
    Depends on vulnerable versions of pretty-format
    node_modules/angular-playground/node_modules/jest-each
    jest-leak-detector  21.3.0-beta.9 - 24.9.0
    Depends on vulnerable versions of pretty-format
    node_modules/angular-playground/node_modules/jest-leak-detector
    jest-validate  20.1.0-alpha.1 - 24.9.0
    Depends on vulnerable versions of pretty-format
    node_modules/angular-playground/node_modules/jest-validate
  strip-ansi  4.0.0 - 5.2.0
  Depends on vulnerable versions of ansi-regex
  node_modules/angular-playground/node_modules/string-length/node_modules/strip-ansi
  node_modules/angular-playground/node_modules/strip-ansi
  node_modules/jest-junit/node_modules/strip-ansi
  node_modules/string-length/node_modules/strip-ansi
  node_modules/webpack-dev-server/node_modules/cliui/node_modules/strip-ansi
  node_modules/webpack-dev-server/node_modules/string-width/node_modules/strip-ansi
  node_modules/webpack-dev-server/node_modules/wrap-ansi/node_modules/strip-ansi
  node_modules/wide-align/node_modules/strip-ansi
    cliui  4.0.0 - 5.0.0
    Depends on vulnerable versions of strip-ansi
    Depends on vulnerable versions of wrap-ansi
    node_modules/angular-playground/node_modules/cliui
    node_modules/webpack-dev-server/node_modules/cliui
      yargs  10.1.0 - 15.0.0
      Depends on vulnerable versions of cliui
      Depends on vulnerable versions of string-width
      node_modules/angular-playground/node_modules/yargs
      node_modules/webpack-dev-server/node_modules/yargs
        webpack-dev-server  2.0.0-beta - 4.1.0
        Depends on vulnerable versions of ansi-html
        Depends on vulnerable versions of chokidar
        Depends on vulnerable versions of yargs
        node_modules/webpack-dev-server
          @angular-devkit/build-angular  0.8.8 - 13.0.0-rc.3
          Depends on vulnerable versions of webpack
          Depends on vulnerable versions of webpack-dev-server
          node_modules/@angular-devkit/build-angular
    jest-junit  2.0.1 - 12.3.0
    Depends on vulnerable versions of strip-ansi
    node_modules/jest-junit
    ora  2.0.0 - 4.0.2
    Depends on vulnerable versions of strip-ansi
    node_modules/angular-playground/node_modules/ora
      @angular-devkit/schematics  9.0.0-next.0 - 9.0.7
      Depends on vulnerable versions of ora
      node_modules/angular-playground/node_modules/@angular-devkit/schematics
        @schematics/angular  9.0.0-next.0 - 9.0.7
        Depends on vulnerable versions of @angular-devkit/schematics
        node_modules/angular-playground/node_modules/@schematics/angular
    string-length  2.0.0 - 3.1.0
    Depends on vulnerable versions of strip-ansi
    node_modules/angular-playground/node_modules/string-length
    node_modules/string-length
      jest-watcher  <=26.0.0-alpha.2
      Depends on vulnerable versions of string-length
      node_modules/angular-playground/node_modules/jest-watcher
      node_modules/jest-watcher
    string-width  2.1.0 - 4.1.0
    Depends on vulnerable versions of strip-ansi
    node_modules/angular-playground/node_modules/string-width
    node_modules/webpack-dev-server/node_modules/string-width
    node_modules/wide-align/node_modules/string-width
      wrap-ansi  3.0.0 - 6.1.0
      Depends on vulnerable versions of string-width
      Depends on vulnerable versions of strip-ansi
      node_modules/angular-playground/node_modules/wrap-ansi
      node_modules/webpack-dev-server/node_modules/wrap-ansi

glob-parent  <5.1.2
Severity: high
Regular expression denial of service - https://github.com/advisories/GHSA-ww39-953v-wcq6
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/watchpack-chokidar2/node_modules/glob-parent
node_modules/webpack-dev-server/node_modules/glob-parent
  chokidar  1.0.0-rc1 - 2.1.8
  Depends on vulnerable versions of glob-parent
  node_modules/watchpack-chokidar2/node_modules/chokidar
  node_modules/webpack-dev-server/node_modules/chokidar
    watchpack-chokidar2  *
    Depends on vulnerable versions of chokidar
    node_modules/watchpack-chokidar2
      watchpack  1.7.2 - 1.7.5
      Depends on vulnerable versions of watchpack-chokidar2
      node_modules/watchpack
        webpack  4.44.0 - 4.46.0
        Depends on vulnerable versions of watchpack
        node_modules/webpack
          @angular-devkit/build-angular  0.8.8 - 13.0.0-rc.3
          Depends on vulnerable versions of webpack
          Depends on vulnerable versions of webpack-dev-server
          node_modules/@angular-devkit/build-angular
    webpack-dev-server  2.0.0-beta - 4.1.0
    Depends on vulnerable versions of ansi-html
    Depends on vulnerable versions of chokidar
    Depends on vulnerable versions of yargs
    node_modules/webpack-dev-server

json-schema  <0.4.0
Severity: moderate
json-schema is vulnerable to Prototype Pollution - https://github.com/advisories/GHSA-896r-f27r-55mw
fix available via `npm audit fix`
node_modules/json-schema
  jsprim  0.3.0 - 1.4.1 || 2.0.0 - 2.0.1
  Depends on vulnerable versions of json-schema
  node_modules/jsprim

node-notifier  <8.0.1
Severity: moderate
OS Command Injection in node-notifier - https://github.com/advisories/GHSA-5fw9-fq32-wv5p
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/angular-playground/node_modules/node-notifier
node_modules/node-notifier
  @jest/reporters  <=26.4.0
  Depends on vulnerable versions of jest-runtime
  Depends on vulnerable versions of node-notifier
  Depends on vulnerable versions of string-length
  node_modules/@jest/reporters
  node_modules/angular-playground/node_modules/@jest/reporters
    @jest/core  <=25.5.4
    Depends on vulnerable versions of @jest/reporters
    Depends on vulnerable versions of jest-config
    Depends on vulnerable versions of strip-ansi
    node_modules/@jest/core
    node_modules/angular-playground/node_modules/jest-cli/node_modules/@jest/core
      angular-playground  5.8.0 - 7.1.1
      Depends on vulnerable versions of @angular-devkit/schematics
      Depends on vulnerable versions of @jest/core
      Depends on vulnerable versions of jest
      node_modules/angular-playground
      jest-cli  20.1.0-alpha.1 - 25.0.0
      Depends on vulnerable versions of @jest/core
      Depends on vulnerable versions of jest-config
      Depends on vulnerable versions of jest-validate
      Depends on vulnerable versions of yargs
      node_modules/angular-playground/node_modules/jest-cli
        jest  24.2.0-alpha.0 - 24.9.0
        Depends on vulnerable versions of jest-cli
        node_modules/angular-playground/node_modules/jest

42 vulnerabilities (34 moderate, 8 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Fixed with PR #332


Multiple compound unique index support

@splio-aleroux added multiple compound index support, but forgot to enable it on unique indexes.

Thanks for this. 👍

I happen to run into some difficulties with this PR. The migration() works perfectly, it creates the expected SQL expression like this: UNIQUE KEY `key_name` (`col1`, `col2`).
But the validation doesn't seem to "understand" that kind of unique constraint. The validation fails as like the individual column was unique. Like col1 is unique and col2 is unique, not col1 and col2 is unique together.
I'll look into this issue later. Could somebody provide some feedback regarding this issue or is it just me?

Indeed, i haven't used this for unique index.


AV-214: Update showcase submit template form upstream to fix warning …

…about leaving form

Moved recaptcha script to form.js and switched recaptcha keys to dev keys.


Use exact versioning in package.json

Describe the bug
Exact versions should be used in package.json to avoid potential bugs by not-exact version upgrade of dependencies.

Hi @yulin-dong , can you provide an example for exact versioning?

https://github.com/ava-labs/avalanchejs/blob/master/package.json uses exact version, instead of ^

@yulin-dong Sorry for the delay. I'll look into it this week.

Thank you @meaghanfitzgerald


Support Fee-Bump Transactions

Please check the link for more information: https://developers.stellar.org/docs/glossary/fee-bumps/

I will add it here as a memo, will implement it later.


Changed k8s-extension creation flag

Changed from configuration-protected-setting file to --config-protected-file @ksurjan

#sign-off

#sign-off


Using st_x and st_y give the same value

Running this query gives me the same value for both st_x and st_y:
SELECT st_y(geom) as y, st_x(geom) as x FROM (SELECT st_point(14.919113688081065, 50.94247828919525) as geom)

If I switch, it's the x value that is returned:
SELECT st_x(geom) as x, st_y(geom) as y FROM (SELECT st_point(14.919113688081065, 50.94247828919525) as geom)

(Using the latest artefact in the CI)

Using DuckDB from R, version 0.8.0, and passing the query directly in SQL (not dplyr translation).
Extension from the latest macos CI run.

So the tests passed when merging #89, could you try if the issue persists with the artefact produced by that run?
https://github.com/duckdblabs/duckdb_spatial/actions/runs/5190312142

mmm... apparently I am unable to get to the latest version of the extension:

INSTALL 'path_to/spatial.duckdb_extension';returns 0 but it does the same if I put a wrong path
When I put manually the extension file in the duckdb folder, it seems to load it (I get an error when not allowing the unsigned extensions) but I still don't have the latest functions (e.g. ST_PointOnSurface)

Wanted to tray again now that the R package is 0.8.1 but still no luck loading the extension:
"version (v0.8.1-dev355) does not match DuckDB version (0.8.1)"

With the 0.8.1 update we also updated the spatial extension we distribute directly through duckdb, what happens if you do a 'INSTALL spatial' followed by 'LOAD spatial' now instead of trying to install it manually?

I started with that, the issue remains.
I guess I have the latest version of the extension, st_pointonsurface works.

You mean the original issue with x/y? Do you know if you can reproduce it through the duckdb cli? We run the exact query you provided as a test on the CI now and we've been passing on all platforms.
I cant really see how the r-client would change a function result and I dont have r installed myself on this computer, but I can try to give it a shot next week.


Add (revised) tests for Nolan's piecewise parameter rounding

Very similar to https://github.com/bsdz/scipy/pull/3, so _nolan_round_difficult_input was tweaked and the rounding tolerances were increased

x_tol_near_zeta from 0.005 -> 0.01
alpha_tol_near_one from 0.005 -> 0.0075
New tolerance: when alpha=1, round |beta| < 1e-12 to beta = 0 to avoid FP issues with extremely small beta

The tests from Nolan's PDF and CDF samples had to be tweaked for these changes to pass the tests.
Also, I added _nolan_S0_from_S1 and _nolan_S1_from_S0 helper functions to reduce more code repetition. These may be useful if we choose to allow user-level parameterization swapping.
Lastly, the ranges in the tests from https://github.com/bsdz/scipy/pull/3 were reduced, so they should be roughly twice as fast now.

This PR is no longer (completely) applicable after the switch to using S0 parameterization by default, so I'm closing this.
Regardless, it appears the rounding tests have been removed.


Define different views for the project.

In order to give shape to this project there's a need to define a few main views to reach an MVP

Here are some wireframes:
https://excalidraw.com/#json=jmAy54-u8ceKU8hsfemYU,OCL13-jER-FiXvzpKPDXXQ


Bring back pagination by (last_modified_at, id)

we reverted the change due to it not being backwards compatible (the migration to make last_modified_at NON-NULLABLE).
after next release, if customers run _backfill_last_modified_at, we can bring back the pagination change.
cc @asdfryan

Migrated to internal project management tool.


Update dashboard documentation for memory plot, fix #9433

[x] Closes #9433
[x] Tests added / passed
[x] Passes pre-commit run --all-files

Can one of the admins verify this patch?
Admins can comment ok to test to allow this one PR to run or add to allowlist to allow all future PRs from the same author to run.

ok to test.

I have updated few things in the documentation files, can you check again, and see if I can improve it more @ncclementi.

@jayeshmanani I think this looks great. I'd like to get a confirmation from @crusaderky or @jrbourbeau to make sure the description of the plot is accurate.
@charlesbluca I see a gpuCI failure can you confirm this is unrelated to this PR? It says "Aborted by user anonymous"

Looks like the build timed out and got marked as aborted from this log:
https://gpuci.gpuopenanalytics.com/job/dask/job/dask/job/prb/job/dask-prb/3198/console
rerun tests

@jayeshmanani It looks like you addressed all the comments suggested, I will wait for CI to finish and merge this in!

@jayeshmanani I noticed this is your first PR, horay 🎉
Thank you for the contribution, this goes in.

@jayeshmanani I noticed this is your first PR, horay 🎉
Thank you for the contribution, this goes in.

Yeah, It was @ncclementi , thank you very much. Looking forward to contributing more in future.


Fix #2631 and Fix #2632

I think this fix is not correct. Consider the following scenario.
transaction {
transaction {
}committed{
abort;
}aborted{
}
}committed{
}aborted{
}
Please correct me if I am wrong :)

No, Sameera. This is valid. in this case outer transaction has to aborted.


Updating MS Learn learning paths to Migrate

Updating direct links to supporting MS Learn learning path within the Migrate section of CAF in order to provide customers more specific guidance and direction on the topic of security and management. Part of our effort with Brian Blanchard to include learning path links which complement CAF guidance.

@scottburmester : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@scottburmester : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Resolved merge conflict.
@scottburmester Thanks for making the changes.
@JanetCThomas @BrianBlanchard Could you review the updated pull request and indicate whether it's ready to merge? Thank you.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@BrianBlanchard approved the updates in https://github.com/MicrosoftDocs/cloud-adoption-framework/pull/27/ and the requested edits were made by the contributor. It looks good to merge.


Migrate reviewDecision of Airlock Reviews

Resolves #3121
What is being addressed
Airlock reviews used to have one of these values: approval_in_progress and rejection_in_progress.
But since #2670 , instead of using these values, we use  approved and rejected,
This causes API type errors when trying to GET requests that have been created with older TRE versions, as these contain the older values.
How is this addressed

Added a DB migration to update each old value to it's updated version

/test

/test


Latest updates for Suricata PR

cf https://github.com/OISF/suricata/pull/11381
Also redo headers parsing to fix some quadratic complexity found by oss-fuzz https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68869

Looks good, thanks! Sorry for the delay merging.

Thanks for the merge Todd


'We conclude' sometimes too powerful ?

In this context:
x_mem: f x ∈ B ∪ B'
⊢ x ∈ f ⁻¹' B ∪ f ⁻¹' B'
Help suggest to use We conclude with x_mem.
We conclude with x_mem solves the goal.
For professional users it is ok, but I wonder if it is not too powerful for beginners ? in this exercise I wonder if the union should not be opaque.

Thanks Julien. This is a slightly tricky one that will require some library support. As you know, the goal is indeed definitionaly equal to x_mem. We can indeed redefine the union as opaque (or even irreducible is enough, no need to add axioms) using something like:
section SetUnion
irreducible_def SetUnion {X : Type*} (A B : Set X) := A ∪ B

/-- `a ∪ b` is the union of`a` and `b`. -/
infixl:65 (priority := high) " ∪ " => SetUnion

variable {X : Type*} {A B : Set X}

lemma mem_setUnion_of_mem_left  {x} (hxA : x ∈ A) : x ∈ A ∪ B := by
  rw [SetUnion_def]
  tauto

lemma mem_setUnion_of_mem_right  {x} (hxB : x ∈ B) : x ∈ A ∪ B := by
  rw [SetUnion_def]
  tauto

lemma mem_or_mem_of_mem_setUnion  {x} (hx : x ∈ A ∪ B) : x ∈ A ∨ x ∈ B := by
  rwa [SetUnion_def] at hx
end SetUnion

where the irreducible_def command from Mathlib creates both a irreducible definition and the corresponding SetUnion_def lemma. And then we override the union notation by giving ours a higher priority. We could also use the same trick with inverse image if you want to avoid students relying on its definition.
The tricky part is that after doing that the We proceed using x_mem tactic will no longer work. You would need We proceed using mem_or_mem_of_mem_setUnion x_mem. The obvious solution is to add a new category of anonymous lemmas to be used by We proceed. This is easy to do, but I have some administration work to do right now.


#[path = "xyz"] is failing

Hi all,
since the latest update, unresolved import errors show up when using the path attribute. This worked before.

A minimal reproducible example would be of help here, we do have some simple tests for path attributes in the repository, and them seem to work.

Sure.
Let me know if this works for you:
git clone git@github.com:rust-embedded/rust-raspberrypi-OS-tutorials.git
cd rust-raspberrypi-OS-tutorials/02_runtime_init
code .
# navigate to src/cpu.rs

We don't generate unresolved import errors, do we? :thinking: So I think these come from rustc?

Opening the example posted by @andre-richter above, I can confirm this error is coming from rustc. There is a cfg item one line above where the original screenshot starts which I think it relevant.
#[cfg(target_arch = "aarch64")]
#[path = "_arch/aarch64/cpu.rs"]
mod arch_cpu;
pub use arch_cpu::*;

I get the same error when running cargo check directly (while not on aarch64).
~/workspace/rust-raspberrypi-OS-tutorials/02_runtime_init master ·
$ cargo check
    Checking kernel v0.1.0 (/home/josh/workspace/rust-raspberrypi-OS-tutorials/02_runtime_init)
error[E0432]: unresolved import `arch_cpu`
  --> src/cpu.rs:10:9
   |
10 | pub use arch_cpu::*;
   |         ^^^^^^^^ use of undeclared type or module `arch_cpu`

I had hoped so. My attempt on it is here:
https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials/blob/master/02_runtime_init/.vscode/settings.json
Any errors there? I suspected this works, since it only recently started failing.

Ah yes, that is it. The settings names changed recently.
I believe you'll want rust-analyzer.checkOnSave.allTargets and rust-analyzer.checkOnSave.extraArgs now.

Thanks a lot for all your help!
I tried to rename those, but with the current rust-analyzer stable, it seems to have no effect.
If I update to nightly, the errors go away. But they also go away with the old config values. And even if some are missing. I am a bit confused at the moment.
But seeing that the next release might resolve this, I'll close for now.
In case it persists after next release, I'll reopen.


gha: use GH_RUNNER_EXTRA_POWER for conformance-k8s-kind workflow

Similarly to [1,2], use GH_RUNNER_EXTRA_POWER for the Conformance K8s Kind workflow.
[1]: 4bc5c06cf9d5 ("Use GH_RUNNER_EXTRA_POWER for CI image workflow")
[2]: bd675975d656 ("gha: make runner type for clustermesh workflows configurable")

/test


enum doesn't play well together with nullable

What version of Ajv are you using? Does the issue happen if you use the latest version?
v7.1.1, latest
Ajv options object
{
  strict: false,
  allErrors: true,
  ownProperties: true,
  passContext: true,
  useDefaults: true,
  validateSchema: true
}

JSON Schema
const schema = {
  "$id": "test",
  "properties": {
    "myEnum": {
      "type": ["string"],
      "nullable": true,
      "enum": [
        "one",
        "two",
        "three"
      ]
    }
}

Sample data
{
  "myEnum": null
}

Validation result, data AFTER validation, error messages
ERROR: [
  {
    keyword: 'enum',
    dataPath: '/myEnum',
    schemaPath: '#/properties/myEnum/enum',
    params: { allowedValues: [Array] },
    message: 'should be equal to one of the allowed values'
  }
]

What results did you expect?
nullable: true should affect the enum keyword validation.
We've been here before, see #824, but now that nullable is a keyword, let's revisit this question?
Are you going to resolve the issue?
I could try.

This is consistent with how OpenAPI treats nullable - as an alternative syntax to extend allowed types in "type" keyword, it has no impact on "enum" - null has to be added there explicitly.
You probably know that in JSON schema properties without type does not require that data is an object, just mentioning as the schema does not have type: object.
Please note that this is different in JTD that ajv now supports via a separate import (import Ajv from "ajv/dist/jtd") - nullable there actually extends the schema and the correct JTD schema that allows null is:
const schema = {
  "properties": {
    "myEnum": {
      "nullable": true,
      "enum": [
        "one",
        "two",
        "three"
      ]
    }
}

(and this schema requires that the data is an object).

Ok thank you for the explanations!


Feature Request: More Robust Multienv push

THE PROBLEM(s)

When using the multienv (beta) support, I've noticed that it is TOO easy to accidentally get into a situation where e.g. env X settings get pushed to env Y (if for example amplify init is skipped when changing branches).
As well, it is made worse by the fact that before confirming the amplify push actions, an Update operation could refer to either "patch existing resource" or "delete-and-recreate resource" (yikes!).
Finally, there isn't a general, ALL CAPS warning when any delete operation happens to existing auth resources.

IDEAL SOLUTION(s)

I think it is a fundamental limit of the approach of coupling the envs to a git branch. I don't have a ready solution for the current approach, but other tooling would be more like amplify push --env production. Maybe this could be an optional argument anyway, so the amplify command would validate the env matches what was requested and aborts otherwise?
Hopefully it is possible to differentiate an Update that is "patch" vs "recreate" and communicate that to the user, and/or print a complete list of the resources that will be changed (not just "auth" or "hosting"), and whether each resource existed already?
I think a basic, dumb warning (or extra confirmation prompt) would help prevent a future disaster, as well (if necessary) an argument like --no-delete-warning to allow automated use but still indicate to script authors what (may) happen.

One other issue, I think related to multienv design being based on git branches -- it makes it hard to do operations in parallel to different branches (e.g. "push-to-dev" and "delete-feature-sandbox" are things I'd like to do in parallel, to save time).

+1. This is related to my feature request of some kind of 'dry run' or preview support so that we know exactly what cloudformation is going to do. See https://github.com/aws-amplify/amplify-cli/issues/366

As a workaround, for the delete-and-recreate resource scenario, I'm thinking of just adding an IAM policy restricting the user amplify cli is running under to not be allowed to delete critical resources like Cognito userpools and Dynamo DB production databases. I have not done that yet but I assume that will work and be a good fail safe.

@paulreimer @hisham
I marked 'feature request' for this issue.
We are working to improve the user experiences of the amplify-cli, thank you very much for your feedbacks.


How to Setup Nginx RTMP With Load Balancing In Ubuntu

Hi I have more than one server
Main server, secondary server and additional server
I want to create load balancing to broadcast so that the load is not on the main server
How's that
Thank you

UP!!

I suggest you push only to the main server, then pull rtmp stream from main server. for HLS stream use http proxy_pass & proxy_cache.

@Lax is there any way you can provide an example nginx configuration that works for hls with support for low-latency chunk handling? I have been struggling to get this to work.


test getInvokeEstimateFee

Motivation and Resolution
Requested in https://github.com/0xs34n/starknet.js/issues/589
...
RPC version (if applicable)
...
Usage related changes
N/A
Development related changes
N/A; SDK test
Checklist:

[X] Performed a self-review of the code
[X] Rebased to the last commit of the target branch (or merged it into my branch)
[X] Linked the issues which this PR resolves
[ ] Documented the changes in code (API docs will be generated automatically)
[X] Updated the tests
[ ] All tests are passing

Multiple linting issues fixed suggested
Updated, thanks!

LibraryError: 20: Contract not found when test run: You can't ping random address
So create a contract and deploy, then test that? 🤔

You are testing that method is called but you called it with rpcProvider.getInvokeEstimateFee unnecessary test
It's testing getInvokeEstimateFee by checking that fetchEndpoint is called with parameter starknet_estimateFee.

You do not test the execution of this method nor its functional or execution response.
Suggestions on how to test this?

Closing this because the underlying code has undergone significant changes. Ask in the corresponding issue if you want to make another attempt.


Voice fixes, better API adherence, bitrate control, documentation

Control over Encoder send rate in Voice. Default is 128kbps.

Way better documentation for the new Audio control structs. Additionally, clients can now see the current position within each track (modifying this currently serves no purpose).

Raw Opus frame streams are now mixed into the multitrack output.

Mainly changes and adds OpCodes and Events which govern communication with the Discord Voice API. This includes soft checks for heartbeat ACK, as in #270. These SHOULD now match the docs, and reflects the fact that we are awaiting both a Hello AND a Ready at connection initialisation. I've added the OpCodes around Resume/Resumed, but there is no code to make use of these. I did need to rename/rework a lot of the voice OpCodes to match the spec, be advised.

Fixes to silent frames.

All the changes should have been made, unless I've accidentally missed something. Thanks for the advice on some of the more useful idioms.

Cherry-picked and retargeted for the new branch.

Travis failure looks legit

A bunch of these would probably benefit v0.5.x -- the first fix, Audio docs etc. I could split some out in the mean time if that'd help.

lgtm, this can be split if you'd like or we can just merge it now?

Thanks


Standardize header file suffix to *.h

We seem to have mixed use of .h and .hpp, and I think it might be good to standardize.  Was thinking of changing these files:
./ConsensusCore/include/ConsensusCore/Quiver/detail/sse_mathfun.h
./include/pacbio/ccs/ChainSeeds.h
./include/pacbio/ccs/ChemistryMapping.h
./include/pacbio/ccs/ChemistryTriple.h
./include/pacbio/ccs/Consensus.h
./include/pacbio/ccs/Exceptions.h
./include/pacbio/ccs/ExecUtils.h
./include/pacbio/ccs/Interval.h
./include/pacbio/ccs/IntervalTree.h
./include/pacbio/ccs/Logging.h
./include/pacbio/ccs/ReadId.h
./include/pacbio/ccs/SparseAlignment.h
./include/pacbio/ccs/SparsePoa.h
./include/pacbio/ccs/Timer.h
./include/pacbio/ccs/Utility.h
./include/pacbio/ccs/WorkQueue.h

Thoughts? .hpp seem the way to go?

Done.


Turn on self-hosted fonts

Flips switch for @use-font-cdn so production pulls from self-hosted fonts, not fonts.net.
Changes

Flips switch for @use-font-cdn to false, so that in production fonts are pulled from consumerfinance.gov/static/fonts

Testing

gulp build
Check the site in localhost.
Check JS console to see that fonts are trying to be loaded from localhost.
Contact @anselmbradford @Scotchester to get the fonts so you can install them locally. Download them from [GHE]/CFGOV/cfgov-fonts/
Place font files in /cfgov/static_built/fonts
cd /static.in/
git checkout [GHE]/CFGOV/cfgov-fonts/
Restart the server.
Visit the page and see that the fonts load locally.

Notes

You'll need to keep the fonts handy in a directory other than cfgov-refresh, as gulp clean will wipe out /cfgov/static_built/fonts.

Updated the documentation. mkdocs gh-deploy --clean should be run after this is merged.


Tasks cannot run in Docker on M1

Expected Behavior
This will work just fine when running locally: cloudquery sync hn_to_duckdb.yml:
kind: source
spec:
  name: hackernews
  path: cloudquery/hackernews
  version: v3.0.13
  tables: ["*"]
  backend_options:
    table_name: "cq_state"
    connection: "@@plugins.duckdb.connection"
  destinations:
    - "duckdb"
  spec:
    item_concurrency: 100
    start_time: 2023-10-09T00:00:00Z
---
kind: destination
spec:
  name: duckdb
  path: cloudquery/duckdb
  version: "v4.2.10"
  write_mode: "overwrite-delete-stale"
  spec:
    connection_string: hn.db

But the kestra task is stuck after WARN log: qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
id: cq_hn
namespace: dev

tasks:
  - id: hn
    type: io.kestra.plugin.cloudquery.Sync
    incremental: false
    configs:
      - kind: source
        spec:
          name: hackernews
          path: cloudquery/hackernews
          version: v3.0.13
          tables: ["*"]
          destinations: ["duckdb"]
          spec:
            item_concurrency: 100
            start_time: 2023-10-09T00:00:00Z
          # 90k rows for just 1 week of data
      - kind: destination
        spec:
          name: duckdb
          path: cloudquery/duckdb
          version: "v4.2.10"
          write_mode: "overwrite-delete-stale"
          spec:
            connection_string: hn.db

the same for CLI:
id: cq_hn_cli
namespace: dev

tasks:
  - id: wdir
    type: io.kestra.core.tasks.flows.WorkingDirectory
    tasks:
      - id: config
        type: io.kestra.core.tasks.storages.LocalFiles
        inputs:
          config.yml: |
            kind: source
            spec:
              name: hackernews
              path: cloudquery/hackernews
              version: v3.0.13
              tables: ["*"]
              backend_options:
                table_name: "cq_state"
                connection: "@@plugins.duckdb.connection"
              destinations:
                - "duckdb"
              spec:
                item_concurrency: 100
                start_time: 2023-10-09T00:00:00Z
            ---
            kind: destination
            spec:
              name: duckdb
              path: cloudquery/duckdb
              version: "v4.2.10"
              write_mode: "overwrite-delete-stale"
              spec:
                connection_string: hn.db

      - id: hn2
        type: io.kestra.plugin.cloudquery.CloudQueryCLI
        commands:
          - cloudquery sync config.yml

they keep running forever:

Actual Behaviour
No response
Steps To Reproduce
No response
Environment Information

Kestra Version: 0.13.0
Plugin version:
Operating System (OS / Docker / Kubernetes):
Java Version (If not docker):

Example flow
No response

fixed by CloudQuery by adding a dedicated image ghcr.io/cloudquery/cloudquery:latest-linux-arm64 here https://github.com/cloudquery/cloudquery/issues/14506#issuecomment-1764373170
example of a working flow:
id: cloudquery_sync
namespace: dev

tasks:
  - id: hn_to_duckdb
    type: io.kestra.plugin.cloudquery.Sync
    docker:
      image: ghcr.io/cloudquery/cloudquery:latest-linux-arm64
    incremental: false
    configs:
      - kind: source
        spec:
          name: hackernews
          path: cloudquery/hackernews
          version: v3.0.13
          tables: ["*"]
          destinations: ["file"]
          spec:
            item_concurrency: 100
            start_time: 2023-10-16T00:00:00Z
      - kind: destination
        spec:
          name: file
          path: cloudquery/file
          version: v3.4.8
          spec:
            path: "{% raw %}{{TABLE}}/{{UUID}}.{{FORMAT}}{% endraw %}"
            format: parquet


Thread pinning on Linux

Correctly pay attention to taskset and cgroups by using
sched_getaffinity() to determine an initial CPU set.
When building the available CPU list, pay attention to
both the distinction between physical and hyperthreaded
cores and NUMA core grouping.
Add --ponynopin to disable all thread pinning.

@sylvanc - don't forget to add a changelog entry.
Now that we're going to have regular releases again, people will actually start reading and using the changelog! :smile:

Oops, thanks! :)


Incorrect format for Non-NixOS descriptions in 24.05 channel

Noticed for multiple packages, under 24.05 channel, that the non-NixOS descriptions have a missing newline before # with flakes.
Some screenshots:
nodejs_22

python3

This makes it inconvenient to copy the command under # without flakes

Fixed by #799.


access_control.bats: add SELinux context tests

Test the SELinux security contexts of the core processes.
Signed-off-by: Stephen Smalley<EMAIL_ADDRESS>

Note: This test will need to be updated if/when this PR is accepted:
https://github.com/OpenXT/xenclient-oe/pull/446


Cellular component terms for Giardia

This ontology project stems from a request by Michael Cipriano (Scott Dawson's lab at UC Davis). New GO CC terms are needed to represent protein localization in Giardia lamblia and related species. Omar Harb and Nicholas Stover also agreed to help. We will work with the experts to make the new terms applicable to as many species as possible, and we'll add taxon constraints otherwise.
I'm attaching the list of terms that Michael sent us originally. I'm emailing the experts directly with questions and comments, but I'd like there to be a reference to this work in SourceForge too, to make everyone aware and in case other curators wish to give feedback. Some terms look very specific with 'spatial' constraints. We've discussed this among editors and agreed to include the terms more or less as they are, provided that they're not redundant with existing terms (including recent ontology work on cilial/flagellar CC terms).
I'll post the new GO IDs and names here when they become available.
Cheers,
Paola
Reported by: paolaroncaglia
Original Ticket: geneontology/ontology-requests/10642

Added
id: GO:1990900
name: ciliary pocket collar
And emailed Scott Dawson and Michael Cipriano about 1) JBMS paper 2) annotation plans.

Also, attaching initial file for reference (contains initial list of terms requested, but I keep a working copy with comments added along the project).
GiardiaGoTerms_SCDrefs.docx

(Old Jira ticket was at https://www.ebi.ac.uk/panda/jira/browse/GO-198, now closed.)

Reviewed entire document. Terms left to add:

For all 8 flagella (but see discussion in GiardiaGoTerms_PR_310516.doc, and updated defs. of existing ciliary terms):
axoneme transition zone
cytoplasmic axoneme
membrane-bound axoneme
flagellar pore

left/right caudal axoneme microtubule root

caudal complex / funis

marginal plate, with 2 children

striated fibers, with 2 children

marginal groove

ventrolateral flange

ventral groove

peripheral vesicles

bare area vesicles

encystation specific vesicles

fimbrae.

Once done, the ontology work is completed, and this ticket can be closed.

Note for self: I’m going to have to leave this for now, and hopefully come back to it sometime in the near future if/when publication plans are finalised. But it makes more sense to leave it assigned to me.

Is there still a contact person for this project ? There are no references for the new terms requested.

Pascale

@paolaroncaglia - We're trying to close tickets this week so I was wondering if this ticket is completed and could be closed.

Hi,
I am on leave today and tomorrow, I will reply when I am back. Thanks.
Paola

On 12 Feb 2018, at 18:47, Karen R Christie<EMAIL_ADDRESS>wrote:
@paolaroncaglia - We're trying to close tickets this week so I was wondering if this ticket is completed and could be closed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@krchristie
This ticket is not completed, but it won't be possible to address it in the near future. So I made a note for myself somewhere else, and I'm closing this now. Thanks.

I am not sure we should close tickets that are not finished. We can put a status = pending -
what do you think ? and @ukemi @vanaukenk ...?

@pgaudet et al
'pending' would be great thanks, in fact that's the label that this ticket had until half an hour ago ;-)

We shouldn't close tickets that are not finished unless the ticket has drifted so much that it would make more sense to open one or more new tickets. In that case, the existing ticket can be closed and new ones opened that all refer to one another.

@paolaroncaglia - Thanks for checking on this ticket. Since the consensus is to leave tickets open unless they are done or out-of-date, I've reopened this to save you needing to come back.

Thanks @krchristie .

If nobody is actively curating Giardia doesn't it make sense to close this ticket, and be led by the community if and when they require the terms?

I'm closing it. It's too long to read... start afresh, no point to add terms imagining that people will use them when people are waiting for terms to use.


Added AutoAnimate to data list

Implemented auto animation using react hook - useAutoAnimate() from https://auto-animate.formkit.com/#usage-react

I have made the requested changes, Please review @yoannfleurydev.


Not recognizing .tex files

I get the following errors when I start neovim:
[Template.nvim] Could not find the filetype of template file path/to/template/.DS_Store
[Template.nvim] Could not find the filetype of template file path/to/template/tex_template.tex

I do not get the error if I change .tex to .latex.
Can I ignore the .DS_Store filetype?

because for text file neovim need content to detect what filetype it is . try use *.tpl and first line of this tpl file is ;; latex.

because for text file neovim need content to detect what filetype it is . try use *.tpl and first line of this tpl file is ;; latex.

This worked, thank you.

closed


⚠ Bofrost.de has degraded performance

In 5cae8da, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1761 ms

Resolved: Bofrost.de performance has improved in 03dbbfe after 9 minutes.


Pod scaling down criteria

I was wondering how can the scaler knows when it is safe to scale down the pods, if there's a long running task in the consumer, will the scaler kill the currently running pod when the message in the queue has reach below the target?

Ok, I've found some more info on this thread https://github.com/kedacore/keda/issues/157, is there any sample on how to use scaledJob with rabbitmq scaler?


The link to the toolchain-specification in the description of the toolchain input is broken

The current link in action.yml points to

https://github.com/rust-lang/rustup.rs#toolchain-specification

This  however doesn't exist any more, as it has been moved to the book under the chapter Toolchain specifications here

https://rust-lang.github.io/rustup/concepts/toolchains.html#toolchain-specification

Closed by #116


Documents disappears from the view when selecting document type after pagination

Description
When navigating to the "Documents" area and clicking on a specific page, such as Page 2, and subsequently selecting a document type, like "Blog", all documents disappear from the view. Refreshing the page is the only way to restore the document list.
Is this a bug or a feature?

[x] Bug
[ ] Feature

Steps to Reproduce

Go to the "Documents" area.
Navigate to a specific page, e.g., Page 2.
Click on a document type, e.g., "Blog".

Additional context
This issue disrupts the user experience by causing the disappearance of all documents when selecting a document type after navigating through pagination. Resolving this bug would ensure smoother navigation and usability within the "Documents" section.
1

2

This is great feedback, thanks a lot! We'll look into fixing it

Should be fixed in the newest release


MXFDump: fix index out of bounds error

Issue #74 was (partially) replicated by building libMXF on Debian 11 with address sanitizer options as suggested for GCC here. However, no global-buffer-overflow error was reported; only a segmentation fault (e.g. shown when using just CXXFLAGS="-fsanitize=address").
Additional installs required: apt install libasan8 libubsan1
Build: CXXFLAGS="-fsanitize=address -fsanitize=undefined -fno-sanitize-recover=all -fsanitize=float-divide-by-zero -fsanitize=float-cast-overflow -fno-sanitize=null -fno-sanitize=alignment" cmake -DCMAKE_BUILD_TYPE=Debug ../bmx/deps/libMXF
Running MXFDump on poc.mxf (provided in #74) results in
...
  47.01     :    06.0e.2b.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.00
  06.01     :    ea.0e.2b.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.00
  ff.ff     :    06.0e.2b.<IP_ADDRESS>.<IP_ADDRESS>.04.02.0d.00.00
MXFDump : Warning : Cannot remap static local key as specified by Primer Pack (property "EditUnitByteCount" has local key 3f05 in the MXF dictionary and 0000 in the Primer)
/build/bmx/deps/libMXF/tools/MXFDump/MXFDump.cpp:3320:42: runtime error: index 321 out of bounds for type 'MXFLocalKey [188]'

Fixes #74

However, no global-buffer-overflow error was reported; only a segmentation fault (e.g. shown when using just CXXFLAGS="-fsanitize=address").

Changing Debug to Release (see issue comment) exposed the buffer overflow error


Proposal for a blocklist to mitigate the 255 device limit

TLDR: this is a proposal for the plugin to support an optional blocklist file to suppress handling of some devices and/or sub-devices.
Like others with lots of zigbee kit I've been running up against the Domoticz framework's limit of 255 devices per plugin.
The option added last year to suppress signal and/or cell and btperc devices helped considerably. However the Universal Adaptor approach, which is basically "if zigbee2mqtt.io exposes it, let's create a device for it" is making things worse again.
Though it's not the fault of the plugin, many of the newly-exposed attributes of devices are completely redundant. For example, there is no point to "tamper" devices for Sonoff sensors which don't even have hardware to detect tampering (go figure!); the temp sensors which Xiaomi/Aqara motion and contact sensors expose appear to report nonsense values;  a single Temp/Humidity/Pressure device can result in nine (yes really!) Domoticz devices And when the novelty of "effec" devices wears off you might rather not have those either. I could go on and on ..
I've been looking for a way to make the plugin more discriminating in its handling of these sub-devices and I'd like to propose a solution.
In my personal, temporary fork of the plugin I've added, and have been testing, code to read in an optional file from the plugin folder, which I've called blocklist.txt.
Each line in the file is a device-id or a fragment of one; each will therefore most probably be one of the following: -
a full device-id as seen in the ID column in Domoticz's Setup/Devices tab, e.g. 0x00124b001f841999_cell
a device suffix, e.g. cell, which will suppress all cell devices
an IEEE Address,e.g. 0x00124b001f841999 which will suppress that zigbee device completely
Note that you aren't restricted to just those id fragments, any will do. For example if for some reason you wanted to suppress all your Sonoff devices you could add a line with just 0x00124b0 on it. I considered using regex to allow really sophisticated matching but in the end I couldn't see anybody needing it, there would be an overhead and python-regex probably isn't even present on most people's systems.
I've added the code to read the file to domoticz.py. This is called during the init of devices_manager.py. A global list variable is created called "block_list". This is then examined in device.py:register and device.py:handle_message to decide whether a particular device should be suppressed (i.e. not created and not updated, respectively).
Devices which are suppressed by the blocklist but which already exist will no longer be updated. If they are deleted from Domoticz the plugin will not recreate them. The Custom Zigbee2MQTT tab is not affected so you will still be able to see your full zigbee mesh there.
The blocklist file does not have to exist; is is entirely optional and this is therefore not a breaking change. Indeed I would expect most users won't even need to know the facility exists..
Note that the ability to suppress signal, cell and btperc devices using the blocklist makes the "Track Link Quality" and "Use Battery Devices" parameters on the plugin's Hardware page redundant, but there is no negative consequence if devices are suppressed "twice".
I'd like to know what others think, particularly @stas-demydiuk of course. My opinion is that even if the Domoticz device limit were raised at some point in the future it would still be useful for users with large numbers of devices to be able to reduce the clutter.
This is clearly not the only way to achieve device suppression, it's just the way I decided to go. I have little knowledge of the overall design of the plugin so I may well have missed hidden implications of my approach. Also, I am brand new to Python coding and it probably shows!
I'd very much welcome comments on the idea and hope something along these lines can be added to the plugin.

In the frontend of Zigbee2mqtt under settings/experimental settings is also a blocklist/whitelist available.
Is that the same of what you mean?

The blocklist facility in zigbee2mqtt.io is very different. It used to be called “ban”, because that is what it does  - it prevents a zigbee device from joining the network at all.
My suggestion is to allow the suppression of unwanted features exposed by devices.

Is the 255 maximum devices only a Domoticz issue or also for Home Assistant?
if this is the case, wouldn’t it be an idea to implement this enhancement at the Zigbee2mqtt side?

It’s a restriction of the Domoticz plugin framework, affecting all plugins. There is a an ongoing discussion about it in one of the open issues here - you might like to read it.
You’d need to do your own research into the limits of Home Assistant, I don’t use it.
I think it would be a bad idea to fix a Domoticz problem by changing zigbee2mqtt.io.

The blocklist facility in zigbee2mqtt.io is very different. It used to be called “ban”, because that is what it does - it prevents a zigbee device from joining the network at all.
My suggestion is to allow the suppression of unwanted features exposed by devices.

Totally agree with your suggestion.

I would love to see this sollution implemented by stas-demydiuk. An easy fix to a very annoying problem. I could easily cut away around 70% of the zigbee devices in my domoticz setup.
Right now I'm closing in on the 255 device limit. With this fix it would be around 80 devices that I actually have use for. At the same time making the domoticz database file less occupied by garbage.

This looks like a workable solution but I could live with something probably more simple:

use domoticz for what it's meant to do: control and read primary device values (on/off, temp, battery level so domoticz can report on that, ..)
use the z2m control page to report and control secondary stuff (link level, power_on_behavior, color_temp_startup maybe) and keep these out of domoticz as these rarely require changes and can be set from z2m directly
add a 'simple' switch to the plugin settings to create separate devices or combined devices for the likes of temp/hum/baro

That way, you don't need to maintain any list and the number of devices (and device updates) is minimal.
Thoughts?

Blacklist support has been added using plugin settings page. Now there is one more parameter to setup the blacklist.

Blacklist could contain several entries devided by semi-colon. Each blacklist entry should be valid Python regexp. For example:

Single item of a device - use full Device ID (ieee addr + alias) to block it i.e. 0x842e14fffe13971a_state
All items of a device - use Regexp to block all logical devices (aliases) of a specified zigbee device (ieee address) i.e. 0x842e14fffe13971a_.*
Specific item of all devices - use Regexp to block all devices (ieee address) with a specific alias i.e. .*_state

Any feedback is highly appriciated

Blacklist support has been added using plugin settings page. Now there is one more parameter to setup the blacklist.

Blacklist could contain several entries devided by semi-colon. Each blacklist entry should be valid Python regexp (the most common regexp entity I guess would be .* which means any number of symbols). For example:

Single item of a device - use full Device ID (ieee addr + alias) to block it i.e. 0x842e14fffe13971a_state
All items of a device - use Regexp to block all logical devices (aliases) of a specified zigbee device (ieee address) i.e. 0x842e14fffe13971a_.*
Specific item of all devices - use Regexp to block all devices (ieee address) with a specific alias i.e. .*_state

Any feedback is highly appriciated

Extra Option also to choose 'whitelist'  instead of 'blacklist'?
I'll test the solution above, thanks!!

No available options left :) Domoticz supports up to 6 custom parameters per plugin

Looks great! I just dropped 40+ devices that I have no need for.

No available options left :) Domoticz supports up to 6 custom parameters per plugin

no problem ;-)

Hmm, it is not working for me. The black_listed devices are still updated....
Is this line ok?

Try removing the devices. They will not be readded.

Try removing the devices. They will not be readded.

Yes, you're right. Thanks

I am finding that if the blacklist parameter is left blank then all devices are blacklisted.

.. and a suggestion .. please consider allowing the word 'heartbeat' as  one of the values.
That would please those who who don't like seeing heartbeat messages being recorded, very confusingly, as motion detections, and lights being shown as having been turned on when they haven't.

nice, works like a charm!

.. and a suggestion .. please consider allowing the word 'heartbeat' as one of the values.
That would please those who who don't like seeing heartbeat messages being recorded, very confusingly, as motion detections, and lights being shown as having been turned on when they haven't.

How do you mean? How should you add heartbeat?

By typing it in the box along with any blocklisted device names.


Address issue #447:Vagrant setup fails running.

For issue #447.

This fix is a duplicate of fix already in #360.

@rabbah ,apology.


aws command prints out both ipv4 and ipv6 ranges even though --ipv6 flag was sent

Describe the bug
aws command prints out both ipv4 and ipv6 ranges even though --ipv6 flag was sent
To Reproduce
Steps to reproduce the behavior:

execute this command:
cipr aws --ipv6 --filter-service s3 --filter-region us-east-1

Expected behavior
only ipv6 CIDRs
Screenshots

fixed in v0.7.3


Crash when compiling file awesome_notifications

Sorry, but i have to drop this issue and mark it as invalid, because you didn't follow the community rules to publish your issue.


Cannot upload image with paste

Describe the Bug
I try to paste an image with Ctrl+V
like this

I just hit Ctrl+V in github and it uploaded the image.
I set APP_DEBUG=true as an env variable but I'm not seeing anything useful in the logs. Only this:
bookstack  | bookstack:80 <IP_ADDRESS> - - [18/Mar/2023:20:50:00 -0400] "POST /images/gallery HTTP/1.1" 500 1661 "http://bookstack.delta.local/books/getting-comfy-with-docker-compose/page/logging-and-monitoring/edit" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"
Steps to Reproduce
I take a screenshot on windows with Win+Shift+S
I paste with Ctrl+V
Expected Behaviour
image uploads
Screenshots or Additional Context
No response
Browser Details
chrome 111.0.5563.65 windows 10
Exact BookStack Version
BookStack v23.02.1
PHP Version
8.2.3
Hosting Environment
solidnerd/bookstack:23.2.1

Oh.
www-data@4ca961d7dfd8:~/bookstack$ id
uid=33(www-data) gid=33(www-data) groups=33(www-data)

chown -R 33:33 ./
Fixed.


[4.0] Godot won't start if  I have 3.5beta1 already open

Godot version
4.0alpha 1
System information
Debian 11
Issue description
As stated in title.
Also If I close 3.5 beta 1 then 4.0 alpha 1 start.
Is like 3.5 put on hold 4.0
ps.: I have NVIDIA Optimus . So to me seems pretty much similar to https://github.com/godotengine/godot/issues/48091#issuecomment-915226816
If I open just the 4.0 the I have this error:
Godot Engine v4.0.alpha1.official.31a7ddbf8 - https://godotengine.org
Can't open bumblebee display.
ERROR: GENERAL - Message Id Number: 0 | Message Id Name: Loader Message
	loader_scanned_icd_add: ICD libnv_vulkan_wrapper.so.1 doesn't support interface version compatible with loader, skip this ICD.
	Objects - 1
		Object[0] - VK_OBJECT_TYPE_INSTANCE, Handle 147716592
   at: _debug_messenger_callback (drivers/vulkan/vulkan_context.cpp:157)
MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete
Vulkan API 1.2.162 - Using Vulkan Device #0: Intel - Intel(R) HD Graphics 4000 (IVB GT2)

It let me open project manager and so on nevertheless..
Thanks
Steps to reproduce
Its seems related who have NVIDIA Optimus. Not sure 100%
Minimal reproduction project
NA

Most likely bumblebee doesn't support running both Vulkan and OpenGL contexts at the same time (or the patched version you might have, as I don't think stock bumblebee supports Vulkan at all, the project is unmaintained since 2013: https://github.com/Bumblebee-Project/Bumblebee/commits/master).
You might be able to confirm that by trying to run other OpenGL and Vulkan applications at the same time.

Most likely bumblebee doesn't support running both Vulkan and OpenGL contexts at the same time

Its possible

You might be able to confirm that by trying to run other OpenGL and Vulkan applications at the same time.

Yes , I can confirm I can run Dota2 (setting on vulkan render) and Blender 3.0 (optirun - OpenGL)  at same time
These issue, however, is related to Godot (3.x and another OpenGL software. Ref: https://github.com/godotengine/godot/issues/48091#issuecomment-824895551
Anyway AFIK its scheduled to be integrated in 3.5 soon. So, I guess, it will be ported in 4.0 too.. Right?