CSHARP-719: use K4os.Compression.LZ4 instead of lz4net to support LZ4…

Use K4os.Compression.LZ4 instead of lz4net to support LZ4 compression for all netstandard targets.
Original issue: https://datastax-oss.atlassian.net/browse/CSHARP-719

As mentioned on the JIRA ticket, compatibility between these two libraries is not guaranteed so we don't want to replace the implementation on a minor release.
How urgent is this for your use case? If you can't wait for the next major (which will be under development for several months) then we could add this new dependency and implementation just for netstandard until the next major where we drop lz4net completely.

Hi, @joao-r-reis.

As mentioned on the JIRA ticket, compatibility between these two libraries is not guaranteed so we don't want to replace the implementation on a minor release.

How urgent is this for your use case? If you can't wait for the next major (which will be under development for several months) then we could add this new dependency and implementation just for netstandard until the next major where we drop lz4net completely.

Actually, I'd like to have LZ4 support for netstandard targets.
Now I understand that lz4net and K4os.Compression.LZ4 may have incompatibilities. Therefore in this PR I've returned lz4net dependency for .NET Framework target and use K4os.Compression.LZ4 only for netstandard2.0 target.

until the next major where we drop lz4net completely

@joao-r-reis, one more question: is Snappy preferred compression algorithm for Cassandra for the future?

@joao-r-reis, one more question: is Snappy preferred compression algorithm for Cassandra for the future?

Sorry I meant just the legacy lz4net dependency, not LZ4 compression altogether, i.e., using K4os.Compression.LZ4  instead of lz4net.
LZ4 is generally preferred over Snappy. This is mentioned on the Apache Cassandra docs

Snappy is kept for backwards compatibility and LZ4 will typically be preferable.

LZ4 is generally preferred over Snappy.

Yes, therefore I was wondered :)  Thanks!
All review suggestions are fixed, all checks have passed.
Please, resolve conversations if all is fine now?

Lgtm, I will post an update here when we figure out which release will have this.

I posted an update on the JIRA ticket


Kubernetes deployment

Create yaml files to deploy TEStribute to a kubernetes cluster.

Bash-templated version at #54.

Add permanent dev and CI deployments on https://c03.k8s-popup.csc.fi:8443


should it not be called ZIO?

shouldn't the main class not be called ZIO? :smile:
Then IO[a] could be an alias to ZIO[Throwable, a]

Right now that alias is called Task https://github.com/scalaz/scalaz-zio/blob/e20ba75df43a169f4830b27675114c0c80db865e/core/shared/src/main/scala/scalaz/zio/package.scala#L21

Or better yet, type IlluminatIO a = IO Throwable a

I'm tempted to add:
type LosersWhoAreInLoveWithThrowable[A] = IO[Throwable, A]

😈

type MercenariesWhoSellTheirHaskellSoulForScalaMoney[a] = IO[Throwable, a]

Well, this derailed quickly. How about we settle on
type SpaghettIO a = IO Throwable a

@emilypi

@jdegoes GET DISTURBED BOIIIII
Square brackets around type parameters violate my code of conduct


Confusions to address on chrisproject.org front page

Home Page observations:
The image on the home page (http://chrisproject.org/assets/images/diagram_chris-arch.png) is hard to read for the vertical text on the left-hand side.
On the homepage, in the “The ChRIS Store” box, the sentence “We link to a recent prototype here.” Is confusing. Is the here expected to be a link or is the link to the store a prototype? Is this sentence even needed?

see https://github.com/FNNDSC/website/issues/20#issuecomment-738319108

Hey @mairin, @jennydaman, can you please assign this issue to me?


OpenSSL ByteBuffer BIO

Motivation:
Currently Netty utilizes BIO_new_bio_pair so we can control all FD lifetime and event notification but delegates to OpenSSL for encryption/decryption. The current implementation sets up a pair of BIO buffers to read/write encrypted/plaintext data. This approach requires copying of data from Java ByteBuffers to native memory BIO buffers, and also requires both BIO buffers to be sufficiently large to hold application data. If direct ByteBuffers are used we can avoid coyping to/from the intermediate BIO buffer and just read/write directly from the direct ByteBuffer memory. We still need an internal buffer because OpenSSL may generate write data as a result of read calls (e.g. handshake, alerts, renegotiation, etc..), but this buffer doesn't have to be be large enough to hold application data.
Modifications:

Take advantage of the new ByteBuffer based BIO provided by netty-tcnative instead of using BIO_read and BIO_write.

Result:
Less copying and lower memory footprint requirement per TLS connection.

only the last commit is part of this PR
this PR depends upon https://github.com/netty/netty-tcnative/pull/216

4.1 (d06990f) 4.0 (00cd6d2)

LGTM... Thanks!


Can't pop New Years (observed) by name if it falls in previous year

Version: holidays 0.12
Platform: Python 3.10.0 for Windows
Example:
import holidays

class TestClass(holidays.UnitedStates):
    def _populate(self, year):
        holidays.UnitedStates._populate(self, year)

        self.pop_named('New Year')

test_holidays = TestClass(years=2022, state='CA')

for date, name in sorted(test_holidays.items()):
    print(date, name)

Expected result: A list of dates and holidays
Actual result:
Traceback (most recent call last):
  File "test.py", line 11, in <module>
    test_holidays = TestClass(years=2022, state='CA')
  File ".virtualenv\lib\site-packages\holidays\countries\united_states.py", line 104, in __init__
    HolidayBase.__init__(self, **kwargs)
  File ".virtualenv\lib\site-packages\holidays\holiday_base.py", line 182, in __init__
    self._populate(year)
  File "test.py", line 8, in _populate
    self.pop_named('New Year')
  File ".virtualenv\lib\site-packages\holidays\holiday_base.py", line 363, in pop_named
    self.pop(key)
  File ".virtualenv\lib\site-packages\holidays\holiday_base.py", line 351, in pop
    return dict.pop(self, self.__keytransform__(key))
KeyError: datetime.date(2021, 12, 31)

@TeejMonster thanks for your report!
@dr-prodigy Thankfully this code does not generate any errors when run against the beta branch. I think my PRs on ensuring that only holidays for the year requested fixes it.
Maybe it's time for a new release?

@TeejMonster thx for your report!
@mborsetti it sounds like a good plan! :) I confirm this is already fixed in beta: I'm applying the last fixes/updates, then time for a new release! 👍


Add example for scrollRef

Issue Number
As asked in https://github.com/namespace-ee/react-calendar-timeline/issues/372#issuecomment-417103151 I provided an example.
Overview of PR
Add sandbox which shows how to use scrollRef to programmatically scroll.

THIS IS AMAZING! Thank you!


🐛 Bug Report: kubernetes plugin doesn't work for EKS on a different AWS account

📜 Description
I have backstage setup locally (for debugging) and I'm authenticated to Account A.
I want to get data about resources in EKS in account B.
This is my app_config:
kubernetes:   serviceLocatorMethod:     type: 'singleTenant'   clusterLocatorMethods:     - type: 'config'       clusters:         - url: 'https://<eks-api-endpoint-in-account-b>'           name: 'eks-clsuter-name-in-account-b'           authProvider: 'aws'           caData: "CA-from-eks-in-account-b"           authMetadata:             kubernetes.io/x-k8s-aws-id: "eks-clsuter-name-in-account-b"             kubernetes.io/aws-assume-role: "arn of IAM role that has access to eks cluster in account B"
Unfortunately, I get error: UNAUTHORIZED_ERROR, status code: 401
I checked the source code and noticed that you use https://github.com/kubernetes-sigs/aws-iam-authenticator so I wanted to reproduce the issue.
To debug, I ran  aws-iam-authenticator token -i <eks-cluster-in-account-b> -r <iam-role-arn-inaccount-b>
and copied the token and then made the same request the plugin does
curl --location 'https://<eks-api-endpoint-in-account-b>/api/v1/namespaces/<namespace-in-eks-in-account-b>/pods' \ --header 'Authorization: Bearer <generated token>' and got a 200 response with the correct data.
So as far as I understand, the problem is not with my local setup
👍 Expected behavior
Display data about the entity in the kuberentes tab
👎 Actual Behavior with Screenshots
error: UNAUTHORIZED_ERROR, status code: 401

👟 Reproduction steps
Try to connect to a eks cluster in account B (different than your current account) with a IAM role from account B
📃 Provide the context for the Bug.
Also, I think there's a typo in the docs.
https://backstage.io/docs/features/kubernetes/authentication#aws
There's no key called roleName in mainAccount (only in accounts)
🖥 Your Environment
`OS:   Darwin 22.6.0 - darwin/arm64
node: v18.19.0
yarn: 1.22.21
cli:  0.25.1 (installed)
backstage:  1.22.0
Dependencies:
@backstage/app-defaults                                          1.4.7
@backstage/backend-app-api                                       0.5.10
@backstage/backend-common                                        0.19.9, 0.20.1
@backstage/backend-dev-utils                                     0.1.3
@backstage/backend-openapi-utils                                 0.1.2
@backstage/backend-plugin-api                                    0.6.9
@backstage/backend-tasks                                         0.5.14
@backstage/catalog-client                                        1.5.2
@backstage/catalog-model                                         1.4.3
@backstage/cli-common                                            0.1.13
@backstage/cli-node                                              0.2.2
@backstage/cli                                                   0.25.1
@backstage/config-loader                                         1.6.1
@backstage/config                                                1.1.1
@backstage/core-app-api                                          1.11.3
@backstage/core-compat-api                                       0.1.1
@backstage/core-components                                       0.13.10
@backstage/core-plugin-api                                       1.8.2
@backstage/e2e-test-utils                                        0.1.0
@backstage/errors                                                1.2.3
@backstage/eslint-plugin                                         0.1.4
@backstage/frontend-plugin-api                                   0.5.0
@backstage/integration-aws-node                                  0.1.8
@backstage/integration-react                                     1.1.23
@backstage/integration                                           1.8.0
@backstage/plugin-api-docs                                       0.10.3
@backstage/plugin-app-backend                                    0.3.57
@backstage/plugin-app-node                                       0.1.9
@backstage/plugin-auth-backend-module-atlassian-provider         0.1.1
@backstage/plugin-auth-backend-module-gcp-iap-provider           0.2.3
@backstage/plugin-auth-backend-module-github-provider            0.1.6
@backstage/plugin-auth-backend-module-gitlab-provider            0.1.6
@backstage/plugin-auth-backend-module-google-provider            0.1.6
@backstage/plugin-auth-backend-module-oauth2-provider            0.1.6
@backstage/plugin-auth-backend-module-oauth2-proxy-provider      0.1.1
@backstage/plugin-auth-backend-module-okta-provider              0.0.2
@backstage/plugin-auth-backend                                   0.20.3
@backstage/plugin-auth-node                                      0.4.3
@backstage/plugin-catalog-backend-module-aws                     0.3.3
@backstage/plugin-catalog-backend-module-gitlab                  0.3.6
@backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.1.6
@backstage/plugin-catalog-backend                                1.16.1
@backstage/plugin-catalog-common                                 1.0.20
@backstage/plugin-catalog-graph                                  0.3.3
@backstage/plugin-catalog-import                                 0.10.5
@backstage/plugin-catalog-node                                   1.6.1
@backstage/plugin-catalog-react                                  1.9.3
@backstage/plugin-catalog                                        1.16.1
@backstage/plugin-events-node                                    0.2.18
@backstage/plugin-github-actions                                 0.6.10
@backstage/plugin-kubernetes-backend                             0.14.1
@backstage/plugin-kubernetes-common                              0.7.3
@backstage/plugin-kubernetes-node                                0.1.3
@backstage/plugin-kubernetes-react                               0.2.1
@backstage/plugin-kubernetes                                     0.11.4
@backstage/plugin-org                                            0.6.19
@backstage/plugin-permission-common                              0.7.12
@backstage/plugin-permission-node                                0.7.20
@backstage/plugin-permission-react                               0.4.19
@backstage/plugin-proxy-backend                                  0.4.7
@backstage/plugin-scaffolder-backend-module-azure                0.1.1
@backstage/plugin-scaffolder-backend-module-bitbucket            0.1.1
@backstage/plugin-scaffolder-backend-module-gerrit               0.1.1
@backstage/plugin-scaffolder-backend-module-github               0.1.1
@backstage/plugin-scaffolder-backend-module-gitlab               0.2.12
@backstage/plugin-scaffolder-backend                             1.20.0
@backstage/plugin-scaffolder-common                              1.4.5
@backstage/plugin-scaffolder-node                                0.2.10
@backstage/plugin-scaffolder-react                               1.7.1
@backstage/plugin-scaffolder                                     1.17.1
@backstage/plugin-search-backend-module-catalog                  0.1.13
@backstage/plugin-search-backend-module-pg                       0.5.18
@backstage/plugin-search-backend-module-techdocs                 0.1.13
@backstage/plugin-search-backend-node                            1.2.13
@backstage/plugin-search-backend                                 1.4.9
@backstage/plugin-search-common                                  1.2.10
@backstage/plugin-search-react                                   1.7.5
@backstage/plugin-search                                         1.4.5
@backstage/plugin-tech-radar                                     0.6.12
@backstage/plugin-techdocs-backend                               1.9.2
@backstage/plugin-techdocs-module-addons-contrib                 1.1.4
@backstage/plugin-techdocs-node                                  1.11.1
@backstage/plugin-techdocs-react                                 1.1.15
@backstage/plugin-techdocs                                       1.9.3
@backstage/plugin-user-settings                                  0.8.0
@backstage/release-manifests                                     0.0.11
@backstage/test-utils                                            1.4.7
@backstage/theme                                                 0.5.0
@backstage/types                                                 1.1.1
@backstage/version-bridge                                        1.0.7`
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

@aberenshtein Is the IAM role running backstage allowed to assume the role on account B?

yes, it's the same IAM role I use locally

I had the same issue, after trying multiple things it got resolved but I am not sure which one did it...

I updated the packages (npx backstage-cli versions:bump)
I tried defining clusters through catalog instead of config:

kubernetes:
  serviceLocatorMethod:
    type: 'singleTenant'
  clusterLocatorMethods:
    - type: 'catalog'

&
apiVersion: backstage.io/v1alpha1
kind: Resource
metadata:
  name: xxx
  annotations:
    kubernetes.io/api-server: 'https://xxx.xxx.xxx.eks.amazonaws.com'
    kubernetes.io/api-server-certificate-authority: "xxx"
    kubernetes.io/auth-provider: 'aws'
    kubernetes.io/aws-assume-role: 'arn:aws:iam::xxx:role/xxx'
spec:
  type: kubernetes-cluster
  owner: xxx

But beware, during the last action I faced a different issue (#23121 ) that I tried to resolve (See #23137 )

Thanks @stijnbrouwers !!
npx backstage-cli versions:bump did the trick for me.
Still using with clusterLocatorMethods: config though


Move to Nokogiri::XSLT and remove ruby-xslt dependency

We can simplify our dependency list and skip some problem with ruby-xslt on windows https://github.com/metanorma/omml2mathml/pull/5
cc @ronaldtse

@opoudjis @ronaldtse should we keep *.gemspec.old file?

Probably not. Let's delete it.

@ronaldtse PR updated

Done


PT-965 | Sort users by joined_date in django-admin

Niko Lindroos while you are doing that users list sorting task to admin, you could add a new column for creation date and a filter for it too. Those could help us too
Khin Loc sure, gonna add it now

Thought you would have added those features in this same PR too?

Already added now, forgot to push the latest changes

Katri needs this PR merged as soon as possible, so I'm merging it...


Slayer plugin shows incorrect jad/zuk task amount

Type
Incorrect behavior
Bug description
Some users have reported that recently the slayer plugin will show a very incorrect jad or zuk task length, such as 154/155. It seems to always be a large overall task length with one less remaining than the "original" length.
Reproduction steps are unknown, but this may be related to getting assigned a tzhaar task, walking away from a slayer master before completing the dialog prompting the player to switch to a jad/zuk task, then returning to the master and using "Talk-to" to resume that dialog and choosing to switch to a boss task.

i have this issue with every single zuk task i get, can confirm its not related to walking away and then using talk-to, it just instantly shows incorrect number on the infobox and !task command. Ill try pay attention from now on to the numbers and see if its related to a previous slayer task or anything


feat(lmdb): add get_env_info() to get lmdb runtime status

add get_env_info() to get lmdb runtime status
FTI-4749

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

We also need test cases and readme for this feature.

Should we move the core logic into another file, like resty.lmdb.status?

@chronolaw Please review and merge.


Support LCH colours

It's normally easier to write colours in a perceptual colourspace than sRGB. This allows you do actions like specify two colours of the same brightness by keeping one number constant, instead of having to do complex sRGB calculations.
Right now what I am doing is color: '#e4efd1' #lch(93,15,120) which allows me to see the colour in a human-readable form and hex, but this requires specifying it in two places.
Lab and Lch colour support would be good. The former is not the most natural to think in sometimes, but is an intermediate step to Lch.
My understanding of colour theory is that the conversion should be done with a D50 illuminant. The python library colormath, while not usable in a JS lib, is useful for checking that the results are right.
HSV is not a perceptual colour space and would not solve this problem. HSV was designed for real-time calculations on 1970s and 1980s hardware, having to calculate hundreds or thousands of times a second. Tangram only needs to do the colour space conversion once on load, and runs on modern hardware.

Have you tried just using a global JavaScript function to do your color conversions? Instead of hard-coding a color in you styles, you would call this function with the parameters in whatever color space you are using.


Volume slider not operable with a keyboard

The volume slider has all it needs to be accessible, it uses an ARIA role=slider, aria attributes for its values etc. However it is not focusable, its tabindex attribute is always -1 even when it's displayed. If I'm not wrong, in previous versions it was always tabindex="0".

I see. I'll add the proper tabindex to the slider and it will be available soon

To clarify, it's about the video volume slider:

Also, a nice accessibility little improvement could be adding aria-orientation="vertical", see https://www.w3.org/TR/wai-aria-practices/#slider

If the slider is vertically oriented, it has aria-orientation set to vertical.

Instead, the audio one doesn't need this because the default value of aria-orientation for a slider is horizontal.

@afercia Please download the master branch and let me know if the Captions/Chapters is working for you as expected

Radio inputs are now announced perfectly. See the screenshots below (ignore the black rectangle, that is something VoiceOver draws around focusable controls):

Perfect. Just waiting on your feedback for the volume

Just tested and seems this needs something more than tabindex. Although the volume slider is now focusable, as soon as the "Mute" button gets blurred (i.e pressing the Tab key), the slider gets hidden with display: none so there's no way to focus it.

Got it. I'll double check this

@afercia Ready. Download the master branch and test once more. It should be visible now

Also a quick question: are this and the past ticket needed for the WordPress update? If so, I can make a small release tomorrow once you confirm this issue is good to go. If not, we can create the new patch file. Let me know your thoughts. Thanks

Just tested and works nicely! Screenshot while testing with Safari + VoiceOver:

I'd really like to see MediaElement updated soon in WordPress, but I think it won't happen immediately since the 4.8 release is in Beta 1.

Sounds good. 4.1.2 version already started with these fixes, so it will see the light soon. Meanwhile, thanks for testing this. Closing this issue now. Can you also star https://github.com/mediaelement/mediaelement-plugins please? It will help a lot to give the plugins more visibility


Create Toll Free Number - prod

Business Context: we want to move to using toll-free numbers due to AWS policy changes that go into effect in April.
Number to use: +18334981539
Checklist:

[x] configure content for default keywords and start keyword for number in Pinpoint
[x] associate number to appropriate SNS topic
[x] update existing services to use toll-free number as default sms sender values

[x] VANotify
[x] va.gov
[x] dmc
[x] vanotify-team

[x] Lighthouse
[x] update prod default number in config.py

Notes:

Can't test with Skype number, need to use real phone number or Google Voice

We have made the following observations that we hypothesize are necessarily bugs, but rather features of Pinpoint system. @emilywu-tw and I will reach out to Ilya for clarification.
Observed that texts that begin with 'help' trigger the HELP default keyword response, which may just be how Pinpoint expects 'help' messages:

Also observed that texts sent quickly in succession do not trigger any response, which could be due to transactional limits per second:


July Workshop Video Update

Description

Related Issue(s)

Checklist

[ ] I have read the contribution guidelines
[ ] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

I am trimming the video a little bit then we should be good to merge.

Youtube isn't letting me cut it down.  I will try again later.  Potentially a bug.


C3 UI crash when in Toggles menu during offroad transition

Describe the bug
UI process crashes within a second or two of an onroad->offroad transition while in the Toggles menu.
What hardware does this issue affect?
comma three
Provide a route where the issue occurs
3cfdec54aa035f3f|2021-11-22--22-56-06
openpilot version
jyoung8607:mqb-long
Additional info
Happening during MQB long development, but I haven't come anywhere near the UI process. Seems 100% repeatable, 4 out of 4 attempts today. My device has uploaded several crash dumps, for example:
cd:/3cfdec54aa035f3f/crash/2021-11-22--22-56-28_2f8e0b67_selfdrive_ui__ui
Steps to repro:

Start car
Settings -> Toggles
Shut off car
Wait a few seconds, display reverts to comma logo for a couple seconds, and then UI restarts

Think it's cameraview's issue. the hideevent will be called twice after going offroad in settings window.


chore: fix number and bigint coercion

this change follows the same pattern as how booleans are coerced.
it also fixes issues with BigInt where if the value is not of a convertable value it doesn't break the app because BigInt/Symbol throw unlike the rest of the type constructors.

@edmundhung fixed


authorization option documentation inferior, not existing

Hi there,
as i want to create screen shots from my website as a logged in user, i think i need to go for the authorization option in my urlbox.io api query.
Unfortunately my approach didn't work and the missing documentation or at least example urls left me stranded.
Could you please add either extended docs on this topic or examples?
Or hand me some so i can create a PR in the READMEs.

Hi Matt, it really depends on how your site authenticates/authorises users. All that the authorization option is doing is sending an Authorization header along with the request set to whatever you pass in to it. If your site doesn't use the Authorization header as an auth mechanism, then it will have no affect. Some sites for example pass the authentication token in cookies. Do you use a well known library or framework for authing users?
As an example, if using basic http authentication the value of this header might be: "Basic " or if using token authentication such as OAuth it would be "Bearer ". The way you get  is again dependent on your site, but usually there would be an API route such as POST /your/api/token which takes in a username/password and returns you an auth token.
Adding this option to your Urlbox screenshot request is just like any other option, you just need to remember to url-encode it once it's in the querystring: api.urlbox.io/v1/api_key/png?url=yoursite.com&authorization=Bearer yourtoken
Let me know if this helps, if you need further help feel free to email support at urlbox.io perhaps with some example URL and dummy account login which we can get working.


Compile error in file BaseTestCase.swift, line 33

As in Apple Documentation at https://developer.apple.com/documentation/swift_packages/bundling_resources_with_a_swift_package , modified test files and Package.swift to work with new Bundle.module feature and work as expected (was returning a compile error in BaseTestCase.swift, line 33)

No activity, closing PR


(BKR-888) install_puppet_agent_dev_repo_on prohibits passing different platforms

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/2913/

@ferglor I'm confused as to how this fixes the issue @johnduarte raises in the ticket.
It seems here that anything passed through the opts parameter still overrides anything in the host itself. @johnduarte, I'm assuming you want some kind of situation where the host overrides the opts? Is there every a situation where you would want the opts parameter to be used?

@ferglor  this does not fix the issue. The constructed opts for first host still trashes the ability to install the repo on the next host.
@kevpl The opts values passed into the method should override the host. I would never expect the host to override the passed in opts value.
The problem is that the opts values are constructed based on the first host and are not updated for the second host. Lets look at what happens internally to the opts hash when passed two hosts (1 windows, 1 osx) and an opts value of { :puppet_collection=>"PC1", :puppet_agent_sha=>"1.5.2", :puppet_agent_version=>"1.5.2"}
During the first round of the block_on hosts:
host['platform'].to_array
=> ["windows", "2012r2", "64", nil]

opts => {:win_download_url=>"http://downloads.puppetlabs.com/windows",
 :mac_download_url=>"http://downloads.puppetlabs.com/mac",
 :pe_promoted_builds_url=>"http://pm.puppetlabs.com",
 :release_apt_repo_url=>"http://apt.puppetlabs.com",
 :release_yum_repo_url=>"http://yum.puppetlabs.com",
 :dev_builds_url=>"http://builds.delivery.puppetlabs.net",
 :puppet_collection=>"PC1",
 :puppet_agent_sha=>"1.5.2",
 :puppet_agent_version=>"1.5.2",
 :download_url=>"http://builds.delivery.puppetlabs.net/puppet-agent/1.5.2/repos/",
 :copy_base_local=>"tmp/repo_configs",
 :copy_dir_external=>"C:/PROGRA~3/"}

During the second round of the block_on hosts:
host['platform'].to_array
=> ["osx", "10.11", "x86_64", "elcapitan"]

opts => {:win_download_url=>"http://downloads.puppetlabs.com/windows",
 :mac_download_url=>"http://downloads.puppetlabs.com/mac",
 :pe_promoted_builds_url=>"http://pm.puppetlabs.com",
 :release_apt_repo_url=>"http://apt.puppetlabs.com",
 :release_yum_repo_url=>"http://yum.puppetlabs.com",
 :dev_builds_url=>"http://builds.delivery.puppetlabs.net",
 :puppet_collection=>"PC1",
 :puppet_agent_sha=>"1.5.2",
 :puppet_agent_version=>"1.5.2",
 :download_url=>"http://builds.delivery.puppetlabs.net/puppet-agent/1.5.2/repos/",
 :copy_base_local=>"tmp/repo_configs",
 :copy_dir_external=>"C:/PROGRA~3/"}

As you can see, the value of opts[:copy_dir_external] is set to C:/PROGRA~3/ for the first host and is unable to be refreshed for the second host.
To fix this problem, the internally used opts should be reconstructed fresh for each host based on the passed in opts. I would suggest doing this with a deep_copy to an internal variable.

Fixing the above would allow BKR-888 to be closed.
@kevpl The remaining impedance mismatch for me is the design where I might want to pass in an array of hosts, but cannot pass in an opts hash with values keyed to the members of that array. I don't think there is enough evidence to support changing the API, but I wanted to raise it as a usability issue with the method call.

@kevpl @johnduarte sorry guys, I've been distracted with BKR-221 so I'm only replying now. I believe that this change does in fact fix the issue at hand. So, before, we modified the opts hash with the external_copy_base from the first host object in the list of hosts passed to the function:
opts[:copy_dir_external]  ||= host.external_copy_base
I.e., we only set copy_dir_external in the opts hash if it currently is nil, using the external_copy_base off the first host we iterate over. For subsequent iterations, this assignment won't be repeated, because copy_dir_external in the opts hash is no longer nil. Later in the function, we then read this value off as follows:
onhost_copy_base = opts[:copy_dir_external]
My modification solves this issue with the following line:
onhost_copy_base = opts[:copy_dir_external] || host.external_copy_base
I.e. for each iteration over the list of hosts, we first check the opts hash for copy_dir_external, and if it hasn't been defined, we read the external_copy_base off the host in the current iteration. This means that if copy_dir_external has been specified in the opts hash, this will always override the external_copy_base from the host objects. If, however, copy_dir_external has not been specified in the opts hash, we read the external_copy_base off the host for the current iteration - hence permitting subsequent hosts to use different external_copy_base values.

Thanks @ferglor ! I have confirmed that this works for the stated case in the ticket. I must not have patched correctly before. My apologies.
:+1:

👍


fix: exclude FlowStepDeserializer exceptions from workflow logs

The test logs in workflows usually have ~32000 lines with a bunch of FlowStepDeserializer errors which slows down the search for a real problem of failure and it is almost impossible to scroll down to the end of the log in a browser.
After this change, the log contains only ~3500 lines

Wouldn't it be better to add it to the application.yaml or application.properties?

@Delawen I didn't want to suppress that error globally, only in GitHub actions (because tests use that class more times so there are lots of these errors and it is not necessary to have it in the log during testing [when tests are green]).
Otherwise, we can miss a different error from FlowStepDeserializer in production/when the app is running.
(Or if that error is not necessary anymore, we can remove, or change the log level directly in FlowStepDeserializer )


java.lang.NoSuchMethodError: No static method forArray

java.lang.NoSuchMethodError: No static method forArray([Ljavax/xml/namespace/QName;)Lorg/apache/xmlbeans/QNameSet; in class Lorg/apache/xmlbeans/QNameSet; or its super classes (declaration of 'org.apache.xmlbeans.QNameSet' appears in base.apk!classes4.dex)

poi-tl 1.7.3
poishadow-all 基于master编译

Please provide the full stacktrace.
But it sounds like a mixup of xmlbeans-jar versions, mayba via the poi-tl library... All tools need to use the exact same version of Apache POI and its dependencies.

No response, thus closing this for now.


Fix broken client-config feature

Fixes #12

I have been thinking about cleaning up this functionality in the past but never got around to do so. Thanks for the fix and the additional docs


OutOfMemoryError and  ArrayIndexOutOfBoundsException occurred when I create AsyncHttpClient

I'm using android-async-http in my app and it works well past 2 years.
However, I've got crash report from fabric and they were so weird to understand for me.
My code is below.
AsyncHttpClient client = new AsyncHttpClient();
and my crash reports are two kinds and they are below.

OutOfMemory
Fatal Exception: java.lang.OutOfMemoryError: java.lang.String[] of length<PHONE_NUMBER> would overflow
at cz.msebera.android.httpclient.conn.ssl.AbstractVerifier.(AbstractVerifier.java:75)
at cz.msebera.android.httpclient.conn.ssl.SSLSocketFactory.(SSLSocketFactory.java:145)
at com.loopj.android.http.AsyncHttpClient.getDefaultSchemeRegistry(AsyncHttpClient.java:301)
at com.loopj.android.http.AsyncHttpClient.(AsyncHttpClient.java:177)
at com.loopj.android.http.AsyncHttpClient.(AsyncHttpClient.java:147)

ArrayIndexOutOfRange
Caused by java.lang.ArrayIndexOutOfBoundsException: length=14; index=-711987539
at cz.msebera.android.httpclient.conn.ssl.AbstractVerifier.(AbstractVerifier.java:75)
at cz.msebera.android.httpclient.conn.ssl.SSLSocketFactory.(SSLSocketFactory.java:145)
at cz.msebera.android.httpclient.conn.ssl.SSLSocketFactory.getSocketFactory(SSLSocketFactory.java:162)
at com.loopj.android.http.AsyncHttpClient.getDefaultSchemeRegistry(AsyncHttpClient.java:301)
at com.loopj.android.http.AsyncHttpClient.(AsyncHttpClient.java:177)
at com.loopj.android.http.AsyncHttpClient.(AsyncHttpClient.java:147)

How could it happen? Is there someone who see this kind of error?
Or Is there something that can be explained that problems?
Someone please let me know.

This issue seems to be when you are passing a very large String[] value to the HTTPClient . Did you check the String you are passing to the HTTP call?

@StreethawkNick At that time, we didn't send or receive any packet, just create a instance of AsyncHttpClient. And the code occurred the errors is below
/**
* This contains a list of 2nd-level domains that aren't allowed to
* have wildcards when combined with country-codes.
* For example: [.co.uk].
*
* The [.co.uk] problem is an interesting one.  Should we just hope
* that CA's would never foolishly allow such a certificate to happen?
* Looks like we're the only implementation guarding against this.
* Firefox, Curl, Sun Java 1.4, 5, 6 don't bother with this check.
*/
private final static String[] BAD_COUNTRY_2LDS =
{ "ac", "co", "com", "ed", "edu", "go", "gouv", "gov", "info",
"lg", "ne", "net", "or", "org" };
actually I can't understand how could make the error that code.

Can you share the full code you wrote when creating the client, and maybe the code calling the creation of the client?
Creating and destroying Async clients repeatedly in a short span of time can result in an overflow,
Though this error looks more to do with SSL

Try to change your AsyncHttpClient to SyncHttpClient.
from new AsyncHttpClient() to new SyncHttpClient()
Its solved the OOM issue for my case

1st issue might be upstream issue of HttpClient AbstractVerifier.java, and you didn't list what version of library you do use, so I'm unable to help you
2nd issue looks the same.
However both issues look like HttpClient is failing due to information listed in SSL Certificate the server provides, or in the SSL Certificate you've provided to do certificate pinning


[ADP-0000] Bump hls to <IP_ADDRESS> with patched branch

[x] Bump hls to 2.6 using a special branch that has a workaround for a problem that affects us https://github.com/input-output-hk/hydra/commit/0b8776ac0bc3f62c8e454feda33327e7d39ff631

@paolino I've cherry-picked the commit(s) from this branch into https://github.com/cardano-foundation/cardano-wallet/pull/4431.


Cilium can fail to take over ownership of CEP if internal node IP of the local node changes on Cilium restart

Description
It is possible for a node to change internal node IPs (observed on GKE, with preemptive nodes) and the "sync-to-k8s-ciliumendpoint" controller will be forever stuck on the following error msg:
level=warning msg="could not take ownership of existing ciliumendpoint" containerID=afc34c5868 controller="sync-to-k8s-ciliumendpoint (1412)" datapathPolicyRevision=162 desiredPolicyRevision=162 endpointID=1412 error="endpoint sync cannot take ownership of CEP that is not local (\"<IP_ADDRESS>\")" identity=1377 ipv4=<IP_ADDRESS> ipv6= k8sPodName=default/curl-84f95b5f4b-mbk9v subsys=endpointsynchronizer

See the offending code here: https://github.com/cilium/cilium/blob/404bf818518ab9f1961cfe67cd43a3b1bf040130/pkg/k8s/watchers/endpointsynchronizer.go#L358
User impact

If Cilium was installed with the Cilium CLI, then installation will fail and trigger a rollback because the CLI detects that controllers are failing.
Cilium will never be able to manage these workloads because of the error bailing out

Additional thoughts

It seems that the above code relies on the CEP UID and if not found, falls back to the node IP check.
It's possible that the CEP UID was not restored properly in this case

Has it ever worked and have we always just been falling back to node IPs because those don't often change? Not obvious from the logs.

I think the cases covered in Test_updateCEPUID from my read don't cover the case where a node IP is mismatching

Fixed by https://github.com/cilium/cilium/pull/26281


Fix valgrind warning related to CStringDatum used instead of NameDatum plus some more fixes.

Description
This PR fixes multiple valgrind warnings.

Replaced all CStringGetDatum occurrences with NameGetDatum when doing CatalogTuple DML operation on a name column. NameDatum is always of NAMEDATALEN length and null padded if needed.
It is okay to use CStringGetDatum in syscache lookup because engine converts it into NameDatum here
Fix string literal to rowversion or timestamp cast warning. Row version is always of fixed length but when we cast string literal to rowversion for a smaller input string, we set the typmod correctly but do not actually blank pad the input string. As a fix we will simply reuse the varbinary/binary handling for string literals for row versions and timestamp, this is possible because row versions and timestamp were getting internally converted to varbinary type.
Make sure string is not empty before accessing its last character in sp_execute_postgresql & sp_addrolemember & sp_droprolemember &sp_rename_internal
In TdsRecvTypeTable we were not initialising all the entries of nulls array. Fixed that.
When logging TVP parameter we simply want to log the name, but we were sending CString as input with a record type which is wrong. To fix it, we will now use CString type for logging TVP name.

Issues Resolved
[BABEL-5104]
[BABEL-5221]
[BABEL-4634]
[BABEL-4644]
Test Scenarios Covered
Following JDBC tests do not throw any error with valgrind now
GRANT_SCHEMA
Test-sp_addrolemember-vu-prepar
Test-sp_addrolemember-vu-verify
Test-sp_addrolemember-vu-cleanu
babel-4475-vu-prepare
babel-4475-vu-verify
babel-4475-vu-cleanup
TestTvp -> with log_statements GUC set to 'all'
Sign Off
Signed-off-by: Tanzeel Khan<EMAIL_ADDRESS>Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

44 of 48 (91.67%)  changed or added relevant lines in 9 files are covered.
3 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.005%) to 74.231%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_tds/src/backend/tds/tdsrpc.c
0
1
0.0%

contrib/babelfishpg_tsql/src/hooks.c
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

contrib/babelfishpg_tsql/src/hooks.c
1
80.35%

contrib/babelfishpg_tsql/src/pltsql_coerce.c
1
80.56%

contrib/babelfishpg_tds/src/backend/tds/tdsrpc.c
1
71.45%

Totals

Change from base Build<PHONE_NUMBER>9:
0.005%

Covered Lines:
44676

Relevant Lines:
60185

💛  - Coveralls


Spoof left and right half of stats independently

Closes #2

Adds switches to each skill that allows the user to decide whether the spoof value applies to only the left, to only the right, or to both parts of the skill display (eg, spoofing 30 attack to 1 can now mean any of these: 1/30, 30/1 or 1/1)

There are improvements that could be made to this code in future, I think. We could make both values independently settable. For instance, rather than the two bools I created, we could use the existing int [skill]Level value for the right value and create a second int[skill]Boost value to control the left value.
However, if I had implemented it in that way, I would have harmed existing user experiences by requiring them to input twice the number of stat overrides even if they didn't want to have the values be independent of each other. Plus this is my first attempt at making a change to a runelite plugin so I wanted to keep it as simple as possible :)


Only null and undefined included in later overloads during inference between overloads

Bug Report

🔎 Search Terms

overload null undefined
🕗 Version & Regression Information

This is the behavior in every version I tried, and I wrote the FAQ

⏯ Playground Link
Playground link with relevant code
💻 Code
This is a bit over-reduced but it's still weird
declare function callIt<T>(func: {
    (): T;
    (): T;
}): T;

declare function overloaded(): string;
declare function overloaded(): number | null;

// m: string | null. Where'd number go?
const m = callIt(overloaded);

🙁 Actual behavior
m: string | null
🙂 Expected behavior
m: string | number | null
This feels intentional since it only null and undefined make it out of the second signature, but I can't find where we do this or what the motivation behind it is.

Hello, same issue on my side:
function test(): undefined;
function test(path: string): null | string | number;

const t = test("hey");

t has type string | number;
If you call test() then t has type undefined.
After exchanging types, it looks like that undefined and null are both ignored when given with other types.

I discover that with react-router 5 types declaration where both hook calls returned match<Params>
export function useRouteMatch<Params extends { [K in keyof Params]?: string } = {}>(): match<Params>;
export function useRouteMatch<Params extends { [K in keyof Params]?: string } = {}>(
    path: string | string[] | RouteProps,
): match<Params> | null;


Update exercise.py

I ONLY CHANGE THE COMMENTING PART SO THAT STUDENT WILL GET UNDERSTAND CODE EASLY.


Are test_eval and test_llama the same data?

Dear Author, Hello, When I followed the data preparation in the challenge/readme documentation, I realized that test_eval.json and test_llama.json are essential the same data (derived from test.json),
and if I train my model using test_llama.json and then generate the output.json, and then ultimately evaluate it according to the documented methods (using output.json and test_eval.json), wouldn't that be equivalent to assess my model with the training set?  Is my understanding wrong?

@DevLinyan

@ChonghaoSima

The files test_eval.json and test_llama.json contain the same data but in different formats. The evaluation can only be conducted using the specific format in test_eval.json.

Thanks for your reply, if so is the evaluation valid? Because I am using test_llama.json to train my model, if I then use test_eval.json to evaluate it, what about the training set and validation set are the same?

@DevLinyan

Not sure what you mean by "the training set and validation set are the same".
The evaluationo is valid as long as you use our provided test file and submit to our official test server.


Error message translation error

Description
Not a breaking issue but there seems to be a mistake with the "longMessage" returned when clerk encounters an invalid email. email_address must be a valid email address   was returned for the English translation, but this should be Email address must be a valid email address instead. Could this be addressed soon? 🙂

Hello @Israeltheminer and thank you for opening this issue.
This is not related to some translation error. It's the error message generated from our Backend, so it may be tricky to change.
How did you manage to view this error message? Could you provide reproduction steps?

If you're using our components (without implementing a custom flow), you could override the translation with the following:
const unstableLocalizationErrors = {
    form_param_format_invalid__email_address: 'Email address must be a valid email address'
};
// @ts-expect-error
<ClerkProvider localization={{unstable__errors: unstableLocalizationErrors}} />

Hello @Israeltheminer and thank you for opening this issue. This is not related to some translation error. It's the error message generated from our Backend, so it may be tricky to change. How did you manage to view this error message? Could you provide reproduction steps?

I can see you have provided a solution 👍. But for future context, the error is returned when working with the signUp.create method of the useSignUp @clerk/nextjs API.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Reset color settings after writing body

The color settings are currently reset immediately after writing the header value in the log_warning and log_error functions, but before setting and writing the (non-bold), colored body value.
As a result, the color setting persist after the function call (e.g. after logging a warning, subsequent log_info output will be yellow). I might be missing something here -- but I doubt that's the intended behavior?

Removing skip-changelog since this (a) changes user-facing behaviour, (b) will fix a bug (see #555) - so should be mentioned in the changelog.


Test SecHub Using Java 19

Test SecHub using Java 19.
Test whether SecHub can run using Java 19
Test whether SecHub can be build using Java 19
Report/document any incompatibilities as part of the issue.

Keep in mind that Java 19 will be available in September: http://openjdk.java.net/projects/jdk/19/. It is not yet available.
However, there are already Early-Access Builds available: https://jdk.java.net/19/.

Duplicate of #1724


Save Checkpoints in PartialFitRegressorUDF

Background

Training can take long
It would be nice to check out regular checkpoints to get a feeling about the progress of training
Furthermore, checkpoints could be used for continuing training if it fails early

Background

Save regularly checkpoints during training to the bucketfs in PartialFitRegressorUDF

Obsolete


Formatted "Algorithms and Data Structures" section in file "free-programming-books-subjects.md".

Added new links for books that were deleted due to broken links.
Fix old "http" links to "https" ones inside Meta Lists.
Formatted section "Algorithms and Data Structures".
What does this PR do?
Add and update resources.
For resources
Description
Added new links for books and a website that were removed because of broken links.
Updated all supporting "http" links to "https" one under Meta Lists.
In section "Algorithms and Data Structures":

Added missing author names for all books.
Added missing file types for all books.
Updated supporting "http" links to "https" links.

Why is this valuable (or not)?
Added new working links for resources that were deleted.
Updated "http" links to "https" ones.
Added author names and file types.
How do we know it's really free?
The PDF files are free to download.
The new "https" links are working.
For book lists, is it a book? For course lists, is it a course? etc.
Some books and a website.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

@eshellman sir, I request you to review the changes here as I am unable to continue work on this file.

@eshellman sir, I request you to merge this PR for now. I have fixed many listings according to what you said. I would address the this problem as a whole in a new PR. I am facing difficulty in correcting the exact changes I made. I am using GitHub from the browser.

Thank you very much sir! 🥹


Encapsulate the sampling steps using OpFromGraph

In this PR I explore the possibility to encapsulate the sampling steps in their own Ops using OpFromGraph. This allows to define types for the different kinds of samplers, and may allow easier manipulation of the graphs downstream as discussed in #71.

[x] Gibbs sampling steps. The Op is created in sampler finders
[x] Added a SamplingStep type that subclasses OpFromGraph, holds the sampled RVs and the sampler parameters
[x] NUTS
[x] Can I add information that allows to identify the parameters to adapt? If so how to adapt them? (parameter types?)
[x] FFBS (not currently used in construct_sampler)
[ ] Can this be used to change the scan order of the different updates in the sampler?

I have encapsulated the Gibbs steps and the NUTS step in OpFromGraph. The following code:
import aesara
import aesara.tensor as at

srng = at.random.RandomStream(0)

X = at.matrix("X")

tau_rv = srng.halfcauchy(0, 1, name="tau")
lmbda_rv = srng.halfcauchy(0, 1, size=X.shape[1], name="lambda")
beta_rv = srng.normal(0, lmbda_rv * tau_rv, size=X.shape[1], name="beta")

a = at.scalar("a")
b = at.scalar("b")
h_rv = srng.gamma(a, b, name="h")

eta = X @ beta_rv
p = at.sigmoid(-eta)
Y_rv = srng.nbinom(h_rv, p, name="Y")

y_vv = Y_rv.clone()
y_vv.name = "y"

sample_vars = [tau_rv, lmbda_rv, beta_rv, h_rv]
sampler, initial_values = construct_sampler({Y_rv: y_vv}, srng)
h_post_step = sampler.sample_steps[h_rv]
aesara.dprint(h_post_step)

Returns:
DispersionGibbsKernel{inline=True}.0 [id A] 'h_posterior'
 |h [id B]
 |Elemwise{sigmoid,no_inplace} [id C]
 | |dot [id D]
 |   |Elemwise{neg,no_inplace} [id E]
 |   | |X [id F]
 |   |NBRegressionGibbsKernel{inline=True} [id G] 'beta_posterior'
 |     |beta [id H]
 |     |Elemwise{mul,no_inplace} [id I]
 |     | |HorseshoeGibbsKernel{inline=True}.0 [id J] 'lambda_posterior'
 |     | | |beta [id H]
 |     | | |Elemwise{pow,no_inplace} [id K]
 |     | | | |lambda [id L]
 |     | | | |InplaceDimShuffle{x} [id M]
 |     | | |   |TensorConstant{2} [id N]
 |     | | |Elemwise{pow,no_inplace} [id O]
 |     | | | |tau [id P]
 |     | | | |TensorConstant{2} [id Q]
 |     | | |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B5A82E0>) [id R]
 |     | | |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E4D1200>) [id S]
 |     | | |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E549040>) [id T]
 |     | | |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E85AF20>) [id U]
 |     | | |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B5EA120>) [id V]
 |     | | |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B5EA660>) [id W]
 |     | | |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B6A19E0>) [id X]
 |     | |InplaceDimShuffle{x} [id Y]
 |     |   |HorseshoeGibbsKernel{inline=True}.1 [id J] 'tau_posterior'
 |     |X [id F]
 |     |h [id B]
 |     |y [id Z]
 |     |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E549040>) [id T]
 |     |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E85AF20>) [id U]
 |     |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B5C59E0>) [id BA]
 |     |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B5C5660>) [id BB]
 |     |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E4F3660>) [id BC]
 |     |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E4F3040>) [id BD]
 |     |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E4D1200>) [id S]
 |     |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B6A5E40>) [id BE]
 |a [id BF]
 |Elemwise{true_div,no_inplace} [id BG]
 | |TensorConstant{1.0} [id BH]
 | |b [id BI]
 |y [id Z]
 |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E4F3660>) [id BC]
 |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E4F3040>) [id BD]
 |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E4D1200>) [id S]
 |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E549040>) [id T]
 |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640E85AF20>) [id U]
 |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B5EAF20>) [id BJ]
 |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B6983C0>) [id BK]
 |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B5C59E0>) [id BA]
 |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B5C5660>) [id BB]
 |RandomGeneratorSharedVariable(<Generator(PCG64) at 0x7F640B6A5E40>) [id BE]

You have also probably noticed that the signature of construct_sample is different, indeed sample_step, updates and parameters are now encapsulated in a datalclass:
sampler, initial_values = construct_sampler({Y_rv: y_vv}, srng)

print(sampler.sample_steps)
# {tau: tau_posterior, lambda: lambda_posterior, beta: beta_posterior, h: h_posterior}

print(sampler.samplers)
# [DispersionGibbsKernel, NBRegressionGibbsKernel, HorseshoeGibbsKernel]

print(sampler.parameters)
# {}
# A map between the `Apply` nodes  and the parameters

A little refactoring work, especially around the names, is necessary, but it feels good enough for now.

I have encapsulated the Gibbs steps and the NUTS step in OpFromGraph. The following code:

That's awesome!  We can definitely do something about all those shared RNG variables, and especially OpFromGraph's ability to handle updates (i.e. https://github.com/aesara-devs/aesara/issues/1316).  (N.B. https://github.com/aesara-devs/aesara/pull/1306 was a precursor PR from a branch in which I implemented https://github.com/aesara-devs/aesara/issues/1316.  I'll push that shortly.)

I streamlined the interfaces as much as possible for now, we'll add more information to these objects as the need arises. The Sampler type holds all the information that was returned before by construct_sampler with two differences:

parameters is now a map from their SamplingSteps to their parameters;
stages is a map from SamplingSteps to the (original) RVs whose value they update


Fix cleanup and apt packages

==> production: Provisioning with shell script: src/scripts/linux/cleanup.sh
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: The following packages were automatically installed and are no longer required:
    production: libice6 libpthread-stubs0-dev libsm6 libx11-doc libxt6 xorg-sgml-doctools
    production: Use 'sudo apt autoremove' to remove them.
    production: The following packages will be REMOVED:
    production: libice-dev* libsm-dev* libx11-dev* libxau-dev* libxcb1-dev* libxdmcp-dev*
    production: libxt-dev* x11proto-core-dev* x11proto-input-dev* x11proto-kb-dev*
    production: xtrans-dev*
    production: 0 upgraded, 0 newly installed, 11 to remove and 8 not upgraded.
    production: After this operation, 8,423 kB disk space will be freed.
    production: (Reading database ... 43478 files and directories currently installed.)
    production: Removing libxt-dev:amd64 (1:1.1.5-0ubuntu1) ...
    production: Removing libsm-dev:amd64 (2:1.2.2-1) ...
    production: Removing libice-dev:amd64 (2:1.0.9-1) ...
    production: Removing libx11-dev:amd64 (2:1.6.3-1ubuntu2) ...
    production: Removing libxcb1-dev:amd64 (1.11.1-1ubuntu1) ...
    production: Removing libxau-dev:amd64 (1:1.0.8-1) ...
    production: Removing libxdmcp-dev:amd64 (1:1.1.2-1.1) ...
    production: Removing x11proto-input-dev (2.3.1-1) ...
    production: Removing x11proto-core-dev (7.0.28-2ubuntu1) ...
    production: Removing x11proto-kb-dev (1.0.7-0ubuntu1) ...
    production: Removing xtrans-dev (1.3.5-1) ...
    production: Processing triggers for man-db (2.7.5-1) ...
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: The following packages were automatically installed and are no longer required:
    production: libice6 libpthread-stubs0-dev libsm6 libxt6 xorg-sgml-doctools
    production: Use 'sudo apt autoremove' to remove them.
    production: The following packages will be REMOVED:
    production: libx11-doc*
    production: 0 upgraded, 0 newly installed, 1 to remove and 8 not upgraded.
    production: After this operation, 9,837 kB disk space will be freed.
    production: (Reading database ... 43009 files and directories currently installed.)
    production: Removing libx11-doc (2:1.6.3-1ubuntu2) ...
    production: Processing triggers for man-db (2.7.5-1) ...
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: Package 'libxmuu1' is not installed, so not removed
    production: Package 'xauth' is not installed, so not removed
    production: Some packages could not be installed. This may mean that you have
    production: requested an impossible situation or if you are using the unstable
    production: distribution that some required packages have not yet been created
    production: or been moved out of Incoming.
    production: E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
    production: The following information may help to resolve the situation:
    production:
    production: The following packages have unmet dependencies:
    production: openjdk-8-jre-headless : Depends: libx11-6 but it is not going to be installed
    production: Depends: libxext6 but it is not going to be installed
    production: Depends: libxi6 but it is not going to be installed
    production: Depends: libxrender1 but it is not going to be installed
    production: Depends: libxtst6 but it is not going to be installed
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: Package 'ppp' is not installed, so not removed
    production: Package 'pppconfig' is not installed, so not removed
    production: Package 'pppoeconf' is not installed, so not removed
    production: The following packages were automatically installed and are no longer required:
    production: libice6 libpthread-stubs0-dev libsm6 libxt6 xorg-sgml-doctools
    production: Use 'sudo apt autoremove' to remove them.
    production: 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: Package 'friendly-recovery' is not installed, so not removed
    production: Package 'installation-report' is not installed, so not removed
    production: Package 'popularity-contest' is not installed, so not removed
    production: Package 'command-not-found' is not installed, so not removed
    production: Package 'command-not-found-data' is not installed, so not removed
    production: The following packages were automatically installed and are no longer required:
    production: libice6 libpthread-stubs0-dev libsm6 libxt6 xorg-sgml-doctools
    production: Use 'sudo apt autoremove' to remove them.
    production: 0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: The following packages will be REMOVED:
    production: libice6 libpthread-stubs0-dev libsm6 libxt6 xorg-sgml-doctools
    production: 0 upgraded, 0 newly installed, 5 to remove and 8 not upgraded.
    production: After this operation, 826 kB disk space will be freed.
    production: (Reading database ... 42070 files and directories currently installed.)
    production: Removing libxt6:amd64 (1:1.1.5-0ubuntu1) ...
    production: Removing libsm6:amd64 (2:1.2.2-1) ...
    production: Removing libice6:amd64 (2:1.0.9-1) ...
    production: Removing libpthread-stubs0-dev:amd64 (0.3-4) ...
    production: Removing xorg-sgml-doctools (1:1.11-1) ...
    production: Processing triggers for libc-bin (2.23-0ubuntu7) ...

Fresh log:
==> production: Provisioning with shell script: src/scripts/linux/cleanup.sh
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: The following packages were automatically installed and are no longer required:
    production: libice6 libpthread-stubs0-dev libsm6 libx11-doc libxt6 xorg-sgml-doctools
    production: Use 'sudo apt autoremove' to remove them.
    production: The following packages will be REMOVED:
    production: libice-dev* libsm-dev* libx11-dev* libxau-dev* libxcb1-dev* libxdmcp-dev*
    production: libxt-dev* x11proto-core-dev* x11proto-input-dev* x11proto-kb-dev*
    production: xtrans-dev*
    production: 0 upgraded, 0 newly installed, 11 to remove and 0 not upgraded.
    production: After this operation, 8,423 kB disk space will be freed.
    production: (Reading database ... 45769 files and directories currently installed.)
    production: Removing libxt-dev:amd64 (1:1.1.5-0ubuntu1) ...
    production: Removing libsm-dev:amd64 (2:1.2.2-1) ...
    production: Removing libice-dev:amd64 (2:1.0.9-1) ...
    production: Removing libx11-dev:amd64 (2:1.6.3-1ubuntu2) ...
    production: Removing libxcb1-dev:amd64 (1.11.1-1ubuntu1) ...
    production: Removing libxau-dev:amd64 (1:1.0.8-1) ...
    production: Removing libxdmcp-dev:amd64 (1:1.1.2-1.1) ...
    production: Removing x11proto-input-dev (2.3.1-1) ...
    production: Removing x11proto-core-dev (7.0.28-2ubuntu1) ...
    production: Removing x11proto-kb-dev (1.0.7-0ubuntu1) ...
    production: Removing xtrans-dev (1.3.5-1) ...
    production: Processing triggers for man-db (2.7.5-1) ...
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: The following packages were automatically installed and are no longer required:
    production: libice6 libpthread-stubs0-dev libsm6 libxt6 xorg-sgml-doctools
    production: Use 'sudo apt autoremove' to remove them.
    production: The following packages will be REMOVED:
    production: libx11-doc*
    production: 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
    production: After this operation, 9,837 kB disk space will be freed.
    production: (Reading database ... 45300 files and directories currently installed.)
    production: Removing libx11-doc (2:1.6.3-1ubuntu2) ...
    production: Processing triggers for man-db (2.7.5-1) ...
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: Package 'libxmuu1' is not installed, so not removed
    production: Package 'xauth' is not installed, so not removed
    production: Some packages could not be installed. This may mean that you have
    production: requested an impossible situation or if you are using the unstable
    production: distribution that some required packages have not yet been created
    production: or been moved out of Incoming.
    production: The following information may help to resolve the situation:
    production:
    production: The following packages have unmet dependencies:
    production: openjdk-8-jre-headless : Depends: libx11-6 but it is not going to be installed
    production: Depends: libxext6 but it is not going to be installed
    production: Depends: libxi6 but it is not going to be installed
    production: Depends: libxrender1 but it is not going to be installed
    production: Depends: libxtst6 but it is not going to be installed
    production: E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: Package 'ppp' is not installed, so not removed
    production: Package 'pppconfig' is not installed, so not removed
    production: Package 'pppoeconf' is not installed, so not removed
    production: The following packages were automatically installed and are no longer required:
    production: libice6 libpthread-stubs0-dev libsm6 libxt6 xorg-sgml-doctools
    production: Use 'sudo apt autoremove' to remove them.
    production: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: Package 'friendly-recovery' is not installed, so not removed
    production: Package 'installation-report' is not installed, so not removed
    production: Package 'popularity-contest' is not installed, so not removed
    production: Package 'command-not-found' is not installed, so not removed
    production: Package 'command-not-found-data' is not installed, so not removed
    production: The following packages were automatically installed and are no longer required:
    production: libice6 libpthread-stubs0-dev libsm6 libxt6 xorg-sgml-doctools
    production: Use 'sudo apt autoremove' to remove them.
    production: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    production: Reading package lists...
    production: Building dependency tree...
    production: Reading state information...
    production: The following packages will be REMOVED:
    production: libice6 libpthread-stubs0-dev libsm6 libxt6 xorg-sgml-doctools
    production: 0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
    production: After this operation, 826 kB disk space will be freed.
    production: (Reading database ... 44361 files and directories currently installed.)
    production: Removing libxt6:amd64 (1:1.1.5-0ubuntu1) ...
    production: Removing libsm6:amd64 (2:1.2.2-1) ...
    production: Removing libice6:amd64 (2:1.0.9-1) ...
    production: Removing libpthread-stubs0-dev:amd64 (0.3-4) ...
    production: Removing xorg-sgml-doctools (1:1.11-1) ...
    production: Processing triggers for libc-bin (2.23-0ubuntu9) ...

the same issue for JenkinsSlaves


Example: Deploying PHP Guestbook application with Redis

The yaml file in "Creating the Guestbook Frontend Deployment" uses an image no more available ( gcr.io/google_samples/gb-frontend:v5 )
I solved the issue by using corelab/gb-frontend
Here is the working version I used!
apiVersion: apps/v1
kind: Deployment
metadata:
  name: frontend
spec:
  replicas: 3
  selector:
    matchLabels:
        app: guestbook
        tier: frontend
  template:
    metadata:
      labels:
        app: guestbook
        tier: frontend
    spec:
      containers:
      - name: php-redis
        image: corelab/gb-frontend:v5
        env:
        - name: GET_HOSTS_FROM
          value: "dns"
        resources:
          requests:
            cpu: 100m
            memory: 100Mi
        ports:
        - containerPort: 80

Hey @selganor74, Can you share us a pic of the solved issue here?

/kind bug

/triage accepted

/assign


Add comment with link to design legend

Current Behavior
Most folks don't know how to interpret the visual snapshots.
Desired Behavior
A comment that links to a "How to interpret Meshery Designs" would be helpful. - - a legend is needed.

Contributor Resources and Handbook
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

📚 See contributing instructions.
🎨 Wireframes and designs for Layer5 site in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack.

Join the Layer5 Community by submitting your community member form.

@Tsu-kimi, I completely missed your message. My apologies.

Fixed by https://github.com/layer5labs/kanvas-snapshot/issues/123


[baseline][ogre] Disable find_package(QT)

What does your PR fix?
Tries to fix ogre build errors when it has Qt6_FOUND despite CMAKE_DISABLE_FIND_PACKAGE(Qt6).

Which triplets are supported/not supported?
I still need to fix warnings about unused variables. (To be pushed when CI finished.)

Thank you!


Update ReadMe.md

Update conventions based on comment in issue #13
https://github.com/ardalis/Ardalis.Extensions/issues/13#issuecomment-884545722

You up for it?

Sure


Update README to account for the newest version of this lib

According to the pub website

Awesome, thanks for the update


Add Python 3.10 to test matrix

Codecov Report

Merging #15 (8970879) into main (d74c958) will decrease coverage by 6.0%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main     #15     +/-   ##
========================================
- Coverage   100.0%   94.0%   -6.0%
========================================
  Files           6       6
  Lines         100     100
========================================
- Hits          100      94      -6
- Misses          0       6      +6

Impacted Files
Coverage Δ

quickhttp/http_server.py
90.6% <0.0%> (-9.4%)
:arrow_down:


Make macros "extendable"

This allows to make macros extendable and overwriteable.
Let's say I have a bunch of macros, which I usually use in my template, but I like to have one or two behave differently, but still be able to use all my macros from the "master" macros, I just write
{% extends "mastermacros.twig %}
{% macro foo(name) %} different foo {% macro %}
and still can use the macros from mastermacros.twig, without changing my template if I want to overwrite another macro later.
See https://github.com/chregu/Twig/commit/819e3ed72c201ddb867b528ab713bc82a4c4e5ff for the tests and some examples.
It's additional code pretty much in the core of Twig, so I'm not sure, if it has any sideeffects. The tests still run and that part of the code is not touched by any of the old tests.
Would be great, if you could include that in standard Twig, it adds some more possibilities to make Twig macros more extendable and reusable

Hi Chegru,
I like this tweak. It'd be ideal if this was built in - solves my current problems.
Thanks,
Lucas.


[gardening] Replace usages of deprecated withUnsafeBytes.

The old signature for withUnsafeBytes/withUnsafeMutableBytes is
deprecated but it is used in the tests. Remove all the usages of the
deprecated signature and use the newer signature instead.
Should remove a lot of deprecation warnings while compiling the tests.

@swift-ci please test


Sandbox errors when function res is invoked with status

When a function is invoked with status, sandbox errors on request. Example:
res({
    status: 500,
    html: 'foo'
  })

Error:
/project/node_modules/aws-sdk/lib/request.js:31
            throw err;
            ^

TypeError: Cannot read property 'status' of undefined
    at _res (/project/node_modules/@architect/workflows/src/sandbox/http/_response.js:48:21)
    at _write (/project/src/html/get-000page/node_modules/@architect/functions/src/http/_response.js:22:7)
    at _update (/project/src/html/get-000page/node_modules/@architect/functions/src/http/session/write.js:26:5)
    at Response._create (/project/src/html/get-000page/node_modules/@architect/functions/src/http/session/_update.js:16:7)
    at Request.<anonymous> (/project/node_modules/aws-sdk/lib/request.js:364:18)
    at Request.callListeners (/project/node_modules/aws-sdk/lib/sequential_executor.js:109:20)
    at Request.emit (/project/node_modules/aws-sdk/lib/sequential_executor.js:81:10)
    at Request.emit (/project/node_modules/aws-sdk/lib/request.js:683:14)
    at Request.transition (/project/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/project/node_modules/aws-sdk/lib/state_machine.js:14:12)

Error does not replicate with status not set, i.e.:
res({
    html: 'foo'
  })

sorry about that! should be fixed in<EMAIL_ADDRESS>