message_fetch: Stop infinite fetch for first unread message id.

Found while migrating message_fetch to Typescript in #30509.
Tested by setting message fetch constants to single digit with some unreads and checking if we are hitting both fetched_substantial_history and found_first_unread.

Merged, thanks @amanagr!


Successfully made ABOUT US page

With about us page , I have added the linking of about us page to index page

@vishanurag Sir i have made the changes

Please also mention your issue no.


Enable / Disable SAML

Hi Ulises,
Is there a way to enable/disable this plugin based on a yml property?
Thank You,
Rajesh

Hi Rajesh, there is no way to do that currently through the plugin itself but fortunately you still have a few other options to accomplish the same. You can for instance do something like this:
@EnableSAMLSSO
@ConditionalOnProperty(name = "property.name", havingValue = "true")
public class SAMLSSOConfiguration {
}

And import that class in the main application class:
@Import(SAMLSSOConfiguration.class)
@SpringBootApplication
public class MyApplication {
    ...
}

The conditional config will basically look for your property and if the property doesn't have the value you want the entire class won't be loaded.
Or, you may choose to disable it this way if you're using ServiceProviderConfigurerAdapter or WebSecurityConfigurerAdapter :
@Configuration
public static class MyServiceProviderConfig extends ServiceProviderConfigurerAdapter {

        @Value("property.name")
        Boolean enableSAML;

        @Override
        public void configure(WebSecurity web) {
            if(!enableSAML) {
                web.ignoring().anyRequest();
            }
        }
}

This last option has the downside that will load all your SAML config regardless of whether you enable it or not, and it will be disable at the URL level only, but if you're looking for using this for testing, it might be totally acceptable.
The first approach will basically avoid loading all the SAML config.

did this work for you buddy?


Sign in URL should not contain /acs

I tried to set up SAML for Sansan, and I found that this tutorial was incorrect about sign-in url.
https://ap.sansan.com/v/saml2/<company name>/acs is should be replaced to https://ap.sansan.com/v/saml2/<company name>

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

The change is updated in the doc now. #please-close


About the Listeners

First of all, your library is AWESOME !!!
But it would be a good idea to make the *Listeners as Interfaces instead of classes :dancer:
See ya! Keep up the good work! I love LibGDX <3

Uhm, which listeners aren't interfaces?

ClickListener for example (I think...)

Look at the implementation of ClickListener, it cannot possibly be an interface.

Well, there should be no reason for it being an interface. Anonymous inner classes works fine, right?

Ye, you are right, they work right, that's what I used.
I guess it's what Darkyenus said, for some reason a ClickListener is forced to be a class. Thank you very much guys !!! <3


Configure rule sets in a safe way

Expected Behavior
The configuration of rule sets should be as explicit and safe as the rule configuration. It should be impossible for the documentation to diverge from the actual implementation.
Current Behavior
The RuleSetProvider may describe configuration properties in the kdoc section. That information is used to generate the rule set documentation as well as the detekt-config-default.yml.
The configured value can be accessed within a rule of that rule set by ruleSetConfig.valueOrDefault("propertyname", false). There is a lot of implicit knowledge here.
Context
#3637 added support for rule configurations via annotation making it impossible to generate a documentation with misspelled configuration options and outdated default values. It would be great to have the same for rule sets.

The configuration of rule sets should be as explicit and safe as the rule configuration. It should be impossible for the documentation to diverge from the actual implementation.

+1 - Also with the rules moving to annotation based configuration, it's better to align rulesets to follow the same paradigm

I'm linking #3816, where some ideas have also been proposed. I'm closing #3816 in favor of this issue in order to avoid the duplicated discussion.

I'm linking #1276, where some ideas have also been proposed. I'm closing #1276 in favor of this issue in order to avoid the duplicated discussion.

There are two different types of configurations provided by ruleset:

Common configurations including "active" and "excludes". These configurations are printed in ConfigProvider while their values are read by ConfigAware and PathFilters respectively.
Rule set specific configurations like "android" and "autoCorrect" fromFormattingProvider. These configurations are printed through parsing KDoc while their values are read directly in FormattingRule and ConfigAware respectively.

The safety is embodied in typo protection: To make sure the key for write (in config) has the same name and value type for key for read. My proposal would be of these two steps:

[ ] Use compile-time constants to represent rule set configurations
[ ] For rule set specific configurations, create an actual Kotlin annotation class to specify the name and type.

There is an absence of finding the corresponding RuleSetProvider given a Rule, and fixing this would require refactoring that is probably beyond the scope of this PR and provides little value in terms of the type safety for rule set configuration. Given that there are only two use cases and we have not seen any new usage in the recent years, I would propose to postpone this until we onboard a third use case.


⚠ Home 主页 has degraded performance

In 02cceb3, Home 主页 (https://www.fangkehou.eu.org) experienced degraded performance:

HTTP code: 520
Response time: 26086 ms

Resolved: Home 主页 performance has improved in a5a16cd after 10 minutes.


⚠ Itaca Gallery has degraded performance

In 355aec0, Itaca Gallery ($SITE_TCGLR) experienced degraded performance:

HTTP code: 200
Response time: 5734 ms

Resolved: Itaca Gallery performance has improved in 4fdd23f after 6 minutes.


Add KubeVirt blog

What this PR does / why we need it:
Adds a new blog post "Gardener Integrates with KubeVirt".
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:
NONE

/cc @g-pavlov

/cc @donistz

/cc @mfranczy


panic: interface conversion: interface {} is string, not map[interface {}]interface {}

Hi,
I try to use postgres exporter with extended.query_path.
I f I start postgres exporter , it appears in prometheus, and work fine.
If would like to use query.yaml I got error, see under.
I dont use docker only single machine. postgres version is 11.
Postgres exporter version:
postgres_exporter v0.4.7 (built with go1.10)
./postgres_exporter --extend.query-path=./program/query.yaml --log.level=debug
INFO[0000] Established new database connection.          source="postgres_exporter.go:1035"
DEBU[0000] Querying Postgres Version                     source="postgres_exporter.go:948"
INFO[0000] Semantic Version Changed: 0.0.0 -> 11.2.0     source="postgres_exporter.go:965"
DEBU[0000] replay_location is being forced to discard due to version incompatibility.  source="postgres_exporter.go:504"
DEBU[0000] procpid is being forced to discard due to version incompatibility.  source="postgres_exporter.go:504"
DEBU[0000] write_location is being forced to discard due to version incompatibility.  source="postgres_exporter.go:504"
DEBU[0000] pg_xlog_location_diff is being forced to discard due to version incompatibility.  source="postgres_exporter.go:504"
DEBU[0000] flush_location is being forced to discard due to version incompatibility.  source="postgres_exporter.go:504"
DEBU[0000] sent_location is being forced to discard due to version incompatibility.  source="postgres_exporter.go:504"
DEBU[0000] New user metric namespace from YAML: pg_stat_user_tables  source="postgres_exporter.go:402"
DEBU[0000] New user metric namespace from YAML: pg_statio_user_tables  source="postgres_exporter.go:402"
DEBU[0000] New user metric namespace from YAML: pg_database  source="postgres_exporter.go:402"
DEBU[0000] New user metric namespace from YAML: description  source="postgres_exporter.go:402"
panic: interface conversion: interface {} is string, not map[interface {}]interface {}
goroutine 19 [running]:
main.addQueries(0xc4201aca00, 0x11ba, 0x13ba, 0xb, 0x2, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
Regards,
Szilvia

Could you try the same with the master branch?

I downloded query.yaml file from the internet, and it has got some unvisible character(s), I changed the yaml file contentents, and now it works.


update titiler

This pr does:

Update titiler and titiler-pgstac version
Update rasterio >=1.3 (and remove pctiler/pctiler/reader_cog.py)

Frontend changes

remove asset_expression (Mosaic and Item)
histogram band names are prefixed with b (e.g b1) (Mosaic and Item) (ref: https://github.com/cogeotiff/rio-tiler/blob/main/docs/src/v4_migration.md#band-names)
expression for STAC have to be in form of {asset}_b{band_name} (e.g red_b1/green_b1) (Mosaic and Item) (ref: https://github.com/cogeotiff/rio-tiler/blob/main/docs/src/v4_migration.md#multibasereader-expressions)
added asset_as_band option to force expression to be in form of {asset} (e.g red/green) (Mosaic and Item)
expression's band should now be delimited with ; (previously , was accepted) (Mosaic and Item)
point output model to include band_names (Item)
added algorithm options

Ref: https://github.com/stac-utils/titiler-pgstac/blob/master/CHANGES.md?plain=1#L55-L63

Due to the breaking expression changes, we're going to wait to evaluate this after the next release (end of Jan).

Thanks @vincentsarago , I'm ready to merge this. Could you resolve the conflict (I can't push to the fork)? The same dependency upgrades have merged after this PR was created.

conflict resolved, I'll let you go ahead an merge


Attempts to use fs (from node) while in browser. Am I missing a step?

I get the following error when attempting to load a tmx file:
pixi-tiledmap.js:12529 Uncaught TypeError: fs.readFile is not a function
at Object.defaultReadFile [as readFile] (pixi-tiledmap.js:12529)
at parseFile (pixi-tiledmap.js:12533)
at resolveTileSet (pixi-tiledmap.js:12480)
at pixi-tiledmap.js:12437
at pendGo (pixi-tiledmap.js:12752)
at Pend.go (pixi-tiledmap.js:12711)
at collectTileSet (pixi-tiledmap.js:12436)
at Object.opentag (pixi-tiledmap.js:11947)
at SAXParser.parser.onopentag (pixi-tiledmap.js:12372)
at emit (pixi-tiledmap.js:13381)
I get similar errors with using the min version, and when using require + browerify or webpack.
My source code looks lilke:
PIXI.loader.add('/images/spritesheet.png', '/images/spritesheet.json')
PIXI.loader.add('mountain.tmx')
PIXI.loader.load(function(loader, resource) {
    var tileMap = new PIXI.extras.TiledMap('mountain.tmx')
    ...

Thanks!

did you try
node: {   fs: 'empty' }
in your webpack config?
Nonetheless this project needs to be updated soon :)

Nonetheless this project needs to be updated soon :)

and done.
It should work now with the recent versions of pixi.js and webpack.
And remember to use node: { fs: 'empty' } in your webpack config.

I also added a working example with webpack under example/ in 1.8.1

It is now working for me using 1.8.1, node: { fs: 'empty' }, and embedding the spritesheet when creating a map (PIXI v4.3.4 and Tiled v1.0.2).
Thanks for your help!


[WIP] Implement cross-validation of time series(a rolling forecast origin)

I made a functionality of cross-validation of time series based on this conversation.
The concept of cross-validation of time series is explained in detail in the following link:

https://robjhyndman.com/hyndsight/tscv/

If this looks good, I will add more tests and implement it in R language as well.
I'm not sure how I name this function and would like to change it through discussion.

Let me know if I should implement the metrics mentioned in https://github.com/facebookincubator/prophet/issues/194 .

@teramonagi Please do! It's a great feature to have!

@Ic3fr0g
I think that we should implement it in a different branch and as a different class because cross-validation and its measure are not the same thing esentially.
How you think about my idea?

Agreed. Would you like me to create a PR ?

This is great, thanks for the PR! A few comments:

I think this would be better as a separate function as opposed to a method of Prophet, and in a separate file. Let's have a file diagnostics.py or something like that, and then this function would be cv(m, ...) where m is a fitted Prophet model.

The current approach for a dataset of length N is to start at N - horizon - periods, and then one observation at a time move forward in the time series, and make a forecast for horizon periods. There are a couple of things here that I think would be better if done slightly differently.

First, it'd be nice to not have to require regular spacing of the time series for this to work. The horizon could be given as a unit of time (5 days, 10 hours, etc.) and then we would construct the future dataframe to hold whatever observations there were in the history within that time window. In the final output we would convert those datetimes to be time deltas from the cutoff (end of the training data). The horizon input instead of being an int could be a string in the form expected by pd.Timedelta. So something like '5 days' or '10 minutes' could be passed directly in.
The second thing is about how we choose those cutoffs. This PR implements what Rob Hyndman recommends which is to use a cutoff at every observation. This is completely reasonable, but at the same time the prediction errors from one cutoff to the next are very correlated: typically adding one observation to the training data will not change the forecast very much. This just means that there is not a whole lot of value to making cutoffs one observation apart, and we can get a pretty-much-as-good estimation of prediction error by spacing out the cutoffs a bit. This of course is desirable because it means fewer models to be trained and so CV is much faster. I'd like this to be the default strategy, with an ability to use cutoffs every day should the user wish. The interface could be something like
cv(m, horizon, periods=10, initial=None)

where initial would be a pd.Timedelta-style string that indicates the minimum amount of time to be used for training (that is, the distance in time from the first observation in the history to the first cutoff). If not provided (None) we could default to something reasonable like 3 horizons. So if t0 is the start of the time series and T the end, the first cutoff would be at the first observation after t0+initial. The last would be at the last observation before T-horizon. And we would uniformly space the remaining periods-2 cutoffs in between those two. If periods is more than the number of observations inside [t0+initial, T-horizon], then we will have a cutoff at each observation as in the current implementation. Thoughts?

Please rebase this on the v0.2 branch, that is where the new features are going in preparation for that launch. And please don't change the version number, we'll increment that when the release is ready.

I understood the situation and realized that it is the same thing 3.3 Simulated Historical Forecasts in the prophet paper.
Is my understanding correct?

I understood the situation and realized that it is a special version of 3.3 Simulated Historical Forecast.
Then, I will implement Simulated Historical Forecasts ( shfs ) at first.
After that, I will implement time-series cross validation as a special case of that.

@bletham
I implemented shf function (Simulated Forecast) based on the paper of Prophet following your advice.
And I also re-newed my cv implementation using shf.
It is completely the same except for these arguments.
Does it sound good for you?
I would like to write a more document and test if it is.

@bletham
I update codes to reflect your comment and add tests & documentations.
In addition to that, I change the name of functions ( shf -> simulated_historical_forecasts, cv
-> cross_validation  ) to be more clear for users.
Could you merge this PR if it looks good to you ? :)
I will implement the same functionality in R language if necessary.

@bletham
Change codes to reflect your comments and add some tests for Prophet.copy method!

This is huge, thanks!
If you'd like to translate this commit over to the R version that'd be great, otherwise I'll get to it in the next couple weeks.


Docker container failing to initialise.

I've attempted to setup the docker container, fresh, on an Unraid server using Docker Compose. The container is struggling to start and I'm seeing this in the container logs:
docker logs silverbullet
Going to start SilverBullet binding to <IP_ADDRESS>:3000
Serving pages from /space
Error initializing database Error: Permission denied (os error 13), open '/space/data.db'
    at Worker.<anonymous> (file:///silverbullet.js:186745:28)
    at innerInvokeEventListeners (deno:ext/web/02_event.js:755:9)
    at invokeEventListeners (deno:ext/web/02_event.js:795:7)
    at dispatch (deno:ext/web/02_event.js:664:11)
    at Worker.dispatchEvent (deno:ext/web/02_event.js:1043:14)
    at Worker.#pollMessages (deno:runtime/js/11_workers.js:197:14)
HTTP Server error Error: Not initialized
    at Worker.<anonymous> (file:///silverbullet.js:186745:28)
    at innerInvokeEventListeners (deno:ext/web/02_event.js:755:9)
    at invokeEventListeners (deno:ext/web/02_event.js:795:7)
    at dispatch (deno:ext/web/02_event.js:664:11)
    at Worker.dispatchEvent (deno:ext/web/02_event.js:1043:14)
    at Worker.#pollMessages (deno:runtime/js/11_workers.js:197:14)

compose.yml
services:
    silverbullet:
        image: zefhemel/silverbullet
        container_name: silverbullet
        restart: unless-stopped
        volumes:
          - '/mnt/user/appdata/silverbullet:/space'
        ports:
        - 3002:3000

permissions
If I ''ls -la'' on my appdata directory, I can see docker has created the silverbullet directory:
drwxr-xr-x 1 root   root     6 Jan 22 15:37 silverbullet/

I'm fairly new to github, docker and linux in general so let me know if there is any more information I can provide. I can see suggestion of a permissions issue in the logs, but I'm not super sure on how to resolve it.

Does whatever user this container runs as have write permission to that silverbullet directory? It doesn't seem that way.

Thank you, you were correct. After some experimentation, I got it to run via one of the following (sorry I can't be more specific).

Running chown nobody:users silverbullet/

Adding PUID, PGID and UMASK environment variables to the docker compose config:

services:
    silverbullet:
        image: zefhemel/silverbullet
        container_name: silverbullet
        restart: unless-stopped
        environment:
          - PUID=99
          - PGID=100
          - UMASK=022
        volumes:
          - '/mnt/user/appdata/silverbullet:/space'
        ports:
        - 3002:3000

Running chmod +w silverbullet/

This was the order in which I made changes, recreating the container at each step. It didn't start working until the last one, so perhaps the last step is all that's needed, but I can't be certain. Thank you for your suggestion.


/god improvements

Serverside:
Prevent server from displaying any signs of actual damage (not signs of being hit) from player using /god, such as blood, broken bone sounds, etc.
Clientside:  Is it possible to prevent the player's client from receiving any sort of damage packet, without preventing them from seeing the shots / hits that would cause the damage?  If so, this could prevent flinching, vision changes, blood, bleeding, broken bones, etc.

Nope..

Not possible?

@Ejraiel Don't think so. Would require client side stuff.

=\


Plus Sign "Slots" stuck open

Often, when moving tasks around, you'll see the empty task slots with a plus sign and an "ants" border, but they don't close unless you're very careful to move the dragged item in a very specific manner:

I'm still trying to figure out the trick to getting them closed, so can't say what is the solution or why this happens.
I think if you drag an item down, a slot opens up above its parent, if you drag it a bit further down, the slot below the item you're dragging opens up, if you set the item down at that point they both stay open. If you drag the item slightly up again, they both close at that point.
Closing and reopening the app closes the empty slots.

Hi! What version are you running?

@mrvladus I think it's the latest (45.1), although I think I saw this issue before this major update as well.

Can you record a video? I can't replicate it.

https://youtu.be/L0QJnH9ldUM

@Natetronn I've tested it in Manjaro VM and found that it is KDE bug, along with the strange black background of app icon, that is KDE bug too. I fixed this issues in fea921fc853a832c2c31881fc99147f648db352d and 9633b79557a75a22c56853fb47049ecd1647f00a, so in the next release all should be fine.

Thank you very much!


Passwordless migration guide improvement

Context

I found some problems about current passwordless migration guide.

Links about passwordless migration guide.

https://learn.microsoft.com/en-us/azure/storage/common/migrate-azure-credentials
https://learn.microsoft.com/en-us/azure/developer/java/spring-framework/migrate-mysql-to-passwordless-connection
https://learn.microsoft.com/en-us/azure/developer/java/spring-framework/migrate-postgresql-to-passwordless-connection
https://learn.microsoft.com/en-us/azure/developer/java/spring-framework/migrate-kafka-to-passwordless-connection
https://learn.microsoft.com/en-us/azure/developer/java/spring-framework/migrate-sql-database-to-passwordless-connection
https://learn.microsoft.com/en-us/azure/developer/intro/passwordless-overview

Problems

Same contents appeared in many places. For example: "Assign the managed identity using the Azure portal" appeared in all above links. If someone updated one page, it's error-prone to miss some other places.
The migration guide is too long. When a customer is in the middle of the whole doc, it's easy to lose himself. Because:

The TOC on the up-right corner will not scroll when customer scrolled the document.
The TOC only has one level, but the document has multiple levels. In the middle of the current document, it's hard to know whether a title is level-2 title or level-3 title.

There are different tabs, which may confuse customers.

Tab change together not worked. I know that MS docs provide this feature: If one page have multi tabs, after customer chooses value in one tab, all tabs in the same page will choose the same tab value (Here is a link to a page with this feature works.). This feature is broken in the current migration guide page.
Some items in one tab are not brother relationship, put them in one tab window may confuse customers. For example: In tab 5, Service Connector and Azure portal are not brother relationship. Same in Tab 3.

Goal
Solve above problems.

Hi @chenrujun Is there a place where I can find all the documentations?

Hi @chenrujun Is there a place where I can find all the documentations?

Do you mean this: https://github.com/Azure/azure-sdk-for-java/issues/32185#issuecomment-1317939807
I have listed all links about passwordless in the issue description.

Yes, I think it's just what I want. Thanks.

After a meeting with content team (Karl). He will handle these problems.
Here is the meeting note from Karl:

What we agreed is that, through December, Scott will take a look at the migration articles and look for opportunities to consolidate identical content into include files. Part of this assessment will be to identify complications such as text blocks that are identical except for small differences (such as product names, header numbering, etc.). Then, in January, we will refactor the content using include files.
Additionally, we’ll assess the content for improvements around header numbering. We tentatively agreed that it would probably be best to number only sections that are procedural in nature, and not number anything that isn’t a clear step in a procedure. Ideally, H2 would not be numbered, and H3 and lower might be numbered. The thinking here is that the numbering of H3/H4/etc. will help distinguish heading levels. If necessary, we can use numbering such as 1.1 etc. We should also look at the numbering that is currently present in some articles and see if that makes things clear. If there is solid precedence, then we can apply similar numbering across the content set. We’ll do that work in January as well.
After we do a first round of consolidation and header fixes, we can do a usability study (perhaps in February) and determine whether the current structure works for our customers, or whether we should break the content into smaller pieces. Keeping in mind that the articles should be sized so that one article = one task, we can determine what a natural breakdown would look like.

Closing this issue because we do not need to do anything.


Update dependency org.jvnet.jaxb2_commons:jaxb2-basics to v0.12.0

This PR contains the following updates:

Package
Update
Change

org.jvnet.jaxb2_commons:jaxb2-basics
minor
0.6.0 -> 0.12.0

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

PR has been edited
:construction_worker: This PR has received other commits, so Renovate will stop updating it to avoid conflicts or other problems. If you wish to abandon your changes and have Renovate start over you may click the "rebase" checkbox in the PR body/description.


chore: add test for #6 (DO NOT MERGE)

Refs #6.

dockertest does not seem to be compatible with testcontainers, so this PR removes the testcontainers-based example. DO NOT MERGE this PR.

Closing as not needed.


Quick fixes for Liquid Tests errors

Description

When the API response is "nothing", create a quick fix to remove the corresponding row
When there is a difference between the "expected" and "got" values, create a quick fix to replace the content of the corresponding item with the value that we have "got" from the Liquid Test run

Type of change

[ ] Bug fix
[x] New feature
[ ] Breaking change

Checklist

[ ] README updated (if needed)
[x] Version updated (if needed)
[x] Changelog updated (if needed)
[ ] Documentation updated (if needed)

Will be added with the Liquid Linter implementation


Disable non-empty nulls assertions

This PR disables the assertions added in https://github.com/rapidsai/cudf/pull/13071 when performing unit tests
contributes to https://github.com/NVIDIA/spark-rapids/issues/6680

Are we turning off assertions in unit tests?  Why would we do that?

Are we turning off assertions in unit tests? Why would we do that?

Yes, but only assert in the class ai.rapids.cudf.AssertEmptyNulls. The reason for that is that we have 4 unit tests that explicitly introduce non-empty nulls which will fail this assertion. Either we disable asserts in that class for all unit-tests or we skip those 4 unit-tests that will fail unless we run the tests with -da:ai.rapids.cudf.AssertEmptyNulls.

Either we disable asserts in that class for all unit-tests or we skip those 4 unit-tests that will fail unless we run the tests with -da:ai.rapids.cudf.AssertEmptyNulls

Turning these assertions off for the unit tests means they never run in practice.  Java assertions are not on by default, they are explicitly enabled during our unit tests runs.  Turning them off here means these assertions in essence never will fire, which makes one wonder why we're adding them.

build

build

build


respect namespace from .kubeconfig file

This adds namespace integration into the the kubeconfig.  The property was there before, but it was not respected.
I left this for last because namespace doesn't quite fit with the  rest of the information.  Everything else in .kubeconfig is about how to connect to a running kubernetes cluster.  Namespace is about what subset of things you want to deal with by default after you've connected.  I can see why we have one file, but it means the integration doesn't touch the same parts of code.
@smarterclayton @jlowdermilk I think this is the final part of #1755.

other comments?

lgtm

LGTM

Rerunning travis then will merge


Royal Flushes Not Evaluated Correctly for Deuces Wild

console.log(Hand.solve(['2s','Kc','Jc','2d','Qc'],'deuceswild').name) evaluates to only a straight flush. Same goes for a natural royal.
If you change .name to .descr it works, but adds extra info for all the other hands. I am trying to figure out a fix, but these evaluation libraries are always convoluted to the person that didn't write them.

I suspect that the answer to this is that technically, a royal flush is a straight flush of the highest rank.  Others may have other feelings about that, though.

I get what you are saying if .name was meant for debug and a synonym of class, but it is not congruent with the other methods. rank and descr work after some testing. I am now just using rank and then using that number to call and array of ordered ranks, minus 1 of course.

If .name returns straight flush, and .descr returns royal flush, then it sounds to me like it's probably intended that way.  I've never actually built anything with the library, though, so I don't have any particular insight into it. :-)

It looks like a logic error to me persistent across games, it's not just deuceswild. The documentation doesn't hint that it should be a class, only that it is a type.
Every single library on github has issues with wrong evaluation except the ones using lookup tables, but haven't found that for wildcard games. There is no progress on the code golf side of such a library I think because ultimately if you care about speed, you just make a lookup table and enumerating one only takes once, so you don't need efficiency at any point, and it's very tedious no matter how quick you are.


chore: rename setAutoFocus public method to prevent naming collisions

Summary
As found out by @wouterds, a change made in the latest autoFocus PR made the project collide with reac-native-screens library. I described the problem there but echoing here for better visibility:

They (react-native-screens) have this SearchBarView which extends ReactViewGroup. I introduced a public method in ReactViewGroup called setAutoFocus and they have this line which generates a setter called setAutoFocus method I believe (Kotlin magic). It's forbidden to create a method while the extended class has the same, so here we have our problem 😄

This PR changes the name of the public method introduced in the previous PR to solve the problem.
We should strictly follow one of the articles below to prevent a future incident like this one:

Don't introduce a new public method in RN Core files at all.
If you do, name the method with a prefix or a suffix like TV to reduce the risk of a potential naming conflict.
Don't overload existing core components with new functionality at all, create separate components extending the original ones.

I followed the second one but this is worth a discussion. Third one seems to be the way to. We've put a lot of logic into ReactViewGroup to support TVFocusGuide functionality which is obviously wrong. I know we have RCTTVView and lots of others on the tvOS side (at least for Paper --old-- architecture), we should probably do the same for Android. This should also ease the RN version updates since there'd be fewer potential conflicts.

2 makes sense to me too


Feature request: Blacklisting hosts from being scaling targets for a service

I'm experimenting with a cluster of systems, 3 at DO, 1 sitting next to me, 1 VM elsewhere and depending on the time of day a dedicated colo box. Loving the ease that this offers for mixing them all and figuring out how I can offer this to my customers.
But I'd really like to be able to flag the box sitting next to me as a private host, not a public one so that the load balancer doesn't scale to it, or really any container trying to expose ports publicly. I know we can't easily generalize a container by it's contents, so was thinking that detecting host ports being called might be an effective way to handle it.
Alternatively, a dropdown list of hosts for a blacklist or whitelist that the user configures could ease the issue.

This can be accomplished with host labels + scheduling rules in this week's 0.23.x release.  We haven't tagged a stable version yet but it should be in the next day or two.
Labels can be any key/value so you'd mark the host private=true, or `location=myhouse, or whatever makes sense to you.  Then you can add scheduling rules to hosts/containers that say e.g. "The host must not have the label private=true", and the containers will be put on to only hosts that meet the rules.

Ahhh I probably need to start playing in the beta playground huh? Probably already covered and coded the next set of wishlist items I haven't thought up yet.

@Zaephor We just tagged latest this morning, so you should be able to do exactly what you want in the new features. We will be releasing some documentation in the next week or two to help users as we've started to add in a lot of features that may or may not be intuitive.
Feel free to open a new issue for any specific questions you might have with our new host labels and scheduling rules.


Content pages

New content pages

[x] tafsir

Deployed to: http://staging.quran.com:32779

Let's wait on the API endpoint? Or is there an endpoint for this already? Lastly, mind squashing to remove the extra commits? It will cause a disaster to commit

rebuild

Deployed to: http://staging.quran.com:32777

Deployed to: http://staging.quran.com:32786

Deployed to: http://staging.quran.com:32788

Deployed to: http://staging.quran.com:32796

rebuild

Deployed to: http://staging.quran.com:32800

Deployed to: http://staging.quran.com:32804

closing in favor of https://github.com/quran/quran.com-frontend/pull/799


django-extensions: 2.1.4 -> 2.2.1

This updates django-extensions to version 2.2.1, which also fixes the pytest5 build failures.
The pipchecker tests all try to execute pip inside the sandbox with either specific version requirements or a git+https repository and are therefore removed because they fail.
nix-review shows two failed pkgs that depend on django-extensions (python3.7-django-q-1.0.1 and python3.7-HyperKitty-1.2.2). They seem to fail due to pytest5 incompatibility.
Motivation for this change
The django-extensions build is currently failing.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers

On macos 10.13:
=================================== FAILURES ===================================
___________________________ test_with_template_dirs ____________________________

capsys = <_pytest.capture.CaptureFixture object at 0x10b960810>
settings = <pytest_django.fixtures.SettingsWrapper object at 0x10b960b50>
tmpdir_factory = TempdirFactory(_tmppath_factory=TempPathFactory(_given_basetemp=None, _trace=<pluggy._tracing.TagTracerSub object at 0...50>, _basetemp=PosixPath('/private/tmp/nix-build-python3.7-django-extensions-2.2.1.drv-0/pytest-of-nixbld1/pytest-0')))

    def test_with_template_dirs(capsys, settings, tmpdir_factory):
        templates_dirs_path = tmpdir_factory.getbasetemp().strpath
        template_path = os.path.join(templates_dirs_path, 'fixme.html')
        settings.TEMPLATES[0]['DIRS'] = [templates_dirs_path]
        with open(template_path, 'w') as f:
            f.write('''{# FIXME This is a comment. #}
    {# TODO Do not show this. #}''')

        call_command('notes', '--tag=FIXME')
        out, err = capsys.readouterr()

>       assert '{}:\n  * [  1] FIXME This is a comment.'.format(template_path) in out
E       AssertionError: assert '/private/tmp/nix-build-python3.7-django-extensions-2.2.1.drv-0/pytest-of-nixbld1/pytest-0/fixme.html:\n  * [  1] FIXME This is a comment.' in '/private/tmp/nix-build-python3.7-django-extensions-2.2.1.drv-0/source/django_extensions/admin/__init__.py:\n  * [121]...s/management/jobs.py:\n  * [107] FIXME HACK: make sure the project dir is on the path when executed as ./manage.py\n\n'
E        +  where '/private/tmp/nix-build-python3.7-django-extensions-2.2.1.drv-0/pytest-of-nixbld1/pytest-0/fixme.html:\n  * [  1] FIXME This is a comment.' = <built-in method format of str object at 0x109ecdbd0>('/private/tmp/nix-build-python3.7-django-extensions-2.2.1.drv-0/pytest-of-nixbld1/pytest-0/fixme.html')
E        +    where <built-in method format of str object at 0x109ecdbd0> = '{}:\n  * [  1] FIXME This is a comment.'.format

tests/management/commands/test_notes.py:34: AssertionError

seems confused about its working dir etc.

@risicle I could reproduce the issue building this on macOS.
One test required localhost networking and an another issue is now reported upstream:
https://github.com/django-extensions/django-extensions/pull/1417
I included the proposed upstream patch in this PR to fix the test failure.

Neat! Afraid I can't test myself till the weekend but you seem to have it under control.

The upstream patch is already merged, so I replaced the file with a fetchpatch.

please rebase and test again

Rebase is done.
Only paperless is failing now as it was before.

@FRidh can this be merged and cherry picked into release now?

Closing as superseded by #72632


[FEATURE] Support List of env parameters

SeedFarmer currently supports and .env file.  Investigate whether we can pass in a list of .env files (maintain ordering) to support multiple env files.
For example:
seedfarmer apply addf --env .env as well as seedfarmer apply addf --env [".env",".env1",".env2"]

https://github.com/theskumar/python-dotenv?tab=readme-ov-file#load-configuration-without-altering-the-environment


poly: add function materialization patterns to lower-poly

I am planning to do this, just wanted to split it off from the initial https://github.com/google/heir/pull/94 in light of https://reviews.llvm.org/D158107

Picking this one up

Fixed by https://github.com/google/heir/pull/154


Update dependencies and pin to versions

Bumps up the pyright version in the project requirements and tox script and fixes any resulting tests and lint failures.
QA steps
As with the base branch, a live end-to-end test environment is pending. PR to be marked as draft for now.
Changelog

Bump up pyright version

Closing in favour of https://github.com/canonical/operator/pull/894


WARNING: 'any' reference target not found: latest_release

root@tomoyafujita:~/ros2_ws/work/ros2_documentation# make html
Running Sphinx v7.2.6
loading intersphinx inventory from http://docs.ros.org/en/independent/api/catkin_pkg/html/objects.inv...
loading intersphinx inventory from http://docs.ros.org/en/independent/api/jenkins_tools/html/objects.inv...
loading intersphinx inventory from http://docs.ros.org/en/independent/api/rosdep/html/objects.inv...
loading intersphinx inventory from http://docs.ros.org/en/independent/api/rosdistro/html/objects.inv...
loading intersphinx inventory from http://docs.ros.org/en/independent/api/rosinstall/html/objects.inv...
loading intersphinx inventory from http://docs.ros.org/en/independent/api/rospkg/html/objects.inv...
loading intersphinx inventory from http://docs.ros.org/en/independent/api/vcstools/html/objects.inv...
building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 260 source files that are out of date
updating environment: [new config] 260 added, 0 changed, 0 removed
reading sources... [100%] index
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
copying downloadable files... [100%] Tutorials/Intermediate/URDF/documents/r2d2.rviz
copying static files... done
copying extra files... done
done
writing output... [100%] index
/root/ros2_ws/work/ros2_documentation/source/Releases/Release-Rolling-Ridley.rst:12: WARNING: 'any' reference target not found: latest_release

i guess reference tag is somewhere missed up...

I'm getting the same error. Looks like latest_release was renamed to latest-release in https://github.com/ros2/ros2_documentation/commit/53f64f5d7fe61405151bc41ceb5fdd32da92eedb


Implement setting config variables that contain the dot in name

[x] Closes https://github.com/dask/distributed/issues/8570
[x] Tests added / passed
[ ] Passes pre-commit run --all-files

Can one of the admins verify this patch?
Admins can comment ok to test to allow this one PR to run or add to allowlist to allow all future PRs from the same author to run.


GOSA24 - Add logout functionality

Add logout button and corresponding firebase function in App drawer.

assign me

@singhtaran1005 express

express?

assign me

assign me

@rithik-dev you can start working on this.

@rithik-dev thank you for the contribution. You have recieved 5 points for the contribution. We merged your pr successfully


Allow affine transformations on epochs

This allows epochs to be transformed with affine transformations given by a 4x4 numpy array using an Epoch.transform method. Should be generally useful, but is also foundational work towards future registration work.

Codecov Report

Merging #258 (7a0d025) into main (8ef524b) will increase coverage by 0.03%.
The diff coverage is 97.22%.

:exclamation: Current head 7a0d025 differs from pull request most recent head 6bece6e. Consider uploading reports for the commit 6bece6e to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files

@@            Coverage Diff             @@
##             main     #258      +/-   ##
==========================================
+ Coverage   89.24%   89.27%   +0.03%
==========================================
  Files          20       22       +2
  Lines        1776     1809      +33
==========================================
+ Hits         1585     1615      +30
- Misses        191      194       +3

Flag
Coverage Δ

cxx
87.18% <100.00%> (-0.09%)
:arrow_down:

python
91.03% <94.44%> (+0.13%)
:arrow_up:

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

Impacted Files
Coverage Δ

src/py4dgeo/epoch.py
93.05% <94.44%> (+0.80%)
:arrow_up:

lib/registration.cpp
100.00% <100.00%> (ø)

tests/c++/registration_t.cpp
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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


Does it work well in hololens?

I have made it work with hololens. But the frame rate is very low, and the usage of CPU is very high. Does it any resolution to deal with this problem. Btw, it seems some "TODO" work in choose the video encoder. Does it use the Raw Data to communicate?

It is the same experience I have with the HoloLens (V1 hardware and software platform), while the UWP application works, the framerate is very low with the image processing running on the limited CPU resource.
The WebRTC session is setup to use H264 video encoding on the network peer session, and the WebRTC UWP wrapper provides both H264 encoded frames, and decoded raw frames but I need to perform a YUV color fix to display properly on the Unity Quad on the native plugin side.
Note that even doing simple BitBlt on the image buffer used by the texture on the native plugin drops the framerate significantly on the Unity player runtime and the native plugin manipulating images.
To achieve a more acceptable framerate on the HoloLens, an alternative solution is to write a native UWP DirectX app that uses the WebRTC library and get the full available hardware resources for your application.   I am personally hoping an eventual hardware/system upgrade on the HoloLens or code access to the hardware video processor to offload the CPU improves the performance with Unity.

Thank you very much.


Change aggregate_logical_cpus to non deprecated

High level
We defined aggregate_logical_cpus as an attribute on a few models. The api/normalizer.rb uses these attributes to generate the columns that are sent to the user. So this deprecated column is included in this list. This was causing a deprecation notice:
DEPRECATION WARNING: aggregate_logical_cpus is deprecated
and will be removed from ManageIQ D-release
(use aggregate_cpu_total_cores instead)
(called from block in normalize_hash at
app/controllers/api_controller/normalizer.rb:22)

Low Level
Instead of bringing back all attributes, virtual and regular, this brings back only regular attributes.
So virtual attributes, some of which are deprecated, most of which are a separate query, are looked up.
This only applies when no attributes are specified. If an attribute is requested, it is brought back whether it is deprecated or not.
@abellotti please confirm the process to change the public api and when it is possible from a versioning perspective.

@abellotti Darn. Think this is a bug
Typically, when you render an object, it has attributes and it will render the thing no problem.
The virtual attributes are not included in the attribute list and there is no deprecation warning.
For an object that is updated, the class itself is passed into render. So when it calls attributes, all the attributes of the class are returned, including the virtual attributes, and thus including the deprecated attributes. So the results for an update will include all the virtual attributes.

If you want to reproduce the deprecation warnings:
rspec spec/requests/api/providers_spec.rb:211

That file is responsible for a majority of them.
It looks like updates pass in the class to normalize attributes. It returns virtual and non-virtual attributes. Some of those virtual attributes are deprecated.

Yes @kbrock the after that you have there is correct, API always expected .attributes to return the physical attrs (this behavior is different in latest code base).

@abellotti does this need to be on darga?

I'd say yes since the API behavior because of .attributes is different that earlier releases.

Lookin' good, just tested locally.
Will merge when 🍏

@kbrock @abellotti @gtanzillo  is there a BZ for this?

@chessbyte this was mostly for deprecation cleanup. turns out it was an api bug as well


Updates to include clearer names and bool type datasets

Updating to use oa as the product group instead of parent names for items such as the solar geometry. This removes the duplication in the measurement name and brings it into line with the idea ard C3 terminology.
Also enables boolean datasets. As GDAL doesn't support compound types, we simply convert the dataset to a GeoTIFF of type uint8.

Will close and establish a clean branch. This one still has binaries in the commit history and lots of conflicts arising from commits mid-way through the commit history.


Group all queries that depend on the DRT output in the same section

In https://github.com/open-contracting/notebooks-ocds/pull/38 I added a step to confirm that the DRT checks are complete before querying their output.
Some other queries depend on the DRT output too:

Local extensions and additional fields and codes
Deprecated fields

We should group all the queries that depend on the DRT output in the same section so that it's clear that analysts need to wait for the DRT checks to be complete before running them.

I've instead just added a note to that section. Better to group thematically rather than by dependency.


Fix breaking buildToolbar change

@znjameswu See the discussion linked in the changelog.

See https://github.com/flutter/flutter/pull/73882/files#r568969211 for the proper fix @znjameswu.

https://github.com/flutter/flutter/pull/73882 introduced the change.

Closing in favor of https://github.com/znjameswu/flutter_math/pull/43.


KMMO fails to check if image exists

We have deployed KMMO commit e899b4cb4ae1665700e4fef77657c2867fe531ba on OCP 4.11. Seeing the following error in kmm-operator-controller-manager logs after deploying module CR. Pls advise, thanks! Can you share some examples or any documentation we can refer to while creating our module CR?
Our module CR looks like this at the moment:
> ---
> apiVersion: kmm.sigs.k8s.io/v1beta1
> kind: Module
> metadata:
>   name: intel-dgpu-kmmo
> spec:
>   moduleLoader:
>     container:
>       modprobe:
>         moduleName: intel-dgpu-kmmo
>       kernelMappings:
>         - literal: 4.18.0-372.19.1.el8_6.x86_64
>           containerImage: image-registry.openshift-image-registry.svc:5000/default/intel-dgpu-driver-container:4.18.0-372.19.1.el8_6.x86_64
>           build:
>             pull:
>               insecure: true
>             push:
>               insecure: true
>             secrets:
>               - name: image-registry-secret
>             dockerfile: |
>               FROM image-registry.openshift-image-registry.svc:5000/openshift/driver-toolkit:latest
>              .......
>   selector:
>     intel.feature.node.kubernetes.io/gpu: 'true'

Error:
 E0914 21:50:02.207291 1 controller.go:326] "msg"="Reconciler error" "error"="failed to handle build for kernel version 4.18.0-372.19.1.el8_6.x86_64: failed to check image existence for kernel 4.18.0-372.19.1.el8_6.x86_64: could not check if the image is available: failed to get pull options for image image-registry.openshift-image-registry.svc:5000/default/intel-dgpu-driver-container:4.18.0-372.19.1.el8_6.x86_64: cannot get keychain from the registry auth getter: could not get the service account's pull secrets: serviceaccounts \"builder\" is forbidden: User \"system:serviceaccount:kmm-operator-system:kmm-operator-controller-manager\" cannot get resource \"serviceaccounts\" in API group \"\" in the namespace \"default\"" "controller"="module" "controllerGroup"="kmm.sigs.k8s.io" "controllerKind"="Module" "module"={"name":"intel-dgpu-kmmo","namespace":"default"} "name"="intel-dgpu-kmmo" "namespace"="default" "reconcileID"="0538c905-bc8a-4a47-80e6-e95ef8bbf2ec"

One more follow-up question, can we create the module CR in any namespace? Or does it have to be in a specific namespace for KMMO to work.

Hi @hershpa, this seems to be an oversight in the RBAC permissions of the operator following the implementation of the BuildConfig support. #47 should fix this issue.

can we create the module CR in any namespace?

Yes, any namespace.

Hi @qbarrand, thanks for the update and fix.

Hi @qbarrand, still seeing the following issue after the fix: Get \"https://image-registry.openshift-image-registry.svc:5000/v2/\": x509: certificate signed by unknown authority"

Tested and seeing the above issue on 2 different OCP clusters.

@hershpa can this issue be closed?


Add testCase.version to EiffelTestCaseStartedEvent

Some Test Management systems version control their test cases. Therefore it would be needed to be able to specify what version of the test case that was executed.

Makes sense. Will you create a PR?


replace internal functions in storage sample code

closes https://github.com/Azure/azure-sdk-for-cpp/issues/5192
Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[x] C++ Guidelines
[x] Doxygen docs
[x] Unit tests
[x] No unwanted commits/changes
[x] Descriptive title/description

[x] PR is single purpose
[x] Related issue listed

[x] Comments in source
[x] No typos
[x] Update changelog
[x] Not work-in-progress
[x] External references or docs updated
[x] Self review of PR done
[x] Any breaking changes?

/check-enforcer override


Input field for account import via seed phrase hidden by keyboard

Only if I close the keyboard, the input field becomes visible. Meaning I have to type the seed phrase blindly.
Device: Huawei P10 Lite, 5.1" screen with 1920x1080 px.
OS: Android 8.0

Closing as fixed.


boards: shields: Append accel/magn sensor nodelabels with bus address

Devicetree aliases, accel0 and magn0, were recently introduced to enable
sensor sample applications to support multiple sensor drivers of the
same type and thereby reduce the number of driver-specific sensor sample
applications.
This was implemented by adding devicetree nodelabels to accelerometer
and magnetometer sensor nodes, which unfortunately can suffer from
naming conflicts when using shield boards. Fix the problem by appending
the I2C bus address or SPI chip select to the devicetree nodelabel for
sensor nodes on shield boards only. Base boards are left alone to keep
their nodelabels as short as possible.
Signed-off-by: Maureen Helm<EMAIL_ADDRESS>Fixes #48780

@MaureenHelm
Thanks for this improvement.


mpg123: 1.25.12 -> 1.25.13

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/mpg123/versions.
meta.description for mpg123 is: '"Fast console MPEG Audio Player and decoder library"'.
meta.homepage for mpg123 is: '"http://mpg123.org"

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.25.13 with grep in /nix/store/k2fvkj52zgy13qij7bsiwnvla3rp9qjs-mpg123-1.25.13

directory tree listing: https://gist.github.com/c32893322782e703b4f596e346406225

du listing: https://gist.github.com/5d27b01cf6d6947d2c0b142a021b86b7

Rebuild report (if merged into master) (click to expand)

686 total rebuild path(s)
229 package rebuild(s)
228 x86_64-linux rebuild(s)
220 i686-linux rebuild(s)
31 x86_64-darwin rebuild(s)
207 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
_90secondportraits
adapta-gtk-theme
ahoviewer
alarm-clock-applet
aravis
audacious
audaciousQt5
audio-recorder
baresip
bashburn
beets
bomi
brasero
brasero-original
byzanz
cage
cantata
cawbird
chrome-gnome-shell
clementine
clementineUnfree
cozy
dablin
deepin.dde-kwin
deepin.dde-launcher
deepin.dde-session-ui
denemo
dir2opus
dragon
easyrpg-player
empathy
enlightenment.econnman
enlightenment.efl
enlightenment.enlightenment
enlightenment.ephoto
enlightenment.rage
enlightenment.terminology
epiphany
evince
farstream
feedreader
flacon
freerdp
freerdpUnstable
gajim
gcompris
gjay
glom
gmrender-resurrect
gmu

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/k2fvkj52zgy13qij7bsiwnvla3rp9qjs-mpg123-1.25.13 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A mpg123 https://github.com/r-ryantm/nixpkgs/archive/d254966a78d4fdd0423ef60357212c8de7a66348.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/k2fvkj52zgy13qij7bsiwnvla3rp9qjs-mpg123-1.25.13
ls -la /nix/store/k2fvkj52zgy13qij7bsiwnvla3rp9qjs-mpg123-1.25.13/bin

cc @ftrvxmtrx for testing.

@GrahamcOfBorg build mpg123


Add MonadFail constraints in obelisk-cliapp for GHC 8.6

Definitely seems like progress; can revist whether we want MonadFail or something else later.


Ensure LaunchAgents directory exists

Two users have had issues (#22, #30) where the LaunchAgents directory doesn't exist. I'm not sure what's causing it to be missing, but we might as well ensure its presence in the postinstall script.
/cc @opsroller

@mastahyeti It's probably the Casper Agent from JAMF.


Add service catalog testing to daily runs

This is nearly identical to the existing "/test service-catalog" execution in test_pull_request_origin_service_catalog.yml.

This is ready for last review/merging now, @stevekuznetsov .

@stevekuznetsov should be good to go now!


[BUG]: [Dataview] Math rendering

Issue validation

[X] I checked the issue to prevent duplicate
[X] I checked my configurations files and the documentation

Command used
Refresh published and upload new notes
Plugin version
6.7.3
Describe the bug
I seem to be unable to render inline math. Here's an example:
>[!infobox|left]
>![[er_dhampir-portrait_4.png|vh-sm]]
>###### Stats
> > -  :fas_dice_d20: \+`$= Math.floor((dv.current().dexterity -10) / 2)` ⋅ :fas_running: `=this.speed`ft
> > - :rif_shield_star: `=this.ac` ⋅ :fas_heart: `=this.hp`
> > - :fas_eye: `=this.perception` ⋅ :rif_spy: `=this.stealth`
> >
> > | Ability      | Score                | Mod                                        |
> > |--------------|----------------------|--------------------------------------------|
> > | Strength     | `=this.strength`     | `$= Math.floor((dv.current().strength -10) / 2)`     |
> > | Dexterity    | `=this.dexterity`    | `$= Math.floor((dv.current().dexterity -10) / 2)`    |
> > | Constitution | `=this.constitution` | `$= Math.floor((dv.current().constitution -10) / 2)` |
> > | Intelligence | `=this.intelligence` | `$= Math.floor((dv.current().intelligence -10) / 2)` |
> > | Wisdom       | `=this.wisdom`       | `$= Math.floor((dv.current().wisdom -10) / 2)`       |
> > | Charisma     | `=this.charisma`     | `$= Math.floor((dv.current().charisma -10) / 2)`     |

The inline =this.ability renders fine, but the math does not. In this case, since the "Mod" table is thus valueless, it doesn't even render in the final result.
How to reproduce ?
try and do some inline math...
Minimal Reproducible Example
Here's the entire note:

---
share: true
tags:
  - erspace/ermis
type: pc
linter-yaml-title-alias: "**`=this.file.name`**"
art: "![[er_dhampir-portrait_5.png|75]]"
player: Griffin
name: Stigs the Stiff
aliases:
  - "**`=this.file.name`**"
class: Artificer
subclass:
level: 1
background: Shipwright
alignment:
strength: 12
dexterity: 17
constitution: 15
intelligence: 18
wisdom: 12
charisma: 10
perception: 13
stealth: 15
hd: 1d8
hp: 12
ac: 15
pb: +2
speed: 35
condition: Healthy
action:
skill-proficiencies: Arcana, History, Investigation, Perception, Sleight of Hand, Stealth
save-proficiencies: Constitution, Intelligence
languages: Common
overview: A shipwright for House Ororos
traits:
ideals:
bonds:
flaws:
pronouns:
pronounced:
ancestry: Dhampir
gender:
age:
sexuality:
height:
weight:
location:
occupation: Shipwright
friends-family: [House Ororos]
rivals:
associatedGroup: House Ororos
associatedReligion: Er
date created: Saturday, September 23rd 2023, 7:45:19 pm
date modified: Monday, October 2nd 2023, 1:06:28 pm
---

>[!infobox|left]
>![[er_dhampir-portrait_4.png|vh-sm]]
>###### Stats
> > -  :fas_dice_d20: \+`$= Math.floor((dv.current().dexterity -10) / 2)` ⋅ :fas_running: `=this.speed`ft
> > - :rif_shield_star: `=this.ac` ⋅ :fas_heart: `=this.hp`
> > - :fas_eye: `=this.perception` ⋅ :rif_spy: `=this.stealth`
> >
> > | Ability      | Score                | Mod                                        |
> > |--------------|----------------------|--------------------------------------------|
> > | Strength     | `=this.strength`     | `$= Math.floor((dv.current().strength -10) / 2)`     |
> > | Dexterity    | `=this.dexterity`    | `$= Math.floor((dv.current().dexterity -10) / 2)`    |
> > | Constitution | `=this.constitution` | `$= Math.floor((dv.current().constitution -10) / 2)` |
> > | Intelligence | `=this.intelligence` | `$= Math.floor((dv.current().intelligence -10) / 2)` |
> > | Wisdom       | `=this.wisdom`       | `$= Math.floor((dv.current().wisdom -10) / 2)`       |
> > | Charisma     | `=this.charisma`     | `$= Math.floor((dv.current().charisma -10) / 2)`     |
> > ||||
> >  - **Skill Proficiencies:** `=this.skill-proficiencies`
> >  - **Save Proficiencies:** `=this.save-proficiencies`
> >  - **Default Action:** `=this.action`
> >  -  **Condition:** `=this.condition`

# **`=this.file.name`**
>[!info|bg-c-purple]- Overview
> - `=this.overview`

>[!column|clean no-title] Characteristics
>> [!metadata|bg-c-blue]+ Traits
>> - `=this.traits`
>
>> [!metadata|bg-c-blue]+ Ideals, Bonds, & Flaws
>> -  `=this.ideals`
>> -  `=this.bonds`
>> -  `=this.flaws`

>[!column|flex 3 clean no-title]
>> [!info|bg-c-gray]+ Bio
>> - **Alias(es):** `=this.aliases`
>> - **Age:**  `=this.age`
>> - **Sex:**  `=this.gender`
>> - **Sexuality:**  `=this.sexuality`
>> - **Height:**  `=this.height`
>> - **Weight:**  `=this.weight`
>> - **Occupation(s):**  `=this.occupation`
>> - **Group(s):**  `=link(this.associatedGroup)`
>> - **Religion(s):**  `=link(this.associatedReligion)`
>
>> [!info|bg-c-gray]+ Other Info
>> - **Ancestry:**  `=this.ancestry`
>> - **Background:** `=this.background`
>> - **Class:** `=this.class`
>> - **Level:** `=this.level`
>> - **Alignment:** `=this.alignment`
>> - **Current Location:**  `=link(this.location)`

## Relationships
>[!column|dataview|clean no-title] Relationships
>> [!metadata|bg-c-green]- Friends & Family
>> - `=this.friends-family`
>
>> [!metadata|bg-c-orange]- Rivals
>> - `=this.rivals`

## Biographical Details

Configuration
{
  "github": {
    "branch": "main",
    "automaticallyMergePR": true,
    "tokenPath": "%configDir%/plugins/%pluginID%/env",
    "api": {
      "tiersForApi": "Github Free/Pro/Team (default)",
      "hostname": ""
    },
    "workflow": {
      "commitMessage": "Merge",
      "name": ""
    },
    "verifiedRepo": true
  },
  "upload": {
    "behavior": "obsidian",
    "defaultName": "docs",
    "rootFolder": "",
    "yamlFolderKey": "",
    "frontmatterTitle": {
      "enable": false,
      "key": "title"
    },
    "replaceTitle": [],
    "replacePath": [],
    "autoclean": {
      "enable": true,
      "excluded": [
        "docs/assets/js",
        "docs/assets/meta",
        "docs/assets/css",
        "tags.md",
        "graph.md"
      ]
    },
    "folderNote": {
      "enable": true,
      "rename": "index.md"
    },
    "metadataExtractorPath": ""
  },
  "conversion": {
    "hardbreak": false,
    "dataview": true,
    "censorText": [],
    "tags": {
      "inline": false,
      "exclude": [],
      "fields": []
    },
    "links": {
      "internal": true,
      "unshared": false,
      "wiki": false,
      "slugify": false
    }
  },
  "embed": {
    "attachments": true,
    "keySendFile": [],
    "notes": false,
    "folder": "docs/assets/img",
    "convertEmbedToLinks": "keep",
    "charConvert": "->"
  }
}

Relevant log output
No errors in log output

OS
MacOS
Anything else?
Here's the displayed site: https://lichfactory.com/adventures/ad astra/the party/stigs the stiff/
Obsidian information
SYSTEM INFO:
	Obsidian version: v1.4.14
	Installer version: v1.4.13
	Operating system: Darwin Kernel Version 22.6.0: Fri Sep 15 13:41:28 PDT 2023; root:xnu-87<IP_ADDRESS>0.8~1/RELEASE_ARM64_T6020 22.6.0
	Login status: not logged in
	Insider build toggle: off
	Live preview: off
	Legacy editor: off
	Base theme: adapt to system
	Community theme: Ebullientworks v0.7.15
	Snippets enabled: 11
	Restricted mode: off
	Plugins installed: 58
	Plugins enabled: 54
		1: Style Settings v1.0.7
		2: Auto Note Mover v1.2.0
		3: Admonition v10.1.1
		4: Advanced Tables v0.19.1
		5: Dataview v0.5.59
		6: Dice Roller v9.4.1
		7: Excel to Markdown Table v0.4.0
		8: Image Toolkit v1.4.0
		9: Kanban v1.5.3
		10: Media Extended v2.11.1
		11: Obsidian Leaflet v5.7.3
		12: Pane Relief v0.5.1
		13: Table Extended v1.6.1
		14: Text Format v2.2.8
		15: Timelines v0.3.2
		16: Second Window v1.1.0
		17: Various Complements v9.0.0
		18: JSON/CSV Importer v0.31.2
		19: DB Folder v3.5.0
		20: Org Mode v1.3.3
		21: Annotator v0.2.10
		22: Webpage HTML Export v1.7.3
		23: Quick Switcher++ v3.3.7
		24: Buttons v0.4.19
		25: Folder notes v1.5.13
		26: Text Generator v0.3.20
		27: Fantasy Content Generator v1.2.2
		28: Force note view mode v1.2.0
		29: Hover External Link Plugin v1.0.0
		30: Linter v1.20.0
		31: Breadcrumbs v3.6.4
		32: Hover Editor v0.11.14
		33: Multi-Column Markdown v0.8.3
		34: Note Auto Creator v1.4.0
		35: Link with alias v1.0.7
		36: Better Word Count v0.10.0
		37: Custom Frames v2.4.6
		38: Settings Search v1.3.8
		39: Obsidian42 - BRAT v0.7.0
		40: Text Mapper v1.0.0
		41: Export Image plugin v1.0.3
		42: Mousewheel Image zoom v1.0.19
		43: Fantasy name generator v0.1.0
		44: Tag Wrangler v0.5.13
		45: Pandoc Plugin v0.4.1
		46: Icon Shortcodes v0.9.7
		47: Templater v1.16.1
		48: Excalidraw v1.9.20
		49: Fantasy Statblocks v3.13.4
		50: Initiative Tracker v12.2.6
		51: Iconize v2.3.1
		52: Github Publisher v6.7.3
		53: Meta Bind Plugin v0.6.5
		54: Calendarium v1.0.0-b29

RECOMMENDATIONS:
	Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
	Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.

Maybe it's a limitation of the dataview API :/

Yes it certainly could be -- though it's hard for me to tell why some aspects of dataview render fine and some don't.

I tried to check but sadly, impossible to come to a conclusion. To be honest, seems to be a problem around the dv Api…

Well, keep the issue open but we need to open a issue on obsidian-dataview to ask about the problem.
Little question : are the other $= function work ? (outside Math.floor)

Okay, think I found a temporary solution

Looks great!


can import module from npm ?

i want to public some module to npm , let the develop easily next time. i have no idea how to import the module ,and where it will be builtted.

You can npm install Lua packages from npm and use them as normal. Importing TypeScript or JavaScript npm packages is currently not supported. See https://typescripttolua.github.io/docs/external-lua-code for more info

do you mean then npm should inculde aa.lua with aa.d.ts  but aa.ts 。 so i need use ts2l transform aa.ts to aa.lua befor public. can ts2l output dts auto?

Yes, npm packages with aa.lua and aa.d.ts will work. See our tests for examples. Packages with just aa.tswill **not** work. You can get tstl to ouput declarations by setting"declaration": true` in your tsconfig.json compilerOptions


Unhandled Promise rejection: n.removeEventListener is not a function, angularfire2/ angular-ssr

**Angular:4.0.0
**Firebase:^4.1.3
**AngularFire:^4.0.0-rc.1
I generated a new project with the latest angular-cli
When I do 'npm run build' without , angularfire2, it builds well with the expected results. But when I do the same with angularfire2, I get the following error:
> ng-render

[info] Rendering application from source (working path: C:\Users\S\AppData\Local\Temp\f38a8c8759a77)
Unhandled Promise rejection: n.removeEventListener is not a function ; Zone: <root> ; Task: Promise.then ; Value: { TypeError: n.removeEventListener is not a function
    at C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\~\firebase\auth.js:28:843
    at C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\~\firebase\auth.js:28:880
    at C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\~\firebase\auth.js:277:366
    at Object.eo/D (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\~\firebase\auth.js:278:2)
    at e (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:19:1)
    at Object.RVyb (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\0.js:15532:72)
    at e (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:19:1)
    at Object.+rnp (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\0.js:673:89)
    at e (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:19:1)
    at Object.Cos1 (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\0.js:11053:77)
    at e (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:19:1)
    at Object.44 (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\0.js:7379:18)
    at e (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:19:1)
    at C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:65:1
    at Object.<anonymous> (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:65:1)
    at Module._compile (module.js:570:32)
  __zone_symbol__currentTask:
   ZoneTask {
     _zone:
      Zone {
        _properties: {},
        _parent: null,
        _name: '<root>',
        _zoneDelegate: [Object] },
     runCount: 0,
     _zoneDelegates: null,
     _state: 'notScheduled',
     type: 'microTask',
     source: 'Promise.then',
     data: undefined,
     scheduleFn: undefined,
     cancelFn: null,
     callback: [Function],
     invoke: [Function] } } TypeError: n.removeEventListener is not a function
    at C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\~\firebase\auth.js:28:843
    at C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\~\firebase\auth.js:28:880
    at C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\~\firebase\auth.js:277:366
    at Object.eo/D (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\~\firebase\auth.js:278:2)
    at e (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:19:1)
    at Object.RVyb (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\0.js:15532:72)
    at e (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:19:1)
    at Object.+rnp (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\0.js:673:89)
    at e (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:19:1)
    at Object.Cos1 (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\0.js:11053:77)
    at e (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:19:1)
    at Object.44 (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\0.js:7379:18)
    at e (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:19:1)
    at C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:65:1
    at Object.<anonymous> (C:\Users\S\AppData\Local\Temp\f38a8c8759a77\webpack:\webpack\bootstrap 19b8eee3ecbed18ba62f:65:1)
    at Module._compile (module.js:570:32)

Note: I have other modules like material2, ng2-pipes that work just well with angular-ssr.
Is there any work around to get angular-ssr to work with angularfire2?

I have the same problem do you find something ?

No .. not yet!  Seems at the current state of things it's  gonna be a tough
one. I read somewhere that Angularfire2 needs some changes to support
universal.  So maybe it's  just to wait.
On Aug 1, 2017 01:19, "Santos da Veiga Nelson"<EMAIL_ADDRESS>wrote:

I have the same problem do you find something ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angularfire2/issues/1077#issuecomment-319121380,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQFR6YZUEjSJ6Fi6ji_ZE45AGOw4fkXbks5sTf6hgaJpZM4OgHu-
.

Follow #1073


Documentation move Nuxt to Vitepress

It will be easier to document with vitepress. It would also be best to move it to the subdomain pergel.oku-ui.com.
https://vitepress.dev/
What do you think about this?

Finish
pergel.oku-ui.com


FX2024 Domain & Capabilities update / Understand cloud usage and cost

🛠 Description
This PR updates all the capabilities that are part of the understand cloud usage and cost  domain according to the new FinOps framework.
📋 Checklist

🔬 How did you test this change?

[ ] 🤏 Lint tests
[ ] 🤞 PS -WhatIf / az validate
[ ] 👍 Manually deployed + verified
[ ] 💪 Unit tests
[ ] 🙌 Integration tests

🙋♀ Do any of the following that apply?

[ ] 🚨 This is a breaking change.
[ ] 🤏 The change is less than 20 lines of code.

📑 Did you update docs/changelog.md?

[ ] ✅ Yes (required for dev PRs)
[x] ➡ Will cover in a future PR (feature branch PRs only)
[ ] ❎ Not needed (small/internal change)

📖 Did you update documentation?

[x] ✅ Public docs in docs (required for dev)
[ ] ✅ Internal dev docs in src (required for dev)
[ ] ➡ Will cover in a future PR (feature branch PRs only)
[ ] ❎ Not needed (small/internal change)

@flanakin All the changes are implemented. It's waiting on your approval now.


Log is missing for faster rcnn with different losses

Hi,
The logs from these experiments are missing:
https://github.com/open-mmlab/mmdetection/tree/master/configs/faster_rcnn

R-50-FPN
IoULoss

37.9
model | log

R-50-FPN
GIoULoss

37.6
model | log

R-50-FPN
BoundedIoULoss

37.4
model | log

Could you share this if available? I'm interested in reproducing the AP results on GIOU.
Thanks!

Thanks for your report, we will update the links.

I was able to reproduce the result. GIoU has better result than IoU which different than the table above.
You can use my logs:
logs.zip

This issue is fixed.


Fix completion of HashMap::new

The ty function in code_model returned the type with placeholders for type parameters. That's nice for printing, but not good for completion, because placeholders won't unify with anything else: So the type we got for HashMap was HashMap<K, V, T>, which doesn't unify with HashMap<?, ?, RandomState>, so the new method wasn't shown.
Now we instead return HashMap<{unknown}, {unknown}, {unknown}>, which does unify with the impl type. Maybe we should just expose this properly as variables though, i.e. we'd return something like exists<type, type, type> HashMap<?0, ?1, ?2> (in Chalk notation). It'll make the API more complicated, but harder to misuse. (And it would handle cases like type TypeAlias<T> = HashMap<T, T> more correctly.)
The ty function for fields was used for signature help, so there we want placeholders so that it looks nicer, I think. Hence I renamed it to signature_ty.

Haven't looked closely yet, but having two functions with the same signature which do different things is super confusing. Is there any way to make something work for both cases?

The way to have something that works for both cases would be to expose the variables, and have the call sites do the substitution themselves.
I tried to avoid the confusion by giving the other version a different name; do you think that's not enough?

do you think that's not enough?

Yeah, I think if you have "which one of two functions do I call", in the limit you will be calling a wrong one. But I agree that there's probably no great solution here, because indeed types with unknowns and types with placeholders are just different things...

bors r+

bors r=matklad


Support PuppetDB 5.2.13? (metrics v2)

We're still on PuppetDB 5.2, which recently received an update to 5.2.13 to mitigate CVE-2020-7943. This means that from 5.2.13 (and higher) the v1 endpoint is disabled by default. Is this catered for in 2.1, as it only mentions PuppetDB 6.9?

I think this was fixed in https://github.com/voxpupuli/puppetboard/pull/558
So we're awaiting a release :-)

That's great! However I just tried upgrading and getting mod_wsgi to work with Python 3 (required per v2?) is... painful (requiring scl packages). Is by any chance getting puppetboard v1 to work with the v2 metrics possible? Otherwise I might consider keeping with puppetdb 5.2.12.

I second this!
I have CentOS7 servers and there is no good way at all to get puppetboard to work on them :(
From: Bouke Haarsma<EMAIL_ADDRESS>Sent: Friday, March 27, 2020 4:37 AM
To: voxpupuli/puppetboard<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [voxpupuli/puppetboard] Support PuppetDB 5.2.13? (metrics v2) (#560)
That's great! However I just tried upgrading and getting mod_wsgi to work with Python 3 (required per v2?) is... painful (requiring scl packages). Is by any chance getting puppetboard v1 to work with the v2 metrics possible? Otherwise I might consider keeping with puppetdb 5.2.12.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/voxpupuli/puppetboard/issues/560#issuecomment-604880866, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABJYF5SICIQECSUS7MF3BF3RJRQRZANCNFSM4LUKIDGA.

@nmaludy could this warrant a 2.1.1 release, do you think?

Yeah we can do a 2.1.1 release. I have some things to do today, but will try this weekend or Monday.

Fixed in #558

Release 2.1.1 was just created with this fix included.

That’s great news for everybody on v2!
Is by any chance getting puppetboard v1 to work with the v2 metrics possible? (back porting those changes?)

I would really like to avoid backporting changes. We don't have mulitple development branches and our release process would break if we backport changes. which bits in v2 block you to update?

Installing Puppetboard v2 on any EL7 series server is impractical due to the lack of WSGI Support for Python 3
I know that for my team and I puppetboard is now broken and cannot be fixed until we complete the migration of our puppetmasters to CentOS 8
Tom
From: Tim Meusel<EMAIL_ADDRESS>Sent: Monday, March 30, 2020 10:37 AM
To: voxpupuli/puppetboard<EMAIL_ADDRESS>Cc: Tom Parker<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [voxpupuli/puppetboard] Support PuppetDB 5.2.13? (metrics v2) (#560)
I would really like to avoid backporting changes. We don't have mulitple development branches and our release process would break if we backport changes. which bits in v2 block you to update?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/voxpupuli/puppetboard/issues/560#issuecomment-606038572, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABJYF5SX5EANPVLZ4ZCVN7DRKCU7ZANCNFSM4LUKIDGA.


Remove GCR from everywhere.

Fixes #1434
Signed-off-by: Nick Young<EMAIL_ADDRESS>

please use your best judgement if docker.io/projectcontour or the bare projectcontour is appropriate. all I ask is that it is consistent across everywhere we write it


sign with complex values does not match numpy 2.0

Reporting a bug

[X] I have tried using the latest released version of Numba (most recent is
visible in the release notes
(https://numba.readthedocs.io/en/stable/release-notes-overview.html).
[X] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

NumPy 2 changes how np.sign handles complex numbers:
https://numpy.org/doc/stable/release/2.0.0-notes.html#change-in-how-complex-sign-is-calculated
Numba 0.60 was not updated to match. Here is an illustration:
In [1]: import numpy as np

In [2]: import numba

In [3]: np.__version__
Out[3]: '2.0.0'

In [4]: numba.__version__
Out[4]: '0.60.0'

In [5]: @numba.njit
   ...: def f(a):
   ...:     return np.sign(a)
   ...:

In [6]: np.sign(1 + 1j)
Out[6]: np.complex128(0.7071067811865475+0.7071067811865475j)

In [7]: f(1 + 1j)
Out[7]: (1+0j)

Thanks for the report!
Though Numba can work with NumPy 2.0, its semantics are still aligned with NumPy 1.x. The next release, 0.61 is planned to be semantically compatible with NumPy 2.0 (release plans are in https://github.com/numba/numba/issues/9540).
I'll keep this open and label it as a  NumPy 2.0 issue so we can track support for this.


only set isUserPreset to true if it's defined in a user presets file

Fixes #4059.
We were not showing presets as being available to select because we are determining that the preset is a user preset, when it really isn't. This is due to the fact that we were incorrectly setting isUserPreset, we should check which file the configure preset was defined in.
Test vsix here:
cmake-tools.zip

@moyo1997 Ping for review, thanks!


Bump serde_with_macros version

sys was missing some feature dependencies, which where hidden due to the dev-dependency features leaking into the normal build.
This caused problems on doc.rs though.

bors r+


ls command returns incorrect swarm details in 0.6.0-rc1

When you have more than one swarm cluster, the docker-machine ls command returns bad data in the SWARM field. It should show the node serving as swarm master for the swarm the node belongs to.  Instead it appears to list the swarm master of whichever swarm is currently active via the environment variables for all nodes.

docker-machine version 0.6.0-rc1, build 174e390

I tried this at my setup. It works fine.
Please confirm, if  --swarm-discovery option has correct value while creation.
NAME          ACTIVE      URL          STATE     URL                         SWARM             DOCKER   ERRORS
default       -           virtualbox   Running   tcp://<IP_ADDRESS>:2376                     v1.9.1
node1         * (swarm)   virtualbox   Running   tcp://<IP_ADDRESS>:2376   node2 (master)    v1.9.1
node2         -           virtualbox   Running   tcp://<IP_ADDRESS>:2376   node2 (master)    v1.9.1
node11        -           virtualbox   Running   tcp://<IP_ADDRESS>:2376   node12 (master)   v1.9.1
node12        -           virtualbox   Running   tcp://<IP_ADDRESS>:2376   node12 (master)   v1.9.1
node13        -           virtualbox   Running   tcp://<IP_ADDRESS>:2376   node12            v1.9.1
swl-consul    -           virtualbox   Running   tcp://<IP_ADDRESS>:2376                     v1.9.1
swl-consul1   -           virtualbox   Running   tcp://<IP_ADDRESS>:2376                     v1.9.1

$ docker info
Containers: 4
Images: 2
Role: primary
Strategy: spread
Filters: health, port, dependency, affinity, constraint
Nodes: 2
 node1: <IP_ADDRESS>:2376
  └ Status: Healthy
  └ Containers: 2
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.1.13-boot2docker, operatingsystem=Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015, provider=virtualbox, storagedriver=aufs
 node2: <IP_ADDRESS>:2376
  └ Status: Healthy
  └ Containers: 2
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.1.13-boot2docker, operatingsystem=Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015, provider=virtualbox, storagedriver=aufs
CPUs: 2
Total Memory: 2.043 GiB
Name: node1

$ eval $(docker-machine env --swarm node11)

$ docker info
Containers: 8
Images: 10
Role: primary
Strategy: spread
Filters: health, port, dependency, affinity, constraint
Nodes: 3
 node11: <IP_ADDRESS>:2376
  └ Status: Healthy
  └ Containers: 4
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: environment=production, executiondriver=native-0.2, kernelversion=4.1.13-boot2docker, operatingsystem=Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015, provider=virtualbox, storage=ssd, storagedriver=aufs
 node12: <IP_ADDRESS>:2376
  └ Status: Healthy
  └ Containers: 2
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: environment=lab, executiondriver=native-0.2, kernelversion=4.1.13-boot2docker, operatingsystem=Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015, provider=virtualbox, storage=hdd, storagedriver=aufs
 node13: <IP_ADDRESS>:2376
  └ Status: Healthy
  └ Containers: 2
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 1.021 GiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.1.13-boot2docker, operatingsystem=Boot2Docker 1.9.1 (TCL 6.4.1); master : cef800b - Fri Nov 20 19:33:59 UTC 2015, provider=virtualbox, storagedriver=aufs
CPUs: 3
Total Memory: 3.064 GiB
Name: node11

@kunalkushwaha are you using docker-machine version 0.6.0-rc1?  Yes, swarm-discovery was set for the daemons.
$ docker-machine ls
NAME           ACTIVE      URL            STATE     URL                          SWARM              DOCKER        ERRORS
default        -           virtualbox     Stopped                                                   Unknown
swarm-node-0   -           digitalocean   Running   tcp://<IP_ADDRESS>:2376   test2-1 (master)   v1.9.1
swarm-node-1   -           digitalocean   Running   tcp://<IP_ADDRESS>:2376   test2-1            v1.9.1
swarm-node-2   -           digitalocean   Running   tcp://<IP_ADDRESS>:2376   test2-1            v1.9.1
test2-1        * (swarm)   digitalocean   Running   tcp://<IP_ADDRESS>:2376   test2-1 (master)   v1.10.0-rc1
test2-2        -           digitalocean   Running   tcp://<IP_ADDRESS>:2376   test2-1            v1.10.0-rc1
test2-3        -           digitalocean   Running   tcp://<IP_ADDRESS>:2376   test2-1            v1.10.0-rc1
test-1         -           digitalocean   Running   tcp://<IP_ADDRESS>:2376   test2-1 (master)   v1.10.0-rc1
test-2         -           digitalocean   Running   tcp://<IP_ADDRESS>:2376   test2-1            v1.10.0-rc1
test-3         -           digitalocean   Running   tcp://<IP_ADDRESS>:2376    test2-1            v1.10.0-rc1

[test2-1]$ docker-machine version
docker-machine version 0.6.0-rc1, build 174e390

[test2-1]$ docker info
Containers: 11
 Running: 0
 Paused: 0
 Stopped: 0
Images: 18
Role: primary
Strategy: spread
Filters: health, port, dependency, affinity, constraint
Nodes: 3
 test2-1: <IP_ADDRESS>:2376
  └ Status: Healthy
  └ Containers: 3
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 513.4 MiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.2.0-16-generic, operatingsystem=Ubuntu 15.10, provider=digitalocean, storagedriver=aufs
  └ Error: (none)
  └ UpdatedAt: 2016-01-25T08:16:36Z
 test2-2: <IP_ADDRESS>:2376
  └ Status: Healthy
  └ Containers: 4
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 513.4 MiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.2.0-16-generic, operatingsystem=Ubuntu 15.10, provider=digitalocean, storagedriver=aufs
  └ Error: (none)
  └ UpdatedAt: 2016-01-25T08:17:09Z
 test2-3: <IP_ADDRESS>:2376
  └ Status: Healthy
  └ Containers: 4
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 513.4 MiB
  └ Labels: executiondriver=native-0.2, kernelversion=4.2.0-16-generic, operatingsystem=Ubuntu 15.10, provider=digitalocean, storagedriver=aufs
  └ Error: (none)
  └ UpdatedAt: 2016-01-25T08:17:01Z
Plugins:
 Volume:
 Network:
CPUs: 3
Total Memory: 1.504 GiB
Name: test2-1
WARNING: No oom kill disable support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No cpu shares support
WARNING: No cpuset support

[test2-1]$ eval $(docker-machine env --swarm test-1)

[test-1]$ docker info
Containers: 7
 Running: 0
 Paused: 0
 Stopped: 0
Images: 11
Role: primary
Strategy: spread
Filters: health, port, dependency, affinity, constraint
Nodes: 3
 test-1: <IP_ADDRESS>:2376
  └ Status: Healthy
  └ Containers: 3
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 519.2 MiB
  └ Labels: executiondriver=native-0.2, kernelversion=3.16.0-4-amd64, operatingsystem=Debian GNU/Linux 8 (jessie), provider=digitalocean, storagedriver=aufs
  └ Error: (none)
  └ UpdatedAt: 2016-01-25T08:17:41Z
 test-2: <IP_ADDRESS>:2376
  └ Status: Healthy
  └ Containers: 2
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 519.2 MiB
  └ Labels: executiondriver=native-0.2, kernelversion=3.16.0-4-amd64, operatingsystem=Debian GNU/Linux 8 (jessie), provider=digitalocean, storagedriver=aufs
  └ Error: (none)
  └ UpdatedAt: 2016-01-25T08:17:34Z
 test-3: <IP_ADDRESS>:2376
  └ Status: Healthy
  └ Containers: 2
  └ Reserved CPUs: 0 / 1
  └ Reserved Memory: 0 B / 519.2 MiB
  └ Labels: executiondriver=native-0.2, kernelversion=3.16.0-4-amd64, operatingsystem=Debian GNU/Linux 8 (jessie), provider=digitalocean, storagedriver=aufs
  └ Error: (none)
  └ UpdatedAt: 2016-01-25T08:17:52Z
Plugins:
 Volume:
 Network:
CPUs: 3
Total Memory: 1.521 GiB
Name: test-1
WARNING: No oom kill disable support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No cpu shares support
WARNING: No cpuset support

Earlier test with dev build, but verified again with version 0.6.0-rc1. It works.
You may see if settings for discovery is correct in swarm-agent-master container.
I had also faced similar issue earlier, While debugging I realised, I made mistake in swarm-discovery settings.

Okay, could it be that my client is the OSX client?
How go you verify the settings for discovery other than confirming that all nodes expected show up in docker info which they do?   I've inspected the CMD passed to the swarm-agent and swarm-master and they appear correct, referencing the local consul agent for the consul cluster that they are part of.  There is no chance of a cross-over as each consul cluster has a different encryption key limiting who can connect.

You are right, discovery must be correct in your setup, as cluster is setup correctly. docker info verifies that.
If possible, you may try with virtualbox once.
To verify you may also use
$ docker $(docker-machine config swarm-node-0) inspect swarm-agent | grep consul
$ docker $(docker-machine config test2-1) inspect swarm-agent | grep consul
$ docker $(docker-machine config test-1) inspect swarm-agent | grep consul

I am not sure, if it has to do anything with client (OSX vs Windows) as code is same for both .
While creation, it fetches the discovery from command line options https://github.com/docker/machine/blob/master/commands/create.go#L162-L194
and save it with host information https://github.com/docker/machine/blob/master/commands/create.go#L216-L236
While docker-machine ls, it retrieve host information and retrieve Discovery info. https://github.com/docker/machine/blob/master/commands/ls.go#L135-L166
For above code, racing cannot be problem, none of code run in parallel.

@BrianAdams did you sort out your issue? Our tests show that everything is ok.

Please re-test and file a ticket if you continue to experience issues.  Thanks @BrianAdams


Tree item dark mode visibility problem

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.
The menu items weren't clearly visible in "Dark Mode"
Here is the diff that solved my problem:
diff --git a/node_modules/strapi-plugin-menus/admin/src/components/TreeMenuItem/styled.js b/node_modules/strapi-plugin-menus/admin/src/components/TreeMenuItem/styled.js
index 8ff5674..9931143 100644
--- a/node_modules/strapi-plugin-menus/admin/src/components/TreeMenuItem/styled.js
+++ b/node_modules/strapi-plugin-menus/admin/src/components/TreeMenuItem/styled.js
@@ -16,6 +16,7 @@ export const Wrapper = styled( Box )`
   cursor: pointer;
   position: relative;
   z-index: 2;
+  color: ${({ theme }) => theme.colors.neutral800};

   ${({ theme, hasErrors, isActive }) => {
     if ( isActive ) {

This issue body was partially generated by patch-package.

Hi @mehrad-meraji Thanks for submitting this issue! 👍🏻  I have included your dark mode suggestion into the latest v1.0.1 of this plugin.


Changing ValueError to ArgumentError in MineSweeper

Fixing #778: Minesweeper test now listens for ArgumentError instead.

Whooops

My editor and silver searcher hid the .meta directory from me. Now I know!

Thanks @abeger :heart:


Maybe sharper egui soon

See notes in #215
Still not solved but colors are closer. Will keep looking into it

investigation progress: https://github.com/kvark/blade/issues/215#issuecomment-2525298153

Just a note, my approach for the investigation was to minimize differences between blade and egui-wgpu, so I made sure to try and replicate the code.
Once we find the issue we can go back and make only minimal changes :)

Closed by #217 and the separate samplers is superseded by #218


fix(structured-list): fixed column header text size

Addressing this issue: https://github.com/carbon-design-system/design-system-website/issues/183
Changed the header size from zeta (14px) to omega 12px
my first PR in carbon-components 😝

@asudoh deleted the file. Thanks!


enable hyperscale

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[x] The relevant Azure service or technology.
[x] A link to the published documentation article that you have feedback about.
[x] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[x] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[x] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

can i enable hyperscale

@BertAnthonyRochester are you referring to Azure SQL Hyperscale? Are you attempting to apply hyperscale to an existing instance?

@BertAnthonyRochester Please elaborate your question or provide documentation page you are referring to take this issue forward.

@BertAnthonyRochester We are going ahead and closing this issue for now. If you need more help with this issue, please get back to us.


xarray

Is your feature request related to a problem? Please describe.
Currently, data variables are stored directly under the model class.  While the 0.1.0 code has unique number of points in each dimension, this may not always be the case.
Describe the solution you'd like
A migration to an xarray dataset would allow for a more self-consistent data access, and could be better compatible with pysat.  Also allows easy sorting of data by solar local time.

Another nice thing about xarray is bounded nearest neighbor interpolation for time. Since distinct instruments don't observe with exactly the same cadence. The "bounded" is from you can set a maximum timedelta so that you don't have a nearest neighbor from an excessive amount of time away  (accidentally loaded file for one sensor from wrong year or month for example)

Closing with merge of #75.


Request lsp.mdx_analyzer

Add support for https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#mdx_analyzer
As this will allow nix users to use the mdx lsp for mdx projects.

I am looking to make a pr, but I am waiting on a package.


invalid json in example

Hi,
https://github.com/MicrosoftDocs/azure-docs/blame/master/articles/virtual-machines/extensions/custom-script-linux.md#L91
the "," needs to be removed
greetings
klaas

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: df5a8957-9b4c-2a2e-81c2-79125373f8f1
Version Independent ID: d1c2d4cf-88cd-7581-10b5-88a5d11986e6
Content: Run custom scripts on Linux VMs in Azure
Content Source: articles/virtual-machines/extensions/custom-script-linux.md
Service: virtual-machines-linux
GitHub Login: @roiyz-msft
Microsoft Alias: roiyz

Thanks for the feedback! We are currently investigating and will update you shortly.

@Klaas- thanks for the find! I have corrected the doc. Once the PR merges the changes will go live in a few hours.


improve tabular model

Implement Tabular.points as a tuple.
Merge after astropy/astropy#5417 and spacetelescope/asdf-standard#133

Coverage decreased (-0.003%) to 93.709% when pulling 803db4c35442a98b7c82d0af8fbf0ad76b1975f8 on nden:fix-tabular into 5fc5720a9eb1d0006c40e54d0457440329096aed on spacetelescope:master.

Not sure why coverage decreased by .003 %. Tests are passing so ...merging.

"Not sure why coverage decreased by .003 %." Because the number of lines not being tested has increased due to the fact that the case when dim > 2 is not being tested at all.

That case was there before. And coverage is supposed to test the "relevant" lines (whatever that means).