No issue - QR-Code with logo possible?

I've just today stumbled over your integration and it perfectly fits into my use case at home. I am able to request vouchers via signal message and get one back together with the QR-Code to connect to the WiFi. All together it was a good bit of effort but it is working. It even detects if there are no more vouchers and generatss some new ones first. All in all I am pleased and even more thankful towards you, the mastermind and genius behind this integration.
Thus said, improving the QR-Code entity with an optional logo or image would be small but tremendous improvement.
Cheers from Germany
Dunkelschunkel

Thank you very much for your feedback.
The logo in the QR code is a great idea. The QR code in my integration was actually just a quick win without much effort, as I use the QR code implementation of the Unifi AIO library:
https://github.com/Kane610/aiounifi/blob/469aabdc478009a48352d8259d2f463598836bff/aiounifi/models/wlan.py#L92
The library in turn uses the Segno library with a ready-made method:
https://segno.readthedocs.io/en/latest/special-qrcode-factories.html
Unfortunately, there is no option to integrate own picture. But it looks to me as if we can do all sorts of things with QR codes using the Sengo Library. So we have to completely rebuild the Wifi QR code thing with the Sengo methods. That looks like a lot of work.
You are welcome to give it a try.

@ufozone No coding skills required I hope. Thanks for shedding some light on that topic though.
Dunkelschunkel

I wanted to try it out now. That's where I am right now:

I am now making the source code look good again and adding a new setting in setup and options flow.

@Dunkelschunkel , done! But a lot of work and a lot of new dependencies. I can't promise that the feature will remain as it is in the future.

@Dunkelschunkel , done! The feature is available in the main branch and will be released in version 1.2.3 in few weeks. But a lot of work and a lot of new dependencies. I can't promise that the feature will remain as it is in the future.

@ufozone ,
Wow, this looks quite pleasant. And all this for a "won't fix". I don't know what to say except I am eager to see and test it by myself. In the meantime I used another QR code integration available via hacs to bring some color into the mix. But I'll switch to your QR code as soon as it goes live.
Thanks.

@Dunkelschunkel , you can also select the main branch as the source for the integration in HACS. Then you can test the new feature immediately. The new version will be at least two weeks away.
Can you please name the QR code integration you are currently using?
What does your configuration looks like?
Please include a screenshot of your implementation.
As written, I have introduced a lot of new dependencies with the feature and cannot promise that the feature will remain available in future versions.
I would therefore like to document an alternative solution right away.

Hi @ufozone,
The QR-Code integration is called QR code generator and the link is https://github.com/DeerMaximum/QR-Code-Generator
They can use templates when creating QR-Codes and even create WiFi codes. And some more options are colors, border and size.
Mine is just a hint of blue I am also using with my hotspot portal.

Of course, I hadn't thought about the fact that the new function should still be documented. I'll add it to the ToDo list.
The logo just needs to be in a place that Home Assistant can access. It makes no sense to specify a fixed location, as there are too many different installation constellations. The folder /config/custom_components/unifi_voucher/ is over written when the integration is updated. I recommend the persistent folder /config/www/.


Follow Chef standards for attribute tree naming

This just renames base or coopr_base to match the cookbook name, which is the best practice for creating Chef cookbooks.

this is a pretty big incompatible change for anyone with templates using the old names.  at the least it needs major version bump.  we should consider adding backwards compatibilty, or if this is even really necessary.

The necessity of it is really just for correctness. Also, I plan on replacing our current internal-only customized "base" cookbook with this public version, reducing maintenance costs in the long run. I can add backwards compatibility and major version bump it.

👍 lgtm


[Scalability] Enable Horizontal Pod Autoscaler (HPA) for Alcor deployment

Configure cluster and network configuration to meet the requirements on using Metrics Server:

Metrics Server must be reachable from kube-apiserver by container IP address (or node IP if hostNetwork is enabled).
The kube-apiserver must enable an aggregation layer.
Nodes must have Webhook authentication and authorization enabled.
Kubelet certificate needs to be signed by cluster Certificate Authority (or disable certificate validation by passing --kubelet-insecure-tls to Metrics Server)
Container runtime must implement a container metrics RPCs (or have cAdvisor support)

Deploy Metrics-Server in cluster.

Deploy Horizontal Pod Autoscaler for each deployment with customized hpa yaml.

Some preliminary test in the Medina cluster appears to be quite promising.
The current 0.19 release already contains a lot of new features therefore we decided to move this feature to 12/30 release.

@yanmo96 We need to test this PR and get it merged by 2/28.


fix: env should be equal to qa

Related issue

Proposed Changes

Checklist

[] I have read the contributing guidelines.
[] I have inspected the website preview for accuracy.
[] I have signed off my issue.

Thank


NIFI-3701 Documentation improvements for 1.x

Admin Guide:

Corrected/updated access policy tables to better align with UI
Split policy tables into one for Global, one for Component
Corrected empty authorizations.xml and users.xml cluster usage
Updated description for nifi.templates.directory properties description
Added note about using List/Delete Queues when clustered

User Guide:

Added note about Back Pressure defaults
Updated "Configure Site-to-Site server NiFi instance" section as it referenced 0.x behavior

Reviewing...

I will make the two minor fixes above and merge. Thanks @andrewmlim .

I ran contrib-check and verified that the generated docs look good. Merged to master.

Sorry @andrewmlim I accidentally got a space into the commit message. Can you please close this branch?

Closing.


API Rate Limits

What is the rate limit for use of the Bookings API?
I read through this article but it doesn't reference Bookings specifically and only talks about service accounts which Bookings does not use.

I suggest using https://developer.microsoft.com/en-us/graph/support to submit questions and feature requests. Thanks.


Feature Request: add tags/x-title

The tags/name is used both as a reference key (`tags: []) as well as text to be displayed on the sidebar and the content.
This mix usage prevents i18n.
I would suggest to add tags/x-title and use it for display instead of the name.
This would be a solution for redoc, but I also think that it can also be fixed at OpenAPI by allowing tags: ['string' | 'Reference']

Redoc already has this functionality just with different name: x-displayName


Android compatibility

@andrewssobral how to make this library work on android?

Hi @sagar1garg , unfortunately I don't have experience on Android to help you on that, but there's a small tutorial explaining how to build the Java wrapper for bgslibrary here: https://github.com/andrewssobral/bgslibrary/wiki/Wrapper:-Java


Installation fails with "python setup.py egg_info" when

When installing the requirements via "pip install -r requirements.txt" after activating the venv, I get the below error.
I was able to fix it following the advice of https://stackoverflow.com/questions/35104097/how-to-install-psycopg2-with-pg-config-error, but it'd be handy if it worked "out of the box", e.g. if this could be added as a dependency.
Collecting psycopg2-binary==2.8.5
  Downloading psycopg2-binary-2.8.5.tar.gz (381 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 381.7/381.7 KB 9.3 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error
  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [23 lines of output]
      running egg_info
      creating /tmp/pip-pip-egg-info-vkrr4ivr/psycopg2_binary.egg-info
      writing /tmp/pip-pip-egg-info-vkrr4ivr/psycopg2_binary.egg-info/PKG-INFO
      writing dependency_links to /tmp/pip-pip-egg-info-vkrr4ivr/psycopg2_binary.egg-info/dependency_links.txt
      writing top-level names to /tmp/pip-pip-egg-info-vkrr4ivr/psycopg2_binary.egg-info/top_level.txt
      writing manifest file '/tmp/pip-pip-egg-info-vkrr4ivr/psycopg2_binary.egg-info/SOURCES.txt'
      Error: pg_config executable not found.
      pg_config is required to build psycopg2 from source.  Please add the directory
      containing pg_config to the $PATH or specify the full executable path with the
      option:
          python setup.py build_ext --pg-config /path/to/pg_config build ...
      or with the pg_config option in 'setup.cfg'.
      If you prefer to avoid building psycopg2 from source, please install the PyPI
      'psycopg2-binary' package instead.
      For further information please check the 'doc/src/install.rst' file (also at
      <https://www.psycopg.org/docs/install.html>).
      [end of output]
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

As said in the error, use and "pip install psycopg2-binary" and remove "psycopg2-binary==2.8.5" from the requirement.txt

I appreciate that the error message says to do that, but my point is that the requirements.txt should be valid if this is a consistent error.


Make TableContext::getTableFromName public

Required for https://github.com/Medology/stdcheck.com/pull/5030

Testing file changes were not found.
Paging @johnnie502 to review the back-end work in this pull request!
Paging @PrinceMegahit to review the testing work in this pull request!


Meshery bash installer incorrect

Description
From Vaibhav Bisht:

The curl install url is incorrect.
currently it is: curl -L https://git.io/meshery | ADAPTERS=istio PLATFORM=kubernetes bash -

Expected Behavior

it should be curl -L https://meshery.io/install | ADAPTERS=istio PLATFORM=kubernetes bash - (edited)

Hi,
I would like to work on this.


OpenComputers recipes

Whenever crafting several of the OpenComputers recipes that require chisels and hammers  it spawns a duplicate pair of tools and throws them out whenever closing the crafting grid.

Fixed in 2.21.7


Epic: convert all core views to NautobotUIViewSet

Proposed Changes
Sequel to #1902 - convert all other core views to use NautobotUIViewSet and remove the existing generic view classes once they are no longer used.
Justification
DRY / making it so there's one way to do things / reducing likelihood of code drift between the two patterns.

Duplicate of #1569?


Compilation error for naming conflicts with namespace names

This should address https://github.com/microsoft/qsharp-compiler/issues/575.

@swernli I believe it should be sufficient to check that a declaration doesn't conflict with the full namespace name. Checking that it doesn't conflict with a (C#) partial namespace name should not be needed for the autogenerated code to work fine - correct me if you see an issue with that.


Temp fix to pip install cell

This is a re-PR from PR#174 that temporarily replaces the pip install cell to install the most recent sparclclient version. We are waiting for the sparclclient to be updated on gp12. Assigning to @rnikutta as reviewer to Approve and merge

@jacquesalice Two things, please clarify:

sparclclient is already updated (as of this afternoon): import sparcl; sparcl.__version__ --> '1.2.0'
This temp fix PR now has conflicts with master.

Do we really need this temp fix?

@rnikutta oh, it is? Was Mike able to update the stack? If it has been updated, then you're right this temp fix is not necessary. This branch is getting a little messy, so I think I'm just going to create a new branch with a new PR and add the notebook there (keeping the pip install cell as it was). Sorry!

@jacquesalice sorry I thought I had included you in the emails (but it was only Mike, Igor, Stephanie).
Do you need to make a new branch? Just close this PR #178, and we're good, no?

@rnikutta oh.....! That would've been useful info!! But the notebook that's currently in Master isn't the updated one with DESI EDR. So yes I do need to create a new PR and close this one. The new PR is here: https://github.com/astro-datalab/notebooks-latest/pull/179

Closed. See new PR here: https://github.com/astro-datalab/notebooks-latest/pull/179


fix(slashing-protection): limit min-max surround epoch lookback to 4096

Motivation
Closes https://github.com/ChainSafe/lodestar/issues/5356
Description
Limits number of epochs in the past to check for surrounding attestations (min-span) to 4096.
DB size
Running with 2k keys, the DB size was initially 4GB and is now reduced to 100MB.
Metrics
These are the metrics when running a VC with 2k keys and an empty db.
There are still quite a lot of read/writes but it goes down very fast compared to initially and does no longer cause instability in VC.

Request times do not show any I/O lag, previously was running into timeouts (10 seconds).

For the first 1-2 minutes there is still a increased step times diff but it goes down very fast, after a few minutes instead of hours as before.

Metrics look good to me now, there are no big issues and also need to keep in mind that those metrics are collected running 2k validators which is not a normal setup. This also only happens if the db is empty, meaning for most setups only on initial installation.

:tada: This PR is included in v1.9.0 :tada:


Add Percentage Discount Handler

Added a discount handler for discounts with a percentage

Hi @GertTimmerman !
Thanks for this PR! This is a nice feature for the upcoming v2.
So can you merge this into v2-develop instead? In terms of Coupons nothing has changed of yet.

Hi @GertTimmerman !
Thanks for this PR! This is a nice feature for the upcoming v2.
So can you merge this into v2-develop instead? In terms of Coupons nothing has changed of yet.

Yeah, this would come in handy for sure. Currently we have our own packages setup and basic sales section. In the sales sections we can add discounts as a percentage of the main subscription packages. We would love to use this in Cashier Mollie. R
The reason we are considering to move to Cashier Mollie is that we are already using Mollie and we love the whole packkage and especially the pro rating options. Currently it is tough for us to do x% discount for all packages and move remaining discount to next package when custom upgrades. Seems we can get this mostly done with Cashier Mollie.. but percentage discount we will have to add as a custom piece of code now it seems.


'Param' with $data expression has unexpected _POST results

When using $data expression in params, the $data in CGridview is incorrectly posted.
'id',
[
	'class' => 'editable.EditableColumn',
	'name' => 'end_datetime',
	'editable' => [
		'params'=>[
			'testId'=>'$data->id',
		],
		'url'=>$this->createUrl('schedule/editableupdate'),
	],
],

The expected $_POST results for params['testId'] is 16; however, $data->id from the final row of the current page is being used instead..
Request Method:POST
Form Data
name:end_datetime
value:01:00:00
pk:16
testid:10  // This should be the same as the pk above

Any help would be great!  Thank you.

Yes this is a bug, if i use the editable Column the params sent to the post were the params of the "last added column" (last row). So the "dynamic" parameters aren't dynamically set at all.
Btw the scenario was always wrong if i have rows with different scenarios (e.g. insert and update scenario).
I found that if i set
[
    'class' => 'editable.EditableColumn',
    'name' => 'end_datetime',
    'editable' => [
        'params'=>[
            'testId'=>'$data->id',
        ],
        'htmlOptions => [
            'data-scenario' => '$data->scenario',
            'data-testId' => '$data->id',
        ],
        'url'=>$this->createUrl('schedule/editableupdate'),
    ],
],

That inside the js in the save function the this.options.scenario as well as the this.options.testId is correctly set. But the "submitted" data in this.options.params which is an array with the additional params has the data values from the "last row".  These are also the parameters which where only set "once" in the js call where editable column is enabled. So the commit https://github.com/vitalets/x-editable-yii/commit/c4660a490aa80277c0b52bfc779f07a3fe78982a wasn't working since then for EditableColumns if each row has other params "values".
The problem with those "params" parameter is that is also used to add the CSRF Token.
And this is added regardles if params is an array or an js function. Because params could also be something like this:
    'params' => 'js: function(params) {
                    //originally params contain pk, name and value
                    params.scenario=$(this).data().scenario;
                    params.testId=$(this).data().testId;
                    return params;
   }',

But then also the data-attribute values must be added to each link by the HtmlOptions.
And then you will get a problem with the current code because the CSRF Token is added to params which destroys the params if its not an array (so there is a check also needed).
But i think if Params is an array and those htmlOptions data-attribute fields are set those should be then used for posting.
And therefore I have also created a pull request:
https://github.com/vitalets/x-editable-yii/pull/141


Sit infront of existing MySQL server

Hi, would something like this be able to act as a MySQL passthru where noria acts as the cache layer infront of MySQL but the storage and data processing is all done by MySQL itself (or MariaDB).
Or does the way that the dataflow work invalidate this as a concept?

A possible set up for something like this could be using a regular MySQL database along with some kind of change capture tool like Debezium.
It would add a lot of infrastructure (For Debezium, you'll need a Kafka cluster, so by extension also a zookeeper cluster), so in terms of infrastructure efficiency it does not make a lot of sense, but building a simple pipe line that funnels your changes 1-1 into a Noria database would give you an interesting way to run a Noria cluster using actual production data without much risk (as you can rebuild the Noria cluster at any time from the source database or Kafka)
Also that source database does not need to be a MySQL, it can be anything that Debezium supports.
If you have an existing system based on a relational database and you need to add-on a ridiculous read capability, this might be a way.
Did anyone look into a set up like this?

Considering trying to set Noria up as a replication slave to the main MySQL instance we have as an experiment, using binlog replication. I think this would cover what you are looking for (tho MySQL specific). Probably will be putting some time aside end of the month to try this out and see where it gets us.

For me, it looks more logical to focus on (essential) MySQL compatibility, thus the contributors and maintainers don't need to spend time and energy on this, and users don't need to worry about using MySQL as a back-end.

Considering trying to set Noria up as a replication slave to the main MySQL instance we have as an experiment, using binlog replication. I think this would cover what you are looking for (tho MySQL specific). Probably will be putting some time aside end of the month to try this out and see where it gets us.

@alexsnaps Did you ever try this? I'd be very interested in Noria as a read replica.

Hi @sandinmyjoints, this is a feature I'm currently working on implementing for Noria. Do you want to email me at<EMAIL_ADDRESS>to tell me more about your specific use case? (I'll then make sure to support it)

@alanamarzoev Thanks -- email sent!


Small improvements of docs

fix links to sample sts manifests for manual restore + specify container when kubectl exec into the backup-restore-sidecar pod of the helper sts

Thanks for the contribution!


Git create template using kauemurakami is incorrect

Hi,
Thank you for the wonderful package! This improves the productivity of programmers using flutter-getx tremendously.
As per the kauemurakami pattern, a module is basically a screen that contains binding, controller, and the view file inside the module folder. This approach keeps the related files of a view together rather than keeping similar types of files together. This is also an accepted best practice in Angular. The GetCli, creates subfolders for controllers, binding, and view which contradicts the pattern.
If a view contains additional widgets, it goes in on a widget folder under the module folder.
Other than this, Get-Cli is a treasure :smiley:

Thanks for watching...
Some time ago I added an option to remove the subfolders.
no pubspec.yaml do seu projeto
add:
get_cli:
  sub_Folder: false


CSS Conflicts

I'm using bootstrap as my CSS framework. That framework defines a css class called .modal. That causes the add-to-homescreen modal to be stretched out since it also uses the .modal classname. You probably want to have webpack (or something else) add a namespace/prefix to all of the classnames used, or have your css rules only apply within the top level div made by the library.

hi @makinde , sorry for delay, i didnt see this issue until yesterday.  ive renamespaced all the css and made a new release 1.1 to fix this.
Please reference the latest release with the fix (ie using jsdelivr with tag 1.1 as shown here)


[TC-441] - corrects reset password link to match format of TP

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/67/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/69/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR/107/


starting in local system

Hi,
Is it possible for you to make a 2 mins short video on how to start and run commands.
Thanks!
Amit

Hello @Ak-Srivastav just follow the installation guide!

@Ak-Srivastav To connect to the database, edit the .env file to add the following key-value pairs: DB_HOST, DB_USERNAME, DB_PASSWORD, and MYSQL_DATABASE. These must correspond to the database setup on your local system. Once you have completed this step, please follow the instructions provided. I have added the .env file; kindly pull it. My main system is currently offline, so I will add the SQL file to the repository as soon as it is back online. Please be patient in the meantime.

I have added the sql file pull it


integration: Fix default branch API url for hosted bitbucket server

Noted in https://github.com/backstage/backstage/issues/4121#issuecomment-764735647
Docs https://docs.atlassian.com/bitbucket-server/rest/7.9.0/bitbucket-rest.html#idp184
I think there are more problems that exist with hosted bitbucket server and URL Reader. Thinking about deploying a trial version soon to test it all out. sigh
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

@regicsolutions if it's possible, I know you're on Bitbucket Server too, could you test this PR?
Can you add files that are in bitbucket server into the catalog-import plugin?

@regicsolutions if it's possible, I know you're on Bitbucket Server too, could you test this PR?
Can you add files that are in bitbucket server into the catalog-import plugin?

@benjdlambert What should we do about this?
I am running a Bitbucket server using their docker image. And have spotted more errors. e.g. The commits URL
https://github.com/backstage/backstage/blob/664dd08c95801870a9434ec8d4b76b979a3bd4e0/packages/backend-common/src/reading/BitbucketUrlReader.ts#L148
is wrong for Bitbucket server and will only work for bitbucket.org.
It should be this (docs: https://docs.atlassian.com/bitbucket-server/rest/7.9.0/bitbucket-rest.html#idp222)
http://custombitbucket.com/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/commits

for Bitbucket server.
I think I can continue to push the changes to this branch.

@benjdlambert What should we do about this?
I am running a Bitbucket server using their docker image. And have spotted more errors. e.g. The commits URL
https://github.com/backstage/backstage/blob/664dd08c95801870a9434ec8d4b76b979a3bd4e0/packages/backend-common/src/reading/BitbucketUrlReader.ts#L148
is wrong for Bitbucket server and will only work for bitbucket.org.
It should be this (docs: https://docs.atlassian.com/bitbucket-server/rest/7.9.0/bitbucket-rest.html#idp222)
http://custombitbucket.com/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/commits

for Bitbucket server.
I think I can continue to push the changes to this branch.

Is the latest nightly build a good version to test?> @regicsolutions if it's possible, I know you're on Bitbucket Server too, could you test this PR?

Can you add files that are in bitbucket server into the catalog-import plugin?

Is the latest nightly build a good version to test?> @regicsolutions if it's possible, I know you're on Bitbucket Server too, could you test this PR?

Can you add files that are in bitbucket server into the catalog-import plugin?

Is the latest nightly build a good version to test?

@regicsolutions Since the PR hasn't been merged, it is not available in any nightly release. So, please test on this branch orkohunter/default-branch-bitbucket-server in this repository. :)

Is the latest nightly build a good version to test?

@regicsolutions Since the PR hasn't been merged, it is not available in any nightly release. So, please test on this branch orkohunter/default-branch-bitbucket-server in this repository. :)

@benjdlambert What should we do about this?
I am running a Bitbucket server using their docker image. And have spotted more errors. e.g. The commits URL
https://github.com/backstage/backstage/blob/664dd08c95801870a9434ec8d4b76b979a3bd4e0/packages/backend-common/src/reading/BitbucketUrlReader.ts#L148
is wrong for Bitbucket server and will only work for bitbucket.org.
It should be this (docs: https://docs.atlassian.com/bitbucket-server/rest/7.9.0/bitbucket-rest.html#idp222)
http://custombitbucket.com/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/commits

for Bitbucket server.
I think I can continue to push the changes to this branch.

I guess we need to check what the hostname is and do different things depending on if it's bitbucket.org or on prem bitbucket. We do something similar in the publisher to create repo's but it's nasty.

@benjdlambert What should we do about this?
I am running a Bitbucket server using their docker image. And have spotted more errors. e.g. The commits URL
https://github.com/backstage/backstage/blob/664dd08c95801870a9434ec8d4b76b979a3bd4e0/packages/backend-common/src/reading/BitbucketUrlReader.ts#L148
is wrong for Bitbucket server and will only work for bitbucket.org.
It should be this (docs: https://docs.atlassian.com/bitbucket-server/rest/7.9.0/bitbucket-rest.html#idp222)
http://custombitbucket.com/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/commits

for Bitbucket server.
I think I can continue to push the changes to this branch.

I guess we need to check what the hostname is and do different things depending on if it's bitbucket.org or on prem bitbucket. We do something similar in the publisher to create repo's but it's nasty.

I guess we need to check what the hostname is and do different things depending on if it's bitbucket.org or on prem bitbucket. We do something similar in the publisher to create repo's but it's nasty.

@benjdlambert Indeed. That is how it's being done here as well. host === bitbucket.org.

I guess we need to check what the hostname is and do different things depending on if it's bitbucket.org or on prem bitbucket. We do something similar in the publisher to create repo's but it's nasty.

@benjdlambert Indeed. That is how it's being done here as well. host === bitbucket.org.

@backstage/maintainers A gentle reminder that we should have this before tomorrow's release. 🙏

@backstage/maintainers A gentle reminder that we should have this before tomorrow's release. 🙏

@regicsolutions can you confirm that this works for you?

@regicsolutions can you confirm that this works for you?

@regicsolutions can you confirm that this works for you?

Just tested this, I imported the springboot template, created a component and get this when i try to view docs:
Error: No preparer registered for type: "bitbucket" at Preparers.get (webpack-internal:///../techdocs-common/src/stages/prepare/preparers.ts:68:13) at new DocsBuilder (webpack-internal:///../../plugins/techdocs-backend/src/DocsBuilder/builder.ts:70:31) at eval (webpack-internal:///../../plugins/techdocs-backend/src/service/router.ts:139:27) at processTicksAndRejections (internal/process/task_queues.js:97:5)

@regicsolutions can you confirm that this works for you?

Just tested this, I imported the springboot template, created a component and get this when i try to view docs:
Error: No preparer registered for type: "bitbucket" at Preparers.get (webpack-internal:///../techdocs-common/src/stages/prepare/preparers.ts:68:13) at new DocsBuilder (webpack-internal:///../../plugins/techdocs-backend/src/DocsBuilder/builder.ts:70:31) at eval (webpack-internal:///../../plugins/techdocs-backend/src/service/router.ts:139:27) at processTicksAndRejections (internal/process/task_queues.js:97:5)

@regicsolutions can you confirm that this works for you?

Just tested this, I imported the springboot template, created a component and get this when i try to view docs:
Error: No preparer registered for type: "bitbucket" at Preparers.get (webpack-internal:///../techdocs-common/src/stages/prepare/preparers.ts:68:13) at new DocsBuilder (webpack-internal:///../../plugins/techdocs-backend/src/DocsBuilder/builder.ts:70:31) at eval (webpack-internal:///../../plugins/techdocs-backend/src/service/router.ts:139:27) at processTicksAndRejections (internal/process/task_queues.js:97:5)

Hey @regicsolutions ! Can you add files that are in bitbucket server into the catalog-import plugin? Or register an existing component using a URL that is from bitbucket server (on the Catalog Create New Component page)?
The TechDocs error is expected. What is the backstage.io/techdocs-ref value in the Entity's metadata annotation? TechDocs does not support bitbucket directly if the URL looks like bitbucket:.... You can see here. Instead try using the URL Reader in TechDocs to support Bitbucket. https://backstage.io/docs/features/techdocs/how-to-guides#how-to-use-url-reader-in-techdocs-prepare-step. But I am afraid, for TechDocs, there is another PR https://github.com/backstage/backstage/pull/4231 which you will need to be merged into this branch for URL Reader to work with bitbucket server. Hence, please don't worry about TechDocs when testing this branch here.

@regicsolutions can you confirm that this works for you?

Just tested this, I imported the springboot template, created a component and get this when i try to view docs:
Error: No preparer registered for type: "bitbucket" at Preparers.get (webpack-internal:///../techdocs-common/src/stages/prepare/preparers.ts:68:13) at new DocsBuilder (webpack-internal:///../../plugins/techdocs-backend/src/DocsBuilder/builder.ts:70:31) at eval (webpack-internal:///../../plugins/techdocs-backend/src/service/router.ts:139:27) at processTicksAndRejections (internal/process/task_queues.js:97:5)

Hey @regicsolutions ! Can you add files that are in bitbucket server into the catalog-import plugin? Or register an existing component using a URL that is from bitbucket server (on the Catalog Create New Component page)?
The TechDocs error is expected. What is the backstage.io/techdocs-ref value in the Entity's metadata annotation? TechDocs does not support bitbucket directly if the URL looks like bitbucket:.... You can see here. Instead try using the URL Reader in TechDocs to support Bitbucket. https://backstage.io/docs/features/techdocs/how-to-guides#how-to-use-url-reader-in-techdocs-prepare-step. But I am afraid, for TechDocs, there is another PR https://github.com/backstage/backstage/pull/4231 which you will need to be merged into this branch for URL Reader to work with bitbucket server. Hence, please don't worry about TechDocs when testing this branch here.

For what it's worth, I have tested it by running Bitbucket server using their docker image and executing readTree when the backend starts.
    const bitbucketServer = await reader.readTree(
      'http://localhost:7990/projects/PROJ/repos/techdocs-test/browse',
    );
    console.log(bitbucketServer.etag);
    console.log(await bitbucketServer.files());

in packages/backend/src/plugins/techdocs.ts backend file where an instantiated reader is passed from createPlugin.
And I have added documentation reference for the API endpoint changes - which are really just two

Default branch URL.
Commits URL was non-existent for bitbucket server.

For what it's worth, I have tested it by running Bitbucket server using their docker image and executing readTree when the backend starts.
    const bitbucketServer = await reader.readTree(
      'http://localhost:7990/projects/PROJ/repos/techdocs-test/browse',
    );
    console.log(bitbucketServer.etag);
    console.log(await bitbucketServer.files());

in packages/backend/src/plugins/techdocs.ts backend file where an instantiated reader is passed from createPlugin.
And I have added documentation reference for the API endpoint changes - which are really just two

Default branch URL.
Commits URL was non-existent for bitbucket server.

For what it's worth, I have tested it by running Bitbucket server using their docker image and executing readTree when the backend starts.
    const bitbucketServer = await reader.readTree(
      'http://localhost:7990/projects/PROJ/repos/techdocs-test/browse',
    );
    console.log(bitbucketServer.etag);
    console.log(await bitbucketServer.files());

in packages/backend/src/plugins/techdocs.ts backend file where an instantiated reader is passed from createPlugin.
And I have added documentation reference for the API endpoint changes - which are really just two

Default branch URL.
Commits URL was non-existent for bitbucket server.

@OrkoHunter  i just re-tested, The catalog-info.yaml file in my template is using url:{{cookiecutter.storePath}} when i try creating a component with that template the output in the repo becomes this
(my project ID in this example is PID and repo name is BACKSTAGE)
  annotations:
    backstage.io/techdocs-ref: url:https://mybitbuckerserver.com/PID/BACKSTAGE

Which is not correct as i get a 404 when i try reaching that url the correct url should resolve to: https://mybitbucketserver.com/projects/PID/repos/BACKSTAGE/browse (browse isn't really required as if i just end it with /BACKSTAGE it will resolve to /BACKSTAGE/browse.... am i missing something?

For what it's worth, I have tested it by running Bitbucket server using their docker image and executing readTree when the backend starts.
    const bitbucketServer = await reader.readTree(
      'http://localhost:7990/projects/PROJ/repos/techdocs-test/browse',
    );
    console.log(bitbucketServer.etag);
    console.log(await bitbucketServer.files());

in packages/backend/src/plugins/techdocs.ts backend file where an instantiated reader is passed from createPlugin.
And I have added documentation reference for the API endpoint changes - which are really just two

Default branch URL.
Commits URL was non-existent for bitbucket server.

@OrkoHunter  i just re-tested, The catalog-info.yaml file in my template is using url:{{cookiecutter.storePath}} when i try creating a component with that template the output in the repo becomes this
(my project ID in this example is PID and repo name is BACKSTAGE)
  annotations:
    backstage.io/techdocs-ref: url:https://mybitbuckerserver.com/PID/BACKSTAGE

Which is not correct as i get a 404 when i try reaching that url the correct url should resolve to: https://mybitbucketserver.com/projects/PID/repos/BACKSTAGE/browse (browse isn't really required as if i just end it with /BACKSTAGE it will resolve to /BACKSTAGE/browse.... am i missing something?

@regicsolutions Wow, thanks for the detailed input. You raise two issues and I think they are valid

Scaffolder: {{cookiecutter.storePath}} is set incorrect in case of Bitbucket Server. It should be complete URL like https://mybitbucketserver.com/projects/PID/repos/BACKSTAGE/browse instead of https://mybitbuckerserver.com/PID/BACKSTAGE

Looking at Bitbucket Server documentation https://docs.atlassian.com/bitbucket-server/rest/7.9.0/bitbucket-rest.html#idp184

/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/default-branch
https://mybitbucketserver.com/rest/api/1.0/projects/HOOV/repos/123/default-branch should have resolved if HOOV and 123 exist.
Could this be a version issue, what is the version of your Bitbucket server?

@regicsolutions Wow, thanks for the detailed input. You raise two issues and I think they are valid

Scaffolder: {{cookiecutter.storePath}} is set incorrect in case of Bitbucket Server. It should be complete URL like https://mybitbucketserver.com/projects/PID/repos/BACKSTAGE/browse instead of https://mybitbuckerserver.com/PID/BACKSTAGE

Looking at Bitbucket Server documentation https://docs.atlassian.com/bitbucket-server/rest/7.9.0/bitbucket-rest.html#idp184

/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/default-branch
https://mybitbucketserver.com/rest/api/1.0/projects/HOOV/repos/123/default-branch should have resolved if HOOV and 123 exist.
Could this be a version issue, what is the version of your Bitbucket server?

@regicsolutions Wow, thanks for the detailed input. You raise two issues and I think they are valid

Scaffolder: {{cookiecutter.storePath}} is set incorrect in case of Bitbucket Server. It should be complete URL like https://mybitbucketserver.com/projects/PID/repos/BACKSTAGE/browse instead of https://mybitbuckerserver.com/PID/BACKSTAGE
Looking at Bitbucket Server documentation https://docs.atlassian.com/bitbucket-server/rest/7.9.0/bitbucket-rest.html#idp184

/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/default-branch
https://mybitbucketserver.com/rest/api/1.0/projects/HOOV/repos/123/default-branch should have resolved if HOOV and 123 exist.

Could this be a version issue, what is the version of your Bitbucket server?

I am running version 7.4.1 which should be using the same v1 API

@regicsolutions Wow, thanks for the detailed input. You raise two issues and I think they are valid

Scaffolder: {{cookiecutter.storePath}} is set incorrect in case of Bitbucket Server. It should be complete URL like https://mybitbucketserver.com/projects/PID/repos/BACKSTAGE/browse instead of https://mybitbuckerserver.com/PID/BACKSTAGE
Looking at Bitbucket Server documentation https://docs.atlassian.com/bitbucket-server/rest/7.9.0/bitbucket-rest.html#idp184

/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/default-branch
https://mybitbucketserver.com/rest/api/1.0/projects/HOOV/repos/123/default-branch should have resolved if HOOV and 123 exist.

Could this be a version issue, what is the version of your Bitbucket server?

I am running version 7.4.1 which should be using the same v1 API

Aha, thanks @regicsolutions!
The 7.4.1 version does not have the latest /default-branch endpoint.
https://docs.atlassian.com/bitbucket-server/rest/7.4.1/bitbucket-rest.html
cc @kaparwan for #4322 since you are running a 5.x version of Bitbucket server.
As @freben suggests, let's support both the endpoints - request /default-branch first, if it returns 404, try /branches/default.

Aha, thanks @regicsolutions!
The 7.4.1 version does not have the latest /default-branch endpoint.
https://docs.atlassian.com/bitbucket-server/rest/7.4.1/bitbucket-rest.html
cc @kaparwan for #4322 since you are running a 5.x version of Bitbucket server.
As @freben suggests, let's support both the endpoints - request /default-branch first, if it returns 404, try /branches/default.

Aha, thanks @regicsolutions!
The 7.4.1 version does not have the latest /default-branch endpoint.
https://docs.atlassian.com/bitbucket-server/rest/7.4.1/bitbucket-rest.html
cc @kaparwan for #4322 since you are running a 5.x version of Bitbucket server.
As @freben suggests, let's support both the endpoints - request /default-branch first, if it returns 404, try /branches/default.

Great, Thanks
One Question: You mention as Scaffolder: {{cookiecutter.storePath}} is not correct for the scaffolder and https://mybitbucketserver.com/projects/PID/repos/BACKSTAGE/browse is correct, this isnt clear to me given i want to auto generate a catalog-info.yaml once the repo is generated and wont know what the project name and repo name is and need to read it from the cookiecutter input variable.

Aha, thanks @regicsolutions!
The 7.4.1 version does not have the latest /default-branch endpoint.
https://docs.atlassian.com/bitbucket-server/rest/7.4.1/bitbucket-rest.html
cc @kaparwan for #4322 since you are running a 5.x version of Bitbucket server.
As @freben suggests, let's support both the endpoints - request /default-branch first, if it returns 404, try /branches/default.

Great, Thanks
One Question: You mention as Scaffolder: {{cookiecutter.storePath}} is not correct for the scaffolder and https://mybitbucketserver.com/projects/PID/repos/BACKSTAGE/browse is correct, this isnt clear to me given i want to auto generate a catalog-info.yaml once the repo is generated and wont know what the project name and repo name is and need to read it from the cookiecutter input variable.

@regicsolutions Hey! The catalog-info.yaml should indeed be auto generated and filled in by cookiecutter variables.
https://github.com/backstage/backstage/blob/a034569199aa59830aad18e2b6ea91253d8dbc70/plugins/scaffolder-backend/sample-templates/docs-template/{{cookiecutter.component_id}}/catalog-info.yaml#L8
This cookiecutter.storePath is a full URL to the newly created repository -

https://github.com/org/repo
https://gitlab.com/org/repo
https://mybitbucketserver.com/projects/PID/repos/BACKSTAGE/browse
...etc

You mentioned that in your case, cookiecutter.storePath resolved to https://mybitbuckerserver.com/PID/BACKSTAGE which is unexpected. If you are using the latest scaffolder plugins or if you are on the master branch, cookiecutter.storePath should have been the full Bitbucket URL. Please create an issue if this is not what happened. 🙏 I'll cc @benjdlambert for extra eyes.


add ConstrainedFloat, confloat, PositiveFloat and NegativeFloat types

Sorry, busy week back from holiday. Will look today.

lgtm, thanks a lot.


Rename website from fileutils to mpifileutils

Rename from fileutils to mpifileutils.
Remove (likely outdated) mailing list links.
Remove google analytics tracking code for the old fileutils.io

Closing as dupe of #79


[FLINK-5812] [core] Cleanups in the FileSystem class

The FileSystem class is overloaded and has methods that are not well supported.
This pull request does the following cleanups:
Commit 1:

Use the WriteMode to indicate overwriting behavior. Right now, the FileSystem class defines that enum and never uses it. It feels weird.
Remove the method FsDataOutputStream create(path, overwrite, blocksize, replication, ...), which is not really supported across file system implementations. For HDFS, the behavior should be set via the configuration anyways.

Commit 2:

Pull the safety net into a separate class
Extend the docs of the safety net.

All changes have to be made in a non-API-breaking fashion.

@StephanEwen Can this PR be closed?

Yes, it was accidentally merged together with another PR.
Since the changes were mostly comments and annotations, it should not be a problem.
Closing...


fix ksmc_suspendEnvironment() deaklock

after suspend all threads
vm_deallocate may cause deadlock

That's indeed a problem, but use threads after deallocated maybe dangerous.
In my point of view, use a global variable to reference suspended threads and deallocate it when ksmc_resumeEnvironment() called should be better.

Use an array of size 1000 to store threads

Add a WeChat? @ZhiyuWong

👍

Add a WeChat? @ZhiyuWong

OK

Use an array of size 1000 to store threads

How about use
static thread_act_array_t g_suspendedThreads = NULL;
static mach_msg_type_number_t g_suspendedThreadsCount = 0;
instead of an arbitrary size of threads array.

I think we can do it like this:
static thread_act_array_t g_suspendedThreads = NULL;
static mach_msg_type_number_t g_suspendedThreadsCount = 0;

void ksmc_suspendEnvironment()
{
#if KSCRASH_HAS_THREADS_API
    KSLOG_DEBUG("Suspending environment.");
    kern_return_t kr;
    const task_t thisTask = mach_task_self();
    const thread_t thisThread = (thread_t)ksthread_self();

    if((kr = task_threads(thisTask, &g_suspendedThreads, &g_suspendedThreadsCount)) != KERN_SUCCESS)
    {
        KSLOG_ERROR("task_threads: %s", mach_error_string(kr));
        return;
    }

    for(mach_msg_type_number_t i = 0; i < g_suspendedThreadsCount; i++)
    {
        thread_t thread = g_suspendedThreads[i];
        if(thread != thisThread && !isThreadInList(thread, g_reservedThreads, g_reservedThreadsCount))
        {
            if((kr = thread_suspend(thread)) != KERN_SUCCESS)
            {
                // Record the error and keep going.
                KSLOG_ERROR("thread_suspend (%08x): %s", thread, mach_error_string(kr));
            }
        }
    }

    KSLOG_DEBUG("Suspend complete.");
#endif
}

void ksmc_resumeEnvironment()
{
#if KSCRASH_HAS_THREADS_API
    KSLOG_DEBUG("Resuming environment.");
    kern_return_t kr;
    const task_t thisTask = mach_task_self();
    const thread_t thisThread = (thread_t)ksthread_self();

    if(g_suspendedThreads == NULL || g_suspendedThreadsCount == 0)
    {
        KSLOG_ERROR("we should call ksmc_suspendEnvironment() first");
        return;
    }

    for(mach_msg_type_number_t i = 0; i < g_suspendedThreadsCount; i++)
    {
        thread_t thread = g_suspendedThreads[i];
        if(thread != thisThread && !isThreadInList(thread, g_reservedThreads, g_reservedThreadsCount))
        {
            if((kr = thread_resume(thread)) != KERN_SUCCESS)
            {
                // Record the error and keep going.
                KSLOG_ERROR("thread_resume (%08x): %s", thread, mach_error_string(kr));
            }
        }
    }

    for(mach_msg_type_number_t i = 0; i < g_suspendedThreadsCount; i++)
    {
        mach_port_deallocate(thisTask, g_suspendedThreads[i]);
    }
    vm_deallocate(thisTask, (vm_address_t)g_suspendedThreads, sizeof(thread_t) * g_suspendedThreadsCount);
    g_suspendedThreads = NULL;
    g_suspendedThreadsCount = 0;

    KSLOG_DEBUG("Resume complete.");
#endif
}

Great. Thanks
I want to release memory in suspend.
But that is  not  necessary, suspend and resume will be  called in pairs.
Sent with GitHawk

Add a WeChat? @ZhiyuWong

OK

XiEJunYI_


fix: NCads_A100_v4 incompatible with fabric manager for MIG profile

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

hmmm im wondering if https://github.com/Azure/AgentBaker/pull/1338/files#diff-59521d60320265e88e46f4702029a64c03d857baee2923ff450f4997f6184fe8R253 is also breaking this
weirdly gpu profiles seem to partition fine without it, but mig mode change should require a reboot?
debug with a sample pod using MIG7g on A100 tomorrow.

confirmed earlier comments, driver install and everything works, mig-partition fails but curiously does not fail CSE (!) even though it looks like it should. guessing we are mistaking an exit code somewhere on systemctl restart (not a oneshot so guessing some service behavior comes into play for simple vs forking vs oneshot)
it fails only when trying to deploy a CUDA workload, with CUDA_ERR_NOT_INITIALIZED or similar, but then continues using CPU only (???)
so definitely need that reboot after gpu reset.
but should check current mig mode first, using nvidia-smi with format csv or similar.

I've tested this with:
"normal" GPU
Standard_NC6s_v3 - plain VHD - MIG N/A
Standard_NC6s_v3 - GPU VHD - MIG N/A
MIG-capable, single card, (incompatible with fabric manager)
Standard_NC24ads_A100_v4 - plain VHD - MIG disabled
Standard_NC24ads_A100_v4 - plain VHD - MIG7g
Standard_NC24ads_A100_v4 - GPU VHD - MIG disabled
Standard_NC24ads_A100_v4 - GPU VHD - MIG7g
MIG-capable, 8 card (requires fabric manager)
Standard_ND96asr_v4 - plain VHD - MIG disabled
Standard_ND96asr_v4 - plain VHD - MIG7g
Standard_ND96asr_v4 - GPU VHD - MIG disabled
Standard_ND96asr_v4 - GPU VHD - MIG7g
all cases seem to provision successfully. hit infoROM host platform bug 2x, but that's unrelated. all configurations seem able to run the sample mnist job from https://learn.microsoft.com/en-us/azure/aks/gpu-cluster#run-a-gpu-enabled-workload
this is really tough to test. it seems like the default job behavior is just to proceed with CPU. we need to grep the logs or have cuda fail on init deliberately if we don't find gpus.

nvidia-smi --query-gpu=mig.mode.current,mig.mode.pending --format=csv,noheader | tr -d ' '

useful to check current/pending mig mode, if mismatched on VM boot, likely host platform issue not us.


[KOGITO-336] Include DMN inside of Spring Boot archetype

I added "http*" for archetype application.properties so that generated DMN REST classes can be scanned. A package name of a DMN REST class is generated from its namespace. So this configuration works when DMN namespace starts from "http" or "https". According to DMN spec, namespace is anyURI. So it's not constrained to http/https but it's a reasonable default value for archetype?

namespace: anyURI [1] | This attribute identifies the namespace associated with this Definitions and follows the convention established by XML Schema.

I manually tested by dropping TrafficViolation.dmn (https://github.com/kiegroup/kogito-runtimes/blob/master/drools/kogito-dmn/src/test/resources/org/kie/kogito/dmn/TrafficViolation.dmn) into the generated project and confirmed that the generated REST endpoint works.
$ curl -d '{ "Driver": { "Points": 2}, "Violation": { "Type": "speed", "Actual Speed": 120, "Speed Limit": 100 }}' -H "Content-Type: application/json" -X POST http://localhost:8080/Traffic%20Violation

{"Violation":{"Type":"speed","Speed Limit":100,"Actual Speed":120},"Driver":{"Points":2},"Fine":{"Points":3,"Amount":500},"Should the driver be suspended?":"No"}

I think the Jenkins failure is not related to this PR.

Jenkins test again


add Infrastructure Lifecycle WG website content

Adds home page of the Infrastructure Lifecycle WG
Copied over our charter
Contains the start of our glossary

✅ Deploy Preview for tag-app-delivery ready!
Name	Link
🔨 Latest commit	0548837
🔍 Latest deploy log	https://app.netlify.com/sites/tag-app-delivery/deploys/66e54abc468e0800086ba86b
😎 Deploy Preview	https://deploy-preview-751--tag-app-delivery.netlify.app
📱 Preview on mobile
Toggle QR Code...

Use your smartphone camera to open QR code link.
To edit notification comments on pull requests, go to your Netlify site configuration.

Is it expected that this netlify preview deployment does not render the newly added Infrastructure Lifecycle pages?

Is it expected that the netlify preview deployment does not render the newly added Infrastructure Lifecycle pages?

No, that is definitely showing an issue. But the issue isn't your pages, it is the surfacing of your pages. You can go directly to the URLs like this: https://deploy-preview-751--tag-app-delivery.netlify.app/wgs/infra-lifecycle/
So what you need to add in is the addition of this WG to the different lists etc where the others are.

Is it expected that the netlify preview deployment does not render the newly added Infrastructure Lifecycle pages?

No, that is definitely showing an issue. But the issue isn't your pages, it is the surfacing of your pages. You can go directly to the URLs like this: https://deploy-preview-751--tag-app-delivery.netlify.app/wgs/infra-lifecycle/
So what you need to add in is the addition of this WG to the different lists etc where the others are.

Fixed @abangser! :)

@abangser, I've addressed the comments and feedback.


Unable to compile

I installed agda and I am able to use from my console. I added the atom extensions language-agda and agda-mode.
Still, when I try to compile an agda file, I get the following error message:
ghc: createProcess: runInteractiveProcess: exec: does not exist (No
such file or directory)

I am not really an expert of ghc, so this could well be a trivial issue

Interesting!
Could you provide the version of ghc and agda you are running? And also the code you want to compile.
ghc -V
agda -V

I'm running ghc-8.2.1 and agda-2.5.3 and I can compile the example provided by the manual just fine!

Thanks for your response. I realized that this is not a agda-mode issue. If I use the --compile option on the command line I get the same error message.
This is probably due to the fact that I installed ghc using stack and therefore I don't have a ghc command available (instead I have stack exec ghc).
Now I installed ghc globally and everything seems to work.


New Release: 0.1.0

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/99274
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" ba6fe5c6529cf1572f68d773470a98fbbefd50f1
git push origin v0.1.0


Change 'install.iss' to 'release.iss' and move to azure-pipelines

Codecov Report

Merging #40 (db3c9e6) into master (9a553f4) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #40   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            2         2
=========================================
  Hits             2         2

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 9a553f4...db3c9e6. Read the comment docs.


Not working on windows 10

Extension Name: html-language-features
Extension Version: 1.0.0
OS Version: Windows_NT x64 10.0.17134
VSCode version: 1.28.0

We have written the needed data into your clipboard. Please paste:
{
	"activationTimes": {
		"startup": false,
		"codeLoadingTime": 653,
		"activateCallTime": 384,
		"activateResolvedTime": 0,
		"activationEvent": "onLanguage:html"
	}
}

Please see #60318


Text Direction Error in Tesseract 5.0.0-alpha

Environment

Tesseract Version: 5.0.0-alpha
Commit Number: 916875d74a340e78be4f068d334a3a2d03986a0e
Platform: Windows 10, 64-bit

Current Behavior:
While using the api to get the "tsv" text from the file with PSM 12 mode (i need this mode because the documents have vertical and horizontal text), I am getting the output text like arabic writing (from right to left) and the original is written from left to right.
I am using spa.trainneddata from best tranning data dictionaries.

Original:

Output:

Expected Behavior:
Output text in same direction as the originial text (left to right writing).
Suggested Fix:

Let to force text direction on api.
Solve the bug (if it is a bug and not a dictionary problem).

Where is the tsv file?
Also, post tsv output you get by running tesseract from the command line.

with PSM 12 mode (i need this mode because the documents have vertical and horizontal text)

Try with psm 1.


Feature: OpenSea streaming API

Hey I just implemented the streaming API for a project of mine, maybe you would like to use it as inspiration.
https://github.com/cojodi/openseapy
I just tested it a bit, but as a general idea + the objects it suffices so far I think.

Thank you so much


Request : Money string

Hello, first of all I'd like to thank you so much for this memory patcher. I've only started using it for a week and I'm enjoying it so far but one thing I feel that is really missing is the Money string. I was wondering if this is even possible to add? Because I swear to god, I have poor eye sight and I can't even tell if it's 1m or 10m or whatever and I always have to get up really close to the screen just to check. xD
Thanks again!

This. With this feature, kanan can finally replace Abyss :^)


Add validation test that looks at file size

New validation tests currently check missing files and for invalid files based on file types. Add another check that looks at file size and flags:

File size outside of range of 95th percentile of old datastore
File sizes all the same for all files in a dataset (sign of invalid files)

This was addressed in #236


[backport] Disable Mergify's auto-merge

Backport of #5556 by @kmaehashi

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 9e773b3c992cdf2387b27778dfcd4e1b74f83756, target branch v9) succeeded!


Jesse: Watch hqns.ca

Jesse requests the watch of the watch_keyword hqns\.ca. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

hqns\.ca has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


pull request for e2e test at 12/07/2016 19:45:01

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


I want to see stats for please fix me

could be interesting for everybody ...

statistics about how many people has reached each rank in each level


Application for a Page

Vanity URL
songbactructuyen2
Your (nick)name
songbactructuyen2
Theme
Dark
Avatar URL
https://www.fb9.com/register?affid=110
Job
No response
Location
No response
About You
fb9
Links
No response
Acceptable Use Policy

[X] I agree to the Acceptable Use Policy

Oh no! ❌
Your application for a goum.cf Pages profile page has been denied.
You might be able to apply for a new page after fixing the below reason(s).
Reason:

A field in the application is malformed (Avatar URL is not an image)


Add txscript API to parse atomic swap contracts.

@jrick Can you provide a detailed description and use case for this change? (or let us know if this is no longer needed)

This was for ltcatomicswap (see https://github.com/decred/atomicswap) but I worked around it by using my fork as the repo source.  It was only necessary as a library function and not needed by the ltcd executable.  If you want this for consistency (it was also added to btcd) I would recommend pulling it in with whatever way you do to keep the repo updated, since the script contract was modified since this PR to specify the secret size to avoid a possible exploit.


fix: import nuxt composables from #imports

This is a DX improvement when developing - we can avoid loading the entire barrel file at #app by using the new granular imports merged in https://github.com/nuxt/nuxt/pull/23951.

Thanks a lot, @danielroe ;)


After restarting the browser, the first time an event is created, the dark theme is disabled

Then the theme is activated again, and then does not turn off. Until the browser is restarted.
Mozilla Firefox 106.0.1 (64-bit)
Stylus 1.5.26 (30 August 2022)
Google Translate Dark 1.3.1
Microsoft Windows 10.0.19045.2130

Does this issue also happen to you with other themes, or even themes on the other websites?
Could you try reinstalling the theme with Stylus to see if it helps?

Does this issue also happen to you with other themes, or even themes on the other websites? Could you try reinstalling the theme with Stylus to see if it helps?

I haven't seen this effect on other sites. I currently have the following styles set:

Dark Docs 2022.10.20
Dark Google Calendar 2.7.8
Fandom Cleanup
Fandom Remove Background Colour 1.2.0
Firefox PNG Transparency Fix 1.0
Google Translate Dark 1.3.1
Instagram Super
Messenger Dark 1.2.15
RU AdList CSS Fixes 0.20221021.1419
Telegram Käfer 1.0.1
Wikipedia Dark 3.6.0
Yandex.Disk Dark MOD 20220121.00.18

Of these, only the following are active on calendar.google.com — "Dark Google Calendar" and "Firefox PNG Transparency Fix".

Could you try reinstalling the theme with Stylus to see if it helps?

I've reinstalled your style and will be watching my computers over the next few days (I use the Mozilla browser profile that is synchronized across multiple computers).

The problem doesn't seem to recur anymore. I will close the issue. If the problem comes back, we'll get back to it.


Non-Python files are not packaged

I don't seem to be able to figure out the whole setup.cfg / MANIFEST.in
situation to get package data files to be included. The default html email
template, the csv file full of test names, and other non-python files are not
being included in the distributed package.
This breaks some functionality.

fixed in 2.0.4


Fix SDK tests: login once per class

Motivation and context
Recently we used workaround with increasing throttle rate to make our tests green.
This PR resolve root cause of the "throttle error" problem in our tests

[x] Get back original value of throttle rate
[x] Use login for SDK tests once per test class
[x] Add SDK tests for main.yml workflow
[x] Rename changedb fixture

How has this been tested?

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added a description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

/check

/check

@kirill-sizov , what is the status of the PR? Are all comments resolved?

@kirill-sizov , what is the status of the PR? Are all comments resolved?

One comment is resolved, and other comment isn't related with this PR and I have created issue about it


Get proxies from source [BUG]

whats up with this, i get very low yields because most of the sources get this error...

( * Website down? )
(* Not connecting? )
Im not sure what it could be

It would be nice if you could provide the full output of the terminal.
Do the sources that give an error open in the browser?

It would be nice if you could provide the full output of the terminal.
Do the sources that give an error open in the browser?

Havent debugged yet, but in console I get https://...com | Error

And sometimes its almost 80% of the sources

Try opening these sources in your browser.

Try opening these sources in your browser.

Locally it works but im hosting on a Linux Based server.

Theses are my gameserver's config for requests

There is a 99% chance that you just have a network problem. On my home computer and on my server (which runs https://github.com/monosans/proxy-list) all sources work.
Closing the issue.


Create graph of unique vs non-unique works viewed since Oct 2018

Here's what unique item page views look like from Q1 201819:

The two peaks are the uplift during the first lockdown and the effect of opening the museum briefly during October 2020.

Here's what works and item pages, both unique and non-unique look like from Q2 202021:

The increase in unique item views look pretty dramatic in the first graph but they're nothing compared to the increase non-unique works page views. I'd say these are due to improved search, filter functionality as well as addition of archives and manuscripts.

Link to data and graphs here:
https://wellcomecloud.sharepoint.com/sites/wcdigitalexperience/Shared Documents/Forms/AllItems.aspx?amp;id=%2Fsites%2Fwcdigitalexperience%2FShared Documents%2FAnalytics&id=%2Fsites%2Fwcdigitalexperience%2FShared Documents%2FAnalytics%2FBreadth of collection accessed&viewid=bb8c30b0-6281-45fa-bfb1-2973d13d217f


Mobile loading

@keybase/react-hackers
Adds loading screen for user bio and proofs and a component that handles transistions.
Preview 1/3 speed to demo animation

:+1:


Updated meta details for fgam and updated audit logging docs

@dsieczko need to fix these formatting issues and this should be good to go https://github.com/authzed/docs/actions/runs/6371591800/job/17293665421?pr=162#step:6:7

Hey @samkim  - I fixed the newline (my bad) but the other one is I think the linter misunderstanding the Docusaurus top of file meta page settings syntax. It complains about "Multiple top-level headings in the same document" but there is only one # in the doc


Change ansible_python_interpreter for debian8

debian8 | FAILED! => {
    "changed": false,
    "msg": "Ansible requires a minimum of Python2 version 2.6 or Python3 version 3.5. Current version: 3.4.2 (default, Sep 14 2019, 00:52:38) [GCC 4.9.2]"
}

Fixed by https://github.com/playwithansible/playwithansible-cli/commit/4a1aa29160e915770e64b93ff4c9d9c04d93da36


AWS_ENDPOINT_URL overrides the endpoint URL of aws command

With the recent release of AWS CLI (v1.29.0 and v2.13.0), the environment variable AWS_ENDPOINT_URL is now being referenced by the aws commands as well. This release has caused a bug where setting AWS_ENDPOINT_URL to the endpoint of LocalStack results in the aws commands connecting to LocalStack instead.
I believe it is necessary to change the name of the environment variable used for awslocal.
https://github.com/aws/aws-cli/blob/develop/CHANGELOG.rst#L29

@whummer
Thank you for your response.
Here's my use case:

I'm spinning up a separate localstack container in a VSCode devcontainer for development.
By default, the connection destination with awslocal is localhost:4566, so I set AWS_ENDPOINT_URL to localstack:4566 in my .zshrc file.
Inside the devcontainer, I'm also deploying to AWS using the CDK, and I need to check actual AWS resources after deployment using the AWS command. Therefore, I want the AWS command and awslocal to connect to separate endpoints.

Given this scenario, I think it's crucial to have the ability to distinguish between the endpoint for awslocal and the endpoint that the AWS command (or the AWS SDK) picks up directly. This is because while the localhost:4566 works perfectly for most local setups, in the context of the devcontainer, where I have to point it to localstack:4566 (since localstack is not technically on localhost), it creates a need for a different setup.


Hub & Spoke concepts updated, removed unsiupported statements

Updated the arcticle with up to date information regarding Express Route connectivity and traffic segmentation. Removed unsupported parts from 'Identity Considerations' section.

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

#sign-off

Hi @shortpatti - You signed off, but also requested revisions. Would you like the contributor or the PR review team to make the revisions before the PR is merged? Thanks.

The contributor approved them.

@shortpatti The revisions have not been incorporated into the PR, but we'll merge the PR as-is with your approval.

We'll incorporate the revisions and then merge.

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


Deduplicate yarn.lock

Checklist:

[ ] Documentation
[ ] Tests
[ ] Ready to be merged

Deploy preview for govuk-react processing.
Building with commit 7921b9fc0310e79c0a9291ab94b5625dd1145989
https://app.netlify.com/sites/govuk-react/deploys/5d1dd409f95ed00008a6a454

Codecov Report

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

@@           Coverage Diff           @@
##           master     #695   +/-   ##
=======================================
  Coverage   99.69%   99.69%
=======================================
  Files         121      121
  Lines         659      659
  Branches       78       78
=======================================
  Hits          657      657
  Misses          2        2

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 292209d...5211a16. Read the comment docs.


Unable to import plugin from JS frontend

Trying to get the plugin going but the showstopper is the import.
I use -
import Database from 'tauri-plugin-sql-api' as per the readme but of course this fails with
TypeError: Module specifier, 'tauri-plugin-sql-api' does not start with "/", "./", or "../". Referenced from tauri://localhost/js/app.js
I sort of expected this because imports of the Tauri api fail in the same way but there is an alternative method which works well -
eg:     var dialog = window.__TAURI__.dialog;
//  import { confirm } from '@tauri-apps/api/dialog';
So is there a similar alternative available for the plugin?

You could download this file https://github.com/tauri-apps/tauri-plugin-sql/blob/dev/webview-dist/index.min.js and use it locally.

Thanks for that but still at sea as to how to use it - tried window.TAURI_IPC.t but no good.

I think you need to import the file with an import statement like this
import Database from './sql.min.js'; //Or whatever you named the file.

const db = new Database("sqlite:mydb.db");

Alternatively you could also use this file instead https://github.com/tauri-apps/tauri-plugin-sql/blob/dev/webview-dist/index.mjs and replace the import at the top with const invoke = window.__TAURI__.invoke;

OK thanks - finally got the import to work and the db object is created but not sure where the db file is - can't find it anywhere - will have a go at using sqlite on the client side with sql.js I think.

can't find it anywhere

it's in the path you can get via the appDir() function. For example on Windows this resolves to AppData/Roaming/bundle-identifier/mydb.db (see the configDir doc for linux and macos paths)

Yup that's what I thought, my appDir shows as -
"/Users/USER/Library/Application Support/uk.org.wanderinghippo.winman.dev/" however the uk.org.wanderinghippo.winman.dev folder doesn't exist which is strange. If I manually create it the db file will still not appear so I think it is time to retrace my steps back to create-tauri-app ....

The database won't be created until it's actually loaded, which also means that i made bad decisions in my example code above, so instead of new Database(path) you'd use Database.load(path) - sorry about that if this was the issue.

Mmmm - I think your initial angle was OK - my results are -
`    import Database from './sql.mjs';  //  (using var invoke = window.TAURI.invoke; at top of file) -
//  import Database from './sql.min.js'  // also works

//	    const db = new Database.load("sqlite:hippo.db");  // TypeError: function is not a constructor (evaluating 'new Database.load("sqlite:hippo.db")')
//	    const db = Database.load("sqlite:hippo.db");  // Unhandled Promise Rejection: plugin sql not found
//	    const db = Database("sqlite:hippo.db");  // TypeError: Cannot call a class constructor without |new|
const db = new Database("sqlite:hippo.db");  // works OK
console.log('DB', db);
const getto = Database.get("sqlite:hippo.db");  // works OK

console.log('GETTO', getto);
`

As far as the import goes I think it works OK now but the new rabbit hole for me is the fact that the app Dir folder doesn't exist even though the path reports it OK. I have tried with default tauri-app and it also does not produce an appDir folder as expected (should be com.tauri.dev folder as set in config identifier). Strange that if the folder doesn't exist that the db creation doesn't error somehow. Maybe it is up to the dev to manually create the appDir folder although I expected that the Tauri app would have just done that particularly as the path reports it as such.

OK - thanks very much for your help, got it working now - I had thought the Rust example and the Webview example on the readme were either(I did the webview) rather than both required. The create dir worked fine from the JS and the Rust in the main.js is good so now hippo.db exists where it should.


Expose HyperspaceSuite.withTempDir() to be used in tests involving temporary directories.

I see many tests where we need to be careful about deleting a directory used after a test is run.
This PR exposes HyperspaceSuite.withTempDir() where you can use it like the following:
withTempDir { dir =>
  foo(dir)
}

This is a copy of SparkFunSuite.withTempDir, which is available in Spark 3.0. When we move to Spark 3.0, we can just remove this function and any existing code should just work since HyperspaceSuite extends SparkFunSuite.

@sezruby @apoorvedave1 @pirz Let's try to utilize this where applicable.


Wallet tables config.toml not recreated if config is deleted after adding key

All other elements in config.toml are recreated and set to defaults if deleted except for wallet tables.
Low priority, causes user to be unable to change name of wallet from "Unknown"

Fixed in https://github.com/xch-dev/sage/pull/157


fix: remove the unused named addresses, fix a deploy test

Description
Brief description of the issue or feature implemented in this PR.
Link to Jira Issue or relevant doc
Dev
Any explanation for the devs that will review your implementation/code.
Qa
Any guidance or important information for the team that will be testing your solution.

Note: you can add any additional information you think is important for giving context to your PR.

Checklist and Markdown

[ ] Remember you could add any type of formatting to enhance your PR.
[ ] Like this checklist
[ ] And with this markdown format

we need to redo this taking into account the new deploy scripts


feat: delete records in full syncs

We can do this by diffing temp table and real table for full syncs only.
This PR also removes the S3 destination

Ty -
Do we want to not do this for Apollo? It might cause arbitrary records to be soft deleted if users are hitting the 10K record limit?

Ty -
Do we want to not do this for Apollo? It might cause arbitrary records to be soft deleted if users are hitting the 10K record limit?

Good point. I can skip this step for apollo.


Integrate service mesh

For security (e.g., mTLS) and observability reasons.
We'll probably just use istio as GKE supports it out of the box.
Note: Knative comes with service mesh built-in (see https://github.com/relaycorp/relaynet-internet-gateway/issues/761).

No longer using Kubernetes! 🎉


feat: support Iam_service in Gax

Supporting IAM service in Gax-nodejs.  Nodejs-kms and nodejs-pubsub are the two APIs that require IAM Client to be part of the methods [getIamPolicy, setIamPolicy, testIamPermission].
Monolith generator has a reroute_to_grpc_interface setting in GAPIC yaml to include extra services when generating client libraries. While this is not supported in micro-generator today. And IAM service is the only one referenced in that way but it does not have a generated client library [nodejs-IAM]  for easy use. This is a pain point for every micro-generator and it makes post-processing script (synth.py in Typescript Microgenerator) really messy.
related issue: https://github.com/googleapis/gapic-generator-typescript/issues/315

Current problem:

System-test runs successfully at local, but fails here.
2 unit tests for longrunnning fail if IamService.ts unit test is added.

Questions: can we expose IamProtos from '../../protos/iam_service'? since from microgenerator, we need the type definition file for request/response type of methods (like protos.google.iam.v1.getIamPolicyRequest) @alexander-fenster Thank you

runs successfully on local but fails here

Easy! rm -rf node_modules build package-lock.json && npm install :) It will likely start failing locally the same way then.
As for exposing - yes, sure, we can expose whatever we need there.

@alexander-fenster yes I removed all dependencies and build files, but still it passes the tests :(

TO DO: once KMS is migrated using --iam-service option to include IAM methods, add one kms system-test to test this feature.


Feat: add multiple pdp and plp with seo settings

What's the purpose of this pull request?
We should enable the possibility of creating multiples PDPs and PLPs using the CMS, and map the pages using SEO settings values. Would be good to use the CMS filter by the slug instead of the content type in the getStaticProps methods. So that we can customize each PLP or PDP according to its context (e.g. Hero Image per brand in PLP).

[x] Enables multiples PDPs and PLPs.
[ ] Map by slug in getStaticProps
[ ] Enable redirects CMS preview by slug (?)

How it works?

How to test it?

Starters Deploy Preview

References

closed due to inactivity and there are updates regarding this subject yet.


Update ApolloMetaServiceConfig.java

使用DefaultHttpFirewall替换spring security默认的StrictHttpFirewall，用于解决客户端配置meta url时加上/，抛The request was rejected because the URL was not normalized.异常的问题

Codecov Report

Merging #1685 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #1685      +/-   ##
============================================
+ Coverage     48.71%   48.72%   +<.01%
- Complexity     1908     1909       +1
============================================
  Files           392      392
  Lines         11550    11551       +1
  Branches       1210     1210
============================================
+ Hits           5627     5628       +1
  Misses         5480     5480
  Partials        443      443

Impacted Files
Coverage Δ
Complexity Δ

...rk/apollo/metaservice/ApolloMetaServiceConfig.java
100% <100%> (ø)
2 <1> (+1)
:arrow_up:

Continue to review full report at Codecov.

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

Coverage increased (+0.004%) to 52.558% when pulling d5c11ca6c0af1004714bcac448e48b43d6397322 on klboke:master into 0ac808d48cbca831c8f9b43cd94379cf06567027 on ctripcorp:master.


Rich text editor | Two mentions without a space renders strangely when setMarkdown()

🐛 Bug Report

When two mentions are added via a setMarkdown() dynamically, they render as IDs instead of two mentions without a space. More info below.
Relevant Bug link in SLE Comments feature,
Bug 2602536: Usernames without a space in between do not render properly when editing a comment.
💻 Repro or Code Sample

Below is the workflow to reproduce the bug in the nimble-rich-text-editor:
When a user sets the <user:1><user:2> markdown string into the editor via setMarkdown() method, it is expected to render as two user mentions in the editor. However, during the first time when setMarkdown() is called the mention configs in the markdown parser are empty so it renders as two links. Since the example autolink is not an HTTP/HTTPS link, they render within the anchor element without href as per the design for mention.
Now, the configuration and corresponding mapping elements are loaded into the DOM, so as per the flow, we perform getMarkdown() +  setMarkdown() to convert the rendered link back to mention node. Here, in Tiptap the link with the same href values without a whitespace in between renders as a single link instead of two links. So created an issue in Tiptap: https://github.com/ueberdosis/tiptap/issues/4686
Due to the above issue, the getMarkdown() returns markdown string as <user:1user:2> so the setMarkdown() converts it to something like below

🤔 Expected Behavior

For the above example, it should be like below considering the below configuration,
pattern: ^user:(.*)
For mention 1 -> mention-href: user:1, mention-label: name1
For mention 2 -> mention-href: user:2, mention-label: name2

😯 Current Behavior

💁 Possible Solution

Since the root cause of this bug is due to an issue in Tiptap where the same href value is rendered as a single anchor element instead of two links, we implemented a workaround to render it as two separate anchor elements.
To render two autolinks without whitespace as separate links in the Tiptap editor by having a unique class attribute value (i.e. href value) in the markdown parser and tiptap editor. This unique attribute value renders them as a separate link so that the bug is resolved.
We have commented this issue link on the code where we added the class attribute and can be removed once the linked Tiptap issue is resolved.
🔦 Context

It is affected when editing a comment in SLE. For more details, see the bug: https://dev.azure.com/ni/DevCentral/_workitems/edit/2602536
🌍 Your Environment

OS & Device: Windows on PC
Browser Google Chrome
Version [e.g. 1.8.0]

Blocked on https://github.com/ueberdosis/tiptap/issues/4686


chore: narrow event trigger for ci testing

No need to run all tests if there is only documentation or lint changes.

So, the previous PR is clearly not working - most lint jobs should have skipped here.

In conclusion: No more fancy stuff. I'm done. Until individual jobs supports triggers or workflows have better grouping I'm not going to bother anymore.


Add Query-specific Hook function and RPC

A new rcp call the query-only function inside of a hook.
I think it would be a third main function (in addition to hook(), cbak()) that would not be able to change the Ledger State by state_set, emit, etc. or read transaction information such as oxtn_field.
This is similar to account_info, etc., only information is obtained without signing the transaction or incurring transaction costs.
This feature allows users to retrieve readable data without having to decode the HookState themselves or pay transaction costs to retrieve the information.

I believe the problem is that the call would require opening up the VM and this should come with a cost to avoid DDOS.

It would be similar to the existing PathFind method.
Public nodes can make this RPC unavailable, and clusters may have dedicated nodes for this RPC.


feat(lexers): add various SSH files

Are you sure you don't want the quotes be part of the string?

I have no personal preference. But I should note that I'm no longer using pygments, and have no immediate plans to work on this further, so I suggest someone else completes it (or closes without merging, but that would be a shame as this is fairly close I think). My branch should be accepting collaborator pushes.

Ok, thanks. Out of curiosity: Which solution are you using now?

After a short pygments try I was using https://github.com/alecthomas/chroma/ for a bit, but I've moved on to https://github.com/sharkdp/bat as it's only console syntax highlighting I'm after, and bat seems to serve me best I've found this far.


feat: coinflip command

I mean... it's in the title.
closes #522

adding to Kyra's review as discussed in Discord: allow cashless flips

cashless flips will probably be added at a later:tm: date, @kyranet pls re-review

oh fruck off


new versions not available with cargo

os: OSX
lsd --version: 1.0.0
echo $TERM: xterm-256color
echo $LS_COLORS: di=34:ln=35:so=32:pi=33:ex=31:bd=36;01:cd=33;01:su=31;40;07:sg=36;40;07:tw=32;40;07:ow=33;40;07:

Expected behaviour
Installing lsd with cargo should give me tha latest version.
Actual behaviour
Cargo installs version 1.0.0. as this is the latest version listed here https://crates.io/crates/lsd

hi @kakulukia, thanks for the report, this is known but not fixed for this issue, https://github.com/lsd-rs/lsd/issues/1014, I am working on a v1.1.2 to fix it and I will post the newer version to crate, sorry for the bothering

v1.1.2 is now available on crate


feat: svg path merge transformer

Description
All core icons with multiple paths in the svg will be modified to have one path.

Closing this, since done in https://github.com/momentum-design/momentum-design/pull/532 more efficiently.
Keeping it in closed state for reference, in case we need to go back to this solution.


Add support for io.netty:netty-transport-classes-epoll:4.1.99.Final

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Yes, refer to #164 .

Describe the solution you'd like
A clear and concise description of what you want to happen.

Add support for io.netty:netty-transport-classes-epoll:4.1.99.Final.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Null.

Additional context
Add any other context or screenshots about the feature request here.

I completed the nativeTest verification of io.etcd:jetcd-core:0.7.5 in GraalVM CE at https://github.com/apache/shardingsphere/pull/29755 , which is missing the following JSON in reflect-config.json entry.

[
{
  "condition":{"typeReachable":"io.netty.channel.epoll.EpollChannelOption"},
  "name":"io.netty.channel.epoll.EpollChannelOption",
  "fields":[{"name":"TCP_USER_TIMEOUT"}]
}
]

I'm working on this issue.


Review resources for consistency

role name/user name usage is not consistent

https://github.com/aspnet/Identity/pull/327


added an extend

Instead of extend() within the already-named updateWorkflowFields method, could you instead call $action->invokeWithExtensions('updateWorkflowFields', $fields); back from the call in WorkflowInstance::getWorkflowFields() instead of the existing $action->updateWorkflowFields($fields); call?

Updated now and works fine.


chore: update footer links

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[ ] Feature
[ ] Refactoring
[x] Chore

What's new?

[x] PR closes #2954
[x] Partnerships gone, hello ambassador program

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[x] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address: Payout

Community participation

[ ] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

pay 50 usd

😍 Perfect, I’ve sent the payout
💵 $50 @ 127.4 USD/KSM ~ 0.392 $KSM
🧗 EqdyzrzVmeHwMdMwvPeCMnNdbuQDbD3YrjY93xq9Ln3jUGW
🔗 0x34600f31ca962d72f18ed7af8d7a97fc0095c27b18591f9c3f39e95080ccc37e
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Polars: add date and time components

Close #1755

Rebased on top of the ExprDomain and SeriesDomain refactors, and comments addressed in the rebase, so new changes aren't in a separate commit.


Missing kong image tag with 0.11.0rc1

missing 0.11.0rc1 version in docker hub

We do not publish release candidates on Docker Hub. Feel free to provision your own image as soon as the distribution packages will be released.


Allow new-lines in Method descriptions

The descriptions of Methods (ex. POST, GET, etc.) can have new-lines on data-entry, but the new-lines are ignored in this Documentaiton module.
As it stands right now, new-lines are, effectively, just spaces.  This can make the description of a given method more more difficult to read when there is more than a few sentences.

See the screen-shot for an example of the desired effect: I have included the CSS ( white-space: pre ) on the related element.

This repository has been closed and moved to laminas-api-tools/api-tools-documentation; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-documentation/issues/10.


Reveal - on open focus on first input

Hi guys,
Struggling to focus on an input field inside a reveal when the reveal is opened.  Currently the focus is just being ignored, though I do get the word 'focus' logged on the console which is coming from your afterAnimationFocus() function.
Simple example as follows:
Open Reveal

  <form action="" method="post" name="login-form" id="login-form">

      E
      <input name="email" id="email" type="email" class="input-group-field" placeholder="Email address" required/>

      P
      <input name="pwd" id="pwd" type="password" class="input-group-field" placeholder="Password" required/>

      Login

  </form>
  <button class="close-button" data-close aria-label="Close modal" type="button">
    ×
  </button>

JS:
$(document).ready(function() {
  $('#reveal-modal').on('open.zf.reveal', function() {
    console.log('reveal open');
    $('#reveal-modal').find("input:visible").first().focus();
  });
});

Using Foundation 6.2.3.  Would really appreciate any advice on this.
Cheers,
Will

It's the animation. Your focus is firing before the model is open, so the input isn't visible yet. If you remove the data-animation-* attributes, it just works. Or you could set a timeout longer than the animation duration so the focus fires once the input is actually visible. Hope that helps.
I'm gonna close this, as it's not a bug. Best place for questions like this is the Forum.


feature: add operation summary sentence casing rule

Added a configurable rule to check operation summaries for sentence casing

You re-requested the review, but I would still like to see something in the page about what to do when there's a correct title that doesn't match the rule, so same feedback as before since I still don't see that here.

Sorry @lornajane, I missed that note. Added an ignore section.


Automate running the pipeline

Creating this draft PR to get help on an error creating the plots.
When complete this PR will allow a user to run sbatch run-pipeline.sh to run the entire pipeline.
This includes the two R Scripts in this repo as well as running BGNN_Snakemake.
The code is still in a WIP state, but feedback is still welcomed.
Fixes #3
Fixes #4

When running selectionCriteriaSegmentedImages.R I receive the following error:
Error in heatmap(stats.sp.trim, labRow = rownames(stats.sp.trim), labCol = colnames(stats.sp.trim),  :
  'x' must have at least 2 rows and 2 columns
Execution halted

https://github.com/hdr-bgnn/minnowTraits/blob/20a4ae13a4078971bbcd45b792424420f3bc7920/Scripts/selectionCriteriaSegmentedImages.R#L210-L213

After debugging I noticed the presence.absence.matrix.csv file created was much smaller than the one in the repo:Files/presence.absence.matrix.csv.
My generated file:
$ wc -l results/presence.absence.matrix.csv
448 results/presence.absence.matrix.csv

The one already in the repo:
$ wc -l Files/presence.absence.matrix.csv
6298 Files/presence.absence.matrix.csv

I think my problem is I am running BGNN_Snakemake with the wrong input CSV and not generating enough `Morphology/Presence/*.json" files.
@megbalk or @thibaulttabarin
Should I run  snakemake with "minnow.filtered.from.imagequalitymetadata_25Jul2022.csv" or "burress.minnow.sp.filtered.from.imagequalitymetadata_25Jul2022.csv" or perhaps another file?

minnow.filtered.from.imagequalitymetadata_25Jul2022.csv will a fair amount of time (I think it took me 5 h with 28 cores)
But I am almost done with it using the most updated version of the different parts
it should be finished in the afternoon.

have you try to use /fs/ess/PAS2136/BGNN/Test_lab

have you try to use /fs/ess/PAS2136/BGNN/Test_lab

@thibaulttabarin It looks like there are only 10 json Morphology/Presence files within that directory.
$ ls /fs/ess/PAS2136/BGNN/Test_lab/Morphology/Presence/*  | wc -l
10

Is this all that's needed for the ending scripts?

I figured out the problem I was having with selectionCriteriaSegmentedImages.R. The bug was due to my changes to remove the hard coded paths. The directory name was making it into the file.name field and this prevented looking up metadata. The following line fixed the problem:
https://github.com/hdr-bgnn/Minnow_Traits/blob/8bdee8fa0a111259259a36790d6de4e7840f9b1d/Scripts/selectionCriteriaSegmentedImages.R#L36-L38

I'm going to close this PR and create a simpler version of these changes once issue #4 is resolved.


Add new adjustment history charts

For the time being just adds a new chart to the existing menu of charts provided and sticks them at the bottom of the all_charts_write_html_file() output
Still to address:

Arrangement of charts in all charts output
New chart for distribution of gamma levels for each col (to complete link between m/u probabilities and influence factor)
Replace adjustment/influence factor with Bayes factor, K in charts and documentation (worthy of a separate PR)

In general this looks good but I think there are some edge cases where the charts don't come out quite right e.g. where there are low numbers of iterations.  Not sure the best solution.  Here's an example:

where you get fractional iterations on the axis and the bars are quite thing.
I was fiddling with the spec in the vega editor
This is by no means complete but i tried to replicate grouped bars
https://gist.github.com/RobinL/55df885a70eca16201c2aabec8de7696
I wonder if grouped bars would be 'good enough' if we hid the x axis?  I'm assuming you didn't use them because it looks a bit rubbish?
Sorry - i've run out of time today but wanted to write this comment, mainly so i remember where i got to with this

Reverting to line chart for the history means no need for jitter and other hacks, so the iteration axis can be set to ordinal and everything's fine.

Just to clarify the changes:

Added a line to _convert_params_dict_to_normalised_adjustment_data to add a column level_proportion to the output
New gamma_distribution_chart to mirror other charts and show that proportion (with "non-null" caveat)
Changed the colour scheme to make m (green) and u (red) probability distributions more intuitive
Tidied up differences between two datasets used in the charts (e.g. "column" vs "col_name", "0" vs "level_0")
Rearranged charts in all_charts_write_html_file

Looks good - happy with this now.  I spent quite a lot of time messing about with colour schemes without really coming up with a better solution.  I wanted to find a sort of 'red orange green' colour scheme, but there doesn't seem to be an easy way of creating a custom domain and range that works in the same way as the scale.
so e.g.:
range: ["red", "orange", "green"]
will map to

red and orange in the case of two levels and
red orange green in the case of three

which probably isn't what we want.
Only thing I wonder is whether viridis may be easer to see than redyellowgreen (although I admit, it's a bit less intuitive in terms of correspondence between colours and levels)


Correct weekly -> weeklong

I think the meaning was supposed to be that the trip lasts a week, not that we do one trip every week. :)
Very cool project by the way, found out about it last week and have been loving it!

@rtsisyk you mean me?
Sorry for the confusion, I did read the comment in the "Checks" tab, but don't understand what's exactly expected of me... Am I the one signing off? Or did you? I mean, sure I can use --sign-off but what difference does it make whether a total stranger on the interwebs signs off on their own commit? :D

@black-puppydog contributors (including ourselves) sign their commits with the real contributor's name and email.

Okay, done. I rebased and dropped your merge commit in the process, hope that was okay.
I also changed the extra three translations that were added in the meantime.


extra-fsharp-features

now stores the output of corecompile and thus gives the sourcefiles and references of an F# project

@daveaglick for some context, @dukedagmor is my intern and he is working on adding fsharp support in https://github.com/stryker-mutator/stryker-net
As part of this he's been working on making buildalyzer work for sharp projects. Please let us know if there are any changes necessary or if there's anything we can do to make this easier to review!

This is awesome. I don't know the first thing about F#, but more than happy to help Buildalyzer work with it. I'm hoping to carve out some time this week to review and merge PRs, so hopefully we can get this in and released relatively soon.
Thanks!

@daveaglick would it be possible to add the hacktoberfest tag and merge before the 31st of October?
I would like to know if I need to open more PR's on other hacktoberfest repo's 😉

Absolutely! Apologies for the delay - I'll YOLO merge it now and take a look at a release.