Images used should include Apache httpd/httpd-devel packages.

The Docker images used as a base or which is created should include httpd/httpd-devel packages or equivalent.
This will allow the use of a more capable WSGI server such as Apache/mod_wsgi to be used.
The gunicorn WSGi server is not the best default server to rely on due to lack of the ability to serve up static files in a performant way. It also does not provide a multi threaded worker which is an important option for WSGI applications which are more I/O bound than CPU bound. The lack of a multi threaded worker forces the use of more worker processes and thus more overall memory, or even the need to scale out to more instances.
Multi threading capabilities are therefore an important choice that users should have available to them and Apache/mod_wsgi is the most flexible and robust choice for that for this sort of environment. The more limited choices of gunicorn don't allow for it. Although one can use coroutines in gunicorn, these are not necessarily a good solution either, as users have to be very aware of requirements for all code to be coroutine aware.
With Apache httpd runtime and development packages being available, it would be a very simple process for users to then use mod_wsgi-express.
All that would be required on users part would be to add mod_wsgi to requirements.txt and drop in an app.py file containing at the minimum something like:
import mod_wsgi.server

mod_wsgi.server.start('wsgi.py', '--port', '8080')

Confirmed that simply adding:
httpd
httpd-devel

to the list of packages to install in the Dockerfile will allow mod_wsgi-express to be installed and then work, allowing Apache/mod_wsgi to be used instead.
Note that #60 had to be fixed first as something about what mod_wsgi package installation does triggers something that updates the nssdb, which leaves it with permissions that cause the chmod in the assemble script to fail and so cause the whole build to fail.

@GrahamDumpleton we are first looking into making the httpd image more useful in terms of layering so we can easily plug configuration for mod_wsgi into it (and allow users to use Apache/mod_wsgi instead of gunicorn). Also I think we would like to use the httpd image as a base image for other frameworks, like Ruby (passenger), Perl and PHP. @bparees I think we should bump the priority of having extendable httpd image in Trello.

For mod_wsgi-express there isn't really any point to doing that as the binary mod_wsgi package from SCL isn't used, it is simply pip installed. When using mod_wsgi-express the user doesn't need to do any Apache configuration themselves at all as mod_wsgi-express does it all automatically. This provides the best flexibility and gets away from the old OpenShift 2 way of doing things where the user couldn't change the Apache configuration at all and so usually ended up with an inadequate configuration that didn't suit their specific application.

FWIW, I personally obviously want to see Apache/mod_wsgi the default again and the whole mod_wsgi-express has been purpose built to a degree to make it easier to deploy Apache/mod_wsgi in Docker. It even has special stuff in it to allow it to be used on OpenShift 2.
In going back to using Apache/mod_wsgi via mod_wsgi-express, one of the things that will be quite easy to achieve is a greater ease of portability of an application from OpenShift 2 to 3. This is because one could prior to starting up mod_wsgi-express detect when legacy wsgi/application and wsgi/static exist and so change the command line options to support the use of these. Thus less work for a user in moving across.
Another thing one could perhaps do is detect if a legacy .openshift/action_hooks directory exists and invoke what hooks one still could do for build and deploy. You would have to perhaps fake up certain legacy environment variables related to OpenShift 2 in case they are being used, but the effort could again make it easier to support better moving applications across.
Overall I prefer the use of the action hooks to having too much magic going on in assemble/run scripts such as detecting use of Django and running collectstatic. Magic is some times good, but for things like that I don't believe it always is and just so they know what is going on, is better to have them opt in.

FYI, I created this trello card: https://trello.com/c/keOtxxXt/697-add-httpd-s2i-image-as-a-base-for-httpd-images

@hanzz FYI^

Just noting that the other main benefit of getting back to having mod_wsgi support is integration with FreeIPA's Apache based SSO strategies: http://www.freeipa.org/page/Web_App_Authentication

@rhcarvalho I think we should just add the requested packages to the dockerfile for now.  I'd rather not keep waiting on the common httpd base image.

For me this isn't really a priority at this point. I have my own separate Python S2I builder which goes quite a way beyond the default builder functionality, supported WSGI servers etc. I have also started a conversation in the Python community about the community developing their own higher level Python base image for Docker which gives beyond Docker Inc Python base images. Part of that will be S2I support. Anyway, the aim is to draw on the wider expertise of the Python web community to come up with a Docker base image and S2I builder which the community believes better suits there needs, with the community supporting it. This would hopefully garner interest beyond just OpenShift and at least have people using a better base image that is setup properly to not run as root etc. I will be presenting more about my own S2I builder for Python and the idea of a community supported builder at devconf.cz.

Shouldn't all those improvements and functionalities be merged here? I don't see why "openshift/sti-python" cannot reflect the needs and wishes of the community and a fork be required.

@rhcarvalho +1

The benefit of separating upstream builders from integrated builders is similar to the benefit of separating upstream projects from downstream packages - even if the downstream version mostly just tracks the upstream one, it doesn't have to track it directly. For example, this would mean the downstream builder can potentially incorporate OpenShift specific additions that wouldn't make sense in an image designed to be usable independently of OpenShift.

@bparees @rhcarvalho one of the reason is that we won't get python 3.15 (is that right?) anytime soon as we depend on SCL to package that. Another reason is that what @GrahamDumpleton was describing to us means the current builder will not backward compatible with the changes he wants to make (or community wants). I agree that if there is a fundamental feature we are missing in python image, we should add it, but our changes should be additive not backward incompatible. I don't know how that play with image @GrahamDumpleton has in mind.

@ncoghlan fair enough, but I so far I don't think we've seen any features that don't make sense for both a generic s2i builder, and the openshift s2i builder.  If we reach a point where there are features the community wants in a python s2i builder that we do not want in this image, sure, forking makes sense.
@mfojtik a different image for a different version of python is a completely different topic imho.  Yes, that would not go in this repository since it's not SCL as you note, but that's really not what we're primarily discussing here.
If adding the httpd-devel packages creates a backards compatibility problem, I agree we need to think about that more carefully and see if there's a way we can do it that does not introduce that problem.  If @GrahamDumpleton indicated the changes are not backwards compatible, I missed it, but I admit to not reading the details of this request in great depth.  I expect @rhcarvalho to sort that out :)

From what I have now heard around timelines for when things would need to be a part of the builder image in order to make it into online preview, if we can get httpd and httpd-dev into the image I will at least gladly accept that much. This is on the basis that it is likely going to be the only change that will be able to be incorporated in the time available. Any other more substantial changes are unlikely to be able to be implemented, reviewed and accepted by what I understand is the cut off.
For the preview the only strategy I can see as being workable, from my perspective of wanting to provide a better and more production capable solution, is if we are still going to push people to use the provided S2I builder base images, is for me personally, or under the umbrella of the evangelists team, to have a separate Git repository with alternate assemble and run scripts which would be pulled in by a user into their own application code through a .sti/bin/assemble override script. I would then recommend people use that as an interim measure when evaluating OpenShift as part of the preview and acknowledge we are working on improvements.
That said, due to issue #87, it will be necessary to also tell people to ignore the RHEL based builder image and use the CentOS based image instead. They would need to do this explicitly, or if openshift/origin#6671 has been fixed in a way to allow project overrides for default S2I builders, which I don't really know if it was even though marked as closed, would be to provide a JSON definition for an image stream which maps python image stream in local project to the CentOS based builder.
So I am going to work on that basis. I am also going to start creating separate issues for all the other problems I have found and changes that would suggest.
As to backward compatibility, part of the problem is where a feature which the builder currently provides is arguably a bad feature and will cause problems and in worst case corruption of a users database. I would argue that a certain feature should be removed and having an environment variable to optionally disable the feature isn't really a solution as likely would be too late at that point as damage would be done. If the stance is that all existing functionality must be preserved, then makes it hard to remove stuff which was a mistake to add.

#87 should be fixed in time, at a minimum it's already fixed for the python33 image.
#6671 is indeed fixed so you can provide your own image in your project, or at least get warned you have multiple matches (at which point you can specify which match you want in a more specific way)


How do I customize all images address not just mysqld?

k8s clusters in intranet

@comeonyang43
The controller provides a option to replace images. This allows you to customize images, not just mysqld, by utilizing this option.

Flags:
...
      --agent-image string                The image of moco-agent sidecar container
      --backup-image string               The image of moco-backup container
      --fluent-bit-image string           The image of fluent-bit sidecar container
      --mysqld-exporter-image string      The image of mysqld_exporter sidecar container

https://cybozu-go.github.io/moco/moco-controller.html

Questions answered.


Will this still work when Authorization header is deprecated on TravisCI?

https://docs.travis-ci.com/user/notifications/#Authorization-for-Webhooks-(Deprecated)

Note: The Authorization header value described here is deprecated and will be discontinued on November 1, 2016

From quickly glancing at the current code, it seems like you do rely on this deprecated method to handle authorization, and it will fail after November 1. https://github.com/wizeline/travieso/blob/c74e689/travieso/core.py#L25
I was interested to try to integrate travieso in https://github.com/venuu/jsonapi-authorization/pull/34 but now I'm no longer sure that it would work much longer.

Does it still works for you?

Btw Travis has Python example with new pubkey system.

I don't remember whether it worked or not. Due to here being no comments, I didn't want to put more effort in debugging this further.

Not sure if this is relevent, but I've just set up an instance and each POST to /notifications is resulting in a 403, so I suspect not.


[Windows] Strip (*) from All Files filter name on Windows 10 and older.

Probably fixes https://github.com/godotengine/godot/issues/99596 (not tested).

Tested and works as intended:

I wrote a comment in the linked issue, which mentions that Windows 10 automatically appends the extensions list to the description, unless it (loosely) matches what's in the description text already.
So changing the description suffix to (*.*) for Windows would also work.

Superseded by #99644.


Why do you use java.time.Instant?

I would suggest to use java.util.Date instead of java.time.Instant in DateAudit.java because some libraries like Olingo JPA does not support java.time.Instant

I think this article should sum up why java.util.date is deprecated.
As for the compatibility with Olingo API, I'm not sure why it would not be compatible? A java.time.Instant can be converted to a java.util.date

I tried to use a converter even but it was not run automatically as claimed in this tutorial:
https://www.adam-bien.com/roller/abien/entry/new_java_8_date_and
At the moment I have no clew why the JPA does not support java.time.Instant, hence I have changed the manually to java.util.date.

Article about JPA does not support Instant:
https://github.com/eclipse-ee4j/jpa-api/issues/63
https://stackoverflow.com/questions/49309076/why-jpa-does-not-support-java-time-instant


feat: global env

~ global environments
https://github.com/user-attachments/assets/2cd2b8af-cec0-4b6a-b9d4-8515035805bb

Excellent feature and is very demanded. Nice work!

Thanks a lot @lohxt1 , much appreciated!!! One question though: where are the global environment (.bru?) files stored? I created a new one but can't find the file

Thanks a lot @lohxt1 , much appreciated!!! One question though: where are the global environment (.bru?) files stored? I created a new one but can't find the file

I was looking too. Found it (on macOS at least) in ~/Library/Application Support/bruno/global-environments.json

Thanks @paulrudy. I think it would make more sense to be able to save it in a different place, like at the root of all collections for example.

Thanks @paulrudy. I think it would make more sense to be able to save it in a different place, like at the root of all collections for example.

I agree, and I'd prefer it to be in the same format as the local environments, to allow easy import (copy/paste) from local to global, and back.

@lohxt1 I assume you are also planning to enable it in the bruno CLI and be able to run the collection with this global environment
bru run folder --env ../Global

Will it soon be possible to configure the storage location of the global environments?

Hi. If I have a global environment called 'user' like:

Is it then possible to access the global variables at collection level? Like:

Usecase: ONLY set user/pwd in a global variable and then use it in all collections


CodeSigning variables

Following the documents, I need to assign some secrets for signing my code.
"KeyVaultCertificateUrlSecretName": "KeyVaultCertificateUrl",
"KeyVaultCertificatePasswordSecretName": "KeyVaultCertificatePassword",
"KeyVaultClientIdSecretName": "KeyVaultClientId",
Well, I always used azuresigntool.exe for signing. and, I used the following structure:
azuresigntool sign -kvt $(TennantID) -kvu $(SigningVaultURL)  -kvc $(SigningCertname)  -kvi $(SigningClientid) -kvs $(SigningClientSecret) -tr $(URLTimeStampServer)  -td sha256 $(FileName)
I can figure out
KeyVaultCertificateUrl = SigningVaultURL
KeyVaultClientId = SigningClientid
but, what about the  KeyVaultCertificatePassword?
We do have several apps, can I create my secrets globaly, or should I use the repository?

Dmitry Katson wrote a blog post about code signing with AL-Go https://katson.com/code-signing-in-2024/

If you are using the legacy signing mode (you have a pfx and a pfx password), then you need to create two secrets
codeSignCertificateUrl
codeSignCertificatePassword
The first containing a direct download URL to your Certificate and the second would be the password.
The KeyVault settings you are looking at has nothing to do with code signing - they are for your container and/or dev environment to have keyvault access.

Many thanks - all fixed :-)


Fix crash issue under multi threading

Under multi-threading, NSMutableDictionary modifying is not safe and requires locking.
At OC language, released variables using -> will cause a crash.

Thank you for your contribution, this looks nice!


[Image cropper] Buttons with too small touch areas

On the image cropper, the two bottom buttons have two small touch areas. Each should take 50% of the screen's width.

You are talking about the touch area of the two buttons, Such that touch events would trigger their respective actions of the buttons or The buttons itself should take 50% of screen width each?

@g123k You are talking about the touch area of the two buttons, Such that touch events would trigger their respective actions of the buttons or The buttons itself should take 50% of screen width each?

I can look into this!!

Ok, I also assign you this issue

@g123k Giving each button a 50% of touch area, May result any accidental rotate or Okay button events if wasn't intended in first place, Instead of that I think we can make buttons itself somewhat bigger, What say?

Yes, they should also be bigger in height

@omkarChend1kar Probably in collision with #3332 - as we need to add a button that will visually cause confusion, we need to change the UI altogether.

@g123k @omkarChend1kar Closing this issue as we now have a different layout:

Feel free to open a new issue about the new layout if relevant.


docs(README): add link to ngx-formly

What
This is just an update to the current README.
Why
A lot of people may come by here in search of an Angular (2+) version of it. I think it's worth pointing to ngx-formly which is a very powerful and viable alternative :smiley:
Checklist:

[x] Follows the commit message conventions
[x] Is rebased with master
[x] Is only one (maybe two) commits

//cc @aitboudad

Codecov Report

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

@@           Coverage Diff           @@
##           master     #770   +/-   ##
=======================================
  Coverage   95.93%   95.93%
=======================================
  Files          17       17
  Lines        1181     1181
=======================================
  Hits         1133     1133
  Misses         48       48

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 88db401...c3409e7. Read the comment docs.

:+1:

can't merge this one

Ya I know, it was just to inform you, given you're the main maintainer of ngx-formly :)


[rambox/rambox-pro] Package Name/Version Change issue

Recently the package rambox-pro.json got renamed to rambox.json - removing the Community Edition from the repository entirely.
2cad5465b609aa65042fea6fbef1aecf733f6b22
I'm not sure why this was done: The pro and community editions offer very different requirements - notably that the Pro version requires an account with Rambox to work.
Should this be reverted? Or should we create a new package rambox-ce.json for Rambox Community Edition?

Tagging @niheaven as the original committer.

can you make a PR for rambox-ce?

Rambox CE was moved to Versions bucket following its deprecation.

Okay, good to know - still a bit unexpected that scoop decided to change which edition was installed for those of us already using the Community Edition, though.

Maybe scoop will be added a new feature of smooth migration, but its priority will be very low.


how to do bulk insert for query with subquery

hello.  I have a question on how I can perform a bulk insert that doesn't have a single insert query written in the format in the official doc:
insert into foo (a, b, c) values (d, e, f)
but instead follows the following format
insert into a (b, c) values (?, (select d from e where f = ? and g = ? and h = ?)', [i, j, k, l])
cheers.

From your code snippet I would rewrite it as:
INSERT INTO a
SELECT ? AS b, d AS c
  FROM e
  WHERE f = ? and g = ? and h = ?;


added doctrine orm batcher to implement less memory intensive providers

Do you have some insights on the memory/CPU consumption this saves actually?


Handle 0x prefix str for Address

Currently, Address type can use from_str to build the instance, for example.
let charman_address = Address::from_str("8663DBF0cC68AaF37fC8BA262F2df4c666a41993")?;

The API just fit and easily for the developer using web3.js before.
And there is a similar another API in Rust crate web3.
let charman_address = Address::from_str("0x8663DBF0cC68AaF37fC8BA262F2df4c666a41993")?;

So it is good to make this the 0x prefix input also work in sewup, such that developer can use this much easier.

I can take this issue! Can you assign this for me?


MergeSort.cpp

I have written a program of merge sort in c++ language.

Hello,
My PR was marked as ineligible yesterday. Can you please accept my PR so that it counts. Thanks in advance.

check #1429 please


Prompt continually being cleared

[x] I've read the CONTRIBUTING guidelines

steps
In the SBT shell, run test:compile interleaved with ctrl-L (to clear console) a few times.
problem
Eventually SBT gets into a state where it keep clearing the current line.
I'll see the root>  prompt appear and then disappear. If I type anything I briefly see the character appear and then disappear again.
expectation
The SBT prompt, and chars I type should remain on the screen.
notes
sbt version: 1.3.0-RC1

@japgolly Thanks for the report. Could you share more on your environment to help reproduce it on our end plz? For instance which os and terminal program are you using?

Ah yes, of course :)
I'm on a mac - osx 10.12.6, just using the built in Terminal app.
I'm also using zsh 5.7.1 (x86_64-apple-darwin16.7.0)
Java is:
> java -version
java version "1.8.0_172"
Java(TM) SE Runtime Environment (build 1.8.0_172-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.172-b11, mixed mode)

If there's anything else useful that I didn't think of, let me know.

On Terminal, I tend to use ⌘K (Clear to Start). It seems like there's ^⌘L (Clear Screen), which might be close to what you're talking about. Either way, I wasn't able to get to the problem state.

Not it's not a terminal command, ctrl-L is a readline or jline supported
command, isn't it? Are you saying you tried ctrl-L and it didn't work? If
so maybe it's shell settings.
Also I'm not exactly sure if the screen clearing is relevant cos I saw a
Reddit comment that somebody else is experiencing this same issue. We
should probably reach out and ask them for more info too. I'd be surprised
if they were also clearing the screen like I was :)
On Sat., 18 May 2019, 7:26 am eugene yokota<EMAIL_ADDRESS>wrote:

On Terminal, I tend to use ⌘K (Clear to Start). It seems like there's ^⌘L
(Clear Screen), which might be close to what you're talking about. Either
way, I wasn't able to get to the problem state.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sbt/sbt/issues/4694?email_source=notifications&email_token=AABRRN32B7GUBAN7MX6QD3DPV4PIHA5CNFSM4HNRNK22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVV43HI#issuecomment-493604253,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABRRNZB655LPMQLIYGZTGDPV4PIHANCNFSM4HNRNK2Q
.

Ah I just visited Reddit to ask the other user if they could add more info to this ticket but I see you've already been there :)

The super shell implementation has been updated since 1.3.0-RC1. Does this problem with Ctrl-L still  happen with 1.3.2?

I've been using 1.3.2 for about a week now and I haven't seen this issue pop up again. I guess it's fixed :) Thanks! I'll close now


[BUG] Can't connect to LNDHub in Firefox; works fine in Chrome

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
In Firefox, when setting up Alby anew, it reports it cannot connect to local LAN instance of LNDHub (details below). I get one of two error messages. First, most common is Connection failed. Is your LNDHub URI correct? API error (http://lndhub.local:3000): . Secondarily I have seen : Error: API error (http://lndhub.local:3000):  (yes, there is a blank space after the final colon in both cases)
However, it works fine in Chrome using the same connection string.
lndhub://<useridpart>:<token/pass-part>@http://lndhub.local:3000
Logs (bland):
Jan 30 05:00:19 lndhub node[597371]: 2024-01-30T05:00:19.301Z : info: [/auth] : ["cba21908-a33b-4c0f-9ac4-cbea8b5d65fd"]
Jan 30 05:00:19 lndhub node[597371]: cba21908-a33b-4c0f-9ac4-cbea8b5d65fd <IP_ADDRESS> - - [30/Jan/2024:05:00:19 +0000] "POST /auth?type=auth HTTP/1.1" 200 118 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:122.0) Gecko/20100101 Firefox/122.0"
Jan 30 05:00:19 lndhub node[597371]: 2024-01-30T05:00:19.312Z : info: [/getinfo] : ["0ae0fa88-bf4e-432c-a6fc-2892844a5733"]
Jan 30 05:00:19 lndhub node[597371]: 0ae0fa88-bf4e-432c-a6fc-2892844a5733 <IP_ADDRESS> - - [30/Jan/2024:05:00:19 +0000] "GET /getinfo HTTP/1.1" 200 1833 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:122.0) Gecko/20100101 Firefox/122.0"

Screenshots [optional]

Steps To Reproduce
Run LNDHub on LAN; hostname lndhub.local served by mDNS. serve directly on port 3000; no TLS
Set up new wallet in BlueWallet. Copy connection string (lndhub://...)
Load fresh instance of Alby in Firefox
Set password to get through
Select LNDHub
Paste connection string.
Fails with above error(s) in Firefox;  Works fine in Chrome
Expected behavior
I expect it to connect correctly; or report an actionable error (rather than a blank string)
Alby information

Alby 3.6.0

Device information

OS: MacOS M1 Sonoma
Firefox (latest)

Additional context
No response
Are you working on this?
No

@dienummer Can you verify that you can open http://lndhub.local:3000 in Firefox?
Since it's exactly the same codebase for the firefox / chrome extension there could potentially also be a problem with resolving this local domain?
Can you maybe follow the steps described in here and try to see if you find the root cause of this problem?
https://guides.getalby.com/user-guide/v/alby-account-and-browser-extension/alby-browser-extension/debugging/mozilla-firefox
Would be interesting to inspect both the network and console tab.


Support dynamic property names

Bug Report
Summary
I am trying to call the TS.stringify on a lhr object and getting the following error key cannot contain .``. The lighthouse report contains an object with a property called icuMessagePaths with keys that contains a . ex:  'lighthouse-core/audits/is-on-https.js | title': [Array]. Is it possible that this will be handled in the future to allow parsing symbols in the key property names?
const data = {
  requestedUrl: 'https://jeffmendez.com/about',
  finalUrl: 'https://jeffmendez.com/about/',
  lighthouseVersion: '9.6.2',
  userAgent: 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/102.0.5005.115 Safari/537.36',
  fetchTime: '2022-07-15T12:19:17.077Z',
  environment: {
    networkUserAgent: 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4695.0 Safari/537.36 Chrome-Lighthouse',
    hostUserAgent: 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/102.0.5005.115 Safari/537.36',
    benchmarkIndex: 1246.5
  },
  runWarnings: [
    'The page may not be loading as expected because your test URL (https://jeffmendez.com/about) was redirected to https://jeffmendez.com/about/. Try testing the second URL directly.'
  ],
  timing: { total: 12460 },
  i18n: {
    icuMessagePaths: {
      'lighthouse-core/audits/is-on-https.js | title': [Array],
      'lighthouse-core/audits/is-on-https.js | description': [Array],
      'lighthouse-core/audits/viewport.js | title': [Array],
      'lighthouse-core/audits/viewport.js | description': [Array],
      'lighthouse-core/lib/i18n/i18n.js | firstContentfulPaintMetric': [Array],
      'lighthouse-core/audits/metrics/first-contentful-paint.js | description': [Array],
      'lighthouse-core/lib/i18n/i18n.js | seconds': [Array],
      'lighthouse-core/lib/i18n/i18n.js | largestContentfulPaintMetric': [Array],
      'lighthouse-core/audits/metrics/largest-contentful-paint.js | description': [Array],
      'lighthouse-core/lib/i18n/i18n.js | firstMeaningfulPaintMetric': [Array],
      'lighthouse-core/audits/metrics/first-meaningful-paint.js | description': [Array],
      'lighthouse-core/lib/i18n/i18n.js | speedIndexMetric': [Array],
      'lighthouse-core/audits/metrics/speed-index.js | description': [Array],
      'lighthouse-core/lib/i18n/i18n.js | totalBlockingTimeMetric': [Array],
      'lighthouse-core/audits/metrics/total-blocking-time.js | description': [Array],
      'lighthouse-core/lib/i18n/i18n.js | ms': [Array],
      'lighthouse-core/lib/i18n/i18n.js | maxPotentialFIDMetric': [Array],
      'lighthouse-core/audits/metrics/max-potential-fid.js | description': [Array],
      'lighthouse-core/lib/i18n/i18n.js | cumulativeLayoutShiftMetric': [Array],
      }
  }
}

The schema defs
/**
 * @license Copyright 2018 The Lighthouse Authors. All Rights Reserved.
 * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
 * Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
 */

import { Result as AuditResult } from "./audit-result";
import { ConfigSettings } from "./settings";

/**
 * The full output of a Lighthouse run.
 */
interface Result {
  /** Gather mode used to collect artifacts for this result. */
  gatherMode: Result.GatherMode;
  /** The URL that Lighthouse initially navigated to. Will be `undefined` in timespan/snapshot. */
  requestedUrl?: string;
  /** The post-redirects URL that Lighthouse loaded. */
  finalUrl: string;
  /** The ISO-8601 timestamp of when the results were generated. */
  fetchTime: string;
  /** The version of Lighthouse with which these results were generated. */
  lighthouseVersion: string;
  /** An object containing the results of the audits, keyed by the audits' `id` identifier. */
  audits: Record<string, AuditResult>;
  /** The top-level categories, their overall scores, and member audits. */
  categories: Record<string, Result.Category>;
  /** Descriptions of the groups referenced by CategoryMembers. */
  categoryGroups?: Record<string, Result.ReportGroup>;

  /** The config settings used for these results. */
  configSettings: ConfigSettings;
  /** List of top-level warnings for this Lighthouse run. */
  runWarnings: string[];
  /** A top-level error message that, if present, indicates a serious enough problem that this Lighthouse result may need to be discarded. */
  runtimeError?: { code: string; message: string };
  /** The User-Agent string of the browser used run Lighthouse for these results. */
  userAgent: string;
  /** Information about the environment in which Lighthouse was run. */
  environment: Result.Environment;
  /** Execution timings for the Lighthouse run */
  timing: Result.Timing;
  /** Strings for the report and the record of all formatted string locations in the LHR and their corresponding source values. */
  i18n: {
    rendererFormattedStrings: Record<string, string>;
    /** Optional because LR has many old LHRs that return nothing for this property. */
    icuMessagePaths?: Result.IcuMessagePaths;
  };
  /** An array containing the result of all stack packs. */
  stackPacks?: Result.StackPack[];
}

// Result namespace
declare module Result {
  interface Environment {
    /** The user agent string of the version of Chrome used. */
    hostUserAgent: string;
    /** The user agent string that was sent over the network. */
    networkUserAgent: string;
    /** The benchmark index number that indicates rough device class. */
    benchmarkIndex: number;
    /** Many benchmark indexes. */
    benchmarkIndexes?: number[];
    /** The version of libraries with which these results were generated. Ex: axe-core. */
    credits?: Record<string, string | undefined>;
  }

  interface Timing {
    entries: MeasureEntry[];
    total: number;
  }

  interface MeasureEntry {
    // From PerformanceEntry
    readonly duration: number;
    readonly entryType: string;
    readonly name: string;
    readonly startTime: number;
    /** Whether timing entry was collected during artifact gathering. */
    gather?: boolean;
  }

  interface Category {
    /** The string identifier of the category. */
    id: string;
    /** The human-friendly name of the category */
    title: string;
    /** A more detailed description of the category and its importance. */
    description?: string;
    /** A description for the manual audits in the category. */
    manualDescription?: string;
    /** The overall score of the category, the weighted average of all its audits. */
    score: number | null;
    /** An array of references to all the audit members of this category. */
    auditRefs: AuditRef[];
  }

  interface AuditRef {
    /** Matches the `id` of an Audit.Result. */
    id: string;
    /** The weight of the audit's score in the overall category score. */
    weight: number;
    /** Optional grouping within the category. Matches the key of a Result.Group. */
    group?: string;
    /** The conventional acronym for the audit/metric. */
    acronym?: string;
    /** Any audit IDs closely relevant to this one. */
    relevantAudits?: string[];
  }

  interface ReportGroup {
    /** The title of the display group. */
    title: string;
    /** A brief description of the purpose of the display group. */
    description?: string;
  }

  /**
   * A pack of secondary audit descriptions to be used when a page uses a
   * specific technology stack, giving stack-specific advice for some of
   * Lighthouse's audits.
   */
  interface StackPack {
    /** The unique string ID for this stack pack. */
    id: string;
    /** The title of the stack pack, to be displayed in the report. */
    title: string;
    /** A base64 data url to be used as the stack pack's icon. */
    iconDataURL: string;
    /** A set of descriptions for some of Lighthouse's audits, keyed by audit `id`. */
    descriptions: Record<string, string>;
  }

  /**
   * Info about an `LH.IcuMessage` value that was localized to a string when
   * included in the LHR. Value is either a
   *  - path (`_.set()` style) into the original object where the message was replaced
   *  - those paths and a set of values that were inserted into the localized strings.
   */
  type IcuMessagePath =
    | string
    | { path: string; values: Record<string, string | number> };

  /**
   * A representation of `LH.IcuMessage`s that were in an object (e.g. `LH.Result`)
   * and have been replaced by localized strings. `LH.Result.IcuMessagePaths` provides a
   * mapping that can be used to change the locale of the object again.
   * Keyed by ids from the locale message json files, values are information on
   * how to replace the string if needed.
   */
  interface IcuMessagePaths {
    [i18nId: string]: IcuMessagePath[];
  }

  /** Gather mode used to collect artifacts. */
  type GatherMode = "navigation" | "timespan" | "snapshot";
}

export default Result;

My ts config:
{
  "compilerOptions": {
    "outDir": "dist",
    "target": "es6",
    "module": "commonjs",
    "lib": ["es6"],
    "sourceMap": true,
    "allowJs": true,
    "moduleResolution": "node",
    "noEmit": false,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "suppressImplicitAnyIndexErrors": true,
    "noUnusedLocals": true,
    "allowSyntheticDefaultImports": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "skipLibCheck": true,
    "resolveJsonModule": true,
    "removeComments": true,
    "baseUrl": ".",
    "paths": {
      "@app/*": ["./src/*"]
    },
    "strict": true,
    "plugins": [
      {
        "transform": "typescript-json/lib/transform"
      }
    ]
  },
  "include": ["src", "*.proto"],
  "exclude": ["node_modules"]
}

Error on TSON.stringify(): no transform has been configured. Configure the "tsconfig.json" file following the README.md#setup
Code occuring the bug
import TSON from "typescript-json";

const json = TSON.stringify<Result>(insight);

/* Demonstration code occuring the bug you're reporting */

interface IcuMessagePaths {
    [i18nId: string]: IcuMessagePath[];
}

typescript-json is not supporting dynamic property.
When such dynamic property exists, TSON.stringify() becomes slow like the native JSON.stringify().
Therefore, I'm considering typescript-json should support it or not.
I hope to listen your idea about it.

@samchon that is a very valid point. I was thinking about separating the calls for my use case into two and then stitching the two JSON strings together. For my case it's kinda simple since the last property is the only property that has . in the name. I wonder if we could have a feature that checks for this or and maybe reduces the speed a bit on parsing.
When the transformer finds a property that contains a " single-quote or double-quote allow opting into the token handling.

https://github.com/samchon/typescript-json/blob/master/test/structures/ObjectLiteralProperty.ts
As you can see from the below structure, typescript-json is testing such special-charactered property name. Therefore, the dot word (.) is not important. The failure comes only by the dynamic property name. If such dynamic property has a significant type, it's possible to boosting JSON string conversion speed. However, the speed would not such dramatic like static property names.
However, such dynamic property names are formal TypeScript spec. Therefore, I need to support it. Supporting such dynamic property names would be done at next week, perhaps. Thanks for suggestion and I'll try out for the update.

Also, such dynamic properties would be supported even in the runtime type checkers.
I've assigned this issue as v3.2 update.

@samchon Love that!! Agreed on the points, in theory it should still be faster than using JSON.stringify until it gets to those properties ( making it a better choice to use still ).
Ps: off topic, I like your github profile description!

Sorry for late implementation. I will try this again in this Saturday.

Now, those functions support dynamic properties. Only stringify() is left.
Current version is 3.3.3 and the next version supporting stringify() would be 3.3.4.

application()
assertEquals()
assertType()
equals()
is()
`validate()
validateEquals()

@j-mendez You've waited for a long time.
Since v3.3.6 update, typescript-json has fully supported the dynamic properties

@samchon thank you for the version tag for the change and work done for this!!


How to mask certain fields?

Hi what would be the best approach if these are the requirements

Be able to mask any fields that start with email, phone (preferably with wildcard)
Depending on what field it is mask it differently

Basically I have several rest api and I want to modify the json response before its hitting the clients. So I think i need to add a filter that uses this library. But can this lib handle the requirements?

In the current version (1.x), the only thing you can do include/exclude fields.
In version 2, you will able to modify the response, including masking fields.

Thanks for the answer. Btw do u know any othet library that offer sum similar for java?

Thanks btw for an awesome lib.

You're welcome.  I do not know of another library that does field masking.

Ok may i ask what you think would be the best approach to solve that?


[IR] Implementation of QoS Features

Implementation of QoS features in the rclcpp package.

Whoops commenting on the wrong review, I'll close this one to reduce confusion

The other review (https://github.com/aws-robotics/rclcpp/pull/2) is qos-min vs. master, but maybe it should have been qos-min vs qos_reviewed.

Changed the base on qos-min


Design and Fabrication of an Environmental Testing Chamber for Simulating Space-like Vacuum and Thermal Conditions

Authors

Thomas Tarazevits, @venku122

Abstract
This proposal describes a project to build a controlled thermal vacuum chamber, called and Environmental Test Chamber or ETC, as well as associated test automation software, and documentation describing its safe operation and use by other SPEX teams.
Comments for Reviewers (optional)
Timeline is preliminary and sources/references of similar projects need to be added.
A rough system outline should be included as well.

@runphilrun @msglazer Check out the updates. See the reference section for an example project with a full BoM.


Enter a new debug scope for every let binding.

This fixes an ambiguity (that leads to a crash further down the pipeline) when
compiling optional unwrap bindings that bind the same variable name.
rdar://73490741

@swift-ci test

Question for the SILGen experts: is SwitchEnumBuilder the best place to enter the scope?

@swift-ci test

@swift-ci nominate
Explanation: Change SILGen to enter a new lexical scope for each let binding in an if let foo = foo, foo = foo, ... expression to avoid ambiguity in the variable debug info that would lead to a crash.
Scope: Debug Info.
Radar/SR Issue: rdar://73490741 / https://bugs.swift.org/browse/SR-14787
Risk: Low.
Reward: Fixes a common crash.
Testing: New regression test.
Reviewer: Slava Pestov


[BUG] Error after "dart run msix:create" command

Version: 3.16.7
After command bellow, occurs the next error message:
Building package executable... (2.9s)
Built msix:create.
Unhandled exception:
type 'String' is not a subtype of type 'int' of 'index'
#0      Configuration.getConfigValues (package:msix/src/configuration.dart:170:54)

#1      Msix._initConfig (package:msix/msix.dart:97:5)

#2      Msix.create (package:msix/msix.dart:58:5)

#3      main (file:///C:/Users/andre.gusmao/AppData/Local/Pub/Cache/hosted/pub.dev/msix-3.16.7/bin/create.dart:4:3)

Can you try again with version 3.16.8 and see if you still get this issue?


Write a FastAPI Example

I think we should get away from completely contrived examples, and start building examples using popular Python libraries. This should benefit sundew twofold:

We can test functionality against real-world coding examples and smooth out the things that don't work or are unnecessarily hard.
It's built in documentation for users who are interested in using sundew in their code with these libraries.

I'll be making several of these issues for the most popular python libraries. I'm also open to suggestions for other libraries if anyone wants to open an issue!

Added a FastAPI Example with #30 but I'm not marking this as complete yet, as I'm not entirely happy with where we are at. It seems that almost universally devs prefer to test the endpoint directly (I know I do), but the main value add with sundew is that tests know what functions they are running. Unfortunately in the case of FastAPI (and I imagine others API frameworks) I'm not yet able to map a function to an endpoint after the fact without writing alot of FastAPI-specific logic. So I either need to decide that testing endpoints is a different functionality for sundew that behaves differently than regular function tests, or I need to figure out a way to map endpoint requests to function calls.
Planning to leave this open until I solve that dilemma


Failed to Compile

We are getting a failed build error.
Here is the error message:

variable issue solved


syncthing: 0.14.21 -> 0.14.23

Motivation for this change
Upstream recommended update. Works here.
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Builds on elementary OS 0.4 (based on Ubuntu 16.04).
nix-shell -p nox --run "nox-review pr 22552"


Add release to aws S3

/kind feature
Add release to AWS S3

 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.

 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.


Log Analytics workspace resource id

Was looking at this policy
https://github.com/Azure/CanadaPubSecALZ/blob/main/policy/custom/definitions/policyset/LogAnalytics.bicep#L27
'Select Log Analytics workspace from dropdown list. If this workspace is outside of the scope of the assignment you must manually grant 'Log Analytics Contributor' permissions (or similar) to the policy assignment's principal ID.'
It asks for a LAW be selected as part of the configuration of the policy. In our deployment this value isnt set.

Is this a manual step ?

This appears to be a UX issue in Azure Portal.  You will see the assigned value for Log Analytics workspace id (this is the full resource id) on the assignment overview screen.

Closing, nothing to modify in the automation.


redisgraph do not support foreach and i need use "case when then" with foreach.What do you suggest instead?

@ebrahimtorabi can you please share a sample query you would like to use foreach with?

thanks.
i need create or merge conditionally
for example:
FOREACH(ignoreMe IN CASE WHEN 'y' THEN [1] ELSE [] END |
MERGE (u)-[r2:STAGE {startdate:20141225, enddate:'99999999', status:'InProgress'}]->(b2 {fork:'fail'})
)
FOREACH(ignoreMe IN CASE WHEN NOT 'y' THEN [1] ELSE [] END |
MERGE (u)-[r2:STAGE {startdate:20141225, enddate:'99999999', status:'InProgress'}]->(b2)
)


jitsi with jetty on ubuntu 16.04

For my jitsi meet on my private platform I would like to use the electron utils for changing the welcome page and eventually remote controlling jitsi. The webserver is jetty.
Thanks for advice.
Best regards
Toni

You can use the jitsi-meet-electron app with your deployment.
Use the community forum for questions and problems before opening issues, thanks.


news item: next pombe talks

Here is the announcement. Pls add news item in the usual format:
Join us Wednesday, May 18th for the first pombeTalks session of the year at 08:00 San Francisco / 11:00 New York / 16:00 London / 17:00 Paris / 20:30 Delhi / 23:00 Beijing / 00:00 Tokyo
We’ll have two exciting talks lined-up to start this season:
Jennifer Porat, Bayfield Lab, York University
“The methyl phosphate capping enzyme Bmc1/Bin3 is a stable component of the fission yeast telomerase holoenzyme”
Ingrid Billault-Chaumartin, Martin Lab, UNIL
“Fus1, the fusion focus formin”

That's done for the morning.

If you need to tweak the text, it's here: https://github.com/pombase/website/blob/master/src/docs/news.PomBase/2022-05-05-pombetalks-may18-2022.md

If you need to tweak the text, it's here: https://github.com/pombase/website/blob/master/src/docs/news.PomBase/2022-05-05-pombetalks-may18-2022.md


The CJS build of Vite's Node API is deprecated

Describe the bug
Hello, I migrate all my project to pure ESM, vite part works fine without any warn about CJS but when I try to launch histoire, I have this warn :

The CJS build of Vite's Node API is deprecated. See https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details.

How to avoid this warn and force histoire to use ESM only ?
Reproduction

launch histoire with vite 5.x+

System Info
System:
    OS: macOS 13.6.4
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 4.44 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
    pnpm: 7.30.0 - /usr/local/bin/pnpm
  Browsers:
    Chrome: 121.0.6167.139
    Edge: 121.0.2277.98
    Safari: 17.3
  npmPackages:
    @histoire/controls: 0.17.9 => 0.17.9
    @histoire/plugin-vue: 0.17.9 => 0.17.9
    @vitejs/plugin-vue: 5.0.3 => 5.0.3
    histoire: 0.17.9 => 0.17.9
    vite: 5.0.12 => 5.0.12

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

1, I'm using nuxt and can no longer build stories getting an error while using vue-imask:

Error [ERR_UNSUPPORTED_DIR_IMPORT]: Directory import '/Users/amonjafarbay/projects/gospace/ui/base-app/node_modules/vue-imask/esm' is not supported resolving ES modules imported from /Users/amonjafarbay/projects/gospace/ui/base-app/node_modules/vite-node/dist/client.mjs

This does not take away the warning, but if your project can't build - I added this line to my histoire.config.ts to get histoire to collect stories:
export default defineConfig({
  plugins: [HstVue()],
  viteNodeInlineDeps: [/vue-imask/],  👈
  tree: {

This does not take away the warning, but if your project can't build - I added this line to my histoire.config.ts to get histoire to collect stories:
export default defineConfig({
  plugins: [HstVue()],
  viteNodeInlineDeps: [/vue-imask/],  👈
  tree: {

🙏  thanks @JannieT  - after updating histoire and adding the viteNodeinlineDeps property the imask error is cleared but build now fails with this error any ideas?
TypeError [ERR_PACKAGE_IMPORT_NOT_DEFINED]: Package import specifier "#build/nuxt.config.mjs" is not defined in package /Users/amonjafarbay/projects/gospace/ui/base-app/node_modules/nuxt/package.json imported from /Users/amonjafarbay/projects/gospace/ui/base-app/node_modules/nuxt/dist/app/nuxt.js

I'm facing the exact same issue as @idlethumbs.
Added viteNodeInlineDeps: ['@turf/boolean-clockwise'] to solve ERR_UNSUPPORTED_DIR_IMPORT and now I see ERR_PACKAGE_IMPORT_NOT_DEFINED.
Very frustrating kinda error

Same here


Jbaker/min date back btn

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes: #136
Summary:
Fix calculation for when to show the prev month button so that it works correctly on first load with minValue and a value set.
Type of change:
Please delete options that are not relevant.

[ ] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Generate JSDoc Documentation

Fully comment the code using JSDoc syntax and publish the generated documentation to http://comcast.github.io/Surf-N-Perf/
I'd like to publish it similar to how Polymer does:
Example Source: https://github.com/Polymer/core-ajax/blob/master/core-ajax.html
Example Output: https://www.polymer-project.org/docs/elements/core-elements.html#core-ajax
I haven't looked at how they're doing that yet.
Note that I originally planned to use NDoc syntax and only commented some of the code, so the existing comments will have to be modified appropriately.

I'm reviewing Pull Request #36 which addresses this. Hope to have my proposed changes to that available today. Pull Request #37 will need to be merged in before that as well since that details with the gh-pages branch

OK I finally figured out what we need to modify in #36 to get this ready to merge. Here's the rundown:

.gitignore - remove the 2 "jaguarjs" lines and under the ## Documentation cache and generated files: section add /_build/
.travis.yml - change it to match the .travis.yml at https://github.com/JohnRiv/Surf-N-Perf/blob/1f245a3cf40183bfc62cb50afa97801c991e1a89/.travis.yml

Also add the deploy.sh file from https://github.com/JohnRiv/Surf-N-Perf/blob/7dd5bb22689e35641c3c65848778484fcbde74cd/deploy.sh to the root so the new travis after_success command will actually execute

Gruntfile.js - remove 'jsdoc' from the watch & default tasks & update the jsdoc options to be the following:

{
  destination: './_build/docs',
  configure: './jsdoc-conf.json',
  template: './node_modules/jaguarjs-jsdoc',
  private: false
}

add the jsdoc-conf.json file from https://github.com/JohnRiv/Surf-N-Perf/blob/7dd5bb22689e35641c3c65848778484fcbde74cd/jsdoc-conf.json
delete the entire jaguarjs-jsdoc directory
add the JSDoc files we need as dependencies by running these commands from the root of your project:

$ npm install jaguarjs-jsdoc --save-dev
$ npm install grunt-jsdoc --save-dev

^ that should add a couple lines to your package.json's list of devDependencies

Before submitting the pull request, run these commands to make sure the documentation generates:
$ grunt jsdoc
$ open _build/docs/index.html

That should open up a webpage with documentation for Surf-N-Perf
You should now have a much smaller Pull Request, containing only edits to:

.gitignore
.travis.yml
Gruntfile.js
deploy.sh [new file]
jsdoc-conf.json [new file]
package.json

If that's the case, send it over! ;-)

Pull Request #44 took care of this


load postgres_scanner in R Windows crash R

Hello.
I tried to use the DuckDB postgres_scanner extension on R and RStudio for Windows (x86_64) and it crashed when I do the "LOAD postgres_scanner;".  "R Session Aborted" message. I tried both the binary version of DuckDB (0.5.1) and the source version, built and installed with install.packages("duckdb", type = "source"). Both methods failed.
On Linux, Debian bookworm, same machine, it worked correctly. Built the DuckDB R package from source in RStudio.
I used ok this extension with CLI client and DBeaver in Windows and Linux.
Thanks very much for your work. Duckdb is becoming one of my favorite library for data work.

Hmm, one small attempt, then this is out of my league!
Could you try wrapping postgres_scanner in single quotes in your load statement?
It still shouldn't crash as is though!

Same behavior. Crashed R
dbExecute(con,"LOAD 'postgres_scanner';")
and
dbExecute(con,"LOAD postgres_scanner;")

Same thing for me.
I opened https://github.com/duckdb/duckdb/discussions/4980.
In th hope that I could help.

I think this is likely fixed now - this is an old issue related to extension loading on Windows in R


Update changelog

Related to https://github.com/aws/aws-parallelcluster-node/pull/422
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closed as duplicate of: https://github.com/aws/aws-parallelcluster/pull/4203


Order PDFs

A few oscar sites here on GitHub, and likely even more not on GitHub, have Order PDF generation.
It seems like it should be a part of the orders app, or an installable app maintained by @django-oscar org.
GitHub implementations:

https://github.com/embedded1/django-package-forwarding/blob/8c3286e9a7da8f4ae0401a81c8037585b3bb7ba6/apps/dashboard/orders/views.py (reportlab)
https://github.com/dbca-wa/ledger/blob/249367358f12c2f8b5b4cda690deec3fee24ecd2/ledger/payments/views.py and https://github.com/dbca-wa/disturbance/blob/2824561b504dc9841e397d915463d4540f245abb/disturbance/components/das_payments/views.py and others in the same org (reportlab)
https://github.com/UnruledLab/MebelJazz/search?q=pdf (pdfkit)
https://github.com/sladinji/blousebrothers/blob/461de3ba011c0aaed3f0014136c4497b6890d086/blousebrothers/dashboard/orders/views.py (django_weasyprint)
https://github.com/leonardo-modules/leonardo-store/blob/8779600542e20197628d1ff8feb2d230c1c7c698/leonardo_store/payments/invoice/views.py (xhtml2pdf)

If you ask me, I would implement django-weasyprint out of the box. It is simple, efficient and with a free and permissive license for commercial projects. Reportlab is probably more powerful and/or versatile, but I don't think it contributes more to this task than django-weasypdf.
As django-weasyprint already comes with a CBV and a Mixin the integration should be trivial.

ping @sladinji , perhaps you'd like to contribute your PDF implementation?

I feel like https://github.com/django-oscar/django-oscar-invoices might already be addressing this use case - and if it isn't then extending it to do so might be a good approach.

Ping @samitnuk and @sasha0 .
For starters, I've created https://github.com/django-oscar/django-oscar-invoices/pull/30 so it is able to be used with modern Django+Oscar environments.

Pong.
Thanks, we'll review soon.

I feel like https://github.com/django-oscar/django-oscar-invoices might already be addressing this use case - and if it isn't then extending it to do so might be a good approach.

Our intention here is that. Use oscar-invoices and extend it with weasyprint. But now we are too busy to make it an installable plugin :\

I'll be glad you use it ! I did it some years ago but I don't think there's
any update to do.
As you can see on the link you provided (
https://github.com/sladinji/blousebrothers/blob/461de3ba011c0aaed3f0014136c4497b6890d086/blousebrothers/dashboard/orders/views.py
)
you can share the same template between html and pdf rendering.html. And
the only skills required to custom pdf invoices are html and css coding.
Unfortunately, I won't be able to contribute more than that those days...
On Wed, Feb 10, 2021 at 8:19 PM John Vandenberg<EMAIL_ADDRESS>wrote:

ping @sladinji https://github.com/sladinji , perhaps you'd like to
contribute your PDF implementation?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/django-oscar/django-oscar/issues/3639#issuecomment-776953435,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7KR72EVNQDOWA6PHHFHXTS6LL45ANCNFSM4XHPBPPA
.

As pointed out, we have https://github.com/django-oscar/django-oscar-invoices/ which looks like it addresses the use case. So I'm closing this issue for now.


Feature requests and use cases

Here are some features and use cases that @cscherrer brought up on Slack.

Inlining data in a model
But not forcing that - data can also be external
Online modeling, e.g. Kalman filtering
Pyro-style approach, passing model and guide
Refactoring, e.g. change to non-centered parameterization
Composability - models as distributions, etc
Easily switch between prior, posterior, likelihood
Posterior predictive checks

Tracking this thread too :) Will add some comments later.

Tracking this thread too :) Will add some comments later.

I'd forgotten we had talked about inlining. I guess you may all have seen it by now, but I presented some progress on that idea here:
https://informativeprior.com/blog/2021/01-25-symbolic-simplification/

I'd forgotten we had talked about inlining. I guess you may all have seen it by now, but I presented some progress on that idea here:
https://informativeprior.com/blog/2021/01-25-symbolic-simplification/


App Crashing with onPointerEvent import on Android

I am running a project in which I implemented pointer events to detect enter and exit pointer events. My interest is in detecting this behavior on platforms that support these input types generally. There is the import import androidx.compose.ui.input.pointer.onPointerEvent , the project compiles on iOS without a problem and on Desktop but fails to compile on Android with the error, Unresolved reference: onPinterEvent.
The project is compiled with Android Studio Giraffe | 2022.3.1 Canary 11

Hi @ngengesenior,
onPinterEvent != onPointerEvent, so first of all please check typos in Android source set.
If problem is still there, please follow instruction in issue template and

"If the bug is Android-only, report it in the Jetpack Compose tracker"
Provide required data according the template.

Regarding androidx.compose.ui.input.pointer.onPointerEvent - this function is not available on Android. Currently we're discussing how to sync a few things including this with Google upstream repo (or maybe move it to separate library).
We'll keep you updated. For now changing tag to "enhancement"

I made a typo while typing. The error is actually real. Here is a screenshot when I attempt building on Android

Actually, here is an IDE error as well. IDE should highlight onPointerEvent with the red color, because it is not availalable in commonMain

For me it does not

It does not highlight on the IDE for me as well

neverthless , it does to me I mean it highlights on the IDE

Can I use onPointerEvent for the android not for the desktop ?

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


dart2js: Better code for ??=

The generated code for a typical lazy-initialized field ...
  Data _data;
  Data get data => _data ??= _compute();

... is a bit verbose:
    get$data: function() {
      var t1 = this._data;
      if (t1 == null) {
        t1 = this._compute$0();
        this._data = t1;
      }
      return t1;
    }

What would it take to compile this to the following?
    get$data: function() {
      return this._data || (this._data = this.compute$());
    }

[ ] Let HFieldSet be used in an expression context to allow chaining.

[ ] (Side task) Use chaining for adjacent field assignments like this.next = this.prev = null.

[ ] Chain the field setter into the phi node:  t1 = this._data = this._compute$0()

    get$data: function() {
      var t1 = this._data;
      if (t1 == null)
        t1 = this._data = this._compute$0();
      return t1;
    }

At this point SsaConditionMerger should recognize that a conditional (?:) can generated
    get$data: function() {
      var t1 = this._data;
      return t1 == null ? this._data = this._compute$0() : t1;
    },

[ ] ToBoolean optimization: determine when t1 == null can be replaced with !t1. (We need to take care here, since == null is a faster operation that !t1 or if(t1).)

    get$data: function() {
      var t1 = this._data;
      return !t1 ? this._data = this._compute$0() : t1;
    },

[ ] Do additional checks in SsaConditionMerger that t1 is used exactly twice in this pattern, register t1 as generate-at-use, and mark the HIf node to generate the || code.

[ ] Methods like get data are frequently inlined (e.g. called from one place, and generally more attractive if the inlined code it compact). Ensure code quality at inlined sites is good.

Regarding general field assignment chaining, the middle one is clearly an improvement. Is the last one a bridge too far?
        last = this._last;
        cell._previous = last;
        last._next = cell;
        this._last = cell;
 -->
        last = this._last;
        cell._previous = last;
        this._last = last._next = cell;
-->
        this._last = (cell._previous = this._last)._next = cell;

If you worry about !t1 being slower than t1 == null, consider swapping the branches and just do t1 ? t1 : this._data = this._computer$0().
(That is, if the test of a two-branch condition is a negation, remove the negation and swap the branches. That should be safe since ! use the same falsy-logic as the condition).
That migth also be easier for a JS-level optimizier to recongize as equivalent to t1 || this._data = this._compute$0().

@lrhn
A JS-level peephole optimizer would work, but since dart2js does variable allocation ahead of generating JavaScript, doing so  would leave a temporary that is assigned once and used once, i.e.
var t1 = this._data;
return t1 || (this._data = this._compute$());

which is quite a bit larger than
return this._data || (this._data = this._compute$());

I'm not worried about !t1 ? ... vs  t1 ? ..., they are pretty much the same - both incur a full ToBoolean conversion, which has 9 tests to cover the full glory of JavaScript truthiness. What we are giving up is that t1 == null can be done with 3 tests (null, undefined, and undetectable objects) vs the full 9 tests.


Rework modal dialogs

Current modal implementation appears quirky in current browser/AT combinations, and has some known shortcomings:

while the modal uses focus trapping and aria-modal, this is still not supported correctly in all browser/ATs. for instance, Firefox/JAWS still allows navigating/reading through the underlying page; similarly, iOS VO ignores it, see https://github.com/twbs/bootstrap/issues/26770
when the dialog is opened and focus is moved, NVDA does not announce that we're in a modal - see https://github.com/twbs/bootstrap/issues/33715
JAWS seems to have a weird issue with the initially set focus - once the modal is opened, the next tab and reading key press all go to the last button in the dialog, rather than starting at the top of the modal

We should take closer inspiration from https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/dialog.html (but that misses the fix for iOS/VO, so would still not be sufficient to copy the approach from there). as mentioned previously (though can't quite find where, worth also looking at approaches like https://github.com/KittyGiraudel/a11y-dialog, and possibly https://github.com/WICG/inert

You mentioned it there: https://github.com/twbs/bootstrap/issues/28481#issuecomment-757491401.
Not sure if @RyanBerliner continued to work on this, since its seems he was waiting for some acknowledgement on his concept.
Personally I'm totally in for making modals more accessible and I can have a look into it, if that is desired (but I'm also totally fine to leave it up to Ryan as he already started).

About the mentioned shortcomings - I'm not sure if there is currently a go-to solution that would work in most situations, as I'm not that deep into that a11y topic. But if it can be build, we could do so too IMO.
According to https://github.com/twbs/bootstrap/issues/26770#issuecomment-796925908 adding role="dialog" and aria-modal="true" seem to work for iOS/VO which is somewhat contradictionary to the claims in your first point.
About #33715 if the problem could be solved by focusing an element in the modal rather than the container (which is more similiar to the w3 example you linked), my guess we should adapt for this then. Just not sure about modals without inputs/focusable elements tho.
I'd say to put the weird behavior in JAWS at the end of our list and rather to focus first on those ATs that work in a similar fashion.

I just spent some hours reading discussions about this inert proposal and the conclusion seem to be that, after it eventually got dropped, it has been readded to the specs as there is a necessity for smth like that.
I'm just not sure how inert would help us here, that would make it reasonable to add it as a polyfill. Also from what I can tell we tend to dislike to add polyfills to our code.
Please correct me if I'm wrong, but we try to trap the focus into our modal but isn't inert rather doing the opposite as it's purpose is to "remove" a (sub)tree from being accessible e.g. receiving input/focus (beside adding a similiar behavior like aria-hidden="true")?
Wouldn't that mean we have to enforce some certain dom structure or to move a modal into a certain spot in the dom? How is that different than using aria-hidden for that matter? Marking a subtree as non-inert within a tree that is marked already as inert seems not to be in the scope of the current proposal.
As I see it the polyfill currently has to rely on aria-hidden combined with pointer-events and user-select (beside using some JS for handling the focus logic). This behavior also satisfies concerns that got raised, that there are already things in place that partly overlap with the behavior that would be expected from inert.

Please correct me if I'm wrong, but we try to trap the focus into our modal but isn't inert rather doing the opposite as it's purpose is to "remove" a (sub)tree from being accessible e.g. receiving input/focus (beside adding a similiar behavior like aria-hidden="true")?

yes, the modal itself remains as is, but the underlying page needs to be inert ... so that it's hidden from AT, and its child elements aren't focusable at all.

As I see it the polyfill currently has to rely on aria-hidden combined with pointer-events and user-select (beside using some JS for handling the focus logic). This behavior also satisfies concerns that got raised, that there are already things in place that partly overlap with the behavior that would be expected from inert.

yes, inert would be the shorthand that makes it much easier in future to do things that currently you have to do as an author with JS (adding tabindex="-1" to everything, adding the pointer-events and user-select, adding aria-hidden="true", etc). the hope is that once natively supported in browser, it'll also be much more performant (particularly if it can avoid the current "walk the entire DOM and sprinkle in tabindex everywhere) approach)

Yes, I do have a proof of concept changing the current modal focus trap to a more standard, forwards and backwards focus trap. However I haven't continued any work as I was awaiting some confirmation that a change like this would still be welcome in v5. Happy to help again if needed.
That said this doesn't necessarily solve any of the screen reader navigation issues. It seems that aria-modal="true" is the most supported method at this time to trap screen reader navigation. Relative to other methods it's easy to implement and does accomplish its intended goal for quite a lot of users (and bootstrap already uses it in their docs).
Unfortunately the reality is that inert just isn't supported - so I'd think any alternative method or inert polyfill is going to have the do the "walk the dom" dance that you're speaking of avoiding @patrickhlauke. Not only that but they'd need to "walk the dom, and watch the dom" in case things change.
I think a great first, forward moving step would be to fix the tab navigation focus trap. Then some of the other assistive tech bugs may be solvable with tweaks to initial focus and/or the timing of the initial focus.

It seems that aria-modal="true" is the most supported method at this time to trap screen reader navigation

not supported in VO/iOS (though apparently VO/macOS does respect it)

@RyanBerliner can't speak for the whole team but IMO it makes sense to continue your work if you're still up for it. As for me, an improved focus trap behavior totally makes sense alone in terms of UX. If we can use this as a foundation to improve the situation for a11y as well, it's even better.

Gonna x-ref https://github.com/twbs/bootstrap/issues/33715 here. Maybe it makes sense to fix that in one rush 😊

Sounds like there's enough interest in improving these dialogs (modal & off canvas bootstrap components) - I should be able to push a PR this week so you all can start testing something tangible.

With the recent release of Safari 15.4 all major browser now support the <dialog> element natively:

https://caniuse.com/dialog
https://developer.apple.com/documentation/safari-release-notes/safari-15_4-release-notes
https://webkit.org/blog/12445/new-webkit-features-in-safari-15-4/

should push for using native <dialog> element instead!

@jimmywarting @mkurz of course, once the feature has been available for a sufficiently long time and is supported not just in the latest versions of Safari on MacOS/iOS, we will (though likely, as it will be a breaking change, only in a future version of Bootstrap, not a dot release) https://getbootstrap.com/docs/5.2/getting-started/browsers-devices/

as mentioned in #37000 switching - for v6 - to using <dialog> will resolve a lot of related issues here caused by screen reader shortcomings and our overly complex legacy implementation.

Proposal
Reference Feature Request: #39191
Implement native <dialog> element in Bootstrap for enhanced accessibility and usability.
Proposal to Implement Native <dialog> Element in Bootstrap
MDN - The dialog element
Introduction
The native HTML <dialog> element has recently gained full browser support. It offers built-in accessibility and usability features, making it an ideal choice for modal dialogs. This proposal suggests that Bootstrap should adopt the <dialog> element to enhance its dialog components.
Benefits

Accessibility: Implicit aria-modal="true" for modal dialogs.
Usability: Built-in .showModal() and .show() methods for rendering.
Standardization: Native HTML element, no need for custom implementations.

Example Code
<dialog id="myDialog">

Dialog content here

  <button id="closeBtn">Close</button>
</dialog>

Built-in Methods for <dialog>
.show()

Opens the dialog as a non-modal.

const dialog = document.getElementById("myDialog");
dialog.show();

.showModal()

Opens the dialog as a modal, making all other elements inert.

const dialog = document.getElementById("myDialog");
dialog.showModal();

.close([returnValue])

Closes the dialog and optionally sets a return value.

const dialog = document.getElementById("myDialog");
dialog.close("User clicked OK");

Conclusion
Incorporating these built-in methods will enhance Bootstrap's dialog components in terms of usability and accessibility.

<dialog>: The Dialog element
Reference Feature Request: #39191
Implement native <dialog> element in Bootstrap for enhanced accessibility and usability.
Proposal to Implement Native <dialog> Element in Bootstrap
MDN - The dialog element
Introduction
The native HTML <dialog> element has recently gained full browser support. It offers built-in accessibility and usability features, making it an ideal choice for modal dialogs. This proposal suggests that Bootstrap should adopt the <dialog> element to enhance its dialog components.
Benefits

Accessibility: Implicit aria-modal="true" for modal dialogs.
Usability: Built-in .showModal() and .show() methods for rendering.
Standardization: Native HTML element, no need for custom implementations.

Example Code
<dialog id="myDialog">

Dialog content here

  <button id="closeBtn">Close</button>
</dialog>

Built-in Methods for <dialog>
.show()

Opens the dialog as a non-modal.

const dialog = document.getElementById("myDialog");
dialog.show();

.showModal()

Opens the dialog as a modal, making all other elements inert.

const dialog = document.getElementById("myDialog");
dialog.showModal();

.close([returnValue])

Closes the dialog and optionally sets a return value.

const dialog = document.getElementById("myDialog");
dialog.close("User clicked OK");

Conclusion
Incorporating these built-in methods will enhance Bootstrap's dialog components in terms of usability and accessibility.

<dialog>: The Dialog element
Reference Feature Request: #39191
Implement native <dialog> element in Bootstrap for enhanced accessibility and usability.
Proposal to Implement Native <dialog> Element in Bootstrap
MDN - The dialog element
Introduction
The native HTML <dialog> element has recently gained full browser support. It offers built-in accessibility and usability features, making it an ideal choice for modal dialogs. This proposal suggests that Bootstrap should adopt the <dialog> element to enhance its dialog components.
Benefits

Accessibility: Implicit aria-modal="true" for modal dialogs.
Usability: Built-in .showModal() and .show() methods for rendering.
Standardization: Native HTML element, no need for custom implementations.

Example Code
<dialog id="myDialog">

Dialog content here

  <button id="closeBtn">Close</button>
</dialog>

Built-in Methods for <dialog>
.show()

Opens the dialog as a non-modal.

const dialog = document.getElementById("myDialog");
dialog.show();

.showModal()

Opens the dialog as a modal, making all other elements inert.

const dialog = document.getElementById("myDialog");
dialog.showModal();

.close([returnValue])

Closes the dialog and optionally sets a return value.

const dialog = document.getElementById("myDialog");
dialog.close("User clicked OK");

Conclusion
Incorporating these built-in methods will enhance Bootstrap's dialog components in terms of usability and accessibility.
A playground Example
JsFiddle Example
Example using existing CSS Implementation
<!doctype html>

    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <title>Bootstrap Dialog demo</title>
    <link<EMAIL_ADDRESS>rel="stylesheet" integrity="sha384-T3c6CoIi6uLrA9TneNEoa7RxnatzjcDSCmG1MXxSR1GAsXEV/Dwwykc2MPK8M2HN" crossorigin="anonymous">

<dialog>: The Dialog element

          <button id="launchDialog" type="button" class="btn btn-primary">
            Launch demo dialog
          </button>

      <dialog id="exampleDialog">

Dialog title

            <button id="closeDialog" type="button" class="btn-close" aria-label="Close"></button>

            Text in the dialog body...

            <button type="button" class="btn btn-secondary" id="closeDialogBtn">Close</button>
            <button type="button" class="btn btn-primary" id="saveDialogBtn">Save changes</button>

      </dialog>

as before, need to be cogniscent of https://getbootstrap.com/docs/5.3/getting-started/browsers-devices/

HTML <dialog> element - Browser Compatibility
For Reference

as before, need to be cogniscent of https://getbootstrap.com/docs/5.3/getting-started/browsers-devices/

I think browser native modal is for bootstrap 6 and should definitely be considered for including.

For <dialog>, be mindful of the fact that in Firefox ::backdrop cannot be animated: https://bugzilla.mozilla.org/show_bug.cgi?id=1725177.


Provide a way to mark methods as mutating

As an example the sort method on Array mutates the array.  It would be nice if we had a way of marking it as such.  We could then use this to disallow the use of mutating methods on non-mutable references.  Then we wouldn't need to have separate Readonly* versions of types like TypeScript does.  We could still generate these types from the Crochet type, but stripping out all of the mutating methods.
interface Array<T> {
    map: (cb: (item: T, index: number, arr: T[]) => U) => U[];
    length: number;
    mut sort(): T[];
    mut [key: number]: T;
}

// [1, 2, 3] is a tuple
// TODO: create a definition for a Tuple interface
let mut_arr: mut number[] = [1, 2, 3];
let arr: number[] = mut_arr; // the `arr` reference points to `mut_arr`, but the `sort` method isn't available and the indexer loses its `mut` modifier.

Classes, once we add support for them, can also define methods that are mutating in the following way:
class Foo {
   a: number;  // can only be set in the constructor
   // the `mut` keyword in this context designates the property as "mutable"
   mut b: number;  // can only be set in the constructor and mutating methods
   constructor(a, b) {
      this.a = a;
      this.b = b;
   }
   // if `bar` is never mutated inside of `baz()` we can have a lint rule that flags this
   baz(bar: mut Bar) {
      // no access to mutating methods on setting properties on `this` is allowed in this context
      // calling mutating methods on other values is allowed, e.g.
      bar.mutatingMethodCall();
      const values: mut number[] = [Math.random(), Math.random()];
      values.sort();  // allowed b/c we aren't mutating
   }
   // the `mut` keyword is this context designates the method as "mutating"
   mut qux() {
      // setting properties on `this` is allowed
      // calling mutating methods on `this` is allowed
      this.b = Math.random();
      this.frobozz(); // allowed b/c qux() is marked as mutating
   }
   mut frobozz() { ... }
}

Classes can conform to an interface, but also define an interface themselves.

Done by #416, #428, and #434.


AeroSpace placing non-active workspace windows in the wrong bottom corner

First off, thanks so much for this great tool. It's my first time using a TWM and I can already feel the productivity boost!
I have the following monitor arrangement which I believe meets the guidelines here:

The leftmost is my built-in MBP retina display, and the other 2 are 1080p
The issue is that non-active workspace windows on my center monitor are being placed in the bottom right corner and are showing up along the bottom of the right monitor. If I'm not mistaken, they should be placed in the bottom left corner of the center monitor, since it hangs below the left monitor there.
Screenshot from right monitor (the WezTerm window is in a workspace on my middle monitor, but I switched off that workspace):

My config is basically the default with a couple of tweaked keybinds and on-window-detected callbacks, so I don't believe it's a configuration issue.
So my main question is "why is AeroSpace choosing the bottom right corner when the bottom left is the better choice?", and/or is there a way to force it to use a particular corner?
Please let me know if any other information would be helpful to provide!
Checklist

[x] I've tried the following queries to search for duplicates (please don't forget to search in closed issues too):

https://github.com/nikitabobko/AeroSpace/issues?q=is:issue+corner
https://github.com/nikitabobko/AeroSpace/issues?q=is:issue+monitor

[x] I've read the documentation https://nikitabobko.github.io/AeroSpace/guide & https://nikitabobko.github.io/AeroSpace/commands & https://nikitabobko.github.io/AeroSpace/config-examples
[x] I've tried searching for the following queries in the documentation:

"monitor" (I believe my arrangement meets the guidelines)

aerospace CLI client version: 0.14.1-Beta 5861e85b65cb7dc914a0a68027c56e2bc90510fd
AeroSpace.app server version: 0.14.1-Beta 5861e85b65cb7dc914a0a68027c56e2bc90510fd

Right now, AeroSpace checks that no other monitor is presented in the bottom 10% of the monitor height. 10% is a very rough number and the algorithm can definetely be improved
The point being, is that AeroSpace thinks that both of your corners are bad corners, your temporary workaround is to lift the left monitor up

Aha, very good to know. Thanks!

So, further observation: I have rearranged like so...

And my window appears across the bottom of my left monitor.

I have tried with "Displays have separate spaces" on and off, both have the same result.
Any suggestions? Thanks.

Can you please try the following custom build? AeroSpace-v0.0.0-SNAPSHOT.zip
It's built from 8cd4ddc07211b4aa6306a6e207798d10810e17f8 so alternatively you can also build from sources

That fixes the followup issue!

0.14.2 is released to address the followup issue
The original issue is yet to be fixed

Wonderful, very much appreciated!

@nikitabobko

I seem to maybe have the same issue, I have my monitors arranged like so, monitor 1 has free space on left and monitor 2 has freespace on right. But I am seeing window flashing in bottom left corner of monitor 1

I was able to fix by moving right monitor up a little, although not ideal

I'm currently trying to understand how aerospace handles screen boundaries. Similarly, I encountered the same issue with a different resolution. As a workaround, rearranging the monitors as suggested here works.
1920x1800
1800x1169 (Bult-in Display)
1920s1080


Bump compiler plugin

@tadgh please revert this change (at least the root pom part) - we're still supporting Java 8


Cannot install

Maybe this is just me but no matter what I do, I can't install the latest version of this package. npm install obviously won't work because the latest version is not published, but doing npm install with references to git repo usually works like a charm. I must've spent a couple hours on this and am completely baffled. Any ideas?

@hermanc-fda it should work... You may need to navigate into the install directory and run npm build in there to build it? What are you adding to your package.json?

package.json I had to add the github repo, otherwise it downloads an older version. But it has some install errors so I had to manually clone to node_modules, go inside there, then npm build and run the cli 😅  Whatever works ;) I'll close since I hacked it to work for myself! Thanks

BTW it's great when it works, thanks.


computed_field not present in model_json_schema

Initial Checks

[X] I confirm that I'm using Pydantic V2 installed directly from the main branch, or equivalent

Description
When declaring a computed field (@computed_field), while the value is returned by model_dump_json, it is not present in the model_json_schema()
Every field that is part of the JSON response should be in the schema, as this could make validators that check for attributes not in the schema fail.
Example Code
import pydantic

class StudentGrades(pydantic.BaseModel):
    english: int
    history: int
    geography: int

    @computed_field()
    @property
    def grade(self) -> float:
        return (self.english + self.history + self.geography)/ 3

student = StudentGrades(english=80, geography=70, history=60)
print(student.model_dump_json())
# '{"english":80,"history":60,"geography":70,"grade":70.0}'
print(student.model_json_schema())
# {'properties': {'english': {'title': 'English', 'type': 'integer'}, 'history': {'title': 'History', 'type': 'integer'}, 'geography': {'title': 'Geography', 'type': 'integer'}}, 'required': ['english', 'history', 'geography'], 'title': 'StudentGrades', 'type': 'object'}

Python, Pydantic & OS Version
pydantic version: 2.0.2
        pydantic-core version: 2.1.2 release build profile
                 install path: /Users/allangalarza/PycharmProjects/detect-api/venv/lib/python3.9/site-packages/pydantic
               python version: 3.9.16 (main, Dec  7 2022, 10:06:04)  [Clang 14.0.0 (clang-14<IP_ADDRESS>)]
                     platform: macOS-13.4.1-arm64-arm-64bit
     optional deps. installed: ['typing-extensions']

Selected Assignee: @dmontagu

Thanks @Galarzaa90 for this issue 🙏
As computed_field is included in serialization, you can see them in the serialization json schema.
print(student.model_json_schema(mode='serialization'))
{'properties': {'english': {'title': 'English', 'type': 'integer'}, 'history': {'title': 'History', 'type': 'integer'}, 'geography': {'title': 'Geography', 'type': 'integer'}, 'grade': {'readOnly': True, 'title': 'Grade', 'type': 'number'}}, 'required': ['english', 'history', 'geography', 'grade'], 'title': 'StudentGrades', 'type': 'object'}

Ooh, that is correct. Thanks!
I guess next step is opening a fastapi issue so computed fields are included in Open API schemas.

I am closing this issue. Please reopen this issue or create another one if you have problem.


WSLg (weston) crash with nautilus in X11 mode

Environment
Your Distribution version:20.04
Your WSLg version: <IP_ADDRESS>
Steps to reproduce
First, copy simple text to Windows system clipboard in Windows side
Second, launch WSLg, then
$ export GDK_BACKEND=x11
$ nautilus &
Then weston compositor crash and restart.
"read error from data source: Bad address" is logged in weston.log
Crash is due to freeing invalid address.
libc.so.6!__GI___libc_free(void * mem) (\build\glibc-eX1tMB\glibc-2.31\malloc\malloc.c:3102)
libwayland-client.so.0!wl_array_release(struct wl_array * array) (...\wayland\src\wayland-util.c:104)
xwayland.so!weston_wm_read_data_source(int fd, uint32_t mask, void * data) (...\weston\xwayland\selection.c:413)
libwayland-server.so.0!wl_event_loop_dispatch(struct wl_event_loop * loop, int timeout) (...\wayland\src\event-loop.c:1055)
libwayland-server.so.0!wl_display_run(struct wl_display * display) (...\wayland\src\wayland-server.c:1351)
libexec_weston.so.0!wet_main(int argc, char ** argv) (...\weston\compositor\main.c:3429)
main(int argc, char ** argv) (...\weston\compositor\executable.c:33)

The fix for this should address https://github.com/microsoft/wslg/issues/2 as well.

Not 100% sure if it is the same issue?! When I launch Nautilus, it starts with 8 icons (Desktop. Documents, Downloads, Music, Pictures, Public, Templates, Videos) but in the shell there is this error: Called "net usershare info" but it failed: Failed to execute child process "net" (No such file or directory) and the "Ubuntu on Community Preview" shell crashes (does not return to :~$).
Also could not copy the error message from that shell into Edge browser running on Ubuntu, so I had to type above text in here, while Copy & Paste into the shell itself still works and also Copy & Paste within the Write section here in Edge.
Finally have to close and reopen the  "Ubuntu on Community Preview" shell to be able to start other Ubuntu apps.


Improvements to memref descriptor

Improves the memref descriptor and adds the ability to import PNG images using libpng.
Usage example:
PNGImage img(path/to/image);
intptr_t sizes[3] = {3, 4, 2};
MemRef<float,3> x(img, sizes);

from my side LGTM, whether remain the stride interface or not, probably it's not important now, I will modify my other PR along this PR.

From my side one question, If I want to init data as NHWC, how can I state my format?
Or whether remain the (size + right stride) interface, if so, I don't have to change my code. Probably it's not important now, I can modify my other PR along this PR if your provide set format interface.

You can permute the dimensions and create your memref using :
intptr_t sizes[4] = {n, h, w, c};
x MemRef<float,4> (sizes);

or you can keep the size in the nchw format and use the transpose function to permute the dimensions of the memref :
intptr_t sizes[4] = {n, c, h, w};
x MemRef<float,4>(sizes).transpose({0, 2, 3, 1});

I think it's better to get rid of the strides. By doing so we won't have to worry about the strides anymore and If there is is an issue in the future we will only need to fix the container.

From my side one question, If I want to init data as NHWC, how can I state my format?
Or whether remain the (size + right stride) interface, if so, I don't have to change my code. Probably it's not important now, I can modify my other PR along this PR if your provide set format interface.

You can permute the dimensions and create your memref using :
intptr_t sizes[4] = {n, h, w, c};
x MemRef<float,4> (sizes);

intptr_t sizes[4] = {n, c, h, w};
x MemRef<float,4>(sizes).transpose({0, 2, 3, 1});

I think it's better to get rid of the strides.

So it's by default NHWC ? I think the comment in the code are NCHW


raidboss/oopsy: add Another Aloalo Island (work in progress)

Sorry for the awkwardness again, but I'm doing this one blind too (so please don't let me know where this is wrong). I'll put my own notes here in this PR if that's helpful for anybody else.

Ok, this should be ready to go. I feel pretty confident in it and I think there's nothing strat-specific, so I might merge it now and then can adjust for any feedback after.


ngrok alternative

can ghostunnel be used as a ngrok alternative?
thx

Depends on what you're trying to do? It's a tunnel that you can use for forwarding traffic, but it's not introspectable in the same way that ngrok is.

I'm mostly trying to expose local service behind NAT, similar to ssh -R. Is there any specific configuration to enable it?

There's examples for how to set up a tunnel in our README:
https://github.com/square/ghostunnel/blob/master/README.md

Note that Ghostunnel doesn't do anything special with regards to NAT hole punching or UPNP, so if you're behind NAT you will need to set up port forwarding on your router yourself to a static port that you intend to have the tunnel listen on.


Windows Defender is throwing a fit over Install-Decentraland.exe

The signature on Install-Decentraland.exe, made 3 weeks ago, has already expired:

File checksums should be included for those who want to formally triple-check.

Fixed with https://github.com/decentraland/explorer-desktop-launcher/pull/208.


Raiden E Eye should be affected by hitlag

I think it's reasonable to assume that since Raiden E's burst dmg buff gets extended by hitlag, the eye dmg part should as well. How exactly the dmg icd works still needs to be investigated.
relevant: https://docs.google.com/spreadsheets/d/1Xxp_SywwuzFEbhHlemNXQdR3o9Jctf1-gRjRF9aolMs/edit#gid=0

related to #658

As discussed here, leaving the issue for now until a later date when I have time to investigate

After more investigation, I've come to the conclusion that the eye status and the eye dmg buff status should both be hitlag extendable. The dmg icd should not be hitlag extendable. This means I'm removing the eye status in favor of just reusing the eye dmg buff status. The eye procs only if the eye dmg buff status is active on the character whose dmg is proccing the eye.


More customisable folding

Context
Golang code can be quite verbose, a standard function call is written as:
result, err := someFunction()
if err != nil {
    return nil, fmt.Errorf("some context: %v", err)
}

Finding acceptable ways to shorten the above is an ongoing, high profile discussion in the Golang community, and I think there's an opportunity for editors like VSCode to help provide a solution.
The current folding behaviour in VSCode could collapse the above to:
result, err := someFunction()
if err != nil {...

Which is not helpful, as it hides the action taken in the case of an error.
What I'd love to see
Somehow enable the folding behaviour to display:
result, err := someFunction()
...check... fmt.Errorf("some context: %v", err) ...

Where check is some name that represents what folding behaviour has been applied.
The code could then be read as if it were written with some kind of macro (which golang deliberately does not support), but the actual file text would be standard Golang code.
I'd also like the above to somehow be folded automatically. For example, once I have the folding configured, a new file I open has these regions folded by default, and once I type a new block and save the file, the new block is folded as well.
(This suggestion is similar to #70794, but I'm looking for a solution to a very well defined use case, with an entire language community that would love to see this implemented. #31966 and #69078 are also related)

sounds like a dup of https://github.com/microsoft/vscode/issues/70794


add log before prefetching hadoop token

Since hadoopSecurityManager.prefetchToken is synchronized, one thread might block all others from entering into this method when it's stuck fetching token. So it's important to prompt users about which step the job is stuck with.

Pull Request Test Coverage Report for Build 4039

2 of 3 (66.67%)  changed or added relevant lines in 1 file are covered.
22 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.04%) to 36.021%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

az-hadoop-jobtype-plugin/src/main/java/azkaban/jobtype/HadoopJobUtils.java
2
3
66.67%

Files with Coverage Reduction
New Missed Lines
%

az-hadoop-jobtype-plugin/src/main/java/azkaban/jobtype/HadoopJobUtils.java
1
37.17%

azkaban-exec-server/src/main/java/azkaban/execapp/event/JobCallbackRequestMaker.java
21
56.25%

Totals

Change from base Build 4036:
-0.04%

Covered Lines:
10488

Relevant Lines:
29116

💛  - Coveralls


Add support for AES128_CM_HMAC_SHA1_32

Adding support for SRTP_AES128_CM_HMAC_SHA1_32 as described in RFC 5764.
This necessitated some light refactoring of how srtpCiphers interact
with ProtectionProfile: the handling of this profile is identical
to handling for SRTP_AES128_CM_HMAC_SHA1_80, but the parameters are
different. This change assigns a profile to a cipher when it is created,
and all profile parameters are delegated to the profile (rather than the
previous setup, which split the values of profile parameters across the
profile and the cipher). This change also splits authTagLen into
rtpAuthTagLen and rtcpAuthTagLen, since they can have different
values depending on the profile in use.

@adamroach All the changes look great to me!
I added TestProtectionProfileAes128CmHmacSha1_32 and it isn't passing. I am debugging now, see anything obvious?
--- FAIL: TestProtectionProfileAes128CmHmacSha1_32 (0.00s)
    srtp_test.go:527: failed to verify auth tag
FAIL
exit status 1
FAIL    github.com/pion/srtp/v2 0.006s

@adamroach got it! authKeyLen was missing an entry.
Should we make this a default cipher suite in pion/webrtc after dtls.SRTP_AEAD_AES_128_GCM, dtls.SRTP_AES128_CM_HMAC_SHA1_80 or do you just want this available but not on by default?

Sorry, I missed your messages yesterday. :)
Thanks for the merge and fixes! In terms of a default cipersuite for WebRTC, I wouldn't recommend adding this one in. 32-bit auth tags only make sense in some specific situations involving extremely low-bandwith audio codecs, sent over similarly low-bandwidth (or expensive) data links. So it's useful to have in certain non-WebRTC contexts, but I don't see it being useful for WebRTC.