Each instance of Spring Auth Server exposes its own JWKS information

When running multiple instances of the Spring Authorization Server behind a gateway/load balancer, the resource servers can't always authenticate. This is because the resource servers only have knowledge of the well known configuration endpoint of one of the instances, not all, as a call to the JWKS endpoint will return only the key information known to that instance of Spring Auth Server. This sometimes prevents the resource server from getting the correct key to decode the JWT token.
I would expect some mechanism to coordinate the well known configuration provided by multiple instances (perhaps something similar to session sharing using Redis?).
Please note that I found a similar query here

@adamleantech I'm going to close this as this is a question that should be asked on Stack Overflow. We prefer to use GitHub issues only for bugs and enhancements.
Furthermore, this appears to be more of a configuration issue on the resource server side so that it can support multiple authorization servers. If this is the case, then this is a Spring Security configuration. Please ses the ref doc.

thanks for pointing me in the direction of the docs.  Would be helpful if you could answer the SO question that I linked 🙏


Updating lambda stopped working with "Code storage limit exceeded"

Context
Running latest zappa in python 3.8 context. slim_handler set to true.
Expected Behavior
Lambda should update with new code
Actual Behavior
Lambda fails to update due to "Code storage limit exceeded" exception.
Zappa has been running great for almost a year now. It even update successfully multiple times earlier today. Then it stopped working. I'm using the slim handler and the code is only 60mb zipped so I don't know why this just started failing. Here's the output:
Packaging project as zip.
Uploading yearend-dev-1597190872.tar.gz (56.3MiB)..
Uploading handler_yearend-dev-1597190947.zip (12.4MiB)..
Updating Lambda function code..
Oh no! An error occurred! :(
==============
==============
Need help? Found a bug? Let us know! :D
File bug reports on GitHub here: https://github.com/Miserlou/Zappa
And join our Slack channel here: https://zappateam.slack.com
Love!,
 ~ Team Zappa!
Traceback (most recent call last):
  File "/var/lang/lib/python3.8/site-packages/zappa/cli.py", line 2778, in handle
    sys.exit(cli.handle())
  File "/var/lang/lib/python3.8/site-packages/zappa/cli.py", line 512, in handle
    self.dispatch_command(self.command, stage)
  File "/var/lang/lib/python3.8/site-packages/zappa/cli.py", line 559, in dispatch_command
    self.update(self.vargs['zip'], self.vargs['no_upload'])
  File "/var/lang/lib/python3.8/site-packages/zappa/cli.py", line 961, in update
    self.lambda_arn = self.zappa.update_lambda_function(**kwargs)
  File "/var/lang/lib/python3.8/site-packages/zappa/core.py", line 1114, in update_lambda_function
    response = self.lambda_client.update_function_code(**kwargs)
  File "/var/lang/lib/python3.8/site-packages/botocore/client.py", line 316, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/var/lang/lib/python3.8/site-packages/botocore/client.py", line 635, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.errorfactory.CodeStorageExceededException: An error occurred (CodeStorageExceededException) when calling the UpdateFunctionCode operation: Code storage limit exceeded.

Turns out we hit the code storage limit for the region due to all the different versions (100% of 75.0 GB). I'm in the process of deleting old versions as part of our deploy cleanup scripts.

We just hit that today. Would it be worth reopening the issue so that we add a Zappa setting to prune older versions on deploy?

there's actually a setting for it already: num_retained_versions.


Fix the webhook timestamp validator

We simplify the timestamp of the webhook pelorus plugin to accept only EPOCH timestamp.
It's up to the service sending POST data to ensure timestamp is a valid format and we do not have troubles converting them from unknown data format.
Fixes: #867
Testing Instructions
Added test to capture wrong data and modify other tests to cover positive test case.
$ make unit-tests
@redhat-cop/mdt

/test 4.9-e2e-openshift

/test 4.9-e2e-openshift

/test 4.9-e2e-openshift

/hold
Need to check int / str

/unhold

/lgtm


ruby193: basic-usage fails with missing gcc

https://ci.centos.org/view/SCLo/job/SCLo-ruby193-rh-C6-x86_64/
https://ci.centos.org/view/SCLo/job/SCLo-ruby193-rh-C7-x86_64/

ruby193 basic usage test is failing to install a native extension required by activeresource, as gcc isn't present on a base installation.  It should be installed first, or simplified to install a gem without native extensions.

++ scl enable ruby193 -- ruby -e 'puts '\''Hello World'\'''
+ out='Hello World'
+ '[' 'Hello World' '!=' 'Hello World' ']'
+ scl enable ruby193 -- gem install activeresource
ERROR:  Error installing activeresource:
	ERROR: Failed to build gem native extension.

        /opt/rh/ruby193/root/usr/bin/ruby extconf.rb
creating Makefile

make
gcc -I. -I/opt/rh/ruby193/root/usr/include/x86_64-linux -I/opt/rh/ruby193/root/usr/include/ruby/backward -I/opt/rh/ruby193/root/usr/include -I. -DJSON_GENERATOR    -fPIC -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -mtune=generic -fPIC -m64 -o generator.o -c generator.c
make: gcc: Command not found
make: *** [generator.o] Error 127

Gem files will remain installed in /opt/rh/ruby193/root/usr/local/share/gems/gems/json-1.8.3 for inspection.
Results logged to /opt/rh/ruby193/root/usr/local/share/gems/gems/json-1.8.3/ext/json/ext/generator/gem_make.out
+ exit_fail 'gem activeresource couldn'\''t be installed'
+ echo -n '[FAIL] '
+ echo gem activeresource 'couldn'\''t' be installed
+ exit 1

Fixed by a196f9f0f0d5f4279117c4d4c2aaa485c35fb546.


Adding minified files to dist packages

The "dist" bundle packages (e.g. https://www.npmjs.com/package/plotly.js-dist) currently only include un-minified JavaScript. This PR is to include the minified version of the same "dist" file alongside this in the package.
It is common to import packages via npm but not have a minification step in your own build process. It is therefore helpful to have the minified version of the files included in the package.

@alexcjohnson @etpinard @antoinerg @archmoj Wondered if you’d take a look at this PR to include minified files in the dist packages. See also this comment here https://github.com/scijs/cwise/pull/25#issuecomment-515100125

Thanks very much for making a PR @cjwainwright. Your patch looks good.
Now, here are the :+1: / :-1:
:+1:

This PR would allow users to

npm i plotly.js-*dist
use node_modules/plotly.js-*dist/plotly-*.min.js
... with no extra work

:-1:

This PR would increase the size of our plotly.js "dist" package by 30 to 50 percent (numbers taken from the plotly.js dist README) with arguably "duplicate" code.

Potential alternatives:

npm i plotly.js and use dist/plotly.min.js

but this downloads the flagged cwise package, some folks will find that bad even if they don't bundle their own code.

npm i plotly.js-*dist and minify node_modules/plotly.js-*dist/plotly-*.js

but not everyone will want to install a minifier

download the minified bundles from our CDN e.g. https://cdn.plot.ly/plotly-basic-latest.js

but some people want to use npm to install all their deps

publish "dist min" package to the npm registry, that is all our "dist" packages would have a "dist min" equivalent so that users could then e.g. npm i plotly.js-basic-dist-min

Thanks @cjwainwright for the PR.
I was wondering if we could select only a few of those partial bundles, for example plotly.js-dist & plotly.js-gl3d-dist?

Thank you for the feedback.
@etpinard Creating separate "dist min" packages sounds like the best approach, satisfying both the package size problem and allowing npm install of the min files. I can look at updating this to do that, unless you foresee any other issues with that?
@archmoj Can you explain why you would only include min files for some of the bundles? Would creating separate min packages be a good alternative from your perspective.

The debate is still on between

adding min.js files to the current "dist" packages, and
publishing new "dist min" packages

We'll make a decision between the 1.50.0 release, which is scheduled for late August.

@etpinard @archmoj Was there any decision made about distributing minified files in dist packages yet? Thanks!

@cjwainwright
You decided on this option:

publish "dist min" package to the npm registry, that is all our "dist" packages would have a "dist min" equivalent so that users could then e.g. npm i plotly.js-basic-dist-min

Would be interesting in trying to make a PR?

(and note 1.50.0 has been pushed back)

@etpinard OK, great thanks. I had already made a PR on my fork for this (#2), if you're ok with that code I can look to make it as a PR back to the plotly repository.

Thanks @cjwainwright - your patch looks good.

We should add some info about the new partial "dist min" bundles to
https://github.com/plotly/plotly.js/blob/master/dist/README.md
generated by
https://github.com/plotly/plotly.js/blob/master/tasks/stats.js
Maybe below line
https://github.com/plotly/plotly.js/blob/240334eb51f9abfa0237aadcae90f1d47b10a92a/tasks/stats.js#L145
we could have:
Starting in `v1.50.0`, partial dist "min" packages are also published to npm.

and maybe below line
https://github.com/plotly/plotly.js/blob/240334eb51f9abfa0237aadcae90f1d47b10a92a/tasks/stats.js#L210
we could have
### dist min npm package (starting in `v1.50.0`)
        '',
        'Install [`' + pkgName + '-dist`](https://www.npmjs.com/package/' + pkgName + '-dist) with',
        '```',
        'npm install ' + pkgName + '-dist',
        '```',

What do you think?

@etpinard Sounds good, I can add those. I was thinking of making the wording a little more descriptive for the first part, maybe:
Starting in v1.50.0, the minified version of each partial bundle is also published to npm in a separate "dist min" package.
Does that sound ok?

Starting in v1.50.0, the minified version of each partial bundle is also published to npm in a separate "dist min" package.

Yep, that's better than my attempt. Thanks!!


Create a timeline

Add a list of all your activities, achievements, work experience. Add as much info as you can remember. In case you don't have working experience tell about your pet-projects or student projects. Don't be shy :)

Unfortunately, I cannot remember any crucial achievements, events in my life and so on. Also, I don't have any work experience, so there is no information I can add suitable for this section(


Adding Belgrade as submodule

Awesome ! 😍
I'll merge it right after fixing the last bits of code (scripts/map) where variables are related to Brussels !

Now that I have updated the scripts, could you run it again ?
Just to be sure we have the last version of the structure before merging !
Thanks A LOT !

You'll also have to add the map settings to your HTML files (see https://github.com/openknowledgebe/equalstreetnames/issues/20#issuecomment-620188135)

I checked and everything is fine. I will send PR to add custom map style, but I don't see any other problem

Good idea to add the style as a setting too !
I'll make the update !

Map style is now configurable for your files !
You just have to add the following to your HTML files (with the correct settings for Belgrade, of course):
<script>
  app.center = [4.3651, 50.8355];
  app.zoom = 11;
  app.bbox = [4.243544, 50.763726, 4.482277, 50.913384];
  app.countries = "be";
  app.style = "mapbox://styles/mapbox/dark-v10";
  app.init();
</script>

(see en/index.html)

Confirming everything works

Awesome !
Can you sync your PR so it's using commit https://github.com/stalker314314/equalstreetnames-belgrade/commit/46e40f3578d526d03736e26e73beaf07750b5d79 (instead of https://github.com/stalker314314/equalstreetnames-belgrade/commit/9cae3f43ac92df2cbf6d2f566b7fa619dde4440d) ?
I'll merge the PR once it's synced! 🚀 🍾

Awesome ! Thank you so much for your help @stalker314314 !


set backend attribute to indicate pdf

Currently the value of the {backend} attribute is html5.
I propose it be either pdf or html or html-pdf or html5-pdf.
Although the toolchain involves the html, the end user is targetting pdf and may have logic (as I do) which seeks to deactivate features or modify the document in response to that.

Currently the "backend" is the converter from AsciiDoc to HTML, and you could use different converters, for example html5s, the semantic HTML converter.
For now I recommend that you add your own attribute on the command line/build process like this:
asciidoctor-pdf -a testattr=abc basic-example.adoc
Looking forward (and to be discussed) the appropriate attribute I'd see is {env}. You can use it or {env-github} today to find out if your source is rendered for example on GitHub for preview:
ifdef::env-github[]
:imagesdir: foo/
endif::[]

I wonder if this this should be pdfjs or pdf.

I was really confused with the backend and converter terminology:

A converter is the software component in Asciidoctor that performs conversion from AsciiDoc to a publishable format. A backend is an alias—kind of like a keyword—that identifies the converter to use.
The backend expresses an intent to transform to a certain format (e.g., html5 for HTML5). But it’s more than just being shorter to type. Multiple converters can bind to (i.e., stake claim to) the same backend in order to provide different approaches for performing that conversion. For example, the backend pdf could activate Asciidoctor PDF, but it’s also possible it means a different implementation. The last converter bound to a backend wins.

https://asciidoctor.org/docs/faq/#converter-vs-backend
So if we follow this principle we should use pdf.
I'm a little reluctant to do that because some users are using the backend in conditional directives.

Currently the "backend" is the converter from AsciiDoc to HTML, and you could use different converters, for example html5s, the semantic HTML converter.

Yes, even though, I think that the backend of the semantic HTML converter should be html5 (not html5s).

Looking forward (and to be discussed) the appropriate attribute I'd see is {env}. You can use it or {env-github} today to find out if your source is rendered for example on GitHub for preview:

I agree.
Ideally you shouldn't use the backend in a conditional block. I wonder if the converter name should be available via an AsciiDoc attribute...
The reveal.js converter is using the following:

backend: revealjs (should be reveal.js)
basebackend: html

I wonder if this this should be pdfjs or pdf.

I think js suffix/prefix is not relevant, we should use either html or web to be consistent with the future new name of this project: https://github.com/Mogztter/asciidoctor-pdf.js/issues/125#issuecomment-555103151
ifdef::env-web-pdf[]
:imagesdir: foo/
endif::[]

In summary:

backend=pdf
basebackend=html (not sure about this one)
outfilesuffix=.pdf
filetype=pdf
env-web-pdf
env=web-pdf

@mojavelinux Thoughts?

For me backend is what I pass on to the command line of Asciidoctor using -b command line option.
Therefore I would keep html5 (or html5s if someone chooses a different converter) for backend.
I'm ok with outfilesuffix, filetype, env-web-pdf and env. I can't think of a situation where I would use basebackend

I'll admit, this one is tricky.
The backend is strictly intended for converter resolution.
The idea of basebackend is to let you know what format inline content is in (for extensions). Although it's a little sketchy, Asciidoctor PDF uses pseudo-HTML for inline content, which is why it sets basebackend to html.
Since this conversion relies on the HTML converter to run first, I'm inclined to say the backend should remain unchanged or be html-pdf. You could also consider introducing a new attribute to give an indication that pdf is the intended output format.

The backend is strictly intended for converter resolution.

Ok.

Since this conversion relies on the HTML converter to run first, I'm inclined to say the backend should remain unchanged or be html-pdf.

At first, I thought that the conversion to HTML was just an implementation detail. An intermediate step to produce a PDF. But now I don't think it's true. The conversion to HTML is a central piece of this converter.
Why not web-pdf? I think it's important to be consistent in the naming, so if we rename this project asciidoctor-web-pdf then I think the backend should be web-pdf.
I also think that html-pdf can be confusing because both html and pdf are output formats.

You could also consider introducing a new attribute to give an indication that pdf is the intended output format.

outfileformat=pdf? outfilemimetype=application/pdf? I don't use separators because outfilesuffix does not use separators but arguably it's hard to read...
What do you think about env-web-pdf and env=web-pdf?

I will move forward and add env-web-pdf and env=web-pdf as they can be useful.

env-web-pdf and env=web-pdf attributes were added in: https://github.com/Mogztter/asciidoctor-web-pdf/commit/fa35c36f3525c4b43c2519b8c002e90f4b5ad343
Please open a new issue if this addition is not enough.

This isn't quite the right use of env. The env is meant to indicate which environment Asciidoctor is being integrated into. For example, if I were to use this converter in Antora, then the env should be Antora, not web-pdf. The "web-pdf" tells me what the converter is, not the environment. So now we have a conflict.
I'm not sure I understand why backend=web-pdf and basebackend=html isn't enough. That tells you that the target format is PDF (specifically generated using the web stack) and that underneath it is using the HTML format.
I'm open to exploring new attributes if that doesn't sufficiently communicate the method of conversion.

backend=web-pdf (I understand if you want this to be pdf instead)
basebackend=html
outfilesuffix=.pdf
filetype=pdf

We could consider a new attribute to qualify the variation of the backend. Perhaps one of these:

converter=web-pdf (where backend=pdf; a converter satisfies a request for a backend)
pdf-generator=web (as opposed to prawn)

Regardless, this converter should not set "env".

This isn't quite the right use of env. The env attribute is meant to indicate which environment Asciidoctor is being integrated into. For example, if I were to use this converter in Antora, then the env should be antora, not web-pdf. The "web-pdf" value tells me what the converter is, not the environment. So now we have a conflict.

I see... 🤔

I'm not sure I understand why backend=web-pdf and basebackend=html isn't enough. That tells you that the target format is PDF (specifically generated using the web stack) and that underneath it is using the HTML format.

The value web-pdf is consistent with what we have today.
For instance, the backend for the reveal.js converter is revealjs. If we follow the same rule, then the value of the backend attribute for the Google Slides converter should be googleslides (or google-slides).
But, unless I'm mistaken, the value should be slides or presentation?
Otherwise, the value of the backend attribute is really the name of the converter.
Recently, I was asked to hide chunks of text when producing slides.
My recommendation was to avoid using "backend" because it's too specific.
If I have more than one converter producing slides/presentations then I will need to do something like:
ifndef::backend-revealjs+backend-googleslides[Not producing a reveal.js or Google Slides presentation.]

What is the recommendation in this case?

backend=web-pdf (I understand if you want this to be pdf instead)
basebackend=html
outfilesuffix=.pdf
filetype=pdf

We could consider a new attribute to qualify the variation of the backend (in the case backend=pdf). Perhaps one of these:

converter=web-pdf (remember that a converter satisfies a request for a backend)
pdf-generator=web (as opposed to prawn)

I like this proposal because we provide exhaustive information.

unless I'm mistaken, the value should be slides or presentation? Otherwise, the value of the backend attribute is really the name of the converter.

Correct, that's really the idea behind it. Which is why I like better the idea of the converter setting an additional attribute to self-identify.

converter=web-pdf

This could even be backend-converter=web-pdf (a readonly attribute)

As a user, I need to make the difference betwen both the engine used and the format generated,
the current value of  the "backend" attribute doesn't allow me to make the difference between html5 generated by asciidoctor and pdf generated by  asciidoctor-web-pdf, because in both case the value is "html5".
My asciidoc files thus depends on external attributes (passed from the command-line)
I would expect the backend value to be one of asciidoctor, asciidoctor-pdf, asciidoctor-web-pdf, asciidoctor-fopub and another attribute like "output-format"

I don't think resolution is obvious, otherwise we would have long since wrapped this up.
The base backend is html, but the converter goes on to subsequently convert that output to yet another format (PDF). So the basebackend has to be set at a minimum. (If you change the basebackend from html, certain features stop working, and that's not conducive for users). It's debatable whether the backend should be changed from html5 to something else too. If you do that, you lose some information tools may rely on. After all, the converter for the html5 backend is being used.
I put forth my suggestions in https://github.com/Mogztter/asciidoctor-web-pdf/issues/129#issuecomment-683349998. Another idea would be backend-variant=web-pdf. We need something to express that it is the html5 backend, but it is being used for a different purpose. (As I mentioned, this is not the right use case for env).
I also just remembered we had been discussing something like this in https://github.com/asciidoctor/asciidoctor/issues/3116.

Another attribute like "output-format" would tell if the output will be epub3, html or pdf.

That's what 'filetype' is.

ok thanks, so if :backend: is html5 and :filetype: is pdf I can infer that the engine is asciidoctor-web-pdf ;-)

That's not quite what I'm saying. If you look at my proposal above and Guillaume's reply that followed it, I think we agree it should be backend=web-pdf basebackend=html filetype=pdf. However, if we decided for some reason not to set backend, then you would look for backend-converter to have the value web-pdf. But that's not an attribute we have ever had in Asciidoctor, so I'm less comfortable with it.

so if :backend: is html5 and :filetype: is pdf,

Let's just say you wanted to take this approach, except you check basebackend=html and filetype=pdf. Then you would only know that Asciidoctor is producing a PDF with an HTML-based PDF converter. Asciidoctor PDF fits that criteria, so it won't tell you you are using Asciidoctor Web PDF. That's an argument for why backend should be set to web-pdf. Because only then does it uniquely identify which converter is being used. However, it violates the design of the backend, which is that you should not care which converter is registered for it.  That makes me think that, if you absolutely must know which converter it is, then we really should have a converter attribute that provides this information.
In light of that, I'd like to revise my proposal:

backend=pdf
basebackend=html
filetype=pdf
converter=web-pdf
pdf-generator=browser (or puppeteer)

Like I said, this decision isn't easy.

In my specific case I need to know what converter is used when features are differently implemented.
This is the case for the [index],
I need to print an alternative when not available like in web.pdf .


Multicolumn ANN indexes on a hypertable

Hi! I'm wanting to perform ANN search on time-series data, so I'm trying to index my tables on multiple columns: the embedding column and the timestamp column, in order to optimally take advantage of timescale hypertable functionality. I'm not able to find any documentation on how to do this.
e.g. I would like something like
CREATE INDEX my_index ON my_hypertable USING diskann (timestamp, embedding);

It seems like pgvector supports conditional indexing only (e.g. CREATE INDEX ON items USING hnsw (embedding vector_l2_ops) WHERE (category_id = 123);) but for obvious reasons this isn't available for time-based partitions.
It would be a major advantage for us to be able to query on long-term timeseries data, so we'd love to see this added if it's not already available. If it isn't, is this functionality possible or on the roadmap as an enhancement at some point?

@hamishc Vector indexes cannot be multi-column right now. What you want to do instead is use time-based table partitioning using Timescale's hypertables and then have a regular diskann column on the embedding column. That way the query executions will be approximately as follows:

the query planner will exclude any chunks (partitions) that cannot have any data based on the time-based constraints in your query
for each chunk that matched, the index on that chunk will get the rows with the closest vectors
the executor will then filter out any rows that don't match the time filter

Step 1 makes sure most of the irrelevant data based on the time constraints are thrown away quickly. Step 2 uses the full power of the vector index. Step 3 does the final cleanup.

Oh, so hypertables don't actually need indexes on the time column in order to use the partitions? When I created the hypertable I ran it with create_default_indexes => FALSE - so I assumed any indexing had to be on both the desired column and the time column (this is what the timescale docs seem to suggest).
I've validated with the query planner that it's using the indexes and only running on the requested partition, so it's working either way! Thanks for your help!


FIX get_n_split

Fixes math for get_n_split

@glemaitre these changes will fix the tests and docstring validations for #23780.

The error was legit. I lower the number of max_train_size. I think that something that we are expecting is to have training split with the same number of samples which is the current behaviour.

**glemaitre ** commented Nov 10, 2022

If this is the case then we should rename max_train_size to train_size since the variable does not have a bounding effect and instead sets the exact train size for 'walk_forward'.

I assume that if it was called max_train_size, it should have an effect in the original setting.

Oh I see, then just a note in the parameter description will do.

Will close this since it has been resolved through your PR.


Front-end: implement walk-through animations

Clicking on a "help" button should start a walk-through that selects & highlights objects on the time-scaled tree and cluster SVGs with tool-tips, and text in the side bar.  User should be able to exit the walkthrough at any time (returning to normal interface).

@bonnielu to assess feasibility of implementing tutorials using the existing front-end code

I looked into this and found a plugin (driver.js) that will make it easier to implement a walkthrough of the website. I'm still having some difficulties trying to get it to select the specific lines and rects of the tree/beadplot but this should definitely be feasible!

I've updated the walkthrough to include snippets of text from the help manuals and have added additional highlights to a lineage, bead, and summary table. I'm still trying to get the library to work with lines right now (for highlighting the beadplot component) but will also need to work on making sure that the text can be translated when navigating to different language pages.

@bonnielu to submit PR to dev


Product Visualization (RF03) - Search bar integration with API on home page  (Issue-13)

Product Visualization (RF03) - Search bar integration with API on home page (Issue-13)
Description:
Implements complete product search flow from navigation bar to search results
Status:
Implemented search functionality with API integration and results display
Main features:

Create searchProducts API endpoint for handling search queries
Connect NavBar search input to searchResults page
Implement unified search results display
Add search query parameter routing
Set up proper header handling for API requests
Optimize data fetching in searchResults page
Style search results with consistent layout

Related commit: [126c7067a94230262074f5a2d9e421be77b679ce]


Office Documents and IE redirecting to home page.

When we are using Microsoft Office document, we may experience issues before open the page that we requested, we can be redirected to home page or error page clicking in some link inside the doc.
The Office session is independent of the Web browser session. Is there some configuration that we can use to have links inside doc works?
Steps to reproduce:

open the Office document in edit mode outside the Web browser.
Click in some link that redirect to some deep path in the site that have SSO.
Result: You will be redirect to home page.

Expected behavior:
To be redirect for the deep path that is inside the Office document
Thanks
Marcelo de Castro

https://github.com/zmartzone/mod_auth_openidc/wiki#20-why-is-my-ticket-closed-as-invalid


React Native v.0.13.1: Error building DepdendencyGraph

While updating my app to latest React Native 0.13.1 I run into following error:
Error building DepdendencyGraph:
 Error: Naming collision detected: {project-folder}/node_modules/react-native/node_modules/react-tools/src/renderers/shared/event/eventPlugins/ResponderTouchHistoryStore.js collides with {project-folder}/node_modules/react-native-location/node_modules/react-native/node_modules/react-tools/src/renderers/shared/event/eventPlugins/ResponderTouchHistoryStore.js
    at HasteMap._updateHasteMap ({project-folder}/node_modules/react-native/packager/react-packager/src/DependencyResolver/DependencyGraph/HasteMap.js:123:13)
    at {project-folder}/node_modules/react-native/packager/react-packager/src/DependencyResolver/DependencyGraph/HasteMap.js:95:28
    at tryCallOne ({project-folder}/node_modules/react-native/node_modules/promise/lib/core.js:37:12)
    at {project-folder}/node_modules/react-native/node_modules/promise/lib/core.js:103:15
    at flush ({project-folder}/node_modules/react-native/node_modules/promise/node_modules/asap/raw.js:50:29)
    at doNTCallback0 (node.js:407:9)
    at process._tickCallback (node.js:336:13)

Removing react-native folder in /node_modules/react-native-location/node_modules/ does fix this error.
Or could you update the dependency to react-native-location to latest RN  ^0.13.1, please?
[EDIT]
Using peerDependencies might be helpful, too:
// package.json
"peerDependencies": {
    "react-native": ">=0.12"
}

[/EDIT]

Issue has been fixed with #4 . Dependencies of react-native are not installed within /node_modules/react-native-location/node_modules/ anymore. I'm not sure if an upgrade of Node to v4.2.1 (from iojs-v3.3.1) helped me, too.
Anyway, Issue can be closed, thanks!


Fixed markup formatting so code displays correctly

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@nihil0 : Thanks for your contribution to the Azure documentation! The author, @spelluru, has been notified to review your proposed change.

@nihil0 - Thank you. I have just reviewed and signed of on another PR that fixed the same issue:
https://github.com/Microsoft/azure-docs/pull/1816
#please-close


When I delete uploaded files the required file check stays active

When I go to the new work screen
And I add local files
Then the check is green
And I delete all the uploaded files
Then the check is still green
The check should go back to red if I remove all files.

Pointed at 3.


dartfmt fails for  1.23.0-dev.11.5

See https://travis-ci.org/dart-lang/angular2/jobs/218587280#L276
Files are unformatted:
lib/src/common/forms/validators.dart
lib/src/compiler/provider_parser.dart
lib/src/compiler/view_compiler/view_builder.dart
lib/src/testing/internal.dart
lib/src/testing/test_injector.dart
test/meta/types_test.dart

@matanlurey @ferhatb This is fun.
Do we want to skip this until we sync Dart SDK versions internally?

I vote skip until we have consistent SDK versions.

Closing out this issue. Will open another issue to re-enable dartfmt tests

Actually, this was fix! Never mind...


Add SAML authentication and challenge

Hi!
I just read about pentesting and breaking SAML in e.g. On Breaking SAML: Be Whoever You Want to Be and thought about how nice it would be to have a challenge about e.g. signature wrapping in this awesome VWA. There are multiple free hosted test Identity Providers available such as TESTSHIB or OpenIdP which enable SAML assertions to be generated for authentication without increasing the complexity of a local installation of the juice shop unnecessarily.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Hi @bkimminich @jsuleder I have been reading about SAML. It appears to me that for implementing it (node modules like passport-saml exist), but I wasn't able to find any good resource online. Please point me to something if you know it already?
Further, the link in the description for TESTSHIB is dead and OpenIdP can be used anymore.(The use of the OpenIdP is now restricted to UNINETT, a state owned company responsible for Norway's National Research and Education Network).

Needs solution design before implementing as this is a quite "enterprisey" feature. Also: Who could the identity provider be? Would have to be something open/free obviously.


the cli parameter -d is not shown in help

We can use wt -d d:\ to open terminal in specific directory. This is not listed via wt /?

Huh. Good point.

Technically, -d is a parameter for new-tab, so it should show up under wt new-tab -?.
When no subcommand is passed to wt, then it tries new-tab by default.

We should probably clarify that second bit in the help text.

ah ok :)
The command wt new-tab -? does not work for me: it just opens new shell without help.
But this works: wt --help new-tab:


Enabling AccessLog Sampling filter results in misconfiguration failures

Bug description
Enabling AccessLog Sampling filter along with other filters results in misconfiguration failures
Expected behavior
No error
Steps to reproduce the bug
Enable accesslog sampling filter at the time of installation of Istio along with stackdriver and metadata exchange filter.
This results in misconfiguration from envoy-wasm that "stackdriver filter has been configured incorrectly"

Can you attach the SHA for istio/istio that you are using and the profile ?

@jplevyak : This is on latest branch of istio/istio(kinda any SHA from last 2 weeks for sure).
I was running using integration test framework but should repro with default profile with following values set:

"telemetry.enabled" = "true"
"telemetry.v1.enabled" = "false"
"telemetry.v2.enabled" = "true"
"telemetry.v2.stackdriver.enabled" = "true"
"telemetry.v2.stackdriver.logging" = "true"

I added following here: https://github.com/istio/istio/compare/master...gargnupur:nup_add_filter_option?expand=1

"telemetry.v2.accessLog.enabled" = "true"
"telemetry.v2.accessLog.logWindowDuration" = "43200s"

Are you using the demo app?    The applying what configuration?

How do I repro with the integration test framework ?


Use pre-message hook to change name of message

After #43 save the rebase information, we should use this to update the message appropriately. 2 rebased should be 2', etc. We should be able to look up the hash and edit the message

@jakeduo, would you like to try and take this on?


AWS ElasticCache/TLS (No cluster) - Connecting but not reading/writing

I can connect to the redis cluster with ioredis via stunnel/localhost, so there shouldn't be any security group issues..
Not running in cluster mode, just a master and two replicas.
My code:
var Redis = require('ioredis');
var redis = new Redis({
  port: 6379,
  host: 'master.master-redis.xxxxx.usw2.cache.amazonaws.com',
  redisOptions: {
    tls: {}
  }
});

redis.set('aws', 'kris');
redis.get('aws', (err, res) => {

  if (err) console.log(err);
  if (res) console.log(res);
  redis.disconnect();
});

DEBUG:
$ DEBUG=ioredis:* node redisTest.js
  ioredis:redis status[master.master-redis.xxxxx.usw2.cache.amazonaws.com:6379]: [empty] -> connecting +0ms
  ioredis:redis status[<IP_ADDRESS>:6379]: connecting -> connect +333ms
  ioredis:redis write command[<IP_ADDRESS>:6379]: 0 -> info([]) +1ms
  ioredis:redis queue command[<IP_ADDRESS>:6379]: 0 -> set([ 'aws', 'kris' ]) +5s
  ioredis:redis queue command[<IP_ADDRESS>:6379]: 0 -> get([ 'aws' ]) +2ms

(it just sits there)
Any ideas?
Thanks!

the problem here is that javascript is async, when the code runs to redis.get, there is a chance that the previous redis.set hasn't completed, and you'll get null as res, to the code will log nothing and disconnect redis connection.

There isn't any previous redis.set. I am aware of async, I get the same issue if I put the calls inside an async.waterfall to make sure the previous operation completes.

alright, then maybe you should update your code sample, it's a little misleading now


PRISM Stable Geoprocessor

tmin (minimum temperature)
tmax (maximum temperature)
ppt (precipitation)

Data acquisition is complete via Airflow.  @jeffsuperglide , can you take a look at the async-geoprocess processor that would be required for this product?

[ ] New DAG created

[ ] Deployed to develop
[ ] Deployed to stable

[ ] New Acquirables added to db migration, New Products added to db migration

[ ] Deployed to Develop
[ ] Deployed to Stable

[ ] Suite name changed / product labels changed to include early/stable

Awaiting:

Deployment of scale-out version of Airflow (USACE/cumulus#215)
develop --> stable merge of Cumulus API (USACE/cumulus-api#284)

@adamscarberry, you got it from here!

Waiting on stable airflow re-deploy by @brettpalmberg  to work out bugs with airflow causing the PRISM stable backloading to fail half the time.  Issues with S3 reading or writing as well.

Waiting on stable airflow re-deploy

In progress now.  Hoping this will be complete and stable by this afternoon 🤞

Airflow is backfilling now 👍


Add @rules_shell//shell:defs.bzl for consistency with other rules.

This is a pattern in some popular rules repositories such as rules_java, rules_cc, rules_python, and rules_rust. As a consumer it makes knowing how to load symbols less complicated as developers don't need to go look up the special cases for each rule. This would be super helpful!

The rulesets in the process of being Starlarkified are moving in the opposite direction, preferring a file-per-rule layout. This does potentially come with efficiency and maintainability gains, so I'm hesitant to introduce a catch all file at this point.
Cc @comius for his input on ruleset layout

I would ask that whatever the layout is that it at least be consistent for all rules in the bazelbuild org.

Deleting defs.bzl from rulesets that have it would be a very breaking change, so I doubt we'll get consistency in that area. According to https://docs.google.com/document/d/1L1JFgjpZ7SrBinb24DC_5nTIELeYDacikcme-YcA7xs, @rules_lang//lang:lang_library.bzl is the canonical load location for lang_library.

https://bazel.build/rules/deploying Should be updated and the rationale communicated at least to maintainers of bazelbuild repositories so there can be some consistency throughout the ecosystem.

Could you file an issue for this on the Bazel repo? This repo has very low visibility.


Are you coding to support fluffypony to siphon off some more money?

https://tinyurl.com/4adtecfv (changed link to removeddit since /r/monero mod removed to try to cover it up - maybe fluffy himself?)
Monero: BUT HE APOLOGISED TO SOME OF THEM AFTER LAUGHING AT THOSE IDIOTS!

Spam or truth? There is only one way to find out. Look into the sources yourself.

tari-project/tari#2893

tari-project/tari#2892

tari-project/tari#2859

tari-project/tari#2808

tari-project/tari#2797

tari-project/tari#2899

tari-project/tari#2898

tari-project/tari#2897

tari-project/tari#2896

tari-project/tari#2895


feature: Exposure of certain internal api's

Did you check the docs?

[X] I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.
I was reading discussion #587 and remembered i made something similar to a plugin market(not really) sometime ago for lazy.nvim. (this is just a skeleton btw:)
https://github.com/folke/lazy.nvim/assets/77913442/b836a09d-d067-453a-b135-361c2700305e
It uses database.json as the plugin store, and there is a temporary api endpoint: https://api.nvimplugnplay.repl.co/
But the problem is I havent found a way to update lazy's float window dynamically (or reload lazy, should i say).
I have read the user events section but could not make it work.
Describe the solution you'd like
Reading #587 , I thought this could be made into an external plugin.
Are there any internal APIs (functions, autocommands, variables, etc) that can help me achieve this?
Describe alternatives you've considered
None
Additional context
The database.json mentioned above is generated by scraping several sources. I believe there might be security issues in such cases but its still cool to have an installer for personal purposes.
The code I used is uploaded here: lazyn. (The code is super ugly so dont judge me lol).

I'm not exactly sure what you're asking. But lazy automatically detects changes to your plugins files if you use a plugin module. Check the section on structuring your plugins.
So after you added the new plugin in one of the specs, just run :Lazy install. No need for a restart.
If you're not really writing a spec, but are creating the specs dynamically, then you'd still have to use a spec module, and just return the correct plugins from that module.
To have lazy force-reload its specs, use require("lazy.core.plugin").load().
And again, you can then do :Lazy install after that.

A better way if you want to turn this into a real plugin would be by using import.
Your plugin, you could have lua/yourplugin/plugins.lua that checks what plugin the user added through your plugin and returns a table with the specs.
A user should then install your plugin with { "you/yourplugin", opts = {}, import = "yourplugin.plugins"}.
This will automatically included the installed plugins in the final spec.
When a user adds a plugin, you'd still have to do that load() followed by an install()

Sure, thanks for the input 👍🏻


movingAverage movingMedian very slow in cluster

These seem to re-pull the data using the _fetchWithBootstrap() function.
For a specific query that was inserted into one of our grafana dashboards, this was mind-bogglingly slow.
In our environment we have 5 storage nodes. The original data query uses a wildcard which in this case matches 1411 metrics, (which are munged then combined with averageSeries) so each query to the storage nodes returns about 282 metrics. This returns pretty quick.
Someone encapsulated one of these queries with a movingAverage(x,100). This generated an additional 1411 separate data queries to the storage nodes (logged in rendering.log) each time. As the result took more than the grafana refresh time to generate (60s - actually took >200s sometimes) and is displayed in multiple locations, something like 90% of the queries to the storage nodes ended up being this one thing, and the whole cluster responds like a slug.
We are working around it by not using movingAverage on large queries, but it wouldn't it  be better if _fetchWithBootstrap() could match the wildcard originally used?
I'm going to stare at it a bit and see if I can figure a fix, but my python foo may not be up to it.

or maybe pre-process the query to look for the need for a bootstrap and pull the correct data the first time?

this seems to apply whenever movingAverage is applies to a series that already has a function applied
for instance
movingAverage(services.real-time-bidder.pnc.*.Heap.heap.percent,11)
generates two retrievals
Thu May 19 15:40:51 2016 :: Retrieval of services.real-time-bidder.pnc..Heap.heap.percent took 0.182778
Thu May 19 15:40:52 2016 :: Retrieval of services.real-time-bidder.pnc..Heap.heap.percent took 0.130155
while
movingAverage(nonNegativeDerivative(services.real-time-bidder.pnc.*.Heap.heap.percent),11)
gets the initial wildcard, then a hit for each node, and takes an age. As most of our interesting metrics are counters that reset to zero at daemon restart, not taking nonNegativeDerivative() on them first would generate silly numbers in a movingAverage

I dug deep and I think I get it now - and I think I see the fix - and I have tested it narrowly.
It appears to be an inconsistent way that TimeSeries.pathExpression is handled.
the field is initially set in fetchData as follows:
series.pathExpression = pathExpr #hack to pass expressions through to render functions

some functions (all of the combination functions) pass this uphill nicely.
Many of the functions set it to be the same as 'name', after putting their own wrapper on name
I tweaked one of these - nonNegativeDerivative() as follows and got the problem to go away. I still get the double-tap on the storage nodes, but only double, not 300X.
as follows:
series.name = "nonNegativeDerivative(%s)" % series.name
series.pathExpression = "nonNegativeDerivative(%s)" % series.pathExpression
# series.pathExpression = series.name

The more I dig into this, the more work it seems to be to fix. It appears that the intent of pathExpression is to be able to re-pull the data with different parameters (typically different time periods). Therefor it should be consistently updated in every function but it is not.
it is initiated in fetchData, and then is rolled up through the stack of  functions.
Some function e.g. sumSeries(), derive it from the pathExpression values in the received seriesList - those seem to work correctly.
Some functions derive it from the name values (many just set it equal to name) in the received seriesList. As name can be populated with arbitrary strings, that's going to generate odd behavior in many cases and result in a pathExpression that cannot be used to re-pull the data.
Some functions e.g. maxSeries() don't update it at all so the resulting pathExpression will no generate the original result if used.
I see two approaches to fixing this:

Fix all the functions to consistently update pathExpression as it walks back up the tree. This is a lot of code, and would take quite a bit of maintenance going forward..

Top down approach. When a seriesList is passed to a function, pass the pathExpression that was used to generate it along with it. I'm not sure how to achieve this best (weak python foo), maybe a  tuple, or make seriesList a class? This would eliminate the need for every function to syntactically correctly update the pathExpression in each series. If it is a function that needs to re-piull the data, it can just pull the pathExpression out of its arguments.

Am I completely off-base with this? It's entirely possible I am missing some design history on this one.

Argh. It occurs to me that the current behaviour has some advantages.
e.g. maxSeries() does not need to add itself, if the series it is filtering are already split out with expanded pathExpressions to individual datapoints. If you time-shift you might get a different set of series from the maxSeries filter if you just used the original wildcard. Which would make that graph invalid.
Dang this is hard.

had fun digging and coding.
fixed. filed pull request
https://github.com/graphite-project/graphite-web/pull/1523
This is against 0.9.x as we are still on 0.9.15.

@arielnh56 Thank you for all of your work into this fix. Much appreciated. 🍰 💯 🍭 👍 😎


MudTextField do not working in .NET 8.0 version WebAssembly

Things to check

[X] I have searched the existing issues for this bug
[X] To rule out a caching problem I made sure the bug also happens in an incognito tab

Bug type
Component
Component name
MudTextField
What happened?
I'm trying to use MudTextField in a application but it does not working well. It does not recognize the properties in MudTextField and looks like is not reading the input.

That is what i'm doing:
                <MudTextField
                    Class="input-fields"
                    Label="Username"
                    Variant="Variant.Outlined"
<EMAIL_ADDRESS>                    Mask="@(new PatternMask("000.000.000-00"))"
                />

This is inside a  with a Model, a On valid and invalid submit
Expected behavior

Reproduction link
https://try.mudblazor.com/snippet/wEcSuVGHUpcGWDmg
Reproduction steps

I try to write something in the input
The mask that should be applied do not work
Even with a valid value, it do not send an return a validation error
...

Relevant log output
No response
Version (bug)
7.4.0
Version (working)
6.20.0
What browsers are you seeing the problem on?
Chrome
On which operating systems are you experiencing the issue?
macOS
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I copied your code from the reproduction link:

Reproduction link
https://try.mudblazor.com/snippet/wEcSuVGHUpcGWDmg

I pasted it into a project created from the official MudBlazor Templates for WebApp. It's using .NET 8.0, MudBlazor 7.4.0, and WebAssembly global interactivity, and I see no problem.

TryMudblazor is also using the latest version and is a standalone WebAssembly (not WebApp), and as you can see, it's working there too. Please check your application configuration. I suggest you try our templates.

Unless I misunderstand something, but in repro steps it says:

The mask that should be applied do not work

But I see that mask is being applied.

Unless I misunderstand something, but in repro steps it says:

The mask that should be applied do not work

But I see that mask is being applied.

Even with a valid value, it do not send an return a validation error

This I don't really understand, but if the question is why the validation is not working, then you are missing a lot of things like <DataAnnotationsValidator/> and For="@(() => loginModel.UserRegister)", please refer to https://mudblazor.com/components/form#editform-support sample

The validation is Working, the problem is the behavior of the MudTextField. It's invaliding any attempt to send a request to the backend

The validation is Working, the problem is the behavior of the MudTextField. It's invaliding any attempt to send a request to the backend and is having the behavior that i showed in the print.

You need to elaborate much more and provide more info on what the actual problem is. Perhaps it would be better to provide a simple reproduction project via zip or repository.
Your TryMudBlazor sample doesn't have a backend request, but I can clearly see that the OnValidSubmit is being executed on login and the value is updated:

This contradicts everything you said above. It looks like you are not running any interactivity mode with MudTextField, which is why you are having all these problems. This is expected, as static SSR is not supported.

I made a sample, you can see here: https://github.com/oliverigor27/AplicacaoTeste.git

The validation is Working, the problem is the behavior of the MudTextField. It's invaliding any attempt to send a request to the backend and is having the behavior that i showed in the print.

You need to elaborate much more and provide more info on what the actual problem is. Perhaps it would be better to provide a simple reproduction project via zip or repository.
Your TryMudBlazor sample doesn't have a backend request, but I can clearly see that the OnValidSubmit is being executed on login and the value is updated:
This contradicts everything you said above. It looks like you are not running any interactivity mode with MudTextField, which is why you are having all these problems. This is expected, as static SSR is not supported.

I made a sample, you can see here: https://github.com/oliverigor27/AplicacaoTeste.git

I made a sample, you can see here: https://github.com/oliverigor27/AplicacaoTeste.git

But this setup is absolutely not correct:

You said it's WebAssembly, but it's using just the InteractiveServer, which means it doesn't use WASM at all.
It's not a complete setup. You are missing <HeadOutlet @rendermode="InteractiveServer"/> and <Routes @rendermode="InteractiveServer" /> in App.razor, which are important parts when setting up your WebApp. Of course, it will not work as your page is rendered as static, not interactive.
Where did you get OnValueChanged from? It doesn't exist in MudBlazor.

I made a sample, you can see here: https://github.com/oliverigor27/AplicacaoTeste.git

But this setup is absolutely not correct:

You said it's WebAssembly, but it's using just the InteractiveServer, which means it doesn't use WASM at all.
It's not a complete setup. You are missing <HeadOutlet @rendermode="InteractiveServer"/> and <Routes @rendermode="InteractiveServer" /> in App.razor, which are important parts when setting up your WebApp. Of course, it will not work as your page is rendered as static, not interactive.
Where did you get OnValueChanged from? It doesn't exist in MudBlazor.

Oh, i didn't knew about that. I'm sorry, i'm a back-end trying to do a webpage. Thank you again!


Upgrades to latest versions react-scripts and react

This PR upgrades react-scripts and react to latest versions. The project is currently using an almost year-old version.
When this PR is merged, developers will need to rebuild the docker image as described in the README to get the changes.

Thanks, @mauricesvay!
Were you able to make the client work? (cf #1)

@adrienjoly yes, it works without issues (with docker or without).

Sorry, I think I've read too quickly. I haven't tested the develop branch, just master.

@mauricesvay I don't even know what's supposed to work, and what's the difference between what's on master and develop branches...
=> Not sure if it's worth continuing from this old codebase, or start a fresh one.

@mauricesvay: @SkinyMonkey said that he's abandoned this repo and worked on a new one instead. See this discussion for more info: https://github.com/openwhyd/openwhyd-react/issues/1#issuecomment-341997100
=> I'm closing this PR. Sorry for not having updated the status of this project before you sent it... 😓


Update bourbon dependency minor version

When starting my local development server just now I came across the hundreds of warnings again:
DEPRECATION WARNING: Passing 100%, a non-string value, to unquote() will be an error in future versions of Sass.
I remembered this had to do with the version of bourbon we're using, which we couldn't update because of some dependency to sass by activeadmin.
Now that we updated sass in the course of our activeadmin update in https://github.com/codevise/pageflow/commit/cb2beef69a7715adfda050136b2d82b5b0a0ed82#diff-063b9e22ec07e7f812323b34dd15f644R24 , we could finally update bourbon to a newer minor version which gets rid of the deprecation warnings mentioned above.

Coverage remained the same at 99.228% when pulling 831c2fcae4029e518c4af31c1208a87a52d31757 on DanielKuhn:update-bourbon-dependency into 0b1601272a30542c1a4b1e0ff736edd2ccea2953 on codevise:master.


API DSL WIP (committed from ZIO World 2022)

LGTM :P

Ah, it seems it's missing a few implementation details :D I'll reopen it shortly!


Allow ruff 0.2.x; disable default enabled formatters

This fixes https://github.com/python-lsp/python-lsp-ruff/issues/79 - there are no deprecated/breaking changes that affects python-lsp-ruff, so we can safely bump to include ruff 0.2.x
And now that ruff has a formatter that is enabled by default, we should disable the default-enabled formatters, like python-lsp-black does:
https://github.com/python-lsp/python-lsp-black/blob/307e87dbf74ff0227991d88cbc734113ce3fff68/pylsp_black/plugin.py#L60-L61
(I had an annoying issue with these and ruff fighting)
Ref: https://astral.sh/blog/ruff-v0.2.0 - https://github.com/astral-sh/ruff/releases/tag/v0.2.0

LGTM, thanks a lot for your contribution!


Migrate dispatcher to centos/httpd

Use https://hub.docker.com/r/centos/httpd/ image instead of official httpd

Also, consider deleting pid file when restarting httpd:
reload {
    cleanDir("/opt/aem/dispatcher/cache/content/example/demo", "/opt/aem/dispatcher/cache/content/example/live")
    execShell("Restarting HTTPD server", "/usr/local/apache2/bin/httpd -k restart")
}

why?

done


Add playwright-python to workspace tags

This PR adds the playwright module to workspace tags for Python.
cc @sana-ajani

can you add the GDPR comment?

Thanks for the review. Just added the comment for GDPR

LGTM, @RMacfarlane can you review?


Edit pass for Update teams-for-vdi.md DO NOT MERGE

Light copy edit

Hi, Lana/@LanaChin,
We’ve finished the edit pass of this article. Please review it and let me know if we’ve changed the technical meaning anywhere. You have five business days for the review (If you need longer, let me know).
When your review is complete, and you’re satisfied with the changes, our team will do the final merge to confirm there are no remaining PR issues.
Thanks!

Lana approved of edits via email.


Html generation error: Uncaught TypeError: Error resolving module specifier “env”. Relative module specifiers must start with “./”, “../” or “/”.

Problem

Steps To Reproduce
Steps to reproduce the behavior:

Simple yew app with service as https to cross origin service via self signed cert.

this code ` let mut rcs= RootCertStore::empty();
let mut reader = BufReader::new(buf.as_slice());
         rcs.add_parsable_certificates(&rustls_pemfile::certs(&mut reader).unwrap());
         console::log!("store len:{}",rcs.roots.len());
         let client_config=rustls::client::ClientConfig::builder()
             .with_safe_defaults()
             .with_root_certificates(rcs).with_no_client_auth();`

last line of code about generate error on browser console: Uncaught TypeError: Error resolving module specifier “env”. Relative module specifiers must start with “./”, “../” or “/”. If I remove last line  - no errors

Cargo.toml:
`[dependencies]
yew = "0.18"
serde = "1"
serde_derive = "1"
serde_json = "1"
anyhow = "1"
yew-router = "0.15.0"
gloo-console = "0.1"
gloo-dialogs = "0.1.0"
gloo-timers = "0.2.1"
js-sys = "0.3"
wasm-bindgen = { version = "0.2.78", features = ["serde-serialize"] }
log = "0.4.14"
wasm-logger = "0.2.0"
rustls="0.20.0"
rustls-pemfile = "0.2.1"
`
Expected behavior
A clear and concise description of what you expected to happen.
Environment:

Yew version:  v0.18, master

Rust version: rustc 1.56.1 (59eed8a2a 2021-11-01)

Build tool trunk

OS, Ubuntu 21.10

Browser and version: Firefox v94

Questionnaire

[ ] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[x] I don't know how to fix it

I think this is not a bug nor is it related to Yew.
Usually, the “cannot resolve module env” error happens when you are trying to use a Rust API that is not available in wasm32-unknown-unknown.
I think what might be happening here is that rustls is trying to use some Rust API that is not available in the browser and hence resulted in an error.
Even if you manage to load the certificate, I don’t think you will be able to establish an https connection with a custom certificate in the browser environment. The browser uses it’s own certificate store and it cannot be specified by code.
You need to either apply for a certificate that is recognised by your browser or add your self-signed certificate to browser’s trust store.
See: https://github.com/rustwasm/wasm-bindgen/issues/2215

not an issue. fix per proposal


Add h2o benchmark

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I would like to make it easier to run h20 benchmarks
Describe the solution you'd like
Add h2o bin to benchmark crate
Describe alternatives you've considered
None
Additional context
None

Related to https://github.com/apache/arrow-datafusion/issues/147
fyi @Dandandan @matthewmturner


[idea] expose the renderer somehow

It would be neat if an end user could switch out the renderer of an element when needed. Such as:
var bel = require('bel')
var div = bel`<div>testing</div>`

Renders a native DOM element but if the user is using React or virtual-dom, they could do:
var vdom = require('virtual-dom')
var bel = require('bel')({
  renderer: vdom.h
})
var div = bel`<div>testing</div>`

Now the div is a VirtualNode. The only problem is ensuring .update() works cleanly with those renderers.
Also maybe this should just be left up to the user:
var div = bel`<div>testing</div>`
var vnode = convertToVNode(div)

Even crazier idea, what if there was a global setting. So window.BEL_RENDERER = vdom.h and then any library using bel would render to virtual nodes instead?

Closing as being able to render vnode and react components inline would be cool but will likely create too much overhead here.


add piTokenCallback to PowerIndexRouter.sol

Codecov Report

Merging #12 (bba97fd) into master (cd80fac) will decrease coverage by 0.41%.
The diff coverage is 76.92%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
- Coverage   84.18%   83.76%   -0.42%
==========================================
  Files          11       11
  Lines         569      573       +4
  Branches       95       95
==========================================
+ Hits          479      480       +1
- Misses         90       93       +3

Impacted Files
Coverage Δ

contracts/PowerIndexRouter.sol
90.43% <76.92%> (-1.06%)
:arrow_down:

Continue to review full report at Codecov.

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


Make ‘forgot password’ link the correct blue

There are probably other instances; this is just the first one I came across.

Closed in favour of https://github.com/alphagov/govwifi-admin/pull/320


Fix fixing swagger copying

Followup to #711. Rewrote the bash bits without using cpio so hopefully it will play nicer with the environment expeditor runs in.

@msorens I tested your changes locally and they appear to work. Thanks!

@phiggins FYI: Looks like you applied my suggestions in the first chunk of code, but the exact same situation occurs in the second chunk of code.


How to serve the .wasm from a local file instead of a CDN, for offline use.

It is possible to instruct setZXingModuleOverrides to locate the .wasm in a local directory? like returning ./src/to/.wasm/ ??

Not sure what your use case and runtime would be, but here's a small demo to use it locally in node.
File structure:
.
├── index.js
├── node_modules
├── package-lock.json
├── package.json
└── zxing_reader.wasm

index.js:
import {
  setZXingModuleOverrides,
  readBarcodesFromImageFile,
} from "zxing-wasm/reader";

import { readFileSync } from "node:fs";
import { fileURLToPath } from "node:url";

setZXingModuleOverrides({
  wasmBinary: readFileSync(
    fileURLToPath(new URL("./zxing_reader.wasm", import.meta.url)),
  ),
});

fetch(
  "https://api.qrserver.com/v1/create-qr-code/?size=150x150&data=Hello%20world!",
)
  .then((resp) => resp.blob())
  .then(readBarcodesFromImageFile)
  .then(console.log);

My solution:
setZXingModuleOverrides({
locateFile : () => {
return  "/assets/libs/zxing/zxing_full.wasm";
}
});

A more comprehensive answer in the v2 README: https://github.com/Sec-ant/zxing-wasm?tab=readme-ov-file#integrating-in-non-web-runtimes


Fixed postgresql path for persistence

You won't be able to persist the database with the previous path.

lgtm