Draw Image on pdf with existing image replace old image

What were you trying to do?
I try to edit a pdf document and let user draw on it :

i load document with pdfJs (scale 1)
i put a canvas on the same size over it where the user can draw
on save, i extract my drawing canvas as png and use pdf-lib to draw the image over the PDF
=> just this work perfectly
if i open again my pdf with previous drawing
i put again a canvas where the user can draw
when i save, the previous drawing is replaced by the new drawing zone
=> so the previous drawing is lost

How did you attempt to do it?
//i show only the part when i use pdf-lib, which is the more relevant
const pages = this.pdfLib.getPages();
for (lCurrentPageNumber = 1; lCurrentPageNumber <= pages.length; lCurrentPageNumber++) {
            var lCurrentPage = pages[lCurrentPageNumber - 1];//attention commence à 0
             const { width, height } = lCurrentPage.getSize();
            var lContainer = document.getElementById("page-container-" + lCurrentPageNumber);
            var lDrawingCanvas = lContainer.querySelector('.canvas-container > .canvas-drawing');
             var dataURL = lDrawingCanvas.toDataURL("image/png");
            const pngImage = await this.pdfLib.embedPng(dataURL);
            lCurrentPage.drawImage(pngImage, {
                x: 0,
                y: 0, //attention on part du bas
                width: width,
                height: height,
            });
}
const pdfBytes = await this.pdfLib.save();
// pdfBytes have the current drawing but lost previous drawing zone which was embed

What actually happened?
the pdf lost all previous image (drawing zone) embed in the doc
What did you expect to happen?
i expect the pdf-lib draw image over it (its transparent png) or merge existing image into one, but not replace existing image
How can we reproduce the issue?

open a pdf, draw an image over it on the same size than the document (with transparency), and save it
open the pdf previously saved, draw another image over it on the same size than the document (with transparency), and save it. The first image will be lost

Version
1.17.0
What environment are you running pdf-lib in?
Browser
Checklist

[X] My report includes a Short, Self Contained, Correct (Compilable) Example.
[X] I have attached all PDFs, images, and other files needed to run my SSCCE.

Additional Notes
No response

I think this is the same as #1075, which should be fixed in v1.17.1.

i confirm i don't reproduce the problem in v1.17.1, thanks !


Update issue templates

Add a Feature request template, one of Github's default template choices. This should be amended for our use in a future commit.
Instructions for reviewing:

Check whether there are spelling and grammar mistakes
Check for clarity
Do any sections need to be added?
Can any sections be removed?

We need this functionality, but @alliequintano and @Dreamy26 please review this still.


Make use of _all in ES queries

ES has the virtual field _all, which allows you to search for any term in every field. Usually you would create an aggregate field in Titan, which is a pain, since you always have to keep it in sync with other fields. It would be great if we could do something like  g.indexQuery("index-name", "_all:foo").vertices().
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-all-field.html

As far as I can tell this already works.
I had a look at also adding this to a standard gremlin query, but some stuff especially around text handling (TEXT vs STRING) won't make sense. Therefore I think this is better left as indexQuery only.

Cool, I just tried it again and indeed it works. Not sure why I opened the ticket, maybe it wasn't possible in 0.5.x.

I'm trying to make it a bit nicer. We get a warning in the logs that will confuse users. The syntax will be more in line with the existing indexQuery. e.g. v.*:"test"


Data-event click, clicking several tooltips leaves all visible instead of the current one.

When several tooltips are instantiated on a single page, the data-event click doesn't act fully as a toggle to hide all active tooltips. Not sure if this is the desired behavior but it would make sense that only the current tooltip be activated at a time.

Have you tried firing ReactTooltip.hide() on the click to close all instance?

On the version 1.2.0 the prop: eventPropagationMode was introduced. Changing the event propagation mode to 'capture' solved this issue.

Issue still occurs, please reopen


Can't set filenameHashing in vue.config.js

Version
3.0.0-rc.10
Node and OS info
node 8.11.3, npm 5.6, macOS High Sierra
Steps to reproduce
Add filenameHashing: false to  vue.config.js
What is expected?
No file hashes in build
What is actually happening?
error in console:
 ERROR  Invalid options in vue.config.js: "filenameHashing" is not allowed

I've seen this bug for rc.3, but I'm using rc.10. Just deleted  ./node_modules and reinstalled vue-cli with npm install -g @vue/cli --force

Make sure @vue/cli-service in your project is also upgraded.

for others:

how to check your global cli-service version: npm list -g @vue/cli-service-global
how to upgrade global package: npm install -g<EMAIL_ADDRESS>--force


Fix slow query functions

Considerably speeds up read times.
Cells marked in red denote times for operations that never completed.

:heavy_check_mark: Checked that the new recursion method isn't messing with the order of results


Add a "contact" button to top ribbon

Contact button just gives<EMAIL_ADDRESS>email.

added contact button


[UI Enhancement] : Adding gsap animation to home page when loaded | gssoc-extd level 3

Adding gsap animation to home page when loaded
please assing this issue to me under gssoc-extd level 3

Hello @Hamza1821
Please provide this issue to me , I can provide gsap animation as I have worked on this , and so that I can make my first contribution in open source 😊


Magic ProfileDescription

It should be mentioned somewhere, that if you set the Profile Description to 'Navigation menu only.' then the profile is excluded from the page Available Roles, where the user can select his role.

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

ID: ad56e752-ba1d-fb3a-8ea4-4d7e3a780235
Version Independent ID: c5dcb9d8-8c4e-7952-15f7-82564319d67c
Content: ProfileDescription Property - Business Central
Content Source: dev-itpro/developer/properties/devenv-profiledescription-property.md
Service: dynamics-365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

I've created an idea to improve the current situation with this dirty workaround.
https://experience.dynamics.com/ideas/idea/?ideaid=f29d01e9-7467-ee11-a81c-00224854d651

Thanks for the feedback. At this point, we won't document that behavior. The idea has multiple votes at this point, thanks for creating that.


pull request for e2e test at 01/20/2017 15:56:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Use assertThatExceptionOfType in dropwizard-auth

Problem:
It is (subjectively) better to specify tests in terms of success rather than terms of failure and also for there to be less code, provided it works and isn't confusing.
With that in mind, some tests could be improved slightly.
Solution:
translate
try {
    something();
    failBecauseExceptionWasNotThrown();
} catch (Exception e) {
    // assert some things about e
}

into
assertThatExceptionOfType(Exception.class)
    .isThrownBy(() -> something())
    // assert some more things

Result:
There is less code and (opinions may differ) the tests become more expressive.
If you agree this is a good thing to do, there are other places where failBecauseExceptionWasNotThrown is used and I'm happy to give those the same treatment if they look like suitable candidates.
Also, if these little cleanup PRs are annoying and creating unnecessary code churn and review effort, don't be afraid to say so. I like Dropwizard and have worked with it on many projects (https://github.com/alphagov/verify-hub being the only one which is public) where it has been really helpful, so I thought I'd try and do some odd bits and pieces to keep its quality up.

Also, if these little cleanup PRs are annoying and creating unnecessary code churn and review effort, don't be afraid to say so.

@rhowe Thanks a lot for addressing these refactorings! They're certainly not annoying. 😉
If you're looking for another thing to contribute, you might want to check out https://github.com/dropwizard/dropwizard/pull/3613.

Also, if these little cleanup PRs are annoying and creating unnecessary code churn and review effort, don't be afraid to say so.

@rhowe Thanks a lot for addressing these refactorings! They're certainly not annoying. 😉
If you're looking for another thing to contribute, you might want to check out https://github.com/dropwizard/dropwizard/pull/3613.


AAD Related: Java EE app accesses AAD user with exception

Steps:

Deploy cluster/dynamic cluster offer with AAD enabled
Deploy the basic auth sample
Login the application with user wlstest
Failed to login and got exception.

Exception details:
The LDAP authentication provider named "AzureActiveDirectoryProvider" failed to make a connection to LDAP server at ldaps://ladps.wls-security.com:636, the error cause is: ladps.wls-security.com: Name or service not known.
Can be reproduced in cluster and dynamic cluster offer.
Root cause, the testing AAD LADP server domain is a private one, we have to specify its IP in the vm machine.
Workaround:
Specify AAD IP address to /etc/hosts in managed server vm
sudo echo "${wlsLDAPPublicIP}  ${adServerHost}" >> /etc/hosts
# <IP_ADDRESS>    ladps.wls-security.com

AB#1141496


Add query validation

Description

Related Issues

Checklist

[ ] Is this code covered by new or existing unit tests or integration tests?
[ ] Did you run make test successfully?
[ ] Do new classes, functions, methods and parameters all have docstrings?
[ ] Were existing docstrings updated, if necessary?
[ ] Was external documentation updated, if necessary?

Additional Notes or Comments

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (34830a7) 80.33% compared to head (f26b345) 69.01%.
Report is 1283 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1507       +/-   ##
===========================================
- Coverage   80.33%   69.01%   -11.33%
===========================================
  Files          95      104        +9
  Lines        6602     7313      +711
===========================================
- Hits         5304     5047      -257
- Misses       1298     2266      +968

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Closing for now, will reopen at a later date.


Provide way to write a file to a specific folder

In a customer project (viur-core 3.5), I've written this function some time ago. It writes a file to the File module, but also to a specific location. This can be seen as an extension for File.write(), so that it should be generalized and integrated into viur-core.
class File(_File):

	def write_to_folder(self, foldername, filename, content, mimetype="text/plain"):
		"""
		Write a file into the file module to a specified folder.
		The foldername is both the folder's initial name and name stored as the key.
		The folder can be renamed later on by the user, but the key remains.
		The folder is created under the module root node.
		"""
		# Check for foldername
		rootnode = self.ensureOwnModuleRootNode()

		folderskel = self.baseSkel("node")
		folderkey = db.Key(folderskel.kindName, foldername)

		# Create the folder if it doesn't exist
		if not folderskel.fromDB(folderkey):
			folderskel["key"] = folderkey
			folderskel["name"] = foldername
			folderskel["parentrepo"] = folderskel["parententry"] = rootnode.key
			folderskel.toDB()

		# Save the file into the folder.
		dl_key = utils.generateRandomString()

		blob = bucket.blob("%s/source/%s" % (dl_key, filename))
		blob.upload_from_file(io.BytesIO(content), content_type=mimetype)

		skel = self.addSkel("leaf")

		skel["name"] = filename
		skel["size"] = blob.size
		skel["mimetype"] = mimetype
		skel["dlkey"] = dl_key
		skel["parentrepo"] = rootnode.key
		skel["parententry"] = folderkey
		skel["pending"] = False
		skel["weak"] = False
		skel["width"] = 0
		skel["height"] = 0

		assert skel.toDB()
		return skel

Some further ideas on this issue:

it should be an extension to File.write()
it should accept for a root-node, and default to self.ensureOwnModuleRootNode()
it should also accept a path of folders as an iterable of str, so ("this", "is", "a", "valid path"). The folders should be created when not existing.


[Translation it] WebAPK

Italian translation of WebAPK.
Please review by @carlaofarrell
Check out a review request at GitLocalize

:tada: This has been pushed live to https://developers.google.com/web/


Feature request: Add opacity control for overlay feature

This is a great map for Viet Nam.
It could be perfect if we can control opacity when adding overlay on Map4D with Flutter. Sometimes, when we add an overlay, we want to adjust the opacity of this layer using control.
Please add this feature to this flutter lib.
Many thanks!

Hi @hunghoang,
Transparency (opacity) already support tile overlay in map4d_map v2.4.0
Thanks for your suggestions

Great! thanks a lot.


ls: Start fix (see comment) color-term.sh GNU test

Fixes GNU test color-term.sh for LS (kind of)
Explaination
ls --color=always should honor the environment variables LS_COLOR and COLORTERM, if they are not set or empty it should honor the env variable TERM and use the default values for coloring. Additionally for TERM there is a terminal list in DIRCOLORS that needs to be checked and only if the value is in that list, it is allowed. Otherwise, even with --color=always no color should be set.
The rust version does not look for any env variables or check the terminal list in DIRCOLOR. This PR will fix it and implement the hirarchy as well as the list check.
I also added tests for the different scenarios. Beware, they need to be either run with cargo test -- --test-threads=1 or cargo nextest run otherwise all test will change the env variables at the same time and the tests will fail.
Why is GNU test color-term.sh not green?
String Coloring in rust is done via LSCOLOR and nu-ansi-term and they do generally what is expected, but not 100% under the hood.
Test result:
FAIL: tests/ls/color-term
=========================

--- exp 2023-05-16 15:56:30.337121900 +0200
+++ out 2023-05-16 15:56:30.102644900 +0200
@@ -1,4 +1,4 @@
-^[[0m^[[01;32mexe^[[0m$
-^[[0m^[[01;32mexe^[[0m$
+^[[1;32mexe^[[0m$
+^[[1;32mexe^[[0m$
 exe$
 exe$
FAIL tests/ls/color-term.sh (exit status: 1)

As you can see all 4 tests are doing what they should be doing, but the rust version is using single-digit numbers for text while the gnu version uses double-digit numbers. Additionally the gnu version starts off by resetting any pre-styling, which the rust version does not.
As said it is working as expected but not technically. Hopefully this PR can still make it. For the next step changes on the underlying libraries are needed or an architectural decision to refrain from getting this test green.

MacOS test is failing since macOS does not correctly support "LS_COLORS" env variable and the mac env var LSCOLORS is not supported by underlying crate -> https://github.com/sharkdp/lscolors/issues/55

but not 100% under the hood.

I think this is OK. Maybe we should just patch the GNU tests to match our results in util/build-gnu.sh

Beware, they need to be either run with cargo test -- --test-threads=1 or cargo nextest run otherwise all test will change the env variables at the same time and the tests will fail.

This is a bit unfortunate and not really sustainable. Is there any way we can remove this restriction? Maybe we can make the function pure by giving it the env variables as arguments, which we can then test and we add the actual env::var calls only in the rest of the code:
// Use this for testing
fn check_variables_against_dircolors(dircolors: &str, ls_colors: Option<String>, colorterm: Option<String>, term: Option<String>) -> bool {
    ...
}

// Use this in `ls`
fn check_env_vars(dircolors: &str) {
     check_variables_against_dircolors(dircolors: &str, env::var("LS_COLORS"), ...)
}

I already did some work on nu-ansi-term and lscolors has an open PR to support gnu legacy Mode aka double digit styles and reset before apply. Once it's done we will be able to use that feature here and do not need to change tests.

@sylvestre We can fix the tests with the nu-ansi-term patch later, but my original comments still hold.

Hey! Love this work, but I'm marking it as a draft, so that we don't accidentally merge the git dependency. Once lscolors has a new release, we can mark this ready again.

Beware, they need to be either run with cargo test -- --test-threads=1 or cargo nextest run otherwise all test will change the env variables at the same time and the tests will fail.

This is a bit unfortunate and not really sustainable. Is there any way we can remove this restriction? Maybe we can make the function pure by giving it the env variables as arguments, which we can then test and we add the actual env::var calls only in the rest of the code:
// Use this for testing
fn check_variables_against_dircolors(dircolors: &str, ls_colors: Option<String>, colorterm: Option<String>, term: Option<String>) -> bool {
    ...
}

// Use this in `ls`
fn check_env_vars(dircolors: &str) {
     check_variables_against_dircolors(dircolors: &str, env::var("LS_COLORS"), ...)
}

Hi, I updated the function to take in env variables as results, so the actual unpacking etc happens inside the function and is tested as well.

Sweet:
Congrats! The gnu test tests/ls/color-term is no longer failing!
Congrats! The gnu test tests/ls/multihardlink is no longer failing!
Congrats! The gnu test tests/ls/root-rel-symlink-color is no longer failing!

sorry we didn't merge this yet. I tried to rebase it, let's see if it works

@alexkunde sorry but do you have plans to finish it?

no activity for a while, closing


feat: New Observable for when Camera has been initalized

Plugin(s)

[X] Barcode Scanning
[ ] Face Detection
[ ] Face Mesh Detection
[ ] Selfie Segmentation
[ ] Translation

Current problem
I am trying to save the state of the torch so that when a user re-opens the camera the torch is set to the same state as when they last closed the camera. However, if I enable to torch right after opening the camera, the torch flashes but does not stay on. If I add a 200ms delay the torch stays on as expected.
Preferred solution
An observable for the camera being initalized and/or opened would be a more elegant and reliable solution. I worry that with older and slower deviced the 200ms delay won't be enough, but I don't want to increase that delay to the point it's noticable by users.
Alternative options
The torch not being reset by the camera opening would be great, but I assume that is being set at the OS level.
Additional context
I only selected bardcode scanning as that is the only part of the library I have used, but I suspect the same issue woudl happen for all of the features.
Before submitting

[X] I have read and followed the feature request guidelines.
[X] I have attached links to possibly related issues and discussions.

Is this an issue on Android or iOS or both?

I was mistaken, this only occurs in iOS (testing on iPad mini), and only occurs on the second time the scanner is open. I modifed the demo code to add a initialTorchState parameter to the Barcode Reader component. For this demo I set initialTorchState to always be True.
https://github.com/derekdavieUH/capacitor-mlkit-plugin-demo-persistent-torch
    await BarcodeScanner.startScan(options);     // Uncomment following line for iOS torch to work correctly based on initialTorchState     // await new Promise(resolve => setTimeout(resolve, 200))     if(this.initialTorchState && !(await BarcodeScanner.isTorchEnabled()).enabled){       await BarcodeScanner.enableTorch();     }

Thanks, i will take a look as soon as i have some time.


need inline documentation on why BGREWRITEAOF forked a process

Following functions need better comments
Here is a list of files along with the lines highlighted that need better comments making it easier to understand what's happening

https://github.com/DiceDB/dice/blob/master/core/eval.go#L170-L176

Here's why I think it is difficult to understand the code
understanding how we are forking, referring to Go doc for that, and the reason for doing it would help.

Added inline documentation, please review.
https://github.com/DiceDB/dice/compare/master...rohanverma94:dice:stable-tested


Add support for logging files without extension?

I would like to setup this cool container to rotate syslog file, but it looks like it cannot be done with the envs provided, since the code assume you have files with extension, or am I missing something?

Does the env LOGS_DIRECTORIES work for you? Should take all files regardless of the file ending.


Document index, constraint, timestamp col drop methods

I'm looking to put a remove index command on a down migration, but not seeing one in the docs, is there a removeIndex?

+1

FYI dropIndex is now documented: https://github.com/tgriesser/knex/blob/05ffb457a885c9a2d27a0684b57cbcf45cbb0456/index.html#L1908

Also need to document foreign() to create foreign key references after a column already exists.  I just replaced some existing foreign key references so I could add cadcade deletions using:
exports.up = function(knex, Promise) {
  return knex.schema
    .table('review', function (table) {
      table.dropForeign('event_id')
      table.foreign('event_id')
        .references('event.id')
        .onDelete('CASCADE')

      table.dropForeign('user_id')
      table.foreign('user_id')
        .references('user.id')
        .onDelete('CASCADE')
    })
})

Thanks @techniq, updated Ben's post.

Would you be interested in supplying a PR, @techniq?

@rhys-vdw See PR #1156

Thanks @techniq.

Welcome @rhys-vdw. You can check those off of @bendrucker's list ;)

Already done.

Thanks.  My page needed a hard refresh to see.  Guess just comments are websocket streamed in.

I figured something like that. I'll update gh-pages later when I'm back from work.


Allow entrypoint to be blank.

Allowing entrypoint to be blank can be used to force default docker behaviour of running cmd in shell. Also updated examples.
Closes #177.
We could also create a PR to set CMD to /bin/sh -l which would be keep previous behaviour when no command is specified.

Hang on, don't merge this yet. It breaks previous behaviour:
docker run alpine:base
docker: Error response from daemon: No command specified.
See 'docker run --help'.

set entrypoint to /bin/sh -c

@panekj I tried that but there is an issue (I assume with quoting) so commands don't run. I note that Docker's official base images don't set the entrypoint.

docker inspect?  i can work on debugging this morning

I tried that but there is an issue (I assume with quoting) so commands don't run. I note that Docker's official base images don't set the entrypoint.

Yes, there is no way of fixing that without setting cmd

@kaniini I'm trying to add cmd support now. Was thinking to just have another top level element, that seemed least confusing.

I think you can just change
default:
  cfg.Config.Entrypoint = []string{"/bin/sh", "-l"}

to
default:
  cfg.Config.Cmd = []string{"/bin/sh", "-l"}

and it will fix the issue

@panekj that's an interesting idea :) Personally, I'd much rather cmd was set explicitly and apko supported custom cmd commands. Note that the ubuntu and debian base images set cmd to "bash".

Personally, I'd much rather cmd was set explicitly and apko supported custom cmd commands.

Isn't that ShellFragment?

Note that the ubuntu and debian base images set cmd to "bash" (but leave entrypoint empty).

You can inspect base image, and set cfg.Config.Cmd to that.

You mean we could use another tool to update the config? Personally, I'd like apko to support setting most, if not all metadata on an image.

You can read image config via Docker Engine API. Otherwise I'm not sure what's the point of mentioning bash here?

I think we're talking past each other :)
What I'm saying is I'd like for apko to create base images "equivalent" to the existing official base images OOTB. So I can see the following requirements:

should be able to do things like docker run apko-alpine echo foo. That seems to require allowing blank entrypoints in the OCI config.
should be able to get a shell with docker run -it apko-alpine. That seems to require cmd to be set in the OCI config.
support cmds other than /bin/sh -l. For example, I can imagine a base image with bash or dash installed (hence my reference to the debian and ubuntu images). And I can certainly see other images wanting to use cmd to pass default arguments (e.g. --help)


Initial delegation certificates are applied incorrectly

Background
In Cardano.Chain.Delegation.Validation.Interface, initial delegation is specified by:

Firstly, constructing an initial delegation map which delegates from stakeholders to themselves.
Secondly, applying the certificates from the genesis data in the normal way.

The problem is that normally, delegation certificates do not come into effect from the moment they are posted - they are only scheduled, and will come into effect at some future slot. For the genesis configuration, this is incorrect - the initial delegation should be in effect from the first block.
Proposed Solution
Change initialState to create the delegation map directly using the heavyweight delegation certificates, rather than calling updateDelegation.
Next Action

[ ] Confirm this diagnosis (@ruhatch?)
[ ] Fix all the things

A simple solution that I've tested out locally is to replace k with 0 in the environment that you pass to updateDelegation, which will let them be adopted instantly.


Fixed issue with listing all documents

Hey @ReeceM ,
Thank you for adding the access token, it worked like a charm. But when creating sitemap.xml it was showing all the links from prismic. So I made a small change to your code in generator.js.
Would you mind taking a look at it and if it's okay can you merge it?

Hey @amala-james-cko,
Thank you for making a PR, I will look at it also locally. The test passed so that's good. 👍
If you could, would you be able to add an example below of what it gave before and then after the change? Doesn't have to be exact to what you had, the links/text can be redacted.

Hi @amala-james-cko, I am not sure if the review requests were submitted yesterday. I don't think I clicked finish then.
There are a few things that have changed as you said, overall there isn't much difference in the functionality added by using the Prismic.Predicates.at and looping or using the Prismic.Predicates.any, the other thing is that if there is more than 20 total docs, then the results need to be paginated properly.
Is it possible to give an example of what you meant by showing all the links from prismic.

Yeah, I hadn't clicked finish on the review panel. I was thought it had been sent through, I hadn't missed the PR.

Closing it since the use case is different.

Closing it since the use case is different.

Hi, the use case of the PR or the package?
The PR is adding improved functionality which is fine


Double Maybe for a QueryParam?

Here's what my routes look like (using servant-generic):
data Routes route = Routes
  { rTest :: route :- "test" :> Get '[JSON] Text
  , rOAuthReturn :: route :- "oauth-return" :> QueryParam "code" Text :> Get '[JSON] Text
  } deriving (Generic)

Here's the function that handles rOAuthReturn:
oauthReturn :: Maybe Text -> AppM Text
oauthReturn = -- some code

The generated Elm type-signature for this API was:
getOauthreturn : Maybe (Maybe (String)) -> Http.Request (String)
getOauthreturn query_code = -- some code

Is this correct?

Can you check you're using the latest version of servant-elm? I believe this was fixed in https://github.com/mattjbray/servant-elm/pull/31.


Add Metric Conventions as a specification

This is a draft PR. I'll add to a link to specification/metrics/purefa-metrics.md once i'm ready to push.
Also happy to push with the TODOs on there.
This PR is to add the metric conventions from the purefa exporter in order to answer some questions about what type of metrics, and how some metrics are correlated from customers.
This style is based off of the semantic conventions from OTel.

For visibility, I would like to go ahead and merge this with the TODOs for the remaining metric instruments.  A later PR will follow to fill in those gaps.
There has also been additional metrics added since this was written (ex. network or replciation metrics) that will need to be added as well.


Does Lazy Load not work when using destroy()? what is wrong?

Friends, help solve the problem. Lazy Load does not work. There is an autoheight function, it creates a new slider when resizing the browser. And in it I do a reset of the current slider via destroy (); But at the same time, lazy image loading stops working.  What have I done wrong? How to write correctly so that both LazyLoad and destroy () work?
Here is a living example: https://codepen.io/Cheizer/pen/bGbqdZb
I use it like that:
`//slider news
var classname = ‘.slider-news’;
const breakpoint = window.matchMedia( ‘(max-width:655px)’ );
const breakpointChecker = function() {
if ( breakpoint.matches === true ) {
return autoheight(breakpoint.matches);
} else if ( breakpoint.matches === false ) {
return autoheight(breakpoint.matches);
}
};
var settings = {
speed: 1000,
spaceBetween: 20,
autoHeight: false,
slideToClickedSlide: true,
preloadImages: false,
lazy: {
loadOnTransitionStart: true,
loadPrevNext: true,
},
on: {
lazyImageReady: function () {
this.updateAutoHeight();
}
},
navigation: {
nextEl: $('.swiper-button-next'),
prevEl: $('.swiper-button-prev'),
},
pagination: {
el: ‘.swiper-pagination’,
type: ‘bullets’,
clickable: true,
},
breakpoints: {
655: {
allowTouchMove: true,
autoHeight: true,
},
},
}
s6 = new Swiper($(classname + ‘ .swiper-container’), settings);
const autoheight = function(e) {
if ( e === true ) {
s6.destroy();
s6 = new Swiper('.swiper-container', settings);
}else{
s6.destroy();
s6 = new Swiper('.swiper-container', settings);
}
}
breakpoint.addListener(breakpointChecker);
breakpointChecker();`
What's wrong? Help!

Do you want to ask a question? Are you looking for support? The Swiper forum and Stack Overflow are the best places for getting support

Please, don't use GitHub issues for questions

@nolimits4web     Well, but the forum also asked, there is silence :(


Rename "interpreters" to "environments" in various places

This will require both code changes as well as doc changes.

[ ] Use localization to standardize

Closing as this has been an ongoing process where older commands are being marked as "Interpreter" for discovery and newer stuff contains "Environment" like "Create Environment".


[Substrate.io Migration] Runtime Upgrades

The "Runtime Upgrades" page was migrated from the existing Substrate.io Tutorial section: https://docs.substrate.io/maintain/runtime-upgrades/

@eshaben take a look at this and let me know what you think. We'll need CSS on admonitions/drop downs at some point

@eshaben added an intro and took out the drop downs.


Low Throughput on Online Boutique Benchmark

Bug Description
Setup:
We are running Online Boutique benchmark (https://github.com/GoogleCloudPlatform/microservices-demo) on chameleon open cloud with three worker nodes (raw k8s, 48 threads and 192G for each). (We also tried on openshift with three 5.8xlarge compute nodes and get very similar results)

Resource allocation: for each server container, we assign 3 vCPUs and 1 Gi Memory, for each sidecar container, we assign 4 vCPUs and 1Gi Memory
Workload generator: we used wrk2 to generate user requests visiting homepage of online boutique web. We used two threads, 320 connections and 2000 input rate to saturate the mircoservices and get the throughput.
Results:

Without istio, we can achieve ~850 req/s.
With istio default settings, we can only achieve ~320 req/s

Tuning:

Concurrency: we changed the concurrency to 0 to allow envoy use 4 worker threads but it didn't help. It makes sense since even the throughput without istio is not high.
Max request per connection (envoy cluster): Online-boutique uses grpc communication which use one HTTP/2 connection. For HTTP/2 connections, envoy connection pooling will use a single connection if there is no limit. So we also tried tuning max_request_per_connection for envoy cluster which reached ~650 req/s with max_request_per_connection=40.
Buffer limit per connection: since frontend will return a whole web page, we also tried increasing buffer limit but it didn't help much.

Now we still have spaces for further tuning. One possible bottleneck would be the outbound listener. For example, frontend service will send requests to port 7000 of currency service. If I check the top output in frontend sidecar container, the one with very high cpu usage is always the one handling connection to port 7000. Also the ratio of user request to requests to currency service is 1:10, which means there should be ~6500 req/s to port 7000 of currency service.

If this is the bottleneck, we are wondering if there is any tuning we can do. If not, what could be the bottleneck and how we can tune it? Thanks!
istio-operator.yaml
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  components:
    base:
      enabled: true
    cni:
      enabled: false
    egressGateways:
    - enabled: false
      name: istio-egressgateway
    ingressGateways:
    - enabled: true
      name: istio-ingressgateway
    istiodRemote:
      enabled: false
    pilot:
      enabled: true
  hub: docker.io/istio
  meshConfig:
    defaultConfig:
      proxyMetadata: {}
      proxyStatsMatcher:
        inclusionRegexps:
        - ".*_cx_.*"
      concurrency: 0
    enablePrometheusMerge: true
  profile: default
  tag: 1.17.1
  values:
    base:
      enableCRDTemplates: false
      validationURL: ""
    defaultRevision: ""
    gateways:
      istio-egressgateway:
        autoscaleEnabled: true
        env: {}
        name: istio-egressgateway
        secretVolumes:
        - mountPath: /etc/istio/egressgateway-certs
          name: egressgateway-certs
          secretName: istio-egressgateway-certs
        - mountPath: /etc/istio/egressgateway-ca-certs
          name: egressgateway-ca-certs
          secretName: istio-egressgateway-ca-certs
        type: ClusterIP
      istio-ingressgateway:
        autoscaleEnabled: true
        env: {}
        name: istio-ingressgateway
        secretVolumes:
        - mountPath: /etc/istio/ingressgateway-certs
          name: ingressgateway-certs
          secretName: istio-ingressgateway-certs
        - mountPath: /etc/istio/ingressgateway-ca-certs
          name: ingressgateway-ca-certs
          secretName: istio-ingressgateway-ca-certs
        type: LoadBalancer
    global:
      configValidation: true
      defaultNodeSelector: {}
      defaultPodDisruptionBudget:
        enabled: true
      defaultResources:
        requests:
          cpu: 4000m
      imagePullPolicy: ""
      imagePullSecrets: []
      istioNamespace: istio-system
      istiod:
        enableAnalysis: false
      jwtPolicy: third-party-jwt
      logAsJson: false
      logging:
        level: default:info
      meshNetworks: {}
      mountMtlsCerts: false
      multiCluster:
        clusterName: ""
        enabled: false
      network: ""
      omitSidecarInjectorConfigMap: false
      oneNamespace: false
      operatorManageWebhooks: false
      pilotCertProvider: istiod
      priorityClassName: ""
      proxy:
        autoInject: enabled
        clusterDomain: cluster.local
        componentLogLevel: misc:error
        enableCoreDump: false
        excludeIPRanges: ""
        excludeInboundPorts: ""
        excludeOutboundPorts: ""
        image: proxyv2
        includeIPRanges: '*'
        logLevel: warning
        privileged: false
        readinessFailureThreshold: 30
        readinessInitialDelaySeconds: 1
        readinessPeriodSeconds: 2
        resources:
          limits:
            cpu: 4000m
            memory: 1Gi
          requests:
            cpu: 4000m
            memory: 1Gi
        statusPort: 15020
        tracer: zipkin
      proxy_init:
        image: proxyv2
        resources:
          limits:
            cpu: 4000m
            memory: 1Gi
          requests:
            cpu: 4000m
            memory: 1Gi
      sds:
        token:
          aud: istio-ca
      sts:
        servicePort: 0
      tracer:
        datadog: {}
        lightstep: {}
        stackdriver: {}
        zipkin: {}
      useMCP: false
    istiodRemote:
      injectionURL: ""
    pilot:
      autoscaleEnabled: true
      autoscaleMax: 5
      autoscaleMin: 1
      configMap: true
      cpu:
        targetAverageUtilization: 80
      enableProtocolSniffingForInbound: true
      enableProtocolSniffingForOutbound: true
      env: {}
      image: pilot
      keepaliveMaxServerConnectionAge: 30m
      nodeSelector: {}
      podLabels: {}
      replicaCount: 1
      traceSampling: 1
    telemetry:
      enabled: true
      v2:
        enabled: true
        metadataExchange:
          wasmEnabled: false
        prometheus:
          enabled: true
          wasmEnabled: false
        stackdriver:
          configOverride: {}
          enabled: false
          logging: false
          monitoring: false
          topology: false

EnvoyFilter for tuning
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: envoy-filter-for-buffer-increase
  namespace: online-boutique
spec:
  configPatches:
    - applyTo: CLUSTER
      patch:
        operation: MERGE
        value:
          max_requests_per_connection: 40

Version
$ istioctl version
client version: 1.17.1
control plane version: 1.17.1
data plane version: 1.17.1 (12 proxies)
$ kubectl version --short
Client Version: v1.26.2
Kustomize Version: v4.5.7
Server Version: v1.26.2

Additional Information
No response

I think your analysis that it's caused by h2 is correct - connections are sticky in h2 so all concurrent streams are handled by a single worker which limits the throughput. For large streams, the suggestion is to limit concurrent streams per TCP connection. Try reducing server side "max_concurrent_streams" (see https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/protocol.proto#config-core-v3-http2protocoloptions). This should cause more connections and more even worker distribution.

Thank you for your response. I tried the following yaml for max_concurrent_streams which didn't help much. And I see the same cpu usage and downstream connections.
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: h2-control
  namespace: online-boutique
spec:
  configPatches:
    - applyTo: NETWORK_FILTER
      patch:
        operation: MERGE
        value:
          typed_config:
            '@type': type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
            http2_protocol_options:
              max_concurrent_streams: 50

Could you please provide more insights about the config? I'm a bit confused how setting max_concurrent_streams would help if the application itself uses one h2 connection for all grpc calls. Thanks!


Scroll wheel in edit mode does not zoom the image/video

Bug Description
Scroll wheel in edit mode does not zoom the image/video
Expected Behaviour
Scroll wheel in edit mode should zoom the image/video.
Steps to Reproduce

Screenshots

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

@wassgha  can you advise on the status here - appears to have been addressed, please confirm

@pbakaus / @o-fernandez - do we need this for stable?

No.

Proof-of-concept: #2563

Verified in QA


fix(java): add configurations for Storage tests

This PR adds a few reflection configurations for native image support in Storage.
prox-config.json:
JUnit Vintage:ITBlobWriteChannelTest:testJsonEOF_0B
    MethodSource [className = 'com.google.cloud.storage.it.ITBlobWriteChannelTest', methodName = 'testJsonEOF_0B', methodParameterTypes = '']
    => com.oracle.svm.core.jdk.UnsupportedFeatureError: Proxy class defined by interfaces [interface com.google.cloud.storage.spi.v1.StorageRpc] not found. Generating proxy classes at runtime is not supported. Proxy classes need to be defined at image build time by specifying the list of interfaces that they implement. To define proxy classes use -H:DynamicProxyConfigurationFiles=<comma-separated-config-files> and -H:DynamicProxyConfigurationResources=<comma-separated-config-resources> options.
       com.oracle.svm.core.util.VMError.unsupportedFeature(VMError.java:87)
       com.oracle.svm.reflect.proxy.DynamicProxySupport.getProxyClass(DynamicProxySupport.java:146)
       java.lang.reflect.Proxy.getProxyConstructor(Proxy.java:66)
       java.lang.reflect.Proxy.newProxyInstance(Proxy.java:1006)
       com.google.common.reflect.Reflection.newProxy(Reflection.java:86)
       com.google.cloud.storage.it.ITBlobWriteChannelTest.lambda$doJsonUnexpectedEOFTest$1(ITBlobWriteChannelTest.java:140)
       com.google.cloud.ServiceOptions.getRpc(ServiceOptions.java:560)
       com.google.cloud.storage.StorageOptions.getStorageRpcV1(StorageOptions.java:149)
       com.google.cloud.storage.StorageImpl.<init>(StorageImpl.java:115)
       com.google.cloud.storage.StorageOptions$DefaultStorageFactory.create(StorageOptions.java:50)

The reflect-config.json file registers some Java classes for reflection:
 JUnit Vintage:ITStorageTest:testUpdateBlobReplaceMetadata
    MethodSource [className = 'com.google.cloud.storage.it.ITStorageTest', methodName = 'testUpdateBlobReplaceMetadata', methodParameterTypes = '']
    => java.lang.IllegalArgumentException: unable to create new instance of class com.google.cloud.storage.BlobInfo$ImmutableEmptyMap because it has no accessible default constructor
       com.google.api.client.util.Types.handleExceptionForNewInstance(Types.java:162)
       com.google.api.client.util.Types.newInstance(Types.java:117)
       com.google.api.client.util.Data.createNullInstance(Data.java:166)
       com.google.api.client.util.Data.nullOf(Data.java:134)
       com.google.cloud.storage.BlobInfo$BuilderImpl.setMetadata(BlobInfo.java:585)
       [...]
     Caused by: java.lang.InstantiationException: Type `com.google.cloud.storage.BlobInfo.ImmutableEmptyMap` can not be instantiated reflectively as it does not have a no-parameter constructor or the no-parameter constructor has not been added explicitly to the native image.
       java.lang.Class.newInstance(DynamicHub.java:909)
       com.google.api.client.util.Types.newInstance(Types.java:113)
       [...]

The resource-config.json file makes certain test resource accessible to the native image builder. Specifically, testNamesWhichCanFail.txt. It is currently located under src/test as it applies to only tests.
The native-image.properties file is located under src/test as it only applies to the tests :
This file handles class initialization during native image generation. Classes can be initialized at either run-time or image build time and class initialization can result in recursive initialization of other classes. The tests in the Storage repo use Parameterized which is explicitly initialized at image build time by the configurations provided by GraalVM. This leads to a bunch of other unexpected classes being initialized at build time as well and leads to the following error:
Error: Classes that should be initialized at run time got initialized during image building:
 com.google.cloud.conformance.storage.v1.RetryTests was unintentionally initialized at build time. To see why com.google.cloud.conformance.storage.v1.RetryTests got initialized use --trace-class-initialization=com.google.cloud.conformance.storage.v1.RetryTests
com.google.cloud.conformance.storage.v1.InstructionList was unintentionally initialized at build time. To see why com.google.cloud.conformance.storage.v1.InstructionList got initialized use --trace-class-initialization=com.google.cloud.conformance.storage.v1.InstructionList

And initializing those same classes at run-time results in image generation failing with inconclusive results:
Error: Classes that should be initialized at run time got initialized during image building:
 com.google.cloud.storage.conformance.retry.ITRetryConformanceTest$RetryTestCaseResolver the class was requested to be initialized at run time

Initializing these classes explicitly at build-time results in a successful build.

@BenWhitehead any idea why some checks are stalled at the moment?

Now the checks are running (Kokoro sample failed)

Feel free to merge when you're ready. The test failure in Samples is being dealt with separately and isn't related to any change here.

Thank you!


UXC-10 & 15: Cannot use semantic color for warning and say “error”. It should be either orange - warning or red - error

Description
UXC-10 & 15: Cannot use semantic color for warning and say “error”. It should be either orange - warning or red - error.
We should adjust highlights in extensions.

[x] severless https://github.com/kyma-project/serverless/pull/1032
[x] telemetry-menager https://github.com/kyma-project/telemetry-manager/pull/1211

Actual result

Processing/intermediate statuses shouldn't be red, make them grey (and remove the error icon)
Popover shouldn't be automatically closing once I've clicked on it
Could the text in the popover be more readable?
We couldn't reproduce an actual error to see if errors are now red
In the screenshots we again see different status wording, is this on purpose? Here I have two functions I created and one of them said "Pending" and the other one said "Building"

hi @vicslavova

https://github.com/kyma-project/serverless/pull/1184 - fix for badges color
Popover shouldn't be automatically closing once I've clicked on it - I can't reproduce that, please refresh the page and double-check
Could the text in the popover be more readable? - https://github.com/kyma-project/serverless/issues/1185
We couldn't reproduce an actual error to see if errors are now red - I checked, and they are red
They are two different states, if you need more details, you can ask @kwiatekus he is the PO of the team that is developing functions


unexpected EOF while parsing

when i run this code it is showing
error
unexpected EOF while parsing
how can i fix it AND Run the code

@shaantanu9  Share the code that's not working.


Feature to detect the PMJ presence/position

Description

New feature
Goal: Detect the presence/position of the PMJ on T2 or T1 images
Could be used for: separating brain/spine sections, croping an image or a centerline mask or a SC segmentation mask, analyzing the CSA between C3 and PMJ levels...etc.

Suggestion 1:
sct_detect_XX -i t2.nii.gz -c t2 -s t2_centerline.nii.gz

Function's name suggestions:

sct_dectect_pmj
sct_detect_brain_section

Output:

an image with one voxel with value = 50 (cf label_vertebrae convention) if PMJ detected, empty image if not (or no output?)

Flag description:

-c: Mandatory, {t1, t2}: there is one model for T2-like images and another for T1-like images
-s: Optional, SC segmentation file OR SC centerline file: could help if the PMJ is not clearly visible on the 2D mid-sagital slice because the detection is done on the 2D mid-sagital slice

Suggestion 2:
(---> If the PMJ detection is only used for cropping the centerline between brain and spine regions)
A module used by/integrated in sct_get_centerline instead of a new sct function

I would go with suggestion 1: sct_dectect_pmj. While I agree with suggestion 2, it is not incompatible with suggestion 1. We could write the function with the new proposed architecture by PO/George, i.e., having a module dectect_pmj that could be imported from other functions (e.g., sct_get_centerline). Having it in a standalone file allows more flexibility and visibility (if users go with "sct + TAB" to see all SCT functions).

Report 24 July 2017
Development on the branch called: cg_i1410
I have finished a first version of this function and I would like your advices on it.
Usage
DESCRIPTION
Detection of the Ponto-Medullary Junction (PMJ).
   This method is machine-learning based and adapted for T1w-like or T2w-like images.
   If the PMJ is detected from the input image, a nifti mask with one voxel, with the value 50,
   located at the predicted PMJ level, is output ("*_pmj.nii.gz").
   If the PMJ is not detected, anything is output from this function.

USAGE
sct_detect_pmj -i <file> -c {t1,t2}

MANDATORY ARGUMENTS
 -i <file>                    input image.
 -c {t1,t2}                   type of image contrast, if your contrast is not in the available
                              options (t1, t2), use t1 (cord bright / CSF dark) or t2 (cord dark /
                              CSF bright)

OPTIONAL ARGUMENTS
 -s <file>                    SC segmentation or SC centerline mask. Provide this mask could help
                              the detection of the PMJ
 -ofolder <folder_creation>   Output folder
 -qc {0,1}                    Output png image for quality control. Default value = 0
 -r {0,1}                     Remove temporary files. Default value = 1
 -v {0,1,2}                   Verbose: 0 = nothing, 1 = classic, 2 = expended Default value = 1

Terminal output
python sct_detect_pmj.py -i /Users/chgroc/data/i1410/t1/t1.nii.gz -c t1 -s /Users/chgroc/data/i1410/t1/t1_seg_manual.nii.gz -ofolder /Users/chgroc/data/i1410/t1 -qc 1 -r 0
Check folder existence...

Create temporary folder...
sct_crop_image -i t1.nii.gz -start 88 -end 88 -dim 2 -o t1_midSag.nii

Run PMJ detector

Ponto-Medullary Junction detected

Save quality control images...
QC output image: /Users/chgroc/data/i1410/t1/t1_sagittal_plane.png & /Users/chgroc/data/i1410/t1/t1_sagittal_plane_seg.png
WARNING: File t1_pmj.nii.gz already exists. Deleting it.
	x_pmj = 142
	y_pmj = 194
	z_pmj = 87

Save resulting file...

Done! To view results, type:
fslview /Users/chgroc/data/i1410/t1/t1.nii.gz /Users/chgroc/data/i1410/t1/t1_pmj.nii.gz -l Red -t 0.7 &

Script architecture
I have tried to follow the guidelines of Pierre-Olivier. I will ask him his opinion on it.
Quality control image

May be we want to adapt it in order to be integrated into sct_qc process?

It needed small changes in msct_image/save_quality_control in order to output a specific slice (index_slice parameter)

output a png image (small small red dot):

Any comment is more than welcome!

a few comments:

"...If the PMJ is not detected, anything is output from this function." --> did you mean "nothing is output"?
QC image: rotate it, and make the red spot way bigger. Alternatively, make a ~15x15mm green box centered around the PMJ (i prefer this option)
usage/output we can affine these details later

Few comments addressed and pushed.

nice, i would go for a flashy green:

Documentation (-help):
-s parameter shouldn't be there. It is too dangerous as segmentation/centerline usually don't reach the PMJ.

Results without straightening:
T1w:
Recall = 1.0
Precision = 0.987
Distance error = 0.46 +/- 11.37 mm

T2w:
Recall = 0.86
Precision = 0.888
Distance error = 0.108 +/- 13.59 mm


Update ChatClient.java

cool..what do you think @avijit1258 ?

merged the commit. @NyorJa

thankz
On Mon, Dec 10, 2018, 5:09 PM Avijit Bhattacharjee<EMAIL_ADDRESS>wrote:

merged the commit. @NyorJa https://github.com/NyorJa
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/avijit1258/ChatApplicationJava/pull/15#issuecomment-445742219,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHxVkl-JPYhD1VQM0uFy0dloIe9_jxXqks5u3iTXgaJpZM4ZEq-t
.


fix address spelling

https://en.wiktionary.org/wiki/adress: "Misspelling of address."

Thanks! I knew there was somewhere a version with both two Ds and Ss.


Web Activity Documentation For Handling HTTP 202

It appears that Data Factory's Web Activity will gracefully handle an API or service that returns an HTTP 202 and in the case of Azure Durable Functions wait for up to the activity's timeout (default of 7 hours) before returning the output from the durable functions status endpoint.
This is a great feature! However, it is not documented anywhere in the documentation for the web activity. The documentation also states that this request will timeout after 1 minute which is untrue if that service is a durable function.
Some additional details as to how and when it performs this would be helpful. Some note about how this performs differently than if you use the Azure Function activity and call a durable function would also be helpful. There are quite a few posts around the internet advising people who are calling a durable function in Data Factory to use the Azure Function activity and implement a polling loop to wait for the results (such as http://datanrg.blogspot.com/2020/12/using-azure-durable-functions-with.html). This is much simpler if you just use the Web Activity.

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

ID: 34b3d465-6a2b-88ad-6e80-4fb784cd489e
Version Independent ID: 51b70888-d089-7352-4abd-7d587726700a
Content: Web Activity - Azure Data Factory & Azure Synapse
Content Source: articles/data-factory/control-flow-web-activity.md
Service: data-factory
Sub-service: orchestration
GitHub Login: @nabhishek
Microsoft Alias: abnarain

Thanks for the feedback! We have assigned the issue to the content author to further review this and update the document as appropriate.

@jesseryoungVUMC Thanks for bringing this up. We have updated the doc through this PR https://github.com/MicrosoftDocs/azure-docs-pr/pull/190326. It adds a note that web activity support async request-reply (202) pattern.

#Please-close

@nabhishek - has your change made it into the official docs repo yet? The last change I see for this file is https://github.com/MicrosoftDocs/azure-docs/commit/f2fb2ee1182430c7c906e803f6386a6e1c02120f but it looks like that's referencing the response timeouts and not the http 202 behavior.

Not only isn't it written in the docs yet. It only seems to work with an orchestrator function. I created an API with the same functionality (returns 202 AND "Retry-After: 5" header) when running and 200 when completed, but the web activity does not poll the result. Are there other requirements?

I came here in a search for what it does with 202 responses. Why was this issue closed? I have yet to find details on how it handles these types of responses.


evalv3: Significant memory consumption increase over v2

What version of CUE are you using (cue version)?
Our service is executing the go API at the following commit of master:
	cuelang.org/go v0.11.0-alpha.3.0.20241010142549-44cceca80690

Does this issue reproduce with the latest stable release?
With evalv3 enabled yes.
What did you do?
I currently do not have a trimmed down example of our configuration that explicitly exercises the higher consumption. I can certainly provide some private source and/or demo this issue to help narrow down where this may come from.
What did you expect to see?
Less memory usage than v2.
What did you see instead?
Below are some pprof graphs that show V2 vs. V3 evaluation run against the exact same configuration set:

Notice the heap on the v3 evaluator is almost 6x larger than the v2 evaluator.

Dupe of #3372


Settings profile feature regression since 1.76.0

Type: Bug
Hi, I was an early user of the experimantal settings profile feature, and the functionality used to worked before 1.76, and also back when it was still an experimental feature.
Since I have distinct sets of user settings between my personal vscode and my workspace vscode, I defined a profile named 'cat' for my workplace and I use the default one for my personal use.
Problem since 1.76: when I open a workspace/a new window/reopen in container/and in some other cases of opening, the current Settings profile would sometimes unexpectedly change from the one I use at work 'cat' to the Default one. This didn't happen before.
I also, encountered issues with my profile extensions not being installed when I create a devcontainer. Similarly, I use wsl at work, and since this week, when i open a window in wsl I don't see any installed extension on the wsl remote when using my 'cat' profile settings, even though the ~/.vscode-server/extensions contains all extensions I have already installed.
The settingss profile seem to have been broken  in many ways since 1.76.

I also, encountered issues with my profile extensions not being installed when I create a devcontainer. Similarly, I use wsl at work, and since this week, when i open a window in wsl I don't see any installed extension on the wsl remote when using my 'cat' profile settings, even though the ~/.vscode-server/extensions contains all extensions I have already installed.

I think this is tracked and answered here https://github.com/microsoft/vscode/issues/176275

when I open a workspace/a new window/reopen in container/and in some other cases of opening, the current Settings profile would sometimes unexpectedly change from the one I use at work 'cat' to the Default one. This didn't happen before.

Can you please provide steps to reproduce this behaviour?

okay, I'll find some free time to explain steps.
But before, I might have a comment related to scoping settings profile per remote: I woud normally rely on the setting "dev.containers.defaultExtensions" to automatically install extensions in my new devcontainers, but this setting only applies in the default settings profile and there seems to be no way to make this setting apply when creating a new devcontainer. That's annoying, because now I need to explicitly copy paste the the list of extensions to any new devcontainer I create.

I experienced another variant of this same issue today. Last week I when closing my last vscode window, it was using my non default work profile. This morning, I logged in then I opened a first empty vscode window.
Expected behavior: the vscode window uses the same profile that was used in the last closed vscode instance on my workplace machine.
Actual behavior: the vscode window was using my default profile

May you offer a feature to let user select the default profile, or use a profile file to totally replace the Default profile?

I would also like to see some way to reset or change the default profile because I use the settings sync and somehow my default profile got messed up where certain extensions keep getting installed even when I uninstall them they remain in the default profile and so when I create new codespaces it automatically opens the default profile and installs a bunch of extensions that I don't want.

I would also like to be able to set the profile that is opened by default for an installation of VS Code. I work on OS X and Windows, and have a different profile for each. I use settings sync. I'd like VS Code to always open with the correct profile.

May you offer a feature to let user select the default profile, or use a profile file to totally replace the Default profile?

But up to now, this default profile has not been replaced. sad. >-<

I see this issue has been side tracked from comment onwards.
To replace default profile please follow https://github.com/microsoft/vscode/issues/168867

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

You can now associate a profile for new window using the setting window.openFilesInNewWindow For more information please refer to this issue - https://github.com/microsoft/vscode/issues/194105#issuecomment-2129939753
Therefore, I am closing this issue in favour of above setting. Please use this feature and provide your feedback.


Unable to play the audio on iOS because the file path is getting corrupted

Please fill the template to help you out. Also, please try the Example project compare before submiting the issue when you have certain issue with your project setup.

Version of react-native-audio-recorder-player - "react-native-audio-recorder-player": "^3.5.3"
Version of React Native - "react-native": "0.68.5"
Platforms you faced the error (IOS or Android or both?) - iOS
Expected behavior - Audio should play if the file is available in the storage
Actual behavior - Audio is not getting played on iOS
Steps to reproduce the behabior:
@hyochan, first of all, a big thanks to this awesome package!
I found an issue that makes it impossible for me to play audio on iOS:
const path = `${RNFS.CachesDirectoryPath}/${Date.now()}audioOut.mp3`;
const audioPlayedFromPath = await audioRecorderPlayer.startPlayer(path);

For me, on both the iOS simulator and in device, if given like the above, the audioPlayedFromPath is getting corrupted/repeated as below:
file:///var/mobile/Containers/Data/Application/5E03275B-C193-4ABE-809A-8D8C7C1B8252/Library/Caches//var/mobile/Containers/Data/Application/5E03275B-C193-4ABE-809A-8D8C7C1B8252/Library/Caches/1681391103391audioOut.mp3
Because of this, I had to manually add file:// and then the issue is resolved.
const path = `${RNFS.CachesDirectoryPath}/${Date.now()}audioOut.mp3`;
await audioRecorderPlayer.startPlayer(`file://${path}`);

I'm open to give any further info or to create a PR if needed.

maybe u are facing this problem because u are using .mp3 format
when recording library throws error when u are trying ot record smth using mp3 format, maybe the same issue is appearing when u are playing sound, try using m4a format, works both IOS and Android


Fix va_args build error in Xcode 9

Fixes #340

Thanks, Accept this answer :))

How about a release now that Xcode 9 is out?


[web][api][SIMS #1078]View and approve a Student Change Request

Created the "View request" button t redirect to the Student Appeal approval page, as shown below.

Created a common component to render the Appeals Requests and the common approval form, as shown below.

Readonly view

Created a new property to formio component called scoped to allow the same formio definition to be rendered multiple times on the same page and avoid HTML id conflicts.

Upcoming changes in the next PR

Prevent a new assessment to be created if there is already one in progress or submitted;
Add a "View request" to show the "Student Requests" form in read-only;
Change the Student Appeal request form to use the same component;
Create a specific note type (using general for now);
Formio definitions.

Great work @andrewsignori-aot.
Thanks for identifying and resolving issues like same form definition being used multiple times with scoped ,form validation util, DTO refactoring etc.
Please have a look at the comments.


Remove protocol parameters from NodeStateAdaptor

Context

The wallet backend requires to know a few of the underlying blockchain protocol
parameters. Those parameters may change over time through updates, at epoch
boundaries. At the moment, nodes are keeping track of those parameters, and the
wallet reads them using some shared context via the NodeStateAdaptor.
Decision

Extend the monitoring API of cardano node to expose protocol parameters (This
can be done by extending the /api/v1/node-settings API endpoint.

Use the extended monitoring API instead of the current NodeStateAdaptor to
fetch protocol parameters and removes them from the current
NodeStateAdaptor.

Add a thin caching layer on top of our http client to only fetch parameters
if the epoch has changed. This cache doesn't need to be persisted and be
stored in plain memory and its usage should be transparent for the wallet
backend.

Acceptance Criterias

Protocol parameters available through the NodeStateAdaptor must be
identified and made available through the node monitoring API
The wallet backend must resolve those parameters from the node monitoring
API its connected to
The wallet backend should cache the results from the API and only refresh
them at epoch boundaries.

Development Plan

Proof of concept
Quick hack to see if everything works when protocol parameters are sent via the API.

[x] List all fields of NodeStateAdaptor / uses (and later: motivate which ones we care about)
[x] Serve some NodeStateAdaptor field via the node API
[x] Call Node API from Wallet as proof of concept
[x] Have integration tests compiling
[x] Have integration not failing because of TLS settings
[x] Have an idea for caching

Wire it up in a proper way

~Revisit TLS Settings and ensure no paths are hard-coded~ Matt did this
~Ensure no localhost/port etc are hardcoded~ Matt did this
[x] Ensure JSON instances are properly decoupled (they are handwritten, so…)
[x] Merge protocol-parameters endpoint with node-settings. I'm delaying this to have more options for caching.
[x] Deal with the first easy protocol parameters
[x] Deal with getCoreConfig Not needed
~Deal with withNodeState~ Separate issue
[x] Actually start the server from the wallet itself (this was missed initially)

Finalizing

~Caching and invalidation~ Separate issue
[x] Error handling — think so, and retries
~Figure out a way to test and ensure this works as expected across epoch boundaries with updated protocol parameters.~ Needed for when we add caching, but not now.
[x] Ensure that problems with node-api-to-wallet communication fail in an appropriate way

PR

Number
Base

input-output-hk/cardano-sl#3930
develop

#215
develop

input-output-hk/cardano-sl#4005
develop

#246
develop

#257
develop

#283
develop

#314
develop

QA

Criteria
Coverage

1.
TODO: Hm…

2.
The implementation of the NodeStateAdaptor fields themselves have changed, and therefore this is fulfilled.

3.
Will be tackled in a separate ADR (#240)

This is an under-the-hood change that only changes the way protocol parameters are retrieved by NodeStateAdaptor — now via the node monitoring HTTP API — instead of directly. Existing tests should verify that everything still works.
The node should be on localhost, and the connection should be flawless. If not, we get:
There was an error connecting to the node: ErrFromServant (ConnectionError "HttpExceptionRequest Request {\n  host                 = \"<IP_ADDRESS>\"\n  port                 = 8080\n  secure               = True\n  requestHeaders       = [(\"Accept\",\"application/json;charset=utf-8,application/json\")]\n  path                 = \"/api/v1/node-settings\"\n  queryString          = \"\"\n  method               = \"GET\"\n  proxy                = Nothing\n  rawBody              = False\n  redirectCount        = 10\n  responseTimeout      = ResponseTimeoutDefault\n  requestVersion       = HTTP/1.1\n}\n (InternalException (HostCannotConnect \"<IP_ADDRESS>\" [Network.Socket.connect: <socket: 49>: does not exist (Connection refused)]))")

simulated using

diff --git a/src/Cardano/Wallet/Kernel/NodeStateAdaptor.hs b/src/Cardano/Wallet/Kernel/NodeStateAdaptor.hs
index 95bc15816..accd04d81 100644
--- a/src/Cardano/Wallet/Kernel/NodeStateAdaptor.hs
+++ b/src/Cardano/Wallet/Kernel/NodeStateAdaptor.hs
@@ -641,7 +641,7 @@ instance Exception NodeCommunicationError
 --
 toMonadIO :: (MonadIO m, MonadThrow m, Show e) => ExceptT e m a -> m a
 toMonadIO = retrying' . runExceptT >=> \case
-    Right a   -> return a
+    Right _   -> throwM . NodeCommunicationError $ ("Artificially failing")
     Left  err -> throwM . NodeCommunicationError $ ("There was an error communicating with the node: " <> show err)

   where

I believe the following capabilities are the ones affected by this change (but as said, only internally):
- Restoration
- Normal block application — BListener
- Sending ADA (POST /api/v1/transactions)
- New unsigned transaction (POST /api/v1/transactions/unsigned)
- New externally signed transaction (POST /api/v1/transactions/externally-signed)
- Redeem a certificate (POST /api/v1/transactions/certificates)
- Estimate fees (POST /api/v1/transactions/fees)

Retrospective

I did not foresee the struggle with Swagger and Aeson instances

Notes:
Which protocol parameters?
I believe it was these (?):
    , getTipSlotId :: m SlotId

      -- | Get maximum transaction size
    , getMaxTxSize :: m Byte

      -- | Get fee policy
    , getFeePolicy :: m TxFeePolicy

      -- | Get the security parameter (@k@)
    , getSecurityParameter :: m SecurityParameter

Where / how are they used
getTipSlotId

Cardano.Wallet.WalletLayer.Kernel.Transactions.getTransactions
Cardano.Wallet.WalletLayer.Kernel.Transactions.toTransaction

getMaxTxSize

Cardano.Wallet.WalletLayer.Kernel.Transactions.newUnsignedTransaction

getFeePolicy

Cardano.Wallet.WalletLayer.Kernel.Active.pay
Matches in tests (excluded)

getSecurityParameter

RelatingWalletSpecToCardano.md
NodeStateAdaptor.hs
Cardano.Wallet.Kernel.Restore.restoreWalletHistoryAsync.restore
Cardano.Wallet.Kernel.Restore.restoreWalletHistoryAsync.finish
Cardano.Wallet.Kernel.BListener.applyBlock
Cardano.Wallet.Kernel.Blistener.switchToFork

I thought I'd look into what endpoints are affected for 1) the sake of testing 2) my own sake, and 3) might be useful later for removing withNodeState.

NodeStateAdaptor proviedes access to fields, ~"protocol parameters", over the node monitoring
api. Where are they used?
Note: withNodeState x does not rely on the node monitoring api.
What functions rely on the Node API?
I used :Ag walletNode
Cardano.Wallet.WalletLayer.Kernel.Active

pay (feePolicy)
estimateFees (feePolicy)
createUnsignedTx

Cardano.Wallet.WalletLayer.Kernel.Transactions

toTransaction (slotCount, tipSlotId)

Used as getTxFromMeta for newTransaction

Cardano.Wallet.Kernel.Restore

restoreWallet (coreConfig, withNodeState getWalletInitInfo)
mkPrefilter
... (many, many more, ignoring)

Cardano.Wallet.Kernel.Transactions

newUnsignedTransaction (maxTxSize)
submitSignedTx (getCreationTimeStamp)
newTransaction (getCreationTimeStamp)
redeemAda (getCreationTimestamp, withNodeState filterUtxo)

Cardano.Wallet.Kernel.BListener
This module will be replaced. It will probably use something from NodeStateAdaptor still.
What features rely on the Node API?
I followed the functions above to the handlers

Restoration
Normal block application — BListener
Sending ADA (POST /api/v1/transactions)
New unsigned transaction (POST /api/v1/transactions/unsigned)
Estimate fees (POST /api/v1/transactions/fees)
New externally signed transaction (POST /api/v1/transactions/externally-signed)
Redeem a certificate (POST /api/v1/transactions/certificates)

@Anviking , If I understand correctly there are now new parameters available now on node-settings endpoint and from there they are now being read by wallet backend?
Where there any new tests added for that?
In particular, perhaps it is a good opportunity to extend the integration test for node-settings (https://github.com/input-output-hk/cardano-wallet/blob/809246c524873afddcfe10ee70b15888e84913fd/test/integration/Test/Integration/Scenario/Node.hs#L18) adding more assertions that make sure all the expected parameters are actually being exposed, what do you think? :)

@piotr-iohk

If I understand correctly there are now new parameters available now on node-settings endpoint and from there they are now being read by wallet backend?

Yes

Where there any new tests added for that?

No :D

that make sure all the expected parameters are actually being exposed

👍 This should already be verified by the existing test, as Client.getNodeSettings will unmarshall JSON to the NodeSettings record. If we were to use another node server with different json format, Integration/Scenario/Node.hs should fail.

:+1:


fs: Allocate file/socket dynamically

Summary
Allocate file/socket dynamically.
Impact
Dynamically allocated file descriptor for every task can reduce ram, especially super task in a project.
Testing
daily test

@Donny9  is there a set of PRs for this that need to come in in some order?

@Donny9 is there a set of PRs for this that need to come in in some order?

yes, This patch associates with apache/incubator-nuttx-apps#609，it need to merge firstly.

depends on https://github.com/apache/incubator-nuttx-apps/pull/612

It seems that CI cancel "Build Documentation" accidently, all other check finish without any problem. So let's ignore the false alarm.

@xiaoxiang781216 @Donny9
Hmm, it seems that telnetd can not accept an incoming connection again.
Could you please check lm3s6965-ek:discover with QEMU?

@xiaoxiang781216 @Donny9
Hmm, it seems that telnetd can not accept an incoming connection again.
Could you please check lm3s6965-ek:discover with QEMU?

Okay. I check it

@xiaoxiang781216 @Donny9
Hmm, it seems that telnetd can not accept an incoming connection again.
Could you please check lm3s6965-ek:discover with QEMU?

@masayuki2009  please apply this patch to fix this issue: https://github.com/apache/incubator-nuttx-apps/pull/619. Thank you very much.


bookletimposer: add new package

BookletImposer: new package
This is a pdf manipulation tool
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested basic functionality of all binary files (usually in ./result/bin/)
[x] Tested basic functionality of all binary files for 22.05 (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

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

1 package built:

bookletimposer

Can you add the backport release-22.05 tag? I tested it works fine there too.

@felschr can you add the backport release-22.05 tag and merge this? I don't have merge rights

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/546

I added the tag, but I don't have merge rights either. The Discourse thread linked above is useful to get more attention for an already reviewed PR.


Certain characters now always displayed as HTML entities

Following some apparent server updates last week, it looks like certain characters always come back as entitles: &,>, and < etc. Even if you save the buffer, the next load or update converts. Most likely happens on the server, but should be (like in the SimpleNote web and app clients) masked.
This is problematic both for Markdown formatting (> means something in md) and perhaps as well for those who need to put entities in their notes: &amp; looks insane.
If the common entities could be shown in the buffer as the standard character, it would be much more usable.

However... if you set the filetype as markdown it looks like it behaves. Will try to look into this and figure out what they've changed.

 Using vim-markdown and believe it is up to date.

Strange. If I have the buffer open and update it externally, and then :SimplenoteUpdate it seems to be correct, but if I close VIM and open up everything without the buffer being open, it is all madness again... Just FYI.

Fix for this in Simplenote.py. Although I've written a test for it I've not actually done extensive testing of it yet. I'm going to do a bit more testing, then do a new release of Simplenote.py and then a new release of Simplenote.vim.
I really don't have a lot of spare time anymore hence why I'm much less active than I used to be here

I've bumped the simplenote.py version with the fix. Tomorrow I'll do the simplenote.vim one (hopefully).

Excellent! Thanks! Talked with someone in support from SimpleNote and they were unhelpful, mostly due to the fact that it wasn't happening in their app or web client...

 Should all be sorted now.


Simplify tabs to make them more obvious interaction targets

This has been completed, and we're now A/B testing the new design against the original skeuomorphic cards


MeshBender and SourceMesh are incredibly slow due to recalculating normals

MeshBender is slow and causes significant frame loss when adjusting nodes. I ran a deep profile when bending a mesh of 1720 vertices and discovered that SourceMesh.BuildData() was taking ~300ms to run and updating mesh normals in a nested loop. I hoisted Mesh.normals out of the loop saw significant performance improvement without a loss of accuracy.

Building the mesh data is indeed slow but mandatory I'm afraid as the
normal of the vertices must be precisely bent for a correct illumination of
the mesh in all situations.
What you may have missed is that this method is extracted from the very
bending process, so it is not run at each frame. In fact, the data has to
be rebuilt only when you change the mesh or one of its parameters, which is
not supposed to occur very often, and certainly not each frame.
If you really need to build mesh data every frame, could you please
describe your use case?
Le dim. 13 sept. 2020 à 18:36, Greg Rogers<EMAIL_ADDRESS>a
écrit :

MeshBender is slow and causes significant frame loss when adjusting nodes.
I ran a deep profile when bending a mesh of 1720 vertices and discovered
that SourceMesh.BuildData() was taking ~300ms to run and updating mesh
normals in a nested loop
https://github.com/benoit-dumas/SplineMesh/blob/0678d8a00cf7863e7cf58970c530cc9ad925056c/Assets/SplineMesh/Scripts/MeshProcessing/SourceMesh.cs#L130.
I hoisted Mesh.normals out of the loop saw significant performance
improvement without a loss of accuracy.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/benoit-dumas/SplineMesh/issues/36, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5QKTV5WTJQPD7EH4PRBSDSFTYIFANCNFSM4RKYDYKA
.

Hit a similar scenario, maybe my case helps as example @methusalah.
Im placing ropes from pole to pole. During the placement of new poles, player can move the aim around the environment to pick the destination, while seeing a dummy rope -originating on an existing pole- following the aim. This requires the mesh to be rebuilt every frame. I will check @rogerscg approach, because on the dummy rope I really dont need accurate mesh lighting.
Thank you for your work!

The method FillRepeatStretch is as slow as the number of vertices in the mesh. The method can be drastically improved with a ParallelForEach or Unity's Jobs, as the computation on each vertices is independent and can be run simultaneously (mult-threaded). This will require to change the way the data is organized, though, but is definitely a good direction if you wish to have a faster update.
Another optimisation would be to send the computation to the GPU but this is far from being a trivial implementation, and has many disadvantage to consider, like the computation being one or more frame late, and the bent mesh not being readable on the CPU side, which is bad in a lot of situations (e.g. if you need to update a mesh collider).
If you go down the multi-threading route, I would be happy to take a look at the result or even implement it in SplineMesh.
Have fun bending things ^^

Turns out the mesh related works were only a part of the issue. A big chunk was consumed by the triggering of unrequired events (on this context) on nodes Position and Direction properties, so created a method for setting them with optional event calling. CreateMeshes() was very unoptimized so in my case was doing per frame stuff that could be made only once, including GetComponent() calls, reworked it. Also FillRepeatStretch indiscriminately allocated lists, producing constantly kicking-in of the GC, so moved those lists to pooling. I checked also some stuff happening at OnEnable at Spline and SplineMeshTilling classes that resulted less than ideal for runtime use, where you show/hide objects for gameplay reasons constantly. Also adjusted the X scale of the mesh to prevent unnecessary mesh tilling. The result, even after the same mesh stuff done as before (without the jobs rework) is drastically better. Overall, it looks like for runtime use the SplineMesh could take some improvements. If time allows, at some point I'll offer some PR that may alleviate the overall situation.
Again, thank you Meth!


Tales of Hearts R: Infinite Evolve [PCSG00163]

App summary

App name: Tales of Hearts R: Infinite Evolve
App serial: PCSG00163
App version: 1.0

Vita3K summary

Version: v0.1.6
Build number: 2805
Commit hash: https://github.com/vita3k/vita3k/commit/67c1eb4c
CPU backend: Dynarmic

Test environment summary

Tested by: othmanead
OS: Windows 11
CPU: Intel i5-10300H
GPU: RTX 3060 mobile
RAM: 16 GB

Issue:
Game is playable but enemies don't die and you don't take damage (the damage taken or done is shown on screen) so the first level can't be completed
Screenshots:

Log
vita3k.log
Recommended labels

Ingame-

@othmanead this is FistingUranus aka Pegi, this game can be marked as perfect, performance have no issue and theres 0 bugs.


Other users updating synced user

Users that are not the user that is setup are having their play status' updated on the user setup for sync
User X is setup on two plex servers and for both the match user and uuid set for true
snippet from servers.yaml file
  user: 375432
  import:
    enabled: true
    lastSync:<PHONE_NUMBER>
  export:
    enabled: true
    lastSync:<PHONE_NUMBER>
  webhook:
    import: true
    push: true
    match:
      user: true
      uuid: true
    token: *********************************
  persist: {  }

When users Y or Z watch something and its completed user X watch status sets that they have watched the same episode

Alright, lets start by debugging the webhook payload please, edit your docker-compose.yaml under the enviroment key add
WS_WEBHOOK_DEBUG: true and restart the container, after doing so, check your config/webhooks/ for webhooks payload. any provide the cParsed section it should have enough information to tell why it's happening.

this the right part:
"parsed": {
        "payload": "{\"event\":\"media.play\",\"user\":false,\"owner\":true,\"Account\":{\"id\":26608833,\"thumb\":\"https://plex.tv/users/a4cda4baa8b131b8/avatar?c=1647607097\",\"title\":\"4craigmc\"},\"Server\":{\"title\":\"Ian's Media Server\",\"uuid\":\"d7b5c5528d3172c2dde373e4936f0b7fa8598720>

4craig is the user whos status will show up

Sorry you wanted this I think
    "cParsed": {
        "event": "media.play",
        "user": false,
        "owner": true,
        "Account": {
            "id": 26608833,
            "thumb": "https://plex.tv/users/a4cda4baa8b131b8/avatar?c=1647607097",
            "title": "4craigmc"
        },
        "Server": {
            "title": "Ian's Media Server",
            "uuid": "d7b5c5528d3172c2dde373e4936f0b7fa8598720"
        },
        "Player": {
            "local": false,
            "publicAddress": "<IP_ADDRESS>",
            "title": "BRAVIA VH1",
            "uuid": "9f02ce053f4094c1-com-plexapp-android"
        },
        "Metadata": {
            "librarySectionType": "show",
            "ratingKey": "791313",
            "key": "/library/metadata/791313",
            "parentRatingKey": "791312",
            "grandparentRatingKey": "791311",
            "guid": "plex://episode/617803a0a0cf35687573fe15",
            "parentGuid": "plex://season/6176985422d40dd252f8fe91",
            "grandparentGuid": "plex://show/5d9c08c07b5c2e001e660bdd",
            "type": "episode",
            "title": "Unlucky in Love",
            "grandparentKey": "/library/metadata/791311",
            "parentKey": "/library/metadata/791312",
            "librarySectionTitle": "TV Shows",
            "librarySectionID": 1,
            "librarySectionKey": "/library/sections/1",
            "grandparentTitle": "American Monster",
            "parentTitle": "Season 7",
            "contentRating": "TV-14",
            "summary": "A woman's hopeful dreams of true love disintegrate into a deadly nightmare.",
            "index": 1,
            "parentIndex": 7,
            "viewCount": 1,
            "lastViewedAt":<PHONE_NUMBER>,
            "thumb": "/library/metadata/791313/thumb/1647218077",
            "art": "/library/metadata/791311/art/1647218072",
            "grandparentThumb": "/library/metadata/791311/thumb/1647218072",
            "grandparentArt": "/library/metadata/791311/art/1647218072",
            "grandparentTheme": "/library/metadata/791311/theme/1647218072",
            "originallyAvailableAt": "2021-10-23",
            "addedAt":<PHONE_NUMBER>,
            "updatedAt":<PHONE_NUMBER>,
            "Guid": [
                {
                    "id": "tmdb://3302871"
                },
                {
                    "id": "tvdb://8801335"
                },
                {
                    "id": "plex://episode/617803a0a0cf35687573fe15"
                }
            ]
        },

Alright, could look for log failed affixed by media.scrobble, and could you list the cParsed and attributes of those logs, please remove SERVER_ID, and out of interest is the user being reported a home or managed or external user?

   "cParsed": {
        "event": "media.scrobble",
        "user": false,
        "owner": true,
        "Account": {
            "id": 26608833,
            "thumb": "https://plex.tv/users/a4cda4baa8b131b8/avatar?c=1647607097",
            "title": "4craigmc"
        },
        "Server": {
            "title": "",
            "uuid": "d7b5c5528d3172c2dde373e4936f0b7fa8598720"
        },
        "Player": {
            "local": false,
            "publicAddress": "<IP_ADDRESS>",
            "title": "BRAVIA VH1",
            "uuid": "9f02ce053f4094c1-com-plexapp-android"
        },
        "Metadata": {
            "librarySectionType": "show",
            "ratingKey": "791388",
            "key": "/library/metadata/791388",
            "parentRatingKey": "791378",
            "grandparentRatingKey": "791311",
            "guid": "plex://episode/60143277b60726002cf46cf0",
            "parentGuid": "plex://season/606f061f65d1b6002ce0b2d6",
            "grandparentGuid": "plex://show/5d9c08c07b5c2e001e660bdd",
            "type": "episode",
            "title": "Ghost From the Past",
            "grandparentKey": "/library/metadata/791311",
            "parentKey": "/library/metadata/791378",
            "librarySectionTitle": "TV Shows",
            "librarySectionID": 1,
            "librarySectionKey": "/library/sections/1",
            "grandparentTitle": "American Monster",
            "parentTitle": "Season 6",
            "contentRating": "TV-14",
            "summary": "In 2017, an unimaginable betrayal leads to the death of a woman in the state of Louisiana. Police discover she has been murdered by her estranged husband.",
            "index": 10,
            "parentIndex": 6,
            "viewCount": 3,
            "lastViewedAt":<PHONE_NUMBER>,
            "thumb": "/library/metadata/791388/thumb/1647218117",
            "art": "/library/metadata/791311/art/1647218072",
            "grandparentThumb": "/library/metadata/791311/thumb/1647218072",
            "grandparentArt": "/library/metadata/791311/art/1647218072",
            "grandparentTheme": "/library/metadata/791311/theme/1647218072",
            "duration": 2520000,
            "originallyAvailableAt": "2021-01-30",
            "addedAt":<PHONE_NUMBER>,
            "updatedAt":<PHONE_NUMBER>,
            "Guid": [
                {
                    "id": "tmdb://2684962"
                },
                {
                    "id": "tvdb://8171274"
                },
                {
                    "id": "plex://episode/60143277b60726002cf46cf0"

The user reported is a external user.   No home users have watched anything since setup

Hmm, this is completely unexpected, i initially thought the webhook is tied to PlexPass user account, not sure what the hell is plex doing triggering webhook event for completely unrelated account.
I have to dig deeper to to understand this, I'll get back to you hopefully today or tomorrow.

Ok i spotted source of the problem and already fixed it, However in my testing i discovered another problem, Please report the main user as 1 regardless of the ID provided by plex.tv users API, which present another problem. i should have a fix for you soon, on unrelated note if your account is the main account set the user: to user: 1 in the meantime

I stopped the container for now and can live without till you want to test something else.  I can set whatever if you want me to test something else however.

Yeah, dont worry about it i should have someone for you within hour

Alright, i think i have fixed your initial problem, once the builds complete pull the updated container and do the following
$ docker exec -ti watchstate console servers:edit --key user --set 1 -- [PLEX_SERVER_NAME]

once that done only the main user account data will be synced.

@ikolsteren The updated containers are live now, please try when you have a chance and drop a comment to know your status.

Running update.  That problem looks to be solved.
will continue to get setup and working between my servers.

The new build is running, once it's finished, please pull the new container and try again, you should get a clear error message in regard to why the request has failed to process. for example you will be shown in the logs something like
watchstate    | response_status: 401 - response_text: "exact_error_message" - .....

As we discussed in discord it seems this issue is fixed. and it's not tool related problem.


AttributeError: 'LightningDistributedDataParallel' object has no attribute '_sync_params'

I got the same error as the title.
I think it's a library version issue like pytorch, so could you tell me the versions of your libraries?

seems to be an issue with pytorch lightning. I believe I used 0.10. please see the environment.yml file

Hi, have you solved this problem? I have the same issue and I use pytorch lightning0.10.0, but this error didn't disappear, could you please show me how you fix it? all the best:)

@OvOtoQAQ did u remove other versions of lightning

@OvOtoQAQ did u remove other versions of lightning

@Ir1d yeah, I think so. I've tried 3 different virtual environments and all kinds of combination, I usually first install lightning==0.10.0 then install torch compatable with cuda11.4, but it always raises an error:(

I think I have tested on cuda10.2 and cuda11.1 before but not on 11.4

I think I have tested on cuda10.2 and cuda11.1 before but not on 11.4

I install cuda11.1 and finally it begins to train! Maybe it's all about fortune.
for who may face the same issue:
you should first make sure your torch compatible with lightning 0.10
for cuda11.1 I use torch==1.10
and you should set num_workers=0 in sinnerf.py
if  RuntimeError:DataLoader worker (pid *** ***) exited occurs
anyway, thanks for your patience, wish you all the best:)

I think I have tested on cuda10.2 and cuda11.1 before but not on 11.4

It seems the problem still exists, I used your command "pip install -r requirement.txt", I checked the version in the python command environment:

torch.version
'1.12.1+cu102'


Two redirects in router and child router

I saw strange behaviour of aurelia router when i was using router with one child router and both of them use redirect parameter in router configuration. I have prepared forked repository of skeleton-navigation repository where my problem is implemented:
https://github.com/milunka/redirect-problem
For quick review, this is what i am talking about:
app.js - this viewmodel has defined only one route where empty route is redirecting to defined route
import {inject} from 'aurelia-framework';
import {Router} from 'aurelia-router';

@inject(Router)
export class App {
  constructor(router) {
    this.router = router;
    this.router.configure(config => {
      config.title = 'Aurelia';
      config.map([
        { route: 'child',       moduleId: './appChild',      nav: true, title:'Welcome' },
        { route: '', redirect: 'child' }
      ]);
    });
  }
}

appChild.js - in this viewmodel is again empty route which redirects to defined route
import {inject} from 'aurelia-framework';
import {Router} from 'aurelia-router';

@inject(Router)
export class AppChild {
  constructor(router) {
    this.router = router;
    this.router.configure(config => {
      config.title = 'Aurelia';
      config.map([
        { route: 'welcome',       moduleId: './welcome',      nav: true, title:'Welcome' },
        { route: '', redirect: 'welcome' }
      ]);
    });
  }
}

After i try to access application root (http://localhost:9000) i receive error Illegal module name "", same error is displayed when i try to access route after first redirect (http://localhost:9000/#child). Only url which works is whole route to welcome page (http://localhost:9000/#child/welcome).
I think that both url (http://localhost:9000 and http://localhost:9000/#child) may works, but maybe i just didn't understand redirect parametr in router configuration.

+1 for fixing this

Is this still a problem? Any workaround?


Broken search in v2.2.6

In v2.2.6 search does not work, but it's ok in 2.2.5.

I can confirm with version 2.2.9


New F3 Mod

Mod name
BetterF3
Curseforge link
https://www.curseforge.com/minecraft/mc-mods/betterf3
Other links
https://github.com/cominixo/BetterF3
What it does
BetterF3 is a mod that replaces Minecraft's original debug HUD with a highly customizable, more human-readable HUD. You can customize colors, position, add spacings, and more
Why should it be in the modpack
Its is much easier to read the words in the debug menu for laptop users.
Why shouldn't it be in the modpack
The F3 menu has colours?
Categories
New feature
Additional details
No response

F3 screen is a debug menu, which means 80%-90% of people should not actually need it on a daily basis. If all you need is FPS or coordinates, there are options for that in Sodium Extra.


Feature Request: Dead zone after buttons on bottom of screen

Expected behaviour
There should be an option for a "dead space" underneath the K9 buttons so it's not right next to the bottom of the screen.
Actual behaviour
My Samsung Galaxy S4 has buttons at the bottom of the screen. Whenever I go to press the "Back" button on the phone while in K9, I invariably hit the Create New Message button instead. Then I have to Menu -> Discard to get rid of the message I just accidentally created.
Steps to reproduce

Start K9 and read a mail message
Try to hit "Back" on a Samsung Galaxy S4 with fat fingers.
You've just created a new draft!

Environment
K-9 Mail version: 5.010
Android version: 4.4.4
Account type (IMAP, POP3, WebDAV/Exchange): POP3

We'll get rid of the actions at the bottom of the screen in the redesign. But we certainly won't add an option just to add more space in certain areas.


DNS Forwarding

<quote>For deployment, DNS servers that Azure Stack forwards requests to are required in the Deployment Worksheet (in the DNS Forwarder field). Provide at least two servers in this field for fault tolerance. Without these values, Azure Stack deployment fails.</quote>
Does this mean that forwarding / recursion is no longer needed AFTER deployment? If it's still needed I have used some powershell cmds to configure/harden your external DNS servers. I could mail you the commands and check if these are sufficient?
Would be nice to see the best practices for those external DNS servers aswell using the Ip ranges from the Deployment Worksheet. (Which Azure Stack servers / subnets need to recurse)

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

ID: 4cf7c779-041d-a232-b441-b769be1aaa67
Version Independent ID: 620aa3f3-4351-5ad3-996e-38140d50f108
Content: Azure Stack datacenter integration - DNS
Content Source: articles/azure-stack/azure-stack-integrate-dns.md
Service: azure-stack
GitHub Login: @jeffgilb
Microsoft Alias: jeffgilb

error in my sentence: "....powershell cmds to configure/harden your external DNS servers...." -->  Your = our

@AzureStackNerd Thanks for the feedback. We are actively investigating and will get back to you soon.

@AzureStackNerd If you are using ADFS to deploy stack, you might not need any forwarding / recursion, but in most cases it will be necessary.
Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

#please-close


Recommendation for writing tests for ModelParallel distribution

A customer mentioned that the ModelPrallel API in Keras is prone to breakage when multiple team members work on the same model. It is easy to make a model or layer modification that impacts the way the LayoutMap regexes match layers and break the ModelParallel Layout map.
We experienced such a breakage ourselves: https://github.com/keras-team/keras/issues/19496
The solution is to write tests for ModelParallel LayoutMaps. Listing layers and their LayoutMaps is not an issue. We document it in the Gemma distributed training docs for example. However, it is not clear to me how to turn this into a unit test.
In the Gemma example, scaling layers are not explicitly partitioned by the user, yet, they display the layout PartitionSpec(None,). How should users test that layers that have not been assigned any partition spec explicitly, do not unexpectedly receive one (like happened to us in issue 19496 when LoRA layers unexpectedly received a partition spec).
Also, the error message on a mismatched partition spec was not very helpful.

Would you mind suggesting something here @qlzh727? Thank you!

You can follow https://github.com/keras-team/keras/blob/6ae7898e4bd464c407de035ed8dc7632eec7d7ee/keras/src/backend/jax/distribution_lib_test.py#L231 as and e2e test example if user would like to verify the weights layout explicitly. If the model is quite large, this will require user to trim down the model size to fit for the hardware limitation.
For layers that receive an layout unexpectly, I think user can catch this via unit test (eg by verify the lora weights is not partitioned.)

assuming that the correct way to "verify the weights are not partitioned" is to compare their weight._value.sharding.spec to (None, )