max_4_fonts_per_family_name: Check only win name records

Fixes #2613

This check currently lives in the opentype profile, which means it should enforce a requirement of the OpenType spec.
@m4rc1e, filtering only win-entries is a googlefonts specific aspect of this check?

I'm assuming this check was created so that non RIBBI styles are selectable in MS Office by enforcing the use of nameid 16 and 17, if the family has more than four fonts.
This is an Adobe check. When I inspect their fonts, they don't use Mac name records, hence this has never been an issue for them.
The current rationale for this check is:

Per the OpenType spec. 'The Font Family name ... should be  shared among at most four fonts that differ only in weight or style ...

This isn't 100% accurate, here's the full text for nameID2 where I guess this came from

While some platforms or applications do not have this constraint, many existing applications that use this pair of names assume that a Font Family name is shared by at most four fonts that form a font style-linking group, and that Font Subfamily names would reflect one of the four basic styles, regular, italic (or oblique), bold, and bold italic (or bold oblique). To be compatible with the broadest range of platforms and applications, it is strongly recommended that fonts should limit use of Font Family in this manner.

For extended typographic families that includes fonts other than the four basic styles (regular, italic, bold, bold italic), it is strongly recommended that name IDs 16 and 17 be used in fonts to create an extended, typographic grouping.

Within an extended typographic family that includes fonts beyond regular, bold, italic, or bold italic, distinctions are made in the Font Family name, so that fonts appear to be in separate families. In some cases, this may lead to specifying a Subfamily name of “Regular” for a font that might not otherwise be considered a regular font. For example, the Arial Black font has a Font Family name of “Arial Black” and a Subfamily name of “Regular”. Note that, in such cases, name IDs 16 and 17 should also be included, using a shared value for name ID 16 that reflects the full typographic family, and values for name ID 17 that appropriately reflect the actual design variant of each font.

https://docs.microsoft.com/en-us/typography/opentype/spec/name#name-ids
AFAIK, the "While some platforms or applications do not have this constraint" applies to Macintosh. Both Glyphsapp and our name spec do not use nameID 16 and 17 for Mac records and we've never had a problem.
I'm more than happy to update the rationale to include this info.

I'm more than happy to update the rationale to include this info.

Yes, please ;-)

@m4rc1e Thank you for addressing this issue.

At the risk of sound a little bit dumb, if I'm understanding well, the solution for this is going to be to change the spec so it doesn't ask for nameID 16 and 17 for Mac records? Am I right?
If I'm not wrong and that's the case, when do you think this could be included? I still get that Fail when running FB today.
If I'm wrong and there is something to be done in the file to fix it… what should it be? Would it be necessary to follow the Name Table Entries instructions on Glyphs tutorial?
Thanks for addressing this!

The fix was included in the v0.7.11 release last week: https://github.com/googlefonts/fontbakery/blob/master/CHANGELOG.md#0711-2019-aug-21
Please install the new fontbakery version in order to benefit from this update:
pip install fontbakery --upgrade

Great! thank you

I might be doing something wrong. But it seems like this issue has just begun again. I'm on a Mac and haven't have this issue before, but last week this FAIL suddenly came up. Please let me know if there is something i can do to fix this?
https://github.com/usted/Albert-Sans/blob/gh-pages/fontbakery/fontbakery-report.md


Ubuntu compatibility

Fix #123

Thanks a lot for this contribution, I used a little bit of hacking to make this work on Ubuntu before your contribution. I have two questions.

Sysconfig vs default

Ubuntu does not have a /etc/sysconfig folder, so in the systemd task, you write down the environment file to /etc/default.
But, in the systemd unit file we still reference the old /etc/sysconfig folder.
Shouldn't those lines be :
{% if ansible_facts.os_family == "Debian" %}
EnvironmentFile=-/etc/default/keycloak
{% endif %}
{% if ansible_facts.os_family == "RedHat" %}
EnvironmentFile=-/etc/sysconfig/keycloak
{% endif %}

keycloak_configure_iptables should be set to false in the defaults.yml, like firewalld. Should the variable be renamed as keycloak_quarkus_configure_iptables to include the full name of the role (like firewalld) ?

Tell me if I'm wrong ? I can create an other PR if you want.

It's correct; now that the PR is merged, I am doing right now some refactoring and adding a molecule test on an ubuntu container. Please check back soon or you are welcome to open any other ubuntu changeset not overlapping with the above

#181
@Aeyk  can you please take a look?


change user ids to system range

is ok, but there is not really a reason to keep space between related entries.


v1.3 Enhancement: Allow prefixes to be optional

Pull Request Test Coverage Report for Build 250

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.04%

Totals

Change from base Build 249:
0.0%

Covered Lines:
2025

Relevant Lines:
2249

💛  - Coveralls


Allow anyone non-propose to submit the asMulti if the threshold was met

closes #62

Looks good 🚀

Re-tested with the accounts already in the predicament and I was able to recover and complete the flow
Tested with brand new accounts, approved the createPure simultaneously with the two remaining approvers. One of the attempts showed a "canceled" toast and then when I approved it a second time I was able to complete the flow


Language detection error

When the language is not automatically detected the perspective-api-client will throw the error:
response error unable to detect language
The easiest workaround to this issue would be making sure to add a default option as suggested by the official documentation. I'd propose adding this following code example to the readme
const result = await perspective.analyze({           comment: { text },           languages: ["en"],   })

There also needs to be something in getAnalyzeCommentPayload to the effect of if (opts.languages) resource.languages = opts.languages; I created a PR, but there are not push permissions aside from @sloria


Array.prototype.includes has inconsistent support, remove

I started using Array.includes() in a few places, it's not totally supported everywhere though. It shouldn't be an immediate issue until someone tries it on IE.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/includes#Browser_compatibility

oh wait, I'm just doing this in some PR's, will change it there


Allow optional c++11 in the build, and require c++11 for tests

With Google test 1.10, c++11 is mandatory (see https://github.com/google/googletest/issues/1366#issue-283686739). To build the tests, this PR requires c++11 support. Additionally, the PR adds a new build flag that enables c++11 for the whole library. By setting SQLITECPP_ENABLE_CPP11 to TRUE the library will use c++11 features.

Hello @emmenlau thank you for this.
I really like this, and modern C++ in general, but for now I have maintained explicit support for pre-C++11, so CI is explicitly testing with C++98 (and fails with this).
I you want to help moving forward, you could disable these CI config using C++98, force enable C++11 or above, add a note to the readme, and increase the lib version accordingly
Cheers

Closing this one since C++11 is now up an running


More of a question than an issue

More of a question than an issue.  Suppose one wanted to use a Wemos D1 Mini, instead of the ESP8266.  How difficult would it be to change the code referencing the ESP to allow for use of a Wemos D1?  The Wemos D1 has a 5v output which, is better for driving more leds.
I have been running a METAR map on a Raspberry PI since Covid lockdowns and like the simplicity of this code.  Using this would free up my PI for another project.
Thanks, very cool project.

Hola! I designed the entire project for a Wemos D1 Mini, so it should work out of the box just fine. (The Wemos uses an ESP8266 as its microcontroller.) But all of the logic pins on the Wemos are 3.3v, not 5v. I’ve found that usually LED strands will accept that 3.3v logic just fine so it may not be necessary to add the level shifting ICs to get it to 5v, but your mileage may vary.


[WIP] Create shared package folder for ANCM in process mode.

Start of moving out HttpSys functions currently used in ANCM inprocess. These classes will be ported for sure, @Tratcher and I will need to determine if classes like Request/Response can be shared too.

#396

@Tratcher It seems we may need to do a bit of massaging to get this working. In all shared folders, we must have all using statements not depend on internal classes. So currently we have a dependency like:
RequestHeaders =>NativeRequestContext => AuthenticationSchemes
Authentication schemes is public, which is an issue because it either:

Would break everyone to change the namespace of a public type
Would require whoever is using it to call using Microsoft.AspNetCore.HttpSys.Internal

In ANCM in process, we change NativeRequestContext to HttpApi.HTTP_REQUEST_V2*. Though HttpApi.HTTP_REQUEST_V2* should be changed to a NativeRequestContext, the implementations would be different as in proc ANCM would not need to alloc the native request.

Not sure I understand the exact problem here, but we sometimes #ifdef either the namespace of the stuff that's in shared source (to make its namespace better match the various destinations), or we #ifdef the various usings so that the code works in each destination.

The using statements aren't really the problem. You're trying to share higher level classes that have non-shared dependencies. This is largely a matter of factoring and deciding how high we should go with shared components. It may make sense to factor out or #ifdef out the non-shared pieces. We should look over it together.

The build is failing because I need to put the package on coherence signed?

@Tratcher :up: :date:

@Tratcher :up: :date:s


fail to use my own avatar

Hi Yaoyao
Thank you for this template!
I'd like to use my own avatar.png (128 x 128) but after committing the change there is still the default avatar.
Could you please help take a look and let me know how to do?
my repo at https://github.com/patricklin26/patricklin26.github.io/tree/main
Very appreciated.
Best!
Pei

FYI,
I simply remove the default avatar.png and then create my own using the same name (avatar.png) and upload to assets/img/.
Thank you!

Thanks for your interest in our project!
It seems that you have successfully changed your avatar. You cannot see the change because your browser’s cache has not been updated. I recommend you build the project locally if you hope to view the changes immediately.
If you have any further questions, feel free to contact me.

I should be more patient to see it happen!
Thank you!


Pattern matching in case doesn't behave like the one in erlang

The erlang code:
X = foo.
Y = bar.
T = bar.

case T of
    X -> io:format("X:~p T:~p ", [X, T]);
    Y -> io:format("Y:~p T:~p ", [Y, T])
end.

Y:bar T:bar ok

I can't make it work in LFE:
(set X 'foo)
(set Y 'bar)
(set T 'bar)

(case T (X (io:format "X:~p T:~p " `(,X ,T)))
(Y (io:format "Y:~p T:~p " `(,Y ,T))))
X:bar T:bar ok ;;not Y:bar in erlang code

(case T (`,X (io:format "X:~p T:~p " `(,X ,T)))
(`,Y (io:format "Y:~p T:~p " `(,Y ,T)))) ;; backquote doesn't help either
X:bar T:bar ok

The pattern matching in the lfe example seems to always shadow the binding T in the outer scope instead of do a symbol to symbol comparison like I intend to do in erlang case example. Any suggustion?

Variables are scoped in LFE, which they are not in Erlang, they behave pretty much as they do in funs in erlang. So in a case variables occurring in the patterns are new, fresh variables which inside the case clause shadow variables bound before it. Same in let.
So you need to do:
lfe> (set x 'foo)
foo
lfe> (set y 'bar)
bar
lfe> (set t 'bar)
bar
lfe> (case t
lfe>   (x1 (when (=:= x1 x)) (io:format "x:~p t:~p " (list x1 t)))
lfe>   (y1 (when (=:= y1 y)) (io:format "y:~p t:~p " (list y1 t))))
y:bar t:bar ok

@rvirding thanks for explaining this to me, I like the consistency of your design


[Chore] Bump version to 1.7.0

What happened 👀
Bump version to 1.7.0
Insight 📝
Automatically created by the Bump Version workflow.
Proof Of Work 📹
On the Files changed tab

We're in Iteration 16, version 1.6.0 FYI


[Core] [Storage] Proposed changes to transport/_aiohttp.py to allow for decompression to be configurable

As it currently stands, there is no way for us to turn auto-decompression off even if the customer specifically passes decompress=False. There is two adjustments that need to be made:

Some sort of configurable variable, decompress, that is popped in _aiohttp.py and has an effect on the value of the decompress parameter to AioHttpTransportResponse's constructor
Additionally passing decompress in the generated download method to the pipeline run() so that it can be used by _aiohttp.py to enact change in behavior

Closing since we found another way to achieve this 😄


Windows - My Books window too wide

On Windows, there is a sidebar on the bottom of the screen and the window is in fact must too wide. No problem on Mac.

fixed in f286291

fixed in #316

On Ubuntu (version 16.04) the sidebar on the bottom is not present but the window is still too wide when i naviguate with touchpad

Laurent, is this still a problem?

@Scarsniik, can you please check on your Linux box?

I don't have the problem anymore


Shei

Steps to reproduce
Big reprt
Relevant log output
Bug reprt

What did you expect to happen?
Shetkls
Version
Wjefvn
Docker Versions (if used)
Whn
OS
Linux
On which CPU architecture did you run Pathway?
None

Hey @ArjitTiwarii,
I am closing this issue as it doesn't contain any information about the bug. If you really need help feel free to open a new issue.


Syncing from upstream zalando/patroni (master)

bt_gitbot

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-2 of 135 (98.52%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 99.844%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

patroni/ha.py
109
111
98.2%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
11506

Relevant Lines:
11524

💛  - Coveralls


User who have left still have room allocated on the server.

Clean up after users disconnecting.
[ ] Send message to clients to remove owned objects.
[ ] Reduce size of allocated room object.

Done in v1.1.0


Add trino origin orc-reader for trino read

Use trino filesystem and trino reader to read data, it will speed up reading.
Now this pr, only support orc reader for paimon.
If you want to use oss, you should refer to:
https://github.com/aliyun/alibabacloud-jindodata/blob/master/docs/user/4.x/4.6.x/4.6.12/oss/presto/jindosdk_on_presto.md
add:
hive.config.resources=/path/to/core-site.xml
in paimon.properties

Maybe we should set a larger orc_tiny_stripe_threshold.


⚠ Bofrost.lu has degraded performance

In f74b725, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1065 ms

Resolved: Bofrost.lu performance has improved in 4d6405b after 9 minutes.


Blocks to represent weeks not days

Hi,
Is there a possibility for the blocks to represent weeks and not days? I'm looking to build out a vertical calendar heat map displaying a year at a time. So in order to save screen space, I would like each block to represent a week (ie: each row of blocks would be a month).
Eg:
[][][][][] August
[][][][][] July
[][][][][] June
etc...
It would be wonderful if this was possible as I need to multi-select blocks representing weeks/months in order to select a date-range for a chart.
Is this possible with the current rect-calendar-heatmap control?

Hi @benjamindesilva! This wouldn't be possible right now, and the suggested functionality seems divergent enough that it'd probably be better just to fork and roll your own.


Demo doesn't work

404 https://rawgit.com/TheSharpieOne/angular-input-match/master/dist/angular-input-match.min.js

the url should be https://rawgit.com/TheSharpieOne/angular-input-match/master/dist/angular-validation-match.min.js
here is a working version http://jsfiddle.net/q300sku2/45/

Sorry about that, one of the side effects for changing the repo name.  I'll update the link in the README


Relative client certificate paths do not work

relates #275
Even though mentioned in the PR that relative certificate path should work, I cannot get them to work.
I placed them directly within my collection folder next to my bruno.json which looks like this:
{
  "version": "1",
  "name": "tibeer",
  "type": "collection",
  "clientCertificates": {
    "enabled": true,
    "certs": [
      {
        "domain": "api.tibeer.de",
        "certFilePath": "prod.cer",
        "keyFilePath": "prod.key",
        "passphrase": ""
      },
      {
        "domain": "api-test.tibeer.de",
        "certFilePath": "test.cer",
        "keyFilePath": "test.key",
        "passphrase": ""
      }
    ]
  }
}

Might also be an user error.

Interesting: They work in the CLI, but not in the UI. I'm having a look.

Aweseome job @jwetzell! Closing this :)


⚠ Hartman Foundation has degraded performance

In 0918415, Hartman Foundation (https://gordonhartman.com/) experienced degraded performance:

HTTP code: 200
Response time: 2706 ms

Resolved: Hartman Foundation performance has improved in 348a92b.


Upgrade to 2.33.0 failed, missing database migration?

Upgrade of DefectDojo 2.24.1 to 2.33.0 failed
We tried to directly upgrade DefectDojo 2.24.1 to DefectDojo 2.33.0 running on Kubernetes, using Helm. Helm chart version 1.6.75 -> 1.6.118.
After the pods come up the instance is broken, with bellow error.
Bug description
After the upgrade, pods were started, but UI is broken with error logs below.
It looks like the database wasn't migrated. How to fix this?
Steps to reproduce
Steps to reproduce the behavior:

Change Helm chart values
Redeploy helm chart
Wait for pods to start
Checkout web interface

Expected behavior
Upgraded instance with working database model and web interface.
Deployment method (select with an X)

[ ] Docker Compose
[x] Kubernetes
[ ] GoDojo

Environment information

Kubernetes v1.24.17 (EKS)
DefectDojo version 2.33.0

Logs
Environment:

Request Method: GET
Request URL: https://defectdojo.<our URL>/dashboard

Django Version: 4.1.13
Python Version: 3.11.4
Installed Applications:
('django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.sites',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'polymorphic',
 'django.contrib.admin',
 'django.contrib.humanize',
 'gunicorn',
 'auditlog',
 'dojo',
 'watson',
 'tagging',
 'imagekit',
 'multiselectfield',
 'rest_framework',
 'rest_framework.authtoken',
 'dbbackup',
 'django_celery_results',
 'social_django',
 'drf_spectacular',
 'drf_spectacular_sidecar',
 'tagulous',
 'fontawesomefree',
 'django_filters',
 'django_prometheus')
Installed Middleware:
['django_prometheus.middleware.PrometheusBeforeMiddleware',
 'django.middleware.common.CommonMiddleware',
 'dojo.middleware.APITrailingSlashMiddleware',
 'dojo.middleware.DojoSytemSettingsMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.middleware.security.SecurityMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'dojo.remote_user.RemoteUserMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware',
 'dojo.middleware.LoginRequiredMiddleware',
 'dojo.middleware.AdditionalHeaderMiddleware',
 'social_django.middleware.SocialAuthExceptionMiddleware',
 'watson.middleware.SearchContextMiddleware',
 'auditlog.middleware.AuditlogMiddleware',
 'crum.CurrentRequestUserMiddleware',
 'dojo.request_cache.middleware.RequestCacheMiddleware',
 'django_prometheus.middleware.PrometheusAfterMiddleware']

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python3.11/site-packages/django_prometheus/db/common.py", line 69, in execute
    return super().execute(*args, **kwargs)

The above exception (column dojo_finding.sla_expiration_date does not exist
LINE 1: ...col3", "dojo_finding"."sla_start_date" AS "col4", "dojo_find...
                                                             ^
) was the direct cause of the following exception:
  File "/usr/local/lib/python3.11/site-packages/django/core/handlers/exception.py", line 56, in inner
    response = get_response(request)
  File "/usr/local/lib/python3.11/site-packages/django/core/handlers/base.py", line 197, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/app/dojo/home/views.py", line 38, in dashboard
    .count()
  File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 621, in count
    return self.query.get_count(using=self.db)
  File "/usr/local/lib/python3.11/site-packages/django/db/models/sql/query.py", line 559, in get_count
    return obj.get_aggregation(using, ["__count"])["__count"]
  File "/usr/local/lib/python3.11/site-packages/django/db/models/sql/query.py", line 544, in get_aggregation
    result = compiler.execute_sql(SINGLE)
  File "/usr/local/lib/python3.11/site-packages/django/db/models/sql/compiler.py", line 1398, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 102, in execute
    return super().execute(sql, params)
  File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 67, in execute
    return self._execute_with_wrappers(
  File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 84, in _execute
    with self.db.wrap_database_errors:
  File "/usr/local/lib/python3.11/site-packages/django/db/utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python3.11/site-packages/django_prometheus/db/common.py", line 69, in execute
    return super().execute(*args, **kwargs)

Exception Type: ProgrammingError at /dashboard
Exception Value: column dojo_finding.sla_expiration_date does not exist
LINE 1: ...col3", "dojo_finding"."sla_start_date" AS "col4", "dojo_find...
                                                             ^

Hi @jas02
Can you

run python manage.py showmigrations in uwsgi container of django pod?
check when initializer-job was triggered last time?

OK, I figured out what was wrong. My colleagues has had disabled initializer job in the Helm chart, which was root cause of missing migration (obviously). After enabling this section in Helm chart was the migration and whole upgrade successful.
Closing this incident, thanks @kiblik for help.


Eagerly trying to connect to running redis server

Hi, I have a spring boot project (spring boot version 3.2.10) with redisson 3.17.1 initially. Whenever the server used to start, it used to connect to a running redis server only when the value of "spring.cache.type" was redis in application.properties file. But since my upgradation to 3.30.0, it tries to connect to running redis server even if the spring.cache.type value is something else or the property isn't there at all. Can anyone please highlight the exact release and the documentation where this eager nature of connecting to redis server is mentioned?
@mrniko Any guidance will be appreciated.

You can disable it. https://redisson.org/docs/integration-with-spring/#faq

Hi @mrniko, I am aware of disabling redisson at runtime. My question was from which release the redisson was trying to eagerly connect during spring boot startup ? Or is this behaviour present from the starting (1st release) of redisson?.... Thanks..

It's the default behavior. It doesn't depend on spring.cache.type


RH V2 support

Currently RH registry doesn't support V2 APIs and skopeo does not support V1 APIs either:
$ ./skopeo inspect docker://registry.access.redhat.com/rhel7
FATA[0001] error pinging repository, response code 404

In order for skopeo to work correctly the following APIs should be supported in the RH registry:
GET /v2/
GET /v2/<name>/tags/list
GET /v2/<name>/manifests/<reference>
GET /v2/<name>/blobs/<digest>

More on each of the above https://docs.docker.com/registry/spec/api/

… and we will need to figure out a signing story.  Will the RH registry expose OpenShift-like APIs for this, or does this mean defining and implementing another transport mechanism?

I would think so yes, we only want to have one set of APIs, Whether you can push is one thing, but we need to be able to pull the signature via Crane.

Since registry.access.redhat.com now supports v2, I think we can close this.
In any case it makes little sense for skopeo to support v1 when it does not make guarantees about content addressability -- signing doesn't really make sense there.

Agreed, we can always reopen in case we'll ever going to need v1


registry/storage/driver: add path and other info to filesytem trace methods.

Also fix Delete (was 'Move').

Bad rebase included AUTHORS change

LGTM!


IOT Packet Verifier

i had a really hard time sorting out everything the balance sufficiency enum was doing at first and i think it's a combination of the fact that on the surface it seems redundant that you would have a balance that's both sufficient/insufficient and enabled/disabled (and it looks like you should be able to derive the desired behavior from just the enum variant or the boolean), but also that the call to mem::replace is swapping out the value of the balance struct's enabled field.
now that i feel i have a handle on what's going on i think what bothers me is how the enum function is reaching into the balance struct and mutating its state remotely. i think it would be a lot more straightforward to follow if we just treated the balance struct as a state machine and pass it around as needed, and then update the enable field or its equivalent directly against the balance struct and take appropriate action against the org (enable/disable) based on the result of that operation (i.e. we could handle enabling/disabling the org within the same function that flips the boolean in the balance state machine as a result of the operation to validate the available balance all atomically)

I think that the BalanceSufficiency enum is pretty terrible and I'm planning on removing entirely in my next push. The plan is to have whether or not we previously enabled or disabled an org to be cached separately, so that all we get back from balance is whether or not the we were able to debit successfully. Hopefully that fixes things up a bit

This could do with a readme that outlines the operation of the verifier from a high level perspective and gives sufficient context to get the basic intent of the verifier.

That's a good idea, I'll add one today


Add documentation

request to merge add-documentation and master branches

I have merged the add-documentation branch into master. Some internal GitHub failure meant that didn't publish the contents of the doc folder as it should, but there were a few tweaks needed anyway, so I regenerated those and recommitted them, which has made them available now at:
https://bodleian.github.io/consolidated-tei-schema/msdesc.html
https://bodleian.github.io/consolidated-tei-schema/msdesc.pdf
I have also tagged the current state as a release:
https://github.com/bodleian/consolidated-tei-schema/releases/tag/v1.1.0


Error while running gen_hist4drmm.py

Hi there,
I've computed the different required files following the indications in data processing,and due to memory limit, I used the "glove.6B.300d.txt" embeddings. When I run gen_hist4drmm.py with my own data, I've got the following error:

python gen_hist4drmm.py 60
[~/MATCHZOO_BASELINES/data/ap88_embed_glove_d300]
Embedding size: 59014
read embedding finished ...
Generate numpy embed: %s (59015, 300)
[~/MATCHZOO_BASELINES/data/corpus_preprocessed.txt]
Data size: 14209
read corpus finished....
[~/MATCHZOO_BASELINES/data/relation_train.txt]
Instance size: 13527
Traceback (most recent call last):
File "gen_hist4drmm.py", line 46, in
curr_hist = cal_hist(d1_embed, d2_embed, qnum, hist_size)
File "../../matchzoo/inputs/preprocess.py", line 433, in cal_hist
mhist[i][vid] += 1.
IndexError: index 77 is out of bounds for axis 0 with size 60

note: I've got the same error with gen_binsum4anmm.py
Thanks for answering

Hello,
I solved the problem by modifying the following line in preprocess.py:
for inum, did in enumerate(dids):         fout.write('%s %s %s\n' % (did,str(len(docs[inum])), ' '.join(map(str, docs[inum]))))   fout.close()
Because in corpus_preprocessed.txt  we should have the document length printed in the second column of each document.
Now it's working well.


Marked the Different Button Types for Translation

Related to: https://github.com/ManageIQ/manageiq-ui-classic/pull/7454
Fixes: #10515

@mzazrivec @chessbyte Please review.

@mzazrivec I see you approved this PR but not the related ManageIQ/manageiq-ui-classic#7454
I can merge both when I get your approval on both.

@chessbyte the frontend PR is not ready for merge yet.

@chessbyte this PR and https://github.com/ManageIQ/manageiq-ui-classic/pull/7454 can now be merged.

Kasparov backport details:
$ git log -1
commit 59966867ae110b6f006570099a533c692b977bd7
Author: Oleg Barenboim<EMAIL_ADDRESS>Date:   Thu Nov 5 11:54:40 2020 -0500

    Merge pull request #20762 from DavidResende0/customization-buttons-fix

    Marked the Different Button Types for Translation

    (cherry picked from commit 31ab766ce63b2f7f313c51d8b17df991aba5cfb1)


Revert "fix(vertical-menu): fixed 'containerRef' error (#7)"

This reverts commit c55709bc7b72bf31f3c631dc9b8fec9c041c7c55.

Hi @perviievgen,
Thanks for showing an interest in contributing.

Thus, we are not considering merging this PR.


fix: Add null check to avoid asserting on undefined process obj

Description
There is a seemingly random occurring error in Composer with the message 'cannot read property stdout of undefined'.
The issue is traced down to a call within the local publish extension where Composer does not null check a Process object prior to calling functions on it and there are times in which this function is called with a null process obj.
Testing indicates that a simple null check fixes the issue and enables true errors to surface for bots that are erroneous as well as working bots to continue working without the error popping up as well.
Task Item
fixes #8547
fixes #8564

Coverage remained the same at 55.894% when pulling f231c54ef84c49061ad31ecbe1fdd3149334041d on pavolum/fixStdOutError into 44d67edf859c90fdb4f017676cab3417165b5b9a on main.


Change 'AFP' -> 'ACKnowledge' in 'thanks for your submission' email

The text for this email is defined in the API and still contains 'AFP' instead of 'ACKnowledge'. This text should be fixed and moved to the config file where all the other emails are defined.

I've just resubmitted data for 00059841 and you should have received an email with the text fixed. Let me know if everything looks good @draciti.

I propose to change the first sentence of the email as follows.
Current text:
Thank you for your participation in ACKnowledge.
Proposed text:
Thank you for your participation in the Author Curation to Knowledgebase (ACKnowledge) project, previously known as Author First Pass.
@vanaukenk feel free to fix the grammar :)

Received and looking good. Closing


Mismatching node colors on Place Collection Map

The colors appear to be incorrect on the Place Collection map. In this example, the orange is "no relation" and the island in the upper left should be the bright red of "non-Cretan site"... as a secondary issue, the "no relation" is actually "undefined", and I would prefer to see that in the legend rather than "no relation".

The markers are partially transparent and basemap colours therefore affect the rendered colours. I've cranked the opacity up from 70% to 85% and that seems to have made a significant improvement.
@kgeographer : what do you think of the suggestion that we change the no relation legend to undefined ? Unfortunately, that looks to me like an uncaught JavaScript error, so how about simply other ? That's what I've switched it to in the upcoming PR (line 155 in utilities.js if you fancy something different).


DISCUSS - How do we allow multiple contributors in parallel?

Right now the nvd_override_candidates_from_cve5 script doesn't provide a nice way for multiple people to enrich data. It streams CVEs in a serial manner, outputting them in groupings of MAX_BATCH_SIZE
We need a way that multiple people trying to work on this data don't trample on the work of each other

I think perhaps we could split the output per assigner and date into smaller groups (maybe something like 5) to actually generate smaller reviewable draft PRs
so we'd end up with a bunch of PRs like apache/{created date}/batch1, apache/{created date}/batch2, github_m/{created date}/batch1, etc.
The idea would be to pick a PR to start reviewing, assign it to yourself, make adjustments to any of the 5 that need adjusting, delete the _notes section, and submit the PR for review
There are probably some complexities to handle for the next run of the automation if all of the PRS from the previous run haven't been merged or deleted
The downside is that it slows down my current workflow which is just blast through the whole queue for a day at once (there are usually less than 100 with the current tuning).  I guess we could scope the created PRS to all of the assigners that I'm not looking at yet then there won't be any collisions and we'd hopefully start to get coverage around the missing areas?

of course eventually no one will need to be contributing to the nvd overrides repo directly but rather to the currently non-existant one with the new annotation format, but in the meantime something like the above might work.


Periodically store checkpoints of non-finalised states

Description
Improve startup performance, and reduce the maximum number of blocks we have to replay to regenerate states, by periodically storing non-finalised states to disk.
Need to think through how this interacts with forks.

This has now been done.


Error on date parsing/RegEx for .ua TLD

whois  zieit.edu.ua
% Request from <IP_ADDRESS>
% This is the Ukrainian Whois query server #A.

% FOR INFORMATION ABOUT THE REGISTRANT OF THE DOMAIN NAME, YOU SHOULD CONTACT THE REGISTRAR.
% % .UA whois
% Domain Record:
% =============
domain:     zieit.edu.ua
admin-c:    ZIEI-UANIC
tech-c:     LSIT-UANIC
tech-c:     SIN101-UANIC
status:     OK-UNTIL<PHONE_NUMBER>0101
nserver:    ns213.inhostedns.net
nserver:    ns113.inhostedns.com
nserver:    ns313.inhostedns.org
created:    0-UANIC<PHONE_NUMBER>0101
changed:    UARR168-UANIC<PHONE_NUMBER>1836
source:     UANIC
TRACEBACK:
Traceback (most recent call last):
File "/home/brice/Workspace/project/WIP.py", line 23, in
who = whois.query('zieit.edu.ua')
File "/home/brice/Workspace/project/venv/lib/python3.9/site-packages/whois/init.py", line 113, in query
return Domain(pd)
File "/home/brice/Workspace/project/venv/lib/python3.9/site-packages/whois/_3_adjust.py", line 18, in init
self.creation_date = str_to_date(data['creation_date'][0], self.tld.lower())
File "/home/brice/Workspace/project/venv/lib/python3.9/site-packages/whois/_3_adjust.py", line 136, in str_to_date
raise UnknownDateFormat("Unknown date format: '%s'" % text)
whois.exceptions.UnknownDateFormat: Unknown date format: '0-uanic<PHONE_NUMBER>0101'
Process finished with exit code 1

only affect UANIC records, not UAEPP records.
(miss clic :'( )

added it to the test.py for further fixing

fixed in the latest pull request


Fix type conversion for numbers

Prerequisites
Put an x into the box(es) that apply:

[x] This pull request fixes a bug.
[ ] This pull request adds a feature.
[ ] This pull request enhances existing functionality.
[ ] This pull request introduces breaking change.

For more information, see the Contributing Guide.
Description
This PR fixes a regression added in #196. There seems to be a discrepancy of how "number" variables are processed (what we observed up to now the numbers on darwin are being treated as int but in linux they are float64, this yet to be validated). So instead we are going to explicitly convert all types of numbers (int, in8, int16, ...) to float64.
Issues Resolved
Fixes #203
Checklist
Put an x into all boxes that apply:

[ ] I have read the Contributing Guidelines.

Tests

[x] I have added tests to cover my changes.
[x] All tests pass when I run make test.

Documentation

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Code Style

[ ] My code follows the code style of this project.

@mgtrrz @apriljo I've opened this as an interim but still haven't been able to test it myself on a Mac to completely rule that out. I'd appreciate it if you could pull this down and test it on your side against your full configuration.

Seems to work.
❯ git fetch origin pull/204/head:fix-number
remote: Enumerating objects: 14, done.
remote: Counting objects: 100% (14/14), done.
remote: Compressing objects: 100% (12/12), done.
remote: Total 14 (delta 1), reused 7 (delta 1), pack-reused 0
Unpacking objects: 100% (14/14), done.
From https://github.com/segmentio/terraform-docs
 * [new ref]         refs/pull/204/head -> fix-number
❯ git checkout fix-number
Switched to branch 'fix-number'
❯ make build && ./bin/darwin-amd64/terraform-docs --version
==> Clean workspace
rm -rf ./bin
==> Build binary for current OS/ARCH
CGO_ENABLED=0 GO111MODULE=on go build -mod=vendor -ldflags " -X github.com/segmentio/terraform-docs/internal/version.version=v0.8.2-18-gaed5126 -X github.com/segmentio/terraform-docs/internal/version.commitHash=aed5126 -X github.com/segmentio/terraform-docs/internal/version.buildDate=2020-02-20T15:59:56-0500 " -o ./bin/darwin-amd64/terraform-docs
terraform-docs version v0.8.2-18-gaed5126 darwin/amd64 BuildDate: 2020-02-20T15:59:56-0500
❯ ./bin/darwin-amd64/terraform-docs markdown table april
## Providers

No provider.

## Inputs

| Name | Description | Type | Default | Required |
|------|-------------|------|---------|:--------:|
| number | the number | `number` | `42` | no |

## Outputs

| Name | Description |
|------|-------------|
| module\_number | the module number, defaults ${var.number} |


Not working on windows currently.

After being able to finally launch it without problems (You need uuidgen in path on windows, you guys said we do not but we do.) the completion does not work. Saw some other people saying its nvim cmp not working with this. Is this being looked at?

We recently adopted this repo from the original author, so I'm still coming up to speed here. Happy to accept a contribution to change the docs regarding the uuidgen requirement, or migrate to using PowerShell for the generation. I'm not sure what you meant by "its nvim cmp not working with this" exactly, could you clarify?

We recently adopted this repo from the original author, so I'm still coming up to speed here. Happy to accept a contribution to change the docs regarding the uuidgen requirement, or migrate to using PowerShell for the generation. I'm not sure what you meant by "its nvim cmp not working with this" exactly, could you clarify?

Some guy tracked down a cmp update that broke codeium. I think it is in one of the issues posted, it might be closed but I did find it back then when I made this post. I think I recall using an older version of cmp made it work again.
I fixed the issues that I had. in your docu it said uuidgen was not required to use codeium on windows, but it is as it does not work without it. So I downloaded it and added it to path, now codeium starst without errors but it does not work as mentioned by many other issues dating weeks back, just check the issue log.
Hoping this will work in the future for neovim 👍

From what I see, the uuidgen and nvim-cmp issues are resolved. Feel free to open a new issue if there's something else that's preventing issues.

From what I see, the uuidgen and nvim-cmp issues are resolved. Feel free to open a new issue if there's something else that's preventing usage.

That is not the issue, the issue is that it is not working. I just stated that uuidgen  is needed for it to work even tho the documentation says otherwise so that is a false statement.
After walking through a minefield of errors (before I made this post), all errors are gone (also before I made this post), codeium still does not work like it does in vscode. There are plenty of issues with the exact same problem.
Reopen, this issue has not been solved.

Yes, uuidgen is a requirement, and I updated the documentation to remove the idea that it wasn't needed for Windows in https://github.com/Exafunction/codeium.nvim/pull/100.
We voluntarily adopted this extension so its users wouldn't be left stranded without their favorite way of using Codeium, so it would be helpful if you can be more specific in what issues you still need resolved.

Yes, uuidgen is a requirement, and I updated the documentation to remove the idea that it wasn't needed for Windows in #100.
We voluntarily adopted this extension so its users wouldn't be left stranded without their favorite way of using Codeium, so it would be helpful if you can be more specific in what issues you still need resolved.

There is no auto completion, no errors. Like all the other issues. Some guy tracked it down to a new update from nvim-cmp, I already told you this in the thread.

The nvim-cmp error should be resolved by #84 and #88.

The nvim-cmp error should be resolved by #84 and #88.
Unfortunately there is still no auto-completion working for this, I do have a lot of other plugins working with auto completion though. No errors, just says Codeium.nvim: server updated and no completion while typing. Auto-completion works with all my other plugins but not this one so I assume the problem with cmp is still there unless there is a new one. I don't know.

Can confirm that this is issue, and the multiple threads that were closed on the subject were less than helpful.
Please reopen this issue @pqn
Error executing luv callback:
....local/share/nvim/lazy/plenary.nvim/lua/plenary/curl.lua:274: post https://api.codeium.com/register_user/ - curl error exit_code=23 stderr={ "curl: (23) Failed writing received data to disk/application" }
stack traceback:
	[C]: in function 'error'
	....local/share/nvim/lazy/plenary.nvim/lua/plenary/curl.lua:274: in function '_user_on_exit'
	.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:240: in function '_shutdown'
	.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:47: in function <.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:38>
E471: Argument required
E471: Argument required
Error executing luv callback:
....local/share/nvim/lazy/plenary.nvim/lua/plenary/curl.lua:274: post https://api.codeium.com/register_user/ - curl error exit_code=23 stderr={ "curl: (23) Failed writing received data to disk/application" }
stack traceback:
	[C]: in function 'error'
	....local/share/nvim/lazy/plenary.nvim/lua/plenary/curl.lua:274: in function '_user_on_exit'
	.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:240: in function '_shutdown'
	.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:47: in function <.../.local/share/nvim/lazy/plenary.nvim/lua/plenary/job.lua:38>


Authentication in Bot framework

I have couple of queries on authentication mechanism between web api's with bot framework SDK and Azure hosted endpoint/Microsoft Cognitive  services.
I am aware that once we configure our web api's end point in azure bot services there is app id and password generated which we have to mention in our web.config for authentication between web api's and azure. Wanted to know what authentication mechanism Azure uses  for authenticating web api's. And similarly when we consume LUIS in our web api's and configure LUIS keys in config files, how web api's gets authenticated with LUIS.

The Microsoft Bot Framework team prefers that how to or advisory questions be submitted on Stack Overflow. The official Bot Framework Github repos are the preferred platform for submitting bug fixes and feature requests.

Essentially, the connector services utilize Oauth.
https://docs.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-connector-authentication?view=azure-bot-service-4.0#authentication-technologies
I don't know much about LUIS other than it a subscription key which provides access to the API:
https://westus.dev.cognitive.microsoft.com/docs/services/5890b47c39e2bb17b84a55ff/operations/590aff885aca2f09e404ec3f

More info for LUIS:
https://docs.microsoft.com/en-us/azure/cognitive-services/luis/luis-concept-keys

Thanks for the details...that helps.


Add lambda function that consumes eventbus

Description of changes:
This adds a new type of service called event-consumer that can be used to subscribe to events that have push onto the EventBridge bus. I've also added back the event publishing logic in the cart service that got lost for some reason.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

LGTM when you'll remove the .gitignore

Fixed!

LGTM when you'll remove the .gitignore

Fixed!


Clean up setup.py

This PR cleans up setup.py based on Composer's setup.py and is a follow up after #127. This is a better organized version of #126 as many of the changes made in #126 were already made in #127.
Specifically, this PR:

Gracefully handles missing torch while running setup.py
Gracefully determines the version of the package with a _version.py file
Adds an __init__.py file to MegaBlocks
Parses the README.md better for the pypi description

These changes pass all the tests on the Github Action on my local fork: https://github.com/eitanturok/megablocks/actions/runs/10183100358. It currently seems like there are issues with the GAs here.
In a separate PR we will update the package owner name and email. (Still waiting on Kobie to get back to me about this.)

Yep, copy and pasted from Composer!


cannot assign requested address

File "/usr/local/lib64/python3.6/site-packages/grpc/_channel.py", line 946, in call
return _end_unary_response_blocking(state, call, False, None)
File "/usr/local/lib64/python3.6/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNKNOWN
details = "Exception calling application: <urlopen error [Errno 99] Cannot assign requested address>"
debug_error_string = "{"created":"@1644900494.345978200","description":"Error received from peer ipv4:<IP_ADDRESS>:50051","file":"src/core/lib/surface/call.cc","file_line":1074,"grpc_message":"Exception calling application: <urlopen error [Errno 99] Cannot assign requested address>","grpc_status":2}"
Not sure why I am getting this?  I can wget and see my server but I keep getting this error.  Please help.

This doesn't look like an error within grpc itself. You're getting an error response from the execution of your RPC, which is the python error Exception calling application: <urlopen error [Errno 99] Cannot assign requested address>. Basically, gRPC did its job properly; it sent the RPC from your client to your server, but then the server code that's running caused a failure while running the service for said RPC.
Without further detail on what's going on in your server, I don't think we can help much more, but in all cases, everything is fine from the gRPC point of view, it's the application layer that's at fault and is being reported here.

Thank you, that pointed me in the right direction.  It was an issue in another part of my code.  A little hard to track down, but with your info I found it!  Thanks again.


Missing CONTRIBUTING.md File in Repository

The repository currently lacks a CONTRIBUTING.md file, which is an important resource for guiding potential contributors on how to engage with the project effectively. A CONTRIBUTING.md file outlines the contribution guidelines, coding standards, and procedures for submitting pull requests, thus streamlining the contribution process and ensuring consistency across contributions.
Could you please assign this issue to me under GSSOC 24.

@andoriyaprashant Please assign this issue to me, I will try to fix it in within 24 hrs.


this repo lack git tags

This repo lack tags / releases, does this mean it works only for latest koatty ?
recommend add git tags for this repo also, for better viewing code changes.

yarn.lock will lock dependent versions. Unless otherwise specified, it is recommended to use the version specified by the project


Unable to find image 'tensorflow-ll-stack:latest' locally

I have problem with Unable to find image 'tensorflow-ll-stack:latest' locally.
This problem comes up when Im excecuting
docker run -v c:/full/path/to/the/clone:/home/jovyan/work -it --rm -p 8888:8888 tensorflow-ll-stack

Hi @Adsyarif, glad to have you over at this new repo!
I think your issue is the same as this existing one. I've provided a resolution there that has worked for other users. Hopefully I'll have time over the next few days to formally update the instructions in this repo to detail usage of the Docker image I've already built instead of you needing to create the Docker image yourself.

it still dosent work. If im wrong with the command line. I just copy and paste from the guidelines
 docker run -v %cd%:/home/jovyan/work -it --rm -p 8888:8888 dltfpt-stack
PS C:\Users\adris\OneDrive\Documents\DLTFpT> docker run -v %cd%:/home/jovyan/work -it --rm -p 8888:8888 dltfpt-stack
docker: Error response from daemon: create %cd%: "%cd%" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path.
See 'docker run --help'.

Oh I just realized you're running Windows. That is tricky for me to debug as I don't have access to a Windows machine.
That said, I'm still pretty sure the docker run step (Step 6 in the Windows installation instructions) isn't the issue. I think it was the preceding step (Step 5).
Earlier tonight, I updated Step 5 from being a docker build call to a docker pull call. Have you run the new Step 5 in the Windows instructions? That is: docker pull jonkrohn/dltfpt-stack:videos

A few other ideas in case you continue to run into issues, @Adsyarif:

Perhaps StackOverflow or some tutorial can provide guidance on how to run the command line / resolve your error on Windows? Regrettably, I haven't used Windows in several decades so can't be of much help. It seems like the most recent error you're getting is related to specifying the path correctly, so might be easy to fix with someone who knows the Windows command line.
Could you use Google Colab in the cloud instead of installing the Jupyter notebooks locally? That's my number-one way of working with the notebooks in this repo anyway.
Could you install Ubuntu (a popular Unix OS) as a dual-boot OS on your Windows machine? You'll find that super helpful for lots of machine learning software in the future anyway.


feat: introduce --workflow-profile and --no-workflow-profile for additional workflow specific profiles that overwrite global profiles; add ability to define key-value CLI flags like --set-threads or --set-resources as multi-level dictionaries in profile config yaml files

Description

QC

[x] The PR contains a test case for the changes or the changes are already covered by an existing test case.
[x] The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

Hoi @johanneskoester
You are WAY too fast for my taste ;-)
Anyway, I like this very much indeed. I will test it by the end of the week (just that some more meetings are in the way to do this any sooner). Allow me a minor question: Why the original --no-workflow-profile flag and the explicitely required None to the --workflow-profile flag? If there is no such flag, it could just be ignored. Or am I missing something here?

Hoi @johanneskoester
You are WAY too fast for my taste ;-)
Anyway, I like this very much indeed. I will test it by the end of the week (just that some more meetings are in the way to do this any sooner). Allow me a minor question: Why the original --no-workflow-profile flag and currently the explicitly required None to the --workflow-profile flag? If there is no such flag, it could just be ignored. Or am I missing something here?

This is because of the behavior that if --workflow-profile is not specified the profile stored at workflow/profiles/default (if Snakefile is at workflow/Snakefile is automatically used. This default behavior is important to allow workflow designers to ensure certain flags are set. E.g. some default constraints on resources like for example:
resources:
  biomart_api_calls: 1

To ensure that some rule that queries biomart is not executed many times in parallel (which would lead to being blocked).


Not seeing files in the list of LeaderfFile

This is what I see:

vim or neovim?

[ ] vim
[ ] neovim

Output of vim --version or nvim --version:  NVIM v0.9.5
Output of :echo has("python"):  0
Output of :echo has("python3"):  1
Output of :echo &pythondll(only vim, not neovim):
Output of :echo &pythonthreedll(only vim, not neovim):
Output of :py print(sys.version):
Output of :py3 print(sys.version):  3.12.3 (main, Apr  9 2024, 08:09:14) [Clang 15.0.0 (clang-15<IP_ADDRESS>)]
Output of :echo g:Lf_Debug_Cmd: git ls-files  "." && git ls-files --others --exclude-standard  "."
Output of :echo g:Lf_FilesFromCache: 1
Operating system:

[ ] Linux
[ x] Mac OS X
[ ] Windows
[ ] Etc.

Configurations related to LeaderF in vimrc:

Describe your question, feature request, or bug.
Not see files when invoke :LeaderfFile
Steps to reproduce
Invoke :LeaderfFile
Actual behaviour

Expected behaviour
Showing some files

After running the debug command, I see git ls-files and look like LeaderF expect the files to be in git history. So I commit the files to git and see it populates. However this is not my wanted behavior. Not sure how did git ls-files is used here. Would not see files unless they were committed to git.

let g:Lf_UseVersionControlTool=0

That solves the problem. Though I wonder why it's not by default. Make me pull my hair for a while.


merge post branch docs changes into new-site

Changes that have been piling up in the master branch need to be merged into the new-site branch.

Will address as part of grommet/grommet#568


Improve parsing of Urxvt and SGR mouse escape codes.

Urxvt mouse escape codes look like this: ESC[35;123;321M
When ttymouse=urxvt, <UrxvtMouse> would be set to only ESC[, and
then some logic later in check_termcode would react to that, and parse
the rest of the data after it. However, ESC[ is also the prefix of some
other escape codes, like <zHome> (ESC[8~). So, those would stop
working when ttymouse=urxvt, as they are then read as <UrxvtMouse>8~.
This patch changes <UrxvtMouse> to not match just ESC[, but match the
full escape code: ESC[*M, where the asterisk is a wildcard. Such a
'wildcard' functionality was already available for ;*X and <M-O>*X,
and is now extended to work for any *X. This way, the <UrxvtMouse>
escape code is no longer a prefix of other escape codes. The logic in
check_termcode parsing the mouse commands is changed accordingly.
This patch does the same for <SgrMouse>, for ttymouse=sgr. However, SGR
mouse escape codes for release events end in m, instead of M. Now
the full escape code is matched, instead of just the ESC[ prefix, these
different escape codes now have different keys in keymap.h: <SgrMouse>
and <SgrMouseRel>.
Tested in Urxvt v9.22 with ttymouse=urxvt, and in Xterm 327 with
ttymouse=sgr.

Tested on Archlinux with urxvt 9.22 and vim 8.0.0628, works fine. Thanks for the patch!


[📊 DATA] Pots: Average Donation in Pot 🟠

Description
Objective / Business Insight

see average donation size
see average donation per pot
see correlation between donation size and matcihng amount

Acceptance Criterion

[]

Data Sources
Similar Queries
Challenges
Resources
How to Present

https://flipsidecrypto.xyz/mlungisi/q/6XiawDg9m-Am/avg_donation_in_pots


Add GPG format git configuration on GPG setup

Why:
Closes #21020

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Thanks for the review and the changes.
This is the same article which push me to contribute on this page


Add support for parsing configs provided through CLI as a TOML doc

Currently we simply consider configs provided through the CLI as string key-value pairs. Since now we support retrieving configs as maps and arrays, we need to reconsider this approach and run the CLI params through the TOML parser as well.

This module is deprecated and is not maintained in Ballerina now. Hence closing the issue.


Fixing description fields in external_ids to be single valued error spotted by @turbomam See also https://github.com/microbiomedata/DataHarmonizer/issues/24

@turbomam Please update the changelog.

Closing after merging near-identical #237


Standard 2nd Ed. Character Sheet (US-Letter)

Love the new default sheet:
A reminder, since you probably already know... but Severity calculation for weapons (at least Phaser type-2) is wrong, it is still being calculated as Severity from 2e PLUS Sec level of character, the latter is no longer a thing in 2e, right?
On a personal request, the "ink" intensity on the blue and gold lettering of the Attributes and Departments sections of this new 2e pdf  output is... light (at least when printed from a high-end color laser printer). It is even a little light on my monitor which is a 4K high refresh screen.  On a bright tablet (ipad m4 from 2024, so OLED screen), all the lettering for all colors is fine.
Charles

For the sake of brevity... additional typesetting issue previously brought up for a few examples, but I missed this. Under the talent "Walking Encyclopedia":
"Once per session, when you attempt a task, you may spend 2 Momentum (Immediate) to gain an addition- al focus..."
so, it is the "addition- al" part

I think I've addressed the weapons dice issue.


Remove noarch, only require colorama on win.

Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Non noarch packages should have python requirement without any version constraints.
Non noarch packages should have python requirement without any version constraints.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@asford ok, we can do this, but for my benefit, what's the problem with colorama on non-windows?

🙏 Thanks.
Not a "problem" per-say, as such much as an unfortunate interaction with awscli and their colorama version pin.
awscli only recently relaxed their colorama version pin to allow 0.4.4 in the 1.23.0 release,
which means it's hard to install awscli alongside other cli tools that may pin against older version of botocore et al.
This change unblocks a few cases where we want to co-install an older awscli along side pipx via conda.

Ok, got it, thanks for the explanation, @asford!
Just to sanity-check, why would you want to co-install awscli rather than pipx or condax install it?
Please ignore in case I'm being annoying here. 😁

Not a problem. I would, in fact, like to pipx or condax install it.
I'm working in the constraints of an existing environment that was designed before pipx/condax were well established.
This env is a bit more "classic" conda, with a single conda environment encapsulating a number of different tools.
First step in refactoring that environment reliably is... co-installing pipx and condax with our existing tools.
Second step is... begin replacing existing tools with pipx/condax variants.
😉

@asford any objections to reverting this to noarch? Pipx is and will remain solvable to the current version without colorama.

No objections, thanks. Just getting it installed w/o colorama is ideal.


W3M Image Display not available.

Hey there,
I found this project via your blog, but I was unable to leave a comment there - great writeup! The video with SRV was very cool :) I'd like to get your client working but I'm getting the error "W3M Image Display not available.". It has been logged to Sentry with Event ID: cccc4fd7d0694392bfd0fb491aa5c233. Hopefully you can find it :) Do I need to install a certain dependency?

Installing w3m and w3m-img fixed that issue. Now once the command line starts keyboard input it not recognised and I am stuck at the donation screen.

Wait a second, I'll push an update in a minute.

Check it out now. Update with npm i -g tidal-cli-client@latest

I updated, but still stuck.

You press ":" and cant input?

Okay, I missed that part. I could select the Copy PayPaaal link and Copy Bitcoin Address with my mouse, but not keyboard, so I assumed it was not receiving my keyboard input. Working - thanks!

Also, now the dependencies are auto installed


GPUParticles2D not emitted in web export

Godot version
4.0.1.stable
System information
Windows 10, NVIDIA GeForce GTX 960M (<IP_ADDRESS>41), GLES3
Issue description
GPUParticles2D are not displayed when exporting for web. CPUParticles2D appear to work as expected but the GPUParticles2D displays nothing upon playing the exported project in a browser.
I've tested in Chrome and Firefox using both Forward+ and Compatibility renderers which all produce the same result for me. Additionally, I've tested a similar project exported using Godot 3.5.2 GLES3 and found that both particles are displayed and emitting correctly in that version.
Steps to reproduce

Create a new project using either Forward+ or Compatibility renderer
Create a main scene with Node2D as the root node
Set up a CPUParticles2D node and a GPUParticles2D node as child nodes
Export for web with default settings
Deploy a dev server to play/debug the exported web project

Minimal reproduction project
Web Particle Test.zip

I've tested in Chrome and Firefox using both Forward+ and Compatibility renderers which all produce the same result for me.

Only the Compatibility rendering method can be used in HTML5.

Trying to use another rendering method will always use Compatibility once you export to HTML5 (check the Project Settings).

I figured they were the same output but I didn't know there was a setting there. Thanks for the heads up.
And I hope you don't mind I saved the log to a file. It would've been a crazy long comment otherwise.
localhost-1679612291758.log

I can reproduce this. GPU particles do not work in web export because of some shader issue:

How can I change this file in the build? I modified it, recompiled and I get the same error in an exported game.

Never mind, I got it. Here is the fix:
https://github.com/godotengine/godot/compare/master...cody82:godot:fix-html-particle-shader

@cody82 Please open a pull request against the master branch with your changes :)
Remember to modify your changes to follow the code style guidelines too.


Create Man Page

If Run had a proper man page, it would feel more like an official *nix tool.

@geoelectric Thinking this might a task you could help with?

Yeah, quite possibly! Let me do a little research this weekend and see what's involved. I'm kind of hoping I don't have to learn groff, but I imagine there's boilerplate out there.
If it's easy enough, I'll at least do a PR with a placeholder that you can update with real text.


callback processing failing with undefined method 'new_session_path'

Hi,
This may be a versioning thing.
I have gate-sso running fine as far as calling out to Google and perfoming the authentication.
But the callback fails with the following error:
I, [2017-06-22T13:40:05.585781 #28966]  INFO -- : Processing by Users::OmniauthCallbacksController#failure as HTML
I, [2017-06-22T13:40:05.585869 #28966]  INFO -- :   Parameters: {"state"=>"a71627ca1b391967fd1f1d31f24c910ce7242c0a3ace090b", "code"=>"4/5YdFdw-hglL9Ve76qMGwIFRaqQzJfqmM_qjDszWCsww"}
I, [2017-06-22T13:40:05.605512 #28966]  INFO -- : Completed 500 Internal Server Error in 20ms (ActiveRecord: 0.0ms)
F, [2017-06-22T13:40:05.609879 #28966] FATAL -- :
NoMethodError (undefined method `new_session_path' for #Users::OmniauthCallbacksController:0x0055a61faf52d8
I have tried adding following method (and varients) to application_controller.rb:
def new_session_path(scope)
new_user_session_path
end
but it doesn't help.
I am running with the following gem versions:
devise (4.1.0)
omniauth (1.6.1)
omniauth-google-oauth2 (0.4.1)
omniauth-oauth2 (1.4.0)
Any help appreciated.
Thanks.

I ran into this yesterday, and just knew what I was missing. Though nothing mentioned on the doc, you need to enable Google+ API as well. But this error still should be fixed. It should skip the session part and return a failure page instead of a server crash.

Hi, malikid
I tried enabling Google+ API as you suggested, but didn't make any difference.  No sign of any request trying to hit google+ api for the project. No sign of any changed behaviour at all in fact.

Can you update to lastest code and tell me if you are still having this error, there was version mismatch i have updated the gems.

Hi Ajey,
Yes, that's fixed it.  I get logged in now and presented with QR code and
openvpn download button.  (Now just need to
work out how it is supposed to integrate with openvpn).
Thanks
John
On Sat, Jul 29, 2017 at 7:36 AM, Ajey Gore<EMAIL_ADDRESS>wrote:

Can you update to lastest code and tell me if you are still having this
error, there was version mismatch i have updated the gems.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gate-sso/gate/issues/11#issuecomment-318808702, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADWYMPXjN0SNbdtcJqtyZ0H9C6m-LCnWks5sStL5gaJpZM4OCUh2
.

Very simple. Install open VPN and point the scripts to easy RSA and you
should be good to go
On 1 Aug 2017 18:58, "John Lane"<EMAIL_ADDRESS>wrote:

Hi Ajey,
Yes, that's fixed it. I get logged in now and presented with QR code and
openvpn download button. (Now just need to
work out how it is supposed to integrate with openvpn).
Thanks
John
On Sat, Jul 29, 2017 at 7:36 AM, Ajey Gore<EMAIL_ADDRESS>wrote:

Can you update to lastest code and tell me if you are still having this
error, there was version mismatch i have updated the gems.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gate-sso/gate/issues/11#issuecomment-318808702, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/
ADWYMPXjN0SNbdtcJqtyZ0H9C6m-LCnWks5sStL5gaJpZM4OCUh2>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gate-sso/gate/issues/11#issuecomment-319338543, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAKK_hTnO05SrA4ds0bCsUuoSgtlp-6Nks5sTwS6gaJpZM4OCUh2
.

Hi Ajey,
Yes, sorted. Works great.
On Tue, Aug 1, 2017 at 3:30 PM, Ajey Gore<EMAIL_ADDRESS>wrote:

Very simple. Install open VPN and point the scripts to easy RSA and you
should be good to go
On 1 Aug 2017 18:58, "John Lane"<EMAIL_ADDRESS>wrote:

Hi Ajey,
Yes, that's fixed it. I get logged in now and presented with QR code and
openvpn download button. (Now just need to
work out how it is supposed to integrate with openvpn).
Thanks
John
On Sat, Jul 29, 2017 at 7:36 AM, Ajey Gore<EMAIL_ADDRESS>wrote:

Can you update to lastest code and tell me if you are still having this
error, there was version mismatch i have updated the gems.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gate-sso/gate/issues/11#issuecomment-318808702,
or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/
ADWYMPXjN0SNbdtcJqtyZ0H9C6m-LCnWks5sStL5gaJpZM4OCUh2>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gate-sso/gate/issues/11#issuecomment-319338543, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAKK_
hTnO05SrA4ds0bCsUuoSgtlp-6Nks5sTwS6gaJpZM4OCUh2>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gate-sso/gate/issues/11#issuecomment-319387599, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADWYMJ1v85TYGzrgEAY0pi7HN8ZkTOz8ks5sTzaXgaJpZM4OCUh2
.


NER output

I want to ask about where can the type and meaning of the fourth column of the output be found?

I think the question was answered here! https://github.com/undertheseanlp/ner/issues/4


Asmanjas Details added

This Pull Request resolves Issue #1
Description:
In this Pull Request we have done the following additions/edits for the code:

Asmanjas hello world added


added build dependency 'clang-tidy'

Signed-off-by: Staschulat Jan<EMAIL_ADDRESS>

obsolete. Fixed in  commit
https://github.com/ros2/rclc/commit/b56b4532885a3da0f1cf2a22e1ab4eb1c880f85d


Custom Headers in Options Rest API Response (Cloud-formation is autogenerated)

Is your feature request related to a problem? Please describe.
We have a few instances where we'd like to send some information via headers in conjunction with a get request, where tenant details are passed alongside a request (as a user can have multiple tenant accounts) - If we update the cloud formation template to add this header everything works - however adding/updating the Rest API re-generates the cloud formation template and we lose our changes.
Describe the solution you'd like
Update api-params.json to allow for additional custom headers to be added. [whilst at it might as well consider doing the same for custom origins]
Describe alternatives you've considered
We have been modifying the cloud formation after the generation and re-pushing changes. Then one has to go to the API Gateway and publish to make sure header changes are propagated.
This works but is prone to mistakes if you forget to repeat the steps.

@jonmifsud could you please send details about how you utilize the Amplify CLI, and what steps you've to repeat/do to achieve the correct deployment you're aiming for?

Sure @attilah.
So in once instance, we're using the amplify-cli to create a new API Endpoint with a lambda function, which in addition to the user needs to additionally take input to know which tenant the user wants to query.
This is particularly as we want to keep get requests as get requests without sending tenant ids within the URL to standardise the API and not expose that in the URL.
This is also important when we expose some endpoints as public APIs as a single user can manage multiple tenants. The current tenant cannot be stored in a session as there may be requests for different tenants at the same time.
What we end up doing right now is update the cloud formation template to add these within the allowed options response for the endpoint. However every time we add a new path to the API the cloud formation re-builds and we lose the changes having to re-apply them.
Without these headers, chrome would reject the request as the options request does not return this as an accepted header.
I hope this gives a bit more clarity of what we're doing and why.

@jonmifsud thanks for the explanation, it is more clear now, I'll discuss this with the team and get back to you.

@attilah thank you. Happy to propose PR changes with a bit of direction where things are if it makes sense to make this change.

@jonmifsud the more the merrier they say, so your feedback is welcome, go ahead and add it please!

@jonmifsud Do you need some help with the PR?

Yeah actually a couple of pointers would help we still got this issue.
I know we got to modify apigw-cloudformation-template-default.json.ejs within amplify-category-api package inside the cloud formation templates.
To be able to add a variable value to method.response.header.Access-Control-Allow-Headers
What I've done for now is update it to "method.response.header.Access-Control-Allow-Headers": "'Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token,X-Amz-User-Agent<%= props.paths[i].headers %>'",
Which looks like it's working though probably not the cleanest solution.

Is it just me or does the current definition of Access-Control-Allow-Headers prevent you from sending a whole range of headers to the REST API?

@kaustavghosh06 / @attilah - not sure if you guys are still on the project. A recent update seems to have broken our work-around completely for this.
Since the cloudformation-template.json was moved into the build folder it can no longer be edited to add custom headers... any pointers of how we can get a PR for this submitted?

@jonmifsud use amplify override api https://docs.amplify.aws/cli/restapi/override/


feat(analytics): divide analytics and metrics databases

Linked Issues

Closes #926

Notes to Reviewer

As a reviewer, please pay particular attention to the following areas when reviewing this PR and tick the above boxes after you have completed the steps.
Config Changes

[ ] Ensure proper order in which CLI and config arguments are applied.
[ ] Ensure that config changes work with individual build features by running cargo ci-check-features.

INX Changes

[ ] Run chronicle using an INX connection.

Database Changes

[ ] Review database queries for correctness/conciseness.
[ ] Ensure queries are supported by indexes if needed.
[ ] Check for breaking changes in the data model and matching (conventional) commit message prefix.

Whoops, totally forgot.


Feature: Backport DetourAttach overloads to C++11

Follow-up to #178
Microsoft Reviewers: Open in CodeFlow

Thank you @sylveon!


etcd autoscale setup

I hope there is a chance to be have an autoscale for etcd. Similar to what high-availability of controller can do.

Thanks for posting this!
Not sure it is feasible to auto-scale a metadata store like Etcd in kube-aws but I'll keep this open for a while to hear from the community.

I think it can be closed as duplicate of https://github.com/coreos/kube-aws/issues/27

@redbaron AFAIK, no. #27 may utilize ASGs for discovery and recovery but not for auto-scaling.

https://github.com/coreos/kube-aws/issues/27 is about implementing etcd management in a proper way, which may or may not include autoscale, but it got to be decided in the context of that discussion.

The primary intent of #27 is indeed for discovery and recovery, but i think you'd get "autoscaling" for free. I don't know why you'd want such a critical part of the system to be autoscaling - in my experience the only reason for having multiple etcd nodes is for concistency, not at all performance. (it could be argued that adding more nodes makes things slower)
Sorry for the lack of progress on #27 - i'm still too busy to work on the poc and i have to digest the changes in this repo. Things have been moving fast. :)

My idea here is to have an auto-scaling group setup, wherein when one etcd instance failed/terminated/gone, another instance will pop up and then join to the etcd cluster. Yup Im also on the consistency actually rather performance. As long as the users will not worry the sudden collapse of an etcd instance, I think there will be a reassurance that the cluster can recover, automatically.

Ah, then we can close this in favor of #27, right?
I had originally thought of something like "Autoscale/Automatically scale-out etcd cluster by automatically scaling up all the etcd nodes one by one without downtime to improve both write/read qps a etcd cluster can serve" for "autoscaling of etcd", which didn't seem to be something covered by #27.

I actually haven't check yet the #27 , if it is also included in #27 , I think we can close this. With your idea above @mumoshu , I think it would be great to have that kind of feature also in the future! Right now, the etcd part of high-availability setup is probably the weakest point for me, since there is still a possibility that instance may go down for sometime and there is no auto-scaling configured yet. User might take a manual task to add another instance and join it to the etcd cluster. I think once we have added this, devops will have a higher confidence in the setup.  thank you guys for making kube-aws awesome!. :)

@billyteves Thanks for the comment!
Yes, I agree to every point and that's what I believe to be already included in #27.


Is it possible to use only on Bluetooth

I don’t own Yale smart link but I have a table lock so is it possible to use only Bluetooth?

This tweak must work with the link bridge, it's because that I can't crack the bluetooth package and simulate it for now. I can only simulate the API request to trigger the bridge.


add(plugins): Downwind CSS Easings

Name
Link

Downwind CSS Easings
https://github.com/downwindcss/easings

Extends transition-timing-function utilities.

[x] My item is in the right category
[x] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] I have read and followed the contribution guidelines

Side Note: Downwind CSS is my GitHub organization. Not a typo of Tailwind CSS

Can you resolve the conflicts?

Can you resolve the conflicts?

I merged upstream master, but so many files have changed :sweat:
Should I abort this PR and create a new one?

Not sure why it closed the PR, but I updated your branch, and you can open a new PR. 👍

Thank you for the review @innocenzi
A new PR is #360


Fixes #YUPTOO-53 - Truncate value for tags with more than 250 char

Co-operated changes similar to foreman-rh-cloud, please refer https://github.com/theforeman/foreman_rh_cloud/blob/master/lib/foreman_inventory_upload/generators/tags.rb#L63.

adding @san7ket and @upadhyeammit in cc. Please request to review newly added changes.

Codecov Report
Base: 78.09% // Head: 78.33% // Increases project coverage by +0.23% :tada:

Coverage data is based on head (83c691e) compared to base (265e903).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #53      +/-   ##
==========================================
+ Coverage   78.09%   78.33%   +0.23%
==========================================
  Files          22       22
  Lines         598      600       +2
==========================================
+ Hits          467      470       +3
+ Misses        131      130       -1

Flag
Coverage Δ

unittests
78.33% <100.00%> (+0.23%)
:arrow_up:

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

Impacted Files
Coverage Δ

yuptoo/modifiers/transform_tags.py
100.00% <100.00%> (+5.88%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

/retest


fixed a bug where horizontal Slicer would invert y axis projections

"horizontal" orientation is rarely used, but when using displaying the zebrafish brain for an internal demonstration i think i found that the Y axis was inverted resulting in a projection that had some dis-orienteering results.
Additionally i added the possibility to create a Slicer by giving a position that is a numpy.number as well
Description
What is this PR

[x] Bug fix
[ ] Addition of a new feature
[ ] Other

Why is this PR needed?
Allow better interoperability with scientific code using numpy and keeping a consistent visualization of the projected cutting planes
Is this a breaking change?
no
Does this PR require an update to the documentation?
no
Checklist:

[x] The code has been tested locally
[ ] Tests have been added to cover all new functionality (unit & integration)
[ ] The documentation has been updated to reflect any changes
[ ] The code has been formatted with pre-commit

i feel like since i moved the slicer to using vectors for defining the slicing plane, some default values could be better defined.
If you feel like this is not the best configuration, we could talk about them here!

Thank you!
The default values I am speaking about are the u0 & v0 and u1 & v1  vectors that define the slicers:

the two vectors also define, for each of the possible positions (horizontal, sagittal and coronal) the x and y axes onto which the 3D shapes are projected into 2D. Their values are thus important in defining which is up and down, left and right. While also being making sure that the normal vector u0×v0 is facing u1×v1 normal vector.
I tried to tweak these parameters myself, but i think it greatly depends on the atlas used. For instance, Allen's Y axis is ~reversed, causing sagittal projections to be flipped.
This particularity with the Y-axis, i think, is not be always true for all atlases and animals

Sorry I think I still don't understand!
All BrainGlobe atlases have the same orientation, and follow numpy convention. In some cases though, this may be different to how they are defined elsewhere (e.g. the Allen has a slightly strange coordinate system). Would you mind creating an issue to describe what the problem is?


Can't install

Hello, I tried to install your module, however react/babel loaders fail on this line https://github.com/posabsolute/redux-flash-notification/blob/master/src/component/growler.js#L12 - @ keyword is not recognized by them on this line:
@connect(mapStateToProps, mapDispatchToProps)

What does @ mean? It's not JS/JSX keyword I guess, I know it only from coffee script.
Maybe you could write a build script that would generate dist version of your plugin that you would push to npm registry so it won't be necessary to compile it using additional loaders?
Your module look cool by the way, looking forward to be able to use it in my project, thanks.

sorry for the late comment, it means you did not enable es7 decorators in your babel config


Convert between LAMMPS and GSD format

Given the similarities of lammpsio objects to gsd.hoomd objects, it would be nice to have a method to convert between them. This would involve adding methods that can cast lammpsio.Snapshot <-> gsd.hoomd.Snapshot. @astatt

I have some python scripts to do some of it in a haphazard way. I think I/we would have to think carefully about what information should be transferred, and also what to do with cases like changing particle numbers etc...
But I think this would be a really nice feature to have for those of us who use both lammps and hoomd in some capacity.

We are doing this too, so it would definitely be helpful to have.
Also this raises a good point:

cases like changing particle numbers etc...

Currently, the id is assumed to form a compact range (i.e., 1, 2, ... N). LAMMPS does not require this, and the most common case where it would be an issue is if you only write out a subset of the system rather than everything. We haven't dealt with this because we are using these mostly for initialization, or post-processing of full trajectories. Let me open an issue to fix this.
One other small thing to be careful of is that LAMMPS and HOOMD have different conventions for defining the simulation box, so there needs to be both a conversion that occurs and also a check for compatibility (all HOOMD boxes can be LAMMPS boxes, but not all LAMMPS boxes can be HOOMD boxes).


API Problems

I have problems with lunarclient API, I cannot even launch lunarclient
but if I use my browser to open API links, I can see all the thing that the API want the program to know.
And one thing that is really magical, if I try to launch lunarclient, I can launch it after several tries, but that is just the situation happens to  main form, if I try to launch the game, no matter how many times I tried, there are always errors(about API) or just stuck in UPDATEING the game with 100% progress.
I tried reinstalling, disabling my Firewall and Antivirus and changing my DNS server to <IP_ADDRESS> and <IP_ADDRESS>. But they can't help me solve the problem, how can I solve it?
Here are the log files
main.log
renderer.log

this isn't the place for this go to https://support.lunarclient.com/ for help with the client.


Fix: Pilot crash when set illegal host in sidecar resource

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Hi @ydh926. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test


Warning with core 2023.7.0

What version of Music Assistant has the issue?
Latest integration
The problem
After upgrading to core 2023.7.0. , the mass integration triggered a warning
How to reproduce
Update to latest core, having the integration installed
Relevant log output
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:371
First occurred: 23:09:17 (5 occurrences)
Last logged: 23:09:17
Entity None (<class 'custom_components.mass.media_player.MassPlayer'>) is implicitly using device name by not setting its name. Instead, the name should be set to None, please report it to the custom integration author.
Additional information
No response
What version of Home Assistant Core are your running
2023.7.0
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Raspberry Pi

Yes was reported in discord here https://discord.com/channels/753947050995089438/1098936700434124811/1123977134289993880 and Marcel said it would be fixed soon
I’ll add to the backlog just to make sure it is tracked

I'm not sure how this works, when it's fixed will I need to back out of this install? Will someone announce here that a solution was found?

Not sure what you mean about backing out of the install. A subsequent beta will fix this. You can monitor the backlog to see when it is fixed.

Seems fixed with latest integration b1

Sweet, still getting same error. I assume I need to reinstall/download/tweak something? A brief explanation to send me in the right direction would be really appreciated.

You need to enable the option in HACS that allows you to see beta updates.

Seems fixed with latest integration b1

Yep, got it. Thanks for the patience.

You need to enable the option in HACS that allows you to see beta updates.


KAFKA-3166; Disable SSL client authentication for SASL_SSL security protocol (backport)

Backport of https://github.com/apache/kafka/pull/827 to 0.9.0 that only includes the essential code changes (excluded the test changes due to conflicts).

Tests passed locally.

@harshach, any chance you could merge the backport too? Thanks.

@ijuma done

Thanks!


WiP stats: remove virtual and multiple inheritance from stats, inline HeapStatData into counters and gauges

This is based on #7364 can the PR cannot be reviewed in isolation till that's merged.
Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

Hey Matt -- it's worth doing a taste-test here before an official review because I think you might not love the trade-off of less multiple/virtual inheritance here, as it is achieved via more templating. It does have significant memory benefit though as having a linear chain appears to save 8 bytes per object.

/azp run

/retest

I think this is ready review now.  Matt, do you want someone else to take a first pass?

/azp run

/azp envoy-macos


Style a footer for the site

Create a flashly footer (see: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/footer) at the end of the home page and any subsequent pages that includes a mention of "P2P Hack Club", and some text like:

This site is open source. Improve this page.

This is a "first-timers-only" issue. That means that we are requesting that only those new to open source try this one out! Please ask as many questions as you need, I am here to help you create your first contribution to open-source :D

I'm going to reopen this issue with a focus on styling the footer with the great baseline code that #9 added!

Reopening per #11

hello @thatrobotdev can i work on this issue?
Previously i have worked on the styling of these two projects
https://aniket1104.github.io/Frontend_templates/weather_webpage/main.html
https://namankhare.github.io/yet-another-tip-calculator/

@aniket1104 this is being worked on by @ArijitAcharjee411

Hi ! Is this issue still open ? If it is I would like to work on it


Automated cherry pick of #9627: fix(region): support rds secgroup operation

Cherry pick of #9627 on release/3.5.
#9627: fix(region): support rds secgroup operation

Codecov Report

Merging #9651 (8ece9d8) into release/3.5 (6a15e02) will increase coverage by 11.92%.
The diff coverage is 1.85%.

@@               Coverage Diff                @@
##           release/3.5    #9651       +/-   ##
================================================
+ Coverage         5.98%   17.90%   +11.92%
================================================
  Files              796       85      -711
  Lines           125693     8923   -116770
================================================
- Hits              7522     1598     -5924
+ Misses          117504     7153   -110351
+ Partials           667      172      -495

Flag
Coverage Δ

aFlag
17.90% <1.85%> (+11.92%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

.../monitor/alerting/conditions/suggestrulereducer.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/conditions/suggestquery.go
2.00% <2.00%> (ø)

pkg/util/seclib2/seclib.go
80.39% <0.00%> (-5.66%)
:arrow_down:

pkg/util/ansiblev2/session.go
0.00% <0.00%> (ø)

pkg/keystone/models/regions.go

pkg/monitor/models/alert.go

pkg/multicloud/ucloud/ucloud.go

pkg/multicloud/esxi/host.go

pkg/keystone/tokens/handlers.go

... and 590 more

Continue to review full report at Codecov.

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


Integration tests

adding integration tests to CI

I'm more in favour of using ava to test this stuff, but bash is fine. The important thing is that it's works.
Since we're testing the ignite boilerplate, thoughts of moving this there?
Also, may as well delete packages/ignite-integration-tests now that we've switched to shell-based testing.

@skellock - let's talk about this.  I might have taken us backwards in time.  Since we did not have any e2e integration tests, I added this.  Are you saying packages/ignite-integration-tests was doing this already?

The tests in our boilerplate are end-to-end tests.
We moved it over to ignite-ir-boilerplate-2016 when we moved the boilerplate out of here.  What's left in packages/ignite-integration-tests is low value and can become unit tests.
Most likely, @jamonholmgren can delete that when he de-lernas this repo.
The reason I like our ava tests is because we can use things like jetpack and things to do fancy stuff instead of bash tricks.  It's not without it's annoyances though (e.g. {preferLocal: false} when calling execa.
That's just my preference.  I care more about working tests than I do my preference though.

I'm a fan of moving to JS over bash as well.  I don't think anything was testing like this was.  Perhaps we re-write this test in JS at some later date?

I didn't see this until now. Whoops.


Crashing when i try to join a server or world

It crashes when ever i try to join a server or world, i play on feather client if it helps

feather client breaks many mods, use normal fabric


Vulnerability fixes

optionator, semver, word-wrap vulnerability has been fixed

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign so-sdhawan
You can assign the PR to them by writing /assign @so-sdhawan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Not needed anymore in the new major version released v3.0.3


Tracks are not automatically submitted after play

Summary
After tracks are played, scrobbles are not automatically submitted in the background. If the app is manually opened, there will be scrobbles in the local cache (and they will automatically scrobble a few seconds after the app is open).
Details

Handset: LG Nexus 5X
Android: 7.1.1
Music app: Google Play Music

Description
It seems like other users are having this issue as well—similar behavior was described by @marekceglowski in #369. I'm trying to pinpoint when I first started noticing this happen, but I feel like it was in the past month? It's hard for me to say because I installed the app maybe two months ago, so it's possible this has always been happening without me noticing (or there is just a huge delay before the app scrobbles them in the background now).
I am using standard battery conservation settings, so as far as I am aware, it should be submitting the scrobbles after each play.
Expected behavior

Play song
After 50% play-through, SLS detects play
Play is scrobbled to server immediately

Actual behavior

Play song
After 50% play-through, SLS detects play
3, Play is stored in local cache
SLS is opened, all scrobbles submit to servers

Is there anything else I can do to help understand this problem or help with debugging?

After paying closer attention to this, it seems like it depends on whether the phone is charging. Whenever it's connected to a power source, scrobbling happens instantly (or at least, from as far as I've noticed). If I'm off of power (even with a full battery) and not actively using my phone, the problematic behavior occurs.

@jflory7, have you exempted SLS from battery saving? Sometimes there are multiple settings to change to disable all types of power saving for specific background apps. Additionally, if you use a 3rd-party battery saving app, such as JuiceDefender, you'll have to exempt SLS there too. This is probably why scrobbling happens instantly when plugged in, because power saving is disabled.

@jflory7, this is the same issue as reported in #357 (and likely other bugs as well)

I exempted it from battery optimizations in the battery settings. I don't use any third-party apps, so will see if anything changes.

I'm getting exactly the same behavior. For me it seems to be the case after an upgrade from Android 6 to 7 on my Samsung S6.
Everything is catched from Google Music (my player of choice) but until I open the app the cache won't be submitted.
Android 7 - at least the Samsung edition added some new battery saving options - and I have done my best I believe to remove SLS from being messed with - but nothing it seems will (sadly) correct this currently.

Confirmed.
Since Android 7 SLS does not scrobble in the background anymore. You have to scrobble manually via the app in order to update your listen track record.
Solution (tested):
Disable battery optimization for SLS. After that SLS does work in the background as intended.
How to exclude apps from battery optimization:
https://android.gadgethacks.com/how-to/android-basics-disable-doze-app-standby-for-individual-apps-0168960/

For what it's worth, exempting it from battery optimization did fix this issue for me. However, in some music players like Google Play Music, the last track played in the queue is not scrobbled until:

User manually goes into app and scrobbles the last song manually
A new song is played

However, I think that would probably be a different bug report…

@jimbo27 - thanks for that tip. Have enabled this for an S6 (once I managed to find the equilivent menu in Samsung's mutated Android 7). See how we go.