ADD: hoc pattern

Pull request fixes issue #7
Checklist

[x] Is the translation source specified?
[x] Did you add a link for your translation in the main readme file?

Description (Optional)
...

@all-contributors please add  @ismailgunayy for translation


Some kind of middlewares for Notification

Ciao @jbogard!

behaviors are fine for sending message
behaviors do not work for publishing notifications

then, is there any way to add some kind of middleware for notifications?
Thanks,
Luca

What kind of middleware? Around all notifications sent, or just one?

all of them, for example for logging purposes, or just storing events on a CQRS system.
does this make sense?

Depending on your container that you use you can do all of those. The Mediator class itself has a method you can override, and if your container supports decorators you can add wrappers around your notification handlers.
The middleware I put in was just some convenience stuff because some containers are a bit of a pain to deal with, or don't support those features.

Yeah it does, I can just use the Autofac interceptors to deal with this, and it's working, so I'm actually fine.
Thanks man, keep up the good work.
Luca

Can you show what you’ve got going? I designed the existing behaviors off
of real world usage but we don’t do any sort of notification pipelines so I
don’t have any examples to work with.
On Sat, Mar 3, 2018 at 3:53 AM Luca Trazzi<EMAIL_ADDRESS>wrote:

Yeah it does, I can just use the Autofac interceptors to deal with this,
and it's working, so I'm actually fine.
Thanks man, keep up the good work.
Luca
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jbogard/MediatR/issues/241#issuecomment-370135168,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGYMgSb913zUWEFdWh5XEl9L26pKMYYks5tamgGgaJpZM4SaSBF
.

Yeah sure,
here you go.
``
builder.RegisterType();
builder
.RegisterType()
.As()
.InstancePerLifetimeScope()
.EnableClassInterceptors()
.InterceptedBy(typeof(MediatorSnifferInterceptor));
``
public class MediatorSnifferInterceptor : IInterceptor {     public void Intercept(IInvocation invocation)     {                    // your stuff here         invocation.Proceed();     } }
It's actually work only for Publishing, not for Sending.. IDK why, so I'm combining pipeline with that.
I wanted to achieve that on my unit tests.
_sandbox.ShouldMediator.Be("CreateAccount -> AccountCreated");


Version Selection Button Enhanced

Signed-off-by: Anirudh Patel<EMAIL_ADDRESS>Description
Styling the Version selection Button on the header of Meshery's Docs
This PR fixes #
Previous Button

Styled Button

Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit 80f998c3cb364ccdfcfd8afa738cd40fb1b4c433 at: https://63111669fe4bd353ac6b1080--meshery-docs-preview.netlify.app

@l5io what am I supposed to do now?

Thanks, @anirudhp26 👍
Gosh, I'm not certain that the issue this PR refers to (is created from) is still valid anymore, though. @warunicorn19 can make this call.

We had an open issue on this before, but I  feel this color doesn't go with the background 🤔.

We had an open issue on this before, but I feel this color doesn't go with the background 🤔.

Yeah but I needed feedback but no one showed up on this PR so had to do it anyway
We can change it still right ! @warunicorn19

Though this was my First PR and first Contribution in Git Hub se i am new to all this

@warunicorn19 how is this lookingg, can we use this ?

Its the color already used for the landing page buttons like quick start etc.

Yeah but I needed feedback but no one showed up on this PR so had to do it anyway We can change it still right !

I'm confused. Three different contributors offered feedback within 5 hours of this PR being opened. How is it that "no one showed up on this PR" leaving you to "so had to do it anyway", @anirudhp26?

@anirudhp26 this really isn't worth the hassle. Please close the two duplicate, non-triaged (validated) issues that you've filed. Let's go ahead and close this PR as well.
Thank you for opening new issues when you see something awry. This is much appreciated. In the future, please await confirmation from another contributor (ideally, a maintainer) before proceeding with implementation of a fix in order to spare potentially lost effort.
Thanks for engaging in the project. I encourage you to seek out another "help wanted" issue and continue to participate. 👍

Yeah but I needed feedback but no one showed up on this PR so had to do it anyway We can change it still right !

I'm confused. Three different contributors offered feedback within 5 hours of this PR being opened. How is it that "no one showed up on this PR" leaving you to "so had to do it anyway", @anirudhp26?

I am really sorry for the inconvenience caused will follow what you said.
I am new to all this so i have no idea how to conduct things like this


ctrl+p picker for loaded scripts

Testing #57249

launch chrome with remote debugging enabled
attach to it from VS Code

The loaded scripts view is there, but it is difficult to jump to a specific file name in the style of quick open.

After switching to the new tree view, the loaded scripts view now supports filtering.


Comments (replies) page

i.e. the page you get from expanding a top-level post

This is done by #74, but again subject to future UI improvements


Eth Calls tutorial

Would be good to show how to batch eth calls, i.e. decimals(), totalSupply(), symbol() ERC20 calls would often be batched together.

@YaroShkvorets Thanks, I'll include in another PR.


How do I parse bog-standard syslog format?

New user here.
I'm trying to read standard Linux system log files, lines that start with Feb 20 00:16:38 some log message here.
As you can see, it doesn't have the year.

And when I add it to a new worksheet, it says the time range is from 1969-02-28 3:59:59 pm to 1969-02-28 4:00:00 pm.
This does not seem normal.  :-/

There are maybe a couple of things at play here.
First of all, as you've mentioned, the source data is missing the year information, so binjr has to complete the elements its got with a default starting point in time, as it cannot deal with partial dates.
For better or worse, the default date I have chosen is 1970-01-01 00:00:00.000 UTC, which is 1969-12-31 16:00:00.000 (4pm) in your timezone (UTC-8).
So this explains why the year shown here is 1969: because the year component for the date was not provided, 1969 is used as a substitute while the day and month are overridden with the data parsed from the file.
With that said, even with this does not explain why the time components are not overridden (e.g. it says 4 p.m instead of 12 a.m.). I could not reproduce this with the parsing rules that you shared above, but this is however what you you get with parsing rules that only picked up the month and day, like such:

Is it possible at all that the two screenshots do not actually match (e.g. the log view in the second screenshot was taken with a version of the parsing rules that does not capture the time)?
If not, then there is probably a bug in binjr, but as I said I could not reproduce it.

Created this logfile:
Feb 19 00:00:01 thinkpad systemd[1]: Starting system activity accounting tool...
Feb 19 00:00:01 thinkpad audit: BPF prog-id=739 op=LOAD
Feb 19 00:00:01 thinkpad audit: BPF prog-id=740 op=LOAD
Feb 19 00:00:01 thinkpad systemd[1]: Starting update of the root trust anchor for DNSSEC validation in unbound...

Fresh screenshot of freshly-imported log file in a new worksheet:

I'd argue that the syslog format should have a year on it, but it's been sacrificed in the name of backwards-compatibility.
I would also argue that when there isn't a year, we should try to follow syslog's algorithm and assume the timestamp is for some moment in the past 365.26 days, with an option for users to override that.
If they've got a logfile containing multiple years' worth of entries, it's tougher: assume the file ends in the most recent 365.26-day period, and extrapolate backwards, assuming that there's at least one log entry per month and the timestamps are in monotonically increasing order.  The filesystem timestamp of the logfile might be worth considering too: if it's roughly the same as the last log entry in the file (logrotation+compression effect), copy the year from it.
Although at some point, this turns into a data forensics problem.  :-)

BTW, I changed the last line in the logfile to be Feb 19 00:00:03 to see if the problem was caused by all the entries having the same timestamp, but it didn't help, the time range at the top of the worksheet was still 1969-02-08 3:59:59pm to 4:00:00pm.
It's odd that it's grabbing Feb 8th, and not Feb 20th or Jan 1st.
BTW, this is Binjr 3.11.0, downloaded yesterday.

I have created two separate issues to track the problems that surfaced in this one:

#129 - Let users choose the date & time that serves as an anchor to construct timestamps for partial data to track making the default time reference point user-selectable
130 - Typing the name of a TemporalCaptureGroup or selecting it from dropdown list in profile editor is not idempotent to track the bug that was the root cause for some parsing keyword not working (and the source of much confusion)

@PenelopeFudd I'm therefore closing this issue; feel free to reopen it I you feel there's a need.


Added optional additional headers to createPlayer config for FetchStreamLoader

Hello! First of all, thanks for the awesome library!
This PR adds additional optional headers to createPlayer config for use in FetchStreamLoader.
For example, it is needed to specify 'Authorization' Basic Auth header to allow fetch FLV stream from auth protected URL.
Example
var flvPlayer = flvjs.createPlayer({
    isLive: true,
    type: 'flv',
    url: "https:/localhost/flv",
}, {
    enableWorker: false,
    deferLoadAfterSourceOpen:false,
    enableStashBuffer: false,

    // additional authorization header
    headers: {
        'Authorization': 'Basic ' + btoa(unescape(encodeURIComponent("admin:1111")))
    },
});

There is withCredentials property on dataSource but it won't work if you don't want auth popup to appear for the user on a page that contains player.  That's because allowing adding 'Authorization' header manually would be beneficial.
Thank you!

Sorry for my late response.
It's a good idea and thanks for your contribution.
Before merging I have to update the declarations in config.js and flv.d.ts

Now it will also work in other browsers like FireFox, etc.
Merged, thanks!


Fix Accept-Encoding and Accept-Language

satisfiedBy on the values makes little sense and is deprecated
satisfiedBy on the headers did not understand priority
made more consistent with Accept-Charset

LanguageTag and ContentCoding are still broken in that they are both values (in the Content-* headers) and ranges (in the Accept-* headers).  These should be split into different types, but there's no reasonable way to do that without breaking binary compatibility.  We'll address that in a later version.

This passes MiMa for me locally, which concerns me.  I expected to have to add exceptions for new signatures.

Well your concerns were valid, as it doesn't pass MiMa on travis.

I'm still not sure why it doesn't complain about the new methods in core.
Probably related to being final.
I'm going to see if I can do all this without MiMa exceptions.
On Sep 17, 2017 13:47, "Christopher Davenport"<EMAIL_ADDRESS>wrote:

Well your concerns were valid, as it doesn't pass MiMa on travis.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/http4s/http4s/pull/1406#issuecomment-330065319, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAItau_krpQb_gCZPgqum8FOoN6wBUDvks5sjVsvgaJpZM4PaBeD
.

Looks good to me so 👍 if travis is happy.


chore: remove mathround polyfill (used in IE)

See: https://github.com/shaka-project/shaka-player/commit/f145dffc9e7743821d7af2c1635abab9a151ca86 and https://github.com/shaka-project/shaka-player/pull/832

According to the stack overflow thread this was a problem on Opera 12.02, but I just tried it out and it looks like they must have fixed it since then. We don't really fully support Opera, but that's still good to know I guess.


update docs to mention the default labels added to the inventory

After merging https://github.com/rancher/elemental-operator/pull/276 now all inventories will have some extra labels added by the operator regarding the system hardware.
Document them in the docs so users are aware that they exist.

https://github.com/rancher/elemental-docs/pull/22


Add option to authenticate with server account.

This adds the option to authenticate using a server instead of a user account.

Thanks for contributing! 🥇

Thank you for fixing and including it!


Proposals from unknown Peer

Problem: A ChannelProposal currently contains a From Peer field. This works fine as long as we only accept proposals from peers which were previously registered with RegisterPeer.
Now the problem is that the payment echo bot wants to accept channel proposals from addresses which where not registered.
The current logic is to reject these proposals, since returning a Peer which was not created by the user with RegisterPeer does not make sense.
Possible solutions:

Remove Peer and replace with common.Address, similar to #11. We could also remove RegisterPeer in this step.
Add a FromAddress common.Address and rename From Peer to FromPeer *Peer in the channel proposal.
Only one if the two field would be set then, depending on whether or not the peer is known.
other?

Change From Peer to From common.Address?

Change From Peer to From common.Address?

Yes we could also do that. I guess that would be the fastest fix for now.


No dlstreamer folder in my data preprocessing folder

Hello, I dont have dl streamer in my data preprocessing folder. The only folder i have in the data preprocessing folder is the audio folder. I am using openvino==2021.3.0
Also, i cant clone this repo

@MfonobongIme , I'm closing this issue. If it is still actual feel free to reopen.


helm v2.14.0 - does not recognize 'release' & 'heritage' in metadata

Output of helm version:
Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.7", GitCommit:"b30876a5539f09684ff9fde266fda10b37738c9c", GitTreeState:"clean", BuildDate:"2018-01-16T21:59:57Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.8", GitCommit:"a89f8c11a5f4f132503edbc4918c98518fd504e3", GitTreeState:"clean", BuildDate:"2019-04-23T04:41:47Z", GoVersion:"go1.10.8", Compiler:"gc", Platform:"linux/amd64"}
I see an error if i have 'release' or 'heritage' in metadata :-
example : https://github.com/helm/charts/blob/164ee72d34f9f8e7888c0619186983d108019165/incubator/azuremonitor-containers/templates/omsagent-rs-configmap.yaml#L227
Error: validation failed: error validating "": error validating data: [ValidationError(ConfigMap.metadata): unknown field "chart" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta, ValidationError(ConfigMap.metadata): unknown field "heritage" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta, ValidationError(ConfigMap.metadata): unknown field "release" in io.k8s.apimachinery.pkg.apis.meta.v1.ObjectMeta]
Is this deprecated ? I dont see any breaking changes in v2.14.0 release notes.
All works when using v2.13.1

I had to look at this for a moment to figure it out. The problem is with the chart. It looks like there have been validation improvements in a dependency.
In a bunch of places there are things like...
name: omsagentclusterrolebinding
chart: {{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}
release: {{ .Release.Name }}
heritage: {{ .Release.Service }}

That should instead be...
name: omsagentclusterrolebinding
labels:
  chart: {{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}
  release: {{ .Release.Name }}
  heritage: {{ .Release.Service }}

Notice how labels is missing.

Also see https://github.com/helm/helm/issues/5750 for context. We're planning on backing this out for Helm 2 in 2.14.1.
This issue can occur due to two different situations:

the chart being submitted via helm upgrade fails object validation, as @mattfarina pointed out. Reporting validation errors for this is a GOOD thing; it informs the user that they need to fix their chart so that the object being installed conforms to the API.
poorly-formed charts installed using an older version of Helm may fail validation during a helm upgrade. This is because prior to 2.14, no validation occurred and the objects were silently accepted. Once helm upgrade is invoked, Helm fetches the older object metadata to perform a diff and validates the objects. This is a BAD thing, as in this case, helm upgrade will always fail validation, preventing upgrades.

Either situation can trigger this issue. In Helm 3, we're planning to force validation to occur from day one so you cannot install invalid objects into Kubernetes, but due to backwards compatibility issues we'll continue to accept invalid chart metadata for Helm 2.

closing as a duplicate of #5750. Thanks!


feat: good ghosting position using smart contract

Awesome!! Thanks so much @camolezi
And congrats on being the very first outside contributor to Valora hooks 🎉 ❤


fix(TimePicker): Returns empty when backspace is pressed

Issue: #1270
What I did

Calling updateTime('') on handleHourKeyDown and handleMinuteKeyDown
Checklist

[X] changeset has been added
[X] Pull request description is descriptive
[X] I have made corresponding changes to the documentation
[X] New and existing unit tests pass locally with my changes
[X] I have added tests that prove my fix is effective or that my feature works

How to test

Navigate to the TimePicker events story or docs site and confirm that pressing backspace clears the time value visually and on the event.

Within The Storybook example should the onChange event be called twice per clear?


Some fix in FAtomicQuery.

Codecov Report

Merging #89 into master will increase coverage by 0.02%.
The diff coverage is 43.75%.

@@            Coverage Diff             @@
##           master      #89      +/-   ##
==========================================
+ Coverage   28.04%   28.07%   +0.02%
==========================================
  Files          44       44
  Lines        1223     1236      +13
  Branches       44       45       +1
==========================================
+ Hits          343      347       +4
- Misses        880      889       +9

Impacted Files
Coverage Δ

.../main/scala/net/scalax/fsn/core/FAtomicQuery.scala
64.28% <43.75%> (-29.05%)
:arrow_down:

Continue to review full report at Codecov.

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


mepo: 0.4.2 -> 0.5

Description of changes
First commit is a simple version bump.
Second commit adds gpsd as an optional dependency and points mepo's scripts' gpspipe to the correct path.  It also makes silent reporting of the user's location to Mozilla and geoclue opt-in rather than opt-out; this issue has been reported upstream to request a build flag so we don't have to use patches.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Added commits which were formerly part of #189345.

Path to GeoClue binaries need substitution
and IMHO Mozilla location service should be
conditionally enabled in the same manner as the others.
BTW you should rebase the commits for each to be meaningful
(GitHub suggestion should be read-only).

Path to GeoClue binaries need substitution

Done: 3b8d39d136de50cfd3b0e3159cb0b2b318b67565

and IMHO Mozilla location service should be conditionally enabled in the same manner as the others.

I don't understand what you mean... isn't reportLocationToMozilla conditionally enabling the mozilla location service?

BTW you should rebase the commits for each to be meaningful (GitHub suggestion should be read-only).

I don't understand this either... what do you mean by meaningful?  And what GitHub suggestion?

isn't reportLocationToMozilla conditionally enabling the mozilla location service?

It is, apologies, I misread :sweat_smile:

what do you mean by meaningful [commit]?

37ceaf7d4c5c1157b3eb51262d520fc0ec0cdb77 and 3b8d39d136de50cfd3b0e3159cb0b2b318b67565 are examples of commits that only make sense with the context of the discussion.  Each commit should make sense by itself should it be merged.

what GitHub suggestion?

The one created 37ceaf7d4c5c1157b3eb51262d520fc0ec0cdb77.

37ceaf7 and 3b8d39d are examples of commits that only make sense with the context of the discussion. Each commit should make sense by itself should it be merged.

Oh, I see, you want me to squash the history to clean it up.  Sure, no problem.

Each commit should make sense by itself should it be merged.

Right.  Just to be clear though, I don't think it is a good idea to merge the version bump without the user location protection.  I will squash the history into two commits, but I hope that either both of them or else neither of them is merged.

The one created 37ceaf7.

I believe that I cherry-picked that into this PR as 37ceaf7d4c5c1157b3eb51262d520fc0ec0cdb77.

Thanks!  GitHub UX kinda only allows merging all or nothing
(unless a maintainer pushes to your remote which is too spooky IMHO),
hence often quite some nitpick round trips are needed.

Thanks! GitHub UX kinda only allows merging all or nothing

Ah, interesting; I did not know that.  I have plenty of complaints about github :)

hence often quite some nitpick round trips are needed.

No problem.  Should be squashed now into four separate topic-specific commits at 8981daa3a8a8b325c0e331e0b972b0a109b3beb9.  This should make things easier down the line if one of them needs to be reverted.

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

2 packages built:

mepo
mepo-x11

I guess .orig file should not be installed:
$ ls results/mepo/bin/*.orig
results/mepo/bin/mepo_ui_menu_user_pin_updater.sh.orig

I guess .orig file should not be installed:
$ ls results/mepo/bin/*.orig
results/mepo/bin/mepo_ui_menu_user_pin_updater.sh.orig

I'm trying to reproduce this.
We might need --no-backup-if-mismatch in patchFlags.  I'm surprised that isn't the default.

So, based on upstream's response it doesn't look like there is an easy solution, and my concerns will likely recur in future version bumps.
I'll let the package maintainers @sikmir @McSinyx decide what to do here.  Feel free to use some/all/none of the changes in this PR.


Subpasses example segfaults

tl;dr, running the subpasses example will result in a segfault, because the first color attachment passed to the second subpass is VK_ATTACHMENT_UNUSED.
https://github.com/GPUOpen-LibrariesAndSDKs/V-EZ/blob/29d2229e44ee692f74a33b698c80273ebcc67c3e/Samples/Data/Shaders/Subpasses/Subpass0.frag#L13-L15
The first subpass will output to attachments[1:3], but attachments[0] is unused.
https://github.com/GPUOpen-LibrariesAndSDKs/V-EZ/blob/29d2229e44ee692f74a33b698c80273ebcc67c3e/Samples/Data/Shaders/Subpasses/Subpass1.frag#L4-L8
This arrangement of layouts results in a call to ConvertVkRenderPassCreateInfoToV2KHR in the Vulkan SDK, executing the line:
const auto format = out_struct->pAttachments[input_attachment.attachment].format;

which causes a segfault because input_attachment.attachment == VK_ATTACHMENT_UNUSED == ULONGINT_MAX
Changing Subpass0.frag to
layout(location = 0) out vec4 redChannel;
layout(location = 1) out vec4 greenChannel;
layout(location = 2) out vec4 blueChannel;

and Subpass1.frag to
layout(input_attachment_index = 0, set = 0, binding = 0) uniform subpassInput redChannel;
layout(input_attachment_index = 1, set = 0, binding = 1) uniform subpassInput greenChannel;
layout(input_attachment_index = 2, set = 0, binding = 2) uniform subpassInput blueChannel;

layout(location = 3) out vec4 combinedChannels;

will fix the segfault, but result in a black screen. :boom:

Fixed by cleaning and rebuilding, checking out original code.


Changing version in Help section

I was looking at your Dockerfile and attempting to remove all traces of Grafana from there. Do you have any insight into how to remove the label in the image below?

It seems like this is coded into the grafanaBootData variable that is passed into the page on load, as the element doesn't exist in the DOM.

That's correct, it's set in the Go code and hard-coded in the grafana-server. Unfortunately, it's quite hard to replace Grafana in the grafana-server similar to what we did for the Main Org. because it's not unique and used in many places.
		helpVersion := fmt.Sprintf(`%s v%s (%s)`, setting.ApplicationName, setting.BuildVersion, setting.BuildCommit)

const (
	RedactedPassword = "*********"
	DefaultHTTPAddr  = "<IP_ADDRESS>"
	Dev              = "development"
	Prod             = "production"
	Test             = "test"
	ApplicationName  = "Grafana"
)

Let me know if there is anything else.

@jacksongoode I like the idea from the Grafana issue to replace it on the proxy server for files with text/html type. Should be similar for NGINX if you use it.
For those who use apache2 as proxy, you can use following configuration (with a2enmod substitute)

      AddOutputFilterByType SUBSTITUTE text/html
      Substitute "s/Grafana v[0-9]\.[0-9]\.[0-9] \([0-9a-z]*\)/my_replacement_chain/"

@mikhail-vl I just got around it by forcibly updating the window.grafanaBootData assignment like:
RUN sed -i "s|\[\[.NavTree\]\],|nav,|g; \
    s|window.grafanaBootData = {| \
    let nav = [[.NavTree]]; \
    let help = nav.pop(); \
    help['subTitle'] = 'Custom name & version'; \
    nav.push(help); \
    window.grafanaBootData = {|g" \
    /usr/share/grafana/public/views/index.html

@jacksongoode This is what I see when tried it:

@jacksongoode That works, I will skip & for the tutorial :)


Upgrade storybook to v7.0.21

This updates storybook to v7.0.21 using their script npx storybook@latest upgrade and required manual migration.
This is primarily to fix the line numbering issue mentioned in #722
I tested a handful of demos, which worked, and the code copied without line numbers, but it could definitely use more testing.

Upgrade is complete


DELETE on a non-existent archive rule generates a 500/DB exception

Other calls (with the exception of some early calls, see #202 ) return a correctly formatted 404 response, but the v1/archive/rules route generates an exception along with a 500:
# curl -X DELETE -u admin:foobar http://localhost:8228/v1/archives/rules/blah
{
  "detail": {
    "error_codes": []
  },
  "httpcode": 500,
  "message": "(psycopg2.ProgrammingError) column catalog_archive_transition_rules.
...
...
...
...
 'rule_id_1': 'blah'}]\n(Background on this error at: http://sqlalche.me/e/f405)"
}

Tested and closing this as resolved in 0.5.0 release


Update goreleaser config

What is currently missing?
Building of packages
How could this be improved?
Add config
Is this a feature you would work on yourself?
[X] I plan to open a pull request for this feature

Done!


UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 215: ordinal not in range(128)

The sentinel was falling to start properly because I use an invalid character. The faulty one was : 'é' and used in the RPC password in the gobyte.conf file.
Here's the trace log I had access to :
SENTINEL_DEBUG=1 ./venv/bin/python bin/sentinel.py
2019-01-27 06:07:57 [info]: SCHEMA_VERSION (code) = [20170111-1]
2019-01-27 06:07:57 [info]: DB_SCHEMA_VERSION = [20170111-1]
Traceback (most recent call last):
File "bin/sentinel.py", line 265, in
main()
File "bin/sentinel.py", line 164, in main
if not is_gobyted_port_open(gobyted):
File "bin/sentinel.py", line 151, in is_gobyted_port_open
info = gobyted.rpc_command('getgovernanceinfo')
File "lib/gobyted.py", line 42, in rpc_command
return self.rpc_connection.getattr(params[0])(*params[1:])
File "lib/gobyted.py", line 31, in rpc_connection
return AuthServiceProxy("http://{0}:{1}@{2}:{3}".format(*self.creds))
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 215: ordinal not in range(128)

Correct. You shouldn't use special characters in passwords. This is currently a limitation of the sentinel code.

Alright thanks for answer !
I just wanted to point it out.
No big deal about it ;-)


How to update android17.d.ts

In the ios-runtime I can run TNS_TYPESCRIPT_DECLARATIONS_PATH="$(pwd)/typings" tns build ios which is by far the most helpful debugging tool for NativeScript.
The android17.d.ts typings are near perfect with definitions/documentation details to almost every class, but it's outdated.
tldr;
How can I generate an updated typings file to say android24.d.ts with definitions and documentation details?
My endeavour so far,

I built the dts-generator.jar from the https://github.com/NativeScript/android-dts-generator repository
I put the $ANDROID_HOME/platforms/android-24/android.jar in the same directory as the built dts-generator.jar file
I ran java -jar dts-generator.jar -input android24.jar
Yay, now I have the generated out/base.d.ts file with declarations for android SDK 24

But they're completely wrong, no interface declarations, and have typescript errors on every line resulting in sublime text crashing when I scroll 😞

You all possibly couldn't have created the android17.d.ts file by hand, so I'm asking, how did you create the original android17.d.ts with perfect declarations and documentation? And how do I go about doing so? I've spent the past few hours playing around with the android-runtime and the android-metadata-generator trying to figure out how you were able to produce such a clean android17.d.ts but I'm having no luck.
Please fill me in on these wizard secrets!
Having these native declaration files is a requirement in my development environment and it would be incredibly helpful to have an updated SDK version.
Thank you!!! 🍰

This issue was moved to NativeScript/NativeScript#2687

@Plamen5kov @hshristov @jasssonpet
Might anyone be able to shed some light on this?
I see some amazing projects that do this sort of thing:
https://github.com/raphaeljolivet/java2typescript
https://github.com/vojtechhabarta/typescript-generator
https://github.com/RedSeal-co/ts-java
https://github.com/palantir/typescript-service-generator

Sorry @roblav96, I have no info about the Android part of the TypeScript generator but if you come up with any such issues (maybe with newer iOS SDKs) on the iOS part let me know and we'll fix them right away.

@jasssonpet No worries, I'm able to work off what's available so far no problem. It's just that itch for latest and greatest. lol I'll see what I come across and let you know.

@roblav96 I'm glad you're taking an interest in the d.ts generator.
Q: How can I generate an updated typings file to say android24.d.ts with definitions and documentation details?
A: Currently you can't do it by only using the d.ts generator. The android-17.d.ts is created partially by the generator and partially by hand.
I am working on the d.ts generator, but currently it's work in progress. Thank you for the links with similar projects, I took a good look at them, and it's true they do some pretty great work, but they're specified for the platform they're used on, as is our d.ts generator. Having said that, they were useful to me and gave me some ideas as to what can we do to better our d.ts generator.

https://github.com/NativeScript/android-dts-generator/issues/1


Feature: order details calculations from api

Added synchronous methods for calculating order details without API requests, adapted from existing API service methods.
Started writing unit tests for these calculation functions

@n-strekalov


Fix non-portable embedding of directive within macro arguments

Fixes warning (GCC): embedding a directive within macro arguments is not portable
According to the C/C++ standard the behavior of the existing code is undefined:

If there are sequences of preprocessing tokens within the list of arguments that would otherwise
act as preprocessing directives, the behavior is undefined.

See the "Macro replacement" section of the C++ language standard.
Not a whole lot of thought went into naming the get_string_from_js_result function so feel free to suggest another name.

The following warning is no longer present in the CI build log:
webview.h:473:1: warning: embedding a directive within macro arguments is not portable
  473 | #if WEBKIT_MAJOR_VERSION >= 2 && WEBKIT_MINOR_VERSION >= 22
      | ^
webview.h:477:1: warning: embedding a directive within macro arguments is not portable
  477 | #else
      | ^
webview.h:486:1: warning: embedding a directive within macro arguments is not portable
  486 | #endif
      | ^


Reverting value getter for the hook

Reverting the 0.7 version change that breaks the lifecycle guarantees. useSyncExternalStore has a bit of an odd mechanic, it calls stuff multiple times, and always starts with the provided .get(). Hence, first time we get a render we won't have any value in store.value, and that's mission critical for all stores that utilize lifecycles (onStart, onMount) for setting initial values.
Added a very simple test case for using a computed store (previous implementation failed it).

Released in 0.7.1, but what do you think about useCallback(() => store.get(), [store])?

But my understanding is that .bind is good enough. I didn't see one problem with it before. Maybe, we'll be able to move to arrow function later in the core:
    // instead of get() {
    get: () => {
      if (!store.lc) {
        store.listen(() => {})()
      }
      return store.value
    },


@DependencyEndpoint & Never returning closure

Description
When applying @DependencyEndpoint to a function which return a non-optional type one must provide a closure. While this moved some runtime checks to compile time checks it's not always possible to provide a sensible value or even a value at all.
One can avoid providing a value using fatalError() but the macro then emits invalid swift code.
Checklist

[X] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
The macro should emit valid swift code even when using fatalError() but I think there should be an option to specify the behaviour of the macro so one can skip writing the fatalError entirely
Actual behavior
No response
Steps to reproduce
@DependencyEndpoint
public var fetchCategoryIds: () async throws -> Set<Article.Category.ID> = { fatalError() }
  private var _fetchCategoryIds: () async throws -> Set<Article.Category.ID> = {
      XCTestDynamicOverlay.XCTFail("Unimplemented: 'fetchCategoryIds'")
      return fatalError()
  }
{
    @storageRestrictions(initializes: _fetchCategoryIds)
    init(initialValue) {
        _fetchCategoryIds = initialValue
    }
    get {
        _fetchCategoryIds
    }
    set {
        _fetchCategoryIds = newValue
    }
}

Dependencies version information
1.1.1
Destination operating system
No response
Xcode version information
No response
Swift Compiler version information
No response

Yeah I picked a bad example, I was working on a use case where I can't provide a default and picked something else close. Also while understandable I think it's surprising that optional are special cased in the same way as void.

My main concern here is departing some the interface vs implementation, I'm all in for the closure style but it's strange to provide default that should not be used. Maybe those shouldn't have the @DependencyEndpoint applied when using @DependencyClient and should be added to the init ?

Yeah I picked a bad example, I was working on a use case where I can't provide a default and picked something else close. Also while understandable I think it's surprising that optional are special cased in the same way as void.

We could reconsider, but since Swift heavily special cases Void and Optional in the language we made exceptions for these types. Any example of why it would be better to not special-case optional?

My main concern here is departing from the interface / implementation idiom, I'm all in for the closure style but it's strange to provide default that should not be used. Maybe those shouldn't have the @DependencyEndpoint applied when using @DependencyClient and should be added to the generated init instead and required then ?

The default is used in tests, though, which is the primary reason to use @DependencyClient in the first place. A fatalError will crash your entire test suite on failure instead of more gracefully emitting a test failure and continuing.

I guess It feel strange that I must provide some defaults to some methods but not for others, for void methods conceptually we are replacing the whole method so it make sens but choosing nil as default is kinda going a bit to far ? As said, it is a very reasonable choice as this would be the default most people use but then why not special case bool ?
I get that the whole point of this is tests but I'm more confortable having at least a tiny separation between interface code that should be used in test and production and test specific code. It's not about the technicalities but more about being able to make the interface as readable as possible. I think having to provide a testValue was a neat middle ground where test shenanigans were grouped without wrinkling code inside the interface.
On a side note, using the labels is awesome !

Is this not where we would use unimplemented directly? I've found that () -> AsyncStream<Value> can be defaulted to { unimplemented() } for tests. Could the macro do that here?

I didn't tried as using it outside of the closure was raising a warning but that would be great IMHO

I guess It feel strange that I must provide some defaults to some methods but not for others, for void methods conceptually we are replacing the whole method so it make sens but choosing nil as default is kinda going a bit to far ? As said, it is a very reasonable choice as this would be the default most people use but then why not special case bool ?

There is only one correct value for Void, and Swift even doesn't force you to put -> Void on func, so we can retain the explicit behavior there.
Optionals are more arguable. We special case because nil is a default, implicit assignment for var foo: Int?, though this is admittedly different than a function return value. Still, for any optional type we don't know about, nil is the one value we can pluck out of thin air.
The reason we don't special case Bool is because we had to draw the line somewhere, and right now we've drawn it pretty shortly. Bool is different than Optional, though, because now there are two values we know about and the library would have to choose. An "empty"-seeming value of false might seem appropriate, but true is just as fine a default and even preferable in some situations (depending on && vs. ||). At the end of the day, though, we're just trying to be ergonomic in omitting these defaults, so maybe Bool.random() would be fine for a default failure.
And if we special case Bool maybe we'd also include numbers and collections...
And then maybe we'd special case DefaultInitializable values with a protocol...
All of these are options, but they introduce more questions and require more opinions.

I get that the whole point of this is tests but I'm more confortable having at least a tiny separation between interface code that should be used in test and production and test specific code. It's not about the technicalities but more about being able to make the interface as readable as possible. I think having to provide a testValue was a neat middle ground where test shenanigans were grouped without wrinkling code inside the interface.

The Dependencies library in general straddles the line by declaring that testability is a requirement of the interface. TestDependencyKey conformances are required in the module that declares the dependency and cannot be separated out into just the tests, for example.
In the case of these dependency endpoints, the default test value is similarly required at compile time to ensure tests don't crash at runtime.

That's why I'm wondering about an option for the @DependencyClient macro to require those in init instead of inline.

I'm not quite sure what you mean by this. Can you sketch an example?

Is this not where we would use unimplemented directly? I've found that () -> AsyncStream<Value> can be defaulted to { unimplemented() } for tests. Could the macro do that here?

@jshier We consider @DependencyClient/@DependencyEndpoint to be a replacement for unimplemented that learned a few lessons along the way. In particular, we believe that the fatalErrors it emitted were a mistake that led to crashing test suites. We consider @DependencyClient's default value diagnostic to be a feature that can help ensure your test suite runs without crashing at compile time.
If anything, even if we do special-case fatalError to allow it in a default, I'd consider adding a warning along the lines of:

Warning
A default 'fatalError' will crash your test suite if accessed without being overridden. Consider using a default value instead.

@jshier @DependencyClient adds the exact same test failures but gives them a better name automatically. Also, the default value is only required if the endpoint is non-throwing, so aside from unimplemented calling fatalError in these cases only, @DependencyClient should be the same behavior, but with fewer runtime issues.

I guess I'm confused. What do you expect users to do for these defaults? Because you're right, there are no sensible default values for () -> Int or () -> AsyncStream<Int>, or most other value-returning closures. That's why they were left to be initialized in the first place, so we have to fill them in for the particular environments, where there are meaningful values or test failures. And if the macro is already generating XCTFail anyway, when would the return value be used anyway?

@jshier Don't think about these defaults as "sensible." They are simply there to fulfill the requirement that an unimplemented test should not crash. So you could specify any value, really. The value doesn't matter, as XCTFail is called unconditionally before returning it.
You can decide what value makes the most sense for an "unimplemented" dependency endpoint. For authorization status you could return .notDetermined or even .denied. For a () -> Float that is returning the volume you could return 1.0. For an AsyncStream<Int> you could return a stream that completes immediately, etc.


fix(gitreceive): specify manifests as Go templates on disk

Fixes #79

currently breaks git pushes. example output:
ENG000656:example-go aaronschlesinger$ git commit -m "asd" --allow-empty && git push deis master
[master a90f0ea] asd
Counting objects: 1, done.
Writing objects: 100% (1/1), 182 bytes | 0 bytes/s, done.
Total 1 (delta 0), reused 0 (delta 0)
Running in debug mode
Running git hook
read [832fbe4502a4eb437f1fb0dcd63bcf1a3270faf2,a90f0ea8d192db31ad2cde7c57c753188c32e8b3,refs/heads/master]
Workflow request /v2/hooks/push (body elided)
To ssh://git@deis.<IP_ADDRESS>.xip.io:2222/gotest.git
   832fbe4..a90f0ea  master -> master

Closed by #133


Ignore void types in overridden function signatures.

Closes #1569

Minor nitpick, but it would be good to group the tests where ignoreOverridden is true, and group the rest where it's false. You can use Spek's context for that purpose.


Feature request: easier to read source

Reading the source when...
module.exports = _curry2(function lens(getter, setter) {
  return function(f) {
    return function(s) {
      return map(function(v) { return setter(v, s); }, f(getter(s)));
    };
  };
});

f? s? v? s is... I think the property name? Or wait, maybe v is the propname and s is . . . well f if "function", that's clear, but what is the function's purpose here?
Meaningful variable names
Benefit

Easier to read source
Makes Ramda a better teaching tool
Makes it easier for newbs to understand & contribute

Cost

???

Are you looking for names for those three properties in this function, or do you think it's an issue endemic to Ramda in general?
Ramda does try to keep reasonably readable source-code.  I picked another function at random.  anyPass is defined like this:
module.exports = _curry1(function anyPass(preds) {
  return curryN(reduce(max, 0, pluck('length', preds)), function() {
    var idx = 0;
    var len = preds.length;
    while (idx < len) {
      if (preds[idx].apply(this, arguments)) {
        return true;
      }
      idx += 1;
    }
    return false;
  });
});

Here we do abbreviate a number of variables, 'idx' for 'index', 'len' for 'length', and 'preds' for 'predicates', but to me its quite readable.  I believe the vast majority of our source code is of this type.
Lenses are a particularly abstract data structure.  Perhaps we could replace 'f', 's', and 'v' -- if my tenuous grasp of lenses is correct (pinging @davidchambers or @scott-christopher!)  -- with 'fn', 'structure', and 'value'.  Note that 'fn' is what we generally use for arbitrary functions.  But 'structure' and 'value' are not really meaningful names; they're as bad as calling a variable 'data' or 'info'.  I think making a change like that just generates a false sense of understanding: "Oh so this is the structure, and that is the value, I get it!"  But I can certainly be convinced otherwise.
Do you have other suggested names for these?  Or any way to write the code that's more clear?

... and I forgot to say that "property name" is not the correct abstraction.  Lenses are applicable to all sorts of data structures, not simply Objects.

... and still further, there is clearly a need to describe what a lens is, and how it works.  Several issues recently have touched on this need, and I hope we can address this soon.  But Lens is one of the oddest functions in the library.  It doesn't return a value that the user is likely to use directly, only one that can be fed into functions like view, set, and over.  This is not something Ramda generally does.

Some other options for the argument names in lens, if it is specifically regarding that particular function.

f: toFunctorFn
s: target
v: focus

We could also document how the lens machinery works inside the implementation of the function, though I'd probably suggest leaving it out of the API docs for the sake of brevity.

I like those names, Scott!

Should we refactor with those names?
(And my grasp was clearly more tenuous than I thought.  I have the abstraction right, I believe, but little understanding of the implementation!)

I've raised #1588 to address the specific concerns raised about the various lens functions.

@Sequoia, are there other functions you'd like to see changed, or were the lens functions the only offenders?

@davidchambers I opened this issue because I was having trouble when investigating this particular function (via lensProp). There are probably other places in the source that could be improved with such changes, but I have not done a thorough review. If I encounter other issues I'll be sure to raise them!
The only other thing I can think of off-hand is the assoc function. Why is the name so short? Does it stand for... "associative?"

I think ultimately, a blog post or "guide" might be a better solution for "lenses." They are a specific concept that goes beyond the more general FP style Ramda enables. Maybe a code walk-thru. Is there such a guide?

Is there such a guide?

Not a Ramda-specific one, but @DrBoolean's Lenses Quick n’ Dirty is terrific! Ramda's implementation is very similar to the one Brian presents in the video, which is no coincidence: I watched the video several times before updating Ramda's lens functions.

Ha! Funny story - I woke up today and decided to start contributing to ramda's lens effort :)
I'd love to add maps, traverses, iso, and folds if that's not too much...

I'd love to add maps, traverses, iso, and folds if that's not too much...

Yes, please!

@Sequoia: There's also a good blog post about lenses with Ramda and Virtual-Dom recently written by @joneshf too: http://joneshf.github.io/programming/2015/12/19/Lenses-and-Virtual-DOM-Support-Open-Closed.html

@DrBoolean: I'd love to add maps, traverses, iso, and folds if that's not too much...

I'd really like to see these too, though I suspect they may be better suited in their own package (arguably along with the existing lens functions in Ramda). I floated the idea of a separate ramda-lens library a while ago – perhaps it might be the time to pursue it now? I also have some prism prototypes which could potentially end up there too: https://github.com/scott-christopher/ramda/commit/ff755e192dfa3124f28650c503b40c98391ff0f7

@scott-christopher That's super cool. I'd love to play with those prisms. I'm most interested in adding iso to work with a few immutable js lenses I've been using:
var lensImmutable = function lensImmutable(k) {
  return lens(function(o){ return o.get(k) },
              function(v, o) { return o.set(k, v) })
}

+1 for ramda-lens, but that means over, set, view should be moved over with it.
I would say we should keep minimal lens stuff here and build upon it in an extension lib, but I feel the use case is almost too weak without supplying mapped at least.

ramda-lens would be great. It think it would be easier to users new to lenses to get start, with all the functionality and documentation in one place.

Just started https://github.com/DrBoolean/ramda-lens
I can make it an organization, we can roll it into ramda, or leave be. Whatever works.
I had to overwrite view/over because Identity Const needed to be extended

Just started https://github.com/DrBoolean/ramda-lens

Nice. I'll have a look this evening.

I had to overwrite view/over because Identity Const needed to be extended

While playing around with prisms I ended up pulling these types out into their own file too for much of the same reason.

This is great.  If you wouldn't mind, I would love to host it as part of the Ramda organization, a related-to-Ramda project, but maintained separately the same way Ramda-Fantasy is.  But wherever it ends up, I like seeing this stuff grow.

@scott-christopher totally! I'd love to combine with your prism work and I tried to keep consistent with your identity/const files.
@CrossEye heck yeah! Let's move it over. I actually would love to integrate with ramda-fantasy in a lot of the coming features.

Yaay!! :palm_tree: I think this is a great outcome for the library, as it will make it less befuddling for newcomers & allow lenses to get the attention they deserve as a distinct concept/tool. :+1:

I added a new team to the Ramda organization, and invited you, @DrBoolean.  I think you have to intiate the transfer.    Whatever you think is easier.

@CrossEye thanks for the invite! I don't do this often so I may be wrong, but it's complaining that I don't have admin rights.

Tried to transfer first, but got the same message

Thanks! All transferred up

@DrBoolean:
Just updated your membership status.  I don't know much about this stuff either.  I think you're now a full owner of all Ramda projects.  We hadn't discussed that with the full group, but @buzzdecafe had already wanted to do that.  If that doesn't make it possible, let me know and I'll ask around for someone with actual expertise.

Great!  I look forward to seeing this happen!


LPT NL PT

This PR implements LPT in the nl_pt modules. This mostly follows the implementation for EPT, but I have included a bunch of additional terms for b_nabla2, and also the template function is a bit different due to the presence of the 1 and delta_L terms. I can change that though if we want full consistency.

FYI, I removed the heft_aemulus import, since I think it was a leftover and I wanted to see if tests pass. Bring it back if it was intentional!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

187 of 205 (91.22%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 97.35%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyccl/nl_pt/lpt.py
186
204
91.18%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
5511

Relevant Lines:
5661

💛  - Coveralls


Collect feedback on how to make writing integration tests easier.

Cleaning u old issues, reopen if this is still active.


ConPTY is not fully working in CI

Re-running a previously passing job shows that ConPTY started timing out on certain tests.  We skipped those tests with XFAIL in #213

This roots out on https://github.com/andfoy/winpty-rs/issues/23

First note: New CI images use Windows Server 2022, whereas previously they used 2019

Yes, indeed, now tests are passing: https://github.com/andfoy/winpty-rs/pull/24. I'll produce a winpty-rs release and make some changes here

Nice detective work!  Once there is a new pywinpty release I'll try removing the explicit backend in terminado.


public: PR from same repo

Docs Build status updates of commit a8fe3f8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

ppe-test-188511/index.md
:warning:Warning

Details

ppe-test-188511/index.md

Line 1: [Warning] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 1: [Warning] Missing required attribute: 'title'. Add a title string to show in search engine results.

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


pull request for e2e test at 01/08/2017 09:56:12

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


Add verifiers for secret.generic and yield

Note one of the verifiers is implemented via a new trait HasParent<"GenericOp">

Oops, looks like my verifiers found some bad test setup in some other secret tests. Will patch this tomorrow morning

Fixed the issues, should be good now


Issue displaying correctly behind nginx proxy manager custom locations

I'm using this great project to display openwrt images i have downloaded for my routers.
Version 1.0.3 is working correctly.
My docker compose:
#source: https://github.com/patrickdappollonio/http-server
version: '2'

services:
  http-server:
    image: ghcr.io/patrickdappollonio/docker-http-server:v1.0.3
    ports:
      - 8005:5000
    volumes:
      - /mnt/dane/container/openwrt:/html
    restart: always
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

How it looks on version 1.0.3:

After changing to newest version image: ghcr.io/patrickdappollonio/docker-http-server:latest it is not working anymore when used with ngix proxy manager as a custom location:

It looks like that:

It works correctly when opening locally http://<IP_ADDRESS>:8005/

logs don't show anything strange:
2022/11/26 17:17:04 SETUP:
2022/11/26 17:17:04  > Configured to use port: 5000
2022/11/26 17:17:04  > Serving path: ./
2022/11/26 17:17:04 Starting server...
2022/11/26 17:17:10 GET "/openwrt/" -- HTTP/1.1 200 OK (served in 587.454µs; 28 bytes)

Hello!
It seems you're running the container from a subpath, like example.com/openwrt. Try setting --pathprefix to --pathprefix=/openwrt/
Let me know how it works!

Thanks for quick reply, i'm a beginner with docker compose and i don't know how to pass --pathprefix in compose file (YAML).

No worries, that's what these questions are here for!
This should work:
version: '2'

services:
  http-server:
    image: ghcr.io/patrickdappollonio/docker-http-server:latest
    command: |
        http-server --pathprefix="/openwrt/" --path="/html"
    ports:
      - 8005:5000
    volumes:
      - /mnt/dane/container/openwrt:/html
    restart: always
    labels:
      - "com.centurylinklabs.watchtower.enable=true"

I set two things for these:

The path prefix (since you're serving the container under example.com/openwrt/
The path set to /html since that's where you're mounting these files

You shouldn't need this because I am setting the container's directory to /html too but it's better IMHO to be declarative

Let me know how/if this works!

Thanks, still not working.
Logs when accessing it locally (green) and via example.com/openwrt/ (red)

Would you mind sharing the hostname you use to connect to it as you pass it in the browser?
I suspect your nginx proxy manager might be sending to http-server the original host as the host. The urls in the log seem correct now.

Sure https://sloniupl.eu/openwrt/

Let me try a few things, set up proxy manager and see what the issue might be. I'll circle back to you asap!

Hey @sloniupl, happy holidays!
I took a look at this (and apologizes for the delay). I spun up a server with Nginx Proxy Manager, added a new "Proxy Hosts":

Note here that nip.io is a convenience endpoint to generate hosts that self-resolve. In this case, if I type app.<IP_ADDRESS>.nip.io it will resolve to my local machine to ports 80/443 which is where Nginx Proxy Manager is running.
Then I added the configuration tab you had. Note one tiny note here:

The message right below says that if you want to "pass" a sub-folder forwarding, you need to add it here.
My docker-compose looks like this:
version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

  http-server:
    image: ghcr.io/patrickdappollonio/docker-http-server:latest
    command: |
      http-server --pathprefix="/openwrt/"
    ports:
      - 5000:5000
    volumes:
      - ./:/html
    restart: always

Note the following:

I am running http-server in the same compose. In practice this doesn't matter as long as you don't create a custom network between the services, then they won't be able to "discover" each other.
Since I defined an app called http-server, I know any other Docker container can access this container using this hostname, so http://http-server:5000 here will resolve from the Nginx Proxy Manager automatically to the local container running http-server

That's why in my 2nd configuration tab I did not put an IP address like you did (you put <IP_ADDRESS>, I made Docker resolve itself). In practice, this doesn't matter though and I was able to achieve the same outcome using my loopback address.
The outcome? Both the content and the page load correctly:

Now granted, your setup might be different than mine, and for example, you might have cases where you must specify a network in your docker-compose file. If that's the case, I'm afraid that kind of setup is far out from being support from http-server but more a question for the Nginx Proxy Manager folks.
The trick here for me was to set the "Forward Hostname / IP" to include the path prefix we selected.
The reason why this worked in the past was because the assets are loaded from 3rd parties (the open internet) while in the latest version they all load locally. While old versions work, making links between resources would've not worked (granted though, that feature wasn't there before so no harm done).
Hope this helps, apologies again for the long wait! Keep us posted.

Thanks a lot for following up with this issue and sorry for the late reply (was away for Christmas and new year).
I was unable to configure it like in your example as my nginx proxy manager container is in separate stack and this is probably the issue.
I just created a subdomain for your http-server container and it works great :)
Thanks again for making this and have a happy new year :)

No problem! Sorry you couldn't get the outcome you wanted, but glad it's working as intended!
(And total side note and recommendation: if you put a markdown file called readme.md in the folder you're serving with http-server, you can add content to the directory listing page, here's an example!)


Define Lint Rules

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[x] Other... Please describe: linting

Current behavior
Running linters gives a lot of errors/warnings
Expected behavior
No linting errors
Minimal reproduction of the problem with instructions

Run nx run-many --target=lint --all

What is the motivation / use case for changing the behavior?
Enforcing linting rules makes for a healthy code base.
Perhaps a linter config discussion is in order :)
Progress
Libs

[ ] Phase 1: Apply a loose-ish set of rules on the code base
[ ] Phase 2: Apply a strick set of rules on the code base

[ ] enable disabled rules in akita tests

[ ] Phase 3: Turn on TSC --strict

Apps

[ ] Phase 1: Apply a loose-ish set of rules on the code base
[ ] Phase 2: Apply a strick set of rules on the code base
[ ] Phase 3: Turn on angulars strictTemplates and strictInjectionParameters

I'll be trying to go for this config
"extends": [
    "airbnb-typescript/base",
    "plugin:@typescript-eslint/eslint-recommended",
    "plugin:@typescript-eslint/recommended",
    "prettier",
    "prettier/@typescript-eslint",
    "plugin:prettier/recommended"
  ],

I might loosen it a bit as Akita alone have ✖ 978 problems 😨

I want to adjust the prettier printWidth so a line doesn't exceed the width of the PR review page width. Currently it's giving horizontal scrollbars 😢
Would also be nice to be able to fit files side by side in the editor.

No

Any news here?

No sorry. I'm still planning on doing it

Closing this for now.


fix: #featured-bg-{{id}} not resizing Unsplash images

Problem:
Unsplash images are not resizing properly because the CSS property background-image being added to #featured-bg-{{id}} is HTML-encoded.
You can try this yourself by adding an Unsplash image in the Unsplash button beside the Add feature image

Then look at your request in the browser using liebling theme to see the HTML-encoded query, then use the Casper theme to see the proper query.
The HTML-encoded query string added to Unsplash URLs shows up as:

crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3wxMTc3M3wwfDF8c2VhcmNofDEwfHxhJTIwbWFuJTIwcmlkaW5nJTIwYSUyMGJpa2UlMjBkb3duJTIwYSUyMHN0cmVldCUyMG5leHQlMjB0byUyMHRhbGwlMjBidWlsZGluZ3xlbnwwfHx8fDE3MjczOTU5MDJ8MA&ixlib=rb-4.0.3&q=80&w=600

Solution:
Add a triple bracket handlebar to properly parse the text instead:

crop=entropy&cs=tinysrgb&fit=max&fm=webp&ixid=M3wxMTc3M3wwfDF8c2VhcmNofDEwfHxhJTIwbWFuJTIwcmlkaW5nJTIwYSUyMGJpa2UlMjBkb3duJTIwYSUyMHN0cmVldCUyMG5leHQlMjB0byUyMHRhbGwlMjBidWlsZGluZ3xlbnwwfHx8fDE3MjczOTU5MDJ8MA&ixlib=rb-4.0.3&q=80&w=320

Result:
10.4MB Request size

versus
956KB Request size

This might save homepage first load dozens of MBs of data and shaves much time when the blog uses Unsplash.

Good catch, thank you!

Thanks for the beautiful theme btw! 🙌


Add configurable token lifetime (like JWT has)

It should be a config option for token lifetime (eg. in minutes) and auth guard should automatically reject requests with expired tokens with appropriate status code (401)

@rcerljenko i think there's already an expiration config here that you can set it in minutes

@Te7a-Houdini cool! missed that because i've installed earlier version that didn't have that
i'm just gonna close that issue now  :)

@rennokki @Te7a-Houdini This package isn't JWT compatible right? It may be useful to have additional methods like refresh() as this is used by JWT, but I don't know if this is the actual indention of this package? :)


QT Error when building thrift dependency

Building for Ubuntu 16.04, I got the same error mentioned here:
src/thrift/qt/moc_TQTcpServer.cpp:14:2: error: #error "This file was generated using the moc from 4.8.1. It"
src/thrift/qt/moc_TQTcpServer.cpp:15:2: error: #error "cannot be used with the include files from this version of Qt."
src/thrift/qt/moc_TQTcpServer.cpp:16:2: error: #error "(The moc has changed too much.)"

Looks like there was a conflict between different versions of QT. I was able to get a work around by adding --with-qt5=no to the thrift build step in mapd-deps-ubuntu.sh:
diff --git a/scripts/mapd-deps-ubuntu.sh b/scripts/mapd-deps-ubuntu.sh
index 5393db7..1cb4052 100755
--- a/scripts/mapd-deps-ubuntu.sh
+++ b/scripts/mapd-deps-ubuntu.sh
@@ -70,6 +70,7 @@ JAVA_PREFIX=$PREFIX/lib ./configure \
     --with-python=no \
     --with-php=no \
     --with-ruby=no \
+    --with-qt5=no \
     --prefix=$PREFIX
 make -j $(nproc)
 make install

Closing this issue. If this is still a problem with one of our current 4.x releases, please open a new issue or start a conversation at https://community.mapd.com/


Maintainer Inactive

Hey guys and @mtl,
there are a lot of sensible and good PRs ready to be merged.
This project is interesting and useful for KiCad.
Is there a plan for future development or is this project abandoned?
If so, is anybody interested in continuing work on it?
Best

Hi @herostrat!
I'm absolutely interested in the continued development and fixing of this useful tool. I've forked it here and incorporated the pull requests from this repo: https://github.com/terje/svg2mod
I don't mind where it lives, so if anyone has a special interest in hosting this under their name I'm game. cc @markrages, @zirafa, @marcan, @n1zzo, @matthijskooijman, @NaH012.
For starters, we could transfer the relevant open issues and get to work. :)
All this assuming @mtl is not interested in managing this project.

Hey @terje I would be interested in having this on my @Sodium-Hydrogen account. I initially made my changes under my alt account @NaH012, but have since moved everything to this account.
Repo: https://github.com/Sodium-Hydrogen/svg2mod/

I'm not interested in maintaining this (or rather, I won't have time to maintain this). Great that you are looking into this, though :-)

If no one else has a problem with me taking over maintenance of this project I will go a head with informing all open issues of this and posting on the wiki page for this repo.

I just have one suggestion: Maybe it would be interesting to create an organization for this repo, or maybe see if it can be put under the KiCad organization? Having an organization makes it easier to distribute or transfer maintainership in the future, and also makes the repo look a bit more official? Just an idea though, just putting it under a personal account is probably more pragmatic.

I do like your idea for using an organization. I just created the svg2mod org. If you or anyone else who has been reading this thread would like to join to make sure this project doesn't die again send me a message.
I decided to not try getting it added to the kicad organization because some of the more recent nightly builds have a very limited version integrated so I don't see the interest being very high.

It'd be great to hear from @mtl first, but an org sounds like a decent idea and would help consolidate the various forks/patches. I'd be interested in helping maintain the project as much as I can

@Sodium-Hydrogen Any special reason for not having an issue tracker active on your new svg2mod repo?

No I thought it was active when I set it up. It should be good to go now. Thanks


Add missing READ_EXTERNAL_STORAGE permission for Player

Change-Id: Icebd59c7b7a7e112f42514a3531cb78ef1537c01

Note that while this technically affects behavior in the companion, I'm submitting it against master because it primarily affects compiled apps since they lack the READ_EXTERNAL_STORAGE permission when using a Player. We request READ_EXTERNAL_STORAGE permission up front in the companion, so the Player will always have this permission at the time it is used in live testing mode.


Create custom command names for custom links.

Hi @DavidBorisK, thanks for the suggestion. I think this could actually be done in the bukkit.yml file by setting an alias to the /link command, but I presume you are meaning to have an unlimited number of custom links. I'm not honestly not quite sure how to do something like this yet, so I cannot guarantee a definite date for when this might be ready. In the meanwhile, were there any commands that you would definitely find useful that I could add in?

Well, you could add something like link, like /link2 /link3 /link4. Then
having something in the config to replace those name, similar to how
bukkit.yml does it. It's nothing major, so we don't really need anything in
the meanwhile.
On Tue, Apr 14, 2015 at 5:32 AM, Justin W. Flory<EMAIL_ADDRESS>wrote:

Hi @DavidBorisK https://github.com/DavidBorisK, thanks for the
suggestion. I think this could actually be done in the bukkit.yml file by
setting an alias to the /link command, but I presume you are meaning to
have an unlimited number of custom links. I'm not honestly not quite sure
how to do something like this yet, so I cannot guarantee a definite date
for when this might be ready. In the meanwhile, were there any commands
that you would definitely find useful that I could add in?
—
Reply to this email directly or view it on GitHub
https://github.com/jflory7/PlayerLink/issues/5#issuecomment-92760064.


Training DetectNet with GTX1070+ubuntu 14.04+Intel i7+8G Mem

My machine is Intel i7(3.2GHz) + GTX1070(8GB Mem) + Ubuntu14.04 + 8G System Memory+Cuda8.0+CuDnn V5+ pre-trained berkley model
I want to run the demo of object detect. I train the DetectNet according to the parameter of tutorial.
But it says it will take almost 20 hours.  The lr is set to 0.0001.  After training 8 hours, the process is 43%.
when it trained epoch 12, the accuracy is still 0.2.  But in the tutorial, when on epoch 5, the accuracy rise to 80%. The total process of tutorial is 7 Hours.
It that normal?  something wrong? Generally, How long should the object detect trainning should take ?
I want to post my desktop's snapshot, but git issues seems do not support uploading pictures.

I post my picture of desktop snapshot on google groups:
https://groups.google.com/d/msg/digits-users/iAukkGudG68/VDzOa0M5BQAJ
I know there are someone else also come across this problem. Can anyone give  advice?

I think that sounds about right due to the size of the images in the KITTI dataset. For me it took almost 24 hours to run the example using the GTX1080. But then I used my own dataset with images (400x600), 4000 for training and 1500 for validation, single class object detection. This took almost 2 hours.
Hope this helps.

Generally, How long should the object detect trainning should take ?

tl;dr: It's going to take a while. You're probably not doing anything wrong.
Depending on several factors, I've seen DetectNet trainings on my machine go as fast as 2.5 hours and as slow as 4 days. Several of those trainings never converged to any useful result. As @lasandcris pointed out, some of the relevant factors are the size and number of images you're using. Here are all the things I can think of that you could do to speedup training:
Data

Use smaller images
Use fewer images

Network

Use a larger stride for the grid

Solver

Train for fewer epochs

Software

Use the latest version of NVcaffe (currently 0.15.13)
Use the latest version of cuDNN (currently 5.1.5-1+cuda8.0 or 5.1.3-1+cuda7.5)

Hardware

Use multiple GPUs
Get a newer, faster GPU (Pascal > Maxwell > Kepler)
Get a GPU with more memory so you can use a bigger batch size and/or use faster convolutional kernels from cuDNN
Put your data on a RAID for faster IO
Get a CPU that's faster and/or has more cores

Of course, some of those suggestions are counter-productive if you're also having trouble getting the network to train. Hopefully most of this is obvious - these are mostly just generic suggestions for machine learning.


Advanced middleware configuration

So middleware requires access to a connect application which is impossible now. this patch allows it.

If you update this PR I will merge it. Looks :+1:  to me.

I am including this in #160. I will close this PR if that is accepted.

Version 3.0.0 created that should enable this like shown above:
https://github.com/AveVlad/gulp-connect/releases/tag/v3.0.0
I did a major version increment in case there were any breaking changes. Let me know if you have any issues!


Aspire, Visual Studio 2022 and Firefox Tabs - Closing a new Firefox Window can close your debugging session and vice versa

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
For ASP.Net Core apps a new browser window is started if "launchBrowser: true" is set in launchsettings.json.
However, for Aspire this is different: With Firefox, instead of opening a new window, a new tab is
opened in an already active Firefox browser (if present).
This behavior seems to confuse the tooling as it doesn't know which process to monitor to determine when to end the debugging session. The tooling waits for a new Firefox process to watch, leading to the following issues:
a) The debugging session does not close when the existing Firefox process exits.
b) The debugging session closes when the next Firefox process exists which was spawned after starting the Aspire App.
c) The next Firefox process spawned after starting the Aspire App is closed if the debugging session is stopped, which may result in data loss.
See attached video
https://github.com/user-attachments/assets/5d16095c-0e2b-4fa6-b049-4768891c9b7b
Expected Behavior
A new Firefox window should be opened, and the correct process should be monitored to ensure proper debugging session management.
Steps To Reproduce

Set "launchBrowser" to true in launchsettings.json.
Open a Firefox browser.
Start debugging the Aspire App with Firefox as the default browser.
Notice that a new tab is opened instead of a new window.
Observe the described issues when the debugging session is stopped.

Exceptions (if any)
No response
.NET Version info
.NET SDK:
Version:           8.0.400-preview.0.24324.5
Commit:            736a2616db
Workload version:  8.0.400-manifests.88eef10b
MSBuild version:   17.11.0+1192b22fd
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.19045
OS Platform: Windows
RID:         win-x64
Base Path:   C:\Program Files\dotnet\sdk\8.0.400-preview.0.24324.5\
.NET workloads installed:
Configured to use loose manifests when installing new manifests.
[wasm-tools]
Installation Source: VS 17.10.35027.167
Manifest Version:    8.0.7/8.0.100
Manifest Path:       C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.workload.mono.toolchain.current\8.0.7\WorkloadManifest.json
Install Type:        FileBased
[wasm-tools-net6]
Installation Source: VS 17.10.35027.167
Manifest Version:    8.0.7/8.0.100
Manifest Path:       C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.workload.mono.toolchain.net6\8.0.7\WorkloadManifest.json
Install Type:        FileBased
[aspire]
Installation Source: VS 17.11.35103.136
Manifest Version:    8.0.0/8.0.100
Manifest Path:       C:\Program Files\dotnet\sdk-manifests\8.0.100\microsoft.net.sdk.aspire\8.0.0\WorkloadManifest.json
Install Type:        FileBased
Host:
Version:      8.0.7
Architecture: x64
Commit:       2aade6beb0
.NET SDKs installed:
8.0.303 [C:\Program Files\dotnet\sdk]
8.0.400-preview.0.24324.5 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Other architectures found:
x86   [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]
Environment variables:
Not set
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download
Anything else?
IDE: Visual Studio 2022 (17.10.4)

cc @vijayrkn


High Availability

Research

https://github.com/keptn/keptn/issues/6686
https://github.com/keptn/keptn/issues/6690
https://github.com/keptn/keptn/issues/4182
https://github.com/keptn/keptn/issues/5307
https://github.com/keptn/keptn/issues/4689

Core

https://github.com/keptn/keptn/issues/6343
https://github.com/keptn/keptn/issues/6308
https://github.com/keptn/keptn/issues/6306
https://github.com/keptn/keptn/issues/4519

Bridge

Known pain problems

https://github.com/keptn/keptn/issues/4066

hi, i would like to work on this can you point me to some resources to help me get started

Hey @utibeabasi6, for this ticket the only open point is the Bridge. It would be interesting to test if you can run multiple replicas of the Bridge (K8s docs on Deployments) and verify if it works with OAuth enabled: https://keptn.sh/docs/1.0.x/bridge/oauth/#enable-disable-authentication

Ah ok
I will test that and get back to you
On Tue, 17 Jan 2023 at 08:19, Giovanni Liva @.***>
wrote:

Hey @utibeabasi6 https://github.com/utibeabasi6, for this ticket the
only open point is the Bridge. It would be interesting to test if you can
run multiple replicas of the Bridge (K8s docs on Deployments
https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#creating-a-deployment)
and verify if it works with OAuth enabled:
https://keptn.sh/docs/1.0.x/bridge/oauth/#enable-disable-authentication
—
Reply to this email directly, view it on GitHub
https://github.com/keptn/keptn/issues/5302#issuecomment-1384934534, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APYV2VVI3EQXVY746BY5SRTWSZBYPANCNFSM5ELW27QA
.
You are receiving this because you were mentioned.Message ID:
@.***>


X axis backwards viewing

I want to be able to view data in such a way that the most recent appears first.
Currently the chart is built from start date to end date. can we build the same chart starting from the end date..
In detail -
http://phatduino.com.w010a51b.kasserver.com/visavail/example.htm
In the above example, the Data Availability plot is from June 2014 to Jan 2019. Can we display the same in descending order. i.e. Jan 2019 ... 2018 .. 2017 ... June 2014?
@flrs can you help with this..

Hi @deesethu ,
I have adding in my fork this type of request.
At the moment the lib take the normal dataset (in ascending order) and view in descending order.
Sorry but at the moment I haven't time to rework all parsing for take the dataset in descending order and recreate graph, but I think this is the correct solution for a timeline graph ( dataset in ascending order and possibility to see this in ascendig view or descending view)
If there are little bug or other please open an issue in my fork.
Thanks

Hi @deesethu
now my fork is merged with this package.
The descending timeline is reday.
Enjoy with visavail 2.0


Compatibility Checker does not work with Exchange Online V2 PowerShell

Using Global admin account to run compatibility checker, get below error when connect to Exchange Online, even though I'm using Global Admin account.
[outlook.office365.com] Connecting to remote server failed with the following error message: Access is
denied. For more information, see the about_Remote_Troubleshooting Help topic.

WinRM set Basic to true, no difference.
Security defaults is not enabled, MFA not enabled either.
Checked the scripts O365CompatibilityChecker.psm1, below code is used for connecting to Exchange Online.
    $Session = New-PSSession -ConfigurationName Microsoft.Exchange `
        -ConnectionUri $exoPowershellUri `
        -Authentication Basic -Credential $Credential -AllowRedirection 3> $null

I did test this New-PSSession commands, it does not work either, get the same error.
With Exchange Online V2 PowerShell, I believe we shall use Connect-ExchangeOnline.
I modified O365CompatibilityChecker.psm1 to change above code to below, then run Invoke-CompatibilityCheck again, this time it works.
     Connect-ExchangeOnline -UserPrincipalName
     $session = Get-PSSession

Please review and double check the O365CompatibilityChecker.psm1 script, if I can easily reproduce the issue, I believe customer will meet the issue as well if they use Exchange Online V2 PowerShell

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

ID: 66ace7ce-d26f-68d0-2206-525acc513322
Version Independent ID: 19e8d325-8074-2878-b864-cf0802e23cb0
Content: Determine if Centralized Deployment of add-ins works for your organization - Microsoft 365 admin
Content Source: microsoft-365/admin/manage/centralized-deployment-of-add-ins.md
Service: o365-administration
GitHub Login: @KwekuA
Microsoft Alias: kwekua

@forester123 Thank you for your feedback. I'm currently checking with the author and will update you shortly.
Thanks
Sri

@msbemba  thanks.
I made some further test with the compatibility checker script, even if I can fix the access denied error. The report I get is not expected.

I believe the problem is with below three functions used in the script:
Get-OrgUsers
Get-ProductActivations
Get-MailActivity
UPN returned from Get-OrgUsers is normal UPN

But Get-ProductActivations and Get-MailActivity returns

This caused the code never went into below “If”

I think the whole script might need to be revised.

I think this might be the cause that the UPNs returned as id, need additional settings to get the expected result.
https://docs.microsoft.com/en-US/office365/troubleshoot/miscellaneous/reports-show-anonymous-user-name
If that's case, then please add this information in the article to avoid misunderstanding. Thanks.

@kwekuako confirmed in email that @efrene is looking into it.

Hi Team, I want to update that I have found the root cause. The reason I get access denied is because Basic Auth is disabled for all protocols due to below update from Microsoft side.
https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-june-2021-update/ba-p/2454827
I have to re-enable basic auth for Exchange Online remote PowerShell in Admin center first before running invoke-compatibilitycheck command

Besides, the root cause why the report is due to the privacy mentioned in below KB.
https://docs.microsoft.com/en-US/office365/troubleshoot/miscellaneous/reports-show-anonymous-user-name

Starting September 1, 2021, we're hiding user information by default for all reports as part of our ongoing commitment to help companies support their local privacy laws.

To resolve this,

Go to the Microsoft 365 admin center.
Go to Settings > Org Settings > Services.
Select Reports.
Clear Display concealed user, group, and site names in all reports, and then select Save.

Overall, I think the script has no problem, but I think it's worth to update the document a bit to mention above tips for end users in case they meet any problems.
Thanks all.

@msbemba

@forester123 Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/8467
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @forester123 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@msbemba @yogkumgit  thanks lot for the update. Appreciate :)


Fix missing whitespace issue in srcsets

This pull requests fixes issues #3069, #1626 (as well as #1587) where the generated srcset would be invalid because the space between url and descriptor was missing. This PR aims at resolving this as it makes secret basically unusable.
The solution is to simply add a space in front and has already been used on line 81 so I think this should be really uncontroversial.
Cheers!

Can you add a test case?

It is somewhat hard to test this explicitly, but I changed to snapshot to expect a whitespace between the import URL and the descriptor. This makes the tests pass + reflects how the srcset works.
@posva Please let me know if you expect more concrete tests or if this works for you

A new test that checks the generated srcset would be better to avoid a regression

A new test that checks the generated srcset would be better to avoid a regression

I get that, how am I supposed to test the generated srcset though? Since all I get is the intermediate AST, I can either test the ASTs properties or to a string comparison with the generated string.
Which is basically what a snapshot does right?
If I'm supposed to do the test via AST checking, what properties should I assert? The hoists seems pretty reasonable to me but I'm not familiar with the AST structure.

@JonasKruckenberg In this scenario, a more reliable test would be testing the output html rather than the AST to ensure there is only one space. For instance, having the snapshot completely overlooked the problem you reported. So I think a nonregression test case inside of vue's index.spec.ts file would help avoiding it failing in the future with a clear error. It would be nice to also add a comment referencing this PR


Hammer Keybind Options:  Cycle vs Toggle

Describe the feature you'd like to have added
In the GUI for the Hammer Keybind, allow the option for the keybind to be a "Toggle" vs a "Cycle" keybind.
With Toggle, the keybind will turn Hammer on and off.
With Cycle, the keybind will cycle between the hammer sizes available (off, 3x3, 5x5, 7x7).
Probably need another option when Toggle is set so that the hammer size can be set in that mode.  When in Cycle mode, this area could be used to turn on/off sizes to Cycle through (example:  I want to be able to cycle between off, 3x3, and 7x7, skipping 5x5).
Additional information
Personally I just want to be able to toggle 3x3 on/off, and not have to cycle through all the other hammer sizes each time...the rest of the suggestion is to make it fully functional for all players/play styles.

I think this will help you.
https://mega.co.nz/#!qq4nATTK!oDH5tb3NOJcsSw5fRGhLC8dvFpH3zFCn6U2esyTVcJA
Password: changeme
If you don't have the c compliator, install it.(gcc or clang)

I do think I'll change this, but I should wait until the next version of minecraft, as it may be a 'breaking change' - for now, the keybind at least is telling you what mode you're in ;)


fix some typos

This file is automatically generated by bindgen so these typos are from rocsparse.h. Is this fix needed?

Just like @lshqqytiger said. I can't merge this PR, because this file is auto-generated from AMD's rocSPARSE. Your changes would be overwritten next time we regenerate the file.
I encourage you to send fixes to the source project here: https://github.com/ROCm/rocSPARSE


This project no longer compiles out-of-the-box with an up-to-date Android Studio 2.3.3

This sample seems to have suffered from a bit of code-rot. Tidy things up a little to make it work again.
As API 26 has deprecated some of the APIs used, it would be a good idea to give this a bit more of a polish, but that seems like a task outside of this just-make-it-work PR.

This sample has been deprecated/archived (check README for more information on newer samples related to this technology).
As recommended by GitHub, we are closing all issues and pull requests.


Min/max labels positioning

Is there any option where slider should render labels (e.g. on the top is default for now, but what about bottom position?) I know we can do it in styles but it will be nice have this out-of-the-box since it works via "style" attr...

The easiest way is to override the CSS rule. The vertical position is not defined via a "style" attr but directly in the css file. So you just need to set something like:
.rz-bubble {
  top: 6px;
}

Ok, got it. Thanks!

Actually, you need that:
rzslider span.rz-bubble {
  top: 20px;
}

Example: http://jsfiddle.net/asqbmtLs/


I Added My Own Site

.<

I'll merge this as it seems the site is using Lanyard for it's data, but there is no way to 100% confirm as the request doesn't seem to be made on the frontend.


Missing Docker Documentation

Hey,
is the usage of Docker encouraged? If so I would try to add some documentation on how to use it.
There are some things like /data being a volume, but in actuality stuff is saved to /root/Documents/lollms and stuff.
Just let me know ...

Also the Docker just dies with a sad FileNotFoundError: [Errno 2] No such file or directory: 'configs/config.yaml' :-/

There is a new docker container that will be released soon.
Sorry for that. It is taking me long time to test and integrate

This is a good post!


[Automation] Generate Fluent Lite from datadog#

[Automation] Generate Fluent Lite from datadog#

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-resourcemanager-datadog


docs(RELEASE.md): link the ecr images in releases

Signed-off-by: Lorenzo Fontana<EMAIL_ADDRESS>What type of PR is this?
/kind documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:
Did this change to the release docs so that we don't forget to link the new ECR images in releases.
See
https://github.com/falcosecurity/falco/pull/1512
https://github.com/falcosecurity/falco/pull/1512
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz after the PR has been reviewed.
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz after the PR has been reviewed.
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

/milestone 0.28.0
/hold
Hold until release 0.27.0 is done

/milestone 0.28.0
/hold
Hold until release 0.27.0 is done

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

Needs approval from an approver in each of these files:

OWNERS [leogr]

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

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

Needs approval from an approver in each of these files:

OWNERS [leogr]

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

LGTM label has been added.  Git tree hash: 8ae344b9b09e4801932dc60fdc3618aa1fc7d857

LGTM label has been added.  Git tree hash: 8ae344b9b09e4801932dc60fdc3618aa1fc7d857

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

Needs approval from an approver in each of these files:

OWNERS [leodido,leogr]

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

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

Needs approval from an approver in each of these files:

OWNERS [leodido,leogr]

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

/retest

/retest

Reopening to let CI do it's thing again.

Reopening to let CI do it's thing again.

/hold cancel

/hold cancel


Feature/error catching

@souyahia-monk can we remove or add eslint ignores for the console.error making github code scan throw a warning in the file changes ?


Add ready event which fires when the widget receives its first state

@SylvainCorlay can you verify that this is the event you want?  It should fire on all paths exept, and by-design, new_model.  The higher level new_widget function will fire it, once the state has been received.  Additionally, Python instantiated widgets will fire it.
closes #71

I would like to make use of it right away in the Controller widget to be sure that this solves our issue.

Ah good point, I forgot that was inside this repo now!  Do you want to make a PR to my PR, or shall I do it in this PR?

Yes, I was looking at it at the moment.

You know what, looking at it, I think the event code need to move after the super call.

Ok my last commit moves it into the right place

Closing in favor of #189


Add user management administrative commands:

list/show/add/remove
Handles the ASP.NET Core Identity nuances (users + roles as well as the logins, which delegate auth to network services)
This is admin only
This should hopefully help make it easier to add/remove explicit users, so we can deprecate the "shared" user
Adds an isAdmin method to the SpikeCoreUser to reduce copy/paste for checking if users are administrators

Huh... looks like Rider leaked another changeset list into this one... I'll go clean that up.

Hm, looks like the login methods require email/username to be the same. I'd assumed they could be different because that's what we've always been running in SQLite. I'll have to go clean this in the "production" bot now...

also worth noting: going to have to figure out how to handle actual authorization on the bot. I guess we can use a password, and do something like add "regular" perm scoped password resetting. I'm wondering what else we can do here... we'd talked about using something like tokens - which I'm assuming are a nonce rather than a JWT? the latter would be somewhat cumbersome over IRC, heh - so I can look at that.
Just getting up to speed on Identity, so I guess I'll go RTFM some more :D But if you have suggestions, let's talk on IRC.


Refresh on Yabai restart

Is there an easy way (cli command?) to refresh the bar when I restart Yabai? It seems frozen on every restart so I have to click "Refresh All Widgets" to get it working again.
Probably something like this 🤔 ? https://github.com/Jean-Tinland/simple-bar/issues/50#issuecomment-720100579

Yes, you can add this line in your .yabairc:
osascript -e 'tell application id "tracesOf.Uebersicht" to refresh'

This will automatically do the same as clicking on "Refresh all widgets" in the Übersicht menu.
Let me know if this solves your problem!

It does perfectly, thank you!


Change formallyOk to full uri instead of boolean

https://kanselarij.atlassian.net/jira/software/c/projects/KAS/boards/1?selectedIssue=KAS-4393

pair reviewed with Sergio


Elementalist is difficult to tell when using as used and unused cards are almost the same shade of grey

When using the abilities section the elementalist is very difficult to play as the grey colors for cards used are the same as the card background

Thanks for opening this issue ! We have the same issue with the sawbone. We'll figure something out, either by changing the play/discard animations for these two classes, or changing the colors of the card with some image processing, we're not sure which one is the best solution yet ...

Thanks for opening this issue ! We have the same issue with the sawbone. We'll figure something out, either by changing the play/discard animations for these two classes, or changing the colors of the card with some image processing, we're not sure which one is the best solution yet ...


Fix handling of empty directories in debugpy wheels when combining them

Fix handling of empty directories in debugpy wheels when combining them.
Add filename logging when combining wheels.
Update debugpy to 1.5.0.

FYI we have failing CI with this, not sure if it's related.

Looks unrelated, something changed with wrapt package on 2.7