ScrollTop allways 0

I have this modal where Simple bar is initiated and a form is  displayed.
el = new SimpleBar($('.fullModal .modal-body')[0]);
When the modal is closed and opened again, the scroll bar remains where it was last placed.
 console.log(el.getScrollElement().scrollTop);
Reveals that no matter where the scroll bar is placed it is set to 0, and when I try to set it equal to some value, it ignores it completely.
I need to be able to set scrollTop = 0 and have it actually got to the top.
Thank you for your work.
Santiago.

The way you're trying to do seems correct.
There might be an issue somewhere in your code that makes it not working.
I can't really help more than that without seeing the code, sorry!

Same problem here:
https://codesandbox.io/s/tender-boyd-xcmdq

@Grsmto @Cyrus-d thank you for your answers.
I've been trying but haven't found a fix yet.  I've annexed some of my code, in the hope you might help me.
I have a bootstrap 4 modal

I dynamically add a form throught ajax as
 $('#fsModal > .modal-dialog').html( form );

The form has a div that where I instantiate the simple bar from a script that came in the same ajax call
 var el = new SimpleBar($('.fullModal .modal-body')[0])

When the modal is closed I empty the .modal-dialog vid
 $('#fsModal').on('hidden.bs.modal', function () {
     $('#fsModal > .modal-dialog').empty();
 })

The scroll works, but when I re open a modal, it "remembers" where it was set.

Thanks!

@Cyrus-d you are doing getContentElement instead of getScrollElement.

@Grsmto correct, works fine with getScrollElement, thank you.

@scammi maybe using simpleBar.recalculate(); when emptying the modal solve your problem!

Thank you, but it seems the problem does not relay relies on simple bar, since I removed it and the issue persists with the browser scroll

@Grsmto getScrollElement is returning undefined in simplebar 4.1

Now just tested with SimpleBar 5.1.0 I get the same: el.getScrollElement() is undefined,
"el" is:
{
  "el": {},
  "minScrollbarWidth": 20,
  "options": {
    "autoHide": true,
    "forceVisible": false,
    "clickOnTrack": true,
    "classNames": {
      "contentEl": "simplebar-content",
      "contentWrapper": "simplebar-content-wrapper",
      "offset": "simplebar-offset",
      "mask": "simplebar-mask",
      "wrapper": "simplebar-wrapper",
      "placeholder": "simplebar-placeholder",
      "scrollbar": "simplebar-scrollbar",
      "track": "simplebar-track",
      "heightAutoObserverWrapperEl": "simplebar-height-auto-observer-wrapper",
      "heightAutoObserverEl": "simplebar-height-auto-observer",
      "visible": "simplebar-visible",
      "horizontal": "simplebar-horizontal",
      "vertical": "simplebar-vertical",
      "hover": "simplebar-hover",
      "dragging": "simplebar-dragging"
    },
    "scrollbarMinSize": 25,
    "scrollbarMaxSize": 0,
    "timeout": 1000
  },
  "classNames": {
    "contentEl": "simplebar-content",
    "contentWrapper": "simplebar-content-wrapper",
    "offset": "simplebar-offset",
    "mask": "simplebar-mask",
    "wrapper": "simplebar-wrapper",
    "placeholder": "simplebar-placeholder",
    "scrollbar": "simplebar-scrollbar",
    "track": "simplebar-track",
    "heightAutoObserverWrapperEl": "simplebar-height-auto-observer-wrapper",
    "heightAutoObserverEl": "simplebar-height-auto-observer",
    "visible": "simplebar-visible",
    "horizontal": "simplebar-horizontal",
    "vertical": "simplebar-vertical",
    "hover": "simplebar-hover",
    "dragging": "simplebar-dragging"
  },
  "axis": {
    "x": {
      "scrollOffsetAttr": "scrollLeft",
      "sizeAttr": "width",
      "scrollSizeAttr": "scrollWidth",
      "offsetSizeAttr": "offsetWidth",
      "offsetAttr": "left",
      "overflowAttr": "overflowX",
      "dragOffset": 0,
      "isOverflowing": true,
      "isVisible": false,
      "forceVisible": false,
      "track": {},
      "scrollbar": {}
    },
    "y": {
      "scrollOffsetAttr": "scrollTop",
      "sizeAttr": "height",
      "scrollSizeAttr": "scrollHeight",
      "offsetSizeAttr": "offsetHeight",
      "offsetAttr": "top",
      "overflowAttr": "overflowY",
      "dragOffset": 0,
      "isOverflowing": true,
      "isVisible": false,
      "forceVisible": false,
      "track": {},
      "scrollbar": {}
    }
  },
  "removePreventClickId": null
}

found the issue:

when the scrollbar is created, it returns the right object with the getScrollElement() defined
the issue is when I need to scroll up, and try to get the SimpleBar on the element that already has the SimpleBar applied, I think the lib tries to apply the plugin again and returns a different object, with getScrollElement() undefined

The only solution I found is to create a global variable, which I hate, and store the SimpleBar object returned when first applied the plugin, then when I need to scroll up, I access that global bar.
Would be nice if the plugin detects that it is already applied and returns the same object instead of a different inconsistent one.

@ppazos, I have the same issue and I cannot use the getScrollElement for the same reason. @Grsmto, can you please look into this and solve this issue?


[4.2] Routing broken when streaming to iOS10

Laravel Version: 4.2.0
PHP Version:5.6

Description:
I have a route that responds to a video request from a video tag in a web page, this works fine in iOS9, on the desktop in all browsers, no problem at all - based on http://codesamplez.com/programming/php-html5-video-streaming-tutorial
Steps To Reproduce:
Just trying to view the video in the page - it fails to play when its routed via laravel. Direct linking to a PHP script does work, however only when laravel isn't handling the route.
What I've discovered is that the route is just not being fired when the request is made, I've tried changing this to Route::any but it makes no difference.
I suspect that iOS 10 has sent the request in an odd way but I've yet to work out whats going on.
For example -
Address  http://DOMAIN/media/play/b32b26c6a839a5033a59b03c0c0d3495ecaccd2a/1465917545
Route::any('media/play/{checksum}/{modified}', array('uses' => 'MediaController@mp4'));
The above route doesn't get fired when I view from iOS10 - the address is as per in the page, I've got logging in the method and it's simply not fired.
Any pointers greatly appreciated!

OK - further info... If I do a check in the routes file for the exact URL and put the videostream class inside the routes file and trigger the stream it works in iOS10. This proves the only issue here is why the route is being ignored otherwise - to be clear this works on all other devices/browsers we've tested...

Sorry, only 5.1 and 5.3 are supported.

Will try and reproduce in 5, unfortunately this project is in 4 but we have another on 5 to check.

I'm now certain this problem is due to the fact that the request has some seek information being sent in the headers by the browser and this is not understood by the 4.2 laravel routing classes. We've had to use a work around for now but its not great - we will test in 5 soon to see if this is a problem in the current release too.


dominoes: consider asking for chain rather than canChain

There are two possible ways to interpret the dominoes problem, as the canonical data tells us.

Only ask for canChain, a boolean telling us whether the given dominoes can be chained. The tests only need to check whether the boolean matches the expectation.
Ask for chain, which will be (I assume for F#) Some of a valid chain if one exists, or None if one does not. The tests would need to check the various properties noted in the canonical data

This track asks for canChain only. I assumed this was an intentional decision, so I did not question it. But Erik asked me to file an issue. So y'all can reopen the issue in case y'all want to ask for chain.

@robkeim How do you feel about this?

Oh, for the record, I find it highly unlikely that a student implementation will falsely pass the tests even if the tests only look for true/false, so I don't think this is very urgent. I predict that students will still actually attempt to find a chain (and if they don't, they're the ones missing out!).
If my prediction is correct, then I think the main advantage of implementing chain is simply a little bit of student peace-of-mind that the chain found by the code is correct. But most of that peace-of-mind is probably already had by canChain?
And if chain gets implemented, the disadvantage tests will get more complex, so y'all have to be prepared for the maintainership of that extra test code.
Current implementors that use boolean only:

C#
F#
Swift

Current implementors that use domino list option (or similar)

Haskell
OCaml
Ruby
Swift
Scala

disclaimer: I haven't implemented this exercise myself yet

If my prediction is correct, then I think the main advantage of implementing chain is simply a little bit of student peace-of-mind that the chain found by the code is correct. But most of that peace-of-mind is probably already had by canChain?

I would definitely feel more confident my solution worked correctly if chain were validated as opposed to canChain.

And if chain gets implemented, the disadvantage tests will get more complex, so y'all have to be prepared for the maintainership of that extra test code.

I had a look at the other tracks that implemented chain (I updated @petertseng's post above to include the links) and the complexity didn't seem too bad in terms of implementation, but you just have to ensure you check for the other permutations. There may be some cases although where the number of potential chains that you can make is infinite due to the fact that you can re-use dominos. I think in that cases it's valid to consider larger chains "not correct".
@ErikSchierboom you were the one that implemented the exercise, what was your thought process in choosing chain vs canChain?

@robkeim The canChain approach was slightly easier to implement, which reduced the difficulty a bit. But now that I see all arguments, I think it would make more sense to convert it to chain. The extra effort I think will not be that bad.

Ok sounds good!

I'm going ahead and closing this for the same reason outlined in https://github.com/exercism/csharp/issues/190

It looks like this track will need to change its README.
The https://github.com/exercism/fsharp/blob/master/exercises/dominoes/README.md says such things like:

Compute a way to order a given set of dominoes

Since this track asks for canChain, this should probably read "Compute whether there exists a way to order a given set of dominoes"

For example given the stones 21, 23 and 13 you should compute something like 12 23 31 or 32 21 13 or 13 32 21

Since this track asks for canChain, this should probably read "For example given the stones 21, 23 and 13 you should declare that there exists a possible chain (for example, 12 23 31 is a possible chain)"
Note upcoming changes to domino text representation in https://github.com/exercism/problem-specifications/pull/972

@petertseng At one point there was mention of some tooling to easily synchronize the test descriptions. Do you know if that tooling is available anywhere?

some tooling to easily synchronize the test descriptions.

I do not know anything about it

For description.md -> README.md changes, I hvae been using git cal --date="$(git --git-dir=../problem-specifications/.git show --format=%ai -s HEAD)" --author="$(git --git-dir=../problem-specifications/.git show --format='%an <%ae>' -s HEAD)" -m "$(git --git-dir=../problem-specifications/.git log --format=%B -n1 HEAD)" but my workflow is not fully set in stone yet.

Re-opening this to track the out-of-date documentation.

I'm working on this


Request: make full filename available as an attribute/property, when clicking on a picture/video

Hello,
I love this beautiful frontend integration, however I’m missing one feature :-)
Can you please make the last selected video/picture available as an attribute, so I can create my own automation for
the selected file ?
I use this component to show a list of my own recordings of my ip cameras.
I need to go into the “media”, to select and delete files.
It would ne nice if the filename of the last clicked image/video is available in an attribute, so I can add a button in the dashboard,
And make my own automation to do things with the file (like deleting it for example)
thanks in advance,
Greetings from Belgium,
Kris
-=[https://www.digitalplayground.be]=-
Where fun meets technology …

Mmm I'm not sure what you are asking for. This component doesn't expose attributes, it only works with sensors and folders existing in your system. As a frontend component it can't generate any entities which you can use to play with on automations


cannot open on OSX running El Capitan

Looks like it could be related to this electrum issue: https://github.com/spesmilo/electrum/issues/2726
When opening the app, it unexpectedly quits, and then I click "report" to get the error message. I've left the error messages for both regular and tor app for OSX below (looks to match the issue from electrum)
Dyld Error Message:
  Symbol not found: _getentropy
  Referenced from: /Volumes/VOLUME/Electrum-XVG.app/Contents/Frameworks/Python.framework/Versions/2.7/Python (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

Dyld Error Message:
  Symbol not found: _getentropy
  Referenced from: /Volumes/*/Electrum-XVG-TOR.app/Contents/Frameworks/Python.framework/Versions/2.7/Python (which was built for Mac OS X 10.12)
  Expected in: /usr/lib/libSystem.B.dylib

This open ticket from another project has more information about the underlying problem caused by Apple and libraries in XCode

you dragged it into applications to open it, or just double clicked the file after downloading?

After separate downloads I dragged to Apps and clicked the file to open. Electrum still returns the same error for me as well.

I have had the same issue. I have Electrum installed on my machine for BTC. Do you have it installed too?

@justinvforvendetta even if I drag it into the applications folder.
I'm running El Capitan 10.11.6
@ryan-blake and @bars1986 what version OSX are you guys running? Let's try and see if it's an El Capitan issue, so at least there could be a small compatibility disclaimer until the issue is fixed.

@pyramation same issue with 10.11.6

same issue with 10.11.6

@pyramation OS X El Capitan 10.11.6
As i mentioned I do have another Electrum wallet installed that holds my mBTC.
Thanks for your help.

@bars1986 @touedraogo you dragged the app into applications?

yes I dragged it into the Applications folder and I have also tried just double-clicking to open.

double clicking shouldnt work, but dragging into applications should. do you have admin rights on that computer?

Yessir. :)

this is what i have done:

Admin rights
Dragged to into application folder
Go to Finder / Application and not from Lanchpad to avoid message saying that that App is not Official+Apple+Blah
then right click + open

Even tried from Terminal console
[admin@DarkMac:/Applications/Electrum-XVG.app/Contents/MacOS]$ ./Electrum-XVG
dyld: lazy symbol binding failed: Symbol not found: _getentropy
Referenced from: /Applications/Electrum-XVG.app/Contents/Frameworks/Python.framework/Versions/2.7/Python (which was built for Mac OS X 10.12)
Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: _getentropy
Referenced from: /Applications/Electrum-XVG.app/Contents/Frameworks/Python.framework/Versions/2.7/Python (which was built for Mac OS X 10.12)
Expected in: /usr/lib/libSystem.B.dylib

My electrum wallet also crashed on macOS high sierra 10.13.2. It just showed an empty error box. I cloud fix it by just renaming the application (in the applications folder) from "Electrum-XVG.app" to "Electrum.app". Everything's working fine now!

This wallet doesn't open at all for me on El Cap 10.11.6. All the usual stuff mentioned above is ok (admin rights, dragged it to App folder, etc.). When doubleclicking to open, the icon does its little expansion animation, and then nothing whatsoever. It won't launch.

I can confirm both @Hubsi3 and @SomePoorSlob's comments. Same deal here. Super weird. Must be a bad reference somewhere???

same issue with 10.11.6

can confirm download and upon opening the Verge OSX Electrum Wallet using Mac OS brings an error...using Mac OS High Sierra Version 10.13.2

The new Wraith build doesn't have this issue so once that launches @justinvforvendetta you can probably close this out.

same error here.


wandb:do not have permission to access the requested resource

Hi . I met a new issue.  Do i need you pemission for wandb or i miss something >.<
Thank you!
wandb: Currently logged in as: zxcvzxcv980234. Use wandb login --relogin to force relogin
wandb: ERROR Error while calling W&B API: entity your_entity not found during upsertBucket (<Response [404]>)
Problem at: /cis/net/io93c/data/shuan124/functional-diffusion-processes/src/functional_diffusion_processes/trainers/trainer.py 93 initialize_wandb
wandb: ERROR It appears that you do not have permission to access the requested resource. Please reach out to the project owner to grant you access. If you have the correct permissions, verify that there are no issues with your networking setup.(Error 404: Not Found)
Error executing job with overrides: ['+experiments_maml=exp_mnist']

Hey there!
I wanted to start by mentioning that in our config file, we've left a placeholder for the wandb entity because we don't know your actual entity name.
The error you're encountering is because this placeholder needs to be updated with your specific wandb username or organization name.
Here's how you can sort it out:

First off, you'll need to update you_entity with your actual wandb entity name when running your script. Your command should look something like this:

PYTHONPATH=. python3 src/functional_diffusion_processes/run.py --multirun +experiments_maml=exp_mnist \
trainers.trainer_logging.wandb_init.project="fdp_mnist" \
trainers.trainer_logging.wandb_init.entity="<your_wandb_entity_name>"

Just swap <your_wandb_entity_name> with your actual entity name.
OR

If you prefer using a config file, just update the entity and project fields in conf/trainers/trainer_maml.yaml with your details. Then run the script as is.

OR

If you don't want to log with wandb: you can skip it entirely by setting use_wandb=False in your command:

PYTHONPATH=. python3 src/functional_diffusion_processes/run.py --multirun +experiments_maml=exp_mnist \
trainers.trainer_logging.use_wandb=False

Hope it helps!

i run it successfully !! thank you so much !!


Add support for go-redis

Change
Added

Added support for go-redis v9.

Note

[ ] document is updated if necessary.
[ ] New features are tested.

The test is also expected. Pleaser read the doc.

You should be able to run this test and make sure it passed, rather than relying on the limited upstream resource to keep rerunning.

You should be able to run this test and make sure it passed locally, rather than relying on the limited upstream resource to keep rerunning.

Just figure out how to run it locally.
The network inside GFW is poor. When I run the integration test, some packages are not able to be downloaded, which needs a lot of change in the .tpl file to use a proxy.
// so those are generated according to the .tpl. System proxy does not work inside the docker container
// so I have to try it step by step.....

This is always better to run on a cloud ubuntu to make all easier. Let me know if you need any help or have passed locally.

Thank you sir. The test workflow is fine on my local PC now. There are some issues to be fixed tho.
BTW I would like to say the documentation is very clean, thanks to @mrproliu . I'd like to write a new blog post about how to extend new plugin to skywalking-go with some detail example. Actually translating those doc into Chinese is already good enough, but I would like to have a step by step demonstration to help more developers who's new to SkyWalking :)

You are welcome to add this to our website, CN blog channel. And we could forward this to juejin as well.

Thanks.
The compilation is failing with error as below. I think most of my codes are following the development guide. Spent an hours to figure it out but still cannot locate the root cause.
/usr/local/go/bin/go build -toolexec /home/jiekun/repo/github.com/skywalking-go/test/plugins/dist/skywalking-go-agent -debug /home/jiekun/repo/github.com/skywalking-go -a -o /home/jiekun/.cache/JetBrains/GoLand2023.1/tmp/GoLand/___10go_build_main_go -gcflags all=-N -l /home/jiekun/repo/github.com/skywalking-go/test/plugins/scenarios/go-redisv9/main.go #gosetup
# github.com/redis/go-redis/v9
/home/jiekun/repo/github.com/skywalking-go/plugins/go-redisv9/hook.go:157: undefined: redis
/home/jiekun/repo/github.com/skywalking-go/plugins/go-redisv9/intercepter.go:44: undefined: redis
/home/jiekun/repo/github.com/skywalking-go/plugins/go-redisv9/intercepter.go:46: undefined: redis
/home/jiekun/repo/github.com/skywalking-go/plugins/go-redisv9/intercepter.go:52: undefined: redis
2023/06/06 22:00:59 exit status 2

I would like to have a few hints from maintainers / reviewers if possible (orz), and continue on this enhencement tomorrow.

@mrproliu When you have time.

@jiekun You need to add the -work parameter and remove the -debug parameter temporarily in the build command, then you can get the real generate files in the console. Please deep into the file you are compiling error, and see what's happening in there.

You need to add the -work parameter and see what's happening in there.

Thanks. I did it yesterday and I am going to post the source file and generated file here as below:
        // source

	switch c := rdb.(type) {
	case *redis.Client:
		c.AddHook(newRedisHook(c.Options().Addr))
	case *redis.ClusterClient:
		c.AddHook(newRedisHook(""))

		c.OnNewNode(func(rdb *redis.Client) {
			rdb.AddHook(newRedisHook(rdb.Options().Addr))
		})
	case *redis.Ring:
		c.AddHook(newRedisHook(""))

		c.OnNewNode(func(rdb *redis.Client) {
			rdb.AddHook(newRedisHook(rdb.Options().Addr))
		})

        // generated

	switch c := rdb.(type) {
	case *redis.Client:
		c.AddHook(skywalking_operatorStaticMethodRedisnewRedisHook(c.Options().Addr))
	case *redis.ClusterClient:
		c.AddHook(skywalking_operatorStaticMethodRedisnewRedisHook(""))

		c.OnNewNode(func(rdb *Client) {
			rdb.AddHook(skywalking_operatorStaticMethodRedisnewRedisHook(rdb.Options().Addr))
		})
	case *redis.Ring:
		c.AddHook(skywalking_operatorStaticMethodRedisnewRedisHook(""))

		c.OnNewNode(func(rdb *Client) {
			rdb.AddHook(skywalking_operatorStaticMethodRedisnewRedisHook(rdb.Options().Addr))
		})

The *redis in switch-case line is not replaced. Initially I thought it's because those structure are not instrumented. However same struct in function call is replaced (e.g. c.OnNewNode(func(rdb *redis.Client) { is replaced to c.OnNewNode(func(rdb *Client) {). Any clue @mrproliu ?

Ok, that's related to the rewrite processing. At present, it may not cover all the scenarios that need to be rewritten. As the version iterations, the function will become more and more perfect. You can have a debug with the following steps:

Find the arguments of compile: The instrument.log file can be found in the compiled temporary directory, where you can find the parameter information of your current compiled package.
Debug the agent tools: Debug Agent Tool with the arguments.

If it's not easy for you, I can give you some help.

Well I have little experience with code generation and ast parsing. I think I would prefer some help here (orz). Not sure how it could perform tho, like rebasing a new branch with the rewritten support for switch-case?
I would like to provide my guess of the missing supports:

switch-case as addressed above: https://github.com/apache/skywalking-go/pull/55/files#diff-67660820b0f7f0cf5ec1b1c22b073b5005a83ac5112535be7b54863f2f4d332dR43
It looks like const (redis.Nil) is not rewritten as well: https://github.com/apache/skywalking-go/pull/55/files#diff-9bfc186e1c784e2abf6fe20c851745fcc16d1f4719051e1ff95e077047245445R163

@jiekun The rewrite-related problem has been fixed, please re-check locally.

@mrproliu Thank you for giving me a hand with the rewrite function.
@wu-sheng I'm removing the draft status. Please review it when you have time. Thank you all.

Docs should be updated accordingly, https://github.com/apache/skywalking-go/blob/main/docs/en/agent/support-plugins.md


feature: add client_auth_method=none into tokens for clients with empty secret

Internally use empty, but write none into tokens. Externally use always none, but internally empty to distinguish in the flow.
The refresh flow with an empty secret is something we allow for now.
So a combination from https://github.com/cloudfoundry/uaa/pull/2435 (external view) and
https://github.com/cloudfoundry/uaa/pull/2447 (internal view)

Based on the title & description of this PR, it seems that this PR's sole purpose is to inject an extra claim client_auth_method=none to the token if the client that originally requested this token is a public client (either no secret or empty string secret).
But when I look at all the tests added, it looks like the PR does more than that (for example, a test is added to forbid refresh request under some conditions)? Is that true? Or are these test "backfilled tests" testing existing logics of develop branch?
To help me understand this PR better, could you summarize, point by point, all the changes included in this PR. This will help me validate my understandings &  help us know what doc edits are required.

@strehle Based on the title & description of this PR, it seems that this PR's sole purpose is to inject an extra claim client_auth_method=none into the token if the client that originally requested this token is a public client (either no secret or empty string secret).
But when I look at all the tests added (I use the test changes to understand the exact implications of the code changes), it looks like the PR does more than that (for example, a test is added to forbid refresh request under some conditions)? Is that true? Or are these test "backfilled tests" testing existing logics of develop branch?
To help me understand this PR better, could you summarize, point by point, all the changes included in this PR. This will help me validate my understandings & help us find out what doc edits are required.

The inject of  client_auth_method=none into the token was introduced with https://github.com/cloudfoundry/uaa/issues/2138 . The feature of allowing public scenarios like authorization code flow and refresh flow without any secret was added as new feature into UAA but with constraint of doing this only if we have a rotation of the refresh token. The rotation of the refresh token is a very important feature because it limits the risk of a stolen refresh token. This feature was done because of https://github.com/cloudfoundry/uaa/issues/1448 . The origin of it is https://oauth.net/2.1/ where public usages are explicitly mentioned.
And this blocks it right now, means the mix of the public refresh exchange with this approach to limit the empty secret. The empty secret and its refresh is an existing scenario which we cannot break.
For new features we can have limitations, like you get the public refresh only with a refresh rotation....

@peterhaochen47 please see this PR as replacement for https://github.com/cloudfoundry/uaa/pull/2435

I'm trying to understand the original problem (that this PR is intended to help address) better: https://github.com/cloudfoundry/uaa/pull/2193#issuecomment-1741594174

I'm trying to understand the original problem (that this PR is intended to help address) better: #2193 (comment)

This PR is needed to solve failing test b) , see https://github.com/cloudfoundry/uaa/pull/2193#issuecomment-1745437039
because this change add client_auth_method=none to cf client autentication and then later we can use none to identiy that it was public and public-2-public should be ok

Based on your comment, this PR is mainly for resolving the failures in #2193 which I have requested to be closed. Do you now suggest that this PR be reviewed independently without considering #2193?

Do you now suggest that this PR be reviewed independently without considering #2193?

Yes please do so. I had the plan to re-use this, but we may wont fix user token.
However this PR is simply about that none should appear in access_token for a not existing secret and for an empty one, so that we can treat in future both as public usage.

FYI: this change is not related to https://github.com/cloudfoundry/uaa/pull/2571 even if topic is empty secret.


What is the behavior in non UWP apps?

This says that Package.Current isn't supported in UWP apps. Does that mean that it throws an exception for a desktop app, or that it returns null?

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

ID: d3099bc3-1eb7-77f0-29ea-d1ce01f4dfa7
Version Independent ID: f25364e8-33ca-d30a-f718-f14636d615f4
Content: Package.Current Property (Windows.ApplicationModel) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.applicationmodel.package.yml&version=GBlive&_a=contents
Product: uwp
Technology: winrt-reference
Git Login: knicholasa
Microsoft Alias: nichola

Thanks for reaching out with your feedback. You'll find quicker support by consulting our developer support resources. For community assistance with development questions I recommend that you ask on our forums or StackOverflow. Otherwise, please see the developer support page for your support options. If you get assistance through these other resources and believe that information would help us improve the docs, please come back and let us know.

This strikes me as a reasonable enhancement request.  Committing to a InvalidOperationException or NotImplementedException or whatever the matches the current observable behavior would be a real improvement for us API consumers.


Encounters with data absent reasons failing validation

After updating to the latest releases I have found that our Encounter resources are now failing test 4.27.03 "All must support elements are provided in the Encounter resources returned". I think this bug was introduced in this change in the us-core-test-kit
https://github.com/inferno-framework/us-core-test-kit/commit/54133f0148782bb5a9b46ba2ef011a587c5558f6
I'm not confident that is the root cause, but this is the only change after us-core-test-kit version 0.2.2 that appears to be relevant to me. Our server passes all tests on version 2.2.1 of the onc-certification-g10-test-kit. The version we failed with is at the latest version of the main branch in the g10-kit, as I wanted to pick up the feature I added here:
https://github.com/onc-healthit/onc-certification-g10-test-kit/commit/31cd34274da67ce48cc9f31f85268a571b39ec62

What error messages did you see?

Could not find hospitalization.dischargeDisposition in the 48 provided Encounter resource(s)

I'm trying out the attached fix to see if that resolves it. Not sure if this is the right solution or not, just wanted to share that I was trying to resolve this on my own already.

Sorry should have added this earlier, all of our resources being returned have the following fields set on the objects
  "hospitalization": {
    "dischargeDisposition": {
      "extension": [
        {
          "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
          "valueCode": "not-applicable"
        }
      ],
      "text": "Not Applicable"
    }
  },

the linked changes do resolve this issue for us

Yes. Inferno may have a different issue here. Could you post the whole Encounter resource? The code segment you post does not look correct. hospitalization. dischargeDisposition is a CodeableConcept. so that should be
  "hospitalization": {
    "dischargeDisposition": {
      "coding": [
        {
          "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
          "valueCode": "not-applicable"
        }
      ],
      "text": "Not Applicable"
    }
  },

@Jammjammjamm
I'll follow up with our team that knows this data better to discuss in more detail why none of these resources have that field populated. We have two different types of practices in our product, hospital practices and ambulatory practices. The one that is failing is ambulatory, and this passes for the hospital practice that we test with. Just looking at the documentation in the spec I'm guessing we don't have this for ambulatory because the patient is never hospitalized with them, so they're never discharged. Doesn't seem like the data element would ever apply.
@yunwwang
I redacted a few things, but this is pretty much what it looked like. The structure is fhir compliant though, a CodeableConcept is derived from Element, so we can have an extension field on it if we want to, and coding is 0..* so we don't have to include it. Encounter.hospitalization.dischargeDisposition is must-support and we supply a CodeableConcept object for it, but we have no relevant data for it in these cases so we attached a DAR.
{
  "location": [
    {
      "location": {
        "reference": "Location/1234"
      }
    }
  ],
  "period": {
    "start": "2000-01-01T00:00:00Z"
  },
  "resourceType": "Encounter",
  "hospitalization": {
    "dischargeDisposition": {
      "extension": [
        {
          "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
          "valueCode": "not-applicable"
        }
      ],
      "text": "Not Applicable"
    }
  },
  "status": "entered-in-error",
  "subject": {
    "reference": "Patient/5"
  },
  "identifier": [
    {
      "system": "https://fhir.athena.io/sid/ah-encounter",
      "value": "3"
    }
  ],
  "participant": [
    {
      "type": [
        {
          "text": "The practitioner that has responsibility for overseeing a patient's care during a patient encounter.",
          "coding": [
            {
              "system": "http://terminology.hl7.org/CodeSystem/v3-ParticipationType",
              "code": "ATND",
              "display": "attender"
            }
          ]
        },
        {
          "text": "The principal or primary performer of the act.",
          "coding": [
            {
              "system": "http://terminology.hl7.org/CodeSystem/v3-ParticipationType",
              "code": "PPRF",
              "display": "primary performer"
            }
          ]
        }
      ],
      "individual": {
        "reference": "Practitioner/8"
      }
    }
  ],
  "id": "9809",
  "class": {
    "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
    "code": "VR",
    "display": "virtual"
  },
  "type": [
    {
      "text": "Indirect encounter",
      "coding": [
        {
          "system": "http://snomed.info/sct",
          "code": "185316007",
          "display": "Indirect encounter"
        }
      ]
    }
  ]
}

Here's another that failed that isn't entered-in-error.
{
  "location": [
    {
      "location": {
        "reference": "Location/8913"
      }
    }
  ],
  "period": {
    "end": "2000-01-01T12:00:00Z",
    "start": "2000-01-01T14:00:00Z"
  },
  "resourceType": "Encounter",
  "hospitalization": {
    "dischargeDisposition": {
      "extension": [
        {
          "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
          "valueCode": "not-applicable"
        }
      ],
      "text": "Not Applicable"
    }
  },
  "status": "finished",
  "subject": {
    "reference": "Patient/7364"
  },
  "identifier": [
    {
      "system": "https://fhir.athena.io/sid/ah-encounter",
      "value": "8544"
    }
  ],
  "participant": [
    {
      "period": {
        "start": "2000-01-01T13:00:00Z",
        "end": "2000-01-01T14:00:00Z"
      },
      "type": [
        {
          "text": "The practitioner that has responsibility for overseeing a patient's care during a patient encounter.",
          "coding": [
            {
              "system": "http://terminology.hl7.org/CodeSystem/v3-ParticipationType",
              "code": "ATND",
              "display": "attender"
            }
          ]
        },
        {
          "text": "The principal or primary performer of the act.",
          "coding": [
            {
              "system": "http://terminology.hl7.org/CodeSystem/v3-ParticipationType",
              "code": "PPRF",
              "display": "primary performer"
            }
          ]
        }
      ],
      "individual": {
        "reference": "Practitioner/13456"
      }
    }
  ],
  "id": "875",
  "class": {
    "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
    "code": "AMB",
    "display": "ambulatory"
  },
  "type": [
    {
      "text": "BRIEF EMOTIONAL/BEHAV ASSMT",
      "coding": [
        {
          "system": "http://www.ama-assn.org/go/cpt",
          "code": "96127",
          "display": "BRIEF EMOTIONAL/BEHAV ASSMT"
        }
      ]
    },
    {
      "text": "OFFICE/ OUTPATIENT E&M ESTABLISHED PATIENT",
      "coding": [
        {
          "system": "http://www.ama-assn.org/go/cpt",
          "code": "99213",
          "display": "OFFICE/ OUTPATIENT E&M ESTABLISHED PATIENT"
        }
      ]
    },
    {
      "text": "BRIEF EMOTIONAL/BEHAV ASSMT",
      "coding": [
        {
          "system": "http://www.ama-assn.org/go/cpt",
          "code": "96127",
          "display": "BRIEF EMOTIONAL/BEHAV ASSMT"
        }
      ]
    },
    {
      "text": "NO CHAD OR CHAD SCR 0 OR 1",
      "coding": [
        {
          "system": "urn:oid:2.16.840.1.113883.6.285",
          "code": "G9931",
          "display": "NO CHAD OR CHAD SCR 0 OR 1"
        }
      ]
    },
    {
      "text": "OFFICE/ OUTPATIENT E&M ESTABLISHED PATIENT",
      "coding": [
        {
          "system": "http://www.ama-assn.org/go/cpt",
          "code": "99213",
          "display": "OFFICE/ OUTPATIENT E&M ESTABLISHED PATIENT"
        }
      ]
    }
  ]
}

@nathanloyer I see the confusion here. You actually find a loophole in our logic.
In this code segment:
  "hospitalization": {
    "dischargeDisposition": {
      "extension": [
        {
          "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
          "valueCode": "not-applicable"
        }
      ],
      "text": "Not Applicable"
    }
  },

The meaning of this code segment is that the server could not populate dischargeDisposition with a reasonable value. When all the dischargeDisposition have the same segment, the server in practical fails the MustSupport requirement. In another way, the server does not demonstrate that it SUPPORT this element.
But structure wise, the server populates the dischargeDisposition.text element. In that sense, the server does provide something other than DAR extension.
One logic is that "IF there is DAR extension, ignores the element". The other is "IF there is anything other than DAR extension, takes the element"
For all the previous resources we have tests, these two logics yields the same result because all tests have either DAR or subelements.
This is the first time that we have seen that DAR extension and a subelement present at the same time.
In @nathanloyer example, the DAR extension and subelement convey the same meaning. But what if they don't. For example, I could have a Patient like
  "name": [
    {
         "extension": [
        {
          "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
          "valueCode": "unknown"
        },
       "family": "Dole"
       "given": [ "John" ]
    }
  ]

Structure wise, this is valid. But what is the meaning of this element?
@nathanloyer Though you can attach DAR extension to any element. US Core has a guidance that your code segment fails to follow:

first, you have a text segment which should be enough to pass the MustSupport test.
second, if you do want to more specific, you should "if the value set does not have the appropriate “unknown” concept code, use unknown from the DataAbsentReason Code System"

first, you have a text, you should use text element without that extension. This should be enough to pass the MustSupport test.

Well that text is just a human friendly representation of the DAR code, so probably don't need it there.

second, if you do want to more specific, you should follow this: "if the value set does not have the appropriate “unknown” concept code, use unknown from the DataAbsentReason Code System". That would be same as the example I posted above. That should also pass the MustSupport test.

So it sounds like your recommendation is to change it to this:
  "hospitalization": {
    "dischargeDisposition": {
      "coding": [
        {
          "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
          "valueCode": "unknown"
        }
      ],
      "text": "Not Applicable"
    }
  },

Or that, but with text removed?
I think we wanted to be more specific here, as for our system, labelling this as "Not Applicable" is more accurate than "Unknown". In this case, we know that we wont have data for that element because patients are never admitted/hospitalized at these practices.
If we just remove text do you think that would satisfy the ruling? i.e.
```json
  "hospitalization": {
    "dischargeDisposition": {
      "extension": [
        {
          "url": "http://hl7.org/fhir/StructureDefinition/data-absent-reason",
          "valueCode": "not-applicable"
        }
      ],
    }
  },

I think we wanted to be more specific here, as for our system, labelling this as "Not Applicable" is more accurate than "Unknown". In this case, we know that we wont have data for that element because patients are never admitted/hospitalized at these practices.

You CAN use "not-applicable" here. The binding strength is "example" which gives you freedom to use any code you prefer.
And I think the intention for the author here "if the value set does not have the appropriate “unknown” concept code, use unknown from the DataAbsentReason Code System" is "use an appropriate unknown code from the DataAbsentReason Code System"
I will ask US Core author to clarify

Thanks for the help @yunwwang. After reviewing with some colleagues we've come to agree with your recommendation and will patch a fix in our code and reject this issue and my PR.
I will say that the spec for this in the US Core IG could be updated to be more clear. I feel like it takes too long to re-review the spec to understand the intention every time I come across a situation where we find we are lacking data for various reasons.
As for why we don't have data for this element, I found my previous guess was correct that in these practices we will never have hospitalization data because they're not a hospital and patients aren't admitted to or discharged from them.


Extension doesn't work on github.com

There is not even a request to access the camera.
Firefox 124.0b2

Unfortunately some websites use CSP in a way that prevents this extension (and many others) from functioning properly. I do not have a quick solution for this. It might be possible to fix by restructuring the extension but since these websites quite few I don't think I'll get to it any time soon.


Bug report link changed

Description of changes
Replaced the bug reporting link with mailTo<EMAIL_ADDRESS>We want to make the website suggestion form more user friendly and It's currently not because users must create github accounts and follow our template.
Issue Resolved
https://github.com/OperationCode/operationcode_frontend/issues/1029

Thanks @kylemh. Just finding my way around github. Thanks for the warm welcome.

@abhinavdc check out our new repository here https://github.com/OperationCode/front-end
would love to see more contributions from you there!


Update dependencies to RTM

What is the plan of updating the project dependencies to rtm bits. I think corefx , coreclr and Asp.net Core packages can be updated to rtm releases.

You need to install latest dotnet core and sdk e.g by using build.cmd (but i don't use it) or from microsoft sites as here or for the latest dev build here. As i remember, the last time i've done it, i've used VS tools updating but i needed before to install Visual Studio 2015 Update 3.
Then, we already use rtm releases of Asp.net Core packages, e.g in Orchard.Web/project.json we use:
"dependencies": {
  "Microsoft.AspNetCore.Server.Kestrel": "1.0.0-*",
  ...

Then, after a dotnet restore from the Orchard2 root folder, core packages are updated, and in the related project.lock.json file we can see that rtm release 1.0.0 are used in place of 1.0.0-rc2-final:
  "Microsoft.AspNetCore.Server.Kestrel/1.0.0": {
    "type": "package",
    "dependencies": {
      "Libuv": "1.9.0",
      "Microsoft.AspNetCore.Hosting": "1.0.0",
      "Microsoft.Extensions.Logging.Abstractions": "1.0.0",
      ...

Best.

thanks for the info.


OHIF working when 'run dev:orthanc' but not when 'build'

Hi, I'm facing a weird problem. When I do 'yarn run dev:orthanc' the studylist shows normally, but does not load any thumbnails or images when I open a study (in console it appears as Uncaught (in promise) Error: [object Object]). When I do 'yarn build'  the studylist does not even show, with a message "Error: true" in top-left corner, and this on terminal:

I'm using port 8042 for DICOM, 8080 when building and 3000 when developping, and saving images in AWS S3.
My docker_nginx-orthanc.js:
window.config = {   routerBasename: '/',   showStudyList: true,   servers: {     dicomWeb: [       {         name: 'Orthanc',         wadoUriRoot: '/wado',         qidoRoot: '/dicom-web',         wadoRoot: '/dicom-web',         qidoSupportsIncludeField: false,         imageRendering: 'wadouri',         thumbnailRendering: 'wadouri',       },     ],   }, };
I'm using orthanc 1.9.7 (tried many versions) and OHIF local (both version 2 or 3 with same problem), but OHIF version 1 hosted in another server do the job perfectly, showing studies and images. I believe it is some misconfiguration but don't know what.

Hey, I have the same problem. Did you already fix it?
Can you help me?

Try viewer-dev.ohif.org instead of viewer.ohif.org
Our viewer.ohif.org is deployed from release branch while viewer-dev.ohif.org is our master  branch
Read more about branch explanations here https://docs.ohif.org/development/getting-started#developing
Please try and re-open if the issue persists


Create empty ResultDetailScreen

Creating empty screen for ResultDetail (#366)

Just switch the type as commented, looks good apart from that

Done. I also renamed id to detailId to keep the same convention as in BookingDetail

LGTM, @JoseDuSV, please also review again.


amazonka-core/test 1.3.7

amazonka-core-1.3.7 depended on by:

amazonka-iot-dataplane-1.3.6 (==1.3.6.*). Brendan Hay<EMAIL_ADDRESS>@brendanhay. @brendanhay

amazonka-test-1.3.7 depended on by:

amazonka-iot-dataplane-1.3.6 (==1.3.6.*). Brendan Hay<EMAIL_ADDRESS>@brendanhay. @brendanhay

I disabled iot-dataplane instead of adding all the upper bounds.

Appears to have been one of the numerous Hackage 50* errors during upload last night which I didn't catch with a retry. Uploading the correct 1.3.7 version now.

Now on Hackage.


Website - UI

[ ] Change complete design of All Tasks page

Sure, I have started with the work.

Done.


fix: scroll to add message input on input focus

Co-authored-by: Ashley Jelks<EMAIL_ADDRESS>The type of this PR is: Bugfix

This PR resolves PURCHASE-2251
Description

Scroll to add message input on input focus
Bonus (please feel free to revert): Grow inbox message input to a maximum of 200 pixels

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a CHANGELOG.yml entry or my changes do not require one.

Looks great, thanks @MounirDhahri !!


this program is better than ifc2 ngl

tbh, it really is
please dont delete this cyte42

This is not related to PasteFix.


handle_internal_errors in views.py does not produce a form error and fails silently

Should produce a form error ideally


Unable to obtain a certificate

Do you want to request a feature or report a bug?

Bug
If you use godaddy for dnsChallenge and try to get a certificate for a domain like *.dev.example.test, the record created will look like _acme-challenge.dev.example.test, but lego will not However, since lego only refers to the TXT record of example.test, the certificate cannot be obtained.

What did you do?

What did you expect to see?
What did you see instead?
Output of traefik version: (What version of Traefik are you using?)

(paste your output here)

What is your environment & configuration (arguments, toml, provider, platform, ...)?
# (paste your configuration here)

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
(paste your output here)

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.


ver 2.1.0: isn't using Image32 engine

Hi Carlo.
I've just downloaded and tested the SVGShellExtensions Setup binary.
Although there's an option to use Image32 in the SVGShellExtensions setup dialog (and it's enabled by default), it's not rendering preview images as I would expect (ie with filters, masks, text etc).

You must set Image32 and disable "Prefer Direct 2D"

Yes I had done that too 😁.

I'm fixing default assign to PreferDirect2D to false ;-)

Thanks. Mostly fixed now 😁.
I did have to toggle the Engine to get Image32 to work.
I suspect the radio and checkbox controls aren't properly synchronised with the startup settings.

yes, at startup the default value of PreferDirect2D was -1 instead of 0 :-(
I've fixed now in 2.2


Config option overrides for a single call

Adds overrideConfig function that allows the user to override config options for a single call, upon which it gets reverted.

Resolves #7, with the slight caveat that it is not integrated in the logging functions themselves


Datasource method is not triggering

Hi,
I have followed the instructions but its not working for me. Whenever I click on collection view cell YSL datasource method is not triggering. And can anyone help me to implement when I have 2 or more images in details screen.

More than one year and no solution yet?
And facing the same trouble here =(
No triggers on datasource PushTransitionImageView


fix(Dropdown,Editor,Input): common placeholer style

PR includes

[x] Bug Fix

QA Instructions, Screenshots, Recordings

/canary

/canary

/canary

/canary


Question about how to get the advertisement ManufacturerData to display from BLE Device without connecting

To help us fix your issue, please provide the information in the below template. If something causes a crash, provide as much information as you can gather.
Just imagine: we do not know what you are doing!

Note: There is often little we can do without a minimal reproducible sample of the issue, so please provide that in a standalone git repository and link it here.

Steps to reproduce
I am trying to display the ManufacturerData advertisement packet from the BLE Device without connecting to the device in the sample App but i am not sure how to..
Expected behavior
Display the ManufacturerData advertisement packet preferably under each device in the mainscreen (scanning screen) without connecting to them.
Actual behavior
N/A
Crashlog
N/A
Configuration
Version of the Plugin: 2.1.2
Platform: e.g. iOS 14.2
Device: e.g. Iphone 8 Plus

Hi @SSmurf99,
I'm the friendly issue checker.
Thanks for using the issue template :star2:
I appreciate it very much. I'm sure, the maintainers of this repository will answer, soon.

Try:
adapter.DeviceAdvertised += OnDeviceAdvertised;
await adapter.StartScanningForDevicesAsync();

and in your OnDeviceAdvertised handler have a look at the advertisement records:
        private async void OnDeviceAdvertised(object sender, DeviceEventArgs args)
        {
            var dev = args.Device;
            var adRecs = dev.AdvertisementRecords;
            foreach (var adrec in adRecs)
            {
                Debug.WriteLine(adrec);
            }
        }

I hope that the above answers your question. I'll close this issue.

in android and windows work fine, but in ios 16.6.1 AdvertisementRecords.Count always is 0, how can i fix this ?
Plugin.BLE: 3.0.0-beta.6
VS2022 MAUI Project

in android and windows work fine, but in ios 16.6.1 AdvertisementRecords.Count always is 0, how can i fix this ?

What works? It's unclear what you're doing and what you expect.

in android and windows work fine, but in ios 16.6.1 AdvertisementRecords.Count always is 0, how can i fix this ?

What works? It's unclear what you're doing and what you expect.

i am so sorry, it works fine,  just no return advertisementRecords with iBeacon ManufacturerSpecificData, only ServiceData.


[Event Hubs] Investigate token renewal when using AAD in Track 1

The current library for @azure/event-hubs of version 2.0.1 supports the use of AAD credentials as generated by using the @azure/ms-rest-nodeauth library.
We seem to be renewing the token (via the cbs link) every 45 mins instead of taking the expiry date (as returned by getToken() on the credential) into consideration.
This issue is to investigate why the above doesn't result in any failure? 1 possible reason is that the token itself has expiry greater than 45 mins. Since it is possible that ms-rest-nodeauth can change the expiry date at any time, we need to ensure that we are doing the right thing here.
Also, the token object returned by the AADTokenProvider adds an extra hour to the expiry date. This clearly looks wrong, need to investigate why this doesn't cause a problem. Probably because it is not getting used :)

@ramya-rao-a @mitchdenny @amarzavery
On debugging, I found that the token that gets returned expires in 28800 seconds i.e., 480 hours (20 days).
We could leave the program running for an hour or 2 and see what the new expiry time is, it's likely going to be set 20 days in future.
This explains why there are no failures when running receiver for long hours.
About fix for it, is there a document/configuration on Service Bus side that dictates this 20 day value?
Maybe a certain configuration/operations required us to consider 1 hour as renewal time which is about when the token gets renewed.
Longer investigation and maybe against multiple operations are required to determine how we can optimize this usage (or why was it optimized.)

is there a document/configuration on Service Bus side that dictates this value?

The token is returned from ms-rest-nodeauth library and is related to Azure Active Directory and not Service Bus. Take a look at the code in this library that generates the token, it might have hints on the value.
Summarizing:

AAD token has 8 hour expiry
Event Hubs and Service Bus renew the token every 55 mins (`tokenValidTimeInSeconds - tokenRenewalMarginInSeconds)
The actual expiry property on the token object never gets used by anyone
So as far as AAD token has expiry > 55 mins, our customers are good to go. But if ms-rest-nodeauth ever changes its logic to have its expiry < 55 mins, then we are in trouble :)

I believe this is for MSI, can you also test the Service Principal way of getting AAD creds and see what the expiry is?
Suggested fix should be to

Fix the bug in amqp-common where the expiry property is set wrongly
Update Service Bus and Event Hubs to use which ever is the lesser value between the expiry date and 55 mins from now as the token renewal

Thoughts?

I believe this is for MSI, can you also test the Service Principal way of getting AAD creds and see what the expiry is?

Right this is the expected behavior for MSI, the tokenRenewal related findings you have posted applies to all that use the _ensureTokenRenewal() utility.

Suggested fix should be to

Fix the bug in amqp-common where the expiry property is set wrongly
Update Service Bus and Event Hubs to use which ever is the lesser value between the expiry date and 55 mins from now as the token renewal

Thoughts?

Looks like we are wanting to investigate behavior with Service Principal as well. Based on findings we can finalize the fix if something stands out
But overall, agree with updating expiry time calculation and don't see issues as noone is using it.
About changing token renewal implementation in Service Bus/Event Hubs to use the expiry time, this needs more work and thinking through all the corner cases. Can we do it as part of Track 2? Do we need it for preview.6?

Sorry, when I meant I said I believe this is for MSI, can you also test the Service Principal way of getting AAD creds and see what the expiry is?, I meant to ask the expiry returned by the token. For MSI, it is 8 hours i.e >55 mins. Is the expiry > 55 mins for service principal as well?
Fixing of the expiry property in amqp-common is needed for Preview 6. Updating Service Bus and Event Hubs can wait, we can log an issue to track the required change.

There is one way where we only need to make the change in amqp-common and Service Bus/Event Hubs would not need any changes
Since upstream code (linkEntity.ts in Service Bus and Event Hubs) are using the tokenValidTimeInSeconds and tokenRenewalMarginInSeconds to decide when to renew the token, the AADTokenProvider class in amqp-common can be updated so that tokenValidTimeInSeconds points to the expiry time and tokenRenewalMarginInSeconds points to the right margin value.
This way no changes are needed in Service Bus/Event Hubs

This way no changes are needed in Service Bus/Event Hubs

Right, this still changes the way token renewal is being done in Service Bus and Event Hubs.
The concern that I have and trying to address is figuring out why was it specifically set to the values that they have - '3599' and 4.5 minutes for the margin.
It's also unclear where and how the 8 hour value is coming from.
On letting the app run overnight, noticed that expiry time is set to 8 hours in future each time consistently.
Here are couple more findings, based on - https://blogs.msdn.microsoft.com/azuredev/2018/07/23/understanding-azure-msi-managed-service-identity-tokens-caching/ (this one though seems much newer and not accurate of current state, but been navigating to other documentation available around ADAL and access tokens  - https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes)

It looks like the token is fetched from MSI endpoint as configured on the Azure VM. As such, the question is whether this is configurable and what may be the permissible values - still looking through code and documentation to determine
On going through the code for Service Principal based credentials, found that the tokens are fetched from ADAL, and it does not fetch it from an MSI endpoint or has the expires_on or expiry time being set - so the concern is that making this change may break functionality when other credentials are being used as the tokens may not have this value set.

cc @ramya-rao-a @mitchdenny @daviwil (if there's any more insights to shed)

The concern that I have and trying to address is figuring out why was it specifically set to the values that they have - '3599' and 4.5 minutes for the margin.

From what I have heard from @amarzavery, AAD tokens had a caching concept on their end and the cache would expire a few minutes before the actual token expiry. To capture all of this, we previously had the margin of 4.5 mins and 3599 is just to mimic "under an hour" concept.
Given that the different AAD credentials use different properties to specify the expiry information, this would need refactoring of TokenProvider in amqp-common.
The re-design of TokenProvider at this point is not worth the time. In the current model, as long as the token expiry is greater than 55 mins we are good. Let's keep it that way. We can re-visit the TokenProvider implementation if we have any user feedback on the same.

ms-rest-nodeauth depends on adal-node for
- interactiveLogin(): Promise<DeviceTokenCredentials>
- loginWithServicePrincipalSecret(): Promise<ApplicationTokenCredentials>
- loginWithServicePrincipalCertificate(): Promise<ApplicationTokenCredentials>
- loginWithUsernamePassword(): Promise<UserTokenCredentials>

The duration for refreshing tokens may be different for Credentials that use adal-node underneath  v/s MSITokenCredentials that is used in VirtualMachines or AppService created in Azure.

The concern that I have and trying to address is figuring out why was it specifically set to the values that they have - '3599' and 4.5 minutes for the margin.

You can take a look at the source code in adal-node over here, where adal-node will return the token from cache if it is not within the last 5 minutes of access token expiration. Thus we try to refresh the token within the last 4.5 minutes of refresh token. This will force adal-node to get the new access token that will be valid for the next 1 hour.
I forgot to comment this in the amqp-common library. Please make sure to comment about this and the link to adal-node source code for others to have a proper context.

Got it, this has been updated o the connected PR #4148
In addition to above, other findings that triggered these changes are that on debugging and running using sample with ApplicationTokenCredentials (which logs in using service principal), the expiry time being set seems to be 3600 seconds (1 hr).
This is the 'expiresIn' value being set on the TokenResponse instance.
However the 'expiresOn' in case of this type credential returns the value in milliseconds. Whereas for MSI based credential this is returned in seconds leading to discrepancies when expiry time is computed.
This is a bug as the milliseconds/seconds granularity is to be same across different type of credentials, and will be fixed in the future.

Closing this issue as the investigation is complete.
Final conclusion:

Event Hubs and Service Bus renew AAD tokens every 55 mins regardless of their expiry
Since the 4 types of AAD creds that are supported all have expiry > 55 mins we are good now
Next version of Event Hubs and Service Bus will be using @azure/identity which will not be having these issues


When will the code come out?

Good work! Are you planning to release the work?

Thanks for your interest in our work. The code has been out since May 2022!


fix build on linux

Fixed the build on linux. You might want to test that this still works on Windows with the modified CMake file

Just confirmed that it still works with Windows. Merging now.


Error in releases > 2.5.1

The version 2.5.1 release was working fine until I updated to 2.5.5, then I got this devtools error:

Firefox shows a slightly different error in devtools console:

The page that errors has a stache loop {{#for (item of items)}}. That loop stops printing any items in both browsers with an error in console. The home page still loads fine (that stache is without loops).
I tried version 2.5.2 which crashed the app while 2.5.3 and 2.5.4 did not show any errors in console but still no items printed on the page with the loop in stache.
I'll be sticking to 2.5.1 for now. Let me know if you have any ideas of what you want me to try.

Thanks for reporting. Releases after 2.5.1 were meant to bring support for the {{#portal()}} helper to done-autorender based apps. It was a big-ish change.  I would like to fix this as soon at possible.
Does this error happen in your terminal in a donejs app or in the browser console?

@leoj3n would you might upgrading to the latest and see if you still get it? I changed how this stuff works a bit.


Add growatt server integration

Description:
Adds intergration for growatt photovoltaic inverters connected to the growatt server
Related issue (if applicable): community post
Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#10032
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: growatt_server
    username: <growatt server username>
    password: <growatt server password>

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

Hi @indykoning,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Thank you for your feedback @MartinHjelmare, this is my first pr so I'm learning a lot from the feedback! I will get to it as soon as possible. I won't have access to my computer for about 3 weeks though so it may take a little while.

I have updated the code according to your feedback @MartinHjelmare
There was one thing i have left unchanged since i couldn't quite understand what should happen to it.

Please don't squash commits after review has started to make it easier for readers to track changes.

Nice! If we can implement a unique_id, I think this is ready.
What do you mean with implementing a unique_id?
For the sensors? since the inverter_id should already be unique per inverter.

Can be merged when build passes.

I will update this PR once more later today since i couldn't successfully run it overnight since i tried only logging in at the start and hoping the session stayed active.
It seems it did not.

The issue should be resolved now.


Use a real BOSH Director to run system tests using BOSH-in-Docker

[#183873383]
Using BOSH-in-Docker has several benefits over the previous approach:

Removes the need of maintaining a new tool "boshcompiler"
Uses official BOSH under-the-hood so we can also test deployments and other BOSH operations that were impossible before
We can also test compilation as before but with better guarantees

There are little or no drawbacks to this approach in comparisons:

It runs in GitHub Actions
It runs locally
It is as fast as the previous approach

Nice.
Is it possible to use the CI manifests in those Dockerfiles? If not, that's fine.


Added a new folder in bonus folder

Updated the bonus9logic.md along with the .txt file of the problem Longest Prefix Suffix

not needed

not needed


Logo image causes SSL warning (and is not compatible with migrations)

The ng_slicknav_brand image logo url needs to be RELATIVE - the full URL is used and retained across domain migrations (security and content integrity issue). The generated js code looks something like:
/* <![CDATA[ */
var slickNavVars = {"ng_slicknav":{"ng_slicknav_menu":"#primary-menu",
"ng_slicknav_position":"body", "ng_slicknav_parent_links":false,
"ng_slicknav_close_click":true,"ng_slicknav_child_links":false, "ng_slicknav_speed":200,
"ng_slicknav_label":"MENU", "ng_slicknav_fixhead":true, "ng_slicknav_hidedesktop":"block",
"ng_slicknav_brand":"**http:\/\/stuck.on.old.domain.this.should.be.relative!.com**\/wp-content\/uploads\/2018\/07\/logo.dark-bg.png",
"ng_slicknav_brand_text":"", "ng_slicknav_search":true, "ng_slicknav_search_text":"search...",
"ng_slicksearch":"**https:\/\/this.should.also.be.relative!.com**\/", "ng_slicknav_closedsymbol":"",
"ng_slicknav_openedsymbol":"", "ng_slicknav_alt":"", "ng_slicknav_accordion":true,
"ng_slicknav_animation_library":"jquery"}};
/* ]]> */

So, the full url is in the setting, so left to end user to make the link relative. A bit confusing since it's auto-generated from the media library - that's the point where it should probably not incorporate the full domain.

The plugin simply passes through whatever element or data is placed in the "brand" property. It is up to the user to specify proper urls.

The plugin simply passes through whatever element or data is placed in the "brand" property. It is up to the user to specify proper urls.

Why can't it force relative urls? This is sloppy

Why can't it force relative urls? This is sloppy

I am confused about what you are expecting. The brand option will take any html and is not explicitly an image or url and can be used for any type of display. The field is simply a passthrough and does not manipulate the input.

I am confused about what you are expecting. The brand option will take any html and is not explicitly an image or url and can be used for any type of display. The field is simply a passthrough and does not manipulate the input.


spring animation time

How long does it take to finish the spring animation?
When I want to set an animation duration, how can I do?

React-motion does not use time based animations.
I am not an expert but if you want to influence how long an animation takes you should add Stiffness and Damping to your animations.


K3s Integration

This adds the ability for Rancher to import k3s clusters and upgrade them
Addresses: https://github.com/rancher/rancher/issues/25371

failures are unrelated. im merging


readme: bump example to v6

Codecov Report

Merging #88 (e8aad51) into master (09bee59) will not change coverage.
The diff coverage is n/a.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Update AI key

VSCode Extension Installation Instructions

Download the extension at https://azuresdkreleasepreview.blob.core.windows.net/azd/vscode/pr/82/azure-dev-0.2.0.vsix
Extract the extension from the compressed file
In vscode
a. Open "Extensions" (Ctrl+Shift+X)
b. Click the ...\ menu at top of Extensions sidebar
c. Click "Install from VSIX"
d. Select location of downloaded file


Unable to configure Audit log connector

Hi guys,
we are trying to deploy CoE Starter Kit to our environment. Unfortunately, we are unable to get through audit log connections. We tried both options the Azure AD app registration and the basic authentication.
Issues facing with Azure App:
We follow the deployment process described here. Everything goes fine until we hit the "Test Operation" button at the "TEST" tab of the connector.
We always get following error:
Headers
{   "cache-control": "no-cache",   "content-length": "71",   "content-type": "application/json; charset=utf-8",   "date": "Tue, 05 Jan 2021 09:22:33 GMT",   "expires": "-1",   "pragma": "no-cache",   "x-aspnet-version": "4.0.30319",   "x-ms-apihub-cached-response": "false",   "x-powered-by": "ASP.NET" }
Body
{   "error": {     "code": "AF20023",     "message": "The subscription was disabled."   } }
Not sure if it might be related but we also see this in the "Schema validation" section:
Property "" type mismatch, Expected: "array", Actual: "object".
The question is which subscription was disabled and how to enable it. MS case did not help...
Thank you
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9fe69498-a485-5379-97ff-53fbe029f11a
Version Independent ID: 5b3f9705-9e49-1575-4ae7-0293d12b739c
Content: Set up core components - Power Platform
Content Source: power-platform/guidance/coe/setup-core-components.md
Service: power-platform
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

For issues with the CoE Starter Kit itself (and not with the documentation), could you please raise them through https://github.com/microsoft/powerapps-tools/issues where they'll be assigned to the appropriate team.
From looking at the error message, have you completed this step to start a subscription, before trying to pull content from the Audit Log?
https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-auditlog#start-a-subscription-to-audit-log-content
When was the Audit Log enabled in your tenant? Often it can take up to 24hrs to be active, and for the API to works.

For issues with the CoE Starter Kit itself (and not with the documentation), could you please raise them through https://github.com/microsoft/powerapps-tools/issues where they'll be assigned to the appropriate team.
From looking at the error message, have you completed this step to start a subscription, before trying to pull content from the Audit Log?
https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-auditlog#start-a-subscription-to-audit-log-content
When was the Audit Log enabled in your tenant? Often it can take up to 24hrs to be active, and for the API to works.

(closing here, please re-raise via https://github.com/microsoft/powerapps-tools/issues if you continue to see issues)

(closing here, please re-raise via https://github.com/microsoft/powerapps-tools/issues if you continue to see issues)


Header height changes between main page and other pages if a logo is used

Something in the padding code still results in the header bar changing its height between the main page and the other pages in case a logo is used.

I just tested 1.15.1 to verify that the bug still exists.

Thank you for filing this case. I can see, why. What I tried to do is to make the logo unclickable on the homepage (because you are already on the homepage). As a consequence, there is a padding applied on the link wrapping the logo which is currently only applied on all pages except the home page.
I'm trying out a few ideas to make this more robust.


PWA on iOS sometimes crashes with an IndexedDB error

:lady_beetle: Describe the bug

When resuming the installed PWA from the background, it sometimes crashes with an error from IndexedDB/Dexie:
UnknownError: Attempt to get count from database without an in-progress transaction
:computer: Components impacted

Web app, iOS only
:bulb: Screenshots and/or logs

UnknownError: Attempt to get count from database without an in-progress transaction
 UnknownError: Attempt to get count from database without an in-progress transaction
  at undefined (UnknownError: Attempt to get count from database without an in-progress transaction:undefined:undefined)
  at undefined ( UnknownError: Attempt to get count from database without an in-progress transaction:undefined:undefined)
  at timeout (https://staging.ntfy.sh/static/media/index-06629207.js:62485:222)
  at t (https://staging.ntfy.sh/static/media/index-06629207.js:4036:221)
  at zh ([native code]:undefined:undefined)
  at timeout (https://staging.ntfy.sh/static/media/index-06629207.js:24470:222)
  at t (https://staging.ntfy.sh/static/media/index-06629207.js:5832:221)

UnknownError: Attempt to get count from database without an in-progress transaction
 UnknownError: Attempt to get count from database without an in-progress transaction
  at Rq@https://staging.ntfy.sh/static/media/index-06629207.js:336:71367
  at x8@https://staging.ntfy.sh/static/media/index-06629207.js:240:3960
  at O8@https://staging.ntfy.sh/static/media/index-06629207.js:240:6876
  at QH@https://staging.ntfy.sh/static/media/index-06629207.js:317:5812
  at withI18nextTranslation(QH)@https://staging.ntfy.sh/static/media/index-06629207.js:268:3139
  at i$@https://staging.ntfy.sh/static/media/index-06629207.js:61:18625
  at s$@https://staging.ntfy.sh/static/media/index-06629207.js:61:19028
  at Q$@https://staging.ntfy.sh/static/media/index-06629207.js:61:29591
  at A8@https://staging.ntfy.sh/static/media/index-06629207.js:240:6337
  at M8@https://staging.ntfy.sh/static/media/index-06629207.js:249:781
  at Suspense
  at Aq@https://staging.ntfy.sh/static/media/index-06629207.js:336:70571

:crystal_ball: Additional context

WebKit Bug: https://bugs.webkit.org/show_bug.cgi?id=197050
Other projects that ran into the same or similar issue

https://github.com/firebase/firebase-js-sdk/issues/2232
https://github.com/pouchdb/pouchdb/issues/8329

Yes, this happens almost every day so would be nice for it to be fixed.


"Show Debug Logs" as option in mainmenu

See tweet: https://twitter.com/ottosuess/status/1086201889765687296
To add an option in the menu to make it easy for people to "see/monitor" and "send" logs for support (pastebin, email).

Would recommend this for 1.1 release.


Draft: codecov github action added

Description
Adds Codecov GitHub Actions

References
#548

Tasklist

[ ] Add test case(s)
[ ] Ensure all CI builds pass
[ ] Review and approve

Please don't worry about commits, I will squash them in a nice single commit :)

For the records, the codedov port to GitHug Actions has already been prototyped by @meshtag  in https://github.com/boostorg/gil/pull/554

Hello @mloskot, I have a little doubt here, how do I build Boost.GIL, I tried looking for it, but no luck so far. I am thinking likr this.
# run get-boost.sh
mkdir build
cmake ..
cmake . #options here

Please tell me if I am going in the right direction.

Hello @mloskot, I need some help now. I am not much experienced with codecov. But as much I know public repositories don't need tokens to upload reports.
The GitHub Actions is perfectly working. You can see the last run here: https://github.com/boostorg/gil/pull/564/checks?check_run_id=1971222975#step:6:1049
It is also being picked by Codecov, which is good

But for some reason, reports are not showing up. I don't know what else is missing.

@avinal I'm afraid I have nothing helpful to offer. I had been struggling in the past with Codecov without having a slightest clue what was going wrong.

For the records, the Codedov port to GitHub Actions has already been prototyped by @meshtag in #554

meshtag missed a really important step that is to compile the library with a coverage flag. Then only you can run the codecov routine. (P.S, I missed it too initially 😅)

@avinal I'm afraid I have nothing helpful to offer. I had been struggling in the past with Codecov, https://github.com/codecov/codecov-bash/search?q=mloskot&type=issues, without having a slightest clue what was going wrong.

Ohh, I will try to solve this. 👍

Hello @mloskot,
It is all working now.

There are more things we may add:

A codecov.yml to further customize reports (I did not notice any significant difference though)
A codecov badge, needs to be added from your side

@avinal Awesome!

A codecov.yml to further customize reports (I did not notice any significant difference though)

AFAIR, my experience with this file was similar.
I sometimes used it to disable Codecov comment
I think we could experiment with the comment configuration to avoid unnecessary PR comments, e.g.
comment:
  layout: "diff"
  behavior: default
  require_changes: true # if true: only post the comment if coverage changes

A codecov badge, needs to be added from your side

We could add two badges to the statuses in the README:

https://codecov.io/gh/boostorg/gil/branch/develop/graphs/badge.svg
https://codecov.io/gh/boostorg/gil/branch/master/graphs/badge.svg

P.S - By no means it was a good-first-issue

Well, the difficulty was judge from the GIL point :-)
Kudos for your persistence!

This looks very good. Thanks!
I'd like to merge it as it is.
If you'd like to apply any further tweaks, then I suggest to do it in new PRs

Ohh actually I was adding those two changes. I will open a new PR, no worries 😊

Sorry for not synchronising our actions better. Please, do new PRs, thanks

I incorrectly put Closes #565 in the commit message. It should read #548


Revamp Your Website: Stylish Navbar Menu & Font Family Update for Contributing to an Open-Source Project for a Sleek and Modern Design

Before Changes***********

After Changes**********

Hi @vishanurag
I recently updated the navbar menu and font family for your project to make it more attractive and user-friendly. Enhance readability, improve navigation, and give your site a visually appealing touch that stands out with these simple yet impactful design updates. I've attached screenshots of the changes, and I'd love to contribute to this enhancement to improve the overall design.
Please assign me to this task. It would be a great opportunity for me to contribute while enhancing my skills.
I'm looking forward to hearing back from you!
Best regards,
@khurshed07
https://github.com/khurshed07

Hi @vishanurag
Please assign this issue #281 to me for contribution

Hi @vishanurag
Please assign this issue #281 to me for contribution

Hi @vishanurag
Please assign this issue https://github.com/vishanurag/Canvas-Editor/issues/281 to me for contribution

Hi @vishanurag
Please assign this issue #281 to me for contribution

Hi @vishanurag
Please assign this issue #281 to me for contribution

Hi @vishanurag
Please assign this issue #281 to me for contribution

Hi @vishanurag
Please assign this issue #281 to me for contribution

Hi @vishanurag
Please assign this issue #281 to me for contribution


[Feature Request]: Add hover effects on cards under section  Our Code Editor

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I will add some scale and transition so it will looks good.
Use Case
user friendly website.
Benefits
No response
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@VaibhavArora314 Please assign me !

@VaibhavArora314 Please assign me !

Hey  @zalabhavy mak it responsive for all sizes ...which I created it i forget to make it responsive...I mean text size is not responsive...I hope you will do that..
Thank you .!


replace rossrad.dat with rossrad.nc (#1083)

Description
Three files reference rossrad.dat whereas test/Data contains rossrad.nc.  This PR replaces the three occurrences of rossrad.dat with rossrad.nc.
Issue(s) addressed

fixes #1083

Testing
to be done
Dependencies
none

Document problem with develop at 204a3eee
Install develop at 204a3eee on Hercules.  Load GDASApp modulefiles/GDAS/hercules.intel.lua to build soca.  Build is successful.  Next execute make install.  Install failed with the following error
-- Installing: /work/noaa/da/rtreadon/git/soca/soca_install/share/soca/testdata/72x35x25/INPUT/ocean_hgrid.nc
-- Installing: /work/noaa/da/rtreadon/git/soca/soca_install/share/soca/testdata/72x35x25/INPUT/ocean_topog.nc
CMake Error at soca/test/cmake_install.cmake:65 (file):
  file INSTALL cannot find
  "/work/noaa/da/rtreadon/git/soca/recursive/bundle/soca/test/Data/rossrad.dat":
  No such file or directory.
Call Stack (most recent call first):
  soca/cmake_install.cmake:84 (include)
  cmake_install.cmake:65 (include)

make: *** [Makefile:130: install] Error 1

install is looking for rossrad.dat.  The file is now rossrad.nc.

Document fix with bugfix/rossrad at 9d9d318
Install bugfix/rossrad 9d9d318 on Hercules.  Load GDASApp modulefiles/GDAS/hercules.intel.lua to build soca. Build is successful. Next execute make install.  The install successfully ran to completion.  In partcular, file rossrad.nc is installed
- Installing: /work/noaa/da/rtreadon/git/soca/rossrad_install/share/soca/testdata/72x35x25/INPUT/ocean_hgrid.nc
-- Installing: /work/noaa/da/rtreadon/git/soca/rossrad_install/share/soca/testdata/72x35x25/INPUT/ocean_topog.nc
-- Installing: /work/noaa/da/rtreadon/git/soca/rossrad_install/share/soca/testdata/rossrad.nc
-- Installing: /work/noaa/da/rtreadon/git/soca/rossrad_install/share/soca/testdata/godas_sst_bgerr.nc

The changes in this PR are required for GDASApp branch feature/install to successfully complete the install (see comment here).  For additional details see GDASApp issue #1302.

Thanks, I made one small change of removing rossrad.nc from .gitattributes. That line is not needed since it is covered by the above *.nc case.

Thanks, I made one small change of removing rossrad.nc from .gitattributes. That line is not needed since it is covered by the above *.nc case.

Thank you @travissluka for making this correction.

Thank you @travissluka


Feat/paginator-optional-size

Linked Issue
Closes #2066
Description
when the size is optional, all controls depending on it are hidden.
Changsets
Instructions: Changesets automate our changelog. If you modify files in /packages/skeleton, run pnpm changeset in the root of the monorepo, follow the prompts, then commit the markdown file. Changes that add features should be minor while chores and bugfixes should be patch. Please prefix the changeset message with feat:, bugfix: or chore:.
Checklist
Please read and apply all contribution requirements.

[x] This PR targets the dev branch (NEVER master)
[x] Documentation reflects all relevant changes
[x] Branch is prefixed with: docs/, feat/, chore/, bugfix/
[x] Ensure Svelte and Typescript linting is current - run pnpm check
[x] Ensure Prettier linting is current - run pnpm format
[x] All test cases are passing - run pnpm test
[x] Includes a changeset (if relevant; see above)

@Mahmoud-zino it looks like we hav a bug. In fact, I'm not sure how we'll overcome this. But when no size is present we don't know the max range, so you can just navigate to the next page forever. Well beyond the limit of the content itself.

I think we may just want to trust our gut on this one and make the recommendation that we don't support pagination without a size defined. If if the end users have to query this separately, they should be able to know the max number of items, which is crucial for pagination to work at all.

@endigo9740 I noticed this when testing but I didn't consider it a bug because if the size is not known, it should be expected that we can't limit the paginator.
With that being said, I can see why this could cause us more trouble than benefits and I agree that we should not implement it. 😄

@Mahmoud-zino yeah this will look and feel busted to end users. They won't understand why this occurring since there's no indicator they've reached the end of the content.


Console error on Workflow info page

Bug Report
Occasionally seeing an error in the browser console on the workflow info page:
InfoTabComponent.html:105 ERROR TypeError: Cannot read property 'toString' of undefined
    at MapFriendlyValuesPipe.push../src/app/search/map-friendly-values.pipe.ts.MapFriendlyValuesPipe.transform (map-friendly-values.pipe.ts:60)
    at checkAndUpdatePureExpressionInline (core.js:19319)
    at checkAndUpdateNodeInline (core.js:19888)
    at checkAndUpdateNode (core.js:19846)
    at debugCheckAndUpdateNode (core.js:20480)
    at debugCheckRenderNodeFn (core.js:20466)
    at Object.eval [as updateRenderer] (InfoTabComponent.html:105)
    at Object.debugUpdateRenderer [as updateRenderer] (core.js:20458)
    at checkAndUpdateView (core.js:19833)
    at callViewAction (core.js:20069)

I cannot reliably reproduce, and I'm not sure what the user facing implications are, but I've seen it twice.
┆Issue is synchronized with this Jira Bug
┆Issue Type: Bug
┆Fix Versions: Dockstore 1.7
┆Issue Number: DOCK-287

Interesting, the workflow descriptorType appears to be null

Cannot reproduce with my http://<IP_ADDRESS>.nip.io:4200/workflows/github.com/nf-core/rnaseq:1.0?tab=info  .  It's probably fixed


Remove cashed DS_Store and make personal directory under homework.

.gitignore seems to be failure for ignoring DS_Store. I guess that DS_Store has been added before generating .gitignore.


Docs: Project, Releases, Security Vulnerability navigation links broken

Current State:
The Project, Releases, Security Vulnerability pages need to be updated to respond to /project/releases, /project/security-vulnerability.
Desired State:

The project page needs an iterator added to it to display links to all pages under this category similar to the guides page index.

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

@gunjanmimo @ashiscs @manishdangi98 would one of you like to take this one on?

@leecalcote sure

Thank you, @manishdangi98. 👍


Search does not work

example:
https://vimeo.com/198175671

in my configuration it works with elasticsearch 1.7.3
Did you run ./manage rebuild_index?
 Please refer to the ES documentation and check how to setup.


Right-click paste with \n comes out upside down?

When using PSReadLine 1.2, and pasting text that has newlines without carriage returns, the lines come out in reverse order.

Seems to be happening because of this key handler: https://github.com/lzybkr/PSReadLine/blob/master/PSReadLine/KeyBindings.cs#L135
LF triggers InsertLineAbove which pushes each text line down as the right click paste is getting processed one char at a time. CRLF works fine because CR triggers AcceptLine. Ctrl+V paste works because it inserts all of the clipboard in one go.
Workaround
Remove-PSReadlineKeyHandler Ctrl+Enter

Closing in favor of #579 which covers all of the known issues with right-click paste.

How and why is this not fixed?


add: Billy Li's username to usernames.txt

Added billy000400 to usernames.txt

Could you resolve conflicts, please?


Correct links to Lambda extension docs

AWS Lambda extension docs moved from the APM Guide to their own docs. Fixing links.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-10-17T14:56:27.035+0000

Duration: 3 min 30 sec

:grey_exclamation: Flaky test report
No test was executed to be analysed.
:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


test(Python): Updated simple action/model tests

Pull Request Description
Description:
Adding additional Python tests
Related Issue:
Checklist

[x] I have added the appropriate prefix  to the pull request title
[x] The CI tests are passing for this pull request.
[x] The pre-commit run -a hooks are passing for this pull request.

This PR is included in version 0.4.1 :tada:

This PR is included in version 0.4.1 :tada:


FollowPath: execute path only once

Short Description
Sometime I prefer the bot to follow the path only once, instead of looping. This could be useful for having the bot walk to a new location following a number of waypoints, and then go chasing pokemon and pokestops at the new location.
Possible solution
In the FollowPath configuration, implement path_mode = 'single'. In follow_path.py in the work() function, check for this path_mode in the piece of code that handles the situation where the end of the path is reached. If so, return WorkerResult.SUCCESS to allow lower priority tasks to run.
How it would help others
It would help if you want your bot to walk to another location once, and there in the new area after the path is finished.

Or add something like 'stop' on map.json
(and pause tot sec)

A similar effect can be achieved now.
Set the number of laps
"number_lap": 1,
A restart time eg
"timer_restart_min": "06:00:00",
"timer_restart_max": "07:00:00"
After each lap be a break 6-7 hours

Not exactly : in that case the bot would stop completely instead of going off chasing pokestops (if you put in a Move to Tower with a lower priority)
On 24 August 2016 18:08:45 CEST, "Przemysław "<EMAIL_ADDRESS>wrote:

A similar effect can be achieved now.
Set the number of laps
"number_lap": 1,
A restart time eg
"timer_restart_min": "06:00:00",
"timer_restart_max": "07:00:00"
After each lap be a break 6-7 hours
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/PokemonGoF/PokemonGo-Bot/issues/4663#issuecomment-242121099

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.


Windows Fluent Design Theme

This project is great, exactly what we need for compose desktop apps to feel platform native.
A theme for windows would be really great, maybe following Microsoft's new Fluent design: https://www.microsoft.com/design/fluent/

I've already made a button for fluent. Feel free to contribute. It's fun and a great way to learn more about compose


Entity has no state

System Health details
System Information

version
core-2024.2.2

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.1

os_name
Linux

os_version
6.1.63-haos-raspi

arch
aarch64

timezone
Europe/Rome

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
5000

Installed Version
1.34.0

Stage
running

Available Repositories
1400

Downloaded Repositories
87

Home Assistant Cloud

logged_in
true

subscription_expiration
January 1, 2018 at 01:00

relayer_connected
false

relayer_region
null

remote_enabled
true

remote_connected
false

alexa_enabled
true

google_enabled
true

remote_server
null

certificate_status
null

instance_id
837ab25cbf944202946611186c9b3f4e

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 11.5

update_channel
stable

supervisor_version
supervisor-2024.01.1

agent_version
1.6.0

docker_version
24.0.7

disk_total
916.2 GB

disk_used
350.0 GB

healthy
true

supported
true

board
rpi4-64

supervisor_api
ok

version_api
ok

installed_addons
Samba share (12.3.0), File editor (5.8.0), Advanced SSH & Web Terminal (17.1.0), Log Viewer (0.17.0), InfluxDB (5.0.0), Home Assistant Google Drive Backup (0.103.1), Studio Code Server (5.15.0), Grafana (9.1.3), Mosquitto broker (6.4.0), Glances (0.21.0), RPC Shutdown (2.4), Syncthing (1.18.2), WireGuard (0.10.2), Samba Backup (5.2.0), rsync (1.7.0), ESPHome (2024.2.0), RTSPtoWeb - WebRTC (1.4.0), Duck DNS (1.15.0), NGINX Home Assistant SSL proxy (3.8.0), A9 Camera fake server (2.4), AdGuard Home (5.0.3), Node-RED (17.0.7), Zigbee2MQTT (1.35.3-1), LibreTiny ESPHome (2023.9.0-dev)

Dashboards

dashboards
10

resources
61

views
85

mode
storage

Recorder

oldest_recorder_run
November 30, 2023 at 15:23

current_recorder_run
February 21, 2024 at 02:37

estimated_db_size
17789.49 MiB

database_engine
sqlite

database_version
3.44.2

Xiaomi Gateway 3

version
3.3.6 (6a494ae)

Xiaomi Miot Auto

component_version
0.7.15

can_reach_server
ok

can_reach_spec
ok

logged_accounts
1

total_devices
22

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of any previous issues..

Describe the issue
Hi, thanks for your work on this import service.
I imported the file and I have the green check at the end, here below a string of my test file (616 lines, tab separated):
statistic_id	unit	start	min	max	mean
sensor.import_test	EUR	28.02.2023 14:00	19647	19647	19647
The problem is that when I check the entity in developer tool/statistic it shows me "there is no state available for this entity." and the only option from fix button is to delete the entity.
Furthermore the entity is not listed in developer tools/states so is not possible to update the current state.
I see no info about the service in the debug log viewer.
Reproduction steps

import the file from the service
check statistic
create state - entity not in the list

Debug logs
---

Diagnostics dump
No response

The problem is that you can only add statistics for already existing entities. For not existing entities, the :-syntax should be used (like sensor:sensorName instead of sensor.sensorName), but this is not yet working with the integration. I will have a look.

Fixed with version 1.0.0. You can now import e.g. sensor:sensorName as well.


Fix os_version and os_version_min conflicting fields

Small bug found while investigating #372

Looks good to me, what was the issue with the path.MatchRoot("node_pools").AtAnyListIndex().AtName validation?

I'm not sure why, but the framework was throwing the error that os_version was set in some ListIndex, which was not the case. So I decided to implement the validation in each individual nodepool, so that we have more control of what we are checking.
Also, it seemed more complex to try to implement that using path expressions which don't support something like validation at the same index out of the box.


first run of timesketch scaffolder

while testing timesketch code generation PYTHONPATH=. python3 tools/l2t_scaffolder.py I encountered the following error[0], it did not affect the end results but it could be related to the use of relative paths.
Path [../timesketch] set as the project path.
[0] - Error:
ERROR:root:Running: "git checkout test_analizer" failed with error: error: pathspec 'test_analizer' did not match any file(s) known to git

try updating the tool and try again... to see if this becomes an issue again....

I ran it again (from HEAD) and I got ERROR:root:Running: "git show-ref --verify --quiet refs/heads/"plugin_test"" failed with error: .
everything worked well, though. this should be WAI since the command did not found the branch.


How to run this example?

It compiles failed on xcode14,  can anyone helps me?

the error now is:
sandbox-exec: sandbox_apply: Operation not permitted
Command PhaseScriptExecution failed with a nonzero exit code

Hm, I can reproduce this. Not sure yet what's wrong here.

Looks like just the Bodies example fails, NorthwindSwiftUI works.

Maybe was b0rked by Apple as part  of this: https://support.apple.com/en-us/103012

Same in Xcode 15.0.1 btw.

Since I suspect that Apple is not going to fix Xcode 14.3, there is little we can do about this.
(the database could probably be moved to a local SPM project, but that would defeat the purpose of the sample)

Looks like just the Bodies example fails, NorthwindSwiftUI works.

@helje5 yes, the   NorthwindSwiftUI works and can be compiled and run, but it still get lots errors on Xcode IDE,  hot to fixit?

How to find the source code of  Northwind.Product ? How to generate it?

The source is generated from the database, that is what Lighter does. Errors shown initially should go away after doing the build.

errors hav't  gone away yet,  but the app can run!