Use more inclusive regexp for matching file paths

Per this discussion over on lbry-desktop: https://github.com/lbryio/lbry-desktop/issues/2777#issuecomment-558000435
As long as you are in ES2018 or later land, you can use the capture group \p{L} to represent all letters and \p{N} all numbers. So you could use this (untested) regexp instead:
 /^[\p{L}\p{N}_@()-][\p{L}\p{N}_.@()-\s]+.(jpeg|jpg|png|bpm|webp)$/

Not supported in Firefox and Edge

Despite being a part of the standard since 2018, unicode proeprties are not supported in Firefox (bug) and Edge (bug).

There’s XRegExp library that provides “extended” regular expressions with cross-browser support for unicode properties.

Alternative: https://github.com/slevithan/xregexp

Looks like we can use this syntax directly with :
https://github.com/josephfrazier/babel-plugin-transform-xregexp

It should be like this:
/^[\p{L}\p{N}_@()-]+[\p{L}\p{N}_.@()-]+.(jpeg|jpg|png|bpm|webp)$/u

Actually this is the correct regex with the unicode support:
https://github.com/btzr-io/Villain/blob/b133147f71ce145b089e1b4a359e3cbb65b5d773/src/lib/utils.js#L5-L7

See: https://github.com/nika-begiashvili/libarchivejs/issues/19


WordPress implementation

Hey guys,
I love this swiper & I'd like to implement it in WordPress.
Any tips on how to get started for a developer trainee?
Preferably, with the option to pick each slide.
Cheers

I think you better to ask for this on some WP forum/portal or Stack Overflow


Makefile.defines: Refactor UI defines per target

Description
Makefile.defines: Refactor UI defines per target
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[x] Other (for changes that might not fit in any category)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (5849a44) 60.42% compared to head (0016a0b) 60.42%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #527   +/-   ##
=======================================
  Coverage   60.42%   60.42%
=======================================
  Files          12       12
  Lines        1660     1660
=======================================
  Hits         1003     1003
  Misses        657      657

Flag
Coverage Δ

unittests
60.42% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Cannot fetch PDB file from rcsb site

The current version cannot fetch PDB file from rcsb site, because HTTP URL for the PDB files at the RCSB site has been changed (PDB files in /pdb/files/ path was removed).

Changed the URL to use files.rcsb.org host (as in the download link in the PDB web site). [2d94af7e31c460d135a7c3b4f7ba7f83bca847e7]


Bugfix/detach grid

Fixes issue in new code found by @jhpedemonte (thanks!).

This isn't fully working with latest code. Nodes are still deleted from DOM when doing a destroy(false).
It works fine with commit 9c01f02 (if I change removeAll(!0) to removeAll(!1) in gridstack.min.js) but fails with commit 85740de (& master). Trying to find out what changed in gridstack.min.js.

Hmm, wait, I may have the commits wrong. But definitely still an issue on master. Just trying to find out where things went wrong.

Seems to be caused by commit a33f046fa6b05ad2e42f4b3eaf2d0921504f2b4b (after manually patching gridstack.min.js to removeAll(!1)). Any idea why these changes would still delete nodes when calling destroy(false)?

Okay, give it one more try. We had found a silly bug a few days ago when we were doing our unit tests. Unfortunately, it turns out that fixing that bug created a new one. I have fixed that. Thanks for your patience and thank you very much for tracking it down to that particular commit. A slight bit of a doozy, but now it should work.
For reference, removeWidget with detachNode=false was also broken. Both destroy as well as removeWidget should now work properly with detach false.


Fixes preview expiry time sent through email.

Fixes #1463
Changes: The local time was sent through email , now the Coordinated Universal Time (UTC) is sent which would remove the time dependency on server.

@Princu7 please review.

I am currently busy due to exams. Will do once it is completed!


Indenter does not respect IndentSize option

TabSize works fine, and luckily people tend to set IndentSize and TabSize to the same value in general, but this should still be fixed.
https://github.com/Microsoft/nodejstools/blob/master/Nodejs/Product/Nodejs/SmartIndent.cs#L84-L214

This is fixed in NTVS 1.2 now that the editor is backed by Typescript.


Fix demo with Node http-server

:boom: thank you, checking it out now

npm install && npm run dev appears to work like a champ!
I'm not sure why the tracebacks aren't coming up right though:

As is, this looks great and does what it needs. I'll address the traceback now.

:+1:  Thanks for looking into the tracebacks, @rgbkrk!

That is... That is... wow.


added ORider Carpool Oracle name

This change adds the ORider Carpool Oracle name that is used by the https://ordier.obyte.app website. This oracle posts statuses of completed rides to unlock smart contracts created to pay for the rides or refund passengers.

Awesome!


Hello,I wonder what your hci1 device is?

because I find that I can't change my mac address of the Intel BT chip


Fix false positive update notification on iPhone

When starting seven23 as PWA on the iPhone, the app trigger way too often a false positive for an available update.
Expected behavior
Update notification only appears when an update is available.

Can't reproduce anymore.


Add Aarhus Municipality Schools domain.

This email address applies to many schools in the Aarhus Municipality of Denmark.
https://docs.google.com/spreadsheets/d/1aTIMabB2ibMDaxDWNSeEMxBIJI8vJAUXBdvlmU7CKYA/edit#gid=0&range=D61
This spreadsheet translated says
<EMAIL_ADDRESS>- shared domain for schools in Aarhus"

@sqlongithub I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host aaks.aarhus.aarhus.dk not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Http.PostJsonAsync Throws Exception

Blazor 0.9.0
Http.PostJsonAsync<T> throw exception when passing an object with DateTime property.
Explanation
When I pass my object which has the DateTime Property, It throws exception. But it also send data to api and the records are inserted in database.
For all other objects it works fine. But for this object which has a Nullable DateTime property it throws exception.

The Model is valid, before passing it to the method.

When I handle it in try catch block and print the ex.Message to console it prints WASM: Invalid JSON string.
try
        {

            await Http.PostJsonAsync<Student>("api/student", StudentModel);
            toaster.Success("Student saved successfully", "New Student");

            CallBack?.Invoke();

        }
        catch (Exception ex)
        {
            Console.WriteLine(ex.Message);
        }

WASM: Invalid JSON string.
Screenshots
Exception when not handled

Model Classes

Thanks for contacting us, @shakeelgithub.
In order for us to investigate this issue, please provide a minimalistic repro project that illustrates the problem.

Hello @mkArtakMSFT
Here is  The Repository   with all instructions in readme.md file.

The Issue is in This File at line 149

Thanks @shakeelgithub.
Looks like this is caused by the fact that the format of the data being passed from the server to client is not something client understands. At the moment, the JSON serializer we use in Blazor has no understanding of the DisplayFormat attribute, hence it completely ignores the DataFormatString you've specified.
As an alternative, you can use JSON.NET on the client.


What is the pearson correlation in lighteval scores between 1B/400M model and 7B model?

Really appreciate your work!
I am wondering if you could share the Pearson correlation for core/mmlu/extended scores between the 7B and smaller models ( similar to the statistics presented in Section 3.2 ) using the LightEval package.
According to your experiment in Appendix G.2 and in recent literature [1], metrics based on the entire answer's log probability tend to show lower variance and steeper changes in pre-training ablations when the training token amount is relatively small.
This has drawn my curiosity about whether using other evaluation methods that incorporate entire answer log probability, instead of llm-foundry, might offer more scientifically solid results for a leaderboard.
I would be extremely grateful if you could provide any insights or data on this topic.
[1] Madaan, Lovish, et al. "Quantifying Variance in Evaluation Benchmarks." arXiv preprint arXiv:2406.10229 (2024).

Unfortunately we currently do not have the bandwidth to run LightEval on our models. I agree that reducing evaluation variance is an important research direction and would suggest you look into other work that has used perplexity evaluation, such as https://arxiv.org/abs/2403.08540


Is it possible to add the SCNN configuration to timeloop?

I'd like to know if it is possible to get the configuration of SCNN.

We are working on releasing more sparse accelerator designs -- will follow up on this thread with new updates.


First Artisan Migrate

Hello, i make the first Artisan Migrate from last release

this is a problem from my side or migrate side ?

@Iwhite67 I just created a new branch feature/email-unique-migration. Can you check if it works? If it does, I'll merge it in dev and master
FYI: Right before creating the branch, I created a new database, and did php artisan migrate:fresh, no issues with MySQL.

i check after

so, have test with just php artisan migrate
this is good

Added in #358


Increment version and publish to crates.io

Version 0.4.1 does not contain the bugfix that allows tables to be read into an AnyLuaValue. Bumping the version will allow crates to be built that use this functionality.

Done.


[SPARK-38474] [Core] Use error class in org.apache.spark.security

Why are the changes needed?
Refactored exceptions thrown in the package org.apache.spark.security in to be in inline Spark error class framework
Does this PR introduce any user-facing change?
No
How was this patch tested?
Modified impacted testcases and added new test cases

cc @bozhang2820

Change LGTM. Not sure about the GitHub Action test failures (about doc generations and docker integration tests). @HyukjinKwon any idea?

yeah that test shouldn't be related, and it's just flaky.

LGTM2 otherwise. @sandeep-katta you might need to rebase your branch and sync to the latest master branch to avoid the linter job failure.

@cloud-fan @MaxGekk could you review this?


fix: check integration tests failure

Description
Check if problems found at PR https://github.com/argilla-io/argilla/pull/4600 are associated to latests changes on argilla-server repository.
Type of change
(Please delete options that are not relevant. Remember to title the PR according to the type of change)

[ ] 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)
[ ] Refactor (change restructuring the codebase without changing functionality)
[ ] Improvement (change adding some improvement to an existing functionality)
[ ] Documentation update

How Has This Been Tested
(Please describe the tests that you ran to verify your changes. And ideally, reference tests)

[ ] Test A
[ ] Test B

Checklist

[ ] I added relevant documentation
[ ] follows the style guidelines of this project
[ ] I did a self-review of my code
[ ] I 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
[ ] I filled out the contributor form (see text above)
[ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

@jfcalvo I relaunched the failling step and the errors is different now. I think the original error wasn't really related to the argilla-server dependency. For dev branches, we should use the main branch dep from argilla-server. Only when a release branch is prepared and published, we should set the server dependency (as we already did in the last release)


Right key to skip quits the screensaver on Mojave

Required information
In order to help us sort your issue, we ask that you provide the following information:

[ ] Mac model: MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports)
[ ] macOS version: Mojave 10.14.6
[ ] Monitor setup: One screen

Description of issue / Feature request
When I press right key, it has recently started quitting the screensaver instead of skipping to the next one. I have tried enabling and disabling the option for skipping.
I can read that this has broken on newer OS'es, but has it also broken on Mojave?

Required information
In order to help us sort your issue, we ask that you provide the following information:

[ ]  Mac model: MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports)
[ ]  macOS version: Mojave 10.14.6
[ ]  Monitor setup: One screen

Description of issue / Feature request
When I press right key, it has recently started quitting the screensaver instead of skipping to the next one. I have tried enabling and disabling the option for skipping.
I can read that this has broken on newer OS'es, but has it also broken on Mojave?

Hi @ZeppelinCaptain
Yes, it's supposed to work in older OSes but 1.7.0 had a bug, I fixed that in the latest beta that you can download here : https://github.com/JohnCoates/Aerial/releases/download/v1.7.1beta1/Aerial.saver.zip
Sorry about the confusion !

Closing with 1.7.1 : https://github.com/JohnCoates/Aerial/releases/download/v1.7.1/Aerial.saver.zip


Fix merge with squash

Q
A

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Tests pass?
no

Fixed tickets
#64

License
MIT

I've tested this fix with PR https://github.com/KnpLabs/php-github-api/pull/863 and it seems to work correct

Thank you @acrobat


BUG: UsageInputs.validate - handle optional

~TODO:~

[x] add unit tests
[x] make sure that DiagnosticUsage works
[x] make sure that ArtifactAPIUsage works

ccing @David-Rod - I think @ebolyen mentioned to me that you might've come across this issue in your own Usage API work.

I am pretty confused about the flake8 errors on travis...

Okay, squared away travis.


Adds ability to generate console URL for CCS acct

Fulfills OSD-4814
To Test:

Pull and start https://github.com/openshift/aws-account-operator/pull/469
make create-ccs
oc get account -n aws-account-operator and then note the account CR name that you just created.
Build this code
./bin/osdctl account console -n [account-cr-name]
Click the URL Given
Verify the aws account ID is correct and that you're logged in with the BYOCAdminAccess-[account-cr-suffix] in the top right corner of the aws console

@rogbas review and test in stage and comment. In stage look for CCS clusters created after Sept 16

PR tested/validated in CCS stage clusters.
/lgtm

/hold

/lgtm

/lgtm

/hold cancel


add debug log for rootfs-not-ready

Signed-off-by: yason<EMAIL_ADDRESS>We should also modify containerd's diff.Apply.

/ok-to-test

/ok-to-test

We should also modify diff.Apply in containerd.

/test pull-cri-containerd-node-e2e

@yanxuean I don't think it's our unmount fails. It is the unmount in containerd fails, it cleans up the snapshot unexpectedly.
IIUC, our removeall will only cleanup the top layer (writable layer), which is fine.

Yes, we need to modify it in containerd.
My main thought is printing the "mounts" got from snapshotter.Mounts in checkSnapshot.
It will verify if the parent snapshot is exist.
But Now I think we don't need it again. Because we has been congratulating the 1785 was solve.

I will close it.

@Random-Liu  Will we revert the commit about checkSnapshot?  If not I suggest to print the  mounts.

The checkSnapshot has been reverted. #473 .  Close this.


[sil-devirtualizer] Fix some bugs in the devirtualizer.

What's in this pull request?

Fix a couple of bugs in the devirtualizer.
dar://25891588 and SR-1206
Resolved bug number: (SR-1206)

Before merging this pull request to apple/swift repository:

[x] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

Don't crash if a class_method instruction could not be devirtualized.
Improve devirtualization of methods with generic parameters and using dependent types.
Fix a bug in isBindableToSuperclassOf, uncovered while fixing the original bug reported in SR-1206.
This bug could lead in certain cases to invocations of a wrong method from the base class, instead
of using a method from a derived class.

rdar://25891588   and SR-1206

@swift-ci Please test and merge

@jckarter Thanks for the quick fix for a problem in Type.cpp! 👍


ES6 refactor

This pull request is a first step to move this project closer to the present times.
Description

Refactor ZooKeeper and its promisified version to ES6 standard.
Get rid of lib/promise, instead use native Promise class.
Fix tests, so they pass.

Motivation and Context
This project remembers the old days of Node 0.x. A lot has changed since then and we should move on. This PR is a first step towards better code quality.
As there are a lot of changes I submit this PR as is for now. I will however start working on enforcing the eslint rules, so we should end up with a project that is nice and tidy.
TODO

[x] Make eslint pass
[ ] Explicitly define API input parameters

How Has This Been Tested?
It has been tested with both unit and integration tests.
Types of changes

[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)

Checklist:

[x] I have read the code of conduct.
[x] I have read the contributing guide.
[ ] I have updated the documentation accordingly (if applicable).

Thank you for doing this long awaited task! It's a massive PR and I will need some time to review this.

You can follow ESLint refactoring in a separate PR: https://github.com/jbienkowski311/node-zookeeper/pull/1

Awesome work @jbienkowski311!

I've merged eslint branch and resolved the conflicts. I did not enable ESLint rules on tests_integration directory - it is a lot of work to make it pass and I do not think that it is worth the effort.
What I would like to do before announcing that this PR ready to merge is explicit definition of the input parameters for the API methods. Before, the library was using arguments, right now I use ...args as a temporary solution to make ESLint pass. However I believe in rule that explicit is better than implicit :wink:

Okay, I think that's enough for this PR. @DavidVujic please check if I did not mess up with the API (I used documentation from README.md and tests). I've added a_sync method to the documentation as it was missing. Not sure if it's correct though... :wink:

Thank you @jbienkowski311! I'll have a look. I would like to finish issue #153 and build a new release from it before merging this branch. Are you ok with that?

Sure thing!

Great work! I have a question about the legacy Promise library that is used in the Master branch: this PR with native Promises will be a breaking change, won't it?
If possible, to avoid breaking changes - could we add wrappers in the ZK Promise class for the old Promise lib functions? They could be marked with JsDoc "deprecated" comments. What do you think about it?

Now this could be a potential breaking change... However it is an easy fix to implement. Just give me few hours :wink:

@DavidVujic I brought back the ZkPromise class with previously missing methods being deprecated as suggested. There was one method that I was unable to restore - Promise.wait. The good news is that it would not work anyway :wink: I have covered new ZkPromise class with tests as well.

Awesome! I'll try to finish the review in the next couple of days. Currently at a location with a poor connection :cow: :sheep: :chicken: :sweden:


用Masonry如何设置？？？

模拟器不没有打印出警告，真机打印了很多了警告 Unable to simultaneously satisfy constraints.
Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
.....

是6p就有打印,其他没有

[self.contentView mas_makeConstraints:^(MASConstraintMaker *make) {
make.height.equalTo(117);
make.width.equalTo([UIScreen mainScreen].bounds.size.width);
}];
加了这个就不打印了？？？

计算时若约束设置正确是肯定可以正确计算的，请检查下 Masonry 约束设置的时机和是否约束正确，Masonry 如何写的问题就不在这儿讨论了。


revision based on Jon's code

revised code and unit testing

Hi @serenejiang Great job! I looked at the Travis error report, and found that it was due to that the variable numRemain was accidentally cropped into numRe. As long as it's changed back the test will go through. I think it will be the easiest for you to just copy and paste the original prototypeSelection.py to replace the one that is accidentally modified.

Coverage remained the same at 100.0% when pulling 06a1c9f3c92110e3ae8baacf5eb213ee1f4783c3 on serenejiang:dev into 413db4a540d77d5f59cac8f9627ed1a3c9490b39 on biocore:master.

Coverage decreased (-8.3%) to 91.72% when pulling ae13e06383a6c21bf367dc622a9e9a8ff35cfcd4 on serenejiang:dev into 413db4a540d77d5f59cac8f9627ed1a3c9490b39 on biocore:master.

Coverage decreased (-1.2%) to 98.837% when pulling 8469e54c3d44bf4aac63dc9ad76f85cfc6de18b5 on serenejiang:dev into 413db4a540d77d5f59cac8f9627ed1a3c9490b39 on biocore:master.

Coverage decreased (-1.2%) to 98.837% when pulling 8469e54c3d44bf4aac63dc9ad76f85cfc6de18b5 on serenejiang:dev into 413db4a540d77d5f59cac8f9627ed1a3c9490b39 on biocore:master.

Coverage remained the same at 100.0% when pulling 47012ecea5ef56f0ff12e7ce4b1896289c2d20cb on serenejiang:dev into 413db4a540d77d5f59cac8f9627ed1a3c9490b39 on biocore:master.

I sit with @serenejiang and saw here worked it out. Serene, awesome job! @sjanssen2 Would you like to take a look? Note: Serene basically re-implemented Jon's code.

@sjanssen2 Thank you for careful reading! @serenejiang Stefan has proposed many insightful comments. Could you please respond? I will be glad to help you.


No-data being tagged incorrectly?

Some of them are being tagged as -20000 instead of the default provided from the config file.

This happens under the inference.


neon_local: fix endpoint api to prevent two primary endpoints

Problem
neon_local endpoint subcommand currently allows creating two primary endpoints for the same branch which leads to shutdown of both endpoints
Refs #4959, #5426
Summary of changes
neon_local endpoint start new behavior

Fail if endpoint doesn't exist
Fail if two primary conflict detected

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

@koivunej could you pls review

Apologies on missing this. I did not consider anyone would attempt this since it seemed very non-trivial design issue, but thanks for your efforts so far. Let's see the test run.

Thanks @rmodpur and apologies for not noticing this earlier, as I mentioned, I was not thinking this could be done at all without big redesign which you have now managed not to do.

@koivunej thanks for the review, I have updated README to indicate cargo neon endpoint create must be run before cargo neon endpoint start

thanks for the review, I have updated README to indicate cargo neon endpoint create must be run before cargo neon endpoint start

Thanks, that was good spotting. We've been a bit busy debugging a too common test failure which this fix should prevent by failing fast.

(Do not worry about check-codestyle-rust-arm there is nothing there to fix -- the runners was just bad.)


question regarding space suit

I understand that the regular space suit has oxygen und hydrogen for the usage and it works well for me.  That works in the first place but i found out, that this armor modified in this way does not work against the slowness and mining fatigue buffs on some worlds as does the regular suit. Is there any way to work around that?

That's a bug on my side I think.  I'll get that fixed


⚠ Bofrost.at has degraded performance

In f3509df, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1631 ms

Resolved: Bofrost.at performance has improved in fe8f5df.


Hotfix/2.0.6 memory backend ets leaks

Fix for a memory leak in the timer reference table used by the memory backend when attempting to limit to a certain amount of used memory.
This will resolve RIAK-1576 (#1064) for the 2.0 branch - will need to forward-merge for 2.1/2.2

Going to cherry-pick these onto a branch from 2.0's HEAD as the deps actually work there.


Add add pandas_options in load_file

Description
closes: https://github.com/astronomer/astro-sdk/issues/1519
What is the current behavior?
currently, load_file do not have an option to pass the pandas-related param while reading file
What is the new behavior?
use load_options and pass the given values while reading files using the pandas path
Does this introduce a breaking change?
No
Checklist

[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

@pankajastro What sort of pandas do we want to pass using pandas_options?

@pankajastro What sort of options do we want to pass using pandas_options? is delimiter?

yes, currently delimiter, but in future maybe other params as well which pandas read_{csv, json} etc method accept.

@pankajastro I was a little concerned because if we keep adding the internal libs-specific parameters we will soon need to expose every database-specific or file type-specific parameter. We are exposing internal details to the end user, kinda violating the interface we have provided. Instead, since load files only have to deal with the file(s) and tables can we keep the parameters specific to tables and files? Like in this scenario, the delimiter is specific to CSV files, maybe we can move this parameter to File Object? WDYT?

@pankajastro I was a little concerned because if we keep adding the internal libs-specific parameters we will soon need to expose every database-specific or file type-specific parameter. We are exposing internal details to the end user, kinda violating the interface we have provided. Instead, since load files only have to deal with the file(s) and tables can we keep the parameters specific to tables and files? Like in this scenario, the delimiter is specific to CSV files, maybe we can move this parameter to File Object? WDYT?

I understand your concern and probably we will expose only limited param. We don't want to make File object messy either  so I closed https://github.com/astronomer/astro-sdk/pull/1225 there is some discussion on https://github.com/astronomer/astro-sdk/issues/482 too

Hi @dimberman Can you please re-review this PR


Change the keyword intent to set

set likely the best option but there could be something better.
I also think we should avoid the word "intent" in general in the codebase. For example, we would change IntermediateIntent to just Intermediate.

It's now predicate.


Fix: tag grapqhl

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.38%. Comparing base (0cebace) to head (065de22).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #19   +/-   ##
=======================================
  Coverage   90.38%   90.38%
=======================================
  Files          11       11
  Lines         312      312
  Branches       69       69
=======================================
  Hits          282      282
  Misses         29       29
  Partials        1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


bump strum 0.21 to 0.24

I use spdx-rs with clap.
clap depends heck v0.4.0,
strum 0.21 depends heck v0.3.3
warning[B004]: found 2 duplicate entries for crate 'heck'
   ┌─ /home/kazuk/sbom-ghr/Cargo.lock:56:1
   │
56 │ ╭ heck 0.3.3 registry+https://github.com/rust-lang/crates.io-index
57 │ │ heck 0.4.0 registry+https://github.com/rust-lang/crates.io-index

Thanks @kazuk! I'll release a new version with the updated dependency shortly.

@kazuk v0.5.1 is now released with the updated dependency.


Send MICROBE soil template to all collaborators

Description of the issue
Send the harmonised soil template to all collaborators, with brief instructions on how to fill and what is expected on certain fields.

Folder with template spreadsheet: https://drive.google.com/drive/folders/1Nx5-Y6NCP8mejZ3Fm0sxI1alY7TLobZG

The instructions are in the same folder as well

TBD: Create a MICROBE general soil sample (Current one is specific to the soil child samples) and send

First email sent - Preparing template

I have prepared a general soil template + another template that explains each of the fields, in detail, with recommended vocabullary etc - I will talk with Jeena on Monday and we can upload the files to sharepoint


Execution inconsistency after deployment with pyinstaller

Expected behavior and actual behavior.
Intersection implementation is faulty after deployment with pyinstaller, the same code without deployment works fine.
Steps to reproduce the problem.

Run code snippet (reproduction.py) and save result:

import math

import numpy as np
from shapely import geometry

if __name__ == "__main__":
    line_segment = geometry.LineString([(0.0, -10.0), (0.0, 10.0)])

    center = (0.0, 0.0)
    radius = 5.0
    circle = \
        geometry.LineString([[center[0] + radius * math.cos(alpha), center[1] + radius * math.sin(alpha)]
                             for alpha in np.linspace(start=0, stop=2*math.pi, num=100)])

    print(f"Line={line_segment.wkt}")
    print(f"Circle={circle.wkt}")

    intersection = circle.intersection(line_segment)
    print(f"Intersection = {intersection.wkt}")

Deploy script using pyinstaller

pyinstaller reproduction.py --onefile

Run deployed script and compare results

./dist/reproduction

Operating system
Ubuntu 19.04
Shapely version and provenance
1.6.4.post2 installed from PyPI using pip.
Works fine on 1.6.4.

@mieszkokl there's not enough information here. Which Python version? Which version of pyinstaller? Have you checked this issue tracker for other issues involving pyinstaller? What are the expected and actual results using pyinstaller? Can you report them here?

I'm going to close this. The entire category of errors involving dynamic loading of GEOS is going away in 2.0 and we won't be doing anything about any of them in the meanwhile.


No circle chart

Hi I can't seem to find a circle chart example or any points to the code? Is this left out?

1


Cadl refresh sdk script

https://github.com/Azure/azure-sdk-for-python/issues/28766
test locally: https://github.com/Azure/azure-rest-api-specs/pull/22229/checks?check_run_id=11131196810

/check-enforcer override


Maybe divide into ergo/base and ergo/errors?

And add ergo/slices.Chunks and some tests?

Maybe base can be called panic.

Fixed by 2d7b204.


 Make it optional

Hi,
as I was testing my comments I saw that the bad word filter seems to be way too strong. It blocks comments containing some normal words like "hell".
I think it's somehow weid that a comment containing "hell" get blocked and all I can do is to display an error like: Bad language used! Please polite your comment...\",\"content\":{\"original\":\"hell\. It's pretty thin line what' good and what's no. This automatic filter could be a super way to handle very abusive comments but I thinks it is rarely the case and it is better to moderate comments by hand after they got posted. I would love to have an option to disable the bad-word filter and manage the comments myself. I think I would be better doing so than automatically blocking legit comments. It might be also a case that having comments with bad words isn't necessarily a bad thing. It would say it depends on the context and your audience.

Yeah, it sounds reasonably to make it that way. The only thing I don't know quite well is how complicated and time consuming this would be, so I would suggest to split the task.
Optional deactivation of the filter seems from my perspective easier to implement and perhaps could be a factor for more people, while the second one is rather nice to have. Although it could be possibly a thing for new user considering if they should use this plugin.

Yeah, it sounds reasonably to make it that way. The only thing I don't know quite well is how complicated and time consuming this would be, so I would suggest to split the task.
Optional deactivation of the filter seems from my perspective easier to implement and perhaps could be a factor for more people, while the second one is rather nice to have. Although it could be possibly a thing for new user considering if they should use this plugin.

Agreed. ETA is Monday / Tuesday.

Agreed. ETA is Monday / Tuesday.

@kwiat1990 version 1.0.1-beta.3 contains what you expect. Refer to the updated Readme.md please.

@kwiat1990 version 1.0.1-beta.3 contains what you expect. Refer to the updated Readme.md please.

Cool, later in the week I should be able to test it. Thanks a lot these fast adjustment!

Cool, later in the week I should be able to test it. Thanks a lot these fast adjustment!

Sure, once it will be satisfying please close the ticket.

Sure, once it will be satisfying please close the ticket.

The new flag for enabling/disabling bad words filter does what it should. I have tested it and it works perfectly fine in both cases.

The new flag for enabling/disabling bad words filter does what it should. I have tested it and it works perfectly fine in both cases.


Add mod menu to configure stat settings

Is your feature request related to a problem? Please describe.
I don't like editing JSON by hand because it's dumb, 1.5 mod menus are cooler and I want one
Describe the solution you'd like
Set up a menu system that will let me configure layout settings. Ideally, 1 page per stat layout

make pause menu keybind configurable also

reolved by 0e850729d70179593e488265055b11e81d4275f5 and 71b56c37094199bd23719803cf30bf309e055013


GridView summary totalCount is not formatted in v.2.0.7. Incorrect thousands separator.

What steps will reproduce the problem?
Render GridView with totalCount >= 1000.
What is the expected result?
Summary text: "Showing records 1-50 of 26 019".
What do you get instead?
Summary text: "Showing records 1-50 of 26,019" (Показаны записи 1-50 из 26,019).
Additional info
There used to be a correct separator in v.2.0.4 before I updated to v.2.0.7.

Q
A

Yii version
2.0.7

PHP version
5.5.9

Operating system
Any

Language
RU

What's Yii::$app->language set to?

I've got 'language' => 'ru' in config file.

Could you try with ru_RU?

this doesn't help.

Which ICU data version do you have? Which intl version?

Thanks a lot, Alexander! I've installed php5-intl and now I have a proper separator!


Update map on the basis of coordatinates

Hi Jeffrey can you just tell me how the map will be marked when a user enter he coordinates in the field.
Thank you!

You need to set the Synchronize with Item attribute to the name of a text field on the page. When the user enters coordinates into the field, the map should update.

How to do it can you just elaborate?

Create a text field item. Give it a name, e.g. P1_COORDS.
On the Attributes on your map plugin region, set the attribute Synchronize with Item to the name of the item, e.g. P1_COORDS.

Hi Jeffrey,
I have passed the item but still map is not showing the particular destination. Please suggest

Please build an example on apex.oracle.com and I can take a look.
Thanks

https://apex.oracle.com/pls/apex/f?p=36814:1:12099810551934:::::
APPLICATION ID : 36814
WORKSPACE : TI
user name<EMAIL_ADDRESS>PASSWORD : Akshita2015
Page no : 1
Thank you for your help
Regards

Thanks. It works for me - for example, when I enter coordinates like this:
-32.49123028794758,115.828857421875
It shows a map with "Nambeelup Rd" nearby.

Have you done any modifications on that particular page?

Hi Jeffrey,
It is working now like a charm. Actually, what I did is pass the static id in region,however when I remove the static id it is working perfectly.
Thank you so much for your time and assistance.
You are doing a great job.


CB-6788 Check right - skip only read, back to account check on cred

I removed entitlement check from hasRights because it is used for usersync only (which is not checking for read rights) and other calls from code of hasRights (which is resource based part of authz framework) is not used in 2.20.


About fixing farthest image's pose

Hello, I have a question about post optimization in reconstruction task.
https://github.com/zju3dv/DetectorFreeSfM/blob/4a370f186ece48ed73c441283b54caf2f9aeec08/src/post_optimization/post_optimization.py#L183-L187
https://github.com/zju3dv/DetectorFreeSfM/blob/4a370f186ece48ed73c441283b54caf2f9aeec08/src/sfm_runner/sfm_model_geometry_refiner.py#L47-L49
In the code above, in reconstruction case, when you run COLMAP's incremental_model_refiner, the command get inputs of fixing the pose of images.
Of course in triangulation task, all given pose would be fixed in the bundle adjustment, but I'm curious whether the fixing farthest image's pose is effective or not in reconstruction task.
Is there any reasonable reason to fix some images?
As far as I know, the incremental_model_refiner doesn't need to be fed with image_list of fixed pose.
Thanks :)

Hi, our modified incremental_model_refiner works similarly to the global bundle adjustment. Therefore, to avoid the large pose drift during optimization in SfM, we find the farthest two images and fix the 6DoF of one image's pose, and one dim of the other image's, following the strategy in COLMAP's global BA process. The detail can be found here. We find without this constraint, the scales and coordinates of recovered poses will different significantly compared with input coarse poses.


Add haproxy to requirements.yml, add example (IDR-0.3.1)

This depends on https://github.com/openmicroscopy/ansible-role-haproxy.git which doesn't currently exist, so for initial testing you'll have to change that line in requirements.yml to https://github.com/manics/ansible-role-haproxy (currently in process of being transferred to @joshmoore)

Transferred to https://github.com/openmicroscopy/ansible-role-haproxy

Conflicting PR. Removed from build MANAGEMENT_TOOLS-merge#1096. See the console output for more details.
Possible conflicts:

PR #174 jburel 'Scripts role'

ansible/Vagrantfile

PR #196 manics 'Add Vagrantfile for IDR (IDR-0.3.0)'

ansible/Vagrantfile

Conflicting PR. Removed from build MANAGEMENT_TOOLS-merge#1097. See the console output for more details.
Possible conflicts:

PR #174 jburel 'Scripts role'

ansible/Vagrantfile

PR #196 manics 'Add Vagrantfile for IDR (IDR-0.3.0)'

ansible/Vagrantfile

Closing until 174 and 196 are cleared up. If may have some commits of my own, in which case I'll just open a new PR.

Note: from my side, happy for this to go in as soon as conflicts are resolved.


added simpleEnum annotation

/claim #506
Throws exception if used where not applicable and it is added automatically if it is indeed a simple Enum.

@pablf so is the intention to automatically insert the simpleEnum into the derived schema? I think in the original issue I wanted to control the application of the annotation (ie make this manual process) so that users of downstream libraries like zio-dynamodb can choose the encoding  they want eg new projects may want the default tagged union encoding and projects that need to integrate with legacy databases say could use this new annotation.

And if we included an automaticallyAdded: Boolean in the annotation's definition? What do you think?

Now it should pass the tests.
@googley42 I have added automaticallyAdded. If you want to use you can use @simpleEnum and it will generate a simpleEnum(false) annotation.

@pablf  so I think the original intention of the issue was just to create a standard annotation for use by downstream libraries - we already have one for zio-dynamodb - but the the thought was to standardise it. The fact that the JSon codec already defaults to this behaviour probably means that there is no extra work required for derive gen macro - what do you think @jdegoes ?

@pablf

Maybe it would also be interesting for a Schema to know if it is a simple Enum, so each one of its codecs can use that information as desired, instead of checking in each codec if it is really a simple Enum

Ah yes - I get this now - this is great idea and will simplify the codecs of all downstream libs!
The only thing I want to confirm is that will a manually created @simpleEnum override the automatically generated one? I suspect this is case and if so do you think it would be a good idea to have a unit test for this?

@googley42 Then great! Yes, that would be the expected behaviour. I have added the tests to ensure that it's like that in the future.


Split up WindowDesc to allow sub-windows and window reconfiguration.

This is extracted from sub-windows.
It allows reconfiguration of windows and paves the way for construction of non-top level ones.

I'll fix some bits later/tomorrow - a lot of the docs are just moved around from WindowDesc, I don't think fixing the content of those docs really has much to do with this PR. Some things are public because they need to be for subwindows I think (which has to construct windows slightly differently from the Druid side - ie not using WindowDesc).

my strategy around pub would be to make things non-pub now, and then change them to pub in the follow-up PRs, as they're needed; this is a nice forcing-function, so that we are only marking pub the things that need to be.


Updated Brackets Extensibility - from brackets/src/extensibility/node to brackets-registry/deps

We should update the deps at Brackets first.

You mean merging this first, https://github.com/adobe/brackets/pull/12933 ?

In my opinion, we shouldn't have a tar file here. The more transparent way would be just to create a folder here like lib-brackets or something and copy the files from brackets there, with a note that this file is a copy of https://.... in adobe/brackets. I don't think there's any bonus of having this archive here. Dependencies can be extracted to root package.json

Yeah using folder instead of tar would be better. I will add the steps in the wiki.
Also once we are done with upgrading node in the brackets-registry prod server, then we can merge https://github.com/adobe/brackets/pull/12933 and then I will pull the latest brackets-extensibility from brackets to registry.

Why don't we just yank the dependency into it's own repo, publish it to npm and install it with npm?

That's probably the best solution :)

If this PR is a prerequisite to update the extensibility/node deps, I'm fine with it.

I am fine with this approach for now as it can complement the extensiblity dependency management PR by  @zaggino. I am merging this PR, so that I can merge the other PR by @zaggino as well.


Cannot use same routing code for multiple operations

Cannot use same routing code for multiple operations
It says record already exists

This is a bug in routing maintenance class and subclass.   It is not allowing more than one operation to be created per routing master ID.   This bug has been corrected...and will be provided in download release 6.0.3.

I have uploaded the 6.0.3 release download files.   Since this is a core patch, download the blueseer.jaronly.zip file.   There is instructions inside to apply the patch.

Both windows and linux 6.0.3 releases have been uploaded.  Closing

Within item maintenance, routing dropdown is showing duplicate routing code


Quote view names

Closes #172

I tried removing this and it ended up causing double quoting because we'd quote on the way out of the db and when it goes in. I think it's only code, but it does break the scheme dump.

On Feb 9, 2017, at 7:34 PM, Derek Prior<EMAIL_ADDRESS>wrote:
@derekprior commented on this pull request.
In lib/scenic/adapters/postgres/views.rb:

@@ -54,6 +54,11 @@ def to_scenic_view(result)
materialized: result["kind"] == "m",
)
end

   def pg_identifier(name)

     return name if name =~ /^[a-zA-Z_][a-zA-Z0-9_]*$/

Can we not safely quote the identifier in any case?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Tesla Component stopped working in v0.96.x (and v0.97.0)

Home Assistant release with the issue:

0.97.0
Last working Home Assistant release (if known):
0.95.x
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Component/platform:

https://www.home-assistant.io/components/tesla/
Description of problem:

Seems that since the 0.96.0 release the tesla component stopped working?
Maybe related to the changes in the climate component?
All tesla sensors (not only tesla climate sensor) show the "entity not available" message in lovelace UI
0.97.0 also produces same issues
I don't see any tesla related issues in the home assistant log

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
# Tesla configuration.yaml entry
tesla:
  username: !secret tesla_username
  password: !secret tesla_password
  scan_interval: 3600

Traceback (if applicable):
I don't see any tesla related issues in the home assistant log

Additional information:
Issue confirmed by @G8YTZ in: #25247 https://github.com/home-assistant/home-assistant/issues/25247

Same here, 0.96 and 0.97 all components "Entity not available"

Sorted it! The entity names have changed, basically remove the VIN number from the entity name. Problem is, what if you have more than one Tesla?

ah great @G8YTZ , will give it a try! tx :)

I also find it a bit weird to remove the VIN number from entity names. For one, it broke all of my history in InfluxDB, and then also the obvious (as it seems?) issue when you have more than 1 Tesla.

They did a similar thing with the condition monitoring of my Samsung Printer where the identity of each printer had the ip address as part of the entity, now they have done something else and I just get the toner levels reported as “unknown”
What’s really bugging me is that the have totally messed up the Lovelace thermostat card to the point it no longer works with KNX, being the largest building automation standard.
I love the Home Assistant project, but the constant breaking changes is getting tiresome. High time we have an LTS fork where releases keep entities the same and just features are added and right now the solution is totally unsupportable if you want to offer it as a customised solution.

Weeks later, nothing yet?

@trombonekenny, I attempted to revert @pvizeli 's changes around entity_id through a custom component override, however the entities didn't change their names back to include VIN, so HA may have been refactored to do entity naming a different way, I don't know and don't really have time to play with it...  All my Tesla stuff is still broken, because I believe we need to get VIN back in there for multi-car households.

For a one-Tesla household its not a massive issue, just I wish they would think things though things through before they make changes, a similar change was made to the Samsung Printers with the IP Address.
Definitely need a LTS version, as right now the solution is not supportable or usable as a service.I’m still gnashing my teeth over the KNX Thermostat Operations mode cock-up.
I’ll give HA some time as we are still on pre- v1.0 releases and the solution stands a real chance of becoming the best out there by far and I know a lot of people are spending a lot of time getting a superb solution out there. I am very happy to pay for Nabu Case that helps fund the ongoing development.
Justin
www.g8ytz.com http://www.g8ytz.com/
Sent from my Macbook

On 17 Sep 2019, at 15:06, Dave Mussulman<EMAIL_ADDRESS>wrote:
Weeks later, nothing yet?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/home-assistant/home-assistant/issues/25809?email_source=notifications&email_token=AIR3TT5B6OZGWIRNVBPLY7DQKDP7BA5CNFSM4IKUGHC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD64URWI#issuecomment-532236505, or mute the thread https://github.com/notifications/unsubscribe-auth/AIR3TT5ZMWARBDF2RLXFB5DQKDP7BANCNFSM4IKUGHCQ.

@pvizeli Can you explain the reason for removing the ENTITY_ID_FORMAT? I'm about to work on this component again and would revert your change as it is a problem for multi-car households. The next version of the teslajsonpy will cut the amount of the VIN being shown if that was the concern.


Use the current thread's classloader for classes

Switch from using the caller's classloader to using the current thread's
classloader. Using the caller's classloader results in subtle issues where
if a test is spawned on a different thread, you will not be able to find
the Substitutor, even though it is present.
This will fix
#6923 and
quarkusio/quarkus#32627

@eddumelendez do I need to keep merging in from main or will you handle that when you go to release it?

I'm just waiting for the last check to pass and I will merge it.

Thanks for your contribution, @snowe2010 ! This is now in main branch and it will be part of the next release.

Wooh! Thank you so much! Glad I could help!

@snowe2010 this fix is part of 1.18.1

Thank you very much!


Traefik serves traffic on port 80 over https

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
Hello, I have inherited traefik deployment running on kubernetes, seems like installed using helm chart traefik-10.3.6, unfortunately I have no values file or anything, but I can view deployment and the args.
What did you see instead?
Everything has been running smooth until we noticed that port 80 is accessible using https, so basically accessing https://example.com:80/ opens up default 404 page not found
From traefik access.log -
{"ClientAddr":"<IP_ADDRESS>:55780","ClientHost":"<IP_ADDRESS>","ClientPort":"55780","ClientUsername":"-","DownstreamContentSize":19,"DownstreamStatus":404,"Duration":203245,"OriginContentSize":19,"OriginDuration":28785,"OriginStatus":404,"Overhead":174460,"RequestAddr":"example.com:80","RequestContentSize":0,"RequestCount":795,"RequestHost":"example.com","RequestMethod":"GET","RequestPath":"/","RequestPort":"80","RequestProtocol":"HTTP/2.0","RequestScheme":"https","RetryAttempts":0,"StartLocal":"2024-06-26T12:43:00.08648126Z","StartUTC":"2024-06-26T12:43:00.08648126Z","TLSCipher":"TLS_AES_128_GCM_SHA256","TLSVersion":"1.3","entryPointName":"web","level":"info","msg":"","time":"2024-06-26T12:43:00Z"}

What version of Traefik are you using?
Docker image is traefik:2.5.3
What is your environment & configuration?
- --global.checknewversion
- --global.sendanonymoususage
- --entryPoints.metrics.address=:9100/tcp
- --entryPoints.traefik.address=:9000/tcp
- --entryPoints.web.address=:8000/tcp
- --entryPoints.websecure.address=:8443/tcp
- --api.dashboard=true
- --ping=true
- --accesslog
- --accesslog.filepath=/data/access.log
- --accesslog.fields.defaultmode=keep
- --accessLog.fields.names.RequestHost=keep
- --accesslog.format=json
- --metrics.prometheus=true
- --metrics.prometheus.entrypoint=metrics
- --providers.kubernetescrd
- --providers.kubernetesingress
- --api.dashboard=true
- --log.level=INFO
- --providers.kubernetesingress.ingressclass=traefik-internal
- --serversTransport.insecureSkipVerify=true
- --providers.file.filename=/traefik/traefik.yaml

The dynamic config file /traefik/traefik.yaml
tls:
  options:
    default:
      minVersion: VersionTLS12
      sniStrict: true
      cipherSuites:
        - TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
        - TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
        - TLS_AES_128_GCM_SHA256
        - TLS_AES_256_GCM_SHA384
        - TLS_CHACHA20_POLY1305_SHA256
        - TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

Those are the IngressRoutes for this specific host (but happens on all the hosts)
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  annotations:
    meta.helm.sh/release-name: example
    meta.helm.sh/release-namespace: example-test
  labels:
    app.kubernetes.io/instance: example
    app.kubernetes.io/managed-by: Helm
  name: example-http
  namespace: example-test
spec:
  entryPoints:
  - web
  routes:
  - kind: Rule
    match: Host(`example.com`)
    middlewares:
    - name: example-redirect
    services:
    - name: nginx-app
      port: 80
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  annotations:
    meta.helm.sh/release-name: example
    meta.helm.sh/release-namespace: example-test
  labels:
    app.kubernetes.io/instance: example
    app.kubernetes.io/managed-by: Helm
  name: example
  namespace: example-test
spec:
  entryPoints:
  - websecure
  routes:
  - kind: Rule
    match: Host(`example.com`)
    services:
    - name: nginx-app
      port: 80
  tls:
    options:
      name: tlsoptions

And here is the Middleware
apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  annotations:
    meta.helm.sh/release-name: example
    meta.helm.sh/release-namespace: example-test
  labels:
    app.kubernetes.io/managed-by: Helm
  name: example-redirect
  namespace: example-test
spec:
  redirectScheme:
    permanent: true
    scheme: https

But seems like it does not even get to my ingressroute rule or any router. I would like to understand why does it even serve https over port 80 and how could I disable this?
Thanks!
If applicable, please paste the log output in DEBUG level
When enabling --log.level=DEBUG nothing shows up at all when accessing https://example.com:80

Ok so when I edit example ingressroute and add - web to entryPoints, the https://example.com:80 now opens up my web app as it would when using just https://example.com
............
spec:
  entryPoints:
  - websecure
  - web
  routes:
,.........

What I still quite dont understand why would it think of https:// as a web entrypoint?

Hi @ghorio,
There is a PR that was merged last week by kevinpollet - see https://github.com/traefik/traefik/pull/10989
The next release of 2.x and 3x should contain this PR and resolve this issue we are facing, just waiting on that now.
👍

It's seems to be a duplicate of https://github.com/traefik/traefik/issues/10818


Merging of areas defined in strategy-options and other areas of Home Assistant

Is your feature request related to a problem? Please describe.
Currently creating area cards for areas, defined in strategy-options, has precedence over creating cards for areas defined in Home Assistant. In other words, only cards of areas in the config are created or only cards of Home Assistant areas are created.
Describe the solution you'd like
I'd like to propose the following:

Create cards for Home Assistant areas with a default config.
Entries in the strategy-options with the same area_id (instead of name), override the default config.
Explicit exclusion of an area by a property in strategy-options.

This way we get a merge of default and custom cards of Home Assistant areas.
Areas defined in strategy-options must exist in Home Assistant anyway.
E.g.
  options:
    areas:
      - family_room:
          name: Family Room
          icon: mdi:sofa
          icon_color: green
      - bedroom:
          hidden: true
          name: Fun Place
          icon: mdi:bed-outline
          icon_color: red

Describe alternatives you've considered
Define configurations in the strategy-options for all areas, just to customize a few of them.
This means defining the same configuration for a lot of areas which actually where meant to be untouched.
Additional context

Hey,
Yes I totally agree with this change. The hidden attribute is also a good idea.
Can you explain your motive behind using area.id instead of area.name for the definition? The main motivation for me to use area name is because it's a bit more human friendly and you can easily remember the names rather than area.ids.

In general, the id is unique and guaranteed to always identify the same entity, while a name can identify multiple entities.
E.g. You can name a several lights the same (like Ceiling Light), but they always have another id (ceiling_light_1, ceiling_light_2, etc.).
However, it could be safe to identify areas by name. I think for those entities, the name has to be unique also.
I suggested it just for creating a convention for if we ever need to setup similar configurations for the other kind of entities.

While dealing with this request, I really think it's better to switch from name to id.
Besides being it a proper convention (IMHO), this will allow us to override all properties, including the name, of an area throughout the different views.

Yeah it is more conventional and is the proper way of doing it.
If you think the option having to use area.id or area.name| is valuable then go ahead, otherwise moving to area.id` is the right way

Option 1 does seem like the best idea. Users still have the option of setting the entity status to hidden.


chore: create cache of compilations for all services to use

Closes #61

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Adding list_verified_email_addresses and testing

Coverage decreased (-0.2%) to 93.262% when pulling 2a65f40a194854aef6337357cc29ba5d55b4c2ef on fdfk:verify_email into 28b1d99100aa568a265fe3382e3adcdccf9b8de6 on spulec:master.

Great work, @fdfk! Thanks for the tests and the feature, this looks really good. Welcome to Moto!


Burn-in - Automate pre-release - new nodes

As a besu dev, I would like a consistent, low-friction, high signal process to confirm a potential release candidate is good enough for brand new Ethereum users.
An RC (release candidate) can be defined by any git tag or sha, allowing the process to be used with maximum flexibility.
When we burn-in / regression test an RC, we do the following:
Deploy brand new client instances with no existing data, which need to synchronize with their respective network. These existing nodes are currently running on Consensys managed infrastructure. They need to account for the sepolia, holesky, and mainnet networks, and each network should be tested against all consensus layer clients.

Confirm that clients synchronize to the head of their network, without need for manual intervention.
Confirm that time taken to reach head is within established tolerances of baselines, per network.
Confirm that clients establish peers and maintain them within established tolerances of baselines.
Once through the sync process, should test for regressions defined in #6638

This is a very manual process, which should be automated.

Including a regular fullsync of nodes during the testing cycle would be good. Some nasty bugs e.g. self destruct Bonsai bug were caught by doing fullsync testing on testnets.

get grafana URL as an output from starting the burn-in nodes


Merge SecureRandom into Random and Random::System

As per https://github.com/crystal-lang/crystal/pull/4882#issuecomment-325023124 keeping SecureRandom is a source of duplication and of confusion. Despite the explicit naming, there are contradictory understandings as what should be the source for secure random numbers in different contexts: SecureRandom, Random::System or Crystal::System::Random?
In order to avoid this pitfall, I propose to clarify that:

Random::System is the source for cryptographically secure random numbers;
Crystal::System::Random is an internal abstraction to feed Random::System (i.e. nothing else must use it).
SecureRandom shall... be removed, and its usage replaced with Random::System throughout stdlib.

Following these, this patch:

moves #base64, #urlsafe_base64 and #uuid methods from SecureRandom into Random;
implements generic Random#random_bytes methods;
moves the #random_bytes(buf) method from SecureRandom into Random::System;
replaces SecureRandom and Crystal::System::Random usages in stdlib to their equivalent calls on Random::System.

A benefit is that all PRNG implementations may benefit from #urlsafe_base64 or #uuid for example, but these methods should only be used with a cryptographically secure PRNG only (e.g. Random::System, Random::ISAAC, ChaCha20, ...). This is stated obviously in the documentation of Random and each concerned method.
That being said, using an insecure but very fast and deterministic PRNG may be suitable in test suites, which is now possible, just by switching the PRNG. Switching from the system source, using a cryptographically secure PRNG (correctly seeded from the system source) is now also possible.

I deeply apologize to @oprypin for not understand the reality of #3434 before :bowing_man:

Looks like the formatter failed.

Indeed. I pushed again.

I'm not sure if it makes much sense to split this change into two commits.

Having 2 commits may help reviewing each patch, avoiding remove/renamings noise. Yet, I agree we should "squash and merge" into a single one if we merge this.

Linux 32-bit crashed again on Travis?

Is this Pull request breaks seed code on #4675?

Probably it will break, if will be merged before.

Thanks for accepting my changes!
Now someone should take a look at random_bytes again.
As a note, if these commits are squashed during merge, authorship info will be lost. So better apply whatever level of squashing is wanted manually.

I like this, but why not call it Random::Secure instead of Random::System?

I kept the Random::System naming since that's what it is: use the system PRNG that happens to be secure. I guess libsodium using this naming also influenced my into keeping it, but Random::Secure sounds good.
If others agree, I'll change the naming, I shall change the specs to expect a fixed result (for base64, urlsafe_base64) too.

If someone could review @oprypin's rewrite of the generic Random#random_bytes that would be sweet.

I just suggest using Random::Secure because if I wanted a secure RNG source I would search "secure" and would never think "system" implies that. If we are sure all "system" RNGs are secure, then I'd say we use the name Secure. Otherwise we can use System but say "system should be secure, but it's not guaranteed".

I think providing the system RNG is pointless if it's not secure, so we should call it Random::Secure and always use the most secure RNG on each system. For 99% of platforms that should be the OS's RNG but I don't think we should make the guarantee that it's the OS rng.

@ysbaddaden, it seems like the rename to Random::Secure is agreed upon, and not much else is blocking this.
So, could you rename that? And rebase this to remove merge commits and squash the commits in the preferred way, because I don't think GitHub will automatically do the right thing in this case

All done. Waiting for CI to run.


Offer an array-based implementation of OsmMap

This pull request builds on top of #20
This is the first major step towards my goal of splitting very large input files.
OsmMap, the data structure storing the list of tiles for each OSM element, is responsible for the largest fraction of Mapsplit's memory consumption. Therefore, this pull request introduces an alternative implementation of OsmMap. Unlike the existing implementation HeapMap, the new ArrayMap has a high, but fixed memory consumption. Shared functionality of HeapMap and ArrayMap is pulled up into an abstract parent class.
The basic idea of ArrayMap is very simple: It is a huge array of primitive long values that uses OSM IDs as the array index. The only complication is that Java's size limit for arrays forces me to use more than one array, but it's still a pretty straightforward implementation.
Of course, this data structure is wasteful for a small input file – it uses the same amount of memory whether you split Liechtenstein or the entire planet. Therefore, using ArrayMap is opt-in through a new command line parameter, --max-ids, which is also used to pass in the current maximum ids for nodes, ways and relations. (This could eventually be replaced with automatic detection of the maximum ids in the input file at the cost of an extra read-through of that file.)
On a standard Hetzner Cloud instance with 128 GB of memory, I was able to split the DACH Geofabrik extract in about an hour using Mapsplit with my ArrayMap implementation. With even larger input files, the other data structures grow in size and OsmMap is no longer the only factor I have to consider for memory consumption. I plan to tackle these other data structures in future pull requests.

Pro memoria this had a minor issue https://sonarcloud.io/project/issues?id=mapsplit&resolved=false&types=BUG (my bad for not running sonar before merging), we can fix this when all the PRs have been merged though.


Ansible failed to complete successfully. reopening #1065

Issue Type

Bug Report / Support Request

Your Environment
Vagrant 1.9.1
VirtualBox 5.1.10r112026
ansible <IP_ADDRESS>
  config file =
  configured module search path = Default w/o overrides

Your OS

macOS (10.10.5)

Full console output
https://gist.github.com/gettysburger/5293989dab70be8548db4365bf5386bc
Summary
In issue #1065 I tried to spin up a fresh instance and got an Ansible error. You recommended that I upgrade Ansible and that worked for that instance. Today I tried to spin up another fresh instance and got the same error, even though I have the latest Ansible.
Thanks,
Stephen

I think I may have figured it out. I forgot to set "build_composer_project: false"

Yes, that was it. I'm a dope. Sorry to waste your time. Great software Thanks!

Ha, no problem!


Support Exchange Online

Describe the solution you'd like
Support connections to Exchange Online
Additional context

support connections to Exchange Online / EOL
installing EOL modules if necessary

implemented dd058dbe146a788c7026980491f82e5eb757633e


feat(perception): add lidar_detection_model option

Description

add lidar_detection_model option
Tests performed

ros2 launch autoware_launch logging_simulator.launch.xml map_path:=/home/kosuke55/data/map/bs/ vehicle_model:=lexus sensor_model:=aip_xx1 rviz:=true perception:=true

change to apollo
<arg name="lidar_detection_model" default="apollo" description="options: `centerpoint`, `apollo`, `pointpainting`, `clustering`"/>

check apollo works instead of centerpoint
~/auto-evaluator.murooka (main %=)
$ ros2 topic list |rg apollo
/perception/object_recognition/detection/apollo/objects
/perception/object_recognition/detection/apollo/objects_with_feature
/perception/object_recognition/detection/apollo/validation/objects
~/auto-evaluator.murooka (main %=)
$ ros2 topic list |rg center
/sensing/radar/front_center/detected_objects
/sensing/radar/front_center/filtered_objects
/sensing/radar/front_center/from_can_bus
/sensing/radar/front_center/noise_objects
/sensing/radar/front_center/objects_raw
/sensing/radar/front_center/scan_raw
/sensing/radar/front_center/tracked_objects

<arg name="centerpoint_model_name" default="centerpoint" description="options: `centerpoint` or `centerpoint_tiny`"/>

[component_container_mt-1] [I] [TRT] Input filename:   /home/kosuke55/autoware_data/lidar_centerpoint/pts_voxel_encoder_centerpoint.onnx

<arg name="centerpoint_model_name" default="centerpoint_tiny" description="options: `centerpoint` or `centerpoint_tiny`"/>

[component_container_mt-1] [I] [TRT] Input filename:   /home/kosuke55/autoware_data/lidar_centerpoint/pts_voxel_encoder_centerpoint_tiny.onnx

Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@miursh want to keep these parameters only in autoware.universe
https://star4.slack.com/archives/C03S84LDJGG/p1707998958152429?thread_ts=1707985773.124859&cid=C03S84LDJGG


Admin Panel - Clear all filters functionality

Problem description
It would be nice to implement functionality where a user can clear filters/set filters to default.
Requirements
Exact requirement for the product - what needs to be done?
Definition of done
A user can clear applied filters in the Admin panel by clicking the 'Clear Filters' button.
Acceptance criteria
When a user with access to the Admin panel navigates to the Admin panel,
Then a user sees clickable the 'Clear filters' button.
Then a user enters any values into the filters fields and clicks on the 'Clear filters' button.
And a user should be able to clear all values entered before.

We have to change the label for the clear button
Let's make it 'Clear filters' instead of 'X'
The functionality works as expected.

QA PASSED. It works as expected.

This ticket was closed on March 18th


To enable command queueing, I placed dtparam=sd_cqe inside /boot/firmware/config.txt and rebooted.
Before
pi@pi5:~ $ dmesg | grep mmc0
[    2.546753] mmc0: SDHCI controller on 1000fff000.mmc [1000fff000.mmc] using ADMA 64-bit
[    2.652792] mmc0: new ultra high speed SDR104 SDXC card at address aaaa
[    2.659679] mmcblk0: mmc0:aaaa SN256 238 GiB
[    2.668229] mmcblk0: mmc0:aaaa SN256 238 GiB (quirks 0x00004000)

TODO PASTE BENCHMARK RESULT
After
pi@pi5:~ $ dmesg | grep mmc0
TODO PASTE RESULT

TODO PASTE BENCHMARK RESULT

GREAT benchmark, thank you Jeff - did not know of iozone. Going to test
SD, eMMC and NVMe on the Banana Pi BPi-F3 too now!
I should submit more SBC specs/tests at some point, but I've been pretty
lazy sorry. Ones I've recently tested, or have here to test;
Debix Model C
Milk-V Meles
Radxa CM5 Lite
BPi-F3
Radxa Fogwise
Luckfox Pico Max
Luckfox Pico Ultra
If any you'd like sooner or have use for, just let me know.
Cheers
------ Original Message ------
From "Jeff Geerling" @.>
To "geerlingguy/sbc-reviews" @.>
Cc "Platima" @.>; "Comment"
@.>
Date 8/07/2024 06:37:49
Subject Re: [geerlingguy/sbc-reviews] Raspberry Pi 5 model B (Issue #21)
Using the following benchmark:
wget https://raw.githubusercontent.com/geerlingguy/pi-cluster/master/benchmarks/disk-benchmark.sh
chmod +x disk-benchmark.sh
sudo MOUNT_PATH=/ TEST_SIZE=1g ./disk-benchmark.sh
To enable command queueing, I placed dtparam=sd_cqe inside
/boot/firmware/config.txt and rebooted.
Before
@.***:~ $ dmesg | grep mmc0
[    2.546753] mmc0: SDHCI controller on 1000fff000.mmc [1000fff000.mmc] using ADMA 64-bit
[    2.652792] mmc0: new ultra high speed SDR104 SDXC card at address aaaa
[    2.659679] mmcblk0: mmc0:aaaa SN256 238 GiB
[    2.668229] mmcblk0: mmc0:aaaa SN256 238 GiB (quirks 0x00004000)
TODO PASTE BENCHMARK RESULT
After
@.***:~ $ dmesg | grep mmc0
TODO PASTE RESULT
TODO PASTE BENCHMARK RESULT
—
Reply to this email directly, view it on GitHub
https://github.com/geerlingguy/sbc-reviews/issues/21#issuecomment-2212599505,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADIYAQBHBPWKSO7N4ITVTRDZLG7L3AVCNFSM6AAAAAA5KNQMO6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJSGU4TSNJQGU.
You are receiving this because you commented.Message ID:
@.***>

Late to the game as I just saw that the Pi 5 supports Command Queueing.
I only had two A2 cards laying around.
Samsung Evo 128gb A2, doesn't seem to be supported, no mmc0: Command Queue Engine enabled, 31 tags after adding dtparam=sd_cqe and no difference in speed before and after.
SanDisk Extreme 64gb A2, this card worked
before
Run 1
prepare-file;0;0;30714;59
seq-write;0;0;74346;18
seq-read;40261;9;0;0
rand-4k-write;0;0;4175;1043
rand-4k-read;9829;2457;0;0
Sequential write speed 74346 KB/sec (target 10000) - PASS
Random write speed 1043 IOPS (target 500) - PASS
Random read speed 2457 IOPS (target 1500) - PASS
After
prepare-file;0;0;39942;78
seq-write;0;0;29942;7
seq-read;92077;22;0;0
rand-4k-write;0;0;11645;2911
rand-4k-read;24220;6055;0;0
Sequential write speed 29942 KB/sec (target 10000) - PASS
Random write speed 2911 IOPS (target 500) - PASS
Random read speed 6055 IOPS (target 1500) - PASS

Raspberry Pi is working on some Pi SDRAM timing adjustments, which benefit both the Pi 5 and Pi 4.
I've been re-testing things like Geekbench (see linked blog post for those results), showing an 8-20% speedup depending on the specific benchmark. HPL also benefits, and here are tinymembench results:
tinymembench v0.4.10 (simple benchmark for memory throughput and latency)

==========================================================================
== Memory bandwidth tests                                               ==
==                                                                      ==
== Note 1: 1MB = 1000000 bytes                                          ==
== Note 2: Results for 'copy' tests show how many bytes can be          ==
==         copied per second (adding together read and writen           ==
==         bytes would have provided twice higher numbers)              ==
== Note 3: 2-pass copy means that we are using a small temporary buffer ==
==         to first fetch data into it, and only then write it to the   ==
==         destination (source -> L1 cache, L1 cache -> destination)    ==
== Note 4: If sample standard deviation exceeds 0.1%, it is shown in    ==
==         brackets                                                     ==
==========================================================================

 C copy backwards                                     :   6345.9 MB/s (0.4%)
 C copy backwards (32 byte blocks)                    :   6247.0 MB/s
 C copy backwards (64 byte blocks)                    :   6250.1 MB/s
 C copy                                               :   6138.4 MB/s (0.1%)
 C copy prefetched (32 bytes step)                    :   6144.8 MB/s
 C copy prefetched (64 bytes step)                    :   6146.3 MB/s
 C 2-pass copy                                        :   5727.1 MB/s (0.3%)
 C 2-pass copy prefetched (32 bytes step)             :   6178.2 MB/s (0.4%)
 C 2-pass copy prefetched (64 bytes step)             :   6186.5 MB/s (0.2%)
 C fill                                               :   9348.8 MB/s (0.5%)
 C fill (shuffle within 16 byte blocks)               :   9343.2 MB/s (0.4%)
 C fill (shuffle within 32 byte blocks)               :   9347.1 MB/s (0.3%)
 C fill (shuffle within 64 byte blocks)               :   9335.3 MB/s (0.2%)
 NEON 64x2 COPY                                       :   6068.6 MB/s
 NEON 64x2x4 COPY                                     :   6081.9 MB/s
 NEON 64x1x4_x2 COPY                                  :   6090.8 MB/s
 NEON 64x2 COPY prefetch x2                           :   5908.0 MB/s
 NEON 64x2x4 COPY prefetch x1                         :   6017.4 MB/s
 NEON 64x2 COPY prefetch x1                           :   5911.9 MB/s
 NEON 64x2x4 COPY prefetch x1                         :   6035.6 MB/s
 ---
 standard memcpy                                      :   6108.1 MB/s
 standard memset                                      :   9359.8 MB/s (0.5%)
 ---
 NEON LDP/STP copy                                    :   6098.9 MB/s
 NEON LDP/STP copy pldl2strm (32 bytes step)          :   6210.6 MB/s
 NEON LDP/STP copy pldl2strm (64 bytes step)          :   6214.1 MB/s
 NEON LDP/STP copy pldl1keep (32 bytes step)          :   6212.3 MB/s
 NEON LDP/STP copy pldl1keep (64 bytes step)          :   6215.8 MB/s
 NEON LD1/ST1 copy                                    :   6091.9 MB/s
 NEON STP fill                                        :   9344.3 MB/s (0.6%)
 NEON STNP fill                                       :   9335.9 MB/s
 ARM LDP/STP copy                                     :   6105.8 MB/s (0.2%)
 ARM STP fill                                         :   9323.0 MB/s (0.4%)
 ARM STNP fill                                        :   9317.7 MB/s (0.6%)

==========================================================================
== Memory latency test                                                  ==
==                                                                      ==
== Average time is measured for random memory accesses in the buffers   ==
== of different sizes. The larger is the buffer, the more significant   ==
== are relative contributions of TLB, L1/L2 cache misses and SDRAM      ==
== accesses. For extremely large buffer sizes we are expecting to see   ==
== page table walk with several requests to SDRAM for almost every      ==
== memory access (though 64MiB is not nearly large enough to experience ==
== this effect to its fullest).                                         ==
==                                                                      ==
== Note 1: All the numbers are representing extra time, which needs to  ==
==         be added to L1 cache latency. The cycle timings for L1 cache ==
==         latency can be usually found in the processor documentation. ==
== Note 2: Dual random read means that we are simultaneously performing ==
==         two independent memory accesses at a time. In the case if    ==
==         the memory subsystem can't handle multiple outstanding       ==
==         requests, dual random read has the same timings as two       ==
==         single reads performed one after another.                    ==
==========================================================================

block size : single random read / dual random read
      1024 :    0.0 ns          /     0.0 ns
      2048 :    0.0 ns          /     0.0 ns
      4096 :    0.0 ns          /     0.0 ns
      8192 :    0.0 ns          /     0.0 ns
     16384 :    0.0 ns          /     0.0 ns
     32768 :    0.0 ns          /     0.0 ns
     65536 :    0.0 ns          /     0.0 ns
    131072 :    1.1 ns          /     1.5 ns
    262144 :    1.6 ns          /     2.0 ns
    524288 :    1.9 ns          /     2.2 ns
   1048576 :    8.3 ns          /    11.2 ns
   2097152 :   12.2 ns          /    14.5 ns
   4194304 :   48.5 ns          /    72.1 ns
   8388608 :   75.7 ns          /    99.8 ns
  16777216 :   89.4 ns          /   108.8 ns
  33554432 :   98.4 ns          /   113.6 ns
  67108864 :  103.5 ns          /   116.7 ns

Strange seeing it go from 13 GB/sec to 9 GB/sec for memset...


universal cable conduits

can you please make universal cable conduits that can transfer rf, eu and joule?

You already made that request in #3204 which got closed as a duplicate - so will this one.


default workflow name is not filename, but file path

Wrote support about this:
https://help.github.com/en/articles/workflow-syntax-for-github-actions#name says that when no name:  is given, GitHub Actions will use the "workflow's filename".
That's not quite the behavior I'm seeing:
That is, in fact, the workflow file path from the root.
The same applies to the url to the action status badge: this also requires the entire file path from the repo root: https://github.com/r-lib/ghactions/workflows/.github/workflows/main.yml/badge.svg
This is a bit weird:The docs are unclear/wrongit's unclear why this would be so; just using the filename would be more succinct, or the path from ./github/workflows, because by definitions, workflows have to exist in that place.The url for the action status badge, in particular, gets ugly.So, perhaps you could change the docs here or the behavior?

https://help.github.com/en/articles/workflow-syntax-for-github-actions#name says that when no name:  is given, GitHub Actions will use the "workflow's filename".

Since at least January of this year (I didn't check further), GitHub changed the text. It now says:

If you omit name, GitHub sets it to the workflow file path relative to the root of the repository.

https://github.com/github/docs/blob/2a58d29f33e31765f517ebd140b8081222d6615a/content/actions/using-workflows/workflow-syntax-for-github-actions.md#name

Even after adding a name to the workflow, github continues to show the filepath as the name under the actions tab.

Happens to me also

The same here

Me too. It was working fine for months, then somehow some of my workflows' name changed to file path.

Those workflows have workflow_dispatch with inputs. After they changed to file path, I cannot run them manually anymore through the web UI.

I had the same issue, it was caused by adding a colon character in input description field (using quotes for whole description text). After removing colon it works fine.

I had the same issue, and the reason was the existence of a commented line(#) in my file.

Issue is open since 2019? Hellooo github team, you there??

Same issue on my project too


Issue 154 smc roundtrip

fixes #154

Tried it out in ad-hoc live testing of alchemiscale compute service. Appears to work as advertised. :grin:


Add GitHub widget to catalog CI/CD tab

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] All tests are passing yarn test
[ ] Screenshots attached (for UI changes)
[ ] Relevant documentation updated
[ ] Prettier run on changed files
[ ] Tests added for new functionality
[ ] Regression tests added for bug fixes

Looping in @shmidt-i - this overlaps with what you do - shall we merge and then you put yours on top of this? I'll let you review.


Style: replace sass-lint with stylelint

Description of PR
Replaced sass-lint and sass-lint-auto-fix with stylelint
Relevant Issues
Fixes #1559
Checklist

[x] Compiles and passes lint tests
[x] Properly formatted
[ ] Tested on desktop
[ ] Tested on phone

Rebase?


Add sample on how to use sam for lambda functions written in Go

Description of changes: This PR shows how to use aws sam for lambda functions written in Go
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@keetonian thank for reviewing my pull request.
Change request have been applied thanks.


MLPAB-2607 try adding xray to scheduler

Purpose
Briefly describe the purpose of the change, and/or link to the JIRA ticket for context
Fixes MLPAB-##
Approach
Explain how your code addresses the purpose of the change
Learning
Any tips and tricks, blog posts or tools which helped you. Plus anything notable you've discovered about the Modernising LPA service

Environment issues so closing in favour of #1582


Add support for minitest

@oleg-py Travis doesn't love you. Looks like unused import errors.

Looks like something with mima now, since there's no previous version for new module, and I have no idea where it is set up.

Ah yeah, that's a bug in how sbt-spiewak handles mima. I've been meaning to fix it.


Connection port parsing

This issue is meant to address #1124
This is a subtle bug because it has practically no impact on the libvirt code base. It only affects libvirt here:
	if err := l.ConnectToURI(libvirt.ConnectURI(u.RemoteName())); err != nil {

Outside of this location, this bug only affects ssh_config settings by incorrectly passing the target as "hostname:portname" instead of "hostname" here:

	// configuration loaded, build tunnel
	sshClient, err := u.dialHost(u.Host, sshcfg, 0)
	if err != nil {
		return nil, err
	}

However, when a port override is specified in the ConnectionString, u.Host will contain the hostname.

The added unittest assertions in this PR reveal the problem here:
 === RUN   TestURI
    connection_uri_test.go:34:
        	Error Trace:	/home/runner/work/terraform-provider-libvirt/terraform-provider-libvirt/libvirt/uri/connection_uri_test.go:34
        	Error:      	Not equal:
        	            	expected: "hostname"
        	            	actual  : "hostname:2222"

        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -1 +1 @@
        	            	-hostname
        	            	+hostname:2222
        	Test:       	TestURI


Analytics Rules with mapped MITRE techniques do not get imported as JSON

I've noticed that deploying detections in JSON format (as exported by the GUI) through a DevOps pipeline, or importing manually through the GUI, does not preserve the techniques configured. Tactics are preserved.
To reproduce, export any single detection with Techniques that have been mapped (e.g. T1136) and import to another Sentinel environment.
Expected behaviour is that the detection would preserve the mapped MITRE techniques. The techniques are present within the JSON file itself as well, however they're not reflected in the GUI in Sentinel.
The section of JSON with the techniques:

The imported rule without the technique:

@rcegan Has this already been fixed?
I have been playing around a lot with tactics and techniques lately in detection rules and building a pester test that validates if the correct tactics and techniques are used.
Also noticed that not all tactics are supported due to Microsoft Sentinel relying on the Mitre Att&ck framework vs9
I did not experience any issues with rules not showing the techniques after importing them from a json template

@azurekid I haven't tried for a while - maybe the v9 thing is why. I'll test it out later if I've got a sec and report back.

I'm currenty expericing exactly the same problems.  The "Techniques":  ["T1078"], key/value is not preserved during a deployment by devops. any light on this yet?

I'm currently experiencing exactly the same problems. The "Techniques": ["T1078"], key/value ie, is not preserved during a deployment by devops. any light on this yet?

Can you share the template?
I haven't been able to reproduce the error from both Azure DevOps, GitHub and manually.
Used to repositories option from Microsoft Sentinel, PowerShell and manual uploaded it to the portal.
I'm not with #Microsoft, so would be nice if someone from the team would pick this up also @vmanojreddy @ashishsyal

@azurekid sure,
this an example template, please don't mind the ttp mapping, there were just for testing purposes. The rule got pushed, as expected, but none of the ttp's got pushed to Sentinel. see screenshot

{
        "severity": "Medium",
        "query": "AuditLogs\n| where LoggedByService =~ \"PIM\"\n| where Category =~ \"RoleManagement\"\n| where ActivityDisplayName has \"Disable PIM Alert\"\n| extend IpAddress = case(\n  isnotempty(tostring(parse_json(tostring(InitiatedBy.user)).ipAddress)) and tostring(parse_json(tostring(InitiatedBy.user)).ipAddress) != 'null', tostring(parse_json(tostring(InitiatedBy.user)).ipAddress), \n  isnotempty(tostring(parse_json(tostring(InitiatedBy.app)).ipAddress)) and tostring(parse_json(tostring(InitiatedBy.app)).ipAddress) != 'null', tostring(parse_json(tostring(InitiatedBy.app)).ipAddress),\n  'Not Available')\n| extend InitiatedBy = iff(isnotempty(tostring(parse_json(tostring(InitiatedBy.user)).userPrincipalName)), \n  tostring(parse_json(tostring(InitiatedBy.user)).userPrincipalName), tostring(parse_json(tostring(InitiatedBy.app)).displayName)), UserRoles = tostring(parse_json(tostring(InitiatedBy.user)).ipAddress)\n| project InitiatedBy, ActivityDateTime, ActivityDisplayName, IpAddress, AADOperationType, AADTenantId, ResourceId, CorrelationId, Identity\n| extend timestamp = ActivityDateTime, IPCustomEntity = IpAddress, AccountCustomEntity = tolower(InitiatedBy), ResourceCustomEntity = ResourceId",
        "queryFrequency": "P1D",
        "queryPeriod": "P1D",
        "triggerOperator": "GreaterThan",
        "triggerThreshold": 0,
        "displayName": "[#{customername}#] [UC1] Detect PIM Alert Disabling activity",
        "enabled": true,
        "description": "Privileged Identity Management (PIM) generates alerts when there is suspicious or unsafe activity in Azure Active Directory (Azure AD) organization. \nThis query will help detect attackers attempts to disable in product PIM alerts which are associated with Azure MFA requirements and could indicate activation of privileged access",
        "lastUpdatedDateUTC": "2021-10-19T00:00:00Z",
        "createdDateUTC": "2021-09-30T00:00:00Z",
        "status": "Available",
        "kind": "Scheduled",
        "tactics":["Persistence", "PrivilegeEscalation"],
        "Techniques":["T1548","T1098","T1078", "T0890"]
      },

I am going through same issue as well. I am using azsentinel 0.6.21 powershell module to import Analytics rules into Microsoft Sentinel. Powershell command I am using in "import-azsentinelalertrule". Below is one of the rule in JSON format. Everything in this rule get deployed except Techniques values.
{
"displayName": "TEARDROP memory-only dropper",
"description": "Identifies SolarWinds TEARDROP memory-only dropper IOCs in Window's defender Exploit Guard activity\nReferences:\n- https://www.fireeye.com/blog/threat-research/2020/12/evasive-attacker-leverages-solarwinds-supply-chain-compromises-with-sunburst-backdoor.html\n- https://gist.github.com/olafhartong/71ffdd4cab4b6acd5cbcd1a0691ff82f",
"severity": "High",
"enabled": true,
"query": "DeviceEvents\n| where ActionType has "ExploitGuardNonMicrosoftSignedBlocked"\n| where InitiatingProcessFileName contains "svchost.exe" and FileName contains "NetSetupSvc.dll"\n| extend timestamp = TimeGenerated, AccountCustomEntity = iff(isnotempty(InitiatingProcessAccountUpn), InitiatingProcessAccountUpn, InitiatingProcessAccountName),\nHostCustomEntity = DeviceName, FileHashCustomEntity = InitiatingProcessSHA1, FileHashType = "SHA1"",
"queryFrequency": "P1D",
"queryPeriod": "P1D",
"triggerOperator": "GreaterThan",
"triggerThreshold": 0,
"suppressionDuration": "PT5H",
"suppressionEnabled": false,
"tactics": [
"Execution",
"Persistence",
"DefenseEvasion"
],
"techniques": [
"T1059"
],
"alertRuleTemplateName": null,
"incidentConfiguration": {
"createIncident": true,
"groupingConfiguration": {
"enabled": false,
"reopenClosedIncident": false,
"lookbackDuration": "PT5H",
"matchingMethod": "AllEntities",
"groupByEntities": [],
"groupByAlertDetails": [],
"groupByCustomDetails": []
}
},
"eventGroupingSettings": {
"aggregationKind": "SingleAlert"
},
"alertDetailsOverride": null,
"customDetails": null,
"entityMappings": [
{
"entityType": "Account",
"fieldMappings": [
{
"identifier": "FullName",
"columnName": "AccountCustomEntity"
}
]
},
{
"entityType": "Host",
"fieldMappings": [
{
"identifier": "FullName",
"columnName": "HostCustomEntity"
}
]
},
{
"entityType": "FileHash",
"fieldMappings": [
{
"identifier": "Algorithm",
"columnName": "FileHashType"
},
{
"identifier": "Value",
"columnName": "FileHashCustomEntity"
}
]
}
],
"sentinelEntitiesMappings": null,
"templateVersion": "1.0.3"
}

After further investigation I can tell that powershell command  "import-azsentinelalertrule" doesn't have feature to deploy Techniques yet.

Is there any update on this?

Is there any update on this?

I've implemented this and it seems to be working when importing through ARM templates!

Is there any update on this?

I've implemented this and it seems to be working when importing through ARM templates!

ARM Templates work for including the Techniques, however using the Powershell Az Module does not. After digging around I discovered it is because the API is outdated and not built to handle the technique variable yet.

Hi @rcegan , thank you for flagging this. Apologies for the delayed response. If you still need assistance, please reply here within 5 business days.

Gentle Reminder: We are awaiting for your response on this issue. If you still need to keep this issue active please respond within next 2 days. If we don't receive response by 17 Feb 2023, we will close this issue.

Since we have not received a response in the last 5 days, we are closing your issue #4386 as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation.

It seem that this issue still persists.
When I upload Analytics rules via an ARM template (manual import via the Import function in Sentinel), the MITRE techniques are not saved.


Add AztecEditor-iOS to Text category

Thanks for your contribution! This is a template that can make it easier when submitting your contribution:
Your Project: AztecEditor-iOS
Project URL: _https://github.com/wordpress-mobile/AztecEditor-iOS_
Category: Text
Description: A very straightforward UITextView subclass and a robust conversion system for transforming HTML to NSAttributedString and back. It also has an amazing example application for showing off all of the capabilities.
Inclusion requirements:

[x] Has 50 GitHub stargazers or more
[x] Only one project/change is in this pull request
[x] Isn't an archived project
[x] Has more than one contributor
[x] Has unit tests, integration tests or UI tests
[x] Addition in alphabetical order (bottom of category)
[x] Supports iOS 12 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

:heart: Awesome iOS Contributors

已收到您的邮件，我会在24小时内回复您的。——Kevin San.

@allenhumphreys Thanks for contributing!


helm: remove CriticalAddonsOnly toleration in preflight DaemonSet

CriticalAddonsOnly toleration will prevent the preflight pods being schedule to nodes with taints, remove this toleration to provision preflight pods to all nodes for verifying the cilium upgrade status.
Fixes: #27317
Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Are you a user of Cilium? Please add yourself to the Users doc
[ ] Thanks for contributing!

Thanks for the PR! The motivation sounds reasonable, there are however a few steps needed to contribute a Helm change:

Please apply your changes to the values.yaml.tmpl
Then re-generate the values.yaml, JSON schema and README.md by running make -C install/kubernetes
Re-generate the docs via make -C Documentation update-helm-values

Thanks!

Thanks @gandro for the quick review and provide the contribute guideline, I've committed the changes.

Thanks @gandro for the quick review and provide the contribute guideline, I've committed the changes.

Thank you, looking much better already. Looking at this some more, I think operator: Exists makes all other tolerations obsolete (from the docs: "An empty key with operator Exists matches all keys, values and effects which means this will tolerate everything."). I think we should therefore remove all other tolerations too, as they are now effectively a no-op.

/test

CI is currently affected by the Bing outage. Let's try again tomorrow.

/test

Thanks for the contribution @HongChenTW !


SET GRID/RESTORE  after CANCEL DATA/ALL gets grid %%

Reported by Ansley B Manke on 9 May 2003 17:56 UTC
Prior to v5.52, the sequence SET GRID/SAVE; CANCEL DATA/ALL;
SET GRID RESTORE gives a final result of the last SHO GRID
as %%.  It should be the grid of ROSE.  Example with notes:
 yes? use etopo20
 yes? set grid rose   !<== this should bump the use count on this grid
 yes? sh grid
 yes? set grid/save  ! <== this should bump it a second time
                     ! (Note that the previously stored grid
                     ! may need to have grid_use_count decremented)

 yes? use geo_borders
 yes? set grid CONTINENT_LON ! <== this should decrement the
                             ! use count on the "rose" grid
 yes? can data/all   ! <== the use counts on the "rose" grid is
                     ! still non-zero, so it will not be deleted

 yes? set grid/restore ! <== this should increment the use count
                       ! as a result of SET GRID

 yes? sho grid

Check whether the SET GRID/RESTORE should also decrement the
same use count because the save/restore grids are on a stack,
and this command pops that stack.  The net result of these two
actions is that the use count remains unchanged.  (May require
just a comment in the code)
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/546

Comment by<EMAIL_ADDRESS>on 6 Nov 2003 20:30 UTC
reassign to ansley