Consider a custom generator for .dart_tool/package_config.json in engine/tools/...

My proposal is to roll our own .dart_tool/package_config.json, or something the Dart team might have developed for their own mono repos, instead of using dart pub get with a lot of confusing constraints.
Background
The engine nominally uses pubspec.yaml files to define repository-private Dart packages:

We add a scary message to most of them:
# Do not add any dependencies that require more than what is provided in
# //third_party/pkg, //third_party/dart/pkg, or
# //third_party/dart/third_party/pkg. In particular, package:test is not usable
# here.

# If you do add packages here, make sure you can run `pub get --offline`, and
# check the .packages and .package_config to make sure all the paths are
# relative to this directory into //third_party/dart

... and use quasi-custom tooling to enforce that all paths come from local dependencies.
Developing these packages, updating the pubspec, is cumbersome, because we need to (manually) iterate out all transitive dependencies via dependency_overrides and point to a confusing matrix of local dependencies. For example, dir_contents_diff:
dev_dependencies:
  litetest: any
  path: any
dependency_overrides:
  async_helper:
    path: ../../../third_party/dart/pkg/async_helper
  expect:
    path: ../../../third_party/dart/pkg/expect
  litetest:
    path: ../../testing/litetest
  meta:
    path: ../../../third_party/dart/pkg/meta
  path:
    path: ../../../third_party/dart/third_party/pkg/path
  smith:
    path: ../../../third_party/dart/pkg/smith

See https://github.com/dart-lang/sdk/blob/main/tools/generate_package_config.dart for what the Dart SDK does. It isn't hard to generate your own package config.
I do think it can be problematic to have both pubspec.yaml files and a custom package config. It allows you to run a pub get in those packages and override the higher level package configuration.
Some considerations:

Do you use dart test? This requires a pubspec and will do a pub get whether you want it to or not.
Would you ever want to publish any of these packages, or any package in the future set up in a similar way? Then you need pubspecs.
If you can reliably only have one package config, at the root of your repo, shared by all packages, this will also improve your IDE experience significantly due to having only one analysis context.

Thanks @jakemac53!

Do you use dart test?

No, but I want to. Is there a path to using this without pub get being required?

Would you ever want to publish any of these packages

No, or at least, I could say not the foreseeable future.

If you can reliably only have one package config, at the root of your repo, shared by all packages, this will also improve your IDE experience significantly due to having only one analysis context

Define one, is it possible to have one but like, web_ui perhaps does their own thing?
Or do we need 100% consensus across the repo?

No, but I want to. Is there a path to using this without pub get being required?

It should be possible to at least add a flag to skip the pub get step. I don't think one exists today, and I don't think that would be a good solution (you would still have to know to pass that flag, and remember to, etc).
Maybe a special configuration in the pubspec.yaml or something would work. See also https://github.com/dart-lang/pub/issues/4022 which is generally related to this issue I think.

No, or at least, I could say not the foreseeable future.

Just note that it might make that harder 🤷. It is best to just be as typical of a package as possible if publishing to pub.

Define one, is it possible to have one but like, web_ui perhaps does their own thing?

Package configs are resolved by looking at the root script uri and the walking up directories searching for .dart_tool/package_config.json files. So yes you could have one at a high level (probably root of the repo) which is the "default", and then override that in subdirectories. (this is why running pub get is problematic, it becomes the higher priority one).

Thanks so much! @jakemac53 Based on what you know so far, do you think this issue is worth resolving?

/cc @zanderso - I am going to send Zach a "test" PR to see if this works like we imagine it would.

I think this was a cool idea, but given what Jake said and the weirdness around analysis I wouldn't consider it solving a problem.


Detail the deprecation of mplex

Ref: https://github.com/libp2p/specs/issues/553
libp2p implementations are in the process of deprecating mplex (in favor of yamux or transports with built in mplexing like QUIC) - this blog post should detail the motivations and describe historical reasons for supporting mplex this long

Good idea! @p-shahi, could you draft something? Would be nice to get this blog post out pretty soon.


Resource hub: add "Results" heading to the search results

Once a search is done, add a "Results" or "Search results" heading to the content area in the resource hub. So screen reader users can directly navigate to the results.

Resolved in #1383.


Boosting: Better formalization of the exponential loss in boosting

We should add the loss L(...) = ... and with that the empirical risk R_emp = sum L(..) not just a formula with exponential loss is used here

This is now commented out in slides-boosting-gbm-with-tress-2.tex see also https://github.com/slds-lmu/lecture_cim2/pull/678/files


Currency system

Enemies now drop coins when they are killed.
Description

Enemies drop a random amount of coins between 2-4 (adjustable in Enemy.cs). There are three different values of coins: small, medium, and large, worth 10, 20, 30 moneys. The value of the coins is adjustable in an enum in Coin.cs. The amount of money the player has is kept track of underneath the health text on the UI. Enemy prefabs now have a BaseCoin attached to them, as well as an enum value representing their worth in coinage. The BaseCoin is changed in color depending on the value of the coin that the enemy should drop. I assigned goons small value, ranged enemies medium value, and spawners large value, but this can be adjusted easily in their prefabs.
Related Task

https://app.clickup.com/t/8678th4pn
Testing

I tested my changes in my CarsonCurrencyScene, and in the TemplateScene before it was outdated, then the MainRoomTemplate scene. I made sure each enemy type dropped the correct color and value of coins, and that they only dropped between 2 and 4 coins.
Screenshots (if appropriate):
After killing a ranged enemy and a goon:

After picking up the coins:

YAYY LOOKS GOOD ty carson!!


10xdev.cc — removed redundant http headers...

...and optimized html/css code.
https://tools.pingdom.com/#60c9f8acf9800000

Sorry but I have actually removed this website (and a few others) for falling under the "ultra minimal" category.

Ok, thanks for the feedback 🙃


remnux upgrade/update is failing (Bad signature for DeXRAY.pl)

Hello,
During upgrade/update, the script is failing after the verification of signature for DeXRAY.pl.
In sls definition [https://github.com/REMnux/salt-states/blob/master/remnux/scripts/dexray.sls] the signature for DeXRAY.pl is 9f314060960677a2c5feefe4e458a17a28694d4f38c05d3be8fe3db612829371.
But if you download this file, the signature is 5a2759d89d8351a5728ce8eceb93db7bac80b062889f2d4ed33b2690303e4249.
Regards,
Bruno

@gloumps Good catch, thank you for noticing. Pull request #143 (referenced above) will resolve this.


Introduce 5 icons to be used for status of canvas apps offline sync.

✅ No public API change.

✅ No public API change.


tmpreaper for formplayer

@javierwilson @emord i tried using tmpreaper for this. i tested on staging doing tmpreaper  7d /opt/data/formplayer and checked the conf to make sure it updated correctly. i'm a little worried that using tmpreaper is too blunt. if formplayer gets deployed to a machine that needs a different config for tmpreaper than i'm not sure how we do that. this may make sense to use our old cron way of killing old files. what do you think?
cc: @proteusvacuum

Maybe we'll have to add it to the inventory file? Is there a way to use different tmpreaper settings per folder?

it wasn't obvious to me if it does exist. according to this: https://github.com/ANXS/tmpreaper. you just set some variables and those variables get written to /etc/tmpreaper.conf

I think I'm going to change this back to our old way of deleting files for the above reasons. @javierwilson that OK with you?

I think the global tempreaper.conf config will not help here, however, you can still use tmpreaper instead of "find", it has some advantages over find.
So maybe just add the cron task but use the command: "tmpreaper 1d {{ encrypted_root }}/formplayer"
To delete files older than 1 day.

ok switched to tmpreaper. the cron looks like this in check mode:
+#Ansible: Purge sqlite db files
+@daily root tmpreaper /opt/data/ecrypt/formplayer 2d

changed: [<IP_ADDRESS>] => (item={u'time_spec': u'2d', u'name': u'Purge sqlite db files', u'dir': u'/opt/data/ecrypt/formplayer'})

small change...

small but big. thanks, i've been running it manually and for some reason didn't catch that


Decide on a policy for updating latest

It could be done on any successful PR to master, but we really want it to happen only after the PR is approved. I'm not sure if there's a good hook for that. Even if there were, maybe it should be a manual process to update latest? ie, only formal releases get that, not every PR.
@pkerpedjiev : policy question for you, but the best answer will probably be more clear with experience.

We think it will be: If there's a tagged release on gitub, then tag it on dockerhub, and update latest.

actually, just put the instructions up for doing it by hand.


add logging overriding

sometimes its nice to have your custom logging in fastapi so i added passing it to uvicorn and fallbacking to uvicorn default  one if nothing is passed in

+1

+1

+1

+1

@wchaws i do not have rights to add lablel and it is failing on the check... if you have some elevated rights or know someone who has i would like you to add tag feature and  rerun test.
thanks

@07pepa  I'm not the maintainer for this project. I just accidentally approved this PR.

+1

Is this PR just missing label "feature"? @07pepa @wchaws Are you able to add it?
Thanks

Is this PR just missing label "feature"? @07pepa @wchaws Are you able to add it?
Thanks

Yes i am unable as author of PR to change/add  label. Label is only thing that is missing.
i tried even modifying labeler and no luck  https://github.com/fastapi/fastapi-cli/pull/110
we probably need to ask @tiangolo how to do this (or to add label)

+1


Bot Offline

Hi there,
I'd love to try out this bot, but it appears to be offline. Is this project still running?
Thanks!

Hii! It's no longer running :( Feel free to download the project and run it on your own database / server :D


[ML] Updated "Validation for Schema" error messages

Description
Changed the error message template for Validation For Schema Failed error for all 7 error cases
Previous error message for MISSING_FIELD example:
Error: The yaml file you provided does not match the prescribed schema for  yaml files and/or has the following issues:

At least one required parameter is missing

Details: Validation for   failed

Resolutions:
Ensure all parameters required by the   schema are specified.
If using the CLI, you can also check the full log in debug mode for more details by adding --debug to the end of your command
Additional Resources: The easiest way to author a yaml specification file is using IntelliSense and auto-completion Azure ML VS code extension provides: https://code.visualstudio.com/docs/datascience/azure-machine-learning. To set up VS Code, visit https://docs.microsoft.com/azure/machine-learning/how-to-setup-vs-code
New error message:
The yaml file you provided does not match the prescribed schema for Data yaml files and/or has the following issues:
Error:
1.) The yaml file provided is missing one or more required parameters.
Details: Validation for DataSchema failed
(x) path:

Missing data for required field.

Solution:
1.) Add the missing parameters with values of the correct type. To know what type of value to assign to any required parameter,
Visit this link to refer to the Data schema if needed: https://aka.ms/ml-cli-v2-data-yaml-reference.
If using the CLI, you can also check the full log in debug mode for more details by adding --debug to the end of your command
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


[Bug]: When unknown browser version used, all polyfills are added to the bundle

Version
System:
    OS: macOS 14.6.1
    CPU: (11) arm64 Apple M3 Pro
    Memory: 874.61 MB / 36.00 GB
    Shell: 3.7.1 - /opt/homebrew/bin/fish
  Browsers:
    Chrome Canary: 133.0.6860.0
    Safari: 17.6
    Safari Technology Preview: 18.0
  npmPackages:
    @rsbuild/core: ^1.1.4 => 1.1.6

Details
First of all, I'm sorry if it's a bug in Rspack or SWC - I use RSBuild (and I love it ❤), I didn't check if the issue occurs in these tools. A quick search across all three issue trackers doesn't reveal already known bug.
The issue is when I use a browser version unknown for RSBuild in my .browserlistrc, instead of adding no transipilation and polyfills (this is the default @babel/preset-env behavior), everything is transpilled and polyfilled. That's a bit unfortunate, as the browserslist-rs tool used under the hood recognizes only browsers released before June 2024. I've already submitted a PR updating the data in that repo. I'm afraid changing how to handle defaults it's beyond my Rust knowledge 😅
Reproduce link
https://github.com/erykpiast/rsbuild-test
Reproduce Steps

Install the dependencies:
pnpm install

Build the app for production:
pnpm build

Observe the JavaScript output artifact contains the generator polyfill.

Go to the .browserslistrc file and change the Chrome version to 125.

Build the app for production:
pnpm build

Observe the JavaScript does not contain any polyfill.

Thanks for your feedback! Rsbuild should ignore unknown values like Babel does. We will fix this issue soon.

I think this is a SWC issue.
When you pass in the browserslist (targets) array, it should contain at least one recognized value. If all values are unknown, SWC will use the default browserslist (seems to be ES5).

SWC + Chrome >= 130: https://play.swc.rs/?version=1.9.3&code=H4sIAAAAAAAAA0vOzysuUchPylKwVajmUlDQ09MDcox0uGoBdJ5oUBoAAAA%3D&config=H4sIAAAAAAAAA3VRQYrDMAy89xVG5x627K2HQukD9gFLWYyttC6yHSwnNJT8vYpJ3aSwPlkzo7E0fmyUAu%2BCawbYq0YT43aCMPRSP%2BQqRdbpgpkF%2BIXTNUWP6qB2319wFn4s%2Bhubt75NyJh6PBKdovcYSm9OXfGeBDqJoDYIwkPI%2Bi4IoPGaTXJthu2LvfF9NijIONvUuauN1%2BFCuNykwE1MXueF8HVAnnLuJ9Dw2SOcec8OLEvDTI3VVxTTrrxyBouN7qj0fVjOgi50jHYVyYK1qO2fiRb%2FE%2BTYEvZIy0hkqlU0FCPXHKZf2oxPuR%2FOf%2BsBAAA%3D

SWC + Chrome >= 100: https://play.swc.rs/?version=1.9.3&code=H4sIAAAAAAAAA0vOzysuUchPylKwVajmUlDQ09MDcox0uGoBdJ5oUBoAAAA%3D&config=H4sIAAAAAAAAA3VRQY7CMAy884rIZw7sdQ9IiAfwALRaRYkLQU5SxWlFhfp33KiEFomc4pnxxJ48NkqBd8E1A%2FyqRhPjdoIw9FI%2F5CpF1umCmQU4w%2FGaoke1Vz%2B7HfwJPxb9jc1b3yZkTD0eiI7RewylN6eueE8CnURQGwThIWR9FwTQeM0muTbD9sXe%2BD4bFGScberc1cbrcCFcblLgJiav80L4OiBPOXcKNHz2CGfeswPL0jBTY%2FUVxbQrr5zBYqM7Kn0flrOgCx2jXUWyYC1q%2B2%2BixW%2BCHFvCHmkZiUy1ioZi5JrD9Eub8QlfI6GU6wEAAA%3D%3D

Considering this an upstream issue, I will close the current issue.
Feel free to create an issue for SWC to discuss this.

Gotcha, thanks for checking that.
I've reopened the discussion here https://github.com/swc-project/swc/issues/9778.


Cannot use import statement outside a module

Hello,
I have this error on my monorepo next js / expo project using next on the web and your package.
Cannot use import statement outside a module
Would you know how to fix this ?
Object.<anonymous>
file:///var/www/node_modules/rn-responsive-styles/lib/index.js (4:24)
Module._compile
node:internal/modules/cjs/loader (1103:14)

Thank you

I managed to fix the issue by using next-transpiles-modules on your package in next.config.js :
const withTM = require('next-transpile-modules')([
    'rn-responsive-styles',
]);

@JinbeiStudio Yes that would be the correct way to handle this package with a nexpo monorepo


[JAVA-3814] Supports BsonIgnore annotation for scala driver

Link to JIRA issue here
Goal is to support BsonIgnore annotation for scala driver in order to ignore some fields during bson serialization which are not meant to be Options
ie:
case class Person(firstname: String, lastname: String, @BsonIgnore metadata: Seq[Metadata] = Vector())

Tests have been added to the MacrosSpec

Hi @rozza @jyemin,
First, I am sorry to tag you directly, but it looks like you're the developers of this repository.
I would just like to know if this PR will be reviewed / merged at some point, if I did something wrong in it (I can see in CONTRIBUTING.md that it can be ignored for some reasons), or simply if this kind of feature is not desired in the library.
Thank you

Hi @gael-ft thanks for the PR and the nudge!
Apologies for not responding sooner, this looks really good, I've scheduled it for the 4.2 release and will review and merge in due course.
All the best,
Ross

Hello @rozza,
I can see there is a 4.2.0-beta1 ongoing, did you have time to review this PR ?
Do you think it could be integrated in the 4.2.0 ?
Thanks

Hello @rozza,
I can see there is a 4.2.0-beta1 ongoing, did you have time to review this PR ?
Do you think it could be integrated in the 4.2.0 ?
Thanks

Hi @gael-ft, happy new year. Just to let you know I plan to review with a mind to merge this week.

Hi @gael-ft, happy new year. Just to let you know I plan to review with a mind to merge this week.

Ok @rozza, thank you.
(My apologizies, for the previous message, happy new year too !)

Ok @rozza, thank you.
(My apologizies, for the previous message, happy new year too !)

Thanks @gael-ft this has now been merged to master.

Thanks @gael-ft this has now been merged to master.


Avoid recursion in dask.core.get

Instead we use a topological sort
This cleans up tracebacks and profiling a bit when we have large complex
tasks or graphs (as we sometimes do when fusing many sequential tasks
together)

[x] Tests added / passed
[x] Passes flake8 dask

cc @jcrist (no rush)

Has this been benchmarked? Feels like a pretty fundamental change that could benefit from that sort of thing.

I have some comments on this, but am traveling all day. Should have time to review tomorrow.

This is only to clean up tracebacks/profiling information then?

I think that it's also a simpler implementation and reduces complexity.  It also marginally improves performance over master, but I don't think that matters that much.

In that case, would we want to reconsider #4091 again, as it also solves those problems with no performance overhead (and some mild speedup)?

I think that my concerns with that PR continue to hold.  It introduces additional complexity without a meaningful return on performance.  (at least not meaningful on current workloads as I see them).

@jcrist is there anything further to do here?

@jcrist ok to merge?

LGTM, merging.


Different simulation results (speeds) across Linux & Windows.

-- Background --
I've used Box2D for a long time now, without even realizing I was using it. Various Game Engines and SDKs utilize Box2D under the hood and as such I know that Box2D is deterministic in nature, but suffers from the same floating-point precision errors as any other floating-point physics library. However, these errors are very insignificant when used in combination with things such as reconciliation with tolerations slightly above an Epsilon.
I developed a project for a client using Planck over the last few weeks as they wanted a JavaScript based server & client that could easily implement things such as prediction & reconciliation. These are fairly trivial and simple tasks.
-- Environmental Information --
However, while everything was working fine for us inside of our windows environments, once we moved the server to Ubuntu 20.04 we noticed from fairly serious issues in how things are simulated. (Ubuntu client & server) I've used Node 12.22.1, Node 14.16.1, and Node 16.0.0 to test this issue.
-- Issue Information --
When two objects are given an exactly similar Linear Velocity and Spawn Location they take completely different amount of time to traverse the same amount of space. Tests indicate that the difference in object speed is roughly 12%. These tests run on the same codebase in both environments and can be replicated as simply as creating an Object/Fixture. Setting normal gravitational forces (x0, y9.82), and creating a Dynamic Rigidbody w/ a Box Fixture and setting the Linear velocity directly to any number. For our tests we used x:-1, y:-0.5. We then timed the amount of time it took for each object to move across the screen. Each object moved consistently inside of its own operating system, but inconsistently (by a rather large margin) between multiple systems.

I doubt that 12% is result of floating point. I remember you previously reported an issue which was related to different game loop frame rates in different environments, have you checked if that's also the issue in this case?

The mentioned issue was regarding an irregular refresh rate (300.180hz) that only caused problems on the testbed. This is an issue that occurs in production (on the server) and as such there is no refresh rate that can be the issue, the server is manually configured to run at 60hz although I have also done tests at 50hz and 30hz. I've run this simulation using other implementations (external to Javascript) without any difference in timing. The server has been debugging on both Windows & Linux to ensure that they are running at the proper hz/intervals. I will be writing a test using a different implementation of Box2D after the weekend and logging the results as well, although I have never seen any differences.

@ChristianTucker did you ever get a solution on this? And if not, did you find another suitable JS physics engine?

I'm currently trying to resolve known issues before releasing v1. I wonder if you could provide any code example to reproduce this issue?


ARROW-8467: [C++] Fix TestArrayImport tests for big-endian platforms

This PR fixes two problems.

DecodeMetadata() always assume that a length of metadata is stored in a little-endian format. According to this specification, the length is stored in a native endianness. This causes the following failure. This PR makes the interpretation of the length correct.

12: [ RUN      ] TestSchemaImport.Struct
12: /home/ishizaki/Arrow/arrow/cpp/build-support/run-test.sh: line 92: 19528 Segmentation fault      (core dumped) $TEST_EXECUTABLE "$@" 2>&1
12:      19529 Done                    | $ROOT/build-support/asan_symbolize.py
12:      19530 Done                    | ${CXXFILT:-c++filt}
12:      19531 Done                    | $ROOT/build-support/stacktrace_addr2line.pl $TEST_EXECUTABLE
12:      19532 Done                    | $pipe_cmd 2>&1
12:      19533 Done                    | tee $LOGFILE

primitive_buffers_... used in TestImportArray implicitly assumes little-endian. The following is an example.

static const uint8_t data_buffer1[] = {1, 2,  3,  4,  5,  6,  7,  8,
                                        9, 10, 11, 12, 13, 14, 15, 16};
static const void* primitive_buffers_no_nulls1[2] = {nullptr, data_buffer1};
...
 TEST_F(TestArrayImport, PrimitiveWithOffset) {
   ...
   FillPrimitive(3, 0, 1, primitive_buffers_no_nulls1);
   CheckImport(ArrayFromJSON(uint16(), "[1027, 1541, 2055]"));

The above code works since 03 04 05 06 07 08 is interpreted as 0x0403 (=1027), 0x0605 (=1541), and 0x0807 (=2055) on a little-endian platform. It is interpreted as 0x0304, 0x0506, and 0x0708 on a big-endian platform. This causes the following failure. The PR prepares data_buffer for each type on both endians.
12: [ RUN      ] TestArrayImport.PrimitiveWithOffset
12: /home/ishizaki/Arrow/arrow/cpp/src/arrow/testing/gtest_util.cc:77: Failure
12: Failed
12:
12: @@ -0, +0 @@
12: -1027
12: -1541
12: -2055
12: +772
12: +1286
12: +1800
12: Expected:
12:   [
12:     1027,
12:     1541,
12:     2055
12:   ]
12: Actual:
12:   [
12:     772,
12:     1286,
12:     1800
12:   ]

AppVeyor failure was unrelated, I restarted it.

I see. Thanks.


Check Configuration won't finish after adding O365-HomeAssistant

Hello,
I'm excited to use this integration. Unfortunately, after I added the configuration to configuration.yaml, the Home Assistant Configuration Check in Developer Tools enters an endless loop and never finishes checking the YAML. Since I can't see if it succeeds or fails, I'm worried about proceeding with a restart to finish setup.
I've tried using both the primary and secondary configuration formats, as well as varying the number of accounts and even stripping out everything except the account_name, client_id, and client_secret. Nothing seems to prevent the endless loop in the config check. But if I remove the "o365" config from config.yaml and then refresh it instantly succeeds.
o365:
accounts:
- account_name: personal
client_id: "redacted"
client_secret: "redacted"
- account_name: work
client_id: "redacted"
client_secret: "redacted"
(I can't get the indentation to appear correctly in this post, but it matches the documentation exactly.)
Is this a known issue? Any suggestions for how to fix it?
Thanks in advance for your help!

Please use the Add code (<>)tool to properly format anything you post. I assume it looks like this:
o365:
  accounts:
    - account_name: personal
      client_id: "redacted"
      client_secret: "redacted"
    - account_name: work
      client_id: "redacted"
      client_secret: "redacted"

I wouldn't ever expect your config checker to loop. I would remove the config, then restart (because you need to have done that before adding the config anyway). Beyond that I really don't know. I'd suspect it is something to do with your setup, but of course you never know.... But with approx 2k users out there, it hasn't come up before.

Also worth stating what version you have installed.

Thanks for the quick reply. After banging my head against the wall for over an hour trying to figure out why it wouldn't work, it turns out the cliche restart fixed it. It must have just been a weird bug in Home Assistant. Thanks!

Thanks for the quick reply. After banging my head against the wall for over an hour trying to figure out why it wouldn't work, it turns out the cliche restart fixed it. It must have just been a weird bug in Home Assistant. Thanks!

I had exactly the same problem - configuration check would result in endless spinner. I then found this ticket but was wondering what a "cliche restart" would be. For me it turned out that performing a full restart of the system (not only a Home Assistant restart) was doing the trick. So if anyone has the same issue - just click on the red button, not the yellow one (sorry for the German labels but I think if you just follow the color of the button you should find the right button in any language):


Using the Ws2812 PIO example on a Ws2811

Hi - Im trying to get the Ws2812 PIO example working using these leds:
https://www.pololu.com/product/2535
I tested one with the Adafruit_Neopixel arduino sketch running on a Pi Pico - the LED is powered from 5V and Im translating the 3.3V logic to 5V with a 74HCT245.
I'm able to control the RGB values of the LED and it behaves as expected.
However when using the PIO example the LED only switches between various intensities of red.
If instead of pushing u32 values into the FIFO I push u8 I am also able to control green and blue, but not red:
pub async fn write_direct(&mut self, words: &[u8]) {
        self.sm.tx().dma_push(self.dma.reborrow(), words).await;
    }

I think the issue is either in:

The Ws2811 timings are different - I tried extending the data bit cycle but it had no effect. Not sure why the NeoPixel library worked if this is the case though.
I am misunderstanding the FIFO behavior as its implemented in the example. Why does the word size matter here? Perhaps its affecting the framing somehow?

Any help would be greatly appreciated

The first difference between the ws2812 and ws2811 is that the 12 expects the color in GRB order and the 11 expects RGB. That difference would mess with your colors, but doesn't fit the issue you're describing. To change this, r and g need to be swapped on line 104, like so:
let word = (u32::from(colors[i].r) << 24) | (u32::from(colors[i].g) << 16) | (u32::from(colors[i].b) << 8);

Different bit timings might explain the issue you're seeing. There are several datasheets for the ws281x family, and the timings are all slightly different, except that the total bit time is the same. In the pio program we divide that time up into T1, T2, and T3, and they need to add up to 10 for the total time to be correct. The specific timings in the example come from the ws2812 example in the rp2040 datasheet.
I played around with them a bit on the ws2812b's I have and found that several timings worked. T1=3 T2=4, and T3=3 is the closest to the 12b's datasheet values. I suspect the neopixel lib uses different sub-bit timings and that's why it worked. Alternately, do you specify the led type you're using?
The fifo is 32 bits wide, but is configured to shift out 24 bits (8 bits each of r, g, and b) before advancing to the next word, this is set with the threshold field of the ShiftConfig struct. Also, it shifts out left, that's why the colors are shifted 24, 16, and 8 bits, rather than 16, 8, and 0.
The ws281x series leds don't have any framing, other than the reset time being used to update the colors. You can think of the led string as a shift register, where you just shift the entire color string out then (with the reset time) update the entire string. If you shift out the wrong number of bytes, your colors will be interpreted wrong. I think if an individual LED gets less than 24 bits it treats the colors it didn't get as 0, but I'm not sure about that.

Thanks for the help.
These are the leds Im using:
https://www.pololu.com/product/2535
One datasheet for the WS2811 I took a look at does specify slightly different timings, but the product page shows the same ~1.2uS frame duration as you'd expect.
I took a look at the NeoPixel source code and it does indeed seem to use the same timings:
https://github.com/adafruit/Adafruit_NeoPixel/blob/master/rp2040_pio.h
Other than that, the only differences I could find is that the NeoPixel code sets the ShiftConfig threshold to 8 bits instead of 24, and uses 3 consecutive blocking writes instead of DMA - but I tried that on my LED and it has the same effect of just setting the red intensity.
What's really confusing me is that StateMachineTx<'d, PIO, SM>::push takes a u32 always but StateMachineTx<'d, PIO, SM>::dma_push is generic over the word size, and if I call dma_push with an array of u8's I can get only blue and green to light up, where as if I send it as a single u32 only red lights up at various intensities.
Just to illustrate - this is how I modified the write function (I realize this doesn't make sense for more than one led but thats what Im testing now):
    pub async fn write(&mut self, colors: &[RGB8; N]) {
        // Precompute the word bytes from the colors
        for i in 0..N {
            let words = [colors[i].g, colors[i].r, colors[i].b];
            // DMA transfer
            self.sm.tx().dma_push(self.dma.reborrow(), &words).await;
        }
    }
}

I also noticed just now that changing the ShiftConfig threshold causes the behavior to change - when changing the threshold to 8 I get different color combos - green and yellow, so this is definitely something to do with framing and timing, perhaps some issue with the way the FIFO is packed?
Should lowering the auto-pull threshold to 8 even make a difference? Doesn't it just mean the FIFO will be pulled 3 times instead of once for each LED? Or does the auto-pull cause a whole word to be read regardless of the actual threshold?

StateMachineTx<'d, PIO, SM>::push takes a u32

The fifo is 32 bits wide. If you want to squish smaller types into one word you have to do that in the CPU.

StateMachineTx<'d, PIO, SM>::dma_push is generic over the word size

I didn't write this, but I'm reasonably certain this is simply for convenience. No matter what type you send, each element takes it's own fifo slot. I suspect that the other bits are zeroed, but they might have random data.

Should lowering the auto-pull threshold to 8 even make a difference? Doesn't it just mean the FIFO will be pulled 3 times instead of once for each LED? Or does the auto-pull cause a whole word to be read regardless of the actual threshold?

The latter, the OUT instruction pulls some number of bits (1 in our case) out of the output shift register (OSR) into some destination (the X register in our case). The PULL instruction moves a word from the FIFO to the OSR. Auto pull does the same as a PULL instruction every threshold bits.
The ws2812 pio program simply takes the bits from the FIFO and serializes it according to the ws281x timings. This example, and the original example from the 2040 ds, pack the color data for an led into a word, using a single FIFO slot per led. The adafruit code uses a FIFO slot per byte of the rgb data, using 3 FIFO slots per led.
If your data is already organized in a big 1d array of [r1,g1,b1,r2,g2,b2,...] then it would be very natural to use DMA and the byte method, if your data is in some kind of rgb struct then it's a bit nicer to use the 24 bit method. Whichever you use, the ShiftConfig.threshold value will need to match the data you're putting in the FIFO.
The pololu documentation says these leds are configured to use the 800kHz/fast mode, but maybe they're actually 400kHz? Try changing ws2812_freq on line 79 to 400 and see if that fixes it. The way that you're getting some colors has me wondering if they're getting garbled data.

So after reading into the DMA code and datasheet - it seems that when DMA pushing partial words to the FIFO, the content will get replicated to fill the FIFO slot, which explains why the behavior is different, but I have no idea why in the full word case I'm only getting red.
The thing I still don't fully understand is the autopull behavior - if my threshold is 24 bits, that means that after 24 out x, 1 instructions the OSR will be filled with 32 bits from the next FIFO slot? What happens to the "remaining" 8 bits in the OSR? Are they overwritten?

I didn't know the DMA would replicate the data, that's certainly more useful than zeros or random data.
Yes, any time a PULL instruction (or an auto pull happens) a full word is written from the FIFO to the OSR.

Well, I finally gave in and hooked up a scope and saw that the timings were very slightly off.
I reduced the 1-bit duration by one cycle and the LED started behaving correctly, even though the timings were still not quite to spec.
Inexplicably - after having reverted to the original code, with the original timings - the LED now works perfectly fine!
I genuinely have no clue what could have caused the original issue, my only guess is breadboard voodoo 🤷
Sorry for the unscientific conclusion


Any type shadows type error in match expressions

Reproducing the behavior
Issue Description
When defining functions that operate on Maybe(A) types, the type checker seems to behave inconsistently, particularly when the unreachable() function is used in a pattern match. Here's an example to illustrate the problem:
Problematic Code
type Maybe(T):
  Some{val: T}
  None

def Maybe/bug(maybe: Maybe(A)) -> Maybe(A):
    match maybe:
        case Maybe/Some:
            return Maybe/Some(Maybe/Some(maybe.val))
        case Maybe/None:
            return unreachable()

def main():
    return Maybe/bug(Maybe/Some(12))

Result:
The above code executes without type errors, producing the following result:
λa (a Maybe/Some/tag λb (b Maybe/Some/tag 12))

This is unexpected, as the function violates the intended type constraints of Maybe(A).

Correct Behavior
When the function avoids using unreachable() and handles the Maybe/None case with a valid return, the type checker properly enforces the constraints, as seen in the code below:
type Maybe(T):
  Some{val: T}
  None

def Maybe/bug2(maybe: Maybe(A), x: A) -> Maybe(A):
    match maybe:
        case Maybe/Some:
            return Maybe/Some(Maybe/Some(maybe.val))
        case Maybe/None:
            return Maybe/Some(x)

def main():
    return Maybe/bug2(Maybe/Some(12), 24)

Result:
Running the above code correctly triggers a type error:
Type Error: Expected function type '((Maybe A) -> A -> (Maybe A))'
but found '((Maybe h) -> (Maybe h) -> (Maybe (Maybe h)))'.
Variable 'a' occurs in '(Maybe a)'

Analysis

Function with unreachable() (Maybe/bug): The type checker does not enforce type correctness, allowing invalid types to pass through and the function to execute.
Function without unreachable() (Maybe/bug2): The type checker properly identifies type mismatches and raises an error, preventing invalid behavior.

This inconsistency demonstrates that using unreachable() somehow bypasses type-checking mechanisms.

Expected Behavior
The type checker should raise an error for Maybe/bug, similar to the behavior observed in Maybe/bug2, since the return type violates the Maybe(A) constraint.

Steps to Reproduce

Define the functions Maybe/bug and Maybe/bug2 as described above.
Run the main() function for each case.
Observe the behavior:

Maybe/bug: No type error, invalid output.
Maybe/bug2: Type error, expected behavior.

System Settings
Environment:

HVM: [hvm 2.0.22]
Bend: [bend-lang 0.2.37]
OS: [Ubuntu 22.04.3 LTS]
CPU: [Intel i7-10700KF]
GPU: [RTX 2070]

Additional context
No response

It seems that the type checker is unifying the Any type of the unreachable too eagearly.
When checking a match, it infers the type of all match arms, unifies them all and then at the end unifies against the type annotation. Since Any forcefully casts everything into it, the incorrect type of the first arm (Maybe(Maybe(T))) is erased and replaced by Any which will type check without issues when unifiying against the Maybe(T) annotation.
A better checking algorithm would be to check each arm separately against the annotation, but that will require substantial changes to how the type checking algorithm is structured.


Fix parsing quoted strings (#20)

Fixes #20

[x] Add test for single-quoted string
[x] Fix parsing problem

Any changes needed before we can merge this?

Hey! Thanks for pinging again. LGTM!


ci: add downstream tests for marimo

What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[ ] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[x] ✅ Test
[ ] 🐳 Other

Related issues

Closes #1163

Checklist

[x] Code follows style guide (ruff)
[ ] Tests added
[ ] Documented the changes

If you have comments or can explain your changes, please do so below.
Attempt at adding downstream tests for marimo to the CI pipeline.
Notes:

marimo's full test suite also includes additional tests for frontend/cli etc.; I've omitted them as not relevant to the python backend testing functionality.
marimo leverages on hatch, though pyproject.toml shows the following

[tool.hatch]
installer = "uv"

also, test:test, test-optional:test and typecheck:check do refer to the following pytest and mypy commands

[tool.hatch.envs.test.scripts]
test = "pytest{env:HATCH_TEST_ARGS:} {args:tests}"
...
[tool.hatch.envs.test-optional]
template = "test"
...
[tool.hatch.envs.typecheck.scripts]
check = "mypy marimo/"

All this said, I've kept the commands as-is (trying to align with the approach in https://github.com/narwhals-dev/narwhals/pull/1161, even though I haven't referenced make commands as they do hardcode the python version in within).
Please let me know your thoughts on these points so that I can tweak accordingly :) (assuming that everything works as intended 🥶 ---EDIT: it does not yet)

thanks for working on this! @akshayka fancy taking a look? reckon this would be good enough to cover how you're using narwhals in marimo?


Fire Stick Version

What version of the Fire Stick were you running?
I'm on <IP_ADDRESS> which I am assuming is only API 17.  I don't know too much about Fire Stick honestly.

After the most recent update it's on Fire OS 5.0.5 (537174420).


cli command often leaves me with bold text

What version of Turborepo are you using?
1.1.6
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Linux
Describe the Bug
I am often left with bold text after running turbo commands.
Usually when I get the cached multicoloured 'FULL TURBO'  label.

Expected Behavior
I would like to run turbo commands and  once exiting, either by reaching to it's end or forcibly by cancelling the process, having the text return to normal (not bold).
To Reproduce
I usually run commands such as npx turbo run build and when getting a cached version the next shell prompt will be left in bold.

I believe this is fixed in the latest canary by #926


Bump version to 1.0.0-pre6

In this PR we update the version of base and time to 1.0.0-pre6.

@armiol, PTAL.


NPM auth failing

Describe the bug
When trying to build an image for the Ubuntu 18.04 authentication for NPM is failing
Area for Triage:
Scripting and command line
Question, Bug, or Feature?:
Bug
Virtual environments affected

[ ] macOS 10.15
[ ] Ubuntu 16.04 LTS
[x] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Expected behavior
NPM installas as expected and image build succeeds.
Actual behavior
I'm following the documentation to create an Ubuntu runner for testing conversion of non action jobs to Actions.
I've condensed the powershell script to bash for my test.
ImageType=Ubuntu1804
ImageGenerationRepositoryRoot=/src/github/actions/virtual-environments
SubscriptionId="**********-*****-*****-******-***************"
ResourceGroupName="actions-test"
AzureLocation="uksouth"
Force=true
GithubFeedToken="*****************************************************"

builderScriptPath=${ImageGenerationRepositoryRoot}/images/linux/ubuntu1804.json

storageAccountName="$(echo $ResourceGroupName | sed 's/-//g')001"
az storage account create -g $ResourceGroupName \
 -n $storageAccountName \
 -l $AzureLocation \
 --sku "Standard_LRS" \
 --https-only true

packer build -on-error=ask \
  -var subscription_id=$SubscriptionId \
  -var location=$AzureLocation \
  -var resource_group=$ResourceGroupName \
  -var storage_account=$storageAccountName \
  -var github_feed_token=$GithubFeedToken \
  $builderScriptPath

Run packer command
wait while it runs
Fail with error

==> azure-arm: Provisioning with shell script: /home/henti/src/github/actions/virtual-environments/images/linux/scripts/installers/hosted-tool-cache.sh
    azure-arm: AGENT_TOOLSDIRECTORY=/opt/hostedtoolcache
    azure-arm: Configure npm to use github package registry for '@actions' scope
    azure-arm: /imagegeneration/installers ~
    azure-arm: Configure auth for github package registry
    azure-arm: Installing npm-toolcache...
    azure-arm: Install<EMAIL_ADDRESS>==> azure-arm: npm ERR! code ENOTFOUND
==> azure-arm: npm ERR! errno ENOTFOUND
==> azure-arm: npm ERR! network request to https://npm.pkg.github.com/@actions%2ftoolcache-boost-ubuntu-1804-x64 failed, reason: getaddrinfo ENOTFOUND npm.pkg.github.com
==> azure-arm: npm ERR! network This is a problem related to network connectivity.
==> azure-arm: npm ERR! network In most cases you are behind a proxy or have bad network settings.
==> azure-arm: npm ERR! network
==> azure-arm: npm ERR! network If you are behind a proxy, please make sure that the
==> azure-arm: npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
==> azure-arm:
==> azure-arm: npm ERR! A complete log of this run can be found in:
==> azure-arm: npm ERR!     /home/packer/.npm/_logs/2020-05-20T15_05_25_968Z-debug.log
==> azure-arm: Script exited with non-zero exit status: 1.Allowed exit codes are: [0]
==> azure-arm: Step "StepProvision" failed
==> azure-arm: [c] Clean up and exit, [a] abort without cleanup, or [r] retry step (build may fail even if retry succeeds)? c

Hello, @henti
Do you have a proxy server configuration in your environment? Because the error is related with network connection reason: getaddrinfo ENOTFOUND npm.pkg.github.com

The only proxy I have is an apt-cacher for Debian packages, other than that, should be straight to the internet.
It must have been transient. I ran the job again and that succeeded.


Added forced uninstall/install about radish and radish-bdd packages i…

This PR fixed the problem where radish and radish-bdd installation could be invalid while installing terraform-compliance package. It enforces a re-installation if the library import fails.

https://github.com/eerkunt/terraform-compliance/issues/34

Pull Request Test Coverage Report for Build 126

5 of 16 (31.25%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.2%) to 54.36%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

terraform_compliance/main.py
5
16
31.25%

Totals

Change from base Build 123:
1.2%

Covered Lines:
187

Relevant Lines:
344

💛  - Coveralls


Any date-fns function that runs toDate returns wrong outputs

Description
The toDate function, which many date-fns functions call internally,  loses the custom UTC proxy methods.
const x = new UTCDate("2023-07-08T21:00:00.000Z")
x.getDay() // prints 6
toDate(x).getDay() // prints 0 on machines UTC > +3

Impact
Consider running the following anywhere that is UTC > 3:
const x = new UTCDate("2023-07-08T21:00:00.000Z")
const y = new UTCDate("2023-07-08T00:00:00.000Z")

isSameDay(x,y) // prints false, should be true
startOfDay(x) // prints 2023-07-08
startOfDay(y) // prints 2023-07-07, should be 2023-07-08

This was fixed in date-fns v3 over a year ago, but never pulled back to v2 (which is still the main version)

Yes, I’m aware and I did change it in date-fns v3 which is coming soon. Sorry that it wasn't clear from the docs.
On Mon, Oct 9, 2023, at 20:18, Eran Dagan wrote:

Description
The toDate function, which many date-fns functions call internally, loses the custom UTC proxy methods.
const x = new UTCDate("2023-07-08T21:00:00.000Z") x.getDay() // prints 6  toDate(x).getDay() // prints 0 on machines UTC > +3
Impact
Consider running the following anywhere that is UTC > 3:
const x = new UTCDate("2023-07-08T21:00:00.000Z")
const y = new UTCDate("2023-07-08T00:00:00.000Z")
isSameDay(x,y) // prints false
startOfDay(x) // prints 2023-07-08
startOfDay(y) // prints 2023-07-07
—
Reply to this email directly, view it on GitHub https://github.com/date-fns/utc/issues/2, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMX2JA7RK7JZ3MZECJIDDX6PTTFAVCNFSM6AAAAAA5YWV5Z6VHI2DSMVQWIX3LMV43ASLTON2WKOZRHEZTEOJUGIYTEMI.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Closing the issue as there's nothing actionable<EMAIL_ADDRESS>is out now, stable release's coming. Follow official Twitter for updates: https://twitter.com/date_fns


Placeholders get shuffle while on use in UITableView

hfghjufj.zip

Ok thanks for pointing out the issue i will look forward to this.
On Feb 21, 2017 6:44 PM, "Raj Sharma"<EMAIL_ADDRESS>wrote:

hfghjufj.zip
https://github.com/ErAbhishekChandani/ACFloatingTextfield/files/790186/hfghjufj.zip
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ErAbhishekChandani/ACFloatingTextfield/issues/9, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANMZ17ADQdrsE5FggEBK1AA7RF5lBBSFks5reuNOgaJpZM4MHTNb
.


Add repository offline

Greetings,
I am using the self-hosted version of RTD using Docker RTD
I am also using Gogs, a self-hosted Git, where I have a lot of repositories offline.
I would like to import my repos docs in RTD. The Import manually seems to work only with Github online repos.
There is a way to build without import the repos from the internet? Maybe drop the repos in an internal folder...
Thanks!

You can do it, I import local repos with the git:// protocol for development.

If you do a git clone git://localhost:3000/administrator/test_repo.git, it works?
I use a custom git alias for serving git repos on local dev
https://github.com/stsewd/dotfiles/blob/3afb09b770780a5b7e1369ce38c8552c1983e6cd/gitconfig#L14-L15

No, it don't work...
errno=Connection refused
Maybe Gogs don't support that protocol, or is my reverse proxy... So the problem is mine and not from RTD.
Thanks for your time!


More tutorials topics

Add textures to simple rendering

Multistream and instancing simple rendering

Using the geometry shader (per-face normals, normal visualization)

Using hardware tessellation (simple terrain rendering)

SpriteBatch with 3D lighting, reflection, refraction using normal maps

SpriteBatch with color-keying shader (emulate old-school colorkey textures)

Simple shadows (drop, projected)

Multi-pass rendering

Basics of deferred rendering

Fullscreen exclusive swapchains

Multimonitor rendering

Split-screen rendering

Direct2D/DirectWrite interop for DX11 / DX12

Yes please, I would be very interested in seeing these.

@isral. I've added the requested tutorial

Here's a good link for any deferred rendering article
https://www.3dgep.com/forward-plus/

Notes for multi-stream & instancing:

Multi-stream vertex buffer
SV_Instance ID + ConstantBuffer/Texture

https://software.intel.com/content/www/us/en/develop/articles/rendering-grass-with-instancing-in-directx-10.html
Skinned Instancing, https://developer.download.nvidia.com/SDK/10/direct3d/samples.html
DX11 FX: https://github.com/walbourn/directx-sdk-samples/tree/master/InstancingFX11
DX12:  https://github.com/Microsoft/DirectX-Graphics-Samples/tree/master/Samples/Desktop/D3D12DynamicIndexing

FSE is covered in this blog series: https://walbourn.github.io/care-and-feeding-of-modern-swapchains/

I'm very interested in a deferred rendering/lighting implementation with DirectXTK 12.
A basic tutorial would be fantastic... especially if the fundamentals of setting up and rendering to a G-buffer (depth, normals, etc) can be extended to a solution containing HDR/MSAA (FP16 render targets resolving to a 10:10:10:2 backbuffer)  plus postprocessing effects.
I would be happy to write and apply my own deferred lighting shaders adopted from previous work (e.g. Practical Rendering & Computation with D3D11, by Zink et al).


Lumina preferences: search results: Escape should escape from results without closing the application

Actions

open Desktop Settings
seek something
observe results
key Escape

Expected

settings

Actual result

disappearance of settings

ESC should no longer close the application.  We will eventually set it to clear the search field and return all results.


Using this.$data creates an issue

Perhaps I am using the validator incorrectly. But for a specific case I am fetching some content using an ajax call inside a ready method and then wanting to set the content using this.$data. It would be cleaner if I can do that instead of setting every single property individually.
However as soon as I do that I get the following error from the console.

It works if I use this.name = 'Caspien' or this.$set('name', 'Caspian') inside the ready function.

Thanks for your report.
I checked your jsfiddle.
But I could not understand that issue.
Would you provide the issue code ?

@kazupon Apologies, I pointed you to the original fiddle, I updated version 2 to be the base.
It shows what I was trying todo. However, seems Evan updated to 0.12.4. I cannot even get a valid validation option to work with that.

vue-validator don't work if you set  the new value to this.$data.
Because vue-validator keep the validation result to this.$data, and also define valid, invalid and dirty property. for that reason, we should  set the value vm.$set('prop', val) or vm.prop = val.
I think that is no good plugin design.
In next version 2.0, I'll try to  implement full-scratch (see #24).

@kazupon thanks for response. In the end I did change my code to use vm.$set(...)


Update Json.NET to 9.0.1-beta1

I mean a different PR, it's way safer to first update all repositories to use 9.0.1-beta1 and then, after a successful build remove all the unnecessary imports from the repositories. Doing it this way, allows me to update repositories one by one without running into restore problems locally


Slow compile times

It seems that something is causing excessively slow compile times. For instance, adding a simple println! costs nearly 40 seconds to recompile:
$ cargo run --database-url ...
   Compiling warp-api-starter-template v0.1.0 (/Users/max/Repositories/warp-api-starter-template)
    Finished dev [unoptimized + debuginfo] target(s) in 39.35s
     Running `target/debug/warp-api-starter-template`

Where the only change is:
diff --git a/src/environment/argon.rs b/src/environment/argon.rs
index b70bcd5..ce58cc9 100644
--- a/src/environment/argon.rs
+++ b/src/environment/argon.rs
@@ -15,6 +15,7 @@ impl Argon {
             argon_iterations,
             ..
         } = args;
+        println!("foo");
         Self {
             secret: argon_secret.to_owned(),
             memory_size: argon_memory_size.to_owned(),

This is actually decently faster than other compile times I've observed, which sometimes exceed two minutes (!) but are not significant changes.
Depending on your development style, this may be a showstopper.

Any recommendations on improving the compile times are welcome.

#12 might help in the case of slow compile times. Rust considers crate as a compilation unit and ATM warp-api-starter-template is huge crate and spliting it into multiple dependent crate might allow for better compile times. This is not tested notion for me. I need to try it out and see.

@aslamplr I think you're right that breaking things up into component crates could help. At the very least, it should avoid to always recompile everything.


GitHub app no installed

:warning: The Git Automator app is not installed on this repo, which will cause the Git Automator service to be unavailable, please click here to install it.
@v-caxian; @TinaLiuGirl;

The Git Automator app has been installed to this repo.


Duplicate site collection menu items when using PnP-Provisioning

I've used Get and Apply-PnPProvisioningTemplate commands for a couple times already where navigation items (top bar for Communication sites) are duplicated.
In the example below, Home results into 2 entries after creating a new site. Should I just remove items under pnp:NavigationNode when the XML file is generated?
    <pnp:CurrentNavigation NavigationType="StructuralLocal">
      <pnp:StructuralNavigation RemoveExistingNodes="false">
        <pnp:NavigationNode Title="Home" Url="{site}" />
      </pnp:StructuralNavigation>
    </pnp:CurrentNavigation>

Thanks!
@fredyano

Hi, it is a known behavior. You should specify RemoveExistingNodes="true" in order to reset the menu items when you provision.


Infinispan gRPC Kafka: Add mutiny gRPC service

gRPC supports both blocking and non-blocking (mutiny) approaches. We had implemented only the blocking scenario. In this PR, we're covering the non-blocking one.

Set @pjgg as reviewer for this PR, he is looking at grpc / http2 atm, he should review this PR.


[WFCORE-3990] Upgrade to Byteman version 4.0.4 for better JDK9+ support.

https://issues.jboss.org/browse/WFCORE-3990
This is the root cause of at least these issues:

https://issues.jboss.org/browse/WFCORE-3869
https://issues.jboss.org/browse/WFCORE-3874
https://issues.jboss.org/browse/WFCORE-3875

Core - Full Integration Build 7722 outcome was UNKNOWN using a merge of f85d0e65d1f91cd2ab8f298e2216a023b0bb4887
Summary: Canceled (Error while applying patch; cannot find commit 9e3eb1e8f0700d9473c1c5b96e86b4eff0297a9b in the https://github.com/wildfly/wildfly-core.git repository, possible reason: refs/pull/3414/merge branch was updated and the commit selected for the ... Build time: 00:00:20

3x infrastructure issues with checkout
1x problem with HotRodPersistenceWebFailoverTestCase, this test case is failing in many PRs
@kabir @rhusar @pferraro are you looking into HotRodPersistenceWebFailoverTestCase failures ?

@rsvoboda Correct.


TH2-1133. Implement SSE client

I would implement the client without using the mobx store. There's going to be only one listener per request, so no need to make a dedicated worker for this.


Tray Title Windows fixed

Tray Title Windows fixed #374
Description
There is added a title functionality for Windows applications. There are 12 new images which are loaded when messages are received.

@RocketChat/core

Closes #115

TODO
We need a template for tray icons.
Example

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.pjakielaszek seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@alexbrazier Can you review this again?


Auto increment the index map_size when run out of space

Right now, there is a hard default of 2^24 bytes for each index (let default_map_size = 16_777_216;), which should accommodate most indices. However, this is suboptimal for two reasons:

Uses up far too much memory on simpler datasets
Cannot be expanded to accommodate larger datasets

I'm not sure how meilisearch handles this (I will look into it later), but an initial thought is the following:

Start each new index off with 2^17 (131072) or 2^18 (262144) bytes in the map call. I think these are reasonable starting values that should accommodate a lot of datasets while still not using an excessive amount of RAM (0.1 and 0.3 mb respectively).
Whenever an add operation fails because the database runs out of memory, close the index and reopen it with 2x the previous memory. This can be seen as the opposite of exponential backoff.

This solution means there will be a performance hit when adding a huge batch of documents at once, but I think that the good this approach brings outweighs that performance hit.

It appears as though map_size should be called the max_map_size, because it only uses up memory as necessary. Thus, closing this issue with a fix setting the maximum map size to 1 GB which should accommodate any dataset stored on a regular device.


Support switch=* tags on power=pole/tower

https://wiki.openstreetmap.org/wiki/Tag:power=switch

Switch are not yet rendered. Could you reopen this issue please?
node/6316737396

These have now been added.


[5.7] Apply square bracket syntax for array destructuring assignment

Apply square bracket syntax for array destructuring assignment, for more information please look into https://wiki.php.net/rfc/short_list_syntax
This rfc was implemented in PHP v7.1. Laravel support php from the 7.1.3

Prior attempt: https://github.com/laravel/framework/pull/25474


[Snyk] Security upgrade moment from 2.24.0 to 2.29.4

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

lab9/package.json
lab9/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

768/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS) SNYK-JS-MOMENT-2944238
No
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

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


[HUDI-1383] Modify hive partition synchronization

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
Modify hive partition synchronization
Brief change log

delete  Collections.sort(hivePartitionValues)  and   Collections.sort(storagePartitionValues)

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #2257 (5ec9f72) into master (430d4b4) will decrease coverage by 43.14%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master    #2257       +/-   ##
=============================================
- Coverage     53.54%   10.39%   -43.15%
+ Complexity     2770       48     -2722
=============================================
  Files           348       50      -298
  Lines         16109     1779    -14330
  Branches       1643      211     -1432
=============================================
- Hits           8626      185     -8441
+ Misses         6785     1581     -5204
+ Partials        698       13      -685

Flag
Coverage Δ
Complexity Δ

hudicli
?
?

hudiclient
?
?

hudicommon
?
?

hudihadoopmr
?
?

hudispark
?
?

huditimelineservice
?
?

hudiutilities
10.39% <ø> (-59.70%)
0.00 <ø> (ø)

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

What don't you understand? i  think  i  can  help  you

@vinothchandar I understand my problem. I will close this PR and start a new one. Please help me review it


More Information needed for "authority" option in MSAL js library for Azure AD B2C. It seems like a very important option.

Core Library
MSAL.js v2 (@azure/msal-browser)
Wrapper Library
MSAL Angular (@azure/msal-angular), MSAL React (@azure/msal-react), MSAL Node Extensions (@azure/msal-node-extensions), Not Applicable
Documentation Location
https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular/docs/v2-docs/redirects.md
Description
I'll start with this as an example.
https://login.bbbbbbbb.com/bbb5bbbbbbb01/b2c_1a_signup_scccccn/oauth2/v2.0/authorize?client_id=bbbbbbbbbbbbb&scope=openid%20profile%20offline_access&redirect_uri=http%3A%2F%2Flocalhost%3A6420&client-request-id=fbbbbbbbbbbbc7d5f&response_mode=fragment&response_type=code&x-client-SKU=msal.js.browser&x-client-VER=2.13.1&x-client-OS=&x-client-CPU=&client_info=1&code_challenge=etq0YbbbbbbVxbbbNjuZ-WL3bbbYtw&code_challenge_method=S256&nonce=390bbbb46bc-a46f-bb0167127b4c&state=eyJpZCbbbbbbbFjNiIsIm1ldGEiOnsiaWcccccccccccccccX0%3D

This is what I see from above <my custom domain>/<my app reg directory id (not tenant id)>/<policy-name>/oauth2/v2.0/authorize? + <clientId> + [[<openid> + <offline_access>]] + <redirect_uri> + <client-request-id> + <response_mode> + <response_type> + <code> + <x-client-sku> + <x-client-VER> + <x-client-OS> + <x-client-CPU> + <client_info> + <code_challenge> + <code_challenge_method> + <nonce> + <state>
I know about 40% of what's going on up there. It pretty much falls off at client-request-id. Is there an api flow diagram explaining exactly what's going on?
I'll pick out nonce for example. I didn't set that anywhere but yet it's there. Any additional information about that I should know?
***More over, and this is kind of the entire point, what makes this URI "https://bbbbbbbbb.com/bbbbbb342-bbbd01/B2C_1A_SIGNUP_SIGbbbb" do/transform the above URI with the following settings:
auth: {
      clientId: "............", // This is the ONLY mandatory field; everything else is optional.
      **[[authority]]**: b2cPolicies.authorities.signUpSignIn.authority, // Choose sign-up/sign-in user-flow as your default.
      knownAuthorities: [b2cPolicies.authorityDomain], // You must identify your tenant's domain as a known authority.
      redirectUri: "http://localhost:6420", // You must register this URI on Azure Portal/App Registration. Defaults to "window.location.href".
    },

The only thing I can tell that is kicking off the above authority is the <Endpoints> section in Azure AD B2C and specifically it is the Azure AD B2C OAuth 2.0 authorization endpoint (v2) section. Can I use others? When do I choose token endpoint (v2) versus OpenID Connect metadata document?
***Which brings me to the sample Angular v2 docs and react for that matter.
export function MSALInstanceFactory(): IPublicClientApplication {
  return new PublicClientApplication({
    auth: {
      clientId: 'bbbbbbbbbbb6',
      redirectUri: 'http://localhost:4200',
      postLogoutRedirectUri: 'http://localhost:4200'
    },

here the authority is not here. Should I add that like I did in the other sample app? Does this MSAL configuration need for me to find the AD B2C authorization endpoint v2 (for PKCE) (???is the token endpoint only for implicit MSAL v1???) flows and therefore that endpoint is the one I should choose?
Also, would this documentation, I found somewhere, not be entirely correct?
URI of the tenant to authenticate and authorize with. Usually takes the form of: (because... above)
https://{uri}/{tenantid}.

It becomes a "how did we get here" exercise that is painful based finding and linking and reading and finding and linking and reading... the current documentation situation.
As well, I found this in the docs for MSAL JS v2. I am so happy after a week I even found those docs.
Type declaration
Optional authority?: string
You can configure a specific authority, defaults to " " or "[https://login.microsoftonline.com/common"](https://login.microsoftonline.com/common%22)

You see, that doesn't tell me anything at all. If I experiment with it over hours and hours eventually I can figure it out. But on something like the URI/authority why isn't it just fully and completely explained? It literally controls your login. It's not a small thing.
Also, when you're putting these in wrappers it's even more abstracted away so if you don't explain it in the docs then it's always a pain to figure it out.
With that said, if you all improved your documenation and created a more comprehensive spec that includes some important parts of the api i.e., like Authority you would see so much more wide spread adoption. Even the youtube videos are, in a sense, lacking.

@xtianus79 that's fair criticism mostly, but you see it's a double-edged sword. One goal of the library is to abstract away the details of OAuth 2.0 & OpenID Connect protocols (which is complex enough) AND how Azure AD/B2C implements that protocol (which introduces other idiosyncrasies) within reason. A proper discussion of authority would require getting into these details, which at that point, you might as well read the OAuth/OpenID specs, or rather, the protocol reference docs on docs.microsoft.com. I'm certain 90% of what goes into your example url above will become familiar afterwards.
But the point where your criticism particularly has merit is that there's a certain lack of connection between MSALs concept of authority and how docs.microsoft.com & Azure portal presents authority related information. That's mostly a verbiage issue, but what authority string should be supplied to MSAL configuration will not be immediately obvious to someone coming from docs or portal/app registration. So perhaps an authority guidance doc might help alleviate these concerns.

@xtianus79 apologies, this one fell through the cracks apparently. I've put this in the backlog and tracking internally, though I don't have an ETA unfortunately.

@xtianus79 please refer to the authority doc here. Closing this.


⚠ Bofrost.at has degraded performance

In 118dbb8, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 820 ms

Resolved: Bofrost.at performance has improved in 0441eed.


Normal transaction value variation

In all my simulations that I have done all the normal transaction value are between 90 - 110. I cannot find a way to change these normal transaction values, Therefore I was wondering if it is possible to tweak the value of the normal transactions?
thanks in advance,
Floris

Does anyone knows how to accomplish this?

I am also in the same situation than yours. I have just started to use this simulator.
With a quick glance at the code, it seems like the conf.json["default"]["min_account"] parameter changes the average value of normal transaction (used in src\amlsim\SimProperties.java).
For the variation of the amounts, the conf.json["simulator"]["transaction_interval"] does not seem like it has an impact.
I'll notify here if I find anything interesting.

Yes exactly the same problem I have. Hope you find a way how to adjust the amounts

In conf.json you can adjust these parameters to change the normal transaction values.
  "default": {
    "min_amount": 100,
    "max_amount": 1000,

...


Upgraded ubi to 1161 and golang/x/net to 0.24 to fix vulns

Per https://issues.redhat.com/browse/OSD-22353

/approve


fix(datahub-frontend): OIDC discovery URL will not have NONE as auth_methods_supported

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Just fixed the AuthorizationGrant compilation error


Support for null values in line/area graphs

Since rickshaw can't handle null values, I usually tend to fill it up with integer 0 values. But, this leads to bad results if there's a lot of data missing - a sawtooth pattern. I'd prefer to actually skip drawing of null values.
Am i wrong here or missing something? I've followed some more leads in d3.js and found a ticket describing the same problem.
A similiar discussion of this problem in d3.js:
https://github.com/mbostock/d3/issues/583
And a pull request from 6 months ago:
https://github.com/mbostock/d3/pull/594
It is possible to use this in rickshaw.js to achieve a similar result?
Kind regards,
-Frederik

Solution with the current version is fairly simple - just fill your series will nulls for the missing points. The fill function works pretty well for this:
Rickshaw.Series.fill(series, null);

Seems to work well for area, line, bar and scatter.


Specify data required for Views

Currently, the UI doesn't show data requirements for views. So, it's not possible to determine what kinds of traces (ex. kernel and/or userspace) and what events (ex. sched switch) are required for a certain view.
Displaying view data requirements at the user's point of need (in the tool) is especially important for users who are managing tracing themselves (vs. using a standardized testing script) since it tells them how to produce the more complex analyses/views without them having to do frustrating guesswork.
Challenges
Providing this information to users is not trivial for several reasons:

Server agnostic - The Trace Viewer client can be used with trace servers other than the Trace Compass Trace Server so view requirements need to come from the trace server and the way the information is displayed client-side needs to not be specific to a server
Tracer agnostic - Trace points can have different names in different tracers (ex. Ftrace vs. LTTng)
Trace format agnostic - Information about which events to enable is only relevant for trace formats that allow you to enable/disable certain events (some formats trace everything available all the time)
Information about required events is distributed all over the place right now. There is no centralized place to find the events required for all analyses.

Resources
Some information about event requirements for views can be found here:
LTTng-utils Tracing Profiles
This resource is great! The profiles list the kernel and userspace (UST) events required for many core analyses (ex. Disk, Memory). Descriptions and other required bits are specified in the profiles. The profiles can also include each other. It's very clear and well organized.
Disk tracing profile
desc:
    The kernel events for disk analysis
kernel:
    - block_rq_complete
    - block_rq_insert
    - block_rq_issue
    - block_bio_frontmerge

Scheduler tracing profile
desc:
    The scheduler events of the kernel
kernel:
    - sched_process_exec
    - sched_process_exit
    - sched_process_fork
    - sched_process_free
    - sched_switch
    - sched_wakeup
    - sched_waking
    - sched_wakeup_new
    - sched_pi_setprio

General kernel tracing profile
desc:
    A subset of kernel events sufficient and necessary to make most Trace Compass analyses
includes:
    - sched
    - interrupt
    - network
    - timer
    - statedump_k
    - disk
kernel:
    - syscall
    - power_cpu_frequency

Trace Compass User Guide
Some of the view data requirements are in Trace Compass user guide, but it's incomplete, possibly outdated, requires digging, and requires that users know the tool's relationship to TC.
Show required trace formats?
Showing the trace types/formats required for the analysis could also be relevant, especially if we make it possible for users to explore the analyses that implemented, but not possible with the current trace type (See #285) to make the analyses more discoverable. Otherwise, users would have to read the documentation to discover the analysis or stumble onto the analysis by accident when they load the correct trace type.
It also allows users to understand which analyses require which kind of traces so they can intentionally collect the kinds of traces (ex. kernel, userspace, GPU) required to see an analysis. Otherwise, they can only stumble onto the analyses by accident if they happen to have the right collection of traces.
The solutions proposed below for displaying the required events could also be used for displaying the required trace types.
Show required events

Quick fix - List required events at the end of each view description. If I understand correctly, according to @MatthewKhouzam this information is already available server side.

[ ] Curate view requirements
[ ] Transform requirements to raw text and concatenate to view description

Tell user which events still need to be enabled. If an analysis is compatible with the trace type, but the events required to perform the analysis are not enabled (based on CTF trace metadata), these missing events can be listed.

Related: How should impossible analyses be presented #285

@bhufmann Are there data requirements for views other than enabling the necessary trace events? For example, pointing to the source code or the executable that was traced.

Some questions for @bhufmann:
* Are there data requirements for views other than enabling the necessary trace events? For example, pointing to the source code or the executable that was traced.

I most cases there are no other requirement than enabling the necessary trace events (and adding trace contexts). However, in some views symbol resolutions need to be done to translate PC addresses to source code location.

* Does the list of events required for an analysis tend to be long (>5 events)? Are the names of trace events typically long? (This will impact how we can display the required events)

There is not a generic answer for that. It depends on the view. For, LTTng thread status or resources view there are more than 5 events needed. See KernelAnalysisModule for the comment-out code of required events. BTW, it's commented out because, this analysis module can be populated by LTTng, Perf or Ftrace traces that hook into the same kernel events, but have different event names, so that a static list of required event names won't work.

The need to list the events required for the available views was highlighted by users in the user survey completed in November 2022.


Install Azure Cli with yum

It seems to go wrong in step 2 where the echo -e is added to the repo-file. This makes the install in step 3 also go wrong. If you then fix the repo-file manually you also get a list of errors (see below). I'm working on Ubuntu 18.10. I tried --skip-broken as suggested at the end of the error listing, but to no avail.
azure-cli                                        | 2.9 kB  00:00      azure-cli/primary_db                             |  30 kB  00:00      Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package azure-cli.x86_64 0:2.0.51-1.el7 will be installed --> Processing Dependency: /bin/sh for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: libpthread.so.0(GLIBC_2.2.5)(64bit) for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: python for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: ld-linux-x86-64.so.2(GLIBC_2.3)(64bit) for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: rtld(GNU_HASH) for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: libc.so.6(GLIBC_2.4)(64bit) for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: /usr/bin/env for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: ld-linux-x86-64.so.2()(64bit) for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: libutil.so.1()(64bit) for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: libpthread.so.0()(64bit) for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: libm.so.6()(64bit) for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: libpython2.7.so.1.0()(64bit) for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: libdl.so.2()(64bit) for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: /usr/bin/env for package: azure-cli-2.0.51-1.el7.x86_64 --> Processing Dependency: /bin/sh for package: azure-cli-2.0.51-1.el7.x86_64 --> Finished Dependency Resolution Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: ld-linux-x86-64.so.2()(64bit) Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: libutil.so.1()(64bit) Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: libpython2.7.so.1.0()(64bit) Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: libpthread.so.0()(64bit) Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: libm.so.6()(64bit) Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: libpthread.so.0(GLIBC_2.2.5)(64bit) Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: libdl.so.2()(64bit) Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: ld-linux-x86-64.so.2(GLIBC_2.3)(64bit) Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: /bin/sh Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: python Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: rtld(GNU_HASH) Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: /usr/bin/env Error: Package: azure-cli-2.0.51-1.el7.x86_64 (azure-cli)            Requires: libc.so.6(GLIBC_2.4)(64bit)  You could try using --skip-broken to work around the problem  You could try running: rpm -Va --nofiles --nodigest

Installing with yum (designed for RPM systems) may not be compatible with working on Ubuntu (which is designed to use apt). Please try the apt install instructions.
Ubuntu is also not listed as a supported platform for yum installs on our documentation. If you experience an issue with yum on RedHat-derived systems, file an engineering bug.

Installing with yum (designed for RPM systems) may not be compatible with working on Ubuntu (which is designed to use apt). Please try the apt install instructions.
Ubuntu is also not listed as a supported platform for yum installs on our documentation. If you experience an issue with yum on RedHat-derived systems, file an engineering bug.

I realized that later as well. I tried apt-get, but couldn't get it to work. I then manually installed it (though not recommended).

Can you provide any more information about why the apt install failed? It could be because of the aborted/incomplete yum install creating incompatibilities. You may need to run some kind of cleanup operation in yum.

Can you provide any more information about why the apt install failed? It could be because of the aborted/incomplete yum install creating incompatibilities. You may need to run some kind of cleanup operation in yum.

I removed yum and its content, but I think the problem is with the repository as it tries to search for the cosmic (Ubuntu 18.10) release. An issue has been created for this: https://github.com/Azure/azure-cli/issues/7776.

OK, that's the case for sure. We do not have Cosmic packages yet, but the Bionic package may work on Cosmic. Thanks for confirming!


Issue 06 seir model

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@5cfcef7). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage        ?   49.12%
=======================================
  Files           ?        3
  Lines           ?       57
  Branches        ?        0
=======================================
  Hits            ?       28
  Misses          ?       29
  Partials        ?        0

Continue to review full report at Codecov.

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

@siting-miao
Could you add a file to the root directory called .coveragerc with the follwoing content

[run]
source = seirmo
omit =
    seirmo/tests/*

[report]
exclude_lines =
    pragma: no cover
    pragma: no linux cover
    pragma: no python 3 cover
    def __repr__
    raise AssertionError
    raise NotImplementedError
    except ImportError:
    if False:
    if __name__ == .__main__.:

This just makes sure codecove is not looking at the tests for coverage.

This just makes sure codecove is not looking at the tests for coverage.

Thx! Done with that. I'm now going to do the docstring test issue?

This just makes sure codecove is not looking at the tests for coverage.

Ah I see there have been several issues created. I'll go to them later in the day since there is a Career Development session now.