Please support switch, xbox and ps4

people making games are going to want to port them to consoles to make money,
can we get a port to the latest game consoles?

Well IIRC Xbox is supported through UWP, for PS4 and Switch you can either get the devkits or you can try porting the games with the open-source PS4-SDK or Switch Homebrew (Which only work on devices that can run homebrew games).

I'm not sure if nintendo or sony support dev kits for this though.

It's entirely possible to have this working on game consoles, however it requires a heavy lift and resources, which isn't something an open source project typically has. Xbox is currently supported as Softizo, but that was brought through community contribution and many hours of work. If you need the switch or ps4, you'll have to acquire a dev kit and work on it with others in the same situation as those require you to sign an NDA not allowing source code for an engine or framework that connects with them to be public. As always, community contributions are welcome :)

@Gamerfiend @raysan5   So this is never going to be added?
the console stuff could be addon libraries that are kept closed source.

@Shadowblitz16 it's can't be, it's not possible. Xbox is supported via UWP. PS4 and Switch both support OpenGL to some extent. There's also the option to use Raylib on Homebrew consoles. I once saw a game jam where someone submitted a Raylib game running on Switch, Vista, and some other consoles.
(I can't really go into detail about the official APIs, since they are under NDA)

@Shadowblitz16 it can't be, it's not possible to use these APIs in an Open Source project. However, Xbox is supported via UWP. PS4 and Switch both support OpenGL to some extent. There's also the option to use Raylib on Homebrew consoles. I once saw a game jam where someone submitted a Raylib game running on Switch, Vista, and some other consoles.
(I can't really go into detail about the official APIs, since they are under NDA)

That gamejam where someone submitted a raylib game on switch actually used SDL2


Adding

Overview
Modifying the PHPCI CopyBuild plugin to add an extra option, which indicates whether the root folder of a build should be included when copying it to a destination. The original (and now default) behaviour was that the build folder would always be copied - it is now possible to copy only the build's contents by setting the include_build_dir flag to false.
Example
Here's an example of how the copy plugin was defined previously. (This is still valid.)
success:
    copy_build:
        directory: "/path/to/test.domain.com/"
        wipe: true
        respect_ignore: true

This copies the build directory and everything in it, so if your build directory is called 34_abcdef, then the path of your built software will be /path/to/test.domain.com/34_abcdef. This may not be the intended result.
The new flag, include_build_dir, allows users to get around this issue:
success:
    copy_build:
        directory: "/path/to/test.domain.com/"
        wipe: true
        respect_ignore: true
        include_build_dir: false

In this case, the contents of the build folder will be copied, leaving the build folder itself behind, and the path of the built software will be /path/to/test.domain.com/.
Please note: While I've done my best to verify the command syntax on Windows using a VM (as you can see from my second commit) I don't have a running PHPCI Windows instance to test this live, though I believe the edit is correct and non-harmful.

Decided I want to look at this again, maybe add an option for the user to specify a source subdirectory. Will re-open once done.


Better/different ABR algorithm?

Have you read the Tutorials?
yes
Have you read the FAQ and checked for duplicate open issues?
yes
What version of Shaka Player are you using?
3.1.0
Please ask your question
I have spent hours analyzing the network traffic and shaka player's behavior. I also compared it with other players.
My findings/conclusions:
Shaka's ABR is extremely conservative. My 1080p stream can play fine and has some seconds in the buffer, yet shaka decides to switch to 360p out of nowhere.
I monitored the estimated bandwidth every second and noticed that when I select 1080p manually, the estimated BW goes up significantly, compared to the lower quality streams. I assume that this is because smaller chunks have the same initial lag as the big ones, before the actual data is being transferred. Hence, if you simply use the chunk size and download time to estimate the bandwidth, you will get lower estimates. It then results in a vicious cycle, as the lower the estimate, the lower the stream quality and lower chunk sizes => even lower BW estimates etc etc.
I am not sure how the other players do it, but e.g. bitmovin player plays the same stream with 1080p without problems and changes in bitrate.
Perhaps, instead of using a hypercomplicated bandwidth estimation formula, it would be better to simply monitor the buffer level? Say, if the buffer length is increasing, or is at its max level, the player can try to switch to a higher bitrate variant. If the buffer level then starts degrading, it would switch back to the lower bitrate.
Another question - do you use AVERAGE-BANDWIDTH from the HLS manifest in the switching algorithm or the maximum one?
And finally - is there a way to change the bandwidth estimator function by means of configuration (without messing with the sources)? For example, I would like to try and make the EWMAs longer, or even change to SMAs.
in my case, some of the video segments are not cached in the CDN, which results in longer download times - but they are not many and thus it wouldn't really affect the playback, except for the ABR, which panics and switches to a low bitrate stream.  I would thus like to smoothen out the bandwidth estimation, to take more segments into account.

You have made some great observations.  Replies inline:

Shaka's ABR is extremely conservative. My 1080p stream can play fine and has some seconds in the buffer, yet shaka decides to switch to 360p out of nowhere.

It is very admittedly conservative!  We would always prefer to downgrade instead of buffering.  There are ways to do streaming and bandwidth estimation that are capable of utilizing a larger percentage of the user's actual bandwidth, but we designed ours with a goal to keep it simple and easy to maintain.
For an example of a way to get higher utilization, you could measure the startup latency of each connection (time to first byte or TTFB), and exclude that time from the throughput measurements.  Then, you could overlap segment requests such that the startup latency of segment N+1 overlaps with the end of the download of segment N.  This would achieve higher throughput for the same bandwidth, and therefore higher quality.  But it's also more complicated.
Instead, we count the startup latency in our throughput measurements, and build our bandwidth estimate from those.  We overlap audio, video, and text segment requests, but not multiple requests from any one stream.  The result is a lower estimate of bandwidth, but it's an estimate that is an accurate reflection of the way we stream content.  It's not so much an estimate of the user's true bandwidth, as much as it is an estimate of how much bandwidth our simplistic streaming system is capable of utilizing.
That said, our overall ABR algorithm has not been revisited since our launch in December 2014, and very few changes to our streaming/fetching algorithm have been made in that time.  We're very open to changing these things.

I monitored the estimated bandwidth every second and noticed that when I select 1080p manually, the estimated BW goes up significantly, compared to the lower quality streams. I assume that this is because smaller chunks have the same initial lag as the big ones, before the actual data is being transferred. Hence, if you simply use the chunk size and download time to estimate the bandwidth, you will get lower estimates. It then results in a vicious cycle, as the lower the estimate, the lower the stream quality and lower chunk sizes => even lower BW estimates etc etc.

This is absolutely true.  What I would suggest is that get the bitrate requirements of your content (when 1080p is selected manually, check player.getVariantTracks().find(t => t.active).bandwidth), and compare that to our bandwidth estimate (which can be found via player.getStats().estimatedBandwidth).  Both numbers are in bits per second.  If the bandwidth estimate is sometimes lower than the bitrate requirement of the 1080p stream, then today's player and default plugins won't play it consistently.
However, if the bandwidth estimate is consistently higher, you may be able to tweak the configuration to improve the quality we select.  By default, and again, because we are very conservative, we only upgrade if that will result in us using 85% or less of the estimated bandwidth.  And if the active stream is using more than 95% of the estimated bandwidth, we downgrade to avoid buffering.  But both of these numbers are configurable:
// Downgrade if more than 98% of estimate is used
player.configure('abr.bandwidthDowngradeTarget', 0.98);
// Upgrade if it would use less than 95% of the estimate
player.configure('abr.bandwidthUpgradeTarget', 0.95);

Perhaps, instead of using a hypercomplicated bandwidth estimation formula, it would be better to simply monitor the buffer level? Say, if the buffer length is increasing, or is at its max level, the player can try to switch to a higher bitrate variant. If the buffer level then starts degrading, it would switch back to the lower bitrate.

That sounds very reasonable.  The only caution I would give is to add some kind of hysteresis (like our upgrade/downgrade targets) to avoid frequent bitrate switching.  Since we stop buffering for a while when a certain goal is met (config streaming.bufferingGoal), there will always be times when the buffer fullness drops.  If you react to every change in buffer fullness, you would downgrade and upgrade on every segment or two.

Another question - do you use AVERAGE-BANDWIDTH from the HLS manifest in the switching algorithm or the maximum one?

A quick search of lib/hls/ shows that we are using the BANDWIDTH attribute.  Though in DASH, we use an attribute that is an average.  So that should probably be fixed.  But AVERAGE-BANDWIDTH is optional according to the spec, so we would need to fallback to BANDWIDTH if it's missing.  Would you like to send a quick PR for this?

And finally - is there a way to change the bandwidth estimator function by means of configuration (without messing with the sources)? For example, I would like to try and make the EWMAs longer, or even change to SMAs.

Absolutely.  You can implement an interface (shaka.extern.AbrManager) and configure a factory (player.configure('abrFactory', () => new MyAbrManager())) to plug in your own ABR algorithm, completely from scratch.  You can monitor the video element's buffered attribute or our recently-added player.getBufferFullness() method and react to that instead of estimating bandwidth.  (That method was just added and isn't in a release build yet.  It's in the latest source, though.)
Here's a shell of how a buffer-based AbrManager could be structured (untested), to help you get started:
class MyAbrManager {
  constructor(getBufferFullness) {
    this.variants_ = [];
    this.enabled _ = false;
    this.switch_ = null;
    this.config_ = null;
    this.getBufferFullness_ = getBufferFullness;
  }

  init(switchCallback) {
    this.switch_ = switchCallback;
  }

  setVariants(variants) {
    this.variants_ = variants;
  }

  configure(config) {
    // Store and use the ABR config if you're going to make it configurable.
    // You can reuse bandwidthDowngradeTarget and bandwidthUpgradeTarget,
    // or you can add new config parameters to Shaka Player that are more fit to purpose.
    this.config_ = config;
  }

  enable() {
    this.enabled_ = true;
  }

  disable() {
    this.enabled_ = false;
  }

  stop() {
    this.enabled_ = false;
    this.switch_ = null;
    this.variants_ = [];
    this.config_ = null;
    this.getBufferFullness_ = null;
  }

  playbackRateChanged(rate) {
    // A no-op if you're monitoring the buffer fullness.
    // A higher playback rate will naturally result in depleting the buffer more quickly.
  }

  getBandwidthEstimate() {
    // If we're not estimating bandwidth...
    return 0;
  }

  chooseVariant() {
    // Choose an initial variant and return it.
    // But don't do this, do something better than this.  :-)
    return variants[0];
  }

  segmentDownloaded(deltaTimeMs, numBytes) {
    // This can be a no-op if you're monitoring buffer fullness,
    // or you can use this method as a prompt to compute the
    // buffer fullness  and react to changes.  I recommend the latter.

    const fullness = this.getBufferFullness_();
    if (fullness is increasing) {
      this.switch_(higher quality variant);
    } else if (fullness is decreasing) {
      this.switch_(lower quality variant);
    }
  }
}

player.configure('abrFactory', () => {
  return new MyAbrFactory(() => player.getBufferFullness());
});

If you can make this work well, we would be more than happy to have a buffer-based ABR system added alongside shaka.abr.SimpleAbrManager as an alternative.  (Though perhaps SimpleAbrManager should get renamed at that point to better describe the difference.)  If you want to work on this, we would be happy to collaborate or provide guidance.

in my case, some of the video segments are not cached in the CDN, which results in longer download times - but they are not many and thus it wouldn't really affect the playback, except for the ABR, which panics and switches to a low bitrate stream. I would thus like to smoothen out the bandwidth estimation, to take more segments into account.

In addition to monitoring buffer fullness, you could also consider making some small changes to SimpleAbrManager and then subclassing it or configuring it to tweak some parameters in the bandwidth estimation.  For example, making bandwidthEstimator_ replaceable or configurable.  Currently, the EwmaBandwidthEstimator class contains these hard-coded constants you might want to change:
https://github.com/google/shaka-player/blob/9709086e9898300324d742fb39deb9afcb386813/lib/abr/ewma_bandwidth_estimator.js#L22-L34

I think latency should be taken into account. I agree with @joeyparrish  about complexity, but in many countries maybe the network is not the best, and the latency can be high and this penalizes the reproduction.
@joeyparrish, are you open to making EwmaBandwidthEstimator configurable? If yes... -> The problem is that the EwmaBandwidthEstimator is created in the constructor when we don't have the configuration yet, do you have any ideas for this? If you give me any ideas I can do a PR for this.

Glad to see great discussion on this! Is there currently a way to write a custom ABR manager that takes latency into account? I'm not sure how to capture latency since segmentDownloaded only accepts deltaTimeMs and numBytes. I may be overlooking something simple, but it would seem to depend on the NetworkingEngine providing this information?

ABR plugins have been possible in Shaka for a long time.  Any implementation of the shaka.extern.AbrManager interface can be plugged in via the configure interface:
player.configure('player.abrFactory', () => new MyCustomAbrManager(myCustomConstructorArgs));

The networking system doesn't capture time-to-first-byte latency, but we would be happy to review PRs to improve this so that network latency info is available to ABR plugins.  We would also be happy to review PRs to use that latency info in our default ABR manager.

@avelad, I overlooked a question you asked here.  Sorry!  Yes, we can make EwmaBandwidthEstimator configurable.  Feel free to create a PR that expands the ABR section of the player config and feed it to the estimator.


Forgot to destroy mutex (operating system object leak) - ver <=4.1.1

Environment

Tesseract Version <=4.1.1:

Current Behavior:
Operating system object leak when using LSTMRecognizer (that is tessdata ver 4).
Suggested Fix:
SVMutex (svutil.h, svutil.cpp) hasn't a destructor, so CloseHandle (Windows) or pthread_mutex_destroy (*nix) is never called.
This should be fixed with version 5, but maybe this fix could be useful to people use <=4.1.1 versions.
SVMutex::~SVMutex() {
#ifdef _WIN32
  CloseHandle(mutex_);
#else
  pthread_mutex_destroy(&mutex_);
#endif
}

In master I do not see these variables ever freed as well.
https://github.com/tesseract-ocr/tesseract/blob/master/src/viewer/svutil.h#L56
Try to search here https://github.com/tesseract-ocr/tesseract/blob/master/src/viewer/svutil.cpp
@stweil

@fdivitto, you already suggested a solution for 4.1. Do you want to send a pull request against the 4.1 branch?

SVSemaphore has a similar issue.

Here is my pull request:
https://github.com/tesseract-ocr/tesseract/pull/3398

Thank you. The semaphore part is needed for git master, too.

Solved now.


How to change the listening host?

I am running this on a headless device, so I need to change the listening host so that it is <IP_ADDRESS>, but I cannot see a way to do this? Is it supported?

Hi there, you can pass additional flags to the underlying jupyter runtime in juv run following --. E.g.,
juv run notebook.ipynb -- --ip=<IP_ADDRESS> --no-browser --port=8889


Separate update and output

The update-step for the ingame state updates the world and writes the occured events into a queue, which is IO code. We should better refactor the output code out to keep the update code pure.
Current loop

Input (IO)
Update (IO)
Render (IO)

How it should be

Input (IO)
Update (pure)
Output (IO)
Render (IO)

Done


Is there a way to tear down embeddinated code in memory after use...

I have a Mac alextension library containing a embeddinated library. At a given point the embeddinated ode is loaded. When the user completes I would like to tear down mono before exiting extension.
At moment since extension stays in memory resources remain. I’m forcing an abort() to kill everything but would be nice to have some kind of dispose once embeddinated library loaded.

Since E4K just automatically generates code to ease embedding mono then you still have (manual) control over things - including shutting down the runtime.
However the same limitations would apply

Note that for current versions of Mono, the mono runtime can’t be reloaded into the same process, so call mono_jit_cleanup() only if you’re never going to initialize it again.


Remove TimeSeries references; replace with DataFrame

This closes issue #10. "Convert TimeSeries into DataFrame".  We chose DataFrame and not Series because we wanted the possibility of having a different series in each column, and then run baseflow on each of them all at once.

Ooops- I closed this before merging. Sorry.


Fixed " conversion of single quoted empty string

Changed \expr{''} to \expr{'{'}} in Constants section
See http://haxe.org/manual/expression-constants.html right before 'bar' for the problem. This is undesired behavior in this particular instance in the manual.

Thanks!

 The next build of the manual should propagate to markdown, html etc. right?

It doesn't build automatically at the moment.

Should I propagate it myself or is that all part of the website's regular maintenance?

We'll take care of it.


add Klarna to sites.json

Klarna is an installment payments company as far as I can tell. To delete your account you have to contact customer service.
Their description of how to do this is here: https://www.klarna.com/us/customer-service/how-do-i-close-my-klarna-account/

Thanks for your contribution!


The newer version of spark,adam,sparklingwater for "Genomic Analysis Using ADAM, Spark and Deep Learning" to the people who want to reproduce the test

Now i have some advice for Genomic Analysis Using ADAM, Spark and Deep Learning to the people who want to reproduce the test using the newer version tools:

Hi @nfergu ,i'm so sorry to open a new pull request just now.Because i didn't really know how to open a pull request before.I have been learning how to use it all the time.Sorry about it very much.

@car2008 -- thanks for the pull request. One thing -- when I look at what's changed in Github, it looks like every line has changed (even though they haven't). Is it possible you've changed the line endings on the files before committing them (from unix to DOS)? Perhaps you could run dos2unix on the files.


Adding StandardSSD_LRS as a valid Storage Account Type to TargetExtendedLocations

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
NA, this is not a new feature and does not affect any existing customers.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
January 2023
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

@MSFT-BrianEddy  adding to an existing enum is a breaking change. could you provide justification for @JeffreyRichter

@MSFT-BrianEddy adding to an existing enum is a breaking change. could you provide justification for @JeffreyRichter

Sure.  We have released 3 versions of an API for which there are no customers yet for edgezones. We discovered we need to add new enum value to support a Storage Account type which will be the default value for all edgezones. We want to maintain consistency and for the sake of completeness, we want to add it to released versions. Here is the breaking change workitem: breaking change request for more details. If this is not correct way then please let us know how to proceed with this.

Adding a new enum value must be done in a new api-version. The reason is because we can't have multiple versions of a single API contract (api-version). This is confusing for customers and Azure Customer Support Services (CSS). Also, we have to re-generate all new docs, SDKs, and tools (PowerShell/CLI) for the already-shipped api-version and this is even more confusion for customers.
But, let me also point out that adding a new enum value can be very breaking and it sounds like this is your scenario: What will a client using the old api-version/SDK do when it receives a new enum value that was never documented or possible before? Some apps are very likely to crash or execute unpredictably when this happens.

Adding a new enum value must be done in a new api-version. The reason is because we can't have multiple versions of a single API contract (api-version). This is confusing for customers and Azure Customer Support Services (CSS). Also, we have to re-generate all new docs, SDKs, and tools (PowerShell/CLI) for the already-shipped api-version and this is even more confusion for customers. But, let me also point out that adding a new enum value can be very breaking and it sounds like this is your scenario: What will a client using the old api-version/SDK do when it receives a new enum value that was never documented or possible before? Some apps are very likely to crash or execute unpredictably when this happens.

Jeffery, the service already supports the new enum value for the past 3 versions and there are no customers as of now.  We need to add this change to swagger to reflect documentation for the enum value.

model validation issues are not introduced by this PR and are being resolved in a separate PR


Feature/environment variables

good catch

Added feature flags to browser configuration https://github.com/Availity/eslint-config-availity/commit/32710bbef4ff52ef18661959886247d3c8bd8b4c

I think what I'll do is document the version of eslint-config-availity that is needed to use the feature flags without modifying the projects esltintrc.yaml.


feat: channel Joins

SUMMARY
In renaming the datasets, one of the joins was incorrectly written. This fixes that.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:

After:

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

🏷 2021.31


GRPC C# iOS native extension build

I am trying to build the latest available unity package with bitcode enabled. When I tried to follow the instructions in the commit #6753812278. I only get macOS native libgrpc.a file under cmake folder by running python3.9 run_tests.py -l csharp -c dbg --build_only. Should I run something else or look for somewhere else to build unity package?

I managed to build static libraries with this post https://www.technicallywizardry.com/cross-compile-grpc-unity/. And I used v1.44.0 to make it compatible with Firebase Unity SDK. However, libgrpc.a file size is too big. After building with make strip command, file's size is 350 MB (which contains only arm64 architecture) is there any way to reduce its size we can not use this in a mobile game?


Poetry/Docker Issue

Correct me if I am wrong but with something like https://github.com/tiangolo/full-stack-fastapi-postgresql/blob/master/{{cookiecutter.project_slug}}/backend/backend.dockerfile#L13
Won't that prevent the dev dependencies for testing and stuff from ever working?  Maybe it should have a check similar to https://github.com/tiangolo/full-stack-fastapi-postgresql/blob/master/{{cookiecutter.project_slug}}/backend/backend.dockerfile#L19 to install dev dependencies or am I missing something?
Still kind of learning poetry so its possible I'm missing something but when I tried adding pytest-cov for example to the pyproject.toml as a dev dependency I can only seem to get it working outside the container so that led me to this.
So I am pretty sure this needs to be changed to something like this which I am trying:
RUN echo "$env" \
  && poetry install \
    $(if [ "$env" = 'prod' ]; then echo '--no-dev'; fi) \
    --no-interaction --no-ansi --no-root

this above seems to work but still not sure if more is needed since it seems like every time I run the test-local.sh now it installs all the dependencies each time.  Might just be how it will work since it takes it down each time, etc.

Hehe, yep, that's right.
I just finished updating all that today. There's now an ARG in the Dockerfiles that installs testing dependencies conditionally, for running the tests, or when developing locally.
Also, now that it uses the TestClient, there are new instructions about reporting test coverage in the generated docs.

Ok great gonna close it out.


[feat] Replace Map with a generic implementation

Hello! :)
Based off this passage in your introductory blog post:

Unfortunately, we don't have the handy map function like in Javascript (until we get generics 🤞)
- https://www.maragu.dk/blog/gomponents-declarative-view-components-in-go/

I replaced the implementation of Map with a generic one that's (in my opinion) easier to use than the previous. The examples and tests have also been updated to match. The CI test runner has also had versions of Go prior to 1.18 removed from the testing matrix.
A couple of things to consider:

This is very much a breaking change
This bumps the minimum required Go version from 1.15 to 1.18

Thanks!

Hey @codemicro. Thank you for the contribution!
I've also played around with a generics implementation recently, also for Map (pretty much the same you've done, but dropping the index int) but also trying to figure out if there are other places where it makes sense to introduce type parameters. So far, I haven't found anything other than Map, so I've been holding off on making this change for the same reasons you mention: it's a breaking change, and it requires Go 1.18.
For those reasons, I don't think I want to introduce generics into the library just yet.

That's perfectly understandable! This was just a shot in the dark, since I had a few spare minutes and felt like playing with it.
Thanks for taking the time to look over it, though :)

BTW, I'm trying to figure out if type parameters could be a nice way to make a distinction between HTML elements, attributes, and other kinds of DOM nodes in the type system, while pretty much keeping the current API. So far, I haven't come up with anything good without using hacky things like tagging interfaces.

That's perfectly understandable! This was just a shot in the dark, since I had a few spare minutes and felt like playing with it.
Thanks for taking the time to look over it, though :)

It's really appreciated! 😊

BTW, I'm trying to figure out if type parameters could be a nice way to make a distinction between HTML elements, attributes, and other kinds of DOM nodes in the type system, while pretty much keeping the current API. So far, I haven't come up with anything good without using hacky things like tagging interfaces.

This is a really interesting idea, though I'll admit I also don't really have any good ideas for it either. I'm still quite new to generics in Go myself, I've only written a little bit of code using it thus far.

(Also, I just wanna note that I'm pretty interested in this project - I've used github.com/stevelacy/daz a decent bit in the past, but this seems like a more mature and usable version of that.)

(Also, I just wanna note that I'm pretty interested in this project - I've used github.com/stevelacy/daz a decent bit in the past, but this seems like a more mature and usable version of that.)

That's nice to hear! I didn't know about daz, looks pretty similar in some respects.
I've seen quite a few projects that do something similar to gomponents. I think the main distinction comes down to the API (basically look and feel of writing components) and simplicity. I'm really trying hard to create something that looks like HTML, but is actually Go, while keeping it as simple as possible.
If you're interested, I could tag you here on Github if I ever come up with an API design I could use some feedback on? (I recently did that with others in #101, for example.) Then you can always decide whether you want to answer or not, obviously. 😊

Please do!


Update README.md

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

In order to install JS1 I think it is needed to export AWS_SAGEMAKER_JUPYTERSERVER_IMAGE=jupyter-server first.


IOSim versions of Server2 tests

@UlfNorell sorry you'll need rebase again, we pushed today a p2p-master branches based on 1.27.0 release of cardano-node.

It looks like my commits are already on coot/io-sim-netenv. Should I rebase and keep the PR open for the cosmetic changes?

It looks like my commits are already on coot/io-sim-netenv.
Are you sure? The coot/io-sim-netenv branch is at aaed567aaa85695a8d760b5383b798cb7490787f right now.
Should I rebase and keep the PR open for the cosmetic changes?
Squash the cosmetic changes onto right commits, and I'll merge it to coot/io-sim-netenv.

Oh no you're right, that was my local copy. My bad.


Questions about the capabilities of JobDispatcher

I'd like to know what are the capabilities of it, so I created a StackOverflow post for it:
http://stackoverflow.com/q/37720015/878126

yes , especially please clarify (or add a section) on how to make recurring jobs


Multiple Runs again

@Munsio Do we still need this PR?

not part of an official evaluation ... we can still reopen and merge if we feel like it

Would ask @zimmski if he wants the results in any reporting folder inside the Repo, also thought that those runs are just some kind of "lets try that out"


Redundant Assignment and Potential Nil Pointer Dereference in reconcileDesiredNetworkInterface

In the reconcileDesiredNetworkInterface method, the line mountedNic.networkInterface.Handle = providerNic.Handle appears redundant as it is not utilized. This assumes mountedNic is non-nil before checking the map element, which may cause a panic.

@sujeet01 could you pls provide link to problematic part of code? thx

@sujeet01 could you pls provide link to problematic part of code? thx

https://github.com/ironcore-dev/libvirt-provider/blob/a4e506dffae7435e2ae9a65bcf2c0f72812dad44/pkg/controllers/machine_controller_nics.go#L219


Active report should be visible in sidebar if mode is GSD

Please Review.
Details
We forget to set the Check for Pinned and Active report while adjusting the SiebarOptions for the GSD mode. I have fixed it and Make the if statement more readable.
Fixed Issues

Fixes #1682
Tests

open any chat.
Now Set the Settings Preioty Mode to GSD.
Active report should be visible in the sidebar.

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

https://user-images.githubusercontent.com/24370807/110586774-b2d13800-8198-11eb-9d9e-fbbefe1991e5.mp4

@Jag96  Here we go. Updated. Please review.


Google Maps Plugin Issue

Google Maps shows in a different color rather than normal in Redmi 6 Pro. Issue with the Android View somewhere. Colors are inverted only in Redmi 6 Pro. Please fix the issue or provide the way to fix it. It also leave some space on the top.

Are you using the lastest version of google_maps_flutter?
Can you provide the steps or code to reproduce?
And the $ flutter doctor -v log

Yes it is the latest version. Infact initially I thought I was the plugin
issue, so I started writing my own plugin and found out the result to be
the same. This issue is seen in redmi mobiles and in addition to change of
map color, there is even a unwanted padding on the top of the map which is
being sent by the platform view( that is used by Google maps plugin to send
the native map from sdk to flutter).
On Thu 6 Jun, 2019, 3:48 AM Melvin Salas<EMAIL_ADDRESS>wrote:

Are you using the lastest version of google_maps_flutter?
Can you provide the steps or code to reproduce?
And the $ flutter doctor -v log
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/33911?email_source=notifications&email_token=AMGJTW6PVZ7PZF76BYAFKYTPZA3UBA5CNFSM4HTVBSK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXBFS4Q#issuecomment-499276146,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMGJTW5KQFL5NG47PAF4CX3PZA3UBANCNFSM4HTVBSKQ
.

@melvinsalas Can you just try out the flutter google maps plugin with your available phones, if MI available. I faced the issue on MI 6 Pro. I will even post the flutter doctor logs in the comment.

Hey @melvinsalas  I have got the issue fixed, as I used the existing issue thread and followed  the steps he did #28121 by updating the Android OS from MIYI 10.2 to 10.3 Android 9 Pie and got the issue fixed.

@GadepalliAditya1998 It's a great news 🎉
Please close the issue and keep contributing on the community


Blog

Should I make a blog? This would likely be in v2 of the site.
Yup, gonna add a blog.

Not now!

Gonna try and set this up. I think if I write small, targeted posts about very specific FE problems, then I might be able to keep it up.
We shall see!


DecoratedBox's border doesn't rendered properly

Steps to Reproduce

Execute flutter run on the code sample

Expected results:

Child of DecoratedBox should not overwrap border.
Actual results:

Child of DecoratedBox overflow border.

Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
        title: 'Flutter Demo',
        home: Scaffold(
          appBar: AppBar(
            title: const Text('Flutter Demo Home Page'),
          ),
          body: Center(
            child: DecoratedBox(
              decoration: BoxDecoration(
                color: Colors.blue,
                borderRadius: const BorderRadius.all(Radius.circular(10)),
                border: Border.all(
                  color: Colors.red,
                  width: 10,
                ),
              ),
              child: const SizedBox(
                width: 100,
                height: 100,
                child: Text('Hello'),
              ),
            ),
          ),
        ));
  }
}

Logs
[!] Flutter (Channel master, 3.7.0-23.0.pre.23, on macOS 13.1 22C65 darwin-arm64, locale en-KR)
    • Flutter version 3.7.0-23.0.pre.23 on channel master at /Users/suhwancha/development/GitHub/flutter
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/2.18.5/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/suhwancha/development/GitHub/flutter. Consider adding /Users/suhwancha/development/GitHub/flutter/bin
      to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d53cc4a10f (64 minutes ago), 2023-01-19 00:04:22 -0800
    • Engine revision 40f7f0f099
    • Dart version 3.0.0 (build 3.0.0-136.0.dev)
    • DevTools version 2.20.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/suhwancha/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.74.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.56.0

[✓] Connected device (2 available)
    • iPhone 14 Pro (mobile) • 8901C55B-ACF1-4F3C-A0B6-A09F5A03E555 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-2 (simulator)
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 109.0.5414.87

[✓] HTTP Host Availability
    • All required HTTP hosts are available

Thanks for the report. I see the same behavior using latest versions upon running the code sample as-is.
I tried to replace DecoratedBox with Ink widget, with which, we get the expected result:

child: Ink(
              decoration: BoxDecoration(
                color: Colors.blue,
                borderRadius: const BorderRadius.all(Radius.circular(10)),
                border: Border.all(
                  color: Colors.red,
                  width: 10,
                ),
              ),
              child: const SizedBox(
                width: 100,
                height: 100,
                child: Text('Hello'),
              ),
            ),

Another solution that you can try and check (using DecoratedBox) is to use SizedBox.fromSize and pass size as Size.fromRadius which also gives you expected result as below:

body: Center(
            child: DecoratedBox(
              decoration: BoxDecoration(
                color: Colors.blue,
                borderRadius: const BorderRadius.all(Radius.circular(10)),
                border: Border.all(
                  color: Colors.red,
                  width: 10,
                ),
              ),
              child: SizedBox.fromSize(
                size: Size.fromRadius(50),
                child: Padding(
                  padding: const EdgeInsets.all(8),
                  child: Text('Hello'),
                ),
              ),
            ),
          ),

@darshankawar It works with Container (expected result screenshot is taken from Container widget), but I think it should work with in DecoratedBox.

From DecoratedBox documentation, it is explicitely stated that this is intended and that the solution is to use a Container.
"Container insets its child by the widths of the borders; this widget does not."
(FYI, DecoratedBox is one of the primitive building blocks for Container)
@SuhwanCha Do you have a use case where you can not rely on a Container instead of a DecoratedBox?

@bleroux Nope, I cannot find case that I rely on DecoreatedBox, but my linter complaint use decorated box instead becasuse it's const, but it works differently with Container and DecoratedBox.
We might change linter, use_decorated_box option not to be complained when there is border

Thanks for your insights @bleroux and feedback @SuhwanCha
Based on above response, I am going ahead and closing as WAI. If you disagree, write in comments and I'll reopen it.

@bleroux Nope, I cannot find the case where I need to DecoreatedBox instead of Container, but my linter complaint to use DecoratedBox instead because it's const, but it works differently with Container and DecoratedBox. We might change the linter, use_decorated_box option not to complain when there is border

@SuhwanCha
That's a really good point 👍
It would be great if you can open another issue pointing out to this linter issue (it will be more actionable than updating this existing issue because it is a very different area). Thanks!


Could this work with FF bookmarks?

Would it be possible to make this work with bookmarks? For example, I'd like to copy an existing FF link in my bookmark toolbar as Markdown link?

No, unfortunately, but you can export bookmarks as HTML, open that HTML in Firefox and right click on the link you want to copy.


New runLook returns large list instead of dataframe

I have a fairly simple look with 5 columns, including two pivot columns. Using the new sdk approach, I used runLook and got a large list of 20 elements:
id, supports_pivot_in_db, null_sort_treatment, from_cache, expired, ran_at, pivots, sql, sql_explain, fields, fill_fields, has_totals, has_row_totals, applied_filters, applied_filter_expression, explore, timezone, data, errors, drill_menu_build_time
Each element in the "data" element is a row of the data (with a number of extra fields, such as $connector_referral.unconverted_ts_date$links[[1]]$url). I can extract the data values I need, but this is cumbersome and not behavior I was expecting. Is this due to using pivot columns?

@chrispatrickcville You're mostly correct about the pivots. The new method is a bit cumbersome, but I left it in place to leave room for when people are using pivots in their query. I was going to return a data.frame for unpivoted queries and a list for pivoted queries, but I'm uneasy about returning a different data structure in a way that is hard to predict for the client, so they both return the whole response for now. You can limit the amount of extra fields that come through by setting the resultFormat to just json (the default is json_detail).
The short-term goal for the next release is for runInlineQuery and runLook drop a data.frame by default, but I am unsure of what to do with queries with pivots in them, since expanding the pivots could get messy. I'll update this issue when my indecision has been resolved!

Thanks!

In case it helps anyone, I did this to turn the json back into a dataframe:
get_look <- function(y) {
  look_json <- sdk$runLook(lookId = y, resultFormat = "json")
  out <- data.frame(do.call("rbind", lapply(look_json, function(x) {
    x[sapply(x, is.null)] <- NA
    unlist(x)
  })), stringsAsFactors = FALSE)
}

df <- get_look(1)

Now it seems that the data structure is cleaned up, but I can't access the pivot columns any longer.

I've pushed some changes to the dev branch that make the default behavior to crunch the data into a data.frame which works fine for pivoted and unpivoted Looks. It automatically expands each pivot column into its own column so this can potentially result in very wide data.frames. I'll merge the change into the master branch at some point soon, but you can use it now by installing from the dev branch:
devtools::install_github("looker/lookr", ref="dev")

I had the same issue

Using the main lookr library this code worked like a charm:
data <- sdk$runLook(lookId = 298) df <-data.table::rbindlist(data, idcol = TRUE)
Still error with sdk$runInlineQuery

@chrispatrickcville @tectoniccollinlooker yep, my bad. i'm working on a fix right now that isn't a short term as the last one I pushed.
Unfortunately R doesn't have very many good tools for ensuring that your dev environment isn't being polluted by other things installed on your disk so I'm setting up a test environment in a VM right now to make sure my changes here won't break on machines other than mine.
I'll update as soon as the tests pass.

hey thanks to the folks in this thread for being my guinea pigs here, I've pushed about a dozen more changes while testing different fixes on the vm and found one that works. i get a bunch of compilation errors while installing on a debian-based system but it didn't seem to get in the way of installing and running runLook

Install works great for me now --- no errors

For me, a few listed errors but it installed the library anyway and appears to be working fine.
And the runInlineQuery() works beautifully I am getting a data frame

seems like the difference is between installing on a machine using clang as the C compiler vs. gcc/g++. I think clang doesn't show those errors. At any rate, seems like this is working ok. I'm going to close this issue and eventually up the version number and merge to master, since this might be a breaking change for some people


Option to use fetch instead of axios

Is your feature request related to a problem? Please describe.
fetch (native or polyfilled) is already common in many NodeJS and front-end projects. It will be useful to reuse existing fetch instead of requiring axios in the SDK.
Describe the solution you'd like.
Require axios by default but allow configuring the SDK's client to use fetch instead. If fetch is configured and not available, throw an error. Allow providing a specific fetch implementation instead of global or require('fetch').
Describe alternatives you've considered.
Leaving axios as the only option. axios is a popular package. But having the ability to switch can decrease the bundle size of the entire project and provide fetch responses which the project already handles.
Additional context
-

https://github.com/spree/spree-storefront-api-v2-js-sdk/pull/233


server rejected WebSocket connection: HTTP 404 (code = 1006, reason = [no reason])

Webex Bot version: 0.2.6
Python version: 3.8.0 64-bit
Operating System: win10

Description
Describe what you were trying to get done. Tell us what happened, what went wrong, and what you expected to happen.
Server rejected websocket connection, don't know how to fix it, can you give me some advice?
i replaced some phrases with "xxxxxx" in the following logs to hide some id's (because i'm not shure if they are access tokens or something like that).

2021-07-06 16:10:56  [INFO]  [webex_websocket_client.root._connect_and_listen]:152 Opening websocket connection to wss://mercury-connection-partition0-a.wbx2.com/v1/apps/wx2/registrations/xxxxxxxxxxx/messages
2021-07-06 16:10:56  [DEBUG]  [protocol.websockets.protocol.init]:244 client - state = CONNECTING
2021-07-06 16:10:56  [DEBUG]  [protocol.websockets.protocol.connection_made]:1340 client - event = connection_made(<_ProactorSocketTransport fd=956>)
2021-07-06 16:10:56  [DEBUG]  [protocol.websockets.protocol.data_received]:1412 client - event = data_received(<39 bytes>)
2021-07-06 16:10:56  [DEBUG]  [client.websockets.client.write_http_request]:82 client > GET /v1/apps/wx2/registrations/xxxxxx/messages HTTP/1.1
2021-07-06 16:10:56  [DEBUG]  [client.websockets.client.write_http_request]:83 client > Headers([('Host', 'mercury-connection-partition0-a.wbx2.com'), ('Upgrade', 'websocket'), ('Connection', 'Upgrade'), ('Sec-WebSocket-Key',
'ivFtcbfe+SeI0BHDHkZVDg=='), ('Sec-WebSocket-Version', '13'), ('Sec-WebSocket-Extensions', 'permessage-deflate; client_max_window_bits'), ('User-Agent', 'Python/3.8 websockets/8.0.2')])
2021-07-06 16:10:57  [DEBUG]  [protocol.websockets.protocol.data_received]:1412 client - event = data_received(<1135 bytes>)
2021-07-06 16:10:57  [DEBUG]  [client.websockets.client.read_http_response]:108 client < HTTP/1.1 404 Not Found
2021-07-06 16:10:57  [DEBUG]  [client.websockets.client.read_http_response]:109 client < Headers([('TrackingID', 'ROUTER_60E46470-F3B4-01BB-256B-3E9C9709256B'), ('Cache-Control', 'no-cache, no-store'), ('Upgrade', 'websocket'), ('Connection', 'upgrade'), ('Sec-WebSocket-Accept', 'xxxxxxx'), ('Content-Type', 'text/html;charset=utf-8'), ('Content-Language', 'en'), ('Content-Length', '714'), ('Date', 'Tue, 06 Jul 2021 14:10:56 GMT'), ('Server', 'Redacted'), ('Strict-Transport-Security', 'max-age=63072000; includeSubDomains; preload')])
2021-07-06 16:10:57  [DEBUG]  [protocol.websockets.protocol.fail_connection]:1257 client ! failing CONNECTING WebSocket connection with code 1006
2021-07-06 16:10:57  [DEBUG]  [protocol.websockets.protocol.close_connection]:1203 client x closing TCP connection
2021-07-06 16:10:57  [DEBUG]  [protocol.websockets.protocol.connection_lost]:1354 client - event = connection_lost(None)
2021-07-06 16:10:57  [DEBUG]  [protocol.websockets.protocol.connection_lost]:1356 client - state = CLOSED
2021-07-06 16:10:57  [DEBUG]  [protocol.websockets.protocol.connection_lost]:1361 client x code = 1006, reason = [no reason]
2021-07-06 16:10:57  [ERROR]  [webex_websocket_client.root.run]:167 runException: server rejected WebSocket connection: HTTP 404

What I Did
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

runException: server rejected WebSocket connection: HTTP 404
code = 1006, reason = [no reason]

Thank you very much!

I just had the same happen. Something to do with the bot token id. Same code, same token was working just fine a few days ago, and now this 404/1006 error exit. Swapped out the bot id token and it works again.
The bot token is valid, I can do api calls such as list room members or send messages, but can't be used for the websocket connection.

Fixed in version 0.2.7


Initial commit - Updated to follow uxpin

Issue #: /bcgov/entity#19039
Show the name and business type of the holding company
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

Unit test in progress

Temporary Url for review: https://business-create-dev--pr-641-clib6d86.web.app

/gcbrun

Temporary Url for review: https://business-create-dev--pr-641-clib6d86.web.app

/gcbrun

Temporary Url for review: https://business-create-dev--pr-641-clib6d86.web.app


Question regarding gas transmittance calculation using libRadtran

Hi, thanks for maintaining the great open source code. I encountered some issues while using it and I’m looking for help.
Questions
I want to use libradtran to perform gas absorption correction of a satellite, but my results are different from the paper. This question has been bothering me for several days, so I’m posting this issue for help.
I used verbose mode to obtain the H2O optical depth, then used spectral convolution method to obtain the optical depth of the satellite band, and used Beer-Lambert’s law to obtain the transmission.

Ideal results:(snapshot from a paper)

my results:
It should be a curve, but it's a straight line

my code
from pyspectral.rsr_reader import RelativeSpectralResponse
from pyLRT import RadTran, get_lrt_folder
import matplotlib.pyplot as plt
LIBRADTRAN_FOLDER = get_lrt_folder()

# use pyspectral to read the RSR of the satellite
band = 'ch2'
sat = 'GOES-19'
sensor = 'abi'
rsr_obj = RelativeSpectralResponse(platform_name=sat, instrument=sensor)

wave_list = rsr_obj.rsr[band]['det-1']['wavelength'] * 1000
response_list = rsr_obj.rsr[band]['det-1']['response']
wave_min, wave_max = np.nanmin(wave_list), np.nanmax(wave_list)

# "options" in pyLRT is equal to the lines of libradtran input file
slrt = RadTran(LIBRADTRAN_FOLDER)
slrt.options['rte_solver'] = 'disort'
slrt.options['source'] = 'solar'
# slrt.options['wavelength'] = '200 2600'
slrt.options['output_user'] = 'lambda eglo eup edn edir'
slrt.options['zout'] = 'TOA'
slrt.options['albedo'] = '0'  # ignore the signal of surface

# setup the wavelength to the
slrt.options['wavelength'] = f'{wave_min:.0f} {wave_max:.0f}'

# loop each water vapour content
h2o_list = np.linspace(0, 100, 10)  # unit: mm

trans_list = []  # Result: Transmittance
for h2o in h2o_list:
    slrt_t = copy.deepcopy(slrt)
    slrt_t.options['mol_modify'] = f'H2O {h2o} MM'
    sdata, sverb = slrt_t.run(verbose=True)

    band_response_inter = np.interp(sverb['gases']['wvl'], wave_list, response_list, left=0, right=0)

    # h2o optical depth, two dimensions: (wavelength, vertical_layer)
    #  I've roughly read the source code of pyLRT, it read the output matrix of libradtran
    tau_h2o = sverb['gases']['h2o']

    # convolution each wavelength to band
    numerator = np.nansum(band_response_inter * tau_h2o.sum(axis=-1))
    denominator = np.nansum(band_response_inter)
    tau_h2o_band = numerator / denominator

    # Calculate transmittance using beer-lambert's law
    t = np.exp(-tau_h2o_band)
    trans_list.append(t)

plt.plot(np.array(h2o_list) / 10, trans_list)
plt.xlabel('Water Vapor Column Content [cm]')
plt.ylabel('Transmittance')
plt.title(f'{sat} {sensor} {band} libradtran')

plt.xlim([0, 10])
plt.ylim([0.95, 1])
plt.minorticks_on()
plt.tight_layout()
plt.show()

Thanks for the report and the sample code - this is not the support for LibRadTran, but just a python wrapper. If you think there is an issue with libradtran itself, the libradtran team will be more use.
You can set pyLRT to print the file used for LibRadTran/uvspec with 'print_input=True' as an argument to the 'run' method.
It is tricky to know what the issue here is without knowing what you are trying to reproduce (which paper is it from) and I am not familiar with the PySpectral setup. However, LibRadTran has an option 'filter_function_file', which might help with the filtering.

Thank you for your reply, I will study libradtran again, if it is solved, I will write a feedback here


add(libraries): Svelte Headless UI

Name
Link

Svelte Headless UI
GitHub

Unofficial Svelte port of Headless UI, the component library by Tailwind Labs that powers Tailwind UI

[x] My item is in the right category
[ ] My item is logically grouped below similar items
[x] My item's name and description respects the conventions of the list
[x] My item is awesome
[x] My item is in line with the Tailwind brand usage guidelines
[x] I have read and followed the contribution guidelines

Re: "my item is logically grouped below similar items", I think by that standard it should go closer to the main Headless UI entry. But I put it at the bottom of the library emoji list per the contribution guidelines. Up to you what to do about it.

Great project, is the name fine here? cc @joshmanders
I think it's stated enough that the project is unofficial, but I want to make sure

@innocenzi yeah I think it should be fine.


2.0 frozen rows and columns

@JLynch7 Indeed, the frozen column/row feature is quite necessary feature, thank you for all your commits here. Is your PR complete? And if possible, could you briefly explain your solution?


Use HttpApp instead of HttpRoutes in Http4sServlet

Same NotFound behavior as with HttpRoutes for unspecified endpoints (see NotFoundHttpAppSpec)

Preserve retrocompatibility in JettyBuilder, ServletContextSyntax, TomcatBuilder

Actually, if the motivation behind this PR is to just add mountHttpApp to the builders - can't we just add something like this to JettyBuilder and TomcatBuilder?
def mountHttpApp(service: HttpApp[F], prefix: String): Self =
    mountService(service.mapK(OptionT.liftK[F])), prefix)

This way we wouldn't have to break anything.
Unless, of course the change to the servlets is the main goal - in which case I don't see the point of it, since we can always get a HttpApp from HttpRoutes with .orNotFound.

So, to summarize the discussion (and to get my thoughts in order):

You want to add a way to mount HttpApps in Jetty and Tomcat builders via mountHttpApp. I think this is useful, and it should be done.
The easiest way to do this is to add mountHttpApp that factors through mountService, as I proposed before. However, in this case the HttpApp would be transformed to HttpRoutes, just to be later made back into a HttpApp in the servlet implementation via .orNotFound. This is a bit silly.
Looking at the servlet implementations, it makes sense for them to receive a HttpApp instead of HttpRoutes they get now, since the Servlet interface itself implies that every request should get a response. It makes sense to move .orNotFound outside the servlet implemenation, since this adds flexibility. So you've changed the constructors for servlet implementations to use HttpApp (so that mountService factors through mountHttpApp). Even though this is a breaking change, it shouldn't be hard to fix in the calling code (a single .orNotFound), and there's probably not a lot of such code out there. All of this seems completely reasonable to me.
The recover { case _: MatchError => thing is a hack to make tests compile without updating them. It should be removed.
Regarding the tests for all of the above, I don't think we need any beyond updating the ones that are already there. This includes fixing any non-exhaustive matches.

Hello @nigredo-tori , I have fixed the PR following your advice.
I kept NotFoundHttpAppSpec because I think it is good to have a test on JettyBuilder.mountHttpApp. Also it displays how NotFound can be handled, while it is handled by default when using JettyBuilder.mountService.

For some reason Travis CI keeps failing on 1 of the 3 test machines:
[error] ## Exception when compiling 2 sources to /home/travis/build/http4s/http4s/json4s-jackson/target/scala-2.13/classes
[error] scala.reflect.internal.FatalError: Error accessing /home/travis/.cache/coursier/v1/https/repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar

but it is successful on the 2 others.
Please let me know what you think and thank you for your help !

I kept NotFoundHttpAppSpec because I think it is good to have a test on JettyBuilder.mountHttpApp.

We already test it in JettyServerSpec since mountService factors through it.

Also it displays how NotFound can be handled, while it is handled by default when using JettyBuilder.mountService.

This by itself is not a sufficient reason for adding tests. Also, the most common case for making a HttpApp from HttpRoutes (.orNotFound) is already used extensively throughout the documentation. Manually handling this depends on the use case, and should be reasonably easy to arrive to for people familiar with Kleisli and OptionT, just by looking at HttpRoutes and HttpApp types.

:thumbsup: from me. @hamnis, @rossabaker, please take a look again - this PR has gotten a lot lighter.

I cleared the travis cache and restarted the build, can be merged on build success.


SessionTokenError & PrismaClient is not configured to run in Vercel Edge Functions or Edge Middleware

Bug description
PrismaClient fails to initialize in an Edge Runtime environment (Next.js middleware) despite using the recommended configuration with driver adapters and Neon's pooled connections. The error persists even after following the official documentation for Edge compatibility.
How to reproduce

Set up a Next.js project with Prisma and NextAuth.
Configure Prisma for Edge compatibility in schema.prisma

generator client {
  provider        = "prisma-client-js"
}

datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL")
}

Set up Prisma client in prisma.ts:

import { PrismaClient } from "@prisma/client";

const globalForPrisma = globalThis as unknown as { prisma: PrismaClient };

export const prisma = globalForPrisma.prisma || new PrismaClient();

if (process.env.NODE_ENV !== "production") globalForPrisma.prisma = prisma;

Configure NextAuth to use PrismaAdapter in an Edge environment.
Set up Next.js middleware to use NextAuth.
Run the application and attempt to access a route that triggers the middleware.

Expected behavior
Prisma Client should initialize successfully in the Edge Runtime environment, allowing the middleware to function properly with database access.
Actual behavior
The application throws a PrismaClientValidationError with the message:
PrismaClient failed to initialize because it wasn't configured to run in this environment (Edge Runtime (Vercel Edge Functions, Vercel Edge Middleware, Next.js (Pages Router) Edge API Routes, Next.js (App Router) Edge Route Handlers or Next.js Middleware)).
In order to run Prisma Client in an edge runtime, you will need to configure one of the following options:
- Enable Driver Adapters: https://pris.ly/d/driver-adapters
- Enable Accelerate: https://pris.ly/d/accelerate

Prisma information
Schema
datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

model User {
  id            String          @id @default(cuid())
  name          String?
  email         String          @unique
  emailVerified DateTime?
  image         String?
  accounts      Account[]
  sessions      Session[]
  Authenticator Authenticator[]

  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}

model Account {
  userId            String
  type              String
  provider          String
  providerAccountId String
  refresh_token     String?
  access_token      String?
  expires_at        Int?
  token_type        String?
  scope             String?
  id_token          String?
  session_state     String?

  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt

  user User @relation(fields: [userId], references: [id], onDelete: Cascade)

  @@id([provider, providerAccountId])
}

model Session {
  sessionToken String   @unique
  userId       String
  expires      DateTime
  user         User     @relation(fields: [userId], references: [id], onDelete: Cascade)

  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
}

model VerificationToken {
  identifier String
  token      String
  expires    DateTime

  @@id([identifier, token])
}

model Authenticator {
  credentialID         String  @unique
  userId               String
  providerAccountId    String
  credentialPublicKey  String
  counter              Int
  credentialDeviceType String
  credentialBackedUp   Boolean
  transports           String?

  user User @relation(fields: [userId], references: [id], onDelete: Cascade)

  @@id([userId, credentialID])
}

Prisma Initialisation
prisma.ts
import { PrismaClient } from "@prisma/client";

const globalForPrisma = globalThis as unknown as { prisma: PrismaClient };

export const prisma = globalForPrisma.prisma || new PrismaClient();

if (process.env.NODE_ENV !== "production") globalForPrisma.prisma = prisma;

Environment & setup

Next.js version: 14.2.11
Node.js version: [Please provide]
Operating System: [Please provide]
Deployment environment: Vercel (Edge Runtime)
Database: PostgreSQL (Neon with pooled connections)

Prisma Version
prisma                  : 5.9.1
@prisma/client          : 5.12.0
Computed binaryTarget   : darwin-arm64
Operating System        : darwin
Architecture            : arm64
Node.js                 : v21.6.1
Query Engine (Node-API) : libquery-engine 23fdc5965b1e05fc54e5f26ed3de66776b93de64 (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 23fdc5965b1e05fc54e5f26ed3de66776b93de64 (at ../../../../../opt/homebrew/lib/node_modules/prisma/node_modules/@prisma/engines/schema-engine-darwin-arm64)
Schema Wasm             : @prisma/prisma-schema-wasm 5.9.0-32.23fdc5965b1e05fc54e5f26ed3de66776b93de64
Default Engines Hash    : 23fdc5965b1e05fc54e5f26ed3de66776b93de64
Studio                  : 0.497.0

Neither the schema, nor the code you've posted here actually uses driver adapters.
Please double check that you've posted correct code and that you actually following the docs for setting up Neon

Hey @mirkobozzetto  ,
Did you get a chance to have a look at my previous comment? Could you confirm that your issue is solved?
Without further information, we'll have to close this issue. Thank you 🙏

@SevInf I need to update my previous response with an important discovery.
While the split configuration pattern worked initially, we encountered an issue where static assets (images, SVGs, etc.) were not accessible to unauthenticated users in production. Here's the complete solution that finally resolved both the Edge Runtime and static assets issues:

The auth.config.ts now includes explicit static asset handling:

export const authConfig = {
  providers: [Google],
  session: { strategy: "jwt" },  // Changed to jwt for consistency
  callbacks: {
    authorized({ auth, request: { nextUrl } }) {
      const isLoggedIn = !!auth?.user;
      const isAuthPage = nextUrl.pathname.startsWith("/auth");
      const isPublicPage = ["/", "/auth/verify-request"].includes(nextUrl.pathname);
      const isApiRoute = nextUrl.pathname.startsWith("/api");

      // Critical: Handle all static assets
      const isStaticAsset =
        nextUrl.pathname.startsWith("/_next") ||
        nextUrl.pathname.includes("/public/") ||
        nextUrl.pathname.endsWith(".svg") ||
        nextUrl.pathname.endsWith(".ico") ||
        nextUrl.pathname.endsWith(".png") ||
        nextUrl.pathname.endsWith(".jpg") ||
        nextUrl.pathname.endsWith(".jpeg") ||
        nextUrl.pathname.endsWith(".gif") ||
        nextUrl.pathname.endsWith(".webp") ||
        nextUrl.pathname.endsWith(".mp4") ||
        nextUrl.pathname.includes("/images/");

      if (isStaticAsset) return true;
      // ... rest of the routing logic
    }
  }
}

This solution:

Avoids Prisma Edge Runtime issues completely
Ensures all static assets are publicly accessible
Maintains proper authentication flow
Works consistently in both development and production

Key learnings from this journey:

Edge Runtime limitations require careful consideration of static asset handling
Sometimes the simplest solution (like proper static asset routing) is better than complex infrastructure changes
Production environment can reveal issues not visible in development

Thank you for your guidance on driver adapters. While we took a different approach, your feedback helped us understand the problem better and find an appropriate solution.

Closing this issue, as OP was not using driverAdapters.


Prevent BearerTokenAuthenticationPolicy to cause UnobservedTaskException

Removed rethrowing of exceptions
Rethrow cause that result headerValueTcs.Task could be never "touched" and it will cause UnobservedTaskException later (for example when GC is performed)
Because immediately after catch blocks there is a mechanism for returning a result of headerValueTcs.Task we can let rethrow exception at that place. It will prevent possible UnobservedTaskException

All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[x] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

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.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.
If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version,

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

Hi @miroslavpokorny.  Thank you for your contribution and interest in helping to improve the Azure SDK experience.  I've added some tags and routed to the team member best able to offer feedback.

Thanks @miroslavpokorny! Can you reproduce the UnobservedTaskException deterministically in a test with the throw still in place temporarily so that this can be validated?

Hi @christothes I have added test case which on previous implementation fails because of UnobservedTaskException. Test is based on GC (because problem occurs during garbage collecting) so IMO it can be flaky in some cases/ENVs...


Features

Please check over this code and run it on your local machine. It keeps giving me an error when I run it in the command line and I am not sure why! I also wanted to add a default url and path to save the file in so we don't have to type it in every time but got stuck on the download issue.... here is the url the data is at:
https://archive.ics.uci.edu/ml/machine-learning-databases/forest-fires/forestfires.csv

Change this line Usage: python test.py <url> <path> in your documentation to Usage: test.py <url> <path> . This should solve the problem.


Update Influenza sequence DB

Problem description
Data at https://ftp.ncbi.nih.gov/genomes/INFLUENZA/ is out of date. New sequences since 2020-10-13 are available elsewhere on NCBI, e.g. https://ftp.ncbi.nlm.nih.gov/genomes/Viruses/AllNuclMetadata/
nf-flu should be using an updated DB of IAV and IBV seqs from NCBI.

Completed in #25 in release 3.3.0


[Table] Poor performance with a fixed height

My app has Material UI table with 100 records and each row has quite a bit of data to be drawn. Please see the sample below. The data is also updated using setInterval function at 2000ms.
https://stackblitz.com/edit/react-ts-9k8gnl?file=Hello.tsx
When there is a table height set <TableContainer style={{ height: '500px', width: '100%' }}> application performance is very poor. Users cant even scroll to the bottom smoothly.
However when I remove the style={{ height: '500px', width: '100%' }} attribute scroll performance is satisfactory.
What is the reason for this and how can I improve the performance when I have height set.
I am using latest react and MUI versions.
Steps to reproduce

Go to
https://stackblitz.com/edit/react-ts-9k8gnl?file=Hello.tsx
Wait for few seconds till the data loads and try to scroll to the bottom. It will be not smooth.

remove style={{ height: '500px', width: '100%' }}  from the table and try to scroll. The scrolling will be smooth.

Please provide steps to reproduce in detail. (also, a video record is nice in this case)

I have added steps now. thanks

Were you able to solve this?

This looks expected, I'm closing. You can either look into virtualization with https://mui.com/components/data-grid/ or upvote #27290 for a bare version of the table.


Cyberware and NPC import error

So far players aren't having al of their cyberware imported over from the transfer despite meeting all prerequisite and NPCs simply can't be imported over at all, unless that wasn't part of the module.

Here's an id import code for an NPC Harden netrunner (1S7YVU) and Player character (YGELH7)

I have the same problem importing NPC. There's any chance you're going to support that? Thanks in advance for your work!

For YGELH7, it looks like that character had Grafted Muscle and Bone Lace, which was not recognized correctly. I did not encounter any other errors trying to import that character. I will track that bugfix with this issue.
I have opened a separate issue to track NPC support in case it is more complex and takes longer to implement: #4


Design and document cli interface

should at least include:

ability to specify a config file
ability to specify a data file
specify if data is an otp blob or rotation history
choose whether to create or update data on the server


Error when editing post

Describe the bug

when editing a post on url:
http://sleepy-gates-596989.netlify.com/admin/#/collections/post
error show:
Sorry!
There's been an error - please report it!

Error: Unable to find a DOM node for "116". This is often because of forgetting to add `props.attributes` to a custom component.

then I post this issue.
To Reproduce

Expected behavior

Screenshots

Applicable Versions:

Netlify CMS version: [e.g. 2.0.4]
Git provider: [e.g. GitHub, BitBucket]
OS: [e.g. Windows 7]
Browser version [e.g. chrome 22, safari 11]

Node.JS version:

CMS configuration

Additional context

@archcra can you post your config.yml or the code for the custom component? We will not have access to the admin on your site.


Allocate only one Label per tag type, and only one default Label.

I was looking at potential memory optimisations in an application and noticed that currently, a new Label is created each for every Id. This can be avoided by:

Having Label.default always return an existing single default Label value
Defining the implicit on CustomLabel as a val instead
Defining the implicit on MakeLabel as a val, though this comes at the cost of a self type error when attempting to use a non-case object as a tag.

Did you notice this as an actual bottleneck or just a nice to have?
Because if it's a nice to have, I wouldn't want to sacrifice the error message, it can be pretty obscure otherwise.

Yeah, it's a nice-to-have. However, I've made it work using a Manifest instead. With that, it should be possible to remove the case requirement entirely. Is that something you'd like?

Manifest uses reflection though, which means you are getting back a possibly larger perf penalty for that, I think

The manifest is only created once when the tag object and its label are constructed

That's the Manifest version pushed. Should I continue with relaxing the case object requirement?


remove NaNs from RGB and depth images

NaNs can not be a input to the network. They must be mapped to a different value (I think!)

Currently, all NaN values get replaced with 0
Idea: Add mask to tell net where mask values are located
Problem: Mask only for rs nans or also for zv nans?
-> Only for rs nans, as zv NaNs aren't avaliable for test time
Loss: The networks loss function sums up pixel loss,
counting only the ones where no NaN is present in the data


Brave: scrolling gives duplicate values

Bug
When I scroll it is keep repeating the items multiple times.
To Reproduce

Goto any list. for example(https://odysee.com/@IWantMusic:c?view=playlists)
just scroll down. the list is keep repeating. after a lot of repeated items i can see not seen items. but again it is repeating after sometime.

Expected behavior
no duplication
Screenshots

System Configuration

Operating system: Windows 10
Brave browser: Version 1.52.122 Chromium: 114.0.5735.110 (Official Build)  (64-bit)

Additional context
Add any other context about the problem here.

Does it only happen in Brave and not in Chrome? Do you have brave shields on and does that make a difference?

@tzarebczan I have not tested with Chrome. It happens with both the shields on and off in Brave all the time in all the pages.

here is another example: https://odysee.com/@jazz:89?view=content

Can i work on this issue? I see this issue in the firefox browser also.

Sure, go for it!

tzarebczan I don't think this is a front-end issue, if you look at the png image i have, both the "canonical_url and claim_id" are both different, in both brave browser and Chrome browser. So I think this is a back-end issue. Any ideas? Or ideas to test my theory?


[metal] Refcount block pool to outlive resource sets

We use resource sets in iree_hal_metal_device_queue_execute to keep track of command buffers and semaphores and release them when the command buffers complete. It would require the underlying block pool backing the resource sets to have a larger lifetime to make sure we don't access destroyed data structures.
Fixes https://github.com/openxla/iree/issues/14814

hmm I don't think this should be required - block pools are thread safe and should be shared, and you don't want multiple block pools.

hmm I don't think this should be required - block pools are thread safe and should be shared, and you don't want multiple block pools.

Yeah I'm just sharing one block pool across everywhere. The problem is not thread-safety; it's the lifetime of the block pool--we allocate resource sets from it for queue execution. Those resources can be released way later in the command buffer completion hander, so we need to make sure the block pool outlives.

(note that devices are resources and if you need to you can add them to the resource set)

Closing this one given #15288 landed.


Slow stepping when debugging Typescript repos

Investigate again why the stepping is slow when debuggin the Typescript repository (steps take 1 second). More details can be found here https://github.com/Microsoft/vscode/issues/5645
fyi @egamma

Please try for both protocols.

I have compared the performance while debugging the checker.ts file in the typescript repository. Below I have attached three gifs illustrating this. The first one is the inspector protocol debugger which shows very good stepping performance (indistinguishable from debugging a simple file). The second shows the legacy adapter which is in the current insiders / stable and the third shows the legacy adapter with a logging bugfix made by @weinand. When comparing these two it seems like the bugfix did not have a noticable impact on the performance.
Current slowness shown only by the node adapter is due the old node debug protocol returning more data than asked for. @weinand would have to dig more in order to find the exect culprit, however that might not be necessery since we are moving towards using the inspector protocol in any case.
User workaround to get a good experience: add "protocol": "inspector" to your launch.json or update to node version 8 or greater (since then we will automatically pick the new inspector protocol)
Also created a related issue for case with much more local variables https://github.com/Microsoft/vscode/issues/25296
fyi @egamma


Node version not switched, even though it says so

✗ n
    node/0.10.32
  ο node/4.0.0
    node/4.1.2

✗ cd ..
cd avn activated 4.0.0 via ../.node-version (avn-nvm v4.0.0)
✗ cd imgur-client
avn activated v0.10.32 (avn-n 0.10.32)

✗ node -v
v4.0.0

✗ which node
/Users/martins/.nvm/versions/node/v4.0.0/bin/node

Please submit debug info.

Sorry for the missing debug info.
Here you are:
➜  imgur-client git:(master) ✗ __avn_debug
avn activated v0.10.32 (avn-n 0.10.32)
n 0.10.32 > /dev/null;
➜  imgur-client git:(master) ✗ node -v
v4.0.0

Hmm.... Do you have n automatically run anywhere else? Perhaps in your bash or zsh profile/rc?

I'm closing this due to inactivity, but feel free to re-open it if you have any additional info to submit.


burpsuite: 2020.1 -> 2020.9.2

Motivation for this change
Update Burpsuite to the latest release
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] 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.

Upon further testing, the new "embedded browser" feature is not working. Looking into this...

@bennofs what do you think of this fix?
As far as I can tell, the next-best option would be using an FHSUserEnv. Patching the jar does not seem practical.

@ofborg eval

Result of nixpkgs-review pr 100677 run on x86_64-linux 1

1 package built:

burpsuite

Oh, I couldn't get the embedded browser working myself. Nice to see that you managed to do it, I think the fix is ok :+1:

I have updated the PR so that it automatically reads the embedded chromium version at runtime.


Mark Socials As Optional

It seems they're not always sending the socials - this patch marks it as optional in case we're not given them to prevent decoding failure.
WARN  discord_compiler_bot::apis::dbl > Unable to retrieve user info: error decoding response body: missing field `social` at line 1 column 243

I'm having déjà vu with #1, I guess now they're not even sending the section if no socials are filled out.

I published a new version. :rocket: Thank you


ninja: 1.8.2 -> 2018-04-10

Motivation for this change
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)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@matthewbauer Ninja's release hasn't been bumped for a long time, and the git version contains many fixes that aren't in any release, including https://github.com/mesonbuild/meson/issues/3992 which was an issue at my workplace.  The official stance (see comments on that issue) seems to be that distributions should just package the git.
I'm happy to just bump default.nix to the git version if you'd prefer, I just thought it would be safer to keep the release packaged in case the git one broke something.  I see similar patterns for several other packages, e.g. arb/arb-git (though I note that arb-git is actually older than arb, so maybe not a great example…).

Yeah I think we would prefer to just bump ninja. Alternatively, you could just add the patch from https://github.com/ninja-build/ninja/pull/1219.patch with a note about it being in the next released version. This would avoid the potential of including other commits that break things.

Okay, changed it to bump. I think it's if anything safer to bump wholesale than to try to back-port patches.

That should go to staging branch first. I would like to also get an opinion from @jtojnar

I did not look into ninja very much (meson has mostly hide it from me) but, if possible, I would prefer fetchpatching the PR, there might be many changes for the last year and the risk of breakage would be probably greater. We should probably also let ofborg or hydra build at least some of the packages that depend on ninja to be more certain there were no regressions. Otherwise, I also prefer a single package.

@jtojnar seems right that it might be better to pick the relevant commit. I have looked at Ninja commit history and noticed that the master branch introduces this issue: https://github.com/ninja-build/ninja/issues/1418

There may be other updates in there that are important to people.  Maybe we should revert to the original approach of having two packages?

Then they can backport the other patches too. We already have too much of multiple package clutter IMO.

I'm OK with a new ninja-unstable if that helps you participate in its development (at least by testing it), but nevertheless we should include https://patch-diff.githubusercontent.com/raw/ninja-build/ninja/pull/1219.patch in the default ninja.

ninja-1.9.0 has been released: https://github.com/ninja-build/ninja/releases/tag/v1.9.0

Oh, merged as https://github.com/NixOS/nixpkgs/pull/55008

Yep, I decided to leave this minefield alone and push ninja for a proper release instead. Thanks @vcunat :)


UnicodeDecodeError: 'utf-8' codec can't decode byte .... in position 1: invalid continuation byte

When fixing model:
Python: Traceback (most recent call last):
File "C:\Users\AaronWu\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\cats-blender-plugin-master\tools\armature.py", line 969, in execute
Common.fix_twist_bones(mesh, bones_to_delete)
File "C:\Users\AaronWu\AppData\Roaming\Blender Foundation\Blender\3.1\scripts\addons\cats-blender-plugin-master\tools\common.py", line 2096, in fix_twist_bones
mix_weights(mesh, vg_twist1.name, vg_parent.name, mix_strength=0.75)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd0 in position 1: invalid continuation byte
location: :-1

This is an issue with blender 3.0 and 3.1. This is fixed in Development version/branch

This is not fixed in the development version. (yes, the path does say cats-blender-plugin-master, but it is the development version installed there)

If it doesn't fail with a UnicodeDecodeError it often fails with a RuntimeError: Error: Modifier is disabled, skipping apply instead, which may be related since it originates from the same mix_weights function and leaves a single VertexWeightMix Modifier on the mesh, with a missing "Vertex Group A".

Rarely, "Fix Model" will manage to succeed without either of these two errors.

The settings I was using with "Fix Model" was every setting disabled

The model in question that is having these issues is Eiri Shimizu V2.pmx from https://bowlroll.net/file/13980
I did nothing other than Import Model followed by Fix Model

I believe I have found the issue here and it's specific to Blender 3.0+. The problem is that applying the Vertex Weight Mix modifier internally recreates/reorders all of the vertex groups on the object in such a way that they don't necessarily remain in the same memory locations. This means that existing references to vertex groups on a mesh cannot be used after applying the Vertex Weight Mix modifier.
To replicate the issue.

Select a mesh object (I've been using a default cube) and add a few vertex groups
In the Python console: all_vg = bpy.context.object.vertex_groups[:]
Apply a Vertex Weight Mix modifier with default settings and any two of the object's vertex groups as Vertex Group A and B
In the Python console: [v.name for v in all_vg]
In most cases, you will get a UnicodeDecodeError or find that the names are now in the wrong order or are now blank

I think this is a Blender bug, because I can't reproduce it in Blender 2.93 or 2.80, but it occurs on 3.0, 3.1 and the 3.2 alpha build I have. I haven't yet got around to checking the 3.2 release or looking for this issue on Blender's issue tracker.
It's worth pointing out that it's not just the names of the vertex groups that end up broken when this happens, during my testing I tried getting the weights of certain vertices from the old references to the vertex groups and found them giving incorrect results, and similarly, I tried getting the index attribute of the vertex groups and those were incorrect too.

I've made a bug report on Blender's issue tracker for this issue https://developer.blender.org/T98751. We will likely need to come up with a workaround in Cats in the meantime.

Having the same issue on my end.

I'm having a similar problem, however it's with naming visemes. This happens in the development version of Cats. If I were to apply a viseme in a Japanese name, whenever it's applied and if I were to click on one of the 3 options ("Viseme AA", "Viseme OH", or "Viseme CH"), the name would end up gibberish and I'd get the error if I clicked on that name.


Quash some error messages

Hi Sam,
I started using sag in the CodeIgniter framework, and I was getting some PHP errors (notice level).  I cleaned up the library in the places that I saw these messages.
Dave

Hi Dave,
Thanks for the pull request! Always love contributions.
It sounds like you are trying to run Sag under PHP's strict mode. This setting is not supported. I've opened a ticket to create better messaging around this in SagConfigurationCheck.php: issue #39.
Cheers.


Typo under Floating point types

Under Value types, "Floating point types" in the fourth bullet, the phrase "and for double, 0 < m < 2^53 and 1075 <= e <= 970" should presumably read "-1075 <= e <= 970", I think.

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

ID: de24f644-5e7c-d3de-fd13-5969bb3e4b78
Version Independent ID: 9173876e-49be-6c60-634d-eeb1944ab2fc
Content: Types - C# language specification
Content Source: spec/types.md
Product: dotnet-csharp
Technology: csharp-spec
GitHub Login: @dotnet-bot
Microsoft Alias: wiwagn

Thanks for spotting this @gplindauer
I've submitted dotnet/csharplang#2933 to fix this error.


Used Float80 instead (results in an insignificant difference in terms of accuracy)


Web component in Vue: 'is' attribute doesn't work for web component

Version
2.6.11
Reproduction link
https://codesandbox.io/s/tender-wave-kcu39?file=/src/App.vue
Steps to reproduce

Create webComponent which is extended from HTMLButtonElement
Try to use it in Vue project

What is expected?
Vue Api provides for developers the opportunity to ignore some attribute like 'is'
What is actually happening?
Vue renders element as a dynamic component.

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.
Web Components work with Vue but you have to use a different approach than the is attribute. I don't have an article right now to give you.

sorry, got it, thank you. Will find the answer


Some directives convert into :::{<directive>}, not  ```{<directive>}

Describe the bug
When converting e.g. a figure directive
.. _fig_intro_workchain_graph:
.. figure:: include/images/basics_workchain_graph.png
    :scale: 30
    :align: center

    Provenance Graph of a basic AiiDA WorkChain.

This gets converted into

(fig-intro-workchain-graph)=
:::{figure} include/images/basics_workchain_graph.png
:scale: 30
:align: center

Provenance Graph of a basic AiiDA WorkChain.

:::

Expected behavior
Doesn't myst-nb need backticks for the directives? I.e. if I convert this into
(fig-intro-workchain-graph)=

```{figure} include/images/basics_workchain_graph.png
:scale: 30
:align: center

Provenance Graph of a basic AiiDA WorkChain.
```#

This works fine for me.
Similar issues arise for note and important directives (and possibly others that are not in the file I'm converting).
Environment

Python Version [e.g. 3.7.1]: 3.8.6
Package versions or output of jupyter-book --version:$ pip freeze | grep myst
myst-nb==0.13.0a1
myst-parser==0.14.0a2
rst-to-myst==0.1.2

Operating System: macOS Big Sur 11.3.1

Title should be:
Some directives convert into :::{<directive>}, not  ```{<directive>}
But if I copy paste this into the Title and save it, it doesn't work. 🤨
This is seriously triggering my OCD. 😅

See https://myst-parser.readthedocs.io/en/latest/using/syntax-optional.html, you can add colon_fence to the myst extensions to also allow for colons.
(But yeh I intend to make it clearer with this tool when it is outputting syntax that requires extensions)

Update title and OP, can't change label unfortunately 😭


Change LaunchScreen background color.

Test Danger flow 01

Codecov Report

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

@@           Coverage Diff           @@
##             master     #1   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      2
  Lines             ?     31
  Branches          ?      0
=======================================
  Hits              ?     31
  Misses            ?      0
  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 8ca8022...3721283. Read the comment docs.

          1 Warning

:warning:
Any meaningful changes to the project should be reflected in the Changelog. Please consider adding a note there.

  Generated by :no_entry_sign: Danger


No-DASH video option limited by resolution

I launched the application with the option --no-dash. It allows me to use my preferences or seek to time in VLC player. I have set resolution="1080p" in config.
Any video that I play opens in 720p resolution. itag=22 To my surprise in mp4 format. I see in the source code itag=46 is available with webm format.
I would like to play video in 1080p and with --no-dash option. Is this a technical limitation by Youtube or by straw-viewer?

Due to historical reasons (mostly due to my misunderstanding at that time), dash in straw-viewer means videos that are split into audio+video, where audio and video are provided by two different URLs.
The highest resolution for videos with audio+video in the same file, is 720p.
The true DASH option can be controlled by the config-option: dash_segmented.


Allow for sortable column name to be different than field.

I have a json such as this
{
  "id": 5,
  "subject": "My Post",
  "author": {
    "id": 10,
    "name": "Chris"
  }
}

If I create a two columns for displaying both the id and the name of the author, I will use the field author and then use a custom component to do value.id and value.name. This works fine for display purposes but if I want to be able to sort on author.id and author.name the sort field will always be author.
I can do a PR but I want to make sure you're open to it before I spend the time.

you can use your own fork

Do you have any interest in adding that to the project itself? my company is not very fond of using personal forks...

Gotcha. I believe it's not that uncommon but It's your project!
Thanks for your response :+1:

https://codesandbox.io/s/0o4vmpj99v

you are welcome