Sample Ingress Shown is Out-of-Date

The section on deploying an ingress for Kubernetes is very out of date.  It's in version 1 since v1.19 of Kubernetes, which I don't believe AKS supports anything < v1.19.11.
I recommend using the new networking.k8s.io/v1 api.

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

ID: f53838fc-1654-fc18-7e45-7d556193f77e
Version Independent ID: 4f92bd5b-4b91-b03d-4f1d-8c31d45af0ef
Content: Use LetsEncrypt.org certificates with Application Gateway
Content Source: articles/application-gateway/ingress-controller-letsencrypt-certificate-application-gateway.md
Service: application-gateway
GitHub Login: @Caya
Microsoft Alias: caya

Hello @pplavetzki
Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

I am closing issues that have not been updated in over a year. I will cross reference and research them individually. I am recording each issue and compiling a list of articles to review. If you feel there is an urgent need to address something related to this GitHub issue, please open a new issue and I will reply in the new thread. Please also reference this GitHub issue number in the new issue. Thanks. #please-close


Faster geometric median.

The 'torch' version of the geometric median code uses lists and numpy arrays a bunch, here's a true torch version
Test it by running sae_training/geometric_median.py
It's about a 5x speedup on cpu and 1000x speedup on gpu :D
(please double check my changes to train_sae_on_language_model.py, I'm running stuff on my own code base and haven't actually set up this environment to try the training! Also consider increasing max iter since it's faster.)

This is awesome! I wanted to use this in my work as well, so I packaged this as a pypi module as torch-geometric-mean, repo is here: https://github.com/chanind/torch-geometric-median. @themachinefan I can transfer ownership of this repo to you if you want, or I can delete it if you'd rather this not be in a pypi module.

This is awesome! I wanted to use this in my work as well, so I packaged this as a pypi module as torch-geometric-median, repo is here: https://github.com/chanind/torch-geometric-median. @themachinefan I can transfer ownership of this repo to you if you want, or I can delete it if you'd rather this not be in a pypi module.

Cool, thanks! Go ahead and transfer it

Just sent the transfer request to you

@themachinefan let me know if you have any questions about how the repo is structured or how to do development work on it (my email is in my github profile) . It's set up to autodeploy using semantic-release, so if your commit message to main starts with feat:  it will do a minor version bump, fix:  will do a patch version bump, and adding BREAKING CHANGE: to the commit body will do a major version bump. The library has CI set up to run all linting/type checking/tests automatically, and should currently have close to 100% test coverage (since it's a pretty simple library).

Thanks @themachinefan and @chanind . I had to make some changes for the formatter but all good now.


Keyboard input doesn't work

Environment
Windows build number: 10.0.19041.264
Windows Terminal version (if applicable): 0.11.1333.0

Steps to reproduce
Run the program
Expected behavior
Entering text from the keyboard, copying and pasting
Actual behavior
Keyboard input doesn't work, paste and copy works

I am seeing the same. started within last day or 2.
same terminal version and os build
cannot enter anything via keyboard. powershell launched natively works fine, but all shells inside terminal exhibit same behavior

my guess is this will be closed and this referenced
https://github.com/microsoft/terminal/issues/4448
an issue from Feb.

this workaround fixes it (at least for me)
changed my values from 1 to 0 for both and it started working
https://github.com/microsoft/terminal/issues/4448#issuecomment-617290424

Thank you, problem solved

I do not recommend maintaining this workaround long-term. Your system will break in unexpected ways.

thats all well and good, but until terminal works without it, what can be done? any other ideas?
terminal was working perfectly for me on this box for months until the last update for 2004

can you elaborate on why it will break? in what situation?
i found this reference to those values:
rem =================================== Windows Settings ===================================
rem ---------------------------------------- Privacy ---------------------------------------
rem ............................... Speech, inking, & typing ...............................
rem ________________________________________________________________________________________
reg add "HKLM\Software\Microsoft\Input" /v "InputServiceEnabled" /t REG_DWORD /d "0" /f
reg add "HKLM\Software\Microsoft\Input" /v "InputServiceEnabledForCCI" /t REG_DWORD /d "0" /f

That seems less like a reference (since I can't follow it and figure out where it's from) and more of just a copy/paste from a batch file :smile:
Quote from the input team about this registry key:

Might fix terminal but will break all IME input and other text integration

I don't have more info than that. All other non-keyboard input methods (all IMEs) might be broken.

https://gist.github.com/jsEveryDay/548e3cfd51d02077df90428caa9bf218
batch file indeed! =)

Note that v1 fixed the issue for me, even after reversing the settings back to 1 for both


Running "npm install @azure/msal-angular --save" returns 404

I was trying the Angular wrapper for MSAL. It seems the package is not published yet. Running:
npm install @azure/msal-angular --save

returns a 404 error:
npm ERR! code E404
npm ERR! 404 Not Found: @azure/msal-angular@latest

Also get this.

Same here. Is it not published to npmjs

@M-Medhat  @simonscoffins @jay-pillai . This is currently under development and it's only merged to the dev branch and not master. We will be releasing it soon. Thank you for your patience!


SingleChildScrollView does not clip semantics child

Fixes https://github.com/flutter/flutter/issues/113615
I can't find a reason to clip it since it was laid out just to be thrown away during the semantics gathering stage.
The original issue is because some children are too far away from cache extent and gets throw away. the voiceover then think there is no child.
The alternative is to expose cache extent in single child scroll view, but it doesn't make sense as an API because everything will be laid out regardlessly.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Looks like some tests are failing on this?

besides the expected scuba the other test failure doesn't seem related


Mime type not specified?

I tried using the example code with my own file, and I keep getting the error markdown_conversion_failed_because_of_content or mime type is not specified....
I've tried including a contentType field in the parameters, but that doesn't seem to help. Is there a simple fix to this?

Actually I haven't use this package for a while now, try digging into Slack API help center. Maybe you can find your answer over there

@apellerite have you find the answer?

Same problem here, but alas I have no real understanding of where to start digging to solve the problem.

@idoshamun, @apellerite, the answer is just to change the file type to be appropriate. Check out https://api.slack.com/types/file#file_types for more details. I was able to upload an image by using
filetype: 'auto' instead of filetype: 'post' in the example. Magic!

Thanks for answering the issue!


Missing package product 'Sparkle' and more

This happens a lot after running make build and opening Xcode afterwards.

Solution:
File → Packages → Reset Package Caches


DB setup

Setting up Postgres DB

[x] Migration: Create prompts table
[x] Migration: Create responses table
[x] Script for inserting initial data into db

We'd also need to validate that all sample responses are good to go before populating db

Tables set up in PROD


Multi-stage Dockerfile builds

There's an interesting pattern that shows up in several of our internal applications, especially those using Go or Rust. In particular, we have two Dockerfiles:

Dockerfile.build contains a complete development toolchain, which may be several hundred megabytes in size, and which may rely on a full-fledged distro like Ubuntu. We use this image to build a statically-linked binary.
Dockerfile contains a minimalistic Alpine image. We simply drop our static binary into this image, and the result is often less than 30MB in size.

We may want to make this pattern "official", and provide support for handling it automatically when we invoke cage build.
A possible design
The design could be fairly simple. We might just add something like the following to an individual service:
label:
  io.fdy.cage.build_outputs: "/app/my_static_binary"

...or perhaps instead to config/sources.yml:
myimage:
  prebuild:
    dockerfile: "Dockerfile.prebuild"
    outputs:
      my_static_binary: "/app/my_static_binary"

Then we could simply define a Dockerfile.prebuild in the source directory.

@dkastner votes for the source.yml-based design.

This is now officially supported upstream! See https://docs.docker.com/engine/userguide/eng-image/multistage-build/
We want to support this, and it should work just fine for ordinary builds. cage test, however, might be a bit more complicated, and we need to think it through.

Note that multi-stage builds require Docker 17.05, but ECS is still on 17.03: http://docs.aws.amazon.com/AmazonECS/latest/developerguide/container_agent_versions.html


Wrong version number in in the version dated 2015-12-28

I think the version number in the version dated 2015-12-28 has to be 1.3.1, but in the file "mobile-detect.min.js" the version is "mobile-detect - v1.3.0 - 2015-12-28".

Thanks. I'll generating a new version as soon as Mobile-Detect bumps its version.

I've updated some regexes today. New devices (tablets).


Styled components application

I'm trying to apply styles to both the SelectElement and MultiSelectElement components, and I've noticed that in multiselects, the root styles are applied to the .MuiInputBase-root rather than the .MuiFormControl-root with the select component. This means that it's difficult to apply styling to the label since it's not a decedent.
I've made a codesandbox with what I'm trying to achieve here: https://codesandbox.io/s/condescending-tereshkova-pvtz6o?file=/src/App.js
Are there any workarounds I can use here? Apologies if this is a dumb question, I'm relatively new to styled components & react in general.

@RhysOnlyBetter you can also provide sx props. This package is not doing anything specific in terms of styling the MUI components, so you might better check inside of the MUI website for answers. Otherwise you can also play around with the AutocompleteElement which has a multiple option as well

I am happy to review a PR. The best would be most likely to add a new prop formControl to forward any props for that element.


Async test succeeds even if done is never called

I'm not sure this is a bug, but it's quite disturbing that an async test that never calls done is considered passing.
describe('Test',  () => {
  it('should throw as done is never called', async (done) => {
    let toto = false;

    setTimeout(() => {
      toto = true
    }, 20000)
  })
})

This is how the tap API's work, ie t.test('returns promise that resolves', async () => {}); will pass.  It is also the documented functionality of mocha API's, see https://mochajs.org/#working-with-promises.
So I think this is not a bug, it's the expected result.

Mocha default behavior is to throw if done is not called. I just tried the exact same code on mocha and the test fails.

It seems that mocha detects done argument callback rather than just detecting calls to it.  I've run into an edge case with mocha itself which I've reported at https://github.com/mochajs/mocha/issues/4135.  I'd like to get clarification on what is expected in that case before I try emulating the functionality here.
it('resolution overspecified', async (done) => {
  process.nextTick(() => done());
});

it("doesn't fail but should it?", async (done) => {
  done();
});

it('fails to resolve Promise due to done arg', async (done) => {});

it('async without done argument passes', async () => {});

Sorry, no, this is 100% working as intended, and it is a very intentional intent.
  It's a bad pattern, and it's one of the areas where tap fundamentally disagrees with mocha, so the "mocha-like" tap api will never be fully mocha-like in this particular regard.
Not a bug.  I recommend using the official tap APIs, where it's less unclear, because it's not mimicking something that has a different design goal.


⚠ Bofrost.at has degraded performance

In 26530e6, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1604 ms

Resolved: Bofrost.at performance has improved in 02e8869 after 8 minutes.


Selectors for parent collection cache

It would be an interesting addition to be able to provide a selector for the parent collection. For example:
// Only add a chairCount on furniture of type "table"
Furniture.cacheCount({
  collection: Furniture,
  referenceField: 'furnitureLink',
  cacheField: 'chairCount',
  parentSelector: { type: 'table' },
  selector: { type: 'chair' },
})

// Only add a legCount on furniture of type "chair"
Furniture.cacheCount({
  collection: Legs,
  referenceField: 'furnitureLink',
  cacheField: 'legCount',
  parentSelector: { type: 'chair' },
})

This allows "polymorphic" collections to have different caches depending on their category, type, etc.
It is mostly done for keeping things clean, but one could also imagine using different cache configurations with the same name:
Here's a sarcastic example 🤣:
Users.cacheCount({
  collection: Users,
  referenceField: 'friendIds',
  cacheField: 'americanFriends',
  parentSelector: { citizenShip: 'american' },
  selector: { citizenShip: 'american' },
})

Users.cacheCount({
  collection: Users,
  referenceField: 'friendIds',
  cacheField: 'americanFriends',
  parentSelector: { citizenShip: 'european' },
  selector: { citizenShip: { $in: ['north-american', 'south-american', 'american'] } },
})

You would be responsible for maintaining non-overlapping parent selectors of course, otherwise it will not work.

Just floating this up, as we face a situation that would benefits from this


Add cancel previous CI runs step

Pull Request Checklist:

[ ] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #xyz

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
[ ] HISTORY.rst has been updated (with summary of main changes)

[ ] Link to issue (:issue:number) and pull request (:pull:number) has been added.

[ ] bumpversion patch has been called on this branch
[ ] The relevant author information has been added to .zenodo.json

What kind of change does this PR introduce?

Adds a workflow to stop already-running workflows when receiving multiple pushes to the same PR

Does this PR introduce a breaking change?
No.
Other information:

Looks like it works!

Coverage remained the same at 91.461% when pulling e3cf1173d5fab6589182b70e43646da7eb792c71 on cancel_previous_ci_runs into 67dce3a5b1d0bf81a8be593b3cd54414684506cf on master.


Crawl D&C People

Goal: ScriptureCentral wants to add all of the D&C People content to their database, so we need to crawl the HTML pages on their website and save it in json files.
Create notebook: 05_dc_people_crawler
Steps:

Start from: https://doctrineandcovenantscentral.org/people-of-the-dc/
Fetch each person in the list
Capture all of the HTML on the page and save the HTML and URL as json to a file

Large


Don't override SSL_CERT_FILE environment variable

https://github.com/google/signet/blob/master/lib/signet/ssl_config.rb sets the SSL_CERT_FILE variable. Seems bad.

Probably related but on JRuby I am getting:
OpenSSL::X509::StoreError: setting default path failed: problem creating X509 Aux certificate: java.io.IOException: problem parsing cert: java.security.cert.CertificateParsingException: java.io.IOException: Duplicate extensions not allowed
JRuby has already loaded the certs but signet is also trying to do it. I don't have this problem with other libraries which do OAuth.

On a fresh Jruby 1.7.19 install I can only get Signet working if I remove the ssl_config.rb file. It looks like a hack which was maybe needed a few years ago.

:+1:

Removed in next version :)


Replace viewNova gate with our own, making sure we are last

I don't like this solution, its too dependent on how other things are actually implemented, but it works.  It relies on the following:

gate definitions are unique.  If a gate is defined a second time, the second definition replaces the first
nova defers all of its registration until the ServingNova event is dispatched.
If we are the last listener for that event, we can replace the gate definition
to be last, we defer registering for the ServingNova event until the NovaServiceProviderRegistered event is raised

I'll leave it up to you whether or not to use it.

I am planning to pull this out later and put it into a CLI Installer of the Tipoff packages per my discussion with @jasonmccreary so that it can be added to the actual Laravel application in the NovaServiceProvider

That's preferred.  There's still a risk Nova changes something that breaks the installer, but that's much better than Nova or Laravel changing something that breaks an already installed application.  Also provides some flexibility to do, or help with, other installation type things that are likely to be required.


Structuring the project and energizing the date

I've noticed that the project is not structured, all the html files are directly in the root folder. In addition the date in the footer in static we can make it dynamic with js
Describe the solution you'd like
My solution consists in reorganizing the projects by putting only the index.html file in the root and all the other .html files in the src/ folder and all those concerning style, images, js, etc. in the assets folder. as for dynamizing the date, I'm planning to use js so that the date can adapt to the current year.
Additional context

Hi @WassCodeur.
Thank you so much for your contribution to this project, and once again, welcome to the community.
However, please note that this request will be closed.
Reasons are:
We already have a structure we are following for the static web project, and it will be disastrous to adjust to these changes now, as we approach the end of this very project.
This suggestion shall be followed in the next project.
Once again, thank you @WassCodeur, and welcome to the Algorithmia SE 🌍 community.
Your contributions are highly valued.
Courtesy:
The @ALX-SE-Algorithmia/code-reviewing-team .


ArduCam Mini ov2640 BMP colors & orientation

Hello,
We are currently testing the Arducam mini with the 2MP OV2640. We are using the ArduCAM_Mini_2MP_OV2640_functions.ino on an arduino uno. We are getting good results when the camera is setup in JPG mode. However, when in BMP mode, the colors are not correctly set as well as the orientation. s
is this a known issue ? we are certain we have the latest version of code. can you please investigate

@maminej
This is due to the pixel data bit error, for our new version camera, you don't need to lost the first byte.
Just go to the line 495  and comment the SPI.transfer()

That fixed the problem . thanks.
Can you please explain what does the 0x00 SPI command do ?

@maminej
You are welcome. the 0x00 is dummy data which is in order to read data. You can get it from SPI protocol.


defective prediction for large focal length

          在训练中，大部分数据也并不1000。比如taskonomy，大部分在500-700左右，测试的NYU等数据集也并不在500左右。所以并不是平均值在1000。关于这部分的ablation，还可以继续深入探索一下。

Originally posted by @YvanYin in https://github.com/YvanYin/Metric3D/issues/3#issuecomment-1657113062
Hi, thanks for your great work! I think I met a duplicate of this issue when testing on different dataset. When inferring on outdoor images with 'intrinsic': [1966.9, 1969.5, 948.7, 498.4], the predicted depth is unexpectedly poor. I tried different crop_size, but it didn't help much, RMSE is about 10m on sparse lidar measurements.

for SHIFT dataset where 'intrinsic': [640, 640, 640, 400], the result is much more reasonable, RMSE is about 7m.

This performance difference seems to be related to the training data, could you share your ideas on this? Thank you!

          在训练中，大部分数据也并不1000。比如taskonomy，大部分在500-700左右，测试的NYU等数据集也并不在500左右。所以并不是平均值在1000。关于这部分的ablation，还可以继续深入探索一下。

Originally posted by @YvanYin in #3 (comment) Hi, thanks for your great work! I think I met a duplicate of this issue when testing on different dataset. When inferring on outdoor images with 'intrinsic': [1966.9, 1969.5, 948.7, 498.4], the predicted depth is unexpectedly poor. I tried different crop_size, but it didn't help much, RMSE is about 10m on sparse lidar measurements.

for SHIFT dataset where 'intrinsic': [640, 640, 640, 400], the result is much more reasonable, RMSE is about 7m.
This performance difference seems to be related to the training data, could you share your ideas on this? Thank you!

Thanks for your cases, we will check the first sample later, the depth map looks terrible.

We tested this case with several models. Our ConvNeXt models cannot predict reasonable depth maps, while an ongoing vit models can output the basic elements (road, vehicles, sound insulation wall). Since there are still problems in this model, it will not be released very soon.

Thanks for looking into this! Metric3D has a convincing theory and shows good generalizing ability in practice, as a novice I can only make blind guesses towards this extreme scenario(focal length = 1967) :

Is it due to the large difference compared with training data distribution (focal length mainly below 1000), such that the ConvNeXt model doesn't perform well in the CNN regression fashion?
Or it has sth to do with the drastic hypothetical move in canonical camera space? I'm trying to tell which of the 2 patterns this website shows applies to Metric3D:

https://exposuretherapy.ca/photography-guide/perspective-and-camera-position/
In the first set of images, 4 cameras shoot at the same spot, and then crop/enlarge to get identical images.

However, in the second set of images, 4 cameras positions differently to directly shoot the target object to be of same size. The background gets wider as a result of pin-hole imaging of shorter focal length.

Are we "cropping / dragging" the objects or "moving closer/away" ourselves? If the latter, does this cone of vision contribute to the distorted prediction?
Forgive me for any silly mistakes, and please do correct me, clearly I could use some help on optics... Cheers!

Personally I do not think focal length will affect the shapes of objects in prediction. However it might affect the scale learning.

For your case, I think following could explain well:

CROP will not affect the scales
RESIZE towards LARGER / SMALLER sizes means the focal length becomes larger/smaller
For one specific object, it can be regarded as moving closer/away from ourselves. But in the real world, while the cameras are posed differently, different objects (with different depth) will be resized differently, as we have derived in the figure above.

I'm also very suspicious of training using image crops, like if your crop looks like this, how do you know how far it is? It looks the same at multiple different distances

I'm also very suspicious of training using image crops, like if your crop looks like this, how do you know how far it is? It looks the same at multiple different distances, as you don't know the surroundings

The showed case has a very small field of view. If you enlarge the training crops size, this problem can be allievated.


Bump Android app version

This PR bumps the current Android app version from 2.3.2 to 2.3.3.
Release: https://github.com/corona-warn-app/cwa-app-android/releases/tag/v2.3.3

@Ein-Tim Thanks. Enjoy Saturday!

@dsarkar Thanks, you too!


dirPagination: Question: how to reset pager back to page 1

I've been working with the pagination directive.  By basic setup is a single page which allows the user to enter search criteria and then click search to see the results.  The results are displayed on the same page, below the search input fields.  The pagination is working great, but let's say the user goes to page 3 and then decides to do a new search.  The user changes the search criteria, clicks search again but the pagination controller is never reset to 1...item 3 is still highlighted.
What is the proper way to reset the pagination control back to page 1?  I tried binding current-page  to a var in my scope and reseting that, but that doesn't seem to change state of the pagination controller.
Any ideas?  Thanks!

I believe this was reintroduce in the new version...

I'll check it out when I get a bit of free time, thanks.

Actually, I just solved my issue by passing paginationService to my controller and inside of it calling
paginationService.setCurrentPage('paginationId', 1);
when I do another search.

So that's a work around at least...

@krinkere I just had time to take a look, and as far as I can see the issue remains solved. The unit test created for it still passes, and just playing around with the plunker demo, I see that changing the current-page scope variable will correctly update the controls.
Do you have any code you can show which isn't working as expected? Or even better, are you able to recreate in Plunker?

I am using several different plugins in my app, so I wonder if something interferes with your code.
I guess at this point I am just happy that I was able to find a workaround so it is no longer an issue. Thank you for looking into it.
I will try to post a sample

I'm having the same issue, Michael. I've followed your async example perfectly, but the pagination controls don't update when I change the $scope.pagination.current variable in my controller.

Otherwise, the directive is awesome--thanks so much for making this!
@krinkere Where/How are you passing the service into your controller? Could you post a code snippet?

@dropfish if you are updating $scope.pagination.current directly in your controller, then you'll have to set up a $watch on that value to trigger the page change callback. This is because the page change callback is only triggered by a click on a pagination link. In the case that you change the page programatically in the controller, it won't be fired, hence the need for the $watch.

@michaelbromley thanks so much for the fast response. I'm new to Angular, so I'm sorry for the basic questions.
It sounds like I need to set up a $watch in my controller that will do something like this:
$scope.$watch('pagination.current', function() {        // call your setCurrent() function    });
Is that correct? If so, how can I call your setCurrent() function in my controller? I tried passing the paginationService by name into the controller but it was undefined.
I assume you didn't mean that I need to simply have a $watch on pagination.current, seeing as there's already one implicitly created because I'm using it in my template: {{ pagination.current }}.
Thank you for your help, I greatly appreciate it!

Yeah, you're on the right track. If you have followed the async example from the docs, you should have a scope method that you are passing in to the on-page-change attribute. In the example, it is  $scope.pageChanged().
You can just use this as the $watch callback:
$scope.$watch('pagination.current', function(val) {
  $scope.pageChanged(val);
});

You don't need to use the internal components such as the paginationService.
... Actually now that I'm taking a closer look at that example, I think there is an error with it. I missed off the current-page attribute from the dir-paginate directive. It should look like this:

See if that works for you.

You're the man! Got it working by adding the current-page attribute. I can't believe how quickly you responded and helped me, that's so awesome :)

I am facing same issue can anyone please please provide me working plnkr.

@samirshah I've modified Michael's plunkr to include a resetPage() function that resets the currentPage variable to 1. You can test it by clicking on any page other than 1 and then clicking the "Reset Page" button I added. Here's the forked plunkr.
If you're having trouble implementing this in your code, make sure you're adding the current-page attribute to your dir-paginate directive (not in the pagination controls). Hope this helps!

@dropfish thanks for the Plunker demo - should be useful to others with the same question.

Micheal,
Is there a way to search on the current page, if I were to be on page 5, this way the search does not default to page 1 and only search within page 5 until it is directed to go else where. Please advice

@shalizi If you mean you want to filter only the results on that page, then yes, this should be possible by putting the filter filter after the itemsPerPage filter. e.g.:
<input ng-model="q">
...

I will try this, I hope this works. Regardless, THANK YOU for helping.
On Mon, Sep 21, 2015 at 8:34 AM, Michael Bromley<EMAIL_ADDRESS>wrote:

@shalizi https://github.com/shalizi If you mean you want to filter only
the results on that page, then yes, this should be possible by putting the
filter filter after the itemsPerPage filter. e.g.:

...

—
Reply to this email directly or view it on GitHub
https://github.com/michaelbromley/angularUtils/issues/21#issuecomment-142016969
.

Michael,
Search is still a bit off, I don't even mind having it search either
current page or entire list. The only thing that I'm doing different, I'm
using div's instead of li's with ng-repeat. I don't think this should
create any issues since ng-repeat works the same way with any element but I
could be wrong. I'm not sure what to make of it. Thanks for helping.
Ahmad:
On Mon, Sep 21, 2015 at 8:34 AM, Michael Bromley<EMAIL_ADDRESS>wrote:

@shalizi https://github.com/shalizi If you mean you want to filter only
the results on that page, then yes, this should be possible by putting the
filter filter after the itemsPerPage filter. e.g.:

...

—
Reply to this email directly or view it on GitHub
https://github.com/michaelbromley/angularUtils/issues/21#issuecomment-142016969
.

Hi,
Sorry, I don't mean to bombard you with all these emails but I thought I
send you this one. This way you don't have to look into something that is
not broken. Everything is working good. My situation was a bit complicated,
I'm using ng-repeat with div's, forms, and tables all at the same time and
after making sure all elements were properly terminated.. everything works
smoothly, thank you for putting together a very robust pagination program.
Ahmad:
On Thu, Sep 24, 2015 at 3:36 PM, Ahmad Shalizi<EMAIL_ADDRESS>wrote:

Michael,
Search is still a bit off, I don't even mind having it search either
current page or entire list. The only thing that I'm doing different, I'm
using div's instead of li's with ng-repeat. I don't think this should
create any issues since ng-repeat works the same way with any element but I
could be wrong. I'm not sure what to make of it. Thanks for helping.
Ahmad:
On Mon, Sep 21, 2015 at 8:34 AM, Michael Bromley<EMAIL_ADDRESS>
wrote:

@shalizi https://github.com/shalizi If you mean you want to filter
only the results on that page, then yes, this should be possible by putting
the filter filter after the itemsPerPage filter. e.g.:

...

—
Reply to this email directly or view it on GitHub
https://github.com/michaelbromley/angularUtils/issues/21#issuecomment-142016969
.

@shalizi Thanks for the update. Glad you got it sorted.

it dont work need help pls

https://embed.plnkr.co/z3Gl6uBnC34cQiEyeInm


Feature: Enable whitepaper option in Spectrum

Implementing the getrawtransaction method in Spectrum should make it possible to retrieve the whitepaper from the timechain with Spectrum.
getrawtransaction is already implemented in the ElectrumX API:
https://electrumx.readthedocs.io/en/latest/protocol-methods.html#blockchain-transaction-get

Seems like #36  was not good enough. @PaarthAgarwal  can you have a look?!
In the case of the whitepaper, it's called like this:
            raw_tx = app.specter.rpc.getrawtransaction(
                "54e48e5f5c656b26c3bca14a8c95aa583d07ebe84dde3b7dd4a78f4e4186e713",
                False,
                "00000000000000ecbbff6bafb7efa2f7df05b227d5c73dca8f2635af32a2e949",
            )

Which creates this stacktrace:
Traceback (most recent call last):
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/flask/app.py", line 1523, in full_dispatch_request
    rv = self.dispatch_request()
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/flask/app.py", line 1509, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/flask_login/utils.py", line 272, in decorated_view
    return func(*args, **kwargs)
  File "/home/kim/src/specter-desktop/src/cryptoadvance/specter/server_endpoints/welcome/welcome.py", line 101, in get_whitepaper
    raw_tx = app.specter.rpc.getrawtransaction(
  File "/home/kim/src/specter-desktop/src/cryptoadvance/specter/rpc.py", line 495, in fn
    r = self.multi([(method, *args)], **kwargs)[0]
  File "/home/kim/src/specter-desktop/src/cryptoadvance/specterext/spectrum/bridge_rpc.py", line 96, in multi
    result = [
  File "/home/kim/src/specter-desktop/src/cryptoadvance/specterext/spectrum/bridge_rpc.py", line 97, in <listcomp>
    self.spectrum.jsonrpc(
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/cryptoadvance/spectrum/spectrum.py", line 386, in jsonrpc
    raise e
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/cryptoadvance/spectrum/spectrum.py", line 376, in jsonrpc
    res = m(*args, **kwargs)
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/cryptoadvance/spectrum/spectrum.py", line 53, in wrapper
    return f(*args, **kwargs)
TypeError: Spectrum.getrawtransaction() takes from 2 to 3 positional arguments but 4 were given

Seems like #36 was not good enough. @PaarthAgarwal can you have a look?!
In the case of the whitepaper, it's called like this:
            raw_tx = app.specter.rpc.getrawtransaction(
                "54e48e5f5c656b26c3bca14a8c95aa583d07ebe84dde3b7dd4a78f4e4186e713",
                False,
                "00000000000000ecbbff6bafb7efa2f7df05b227d5c73dca8f2635af32a2e949",
            )

Which creates this stacktrace:
Traceback (most recent call last):
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/flask/app.py", line 1523, in full_dispatch_request
    rv = self.dispatch_request()
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/flask/app.py", line 1509, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/flask_login/utils.py", line 272, in decorated_view
    return func(*args, **kwargs)
  File "/home/kim/src/specter-desktop/src/cryptoadvance/specter/server_endpoints/welcome/welcome.py", line 101, in get_whitepaper
    raw_tx = app.specter.rpc.getrawtransaction(
  File "/home/kim/src/specter-desktop/src/cryptoadvance/specter/rpc.py", line 495, in fn
    r = self.multi([(method, *args)], **kwargs)[0]
  File "/home/kim/src/specter-desktop/src/cryptoadvance/specterext/spectrum/bridge_rpc.py", line 96, in multi
    result = [
  File "/home/kim/src/specter-desktop/src/cryptoadvance/specterext/spectrum/bridge_rpc.py", line 97, in <listcomp>
    self.spectrum.jsonrpc(
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/cryptoadvance/spectrum/spectrum.py", line 386, in jsonrpc
    raise e
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/cryptoadvance/spectrum/spectrum.py", line 376, in jsonrpc
    res = m(*args, **kwargs)
  File "/home/kim/src/specter-desktop/.env/lib/python3.10/site-packages/cryptoadvance/spectrum/spectrum.py", line 53, in wrapper
    return f(*args, **kwargs)
TypeError: Spectrum.getrawtransaction() takes from 2 to 3 positional arguments but 4 were given

Did a some research. I don't know how to test but adding a 4th parameter hex string here might do the trick.
https://github.com/cryptoadvance/spectrum/blob/fa87be3f8c0fdf1628941d0558e065c666092079/src/cryptoadvance/spectrum/spectrum.py#L580

To clarify a bit and give some background: @PaarthAgarwal
In Specter using Bitcoin Core getrawtransaction is called exactly like it is specified here:
https://developer.bitcoin.org/reference/rpc/getrawtransaction.html?highlight=getrawtransaction
00000000000000ecbbff6bafb7efa2f7df05b227d5c73dca8f2635af32a2e949 is the blockhash where the tx with the whitepaper data can be found. This is an optional argument but it speeds up the feature. So I would just add this.

You can test this in the end pretty easily, connect via Spectrum to one of the main chain provider (emzy or Blockstream server).

Thanks for the clarification @moneymanolis. I appreciate that. Will open a PR soon with the fix.
Also, I'm glad to share I just now cleared the screening round of the Summer of Bitcoin!🎉🎉


Feature Request: Strict import scope and function signature semantics

Summary of the new feature/enhancement
The current version of PowerShell is actually a very runtime driven framework. Function calls are only checked runtime whether the function is present and the parameters are met.
Import-Module instructions only execute runtime and there is no guidance design time which functions will be pulled into the current scope.
What we like to see is a more design time driven experience such as frameworks as TypeScript Nodejs.
The benefit of the EcmaScript module system is that you know design time which functions you are pulling into scope. Additionally, the import process of Nodejs is much faster than PowerShell.
The benefit of TypeScript is that function calls are validated design time. When a parameter or return type is not met, the file simply does not get compiled.
PowerShell should block any function use that is not coming from an import statement. TypeScript nodejs files simply don't compile when unknown functions are being called.
E.g.
# Import specific functions / cmdlets
Import Get-AzResourceGroup, Get-AzKeyVault from Az
Get-AzResourceGroup -Name xyz

# Import the whole set of exported functions / cmdlets to a variable
Import * as $Az from Az
$Az.Get-AzResourceGroup -Name xyz

# This should not compile / execute and should throw a parameter mismatch error
Get-AzResourceGroup -RandomParameter

Can't you get what you want already by using $PSModuleAutoLodingPreference?

Can't you get what you want already by using $PSModuleAutoLodingPreference?

Yes we already always import explicitly. This still does not guarantee if the function signature is called correctly.
Interesting to learn the ModuleQualified setting though, have not seen it before, I will discuss this with my team.

Yes we already always import explicitly. This still does not guarantee if the function signature is called correctly.
Interesting to learn the ModuleQualified setting though, have not seen it before, I will discuss this with my team.

I think if you want strict validation of function signatures, that might be better suited as a PSScriptAnalyzer rule cc @rjmholt @JamesWTruher
PowerShellGet v2 depends on PackageManagement module.  Since the call to PackageManagement cmdlet is fully qualified, I would have expected that to work...
Az module is just a meta-module that loads all the other actual Az modules, so that behavior is currently expected.  I believe individual Az modules end up importing Az due to cross dependencies across Az modules.  If you're goal is to restrict the cmdlets/functions that can be called within a script, you should look at constrained runspaces.  The easiest way to do this via script is Just Enough Administration.

I think if you want strict validation of function signatures, that might be better suited as a PSScriptAnalyzer rule cc @rjmholt @JamesWTruher
PowerShellGet v2 depends on PackageManagement module.  Since the call to PackageManagement cmdlet is fully qualified, I would have expected that to work...
Az module is just a meta-module that loads all the other actual Az modules, so that behavior is currently expected.  I believe individual Az modules end up importing Az due to cross dependencies across Az modules.  If you're goal is to restrict the cmdlets/functions that can be called within a script, you should look at constrained runspaces.  The easiest way to do this via script is Just Enough Administration.

I think if you want strict validation of function signatures, that might be better suited as a PSScriptAnalyzer rule cc @rjmholt @JamesWTruher

Makes sense! I would like to learn how I could establish this.

If you're goal is to restrict the cmdlets/functions that can be called within a script, you should look at constrained runspaces. The easiest way to do this via script is Just Enough Administration.

No this is too much for us. We just want to have proper "compile-time" support. Additionally, as as nice to have we would like to see better semantics on the Import-Module side, not cluttering the current scope so much, and much faster processing. Maybe we are spoiled too much by the EcmaScript module way of working 😉

I think if you want strict validation of function signatures, that might be better suited as a PSScriptAnalyzer rule cc @rjmholt @JamesWTruher

Makes sense! I would like to learn how I could establish this.

If you're goal is to restrict the cmdlets/functions that can be called within a script, you should look at constrained runspaces. The easiest way to do this via script is Just Enough Administration.

No this is too much for us. We just want to have proper "compile-time" support. Additionally, as as nice to have we would like to see better semantics on the Import-Module side, not cluttering the current scope so much, and much faster processing. Maybe we are spoiled too much by the EcmaScript module way of working 😉

I've been interested in the idea of a more strict, more maintainable style of import for awhile as well.
I'm not sure it can be within PowerShell itself though. Languages with multiple dialects are pretty difficult to maintain.  Some good evidence of this within PowerShell itself is how neglected Set-StrictMode has become over time. I think for something like this to happen, it would really to be a transpiler (like typescript) and probably would need to be developed and maintained by a different org.
There's definitely some potential there, but it's really difficult to recommend anyone take on that work when you could just as easily make a C# binary module instead.

I've been interested in the idea of a more strict, more maintainable style of import for awhile as well.
I'm not sure it can be within PowerShell itself though. Languages with multiple dialects are pretty difficult to maintain.  Some good evidence of this within PowerShell itself is how neglected Set-StrictMode has become over time. I think for something like this to happen, it would really to be a transpiler (like typescript) and probably would need to be developed and maintained by a different org.
There's definitely some potential there, but it's really difficult to recommend anyone take on that work when you could just as easily make a C# binary module instead.

Classes provide you with a more structured, early checked model. Have you tried using these? Also quite a bit faster if you don't require all the features of the parameter binder.

Classes provide you with a more structured, early checked model. Have you tried using these? Also quite a bit faster if you don't require all the features of the parameter binder.

We are using the Az modules heavily. So we really would like to see the strictness applied to the Az modules as well.
@powercode It seems PowerShell is lacking named parameters with class methods. So readability is impacted if we move away from regular functions.
@SeeminglyScience I guess c# would be an option if we were able to just ship the c# as a script.  There was already csx, and now with c# there is this top-level program feature.
We are also considering moving to nodejs which gives a perfect solution for all of this. Unfortunately the Az modules nodejs equivalent last time we checked (August 2020) were not very mature and incomplete (https://azure.github.io/azure-sdk-for-js/). Nodejs brings us:

Compatibility with Azure Pipelines; it is providing a nodejs task runner;
Perfect module import semantics;
Strict function signature checking.
I guess we need to revisit this area. It looks like the past few months they didn't stand still!

If we would be able to mix our PowerShell with dotnet code, I guess that we then would hit the dotnet Azure sdk also lagging behind the az cli and az PowerShell modules surfaces.

We are using the Az modules heavily. So we really would like to see the strictness applied to the Az modules as well.
@powercode It seems PowerShell is lacking named parameters with class methods. So readability is impacted if we move away from regular functions.
@SeeminglyScience I guess c# would be an option if we were able to just ship the c# as a script.  There was already csx, and now with c# there is this top-level program feature.
We are also considering moving to nodejs which gives a perfect solution for all of this. Unfortunately the Az modules nodejs equivalent last time we checked (August 2020) were not very mature and incomplete (https://azure.github.io/azure-sdk-for-js/). Nodejs brings us:

Compatibility with Azure Pipelines; it is providing a nodejs task runner;
Perfect module import semantics;
Strict function signature checking.
I guess we need to revisit this area. It looks like the past few months they didn't stand still!

If we would be able to mix our PowerShell with dotnet code, I guess that we then would hit the dotnet Azure sdk also lagging behind the az cli and az PowerShell modules surfaces.

Much of the readability issues can be countered with good naming of variables. But in general, there is a tension between being a good shell and a good language. There are areas where the late binding and type conversion of PowerShell is more of a bug than a feature.
When I find myself in that situation, I write the code in C# and use PowerShell where it really shines, to glue different pieces together.

Much of the readability issues can be countered with good naming of variables. But in general, there is a tension between being a good shell and a good language. There are areas where the late binding and type conversion of PowerShell is more of a bug than a feature.
When I find myself in that situation, I write the code in C# and use PowerShell where it really shines, to glue different pieces together.

Would there be an opportunity for me to connect with a developer of the PowerShell vscode extension? I am eager to explore the changes required myself.
It would make perfect sense to me at least to have an optional switch in the PowerShell strictness mode to enable both of the features mentioned in the original post, being:

Strict import semantics
Strict function signature linting

Ad 2. Currently you already get very nice intellisense when writing a cmdlet invocation, i.e. vscode knows perfectly which parameters are allowed. Would be a small adjustment to falsify unexpected parameters.
Ad 1. Maybe there is some intermediary easy solution? For example, we could first go for some comment driven metadata to steer the linting engine to the right file or module for the specific cmdlet and block the linting process to freely peek in every file available in the workspace and psmodule path.
@powercode do you have an example repo where you lay out your way of working where you mix and match PowerShell and c#? And what is your assessment of the maturity of the Azure .NET SDK? To what extent is it lagging behind the latest REST APIs.

Would there be an opportunity for me to connect with a developer of the PowerShell vscode extension? I am eager to explore the changes required myself.
It would make perfect sense to me at least to have an optional switch in the PowerShell strictness mode to enable both of the features mentioned in the original post, being:

Strict import semantics
Strict function signature linting

Ad 2. Currently you already get very nice intellisense when writing a cmdlet invocation, i.e. vscode knows perfectly which parameters are allowed. Would be a small adjustment to falsify unexpected parameters.
Ad 1. Maybe there is some intermediary easy solution? For example, we could first go for some comment driven metadata to steer the linting engine to the right file or module for the specific cmdlet and block the linting process to freely peek in every file available in the workspace and psmodule path.
@powercode do you have an example repo where you lay out your way of working where you mix and match PowerShell and c#? And what is your assessment of the maturity of the Azure .NET SDK? To what extent is it lagging behind the latest REST APIs.

Would there be an opportunity for me to connect with a developer of the PowerShell vscode extension? I am eager to explore the changes required myself.

You'd want to check out PSScriptAnalyzer.  There isn't much related logic in the VSCode extension nor even the language server (PowerShellEditorServices).

Ad 2. Currently you already get very nice intellisense when writing a cmdlet invocation, i.e. vscode knows perfectly which parameters are allowed. Would be a small adjustment to falsify unexpected parameters.

VSCode only knows because the PowerShell itself tells it though (through the SMA.CommandCompletion API), and only on demand based on cursor location.  That kind of analysis for an entire document would be very expensive, especially once you get into type inference (assuming you want to check input signature). That's not to say that that type of analysis can't be done incrementally, but there is currently no tooling for that.

Ad 1. Maybe there is some intermediary easy solution? For example, we could first go for some comment driven metadata to steer the linting engine to the right file or module for the specific cmdlet and block the linting process to freely peek in every file available in the workspace and psmodule path.

VSCode uses the same runspace that the PowerShell Integrated Console uses. So you can somewhat control state by changing module autoloading preference and/or manually importing modules. There is no static analysis way to do that though with the exception of fully module qualified commands.

Would there be an opportunity for me to connect with a developer of the PowerShell vscode extension? I am eager to explore the changes required myself.

You'd want to check out PSScriptAnalyzer.  There isn't much related logic in the VSCode extension nor even the language server (PowerShellEditorServices).

Ad 2. Currently you already get very nice intellisense when writing a cmdlet invocation, i.e. vscode knows perfectly which parameters are allowed. Would be a small adjustment to falsify unexpected parameters.

VSCode only knows because the PowerShell itself tells it though (through the SMA.CommandCompletion API), and only on demand based on cursor location.  That kind of analysis for an entire document would be very expensive, especially once you get into type inference (assuming you want to check input signature). That's not to say that that type of analysis can't be done incrementally, but there is currently no tooling for that.

Ad 1. Maybe there is some intermediary easy solution? For example, we could first go for some comment driven metadata to steer the linting engine to the right file or module for the specific cmdlet and block the linting process to freely peek in every file available in the workspace and psmodule path.

VSCode uses the same runspace that the PowerShell Integrated Console uses. So you can somewhat control state by changing module autoloading preference and/or manually importing modules. There is no static analysis way to do that though with the exception of fully module qualified commands.

@SeeminglyScience albeit unrelated to my OP, if the runspace is shared, then there are two things not clear to me:

Why is the completion support on the cmdlets so different in the editor and on the prompt? On the prompt is so much better, so much faster.
Where is the pesky delay coming from when I press F8 from the editor? Sometimes it takes many seconds before the selected text get passed to the prompt.

Why is the completion support on the cmdlets so different in the editor and on the prompt? On the prompt is so much better, so much faster.
Where is the pesky delay coming from when I press F8 from the editor? Sometimes it takes many seconds before the selected text get passed to the prompt.

Bugs.  PowerShell/PowerShellEditorServices#1295 is probably the thread to follow.

I think if you want strict validation of function signatures, that might be better suited as a PSScriptAnalyzer rule cc @rjmholt @JamesWTruher

I've done some work toward this. Requires investment in a static parameter binding approximation algorithm. Which PSScriptAnalyzer has general need of. But this plus more performant profiles would be the silver bullet for static analysis.

@rjmholt Has there been any recent development? Many of our bugs are caused by insufficient static analysis. Would it be easy to start with some manual decoration language so that you can help the language service? If we were able to adopt something like the TypeScript module import semantics, then the language service can limit its analysis to the particular file.

No new developments here.

Would it be easy to start with some manual decoration language so that you can help the language service? If we were able to adopt something like the TypeScript module import semantics, then the language service can limit its analysis to the particular file.

Unfortunately adopting new syntax or semantics is hard, and writing the analysis around it is also hard.

Many of our bugs are caused by insufficient static analysis

Traditionally, static analysis will find bugs, but lack of it won't cause them.

@rjmholt you were mentioning in the August 2021 community call that some internal projects that have been building extra analysis rules for static analysis? Not suitable for general purpose, but maybe the various bits can be shared to build upon further? We are not using the dynamic nature of PowerShell to great extent. For us it is just a dotnet dialect and I guess the suggested Use-StrictMode -Ultra would be helpful to us 🙂
In the meanwhile if I find further time I will try to continue working on a simple custom analyzer that takes import statements inside comment conventions, combined with scraping the abstract syntax tree for function definitions. I started this exploration during past summer break.

that some internal projects that have been building extra analysis rules for static analysis? Not suitable for general purpose, but maybe the various bits can be shared to build upon further?

Yeah, I don't control that code but I've seen it and it's very very old and different. There's interest from the owning team to perform a gradual migration, at least of the easier parts. As a first example, see https://github.com/PowerShell/PSScriptAnalyzer/pull/1705.

In the meanwhile if I find further time I will try to continue working on a simple custom analyzer that takes import statements inside comment conventions, combined with scraping the abstract syntax tree for function definitions. I started this exploration during past summer break.

So on this front, I've seen other examples of custom #include pragmas in scripts. using module and using assembly were meant to be the actual versions of this. But for the most part, my intuition is that analyzers should simply forbid things like:

Using variables with Import-Module or Export-ModuleMember
Using *-Variable cmdlets
*-*Item cmdlets with variable/function providers
Anything involving dynamic scope (variables not defined in the immediate scope)
Probably a few other things I haven't thought of that allow you to dynamically create variables/functions

Once those become errors, you can statically reason about a lot more things.
At that point, you want constant folding (to propagate variable values, splatting, etc) and type inference:
https://github.com/PowerShell/PowerShell/blob/176303d172bcb0726e097ac5139de9f724ecec6b/src/System.Management.Automation/engine/parser/TypeInferenceVisitor.cs#L42-L50
You also need some concept of the modules available at runtime and the whole command metadata for each exported command. That's needed to work out types and parameter binding. That essentially requires a manifest of well-known commands on each platform. I've done a fair amount of the work required for that as part of PSSA's UseCompatibleCommands rule.
I've also seen things that try to follow through a script's dependencies and dot-sources as well, and those basically require static inference of the filesystem layout in a script/module's deployment environment.
Anyway, I don't see a huge reason to build a fresh analyzer from scratch here. PSSA is perfectly capable of providing the platform for a lot of this. But if you are interested, I started some work to reform PSSA as a platform some time ago but had to drop it to work on other things.

Are InferTypeOf and StaticParameterBinder readily available from the context of a PSSA rule?
Chris Dent provides the following PSSA rule in PowerShell which can be used as an example: https://github.com/indented-automation/Indented.ScriptAnalyzerRules/blob/main/Indented.ScriptAnalyzerRules/public/rules/UseSyntacticallyCorrectExamples.ps1
I have been put on two tracks here because I find it easier to explore this all within Visual Studio where everything is c#. The core PSSA rules are written with c# whereas PSSA provides custom rules through PowerShell. At least I am more familiar with the debugging experience inside Visual Studio compared to Visual Studio Code. I guess I should explore the debugging experience for PSSA rules in PowerShell a bit more.


I believe the clients call it data over JSON-RPC.

Nethermind at least supports both, does anyone know about other clients?

@MicahZoltu geth calls it input, not data: https://github.com/ethereum/go-ethereum/blob/dfeb2f7e8001aef1005a8d5e1605bae1de0b4f12/internal/ethapi/api.go#L1275
Does nethermind return data by default?

Please reopen if you believe there is a strong reason to prefer data over input.


Cannot show custom message in numericality validation

All custom messages for numericality validation does not work. The messages as below:
notInteger
notGreaterThan
notGreaterThanOrEqualTo
notEqualTo
notLessThan
notLessThanOrEqualTo
notOdd
notEven

This is my use case:
quantity: {
                presence : {
                    message : "^coupon.qty.required"
                },
                numericality: {
                    onlyInteger: true,
                    notInteger: "^coupon.qty.int",
                    greaterThanOrEqualTo: -1,
                    notGreaterThanOrEqualTo: "^coupon.qty.min"
                }
            }

When i debugged, i found that there is one issue at line https://github.com/ansman/validate.js/blob/master/validate.js#L834
If we change:
var msg = this["not" + v.capitalize(name)] || "must be %{type} %{count}";
to
var msg = options["not" + v.capitalize(name)] || "must be %{type} %{count}";
then the custom messages will be shown.

This is intentional, there currently isn't any support for setting the messages for individual cases using the options. It's still TODO.

This has been fixed in 0.9.0


apiExamples.md  file is not generated

Describe the bug
No examples for any public attributes or functions in the API.
To Reproduce
Steps to reproduce the behavior:

Go to menu.
Click on API tab.
See that there are no examples.

Expected behavior
API examples present.

The current automated task of creating API examples is not persistent between all component repos and is a custom add to the repo.
It's preferred that this feature be baked into the generator and added to the repo when the repo is upgraded.


Document the query by column feature including cardinality

Based on our conversation on Slack, I added some documentation for the feature of querying by column.
Please have a look and see if you think this would be a helpful addition.
One thing I think was incorrect before was this
Dataloader.load(:accounts, :user, :organization)
I highlighted with a comment in the PR

Fantastic, thank you!


Error : sendViewBook

Since 1.9, the  "sendViewBook" don't work because the "SPacketCustomPayload" require the hand.
You need to add a varInt for the hand : 0 for the main hand, 1 for the offhand
http://wiki.vg/Plugin_channels#MC.7CBOpen

Due to an error on my part, I have created a new PR : https://github.com/SpongePowered/SpongeCommon/pull/924


Fix issues related to "Not AWS" platforms

What this PR does / why we need it:
First issue: Create oidc-storage-provider-s3-creds volume only if OIDCStorageProviderS3Secret exists
The code added in PR #949 cause to  command to fail to all not AWS platform
The code try to access to OIDCStorageProviderS3Secret param which initialized only in AWS platform
(initialized only if user add oidc-storage-provider-s3-credentials flag)
Therefore, in order to fix this, validate OIDCStorageProviderS3Secret not empty before the create
Second issue: Fix issue of NodePool not created for Agent and None platforms
Since PR #944 NodePool is not created for None and Agent platforms
Add Default case to the switch/case to handle those platforms
Checklist

[x] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/lgtm

/hold
Can we make this a platform check instead of a nil check?

Could you clarify how did https://github.com/openshift/hypershift/pull/944 dropped agent/None? It's not obvious to me looking at the PR

Could you clarify how did #944 dropped agent/None? It's not obvious to me looking at the PR

Before the change, the default NodePool was assigned to the nodepool param, in the end of the function the nodepool was returned even if it wasn't changed by the platform type
After the change, empty NodePool is created and objects are added to this list only in AWS and Kubevirt platforms cases, otherwise it returned empty

NodePool commit lgtm.  Deferring to @ironcladlou on the other commit.
/approve

@ironcladlou Can this be merged?

So right now:

We validate()

	if len(o.OIDCStorageProviderS3CredentialsSecret) > 0 && len(o.OIDCStorageProviderS3Credentials) > 0 {
		errs = append(errs, fmt.Errorf("only one of --oidc-storage-provider-s3-secret or --oidc-storage-provider-s3-credentials is supported"))
	}

Then we build the secret if needed and pass it through deployment.Build and build the volumes unconditionally.
Now, I'd suggest the following:

Improve Validate() to ensure also OIDCStorageProviderS3Region and OIDCStorageProviderS3BucketName are also set if OIDCStorageProviderS3CredentialsSecret or OIDCStorageProviderS3Credentials are set.

Cover the all Validate() OIDCStorage logic with a unit test.

Cover your change to the Build() function with a unit test for use cases involving
OIDCBucketName
OIDCBucketRegion
OIDCStorageProviderS3SecretKey
OIDCStorageProviderS3Secret
Which i.e should not build volume if OIDCStorageProviderS3Secret!=nil for any test case.

Then we follow up separately to consider having first support for platform in the install command as we did for Cluster and NodePool.

Let's make sure this make sense to @ironcladlou so we avoid making you go back and forth.

Droped oidc-storage commit, as @relyt0925 added another fix in https://github.com/openshift/hypershift/pull/965

Let's ship the NodePool change and move this discussion here https://github.com/openshift/hypershift/pull/965
/hold cancel
/lgtm


Order nodes by score?

Hi,
Thanks for a great plugin!  I'm just trying to learn how to use it still and can't seem to find a way to order my nodes based on the elasticsearch score?  For instance if I search for "javascript" in my document collection, I can't seem to find a good way to avoid sorting the results by their titles alphabetically?

Hi @pkmital,
You can order the nodes in the tab "Order by" inside the "Node" bucket.


Cache calls querying parent groups in bridge subjects

^
... and check all methods in those classes. They should be cached in the same way as local subjects.

Should fix the issue with Nucleus chat lag. Sorry it took so long.

Thank you!


TST: interpolate: use xp_assert infrastructure

Reference issue

cross-ref https://github.com/scipy/scipy/issues/21031, https://github.com/scipy/scipy/issues/21044, https://github.com/scipy/scipy/pull/21091,
What does this implement/fix?

Convert all scipy.interpolate tests to use xp_* style assertions instead of numpy.testing.assert_*.
Additional information

All remaining failures are blocked on https://github.com/scipy/scipy/issues/20959https://github.com/scipy/scipy/issues/21044

(marked as draft until we resolve gh-21044)

Thank you Lucas for the review! I believe I addressed all open comments.


fix(decl): use SetUint for open_mode uint32 field

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind documentation

/kind tests

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area commands

/area pkg

/area events

What this PR does / why we need it:
The issue can be reproduced with the following test:
tests:
  - rule: DirectoryTraversalMonitoredFileRead
    name: test2
    runner: HostRunner
    before: "echo Hi"
    steps:
      - type: syscall
        name: open
        syscall: open
        args:
          pathname: "/etc/../etc/../etc/shadow"
          flags: 0
          mode: 0644
    after: "echo Bye"

It was crashing with:
panic: reflect: call of reflect.Value.SetInt on uint32 Value

After this fix it runs successfully:
2024-11-10T23:22:23.483+0100	info	root	/Users/jose.calvo/repos/event-generator/cmd/declarative/run/run.go:221	Starting test execution...	{"testName": "test2", "testIndex": 0}
2024-11-10T23:22:23.494+0100	info	root.runner.test.script	/Users/jose.calvo/repos/event-generator/pkg/test/script/shell/shell.go:174	Script log line	{"runnerType": "HostRunner", "testName": "test2", "testIndex": 0, "type": "stdout", "line": "Hi"}
2024-11-10T23:22:23.504+0100	debug	root.runner.test	/Users/jose.calvo/repos/event-generator/pkg/test/test/test.go:142	Executed test step	{"runnerType": "HostRunner", "testName": "test2", "testIndex": 0, "stepName": "open", "stepIndex": 0}
2024-11-10T23:22:23.510+0100	debug	root.runner.test	/Users/jose.calvo/repos/event-generator/pkg/test/test/test.go:187	Executed test step cleanup	{"runnerType": "HostRunner", "testName": "test2", "testIndex": 0, "stepName": "open", "stepIndex": 0}
2024-11-10T23:22:23.511+0100	info	root.runner.test.script	/Users/jose.calvo/repos/event-generator/pkg/test/script/shell/shell.go:174	Script log line	{"runnerType": "HostRunner", "testName": "test2", "testIndex": 0, "type": "stdout", "line": "Bye"}
2024-11-10T23:22:23.514+0100	info	root	/Users/jose.calvo/repos/event-generator/cmd/declarative/run/run.go:249	Test execution completed	{"testName": "test2", "testIndex": 0}

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jacalvo
Once this PR has been reviewed and has the lgtm label, please assign alacuku for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 5936cab66bbf055ef1be4ed8ca8bed6b7c87ab20

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, jacalvo
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [alacuku]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/hold

Hey @jacalvo, thanks for the fix! Can you have a look at the linter?

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3bf6c96 fix(decl): return error if openMode is negative

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

New changes are detected. LGTM label has been removed.

/unhold

LGTM label has been added.  Git tree hash: 2147e67fb1f4e81d8aa9b8e92ee7c599fede48bb


tr_init: reset any existing r_ext_multisample as it is not implemented yet

We set some r_ext_multisample values with Unvanquished graphics preset, but the feature is not implemented yet and then the values aren't tested. It means the day we implement the feature, people may have the bad surprise of a potential performance hit because the variable may have been silently set to an high value before.
This patch ensures that any future released build of the engine will reset the cvar on user's configuration to clean-up them from random untested values.
Deleting the cvar would not reset the bad value in user's config, so if we delete the cvar today and re-add it in the future the day we implement the feature, the untested user's cvar would still be there and used.
See also https://github.com/UnvanquishedAssets/unvanquished_src.dpkdir/pull/169

What about just giving it a different name when it is implemented. The ext prefix seems meaningless and incomprehensible anyway

I assume those cvars are prefixed with _ext because at OpenGL 2.1 time they were enabling features that were only available through OpenGL extension, here it was GL_EXT_framebuffer_multisample.
We have a bunch of those OpenGL-extension-named cvars:
	extern cvar_t *r_ext_multisample;  // desired number of MSAA samples
	// …
	extern cvar_t *r_ext_occlusion_query; // these control use of specific extensions
	extern cvar_t *r_ext_draw_buffers;
	extern cvar_t *r_ext_vertex_array_object;
	extern cvar_t *r_ext_half_float_pixel;
	extern cvar_t *r_ext_texture_float;
	extern cvar_t *r_ext_texture_integer;
	extern cvar_t *r_ext_texture_rg;
	extern cvar_t *r_ext_texture_filter_anisotropic;
	extern cvar_t *r_ext_gpu_shader4;
	extern cvar_t *r_arb_buffer_storage;
	extern cvar_t *r_arb_map_buffer_range;
	extern cvar_t *r_arb_sync;
	extern cvar_t *r_arb_uniform_buffer_object;
	extern cvar_t *r_arb_texture_gather;
	extern cvar_t *r_arb_gpu_shader5;

I assume some were just booleans to enable features, while some like r_ext_multisample expected to be set to a configuration value (like sample numbers, here) as an enablement.

Yeah there are some that make sense - r_ext_texture_float, r_ext_gpu_shader4, etc. - cvars which actually control extension loading. These may be used by a developer to test compatibility with hardware that lacks the extension. But r_ext_multisample is just idiotically named. We should just delete it from the engine and next time something is implemented we will give it a non-idiotic name.

OK, I suggested that if we implement MSAA we name the cvar r_MSAA like the r_FXAA cvar we already have:

https://github.com/DaemonEngine/Daemon/issues/532#issuecomment-1369285204

Let's delete the cvar entirely.

I rewrote the PR to delete r_ext_multisample, I also deleted unused r_alphabits while I was at it (old cvar from legacy renderer).

LGTM


feat(universal): support for angular universal

Hi.
I have added support for the compilation in Universal Angular, this error is referring to
https://github.com/angular/material2/issues/306

The date picker doesn't close after this commit @nadim500


fix: check has_min_max_set before invoking min()/max()

Which issue does this PR close?

Closes #6091.
Rationale for this change
When column is null in parquet,the ValueStatistics's min max will be set None,so if we call ValueStatistics.min()/max() directly, the program will panic

What changes are included in this PR?
use ValueStatistics.has_min_max_set() to check before invoking min/max

Are there any user-facing changes?
No

I think I see the issue and this PR makes sense. Thank you. I still think we need to add test coverage
Perhaps we can add something here https://github.com/apache/arrow-rs/blob/9be0eb530de85a68358dc31c146f71ccb97739ca/parquet/src/file/metadata/mod.rs#L1288-L1287
Here is an issue that tracks making this API less easy to misuse: https://github.com/apache/arrow-rs/issues/6093

I add test in https://github.com/apache/arrow-rs/blob/9be0eb530de85a68358dc31c146f71ccb97739ca/parquet/src/file/metadata/mod.rs#L1288-L1287, i check memory with and without statistics. Please review it @alamb

This test seems odd. In the code, I noticed that the heap size for types like i32 is set to 0, so I set my expected value to 1320. However, the result I got was 2024. When I reran the test, the result changed to 1320. Could you tell me what might be causing this ？@alamb

This test seems odd. In the code, I noticed that the heap size for types like i32 is set to 0, so I set my expected value to 1320. However, the result I got was 2024. When I reran the test, the result changed to 1320. Could you tell me what might be causing this ？@alamb

I think it is because the heap size includes not just the size for the Statistics but also the size for the newly added ColumnMetadata and RowGroupMetadata as well

This test seems odd. In the code, I noticed that the heap size for types like i32 is set to 0, so I set my expected value to 1320. However, the result I got was 2024. When I reran the test, the result changed to 1320. Could you tell me what might be causing this ？@alamb

I think it is because the heap size includes not just the size for the Statistics but also the size for the newly added ColumnMetadata and RowGroupMetadata as well

I got it, since all checks in CI are passed, can this PR be merged into main？

Thanks again @Fischer0522


docs: don't blow away existing query string

See comments in diff - I ran across this and it took me a while to work out why my client side code worked, but the server didn't. It was because I didn't realise that .render's 3rd arg was the query object, so it was losing the actual query string.

Good catch!


feat!: Nymlab Prop31

This PR is for the first phase for Prop31 which has the changes connecting with the resource module via IBC.
This branch can be compiled to the v2.0.0-rc2 container, along with the original cheqd-node v1.4.4 used in the interchaintest.
There are a few tests in the interchaintest

simple both chain start
upgrade test from v1 - v2
using v2 and connecting with juno over ibc to communicate with the vectis-ssi contract
e2e test where we start with v1, create resource, upgrade to v2, get that resource over IBC on another chain with the vectis-ssi contract

The interchain has dependency conflicts with v1.4.4 of the cheqd node and therefore currently it is in a separate repo, the directory organisation will be worked out with the maintainers.
We look forward to getting this merged!

Waiting on merging the conflict resolution PR https://github.com/nymlab/cheqd-node/pull/1, before proceeding with further modifications.


Performance Test Failures when VCS Branch Name is too long

When the VCS branch name is too long, the performance tests fail because they can't put the information into the database.
https://ge.gradle.org/s/hwpbj4l6znanm/tests/:performance:bigCppAppPerformanceTest/org.gradle.performance.regression.nativeplatform.NativeBuildPerformanceTest/assemble with header file change?anchor=e30&focused-exception-line=0-1-0#1
This happened because dependabot generates some insanely long branch names.

@JLLeitschuh I don't think we should fix this on our side. Why are we running performance tests on those PRs? I think those individual PRs should not be merged but we should create one PR which replaces all usages of the old JUnit version by a newer one if it makes sense. And if you really want to build this PR, then build the pull/<PR number>/head branch on TC.

@big-guy and I just ignored the performance failures and merged anyway. Since there are usually only 1-2 PRs ever generated at a time, most of the time merging them together doesn't make sense.


bug: wrong ionic apk build --prod after update

i run this command
ionic cordova build android --prod --release
but my apk build  in
platforms\android\app\build\outputs\apk\debug
but before update ionic my apk build in
platforms\android\app\build\outputs\apk\release
my use release command but apk build in debug folder

ionic cordova build android --release --prod


Create a PopularDishCard component

[ ] Create a PopularDishCard component in the atoms folder
[ ] It has to receive image and link props
[ ] It should match the design

i will take this


[SPARK-21504] [SQL] Add spark version info into table metadata

What changes were proposed in this pull request?
This PR is to add the spark version info in the table metadata. When creating the table, this value is assigned. It can help users find which version of Spark was used to create the table.
How was this patch tested?
N/A

Test build #79853 has started for PR 18709 at commit ccbd3a9.

cc @cloud-fan

Test build #79853 has finished for PR 18709 at commit ccbd3a9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79853/
Test FAILed.

"Create Version" isn't a good user facing description. It'd make more sense to just say "Created by Spark xxx"

Test build #79893 has started for PR 18709 at commit 4c511c3.

Test build #79893 has finished for PR 18709 at commit 4c511c3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79893/
Test FAILed.

Test build #79896 has started for PR 18709 at commit 9fba6db.

Test build #79896 has finished for PR 18709 at commit 9fba6db.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79896/
Test PASSed.

LGTM except one comment.

Test build #79959 has started for PR 18709 at commit 4e71b66.

Test build #79959 has finished for PR 18709 at commit 4e71b66.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79959/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #79967 has started for PR 18709 at commit 4e71b66.

Test build #79967 has finished for PR 18709 at commit 4e71b66.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79967/
Test FAILed.

Test build #80398 has started for PR 18709 at commit 5b76403.

Test build #80398 has finished for PR 18709 at commit 5b76403.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80398/
Test FAILed.

Merged build finished. Test FAILed.

Test build #80410 has started for PR 18709 at commit 9d7c577.

Test build #80410 has finished for PR 18709 at commit 9d7c577.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80410/
Test PASSed.

Merged build finished. Test PASSed.

LGTM

Test build #80445 has started for PR 18709 at commit f5a26cc.

Test build #80445 has finished for PR 18709 at commit f5a26cc.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80445/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #80447 has started for PR 18709 at commit f5a26cc.

Test build #80447 has finished for PR 18709 at commit f5a26cc.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80447/
Test FAILed.

retest this please

Test build #80452 has started for PR 18709 at commit f5a26cc.

Test build #80452 has finished for PR 18709 at commit f5a26cc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80452/
Test PASSed.

Thanks! Merging to master.


sub partitions

The current implementation didn't offer sub partition support (customer_id, fund_family_id). This pr adds sub partition support for LIST partitions.

Adding the ability to create sub partitions via migrations (PostgresAddListSubPartition)
Updated the schema manager to correctly create the partitioned table with the appropriate unique constraint (id, customer_id, fund_family_id)
fixed some tests

Yea something like that. Rather than dural writes i think we'll just have a formal maintenance window where we stop writes to the system(tbd on that mechanism) do the migration then enable writes.


Pretrained weights

A great job.
Will you release pre training weights?

Thanks! Yes, link is in the README now.


Unable to resolve './' paths

In my code... as an example, I have the following directory structure
|-app
...
    |- Home.jsx
    |- index.js
    |- Test.jsx

inside the index.js, I have the following as barrel exports
// index.js

export * from './Home';
export * from './Test';

inside the Home.jsx I have the following test code
// Home.jsx
import React from 'react';
import { Test } from './';

export class Home extends React.Component {
    render() {
        return (

                <Test />

        );
    }
}

inside my Test.jsx I have the following code
import React from 'react';

export class Test extends React.Component {
    render() {
        return
This is a test element
;
    }
}

In development, when I run, there was no problem. But in production, the component is not rendered. Upon changing the import from './' to point to the file, i.e. './Test', it started working. Is there any reason why this is so?

Any updates on this?


shared projects not showing up on profile page

for a project that's already been created, if it's edited and someone is added, it is not found on the other person's project page

Can't reproduce


supported language list of BGE-M3

Hi, what languages is BGE-M3 supported ?
Could you please provide the a list of supported languages? It seems that the paper does not mention it.
Thanks

Hello, @yanfan0531! For the languages included in MIRACL, MKQA and MLDR, BGE-M3 shows excellent performance. The list of languages (merged from MIRACL, MKQA and MLDR): ['ar', 'bn', 'da', 'de', 'en', 'es', 'fa', 'fi', 'fr', 'he', 'hi', 'hu', 'id', 'it', 'ja', 'km', 'ko', 'ms', 'nl', 'no', 'pl', 'pt',  'ru', 'sv', 'sw', 'te', 'th', 'tr', 'vi', 'yo', 'zh', 'zh_cn', 'zh_hk', 'zh_tw'].
However, as shown in the Limitations section of our paper, the potential variations in the performance of BGE-M3 across different languages are not thoroughly discussed. If you want to know all languages included in the training data of BGE-M3, you can refer to the individual datasets to access all languages. For example, the list of languages for multilingual CC-News is available here.


Subtitles are not working in HLS-Safari with src mode

Have you read the FAQ and checked for duplicate open issues? Yes
What version of Shaka Player are you using? master
Can you reproduce the issue with our latest release version? No, because the regression is not in any release yet
Can you reproduce the issue with the latest code from master? Yes
Are you using the demo app or your own custom app?  Demo
What browser and OS are you using?
Safari 13.1 macOS 10.15.4 and iPadOS 13.4
What are the manifest and license server URIs?
https://storage.googleapis.com/shaka-demo-assets/angel-one-hls/hls.m3u8
What did you do?

Load the previous stream
What did you expect to happen?
The subtitles are shown in the UI
What actually happened?

The subtitle are not shown due a regression in https://github.com/google/shaka-player/commit/ad3d4604af69d70855fd80bbdc2fdf42c62370f4
Example in demo app: https://nightly-dot-shaka-player-demo.appspot.com/demo/#audiolang=es;textlang=es;uilang=es;asset=https://storage.googleapis.com/shaka-demo-assets/angel-one-hls/hls.m3u8;panel=ALL_CONTENT;build=uncompiled

Some additional info:
In getTextTracks the tracks with mode disabled are filtered, https://github.com/google/shaka-player/blob/master/lib/player.js#L2858-L2861
In selectTextTrack other tracks are configured with mode disabled https://github.com/google/shaka-player/blob/master/lib/player.js#L2904-L2914

My fix for #2516 is causing this issue, so I'm going to revert that change and reopen that issue.
Thanks for the detailed report!
As an aside, I think we need to improve test coverage for native HLS on Safari.  For that, we'll need to use real content URIs like the one in this issue, because we can't use locally-generated or fake content in a non-MediaSource playback.


Enhance RCE Challenge

As a juice shop user I want to see realistic scenarios, therefore the Remote Code Execution examples are not sufficient.
A DoS is not the impact I would like to show for a Remote Code Execution Vulnerability.
To show a real Remote Code Execution, I removed the sandbox in b2bOrder.js (see bottom of this issue).
I would like to have a RCE-Challenge in which the attacker can copy a file (e.g. /etc/passwd to juice-shop/ftp).
I would like to allow fs inside the sandbox. This will lead to a more dangerous public juice-shop instance. In addition, the Dockerfile needs to be hardened to reduce possible impact. I recommend to run nodejs as a user (by using USER in Dockerfile). Is that measure enough to allow fs inside of the sandbox?
Here is my very open RCE (which needs to be less open):
diff --git a/routes/b2bOrder.js b/routes/b2bOrder.js
index 5f8d65a6..7d683146 100644
--- a/routes/b2bOrder.js
+++ b/routes/b2bOrder.js
@@ -10,7 +10,7 @@ module.exports = function b2bOrder () {
     try {
       const sandbox = { safeEval, orderLinesData }
       vm.createContext(sandbox)
-      vm.runInContext('safeEval(orderLinesData)', sandbox, { timeout: 2000 })
+      eval(orderLinesData); //', sandbox, { timeout: 2000 })
       res.json({ cid: body.cid, orderNo: uniqueOrderNumber(), paymentDue: dateTwoWeeksFromNow() })
     } catch (err) {
       if (err.message === 'Script execution timed out.') {

No sandbox means people can just grab the server process and stop it, so it'd be a real DoS... Best check the original issue on GitHub where we played around with it for a while until it finally was working...

Maybe my question is not clear enough...
In case I can introduce fs into the sandbox, is it acceptable to use the sandbox and allow fs?

Ah, ok that might be fine, I guess...
Am 25. Mai 2018 14:18:01 MESZ schrieb Timo Pagel<EMAIL_ADDRESS>
Maybe my question is not clear enough...
In case I can introduce fs into the sandbox, is it acceptable to use
the sandbox and allow fs?
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/bkimminich/juice-shop/issues/571#issuecomment-392037053

Close, no time.


Allow resolving enso:// URIs in Data.read and other places

Pull Request Description

Implements the core parts of #9048
Currently the path resolution is done by resolving each segment, one by one - requiring as many API calls as there are segments in the path.

This should be replaced in a followup PR, once https://github.com/enso-org/cloud-v2/issues/899 is implemented.

Important Notes

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[ ] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

Sorry for pinging unrelated reviewers - GitHub did this automatically when changing PR's base branches.


Change loglevel to reduce logging noise during training.

Very noisy logging from dvc_studio_client/post_live_metrics.py#L169 during training. Im training a model with pytorch lightning but I believe that this issue would be valid for most ML frameworks.

I suggest the loglevel for this line should be changed to DEBUG.
logger.debug(f"post_studio_live_metrics `{event_type=}`")

I have a branch with this change but I'm not allowed to push it, otherwise I would have made a PR :)

Hi @ludjac ! Thanks for the report, I will make a release with the changes.
For the record, you should be able to control the level via env var:
export DVC_STUDIO_CLIENT_LOGLEVEL="DEBUG"

That was quick! Thanks :)


Fix UBI version skew

The Go 1.22 builder image is built with UBI9, so passing the binary to a UBI8 image with CGO enabled is broken.

/lgtm

/approve


Is my account free

I'm new in AWS, and opened a free account to start with.
Now, I added a new Amplify App and connected it to BitBucket.
I have two questions:

I want to add to AWS only part of the branch in BitBucket, is that possible?
How could I make sure that my account is still free with the things I added?

Hi @TYakob  👋🏽 thanks for raising this question.

With AWS Amplify you can host a specific branch in you repository. When you host an app via the AWS console, there will be a dropdown menu under *Branch where you can specify which branch you would like to host.
With Amplify Hosting- Free tier you get:

1,000 build minutes per month
5 GB stored per month
15 GB served per month.

Please see the Amplify Pricing Page for more information: https://aws.amazon.com/amplify/pricing/?nc=sn&loc=4

Hi,
Thanks for your email,
I have some questions - I'll be glad if you could help me:

I set up a free account and in the bills page I see that I'm charged for
"Elastic Compute Cloud".
Can you tell me what it is getting charged for? I thought a free tier is
free.
I uploaded a static website on s3 that sends a lot of requests - what is
the cheapest plan to choose for website that sends a lot of api requests,
and how much would I be charged per request?

Thank you so much for your help
On Wed, Jul 6, 2022 at 10:00 PM hloriana @.***> wrote:

Hi @TYakob https://github.com/TYakob 👋🏽 thanks for raising this
question.

With AWS Amplify you can host a specific branch in you repository.
When you host an app via the AWS console, there will be a dropdown menu
under *Branch where you can specify which branch you would like to
host.
With Amplify Hosting- Free tier you get:

1,000 build minutes per month
5 GB stored per month
15 GB served per month.

Please see the Amplify Pricing Page for more information:
https://aws.amazon.com/amplify/pricing/?nc=sn&loc=4
—
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-hosting/issues/2848#issuecomment-1176569480,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYH5OTDMMZPFNNGEU7JYSMTVSXJWFANCNFSM52W44GDQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


feat(rules): add tslint/newline-per-chained-call

This rule was introduced in tslint 5.9.0, but I forgot to add it in #92. 😅

Sorry for the extremely late review, great work @ikatyang !!! Thanks a lot!


svg files should be either shown as normal file or have appropriate icon to populate the area

rather than a big empty space

The faulty svg event: https://matrix.to/#/!zOmsiVucpWbRRDjSwe:matrix.org/$14803589371313093pdwXF:matrix.org

the solution to this is to thumbnail them clientside on the sending client, i suspect.

These do show up as just a file now which matches what RIot Web does.


Updating Date Progress app to use color functions and added color schema

@possan I've updated your app to utilize color functions that can dynamically adjust the color rather than hard coding the colors (as I suggested in https://github.com/tidbyt/community/issues/41, it would be sweet if there was a global color library that could be used for this purpose).
Anyway, this PR gives users the ability to choose colors for each of the progress bars for a bit more personalization. I haven't been able to test it with the schema, but I'm pretty sure I got it all right.

Hi @joeyhoer. Thanks for the contribution!
Looks like there are two things that need to be fixed to pass the tests:

[ ] Run make format to fix formatting.
[ ] Fix the bug here: https://github.com/tidbyt/community/runs/5353499434?check_suite_focus=true#step:5:56

@betterengineering @rohansingh Just a heads up, this has been updated!


New DeFiChain Logo

DeFiChain-Logo Files-112022.zip
I am the designer of this logo and I would like to contribute this logo to DeFiChain, DeFiChain community & The DeFiChain Foundation to be released under the Creative Commons Zero (CC0) license. https://creativecommons.org/publicdomain/zero/1.0/

Thank you @andyfasch for your contribution.

My pleasure :) @uzyn . Please consider that the brand mark (jelly) was also improved (lines, corners, spacing) it is very subtle, but that was the goal.

That is super helpful. Thank you

why did u lose the dots of the "i"? the "f" and "i" look very free font like. i am not a fan of this – sorry to say. My bad I havent seen it earlier.