Add DuckDaoDime (DDIM) and DLP Duck Token (DUCK) to MetaMask

DuckDAO is a decentralized incubator that helps promising projects achieve their full potential by leveraging the investment power and buzz making potential of our community.
We aim to democratize access to investment opportunities that were previously available only to well-heeled investors and venture funds, opening up the closed ecosystem of early-stage crypto project investments to everybody.
Website: https://duckdao.io
Etherscan (DDIM): https://etherscan.io/token/0xFbEEa1C75E4c4465CB2FCCc9c6d6afe984558E20
Etherscan (DUCK): https://etherscan.io/token/0xc0ba369c8db6eb3924965e5c4fd0b4c1b91e305f
Twitter: https://twitter.com/dao_duck/
Medium: https://duckdao.medium.com/
Telegram (DDIM): https://t.me/duckdaolobby
Telegram (DUCK): https://t.me/duckliquiditypool
CoinGecko: https://www.coingecko.com/en/coins/duckdaodime
CoinGecko: https://www.coingecko.com/en/coins/dlp-duck-token

@xrn Let me know if there's any change required or requires additional information.


Angular-jsonapi

For past few months I've been implementing JSON API client for angular.js users. Currently it is in the 1.0.0-alpha state, but I'm planning stable 1.0.0 to be released in the near future. It is accessible at jakubrohleder/angular-jsonapi.
Documentation is only partially ready, so everyone who is interested in using/collaborating - feel free to post issues.
Please also add the link to the Implementations section on the website.

@jakubrohleder Awesome! I'll get it added to the implementations page momentarily.
cc @TechAtNYU/infrastructure-team

Great, Thanks mate!

Added.


parseInt() browser compatibility

Hi guys !
Amazing work on the site, I use it almost everyday. Can you please do a research about parseInt() function ? Like parseInt(' 0xF', 16); ? This is the function on MDN https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/parseInt
Thank you so much !
Kind regards,
Radu

And you can tell me for sure which desktop version, mobile version, platform version is this function supported ? And you're just assuming that everyone is born with all the frontend + backend developer knowledge ? I find your fronting rather noobish and ignorant. To say the least.

Haha wow...

And you're just assuming that everyone is born with all the frontend + backend developer knowledge ?

No, I don't. But in the link you posted yourself, it says it was defined in ECMAScript 1st Edition (ECMA-262). If you had clicked that, you would see that this is from 1997. Also, the table on MDN clearly specifies that all browsers support this.
This does not belong on caniuse.

It would be kind of nice to know which browsers support it without parsing strings that start with "0" as octal.  That would help developers know whether they can use it safely without the radix parameter.  I don't know if that would fit on caniuse, though.

It would be kind of nice to know which browsers support it without parsing strings that start with "0" as octal.

See #1686 (modern browsers no longer parse as octal).

Available at https://caniuse.com/#feat=mdn-javascript_builtins_parseint and https://caniuse.com/#feat=mdn-javascript_builtins_parseint_leading_zero_strings_as_decimal


upgrade to python 3.7

Codecov Report

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

@@           Coverage Diff           @@
##           master     #142   +/-   ##
=======================================
  Coverage   96.05%   96.05%
=======================================
  Files          11       11
  Lines        1572     1572
  Branches      183      183
=======================================
  Hits         1510     1510
  Misses         33       33
  Partials       29       29

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 3e6d61e...726676b. Read the comment docs.


Add SSL certificate support to Cloud SQL sample app.

the MS SQL Server readme update is missing? Or is there no need to change the readme in that case?

Yes no need to change the readme for MS SQL Server at this time.


Visual C++ 14.0 is required to instyall JPype1 on 32bit Python

Hello,
I have a question similar to Issue 510 but then for 32 bit. The error I get is the same.
Could you please also add the 32 bit .whl package to pypi? It would save a lot of time & effort not having to install 6gb of Visual Studio on every system.

I would have to look to see if there is an image in azure that can be used to build the required wheel.


Add FPS Cap

This PR adds an FPS cap feature.
By default, GDTuber will run with an uncapped FPS. This can cause performance issues, especially for slower PCs. Limiting the app's FPS can alleviate these issues.
Note: Changing the max FPS affects ALL aspects of the app, not just the avatar animations! This includes the audio processing and app responsiveness. As a result, the MaxFPSSpinbox node has a minimum value of 15. This value can be changed, and we can add another validation check in the _on_max_fps_spinbox_value_changed method if needed.

Created a new PR #150 updated and tweaked a few things


Bump dependency for inifile

A new version of this module was released to add Puppet 8 support, so bump the dependency in this module to account for it.

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


Possibility with PYNQ3.0

Hello,
Thank you for your information with AXU3EG. I tried to reproduce the image with the PYNQ3.0, but always getting error at the final steps
with the error saying:
++ find ../boards/AXU3EG -maxdepth 2 -iname '*.bit' -printf '%h\n'
find: ‘../boards/AXU3EG’: No such file or directory

overlays=
unmount_special
for fs in $fss
sudo umount -l /media/x2-b7010/data02/xilinx_proj/PYNQ/sdbuild/build/jammy.AXU3EG/proc
for fs in $fss
sudo umount -l /media/x2-b7010/data02/xilinx_proj/PYNQ/sdbuild/build/jammy.AXU3EG/run
for fs in $fss
sudo umount -l /media/x2-b7010/data02/xilinx_proj/PYNQ/sdbuild/build/jammy.AXU3EG/dev
sudo umount -l /media/x2-b7010/data02/xilinx_proj/PYNQ/sdbuild/build/jammy.AXU3EG/ccache
rmdir /media/x2-b7010/data02/xilinx_proj/PYNQ/sdbuild/build/jammy.AXU3EG/ccache
Makefile:371: recipe for target '/media/x2-b7010/data02/xilinx_proj/PYNQ/sdbuild/build/AXU3EG.tar.gz' failed
make: *** [/media/x2-b7010/data02/xilinx_proj/PYNQ/sdbuild/build/AXU3EG.tar.gz] Error 1
=============================================================================
Have you had the same problems during your time?
Also do i need to switch to the sudo to use make compiling?

Best Regards

Sorry, I no longer work on FPGA-related projects and currently don't have any hardware or time to test this.


Enable SockaddrStorage::{as_link_addr, as_link_addr_mut} on Linux.

This was an oversight from #1684.
Fixes #1728

I do think that a patch release would be worthwhile.  But there's one other issue that ought to go into it.  I'll go ping the reporter again.


feat(build): add arm64 support with cross-compilation

Motivation
To run dockerized containers in M1 and other ARM64 processors, we need to cross-compile the Docker image for this platforms. This makes it very hard to test locally, as all builds must be done remotely, or pushing to confirm on GHA.
This supersedes #3678
And reverts: #3791
Solution
Previously, we had to temporarily remove ARM64 support for Zebra until we could improve build times or have ARM64 instances to build it. Now that we're using Docker Build Cloud, we don't have to deploy ARM64 runners specifically for this task.
Tests

Download the resulting artifact to an ARM64 machine and run it with docker, without using CPU virtualization.

Follow-up Work

Must be done here: Update documentation for supported platforms.

PR Author's Checklist

[x] The PR name will make sense to users.
[x] The PR provides a CHANGELOG summary.
[] The solution is tested.
[ ] The documentation is up to date.
[x] The PR has a priority label.

PR Reviewer's Checklist

[ ] The PR Author's checklist is complete.
[ ] The PR resolves the issue.

We won't be able to do this until https://github.com/zcash/lightwalletd/pull/476 is merged, and we don't have a deadline for that.


Packaging and doc

Put all functions and modules into a package, (named ovrolwasolar)
After install the package, the functions and pipeline can be used with more flexibility (not necessarily be in the same directory)
More detailed see the added part of README in this commit

@surajit4444mondal I reviewed the changes @peijin94 made. I think this PR should work and can simplify the workflow of installing the package. But it does change the current structure of the repo. Please take a look and let us know if you have any comments before I merge.

Thanks @surajit4444mondal for all the suggestions, updated solar_pipeline.py accordingly


stats_flush_interval ignored

Hi
When envoy loses connection to the control-plane it starts sending 2 metrics every second:
envoy.test-service.global.XX.test-service_12345.cluster.envoy-control-xds.upstream_cx_length_ms:2|ms
envoy.test-service.global.XX.test-service_12345.cluster.envoy-control-xds.upstream_cx_connect_ms:1|ms
It stops respecting the status_flush_interval

For statsd (which I assume you are using), histograms are flushed immediately.


Add Proxy support

This change adds the ability to specify SOCKS or other proxies to be used by Instaloader when making HTTP requests.
Here is an example of creating Instaloader object with SOCKS5 proxy:
pdef = 'socks5h://%s:%d' % (...)
proxies = { 'http': pdef, 'https': pdef }
L = Instaloader(proxies=proxies, user_agent='Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0')

Currently the changes affect only Instaloader and InstaloaderContext objects, not the CLI. The appropriate options should be added.
The documentation also was not updated.

would it not be sufficient to always set session.proxies = self._proxies and omit the if-clause?
Yes, thanks for noticing this useless statement. It needs to be removed.

When setting the proxy inside get_anonymous_session(), load_session_from_file() and login(), as far as I can tell, all relevant requests inside InstaloaderContext that are issued got enhanced with the proxy setting. Does this not make it redundant to additionally specify the proxy as an argument when using session.get() and session.post()?

I tried omitting this argument but the requests were still sent directly despite that the session was initialized with proxy. I don't know, maybe it works with the current version of requests library but this argument was necessary at the time when I was writing this patch.

would it not be sufficient to always set session.proxies = self._proxies and omit the if-clause?

I looked at the code again and now I think this if clause is needed because otherwise proxies may not be picked from the environment variables by requests library. So I would leave the code as it is.

I tried omitting this argument but the requests were still sent directly despite that the session was initialized with proxy.

If altering session.proxies does not have any effect, why did you introduce code that does so? But according to the python-requests documentation session.proxies.update(proxies) does configure proxies for the entire session.
Using the proxies argument with request methods like get() and post() is described as an alternative way of configuring proxies which can be useful if only individual requests need to be modified. Having both methods in our code is redundant and unpleasant.

I looked at the code again and now I think this if clause is needed because otherwise proxies may not be picked from the environment variables by requests library. So I would leave the code as it is.

Ah, you are right. The documentation indeed states that Requests only defaults to the proxy configuration defined by standard environment variables if none of the above mentioned ways of altering the configuration is used.

@zabalkansky Are you still interested to work on this PR?


How to set the page size? It looks like the page is out of shape.

How to set the page size? It looks like the page is out of shape.

Closed due to inactivity. Feel free to reopen it if needed.


fix typo error in anchor_head.py

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
https://github.com/open-mmlab/mmdetection/issues/5551
There is a typo error in anchor_head.py. It causes error when use AnchorHead with default init_cfg.
Modification
Fix that typo.

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


Update the fhir-works module to enable CORS requests

I reviewed it and have no comments so far. I am getting familiar with this repository.


Consider using a consolidated/shared proto implementation

Must support field presence (proto3 feature)

Possible packages for consideration

https://github.com/open-telemetry/opentelemetry-proto/blob/main/Makefile
https://github.com/protobufjs/protobuf.js/blob/master/cli/README.md#pbts-for-typescript
https://github.com/stephenh/ts-proto

Ideally there will be a package like @opentelemetry/proto which handles all proto serialization tasks for the protobuf and grpc exporters.

Closing as the package otlp-transformer has been landed.


feat(auth-api, auth-portal): Show the owner of the workspace when you are an editor

Also, show when you were invited to a workspace. Any existing invitations will be set to the date we run this migration as we don’t have a backward set of data on this

bors merge


Added Lycée Marie Pila

@xotluv First stage of verification passed, official domain for Lycée Marie Pila is eleve.mariepila-carpentras.fr as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@xotluv Please provide us with:

the school official website URL
the school street address, including city and country
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

Thank you.

@xotluv You might miss my previous comment. Please react.

@xotluv I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


getInfo on multiple sliders on a single page

Not an actual code issue but unsure where else to ask this.
Documentation doesn't cover much about multiple sliders on a page.
Have followed the demo example and setup a script that can instantiate multiple carousels on a page when/if required. All working fine. However, design calls for a " 1/3 " type text between the prev/next buttons to show pagination of current slider. I can't seem to figure out how to get the event info from these individual sliders without knowing the specific slider ID.
When I try and do a:
document.querySelector('button[data-controls="next"]).onclick = function () {
    for(var i in options){
        let info = sliders[i].getInfo();
        console.log(info);
    }
}

I obviously get an issue with sliders being undefined. If i try and define it with sliders[i]=tns(options[i]); (as per the demo page) it reinstantiates the sliders. Not sure how to specifically target the slider I'm on to get the relevant info. Any guidance would be much appreciated.

I got it. I added a
sliders[i].events.on('transitionEnd', updatePages);

Event and function and I have the data now. Sorry, should have read the documentation more closely. Thanks so much for a superb tool.


NURBS dof functions [nurbs-helper-dev]

This PR:

Moves the function NURBSExtension::DofMap const to public such that it can also be used outside the class. This is needed if a user has to account for periodic boundaries outside of the class. There are for instance some post processing applications of this.
Introduces NURBSExtension::GetActiveDof const such that a user can find the local dof number. There are some post processing applications for this.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#4126
@JacobLotz
@tzanio
@dylan-copeland + @tzanio
2/10/24
⌛due 2/24/24
⌛due 3/2/24

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

@IdoAkkerman, can you take a quick look?

Merged in next for testing...


Add emitter for new files that returns name and data

Is your feature request related to a problem? Please describe.
My test case is transcoding a webstream in the browser. To do this I need to be immediately notified when a new file chunk has been transcoded with the file name and data.
Describe the solution you'd like
I would like to have an event emitter I could listen to. Perhaps 'newFile'.
(async () => {
   await ffmpeg.load();
   ffmpeg.run('-i http://livestream.com/stream.ts -f segment -segment_time 1 stream_%06d.ts');
   ffmpeg.on('newFile', (ob) => {
      console.log(ob.name);
      console.log(ob.data);
   });
});

In fact, you can just use ffmpeg.FS in your existing emitter like:
rec.ondataavailable = async (evt) => {
  ffmpeg.FS('writeFile', evt.name, evt.data); // just an example, not sure if there is a name in evt
  await ffmpeg.run('-i', evt.name, 'video.mp4');
}

What is ".FS"? I don't see any documentation on that.

You can check documents here: https://github.com/ffmpegwasm/ffmpeg.wasm/blob/master/docs/api.md#ffmpeg-fs


After reopening an old project and engaging in multiple rounds of conversation, subsequent code modifications are lost the next time the project is opened.

Describe the bug
First thanks the great job!
Recently, I tried to create a project. After several attempts, I often found that previously resolved design issues reappeared. Upon careful inspection, I discovered that the code was missing. It has been confirmed that this is not due to the code being overwritten during the AI generation process. Projects with resolved issues are incorrect the next time they are opened.
Link to the Bolt URL that caused the error
http://localhost:5173/chat/project-name
Steps to reproduce

Open an old project: select and open a previously created project from the project list.
Engage in multiple rounds of conversation: Within the project, engage in multiple rounds of conversation, during which I may make several code modifications and updates.
Save and close the project: After completing the conversation and code modifications, I close the browser.
Reopen the project: The next time I open the same project, I find that the previous code modifications have not been saved, or some modifications are missing.

Expected behavior
Hope when the next time the project is opened, the code shoud fully retain the final modifications from the last session.
Screen Recording / Screenshot
No response
Platform

OS: [Windows]
Browser: [Chrome,]
Using anthropic/claude-3-5-haiku-20241022

Additional context
No response

this is an annoying problem, its making me run a fresh project on each test

this is an annoying problem, its making me run a fresh project on each test

Same for me, this should be a HIGH PRIORITY since persisting the codebase between conversations saves lots of tokens.
This might not be an issue if you have lots of time and money :)

actually it doesn't require token to restore the project as all the messages are cached in browser its just running the existing messages and re creating the project from cache.
but the issue here is its not able to recreate as its not processing the messages in sequence but in parallel which is causing the issue..
if the actions doesn't get executed in the same order as it happened originally, the recreated project gets corrupted

actually it doesn't require token to restore the project as all the messages are cached in browser its just running the existing messages and re creating the project from cache.

Technically it doesn't require tokens to restore the project (because of cache) but in practice, an older version of the project is loaded and you need additional tokens to get to the same functionality that you left when closing the browser (that you have in cache but is not loaded).

but the issue here is its not able to recreate as its not processing the messages in sequence but in parallel which is causing the issue..

Is there a way to not load all the messages? This issue is not present in the bolt.new project, so there must be a fix for this.

if the actions doesn't get executed in the same order as it happened originally, the recreated project gets corrupted

the bolt actually saved the code to the cloud periodically or maybe after each AI response.. and when you open that chat again it loads from the cloud


Req as a HTTP client

Using Req as a HTTP client (instead of HTTPoison)
Req configured with retries. It solves the issue with random errors when sending traces: {:error, %HTTPoison.Error{reason: :closed, id: nil}}
Removed injecting HTTP client to ApiServer through opts.
Req client is wrapped in a mockable module (using mox).
If needed, HTTP client implementation can be replaced through Config.

@JerzyDziala Good idea. Done ✅


Building bear inside install_bootstrap stage

Bear is now built inside the install_bootstrap stage every time
tuscan_build is run. This will allow custom versions of bear to be built
on every run, and also ensures that bear is correctly linked to the
libraries installed on the base container.

This'll have to be updated once you land #98, but that should be pretty straightforward.


feat(datepicker): add closeOnSelect property

adding new behaviour to cover more use cases
Prevent close datepicker when clicking on a date #15295

I signed it

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

I signed it

We are planning to add an option to enable 'confirm'/'cancel' buttons in the footer instead that will be used to commit the selection and close the datepicker


Migrate from PlanetScale to Neon

Unfortunately with the removal of the Hobby plan, PlanetScale no longer fits the philosophy of next-forge.
Thinking of swapping to Neon unless there's a preferred alternative.

May also consider Supabase as a Clerk, PlanetScale, Vercel Blob and Liveblocks replacement + unlocks Prisma Pulse (Postgres)

Exploring supabase, keeping track of missing basic features:

[ ] Ability to sign up a user with a OTP
[ ] Ability to check if a user exists by their email
[ ] Ability to generate an OTP for user signup
[ ] Ability to use a custom email for signup i.e. react.email (partially, but missing the two things above)


Unable to set UIImage of UITableViewCell

I am trying to use your library to set the image of a UITableViewCell (basic style).
I am using the following method to do so: cell.imageView?.setImageWithString(user.displayName, color: UIColor(hex: MVColor.Primary.Normal))
Unfortunately the image is not set and I am getting the following error:
<Error>: CGContextRestoreGState: invalid context 0x0. This is a serious error. This application, or a library it uses, is using an invalid context  and is thereby contributing to an overall degradation of system stability and reliability. This notice is a courtesy: please fix this problem. It will become a fatal error in an upcoming update.
I tried debugging the error. By using this method I found the cause of this problem. The error is produced by this call: CGContextTranslateCTM(context, -self.bounds.origin.x, -self.bounds.origin.y); (line 121 in your latest CocoaPods release) in your - (UIImage *)imageSnapshotFromView:(UIView *)inputView function.
It would be great to resolve this problem or find a workaround!
Thanks

Hey @steilerDev, thanks for pointing this out. Try pulling down the latest cocoapod release, and let me know if that fixes things.

Hey @bachonk, thanks for getting back that fast. I can see that you released a new version on Github, but CocoaPods is not updating (when running pod update). Is it a problem on your side or on CocoaPods side (Never looked how they actually detect new versions)?

Forgot to push up the latest to cocoapods, thanks for pointing that out. Try now

Pod update worked, unfortunately the error persists :/

I am not sure, but by looking at the error and your code, I think the problem is that the size of the image view is not set until you are setting an actual image into the view. Your framework uses the size of the context to create the image, which is not possible (or lead to that error) because the context size is 0x0 before setting the image.
Not sure if this is a fix but having a function that would explicitly draw inside a rect and return/set the image. Something like imageFromText:inRect: might help. Does that make sense?

You must set frame for cell uimageview.
[cell.uiimageview setframe:cgrectmake(0,0,weight, height);

See here
Issue 20


Competition Agent Zoo integration

Added competition agent to zoo/policies. Can be tested by using following code.
import gym
from smarts.zoo import registry

test_agent = registry.make_agent("zoo.policies:competition_agent-v0")
test_agent_spec = registry.make("zoo.policies:competition_agent-v0")

shared_configs = dict(
    action_space="TargetPose",
    img_meters=50,
    img_pixels=112,
    headless=True,
    sumo_headless=True,
)

test_env_path = "smarts.env:multi-scenario-v0"
test_senario = "1_to_2lane_left_turn_c"
test_env = gym.make(test_env_path,scenario = test_senario,**shared_configs)
test_env = test_agent_spec.env_adapter(test_env)

for _ in range(10):
    observations = test_env.reset()
    actions = test_agent.act(observations)
    print(actions)
    observations, rewards, dones, infos = test_env.step(actions)

test_env.close()

Please also add an entry to the CHANGELOG.md and a follow-up issue to connect this utility to the competition agents.


Issues with the ThrottleStop manifest

Currently, ThrottleStop fails to install because the URL in the manifest is not correct. I believe there are several problems with the manifest that I will attempt to outline below:
(I'd like to note that I don't intend to slight anyone who has worked on it)

The current URL uses HTTP when it's possible to use HTTPS.
The manifest currently installs beta versions with no indication that this is the case.
The download is available from regional mirrors, which is reflected in the subdomain of the URL (nl2, de1 etc.), and the number suffixes appear to change regularly.
The URLs are not available on the page, rather one is retrieved when clicking on the button for a region.
The URL now appears to require some kind of randomized string (perhaps an authentication token).
Perhaps most importantly - the current host, TechPowerUp, requests that users refrain from hotlinking to their downloads. You can verify this by going to https://nl2-dl.techpowerup.com/files/34qergaerg/1630442183/ThrottleStop_9.4.2.zip.

At a minimum, we should probably change hosts, though I believe TechPowerUp is the original source of ThrottleStop, so there is perhaps some risk involved when going to a 3rd party host.
I'm also of the opinion that the manifest should not install beta versions, though that opinion isn't a particularly strong one. I have some ideas about how to change the checkver string to achieve this but I'd like to see if any kind of consensus forms before I commit to something.
If we are unable to find a new host to download from, we should probably deprecate the manifest, as I don't see an easy way around the numbered mirror subdomains and authentication token requirement, not to mention the request to not hotlink.

https://github.com/lukesampson/scoop-extras/issues/6700#issuecomment-906515741

@ItzLevvie Thank you for informing me about all of this!
An immediate temporary workaround I can see would be to change the UA to winget/1.0. Perhaps we could also change the mirror region to a US one, as they appear to outnumber the other regions, so we can reasonably expect a subdomain like us2-dl to be available most of the time.
I'm not sure if we'd be allowed to use a winget UA though.


New record notification

The level now always shows the best time under the current time, both in-level and on the game over screen.
When you get a new record on a level, the best time will be replaced by the text "NEW RECORD!", which will pulse twice.
Afterwards, on the game over screen, the text "NEW RECORD!" will replace the best time and pulse indefinitely.
(Also, my editor automatically removes trailing whitespace, so that will show up in the diffs.)

Looks great! I'll try it out!

Cool!

I'm using Emacs with (add-hook 'before-save-hook 'delete-trailing-whitespace) in my config file

ah ok. I'm using eclipse (though 98% of this program was originally written in notepad++). I switched from notepad++ to eclipse because I wanted better syntax highlighting and I could automate builds a little bit better.
But emacs is cool!


Didn't received notification for Multiple project creation.

Describe the bug
Created job for multiple project creation. Job has been processed and projects where created but didn't received notification for that in app.

Need to test it after Automation for Notification gets released.


Laravel 8.x support

Description

Laravel 8.x is now released, should add support to allow installation on Laravel 8.x projects.
Describe the solution you'd like

Describe alternatives you've considered

Additional context

The next release will support Laravel 8 and should be released today or tomorrow (https://github.com/bugsnag/bugsnag-laravel/pull/409)


Remove Patreon from FUNDING list

Patreon should not be available as a funding option anymore as they do not offer a free subscription to use the platform.

Patreon page relaunched


Examples?

There is no example folder for examples on how to use the API

I'll keep this issue open for a while until I have added some examples visualized with macroquad, and with some screenshots to explain the API a bit better.

Examples are now available since version 0.2.0 https://github.com/tirithen/clipper2/tree/main/examples


Driver Drowsiness Detection

Project Request

Field
Description

About
This project aims to build a safety technology for vehicles on-road that will detect if the driver’s eyes are closed for a few seconds and will alert the driver when drowsiness is detected to avoid any accidents.

Github
transponster27

Email
<EMAIL_ADDRESS>

Label
Python, OpenCV, Imutils, Scipy, Pygame , Dlib

 [https://github.com/transponster27]

Define You

[ ] GSSOC Participant
Contributor

Project Name
 Driver Drowsiness Detection
Description
 In this project, I'll be making a Driver Drowsiness Detection System built using Python, Open CV, AND Dlib.
Since countless people drive on the highway day and night. Taxi drivers, bus drivers, truck drivers, and people traveling long-distance who suffer from lack of sleep.
Due to this, it becomes very dangerous to drive resulting in the majority of accidents happening due to the drowsiness of the driver.
So, to prevent these accidents I will build a system that will alert the driver whenever they feel sleepy.
This project aims to build a safety technology that will detect if the driver’s eyes are closed for a few seconds and will alert the driver when drowsiness is detected in order to minimize the impact and number of road accidents.
Scope
The project focuses on warning the drivers of any vehicle at any time of the day/night in case of drowsiness while driving. It can majorly help prevent accidents and make the driver retrieve consciousness to focus on the path properly. The requirement for this project is a web cam through which we will capture images of the vehicles along with the drivers.
Timeline
15-06-2023 to 15-07-2023 (max)
(I'll try to wrap up the project at the earliest possible date.)
Video Links or Support Links
I'll update you on the videos and support links I'll be using as a reference once I get the project assigned to me.
Thank you!

Please assign this project to me and allow me to contribute my hard work to GSSoC'23.

Hey, I am GSSOC'23 contributor and would like to contribute to this issue. Please assign this issue to me!! and this project is already done by me as my school project
so i can easily do this project with the necessary changes

Hello, my name is Ishanya. I wish to contribute to this project, kindly assign me the project


Fix: save user settings on server, audio buffer empty crash

Fixes issue #149, #157
Changes:

load user settings on login
save settings on the server
fixed audio buffer crash when hot word recognition started on load

please review @dynamitechetan @chiragw15 @isuruAb @mayank408 @amitiwary999 @betterclever


Siri (italian) wrong answer when turn on the switch

Hi, a few days ago, I finally installed and configured the homebridge platform.
After the first check, I proceed to install the "homebridge-cmdswitch2" with success...
Success, yes, but when I ask at Siri to turn on the switch named "luci garage" (garage lights in english) the answer is:
OK, le luci garage è masculine
Instead of: OK, le luci garage è acceso
I have tried to turn off the switch with Siri and the answer is correct (OK, le luci garage è spento), and finally I tried to change the Siri language to English to make other test, and the answer on toogle switch is correct!
Have you got any idea how to solve it?
I' m attaching some screenshots to demonstrate the issue.
Thanks
In italian (the first image is the wrong one)

In English

Looks like Siri Italian cousin doesn't understand correct Italian?

it's the idea.
the command is well pronounced (pronounced the same in English), but when you turn on / turn / open etc. responds with a word that might seem (risking a literal translation):
ok, the light is STRONG
within the program, there are special settings that impact Siri answers?
Thanks

Not really, those response are generated by Apple from server side. You can probably contact Apple Support and report the issue.
Sent from my iPhone

On Mar 28, 2017, at 1:34 AM, zonasoluzioni<EMAIL_ADDRESS>wrote:
it's the idea.
the command is well pronounced (pronounced the same in English), but when you turn on / turn / open etc. responds with a word that might seem (risking a literal translation):
ok, the light is STRONG
within the program, there are special settings that impact Siri answers?
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

me had the same answer a couple of days ago too and was not  thinking was an issue but just Siri trying to be smart/cool with some sentences.

Same issue, something went wrong when translating this sentence. :)

Buongiorno Zonasoluzioni, ti contatto riguardo il problema con Siri e la sua risposta "masculine" alla richiesta di attivazione degli switch in homekit. Condivido anche il tuo pensiero riguardo la mancanza di un feedback sul reale stato dei relé. Mi chiedevo se tu avessi risolto anche solo uno di questi problemi, proprio adesso sto per fare un hard reset dell'iPhone perchè non so più dove sbattere la testa, dal momento che ha funzionato correttamente per una settimana prima di iniziare a dare i numeri. Grazie!


SVGImage issue on CrossPlatform Avalonia application using 11.0.0-preview4

Receive the following error when referencing an SVGImage in a source for an image.
System.IO.FileNotFoundException: 'Could not load file or assembly 'Avalonia.Visuals, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=c8d484a7012f9a8b'. The system cannot find the file specified.'
I ported over my UI from my Avalonia desktop project that was utilizing 0.10.19 and everything worked great.  After porting over the axaml code into the new project and all converted just fine but the SVGImage tags.
To Reproduce
Steps to reproduce the behavior:
Create a crossplatform application in visual studio using the MVVM Avalonia template.
Add the Avalonia.svg.skia nuget
Add the following tag to the ui and try to run the application
<Image Source="{SvgImage /Assets/Minimal-Computer-Screen-Monitor.svg}"/>
I received the error that I mentioned above.
I expected the this tag to work correctly in the new Crossplatform application as it did in the Avalonia Desktop application.

OS: Windows 11
Version 11.0.0-preview4

You are using dependency built for 0.10 version of Avalonia. In order to use it with 11.0, please check if newer version of this dependency supports Avalonia 11.0.  Possibly there is a preview version of that dependency as well.


Running VM snapshot on dir pool copies config.mount incorrectly

Snapshotting running VM on dir storage pool means causes the snapshot to be unusable due to copying the config.mount directory, thus preventing starting of the VM when restored/copied to a new instance.

@tomponline as you mentioned elsewhere, moving the mount point to the devices directory should avoid this issue.

@stgraber excellent will do thanks.


MS-Windows: external commands cannot be executed if &shell contains a space

&shell is incorrect escaped in init
On Windows, Use double-quoting instead escape spaces with backslash.
Ex. Using Git bash installed in path that contains a space.
in bash.exe:
$ cmd.exe /c "echo %SHELL%"
C:\Program Files\Git\usr\bin\bash.exe
$ /path/to/ms-win-vim/gvim.exe -u NONE -U NONE

in gvim.exe:
:echo &shell
C:\Program\ Files\Git\usr\bin\bash.exe
          ^ Incorrect backslash here

Enclose the command in parentheses, when _wsystem()
If &shell is double-quoted, _wsystem() call will fail.
:!echo ok is converted to "C:\Program Files\Git\usr\bin\bash.exe" -c "echo ok" and execute,
but cmd.exe (called internally by _wsystem()) deletes double quotes at first and last,
resulting C:\Program Files\Git\usr\bin\bash.exe" -c "echo ok and fails.
:!echo ok
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

To resolve, enclose the command in parentheses,
like ("C:\Program Files\Git\usr\bin\bash.exe" -c "echo ok").

Sorry, this PR is buggy.
It's brokes system(). 😢

Codecov Report

Merging #4920 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4920      +/-   ##
==========================================
- Coverage   81.47%   81.46%   -0.01%
==========================================
  Files         126      126
  Lines      146220   146220
==========================================
- Hits       119130   119119      -11
- Misses      27090    27101      +11

Impacted Files
Coverage Δ

src/option.c
82.59% <ø> (ø)
:arrow_up:

src/gui_beval.c
62.5% <0%> (-0.87%)
:arrow_down:

src/viminfo.c
75.13% <0%> (-0.53%)
:arrow_down:

src/window.c
87.8% <0%> (-0.11%)
:arrow_down:

src/channel.c
84.14% <0%> (-0.08%)
:arrow_down:

src/gui.c
63.39% <0%> (-0.06%)
:arrow_down:

src/term.c
79.27% <0%> (+0.15%)
:arrow_up:

src/profiler.c
94.67% <0%> (+0.56%)
:arrow_up:

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 0eddca4...56dc4f2. Read the comment docs.

Does this work even without vimrun.exe?

Also note that vim.exe and gvim.exe handle the command line differently.

I confirmed that this PR works with or without vimrun.exe and with cmd.exe or C:\Program Files\Git\bin\bash.exe. Also confirmed with gvim.exe and vim.exe.
I think this is ready to be merged.


Improve documents highlighting

The current engine doesn't highlight the query words found in the documents, this is dur to the fact that it doesn't even know where in terms of bytes a query words were extracted from the documents.
In the previous engine we were keeping the positions of the words in terms of bytes offset and length and it appears to be one big source of problem when it came to highlighting the document, many out of bounds, etc. This was also a big parts of what was stored on disk, maybe 30% of the database size on disk.
So, I thought about why not getting rid of this raw information? Using the query words the user inputed to reconstruct an higlighted document, by using the stored document.
We can highlight a document by extracting its content, using the tokenizer to find the words it contains and highlighting those matching. It could be a little bit harder when it come to highlight multi word synonyms but maybe we could find a solution later.

Some update
The search engine now highlights only the query.
Ex: a document with cheval and a query che will highlight this way cheval.
However, we still have the following issue: the highlighted words are not necessarily the words that made the document matches the query.
Example: a dataset containing a document with "description": "Blabla news... blabla ... good news". If the user types "good news", the document matches the query thanks to good news, not news at the beginning of the file. Despite that, the search engine will highlight news and good news. This can be problematic during the crop: the search engine indeed crops around the first matched word, here news and not good news, which are the "real" words to highlight


pdbqt format with structure_utils building blocks

It would be nice if the building blocks using the structure_checking inside could accept pdbqt format. For example, extract_models could then be used directly with pdbqt files coming from autodock_vina.

done


Fix router template of scaffold generator for models with name compose of more than 1 word

One example:
rails g scaffold TestCase name:string content:string
rake db:migrate
rails g backbone:scaffold TestCase name:string content:string

the router gets generated would be like:
class AppName.Routers.TestCasesRouter extends Backbone.Router
initialize: (options) ->
@testCases = new AppName.Collections.TestCasesCollection()
@testCases.reset options.testCases
...
newTestCase: ->
@view = new AppName.Views.TestCases.NewView(collection: @test_case)
...
index: ->
@view = new AppName.Views.TestCases.IndexView(test_case: @test_case)

While it should stick to camel name convention for js code, use testCase instead of test_case. And there're some other part of the code is using something like options.testCases but here you passed in test_case hence the problem like 'bind' is not a function on 'undefined' would happen.

I faced the same issue with multiple word model names as well. The fix mentioned here seems to work. Might be a good idea to merge this in?

+1 for merging this


ci updates (Ubuntu 20.04 x64, prep for c++20)

This brings us clang 10 and its understanding of C++20 as a standard (rather
than it being called c++2a in earlier versions).
If people are happy with this, I can rebuild the snmallocciteam image and push.

I've backed up the previous snmallocciteam/build_linux_x64:latest as snmallocciteam/build_linux_x64:ubuntu18.04 and have just built locally and pushed a new image to the name snmallocciteam/build_linux_x64:latest.  In so doing I fixed a typo in the ci/README.md and have an excuse to push to this branch again.  Let's make sure I haven't broken the CI images...


Trying to upsert with exists: false throws UniqueError on updates

Describe the bug
Trying to upsert within unique: true attributes is causing UniqueError on updates.
👇  works on create
const branding = await this.Branding.update(params, { exists: false });

fails on update 👇

To Reproduce
Sample model:

Call await this.Branding.update(params, { exists: false }); twice, first works, second fails.

Can you please create a debug.ts that replicates this. Then we can fix quickly.

@mobsense sure!
First upsert work, then I try to update again, changing a random attribute, and it fails.
import DynamoDB, { DocumentClient } from 'aws-sdk/clients/dynamodb';
import { Entity, Table } from 'dynamodb-onetable';

const Schema = {
  format: 'onetable:1.1.0',
  version: '0.0.1',
  indexes: {
    primary: { hash: 'pk', sort: 'sk' },
  },
  models: {
    Test: {
      pk: { type: String, value: '${id}' },
      sk: { type: String, value: 'test' },
      id: { type: String, required: true },
      name: { type: String, unique: true },
      random: { type: String },
    },
  } as const,
  params: {
    isoDates: true,
    timestamps: true,
  },
};

type TestType = Entity<typeof Schema.models.Test>;

const getTable = (tableName: string, client: DocumentClient) => {
  return new Table({
    client: client,
    name: tableName,
    schema: Schema,
  });
};

void (async () => {
  console.log('starting');
  const client = new DynamoDB.DocumentClient({ region: 'us-east-1' });
  const tableName = 'debug-table';
  const Test = getTable(tableName, client).getModel<TestType>('Test');

  const resultCreate = await Test.update(
    { name: 'testx', id: '4', random: String(Math.random()) },
    { exists: false, return: 'get' },
  );
  console.log({ resultCreate });

  const resultUpdate = await Test.update(
    { name: 'testx', id: '4', random: String(Math.random()) },
    { exists: false, return: 'get' },
  ); // <==== This will fail: TransactionCanceledException: Transaction cancelled, please refer cancellation reasons for specific reasons [ConditionalCheckFailed]
  console.log({ resultUpdate });
  console.log('done');
})();

output
tarting
{
  resultCreate: {
    id: '4',
    name: 'testx',
    random: '0.9448450278360672',
    updated: 2022-04-28T22:01:59.188Z
  }
}
TransactionCanceledException
TransactionCanceledException: Transaction cancelled, please refer cancellation reasons for specific reasons [ConditionalCheckFailed]

As a workaround, what I'm currently doing for simulating upsert is:
function upsert(...) {
  try {
   Test.update({ ... })
  } catch (e) {
    if (e instanceof OneTableError && e.code is `NotFoundError`) {
      Test.create({ ... })
    } else {
      throw e
    }
  }
}

You are using {exists: false} in the first and 2nd update. The first works because the item does not exist. The second fails because the item exists.
What were you expecting to happen?

I wanted a true upsert. Test.update(...) to create or update. Similarly to putItem that creates or replaces. Is this possible with OneTable or should I stick with this implementation https://github.com/sensedeep/dynamodb-onetable/issues/323#issuecomment-1112719960

Yes, just use exists: null on update.
See: https://doc.onetable.io/api/model/methods/#update
In update, the params.exists will default to a true value to ensure the item exists. If set to null, an update will be permitted to create an item if it does not already exist. This implements an "upsert" operation.

@mobsense thank you, but I believe that's the bug, it is not, you can test this example here. It is set to false, which should work as null and it does not work because of the unique attribute.

False does not mean the same as null.
False means the item must not exist. Null means we don't create if it exists or not. If not, it is created. If so, it is updated.
True means the item must exist.


Gallery Lightbox

How can I get the images to open in a lightbox (Like the Divi Gallery module) when using gallery upload. I have tried to replicate all classes from the Divi Gallery to achieve this but without success. Is it possible?

Hi @snewsh Divi uses magnificPopup (https://dimsemenov.com/plugins/magnific-popup/documentation.html) so you can use it in your own code too.

Hi @snewsh Divi uses magnificPopup (https://dimsemenov.com/plugins/magnific-popup/documentation.html) so you can use it in your own code too.

Thanks, I'll take a look.

Thanks, I'll take a look.


DeprecatedWarning: Call to deprecated property body

I get the following warning, any idea?
.local/lib/python3.7/site-packages/gunicorn/workers/sync.py:179: DeprecatedWarning: Call to deprecated property body. Please use text instead.
respiter = self.wsgi(environ, resp.start_response)
using gunicorn  20.1.0 and falcon  3.0.0

Hi @wilwet !
Yes, it is basically as the deprecation warning reads :slightly_smiling_face:

Call to deprecated property body. Please use text instead.

To elaborate, in Falcon 3.0, resp.body was renamed to resp.text.
So if you had your responder along the lines of,
def on_get(self, req, resp):
    # Simply rename resp.body to resp.text:
    # resp.body = 'Hello, World!\n'
    resp.text = 'Hello, World!\n'

    # ...

You may also want to check this brief overview: When would I use media, data, and stream?
Hope this sheds some light on the subject, or did you have something else in mind?

Thank you for your swift response and your great support! This fixes the warnings.

Awesome sauce, closing this then.
Happy tinkering!


Fix/download window

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other

PR description
修复下载管理器窗口无法二次打开问题。

Issue Number: #15

Fixed #15


Rebuild the Win32 Parser (VC2012) and remove unnecessary cygwin binaries

Also update json-c to newest revision and add build instructions.
Should address #824

@ping ovr

Thanks

+1 will give it a go tonight :-)

Yeah but the WINDOWS.md assumes that you use the already built parser.
(because building the parser is annoying)
The section about building the parser is just for information,
if you want to do it yourself.

Ah, I get it. Still learning the ropes here, think I've been a bit spoilt in the past with symfony holding your hand every step of the way (at the expense of speed). Just bought "head first : C" so hopefully I'll get a bit more adept and actually contribute rather than leeching :-)

Yeah I admit that it's not very intuitive,
but I just added the instructions there quickly,
that if somebody wanted to build it, he could, even though he wouldn't need to.
It should be definitely marked as optional with explanation,
that you could also just use the .exe from the repository :)


Create have_disabled_field matcher

Hi,
What do you think about creating a have_disabled_field matcher?
I often create it in my applications and maybe it fits on capybara by default since it's pretty common.
An example of usage:
fill_in 'Value', with: '100.00'
fill_in 'Discount', with: '10.00%'

expect(page).to have_disabled_field 'Total', with: '90.00'

The total field must not be editable and must have the value 90.00 in this example.
I have this one:
module Application
  module Matchers
    extend RSpec::Matchers::DSL

    matcher :have_disabled_field do |name, options|
      match do |page|
        selector = XPath.descendant(:input)[XPath.attr(:id).equals(XPath.anywhere(:label)[XPath.string.n.contains(name)].attr(:for))]

        field = page.find(:xpath, selector)

        expect(field[:disabled]).to eq 'disabled'

        if options && options.key?(:with)
          expect(field[:value]).to eq options[:with]
        end
      end

      failure_message_for_should do |page|
        "expected page to have disabled field #{name.inspect}"
      end

      failure_message_for_should_not do |page|
        "expected page not to have disabled field #{name.inspect}"
      end
    end
  end
end

RSpec.configure do |config|
  config.include Application::Matchers, :type => :feature
end

It is not strictly and the error message is useless but it's just an idea.
I would be happy to work in a pull request to add it but I'm not sure where to put it (capybara or XPath::HTML.disabled_field).
An second implementation would be an option on have_field:
fill_in 'Value', with: '100.00'
fill_in 'Discount', with: '10.00%'

expect(page).to have_field 'Total', disabled: true, with: '90.00'

I prefer the latter but it requires more effort since XPath::HTML.field ignores disabled elements.

I am late to this party but thanks for this feature


fgbio passing multiple options

Hello,
I am trying to pass multiple options, but passing only one (options: [--min-reads, 2]) does work so far.
Could you give me an example of what format it should be?
I thought this example would work, but didn't:
options: [--min-reads, 2, --max-reads, 500000]

I thought it didn't work, but later I find that the option I provided was correct and worked.

Thank you for following up!


C is not under Language Section in README.md

Cheat sheets for C is not present in README.md but the file could be accessed by going to here
I want C to be added in READ.md.

I though you ignored my Issue. Sorry :disappointed:

No I'm note :)


Dry run mode for Actions.sh

Trying to improve the testing framework, but also make it less intrusive for the source code. Inspired by the discussions in #14471.
One idea is to add a new parameter to Actions.sh which will be used in tests and when running fastlane --dry-run:
A. Existing code
# do not need to update existing code to keep previous behavior
Actions.sh('git rev-list HEAD')
# or explicitly
Actions.sh('git rev-list HEAD', dry_run: :return_commandline)

This will run the command in production, and return 'git rev-parse HEAD' in dry-run / tests, as it is now.
B. Dry-run supporting code with side effects
Actions.sh('rm -v .checkpoint', dry_run: "removed '.checkpoint'\n")

This command will not run in testing / dry-run mode, but Actions.sh will return removed '.checkpoint' instead of the command itself.
C. Dry-run supporting code without side effects / hermetic
Actions.sh('git rev-parse HEAD', dry_run: :no_side_effects)

This is most useful for tests. We run the command in production / tests / dry-run, but expect no side effects from it.

I'm interested in feedback from fastlane team, and I am happy to start implementing a PoC if you like the idea.

dry_run: :no_side_effects would enable us to set this for e.g. git commands where we are able to work with tmp repos that are safe to mess with, correct? That would improve some of our tests that exercise code that uses Actions.sh internally from just comparing the generated command, to actually running the command and looking at the result, right?

Thank you for these clarifying questions.  Correct for both: that is exactly what I had in mind.

One more way to support dry-run could be
# instead of
Actions.sh('rm -v .checkpoint', dry_run: "removed '.checkpoint'\n")
# pass a lambda
Actions.sh('rm -v .checkpoint', dry_run: do |cmd, stdin|
    ShellActionResult.new(status: 0, stdout: "removed '.checkpoint'\n", stderr: '')
end)

Ahh, I didn't manage to find an image for bumping this thread on time.  But that's alright; here, have Patrick Stewart.

Poop


isCollapsed missing function

Hi, could you please add isCollapsed function ?
Like isExpanded, isHidden, isAnchored...
best

You can already do getPanelState() to check if it's collapsed.


Bump to Dart SDK 1.21.0-dev.0.0.

Bump to latest Dart SDK dev build (1.21.0-dev.0.0).

updates to analyzer w/ support for bazel workspaces (cc @tvolkert)
removes deprecated analysis cacheSize variable access

/cc @Hixie @abarth


Release v2.0

I would like to release v2.0 around November 15.
(cc'ing @xspec/xspec, @xspec/maven-plugin, @xspec/oxygen-xml-editor-xspec-support, @vincentml)

TODOs
(based on Release Workflow)

Prepare the release

[x] Release 2.0.6 to Oxygen add-on channel (Stable Release Candidate) (#1282)

[x] Notify the XSpec discussion list of the upcoming v2.0 release.

Notable changes

Oxygen add-on changelog
CLI-specific changes (#1276 and anything else?)
Breaking changes (#1121)

[x] Test the add-on 2.0.6 with Oxygen 23

All the 4 transformation scenarios should work. (Don't forget to test Run XSpec Test with XSLT, XQuery and Schematron.)
DITA DTD should take effect via ${xmlCatalogFilesList} (#980).
Loading xspec.xpr should disable the add-on and enable its own framework.

[ ] Draft a new release (v2.0.7) at Releases page

[ ] Create a pull request incrementing the version (to 2.0.7 without -SNAPSHOT) of pom.xml and the Oxygen add-on and merge it into master

Release it

[ ] Make sure 2.0.7 has been deployed to Maven Central successfully (automated)
[ ] Publish the release at Releases page
Promote the release v2.0

[ ] XSpec discussion list
[ ] xml.com
[ ] xml mailing list
[ ] tweet

Update Wiki

[ ] Requirements - Saxon
[ ] Running with Maven - Fetching XSpec file set in Maven

Create a pull request for the Oxygen XSpec Helper View

[ ] https://github.com/xspec/xspec/issues/1121#issuecomment-690997853

Prepare the next development

[ ] Close the project and the milestone related to v2.0
[x] Create the project and the milestone for v2.1

Start the next development

[ ] Create a pull request incrementing the version (to 2.1-SNAPSHOT) of pom.xml and merge it into master

(If something critical is found, we will create a branch for 2.0.8-SNAPSHOT and work on it.)

When v2.0 is released, I'd also announced it in https://xspec.io. I can create an article for that based on the release notes and other announcements.

Thanks @cirulls
I had been deadly busy lately. I'll have some time from Saturday and will resume working on the release.
Now that Oxygen 23 is there, we'll need to check compatibility with it before releasing v2.0.

No worries @AirQuick, thank you time for the release, you have been doing an amazing job! I'll watch this issue, let me know in case I can be of any help for the release.

Draft a new release (v2.0.7) at Releases page

Done. The Summary section is written by hand. The rests are auto generated.
Feel free to suggest any improvements.

It looks really good!

I agree, it looks really good! Thank you for putting this together, @AirQuick . A couple of minor bits of feedback:

Consider providing a little context for the heading "Common", such as "Common to Languages Under Test" or "Common to XSLT, XQuery, and Schematron".
Is #1040 worth mentioning in the summary?

I hadn't noticed #1107 before, but if it's what I think it is, that's a very welcome enhancement and definitely a highlight. :)

Thanks @galtm

Consider providing a little context for the heading "Common", such as "Common to Languages Under Test" or "Common to XSLT, XQuery, and Schematron".

Renamed the section title "Common to Languages Under Test".

Is #1040 worth mentioning in the summary?

Added "Arrays and maps are reported in the same way as XSLT scenarios" to the XQuery section.

I hadn't noticed #1107 before, but if it's what I think it is, that's a very welcome enhancement and definitely a highlight. :)

#1107 corresponds to "You can write advanced expressions in @location" in the draft release note, but it looks somewhat vague. Added "(e.g. <x:expect-assert location="//sec[@id='lower']" />)" to it for clarification.

@cirulls
If everything looks fine so far, can you possibly own and perform these tasks?

[ ] Publish the release at Releases page
Promote the release v2.0

[ ] XSpec discussion list
[ ] xml.com
[ ] xml mailing list
[ ] tweet

Sure, I'll put aside some time during this weekend to perform these tasks.

Today I did the following:

[x] Publish the release at Releases page: I hit the release button on https://github.com/xspec/xspec/releases/tag/v2.0.7. I added v2.0.7 in the description (originally it was v2.0), I hope it's fine
Promote the release v2.0

[x] XSpec discussion list: see https://groups.google.com/g/xspec-users/c/wYf5XB12A5c
[x] xml.com: see https://www.xml.com/news/2020-11-xspec-v207/
[x] xml mailing list: see http://lists.xml.org/archives/xml-dev/202011/msg00010.html
[ ] tweet: I don't use Twitter but I know @cmarchand and @yamahito do and are very active on Twitter. Would you mind posting a tweet on the XSpec v2.0.7 release?

I also added a post on the xspec.io website, it's on https://xspec.io/posts/xspec_207_release  I added this new promotion step in the wiki.
@AirQuick: Let me know if I missed something or if there are other outstanding tasks I can help with.

Thank you @cirulls. They all look prefect!

I did a tweet from Markup UK (and shared it) - should get more exposure that way!

Tomos Hillman
eXpertML Ltd
+44 7793 242058
On 30 Nov 2020, 17:39 +0000, AirQuick<EMAIL_ADDRESS>wrote:

Thank you @cirulls. They all look prefect!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

At least one tweet has gone out. I ticked the boxes related to tweeting.
@AirQuick: do you think we can close this issue? Any outstanding task for the v2.0.7 release?

Thanks @yamahito !
Let's close this issue, @cirulls


Fix the vppbranch var to say v3.25.1 instead of master

The docs were moved to the dedicated docs repo and as such the vppbranch var that was updated in https://github.com/projectcalico/calico/blob/v3.25.1/calico/_config.yml seems to be failing to do its job. This fix will hopefully do the trick.
Product Version(s): v3.25.1

Issue:

Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

@ctauchen
12:45:15 PM: [WARN] LINK-CHECK found the following 1 dead link(s):
12:45:15 PM: https://techcommunity.microsoft.com/t5/networking-blog/direct-server-return-dsr-in-a-nutshell/ba-p/693710 is dead (503)
12:45:15 PM: ==>Origin: http://localhost:4242/calico-enterprise/3.14/getting-started/install-on-clusters/windows-calico/demo
12:45:15 PM: [ERROR] The crawler tests failed due to error / dead links

The link is not dead!

LGTM

@lwr20 How's this for you?


Improve Pytree type errors across conditional primitives

Hi all!
Often times, users run into bugs in my code. One bug which I dread attempting to debug deals with Pytree type mismatch across jax.lax.cond -- I end up with massive dumps of Pytree types and I have to manually parse and compare these dumps each time I try and fix these issues.
I believe we have the technology to make this more convenient. Is it possible to push the comparisons into the Pytrees? (So, at the very least, I don't have to manually do the diff -- but it is done for me in the structure)?

Something like this is definitely possible, and we already do have some code to improve the outputs of pytree equality checks that is used in lax.control_flow: https://github.com/google/jax/blob/f132527792e1397c6c2f59821862517cec098274/jax/_src/lax/control_flow/common.py#L200-L203
Can you give a short example of code that produces inconvenient output, and a suggestion for what output you'd prefer?


chore(queue): handle panic in worker

Signed-off-by: Bo-Yi Wu<EMAIL_ADDRESS>

Codecov Report

Merging #18 (d4ac5b6) into master (bbdc746) will increase coverage by 0.22%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
+ Coverage   84.56%   84.79%   +0.22%
==========================================
  Files           7        7
  Lines         337      342       +5
==========================================
+ Hits          285      290       +5
  Misses         38       38
  Partials       14       14

Impacted Files
Coverage Δ

simple/simple.go
95.89% <100.00%> (+0.30%)
:arrow_up:

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 bbdc746...d4ac5b6. Read the comment docs.


Fix error on empty array config

Fixes https://github.com/webpack/webpack/issues/1455

This seems to solve the problem described in https://github.com/webpack/webpack/issues/1455.
I tired writing a test for it under test/configCases/simple/empty-array-config by copying test/configCases/simple/empty-config and changing the content of webpack.config.js to module.exports = []; but something seems to be going wrong.
I thus have two questions..

Does this fix require a test?
If yes then what should I check for in it? Also some pointers to similar existing tests/asserts will help.

Thanks in advance. @sokra

cc: @bebraw

@ksonnad does this fix your issue?

Yep.

@sokra What needs to be done here?

Nothing, thanks


Add button to set numerical parameters

Each time you type something in the text box it automatically executes the function to set the parameter. To avoid inconveniences it would be better to have a button that executes this function to set all the parameters.
Apparently, this behavior happens with numerical parameters only (int and double). With string parameters, you have to press enter in the text box to set the parameter, which is fine.

This behavior was recently adjusted for string parameters in #18. It seems useful to have the same behavior for numbers as well.
ping @authaldo

Should be fixed in #27


can't connect internet by https.

android phone browser can work.
the app can't work.

Please use our bug report template in CONTRIBUTING.md.


Audit isize

These commits should fix the improper usage of isize throughout most of src/sdl. A few improper usages of usize that appeared around the isize instances are fixed as well. keyboard.rs needs to be looked at still, and the casting between i32 and c_int may not really be needed, but may be good for explicitness.

cc #283

Grand, cheers


Unskipping test_flash_attention.py breaks regular runs

The commit https://github.com/intel/intel-xpu-backend-for-triton/commit/e47fd9537aeb313cd048393ac50d71b25993ec56 enables several tests, this breaks conda basekit run.
See the log at
https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/9056251421/job/24878516034

Those test_flash_attention tests are enabled by 1e4fb6497c1e2c55b738a842d05f14ae995e07c9 and not e47fd9537aeb313cd048393ac50d71b25993ec56.
@leshikus Are you sure the failures are caused by e47fd9537aeb313cd048393ac50d71b25993ec56?

Whitney, probably you are correct. Both commits happen at the same day, I've just start noticing failures

@whitneywhtsang thank you for the help with the owner

@leshikus they pass without using the conda env. so can you explain what is the difference the conda env. introduces ?

@etiotto the conda env means the different environment, namely, different libraries and different library paths; in some cases when a compiler is called and the problems can happen due to different header resolution, but this particular problem looks more like a linking problem to me

@leshikus can we close this ticket?

test_flash_attention.py no longer exists, closing this issue.


Set Token mint

Using the mechanism we described today to validate sender of a mint request. Justin, you should be using this in burn.

Pull Request Test Coverage Report for Build 207

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 90.909%

Totals

Change from base Build 187:
0.09%

Covered Lines:
59

Relevant Lines:
65

💛  - Coveralls


Removed all hardcoded gufe keys from GufeTokenizable tests in test suite

We do not consider gufe keys to be stable across versions, though they should be stable in-process and generally across machines running the same software versions. We only rely on them being stable in-process, however.

Gracias @IAlibay! Merging!


Implement capability reflecting Taint support in RKE clusters

Prior to v2.3 CNI addons in Rancher clusters didn't have tolerations allowing them to be started on  tainted nodes. In v2.3 tolerations were added to the system addons templates, and should get applied on the very first rke reconcile for the cluster for every k8s version. The thing that is left to implement is an indication that the tolerations are applied, hence the taints are supported. We should:

Add TaintSupport capability (type *bool)
The value should be left as nil for the hosted k8s providers
The value should be set to true at the end of the very first rke reconcile (provisioner.go). Once set to true, the value will never be averted again.

Verified on an upgrade from 2.2.8 to master-head.
Cluster specs:
2 custom clusters - minimum - 1etcd, 1 control plane and 1 worker node
2 rke DO clusters -  minimum - 1etcd, 1 control plane and 1 worker node with individual node pools

Steps:

Have the cluster deployed in 2.2.8.
Upgrade rancher to master-head.
The clusters do not have taintSupport": true flag.

Scenarios verified:
On rancher upgrade -

In Edit custom cluster --> register page --> Add Taints is available

In Custom cluster --> Edit node --> No Taints available.

In rke cluster - Edit node does NOT have taints

In rke cluster - Edit cluster --> Node pool has taints

Edit node template -- has taints. Taints can be added.

Add a taint on the node template and scale up the worker node. taintSupport": true flag is seen set on the cluster after it comes up Active.

etcd and control plane nodes, do not show existing kubernetes taints -- logged issue --https://github.com/rancher/rancher/issues/22565

new cluster created in master-head has the taintSupport": true flag set and the nodes --> Edit node --> Have taints available, user can add taints.


Wrong Screenshot

Under Solution Detail Worksheet the screenshot is for the Document Details Worksheet not for Solution Details - 26/07/2018

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

ID: 621d3141-346d-0f15-c850-db51cfbc32b9
Version Independent ID: 00686abe-6714-7736-e3f1-06c4b317cdff
Content: Telemetry Dashboard worksheet reference
Content Source: DeployOffice/compat/telemetry-dashboard-worksheet-reference.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

Thanks for bringing this to our attention. The correct screenshot for "Solution details" is now appearing in the article.


Optimize Trivial Methods to avoid needing a frame

Currently, trivial methods are:

methods/blocks returning a literal
methods/blocks returning a global
methods/blocks returning value from a field
methods that set a field from an argument (setters)

This change is a pretty good win.
NBody (AST startup) sees a 37% reduction in run time, Richards (AST startup) 22%.
NBody (BC startup) sees a 32% reduction in run time, Richards (BC startup) 15%.
Bounce on BC+JIT sees a 48% reduction in run time, Towers (BC+JIT) 21%.
The SomSom benchmarks see 8-10% reduction for the AST interpreter, and 16-21% for the bytecode interpreter.
https://rebench.stefan-marr.de/compare/RPySOM/1bb77ce0b2e9bd1b0250a4e51c3d67f57b702d68/705ede66bf7dc8338cb5380c7be1b982a78d5491
Pretty good results. This reduces the gap to 22-27% on the SomSom benchmarks.

Pointer to related data on ZeroVM from the OpenJDK: https://bugs.openjdk.java.net/browse/JDK-8255066


Not working

The base.css import code returns 404. Looks like the GitHub pages were taken down.

All my themes got a structure change meaning the base.css file doesn't exist anymore.
All you have to do is just change the end of the url from base.css to dist/HorizontalServerList.css.
Example with Frosted Glass:

It works now thanks!


Dapr Sidecar loses connection to Azure Service Bus, both consuming and publishing messages fails

Expected Behavior
PubSub with Azure Service Bus should publish and consume infinitely.
Actual Behavior
After a while (a couple of hours today) neither publishing nor consuming messages works.
Notable log lines are
Too many failed attempts while publishing Service Bus message (nil): *Error{Condition: amqp:not-allowed, Description: A link to connection '72854951' $cbs node has already been opened., Info: map[]}

and
Error reading from topic publiccloudconnectorgwinbox. *Error{Condition: amqp:not-allowed, Description: A link to connection '72854951' $cbs node has already been opened., Info: map[]}

Here's the full log of the Dapr sidecar since the last restart of the pod.
publiccloudgateway-deployment-5376ce03-588df56647-g6p4h.log
Steps to Reproduce the Problem
Have a sidecar with Service Bus subscriptions and eventually the sidecar stops publishing and consuming the servicebus subscription.
We're using the AKS extension, which keeps Dapr up to date autometically, so we're on Dapr 1.10.2

Just trying to analyze the issue here.
Was this working before upgrade to Dapr 1.10.2 ?
This seems to have been reported and fixed here in Azure SDK: https://github.com/Azure/azure-sdk-for-go/issues/19347
It seems to have fixed with PRs like https://github.com/Azure/azure-sdk-for-go/pull/19326 and https://github.com/Azure/azure-sdk-for-go/pull/19492.
From all these, it seems that cbs connection is an exclusive link and we might need to close it, whenever-wherever required.
I am not sure, but just a theory/possibility:
While sending a message, it receives an error and goes in this loop:
https://github.com/dapr/components-contrib/blob/907b6b9ebeeba9c4f74f4df1ae3316eae3cb784e/internal/component/azure/servicebus/publisher.go#L62
Here, it does not go into NetworkError condition, as connection is already open.
It doesn't satisfy IsRetriableAmqpError as well, as Condition: amqp:not-allowed is not one of https://github.com/dapr/components-contrib/blob/907b6b9ebeeba9c4f74f4df1ae3316eae3cb784e/internal/component/azure/servicebus/errors.go#L11
Finally, it backoffs permanently and you keep receiving same error for all messages published.

Do we need to re-connect while backing off permanently, may be depending on some Conditions apart from NetworkError? So that further messages might be sent
As per Condition: amqp:not-allowed, is there any setting required by your side on ServiceBus to allow this? And, were same settings working earlier with Dapr 1.9.x?

I don't remember having seen this issue before 1.10.x. As far as I know we didn't change any settings recently, but we upgrade the Pulumi packages for our deployment.

We retain the AKS logs in Log Analytics for 30 days, so we've been able to do some research.
In fact, the error first occured 2/28 with Dapr version 1.10.0.

Kusto query
ContainerLog
| where TimeGenerated > ago(30d)
| where LogEntry has "node has already been opened"
| where LogEntry has "scope=dapr.contrib type=log"
| extend DaprVersion = substring(LogEntry,-6,6)
| project TimeGenerated,DaprVersion,LogEntry
| summarize count() by DaprVersion, length=bin(TimeGenerated, 1d)

Waiting for https://github.com/Azure/azure-sdk-for-go/pull/20334 to be released. We will include this in Dapr 1.10.3


bit: init at 1.05

Motivation for this change
Command-line tool for git
https://github.com/chriswalz/bit
Fixes #117286
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)
[x] 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.

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

1 package built:

bit


Fixes missing FQFN

This PR adds some FQFN within the @service macro. It also:

Upgrades to freestyle 0.4.4.
Releases a new patch release: 0.3.3.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #88   +/-   ##
=======================================
  Coverage   88.52%   88.52%
=======================================
  Files          12       12
  Lines         122      122
=======================================
  Hits          108      108
  Misses         14       14

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 c8ee4d5...04d2978. Read the comment docs.


Fix package metadata

@halter73 @Tratcher
FYI this is for release/RC2.

:shipit:

:shipit:

@halter73 will push this, thanks for the reviews!


luci-proto-wireguard: fix generated AllowedIPs

In the generated client configuration, the AllowedIPs option should contain the host IPs, instead of the client IPs.
Fix #5956
Signed-off-by: Julien Cassette<EMAIL_ADDRESS>

This fix looks wrong - simply stripping the network prefix and replacing it with /32 or /128 will not work in all cases, e.g. when the CIDR address was a network and not a host address. Also, shouldn't a typical WireGuard roadwarrior client route all IPs through the tunnel (::/0, <IP_ADDRESS>/0)? Wouldn't setting AllowedIPs to only the router side WireGuard interface addresses prevent traffic towards the internet?
For now, this is a NACK from me.

Why would one specify a network address as the interface address?

You're right, I overlooked this - so simply stripping the prefix (a little bit less verbose than appending /32 or /128) should be fine.

Should we consider roadwarrior as the default

I think road warrior is the most common case for which the users export client configs for, so that should work nicely.

always generate AllowedIPs = <IP_ADDRESS>/0, ::/0

We could extend the export dialog to present an additional combo box dropdown to configure the embedded peer AllowedIPs. It would default to <IP_ADDRESS>/0, ::/0 and offer an additional custom... option which, if selected, morphs into a input value prefilled with your suggested values (router's wg Address values converted to host addresses).

Perfect - merged via 73aca68b9e35857ec155f33ca1b1fb5358d69e52, thanks!


Header swipeable.

Hello guys!
Do you know how can I do the same swipe behavior with animation for the header?
For example, make the swipeable green area in the header(attached image).

react-native - 0.61.5
react-native-tab-view - 2.14.4
react-native-gesture-handler - 1.6.1
react-native-reanimated - 1.8.0

Same here. Did you find a solution?
Version packages:

react-native 0.64.0
react-native-tab-view 3.0.1
react-native-gesture-handler 1.10.3
react-native-reanimated 1.13.3

Thank you

Didn't.

I have found a workaround, it is not the best one but you just need the required area to be represented by a component with the style {position: "absolute", top: ..., left: ..., right: ..., bottom: ...}. The trick is the position: "absolute" related to the parent, you can also add your margins and whatever you need in your style, with top, left, right, bottom you set the position of your component.
You need to add this component to each page of the tab view (the page reppresents your parent), my component is just a simple button


CTCP-5488: Add submission logic for when user has selected yes to revised procedure

merge into feature branch once navigation is implemented


HubIntegrationController does not use tenant for filtering

Tenant does not seem to be used in filtering
getExportItemIds():
https://github.com/SAP/vulnerability-assessment-tool/blob/201bfe74adf8eb3320ffd74d0145a96174265e4f/rest-backend/src/main/java/com/sap/psr/vulas/backend/rest/HubIntegrationController.java#L158
getExportItem():
https://github.com/SAP/vulnerability-assessment-tool/blob/201bfe74adf8eb3320ffd74d0145a96174265e4f/rest-backend/src/main/java/com/sap/psr/vulas/backend/rest/HubIntegrationController.java#L208

The tenant can be specified using the HTTP header X-Vulas-Tenant, otherwise the default tenant is taken: See lines 125-136, 207-218 and 284-295 of https://github.com/SAP/vulnerability-assessment-tool/blob/master/rest-backend/src/main/java/com/sap/psr/vulas/backend/rest/HubIntegrationController.java
For getExportItemIds, the spaces of the chosen tenant are read in order to determine the export items (see lines 142 and 224).
In getExportItem(), the space with the given space token is read. Here, you are right that it is not checked whether the given space is indeed part of the specified (or default) tenant. I just addressed this with 3b0de76.

Closed with #305. Thanks Henrik!


Dismissed notifications are lost forever

This is a follow-up to: #22388.
Summary
The current notification model does not accurately represent the desired user actions. Currently, notifications are either "read (deleted)" or "unread". However, there should be a third state, "read (dismissed)". This would be used when a user would like to remove a notification from their screen, but come back to it later. This would also be required for a true notification center, where "dismissed" notifications would be acted upon.

@mattacosta you can just press ESC when notification toasts are there to ignore them and they will still be in the notification center. Why do you need a third state? To my knowledge not even Windows has this?

You are technically correct, there is no need for a third state. Windows doesn't have it either because it forces applications to manage their notification history in all cases except one. I was thinking of a scenario where vscode would handle it, but that can be fixed with a better API, so I'll just leave it to #44121 instead.

From #44185:

Maybe these unimportant notifications could go away entirely, or be in the notification center but without the alert in the status bar?

The second case also covers what I was thinking about here. Clicking "show notifications" should mark unread notifications as read and set the "new notifications" counter to 0. Currently, the only way get the counter back to 0, is to also delete the notification.
I'll add a picture to the summary to better describe the original use case too. I still think #44122 is a better fix though, so I'm keeping this issue closed. You guys can use the other issue if you want to fix it another way.


Implement SyncSnapshot which syncs the content of source snapshot to a file on remote host

longhorn/longhorn#2403
longhorn/longhorn#2534
longhorn/longhorn#1815

Thanks @shuo-wu !
I have implemented the 2nd method


statistics-graph-card to drawcustom

Might be too much to hope for, but it would be great if a statistics-graph-card could be output as an image in the drawcustom function. Or, some other way to draw the line of a line-chart.

Perhaps this is what you’re looking for?
https://github.com/jonasniesner/open_epaper_link_homeassistant/wiki/Bar-Graphs-that-trend-over-time

Perhaps this is what you’re looking for?
https://github.com/jonasniesner/open_epaper_link_homeassistant/wiki/Bar-Graphs-that-trend-over-time

Sorry for the late reply. Appreciate it, thanks! Haven't had time to try it out.


[BUG] stat api is showing the wrong ml_model_count

What is the bug?
When we invoke GET /_plugins/_ml/stats it shows detailed statistics about model.
However there's a field ml_model_count which doesn't show the correct value.
I've deployed 2 SentenceTransformer models in my cluster and the ml_model_count was showing 65.
Reason is: one model has 49 chunks and another model has 14 chunks. 49 + 14 = 63
Which is why it's showing 65.
We need to fix this stat api to get correct number in ml_model_count field.
How can one reproduce the bug?
Steps to reproduce the behavior:

Execute 'GET /_plugins/_ml/stats'
Then you will see the ml_model_count field.

What is the expected behavior?
ml_model_count is showing wrong value.
What is your host/environment?

OS: [e.g. iOS]
Version [starting from 2.4]
Plugins

Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.

https://github.com/opensearch-project/ml-commons/pull/1180 --> Solves this bug.


feature: make GLVis socket user-configurable in miniapps

Add port option to MFEM miniapps.

Mention in CHANGELOG?

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

@johnbowen42 -- some CI tests are failing

@johnbowen42 -- some CI tests are failing

seems good now

Merged in next for testing...


Add sidetag support for koji_build

Tested locally, seems to work like a charm.
TODO:

[x] Write new tests or update the old ones to cover new functionality.
[x] Update doc-strings where appropriate.
[ ] Update or write new documentation in packit/packit.dev.

Fixes https://github.com/packit/packit-service/issues/2377.
Merge after https://github.com/packit/packit/pull/2299.
RELEASE NOTES BEGIN
koji_build job has a new sidetag_group option that allows to perform a downstream Koji build in a sidetag. A new sidetag will be created for each configured dist_git_branch if it doesn't already exist.
RELEASE NOTES END

recheck

[ ] Update or write new documentation in packit/packit.dev.

I don't think it makes much sense to document this now as practical use is quite limited until the follow-up issues are implemented.